Related
I have a small hunch that some of you want a one shot, easy way to downgrade to the most recent AW 1.5 version. Here it is. Flash with TWRP.
THIS WILL WIPE YOUR DATA!!!! THIS WILL WIPE YOUR DATA!!! THIS WILL WIPE YOUR DATA!!!
The first boot takes a while. Be patient.
https://www.androidfilehost.com/?fid=889764386195900228
To disable OTA updates, do the following:
1. Download supersuwear.zip (attached to this post) and flash in TWRP to root the watch.
2. Factory reset the watch in TWRP.
3. Boot normally. DO NOT SET UP THE WATCH YET.
4. At the welcome screen, hold the power button until you get into settings.
5. Enable USB debugging.
6. Download the latest version of Google Play Services from here: https://www.apkmirror.com/apk/google-inc/google-play-services-android-wear/
7. Connect to your computer and install this apk file by performing the following command:
adb install -r C:\path to apk file\file.apk
This might take a few minutes. Do not close the window until it says Success.
6. Either use the batch file attached to this post (rename to killUpdate.bat, move to same folder as adb.exe, double click on it) or perform the following commands:
adb shell
su
pm disable com.google.android.gms/.update.SystemUpdateServiceActiveReceiver
pm disable com.google.android.gms/.update.SystemUpdateService
pm disable com.google.android.gms/.update.SystemUpdateGcmTaskService
pm disable com.google.android.gms/.update.SystemUpdateWearableActivity
pm disable com.google.android.gms/.chimera.GmsIntentOperationService
7. Reboot the watch.
8. Flash unsu.zip to remove root if desired.
9. Feel free to setup and use the watch normally now.
You will need to repeat these steps if you ever factory reset the watch or delete the data for Google Play Services in the future. If the update ever pops up again, please let me know in this thread or pm me. If you change your mind and you want to go 2.0, use the restoreUpdate batch file in the same way that you used the killUpdate batch file.
TheSt33v said:
I have a small hunch that some of you want a one shot, easy way to downgrade to the most recent AW 1.5 version. Here it is. Flash with TWRP.
THIS WILL WIPE YOUR DATA!!!! THIS WILL WIPE YOUR DATA!!! THIS WILL WIPE YOUR DATA!!!
The first boot takes a while. Be patient.
I tried to make it so OTA updates were disabled in this version, but I haven't been able to test it yet. If someone could test that for me, that would be awesome.
https://mega.nz/#!vwZhjZrK!S_3yyZo1JjyQgq3XJTp8ZXpNDb_DVwtyAhlvEForHUA
Click to expand...
Click to collapse
big thx !!! (i dont like the 2.0!)
one question. is the the "full" image or OTA ? completly stock?
i try this when i'm back home ;o)
btw. i found this (maybe helpfull)->
https://forum.xda-developers.com/g-watch-r/general/to-android-wear-1-5-complete-guide-t3592606
ELIMINATE THE PERSISTENT UPDATE NOTIFICATION
need rooted watch (orginal thread is for LG watch!!!)
1) adb shell
2) su
3) pm disable com.google.android.gms/.update.SystemUpdateService
4) pm disable com.google.android.gsf/.update.SystemUpdateService
Click to expand...
Click to collapse
inteks said:
big thx !!! (i dont like the 2.0!)
one question. is the the "full" image or OTA ? completly stock?
i try this when i'm back home ;o)
btw. i found this (maybe helpfull)->
https://forum.xda-developers.com/g-watch-r/general/to-android-wear-1-5-complete-guide-t3592606
Click to expand...
Click to collapse
It is completely stock. It's the full image, but it does not include the bootloader, userdata, cache or recovery images. Including the bootloader is unnecessary, as 1.5 runs just fine with the 2.0 bootloader and flashing the bootloader would require that people unlock their bootloaders first. Without the bootloader image, this package can be flashed with a locked bootloader. I didn't include userdata or cache because these partitions were not changed at any point in the history of HW updates, so simply wiping those partitions is sufficient. I didn't include recovery.img because that would erase people's TWRP installations, and if you never plan on updating, there is no reason to have the stock recovery. However, if anyone wants any of the images that I left out, I have them and will provide them upon request.
The commands that you linked to are integrated in this zip. Please let me know if you see any OTA pop ups when you give this a try. If it doesn't work, I'll try to figure out a better way to disable them.
TheSt33v said:
It is completely stock. It's the full image, but it does not include the bootloader, userdata, cache or recovery images. Including the bootloader is unnecessary, as 1.5 runs just fine with the 2.0 bootloader and flashing the bootloader would require that people unlock their bootloaders first. Without the bootloader image, this package can be flashed with a locked bootloader. I didn't include userdata or cache because these partitions were not changed at any point in the history of HW updates, so simply wiping those partitions is sufficient. I didn't include recovery.img because that would erase people's TWRP installations, and if you never plan on updating, there is no reason to have the stock recovery. However, if anyone wants any of the images that I left out, I have them and will provide them upon request.
The commands that you linked to are integrated in this zip. Please let me know if you see any OTA pop ups when you give this a try. If it doesn't work, I'll try to figure out a better way to disable them.
Click to expand...
Click to collapse
Hi TheSt33v,
I'm trying to better understand how to deploy this to my Huawei watch, as I'm not so certain on which you refer to with regards to using TWRP. Would you, or anyone else, be so kind as to provide a quick write-up or how-to on how to reflash with this image?
Everything I've found so far refers to using ADB to flash the watch, and unsure if that is the same or a different process to using TWRP.
I really dislike AW 2.0 and have no intention to ever go back to it should I be successful in downgrading back to 1.5.
Thank you very much for the work you have done and I hope that you (or someone else) can give just a quick guide.
Thanks everyone!
goto https://forum.xda-developers.com/hu...ecovery-negalite-hw-twrp-3-0-2-0-lz4-t3448137
and download negalite-HW-TWRP-3.0.3-v1.5.img
enable usb debugging
adb push '.\Downgrade to M9E42C.zip' /sdcard/
adb reboot bootloader
fastboot boot negalite-HW-TWRP-3.0.3-v1.5.img
on watch select "install zip"
select /sdcard/Downgrade to M9E42C.zip
Jrubes said:
Hi TheSt33v,
I'm trying to better understand how to deploy this to my Huawei watch, as I'm not so certain on which you refer to with regards to using TWRP. Would you, or anyone else, be so kind as to provide a quick write-up or how-to on how to reflash with this image?
Everything I've found so far refers to using ADB to flash the watch, and unsure if that is the same or a different process to using TWRP.
I really dislike AW 2.0 and have no intention to ever go back to it should I be successful in downgrading back to 1.5.
Thank you very much for the work you have done and I hope that you (or someone else) can give just a quick guide.
Thanks everyone!
Click to expand...
Click to collapse
The guide provided by inteks is accurate, mostly. Alternatively, you can use the same method with my updated version of TWRP here: https://forum.xda-developers.com/hu...ent/recovery-twrp-3-1-0-0-unofficial-t3603001. The older version should work just as well though.
inteks said:
goto https://forum.xda-developers.com/hu...ecovery-negalite-hw-twrp-3-0-2-0-lz4-t3448137
and download negalite-HW-TWRP-3.0.3-v1.5.img
enable usb debugging
adb push '.\Downgrade to M9E42C.zip' /sdcard/
adb reboot bootloader
fastboot boot negalite-HW-TWRP-3.0.3-v1.5.img
on watch select "install zip"
select /sdcard/Downgrade to M9E42C.zip
Click to expand...
Click to collapse
adb reboot-bootloader
TheSt33v said:
adb reboot-bootloader
Click to expand...
Click to collapse
adb reboot bootloader also work i know this because that are the steps i put into my console
anyway
but it seems that your disableOTA.sh does not work. it runs without errors but the services are still active. maybe because pm cannot disable services from recovery if wear is not running...
i flashed superuser and disabled them from adb shell.
this is my "debloat" script
Code:
pm disable com.google.android.gms/.update.SystemUpdateService
pm disable com.google.android.gsf/.update.SystemUpdateService
pm disable com.google.android.apps.fitness
pm uninstall me.timos.busyboxonrails
pm disable com.huawei.dailytrack
(chargedetection has to be disabled if you use chargingwidget)
Code:
pm disable com.huawei.mercury.chargedetection
inteks said:
adb reboot bootloader also work i know this because that are the steps i put into my console
anyway
but it seems that your disableOTA.sh does not work. it runs without errors but the services are still active. maybe because pm cannot disable services from recovery if wear is not running...
i flashed superuser and disabled them from adb shell.
this is my "debloat" script
Code:
pm disable com.google.android.gms/.update.SystemUpdateService
pm disable com.google.android.gsf/.update.SystemUpdateService
pm disable com.google.android.apps.fitness
pm uninstall me.timos.busyboxonrails
pm disable com.huawei.dailytrack
(chargedetection has to be disabled if you use chargingwidget)
Code:
pm disable com.huawei.mercury.chargedetection
Click to expand...
Click to collapse
I thought that might be the case. My goal was to make this as easy as possible, so I don't want to tell people to root just yet. I'll see if I can include a script that runs at boot that disables the services. Rooting might be unavoidable though. If it is, I'll pre-root the image.
Maybe I can decompile the appropriate apk and disable it that way...
Thanks everyone! I was able to successfully downgrade back to 1.5 with this information. As previously mentioned, the update notification is still there.
Thanks again for all the hard work and the assistance.
TheSt33v said:
It is completely stock. It's the full image, but it does not include the bootloader, userdata, cache or recovery images. Including the bootloader is unnecessary, as 1.5 runs just fine with the 2.0 bootloader and flashing the bootloader would require that people unlock their bootloaders first. Without the bootloader image, this package can be flashed with a locked bootloader. I didn't include userdata or cache because these partitions were not changed at any point in the history of HW updates, so simply wiping those partitions is sufficient. I didn't include recovery.img because that would erase people's TWRP installations, and if you never plan on updating, there is no reason to have the stock recovery. However, if anyone wants any of the images that I left out, I have them and will provide them upon request.
The commands that you linked to are integrated in this zip. Please let me know if you see any OTA pop ups when you give this a try. If it doesn't work, I'll try to figure out a better way to disable them.
Click to expand...
Click to collapse
Thanks for your work! I want to back to competely stock M9E42C but I find the files just for M6E69F. Can you share all the images please? Also, do I have to wipe data, cache, or something in twrp?
EDIT: I found the zip containing the 3 OTAs to install in M6E69F. Which is the right way?
agarth said:
Thanks for your work! I want to back to competely stock M9E42C but I find the files just for M6E69F. Can you share all the images please? Also, do I have to wipe data, cache, or something in twrp?
EDIT: I found the zip containing the 3 OTAs to install in M6E69F. Which is the right way?
Click to expand...
Click to collapse
If you found the zip containing the 3 OTAs, just install them in order (update1, update2, update3) when you're on M6E69F. Make sure to reboot in between each update.
Or if you prefer, flash my M9E42C zip (cache and data are wiped automatically) and then flash the following images via fastboot:
Recovery: https://www.androidfilehost.com/?fid=817550096634771860
Bootloader: https://www.androidfilehost.com/?fid=673368273298957367
TheSt33v said:
If you found the zip containing the 3 OTAs, just install them in order (update1, update2, update3) when you're on M6E69F. Make sure to reboot in between each update.
Or if you prefer, flash my M9E42C zip (cache and data are wiped automatically) and then flash the following images via fastboot:
Recovery: https://www.androidfilehost.com/?fid=817550096634771860
Bootloader: https://www.androidfilehost.com/?fid=673368273298957367
Click to expand...
Click to collapse
Thanks a lot for the clear answer! :good:
I have flashed the supersuwear.zip in twrp rebooted and when I try to SU, I get
/system/bin/sh: su: not found
NM I got it
Is there any stock fastboot .img files for wear 1.5 or 2.0?
I want to go completely stock whenever I want to.
It seems that there was a download link in developer.android.com but it must have been removed...
Can anyone share fastboot img files?
I especially need stock wear 2.0 recovery img or all images for wear 1.5.
Also a noob question: is it safe to relock after flashing twrp? When I used Huawei 6P, its bootloader shouldn't be unlocked unless every file(boot, recovery, system, etc...) is completely stock. Is it the same with Hwatch?
Does this require a bootloader unlock before proceeding?
(Please ignore, found the answer (it doesn't), mustve been blind )
ddaggebi said:
Is there any stock fastboot .img files for wear 1.5 or 2.0?
I want to go completely stock whenever I want to.
It seems that there was a download link in developer.android.com but it must have been removed...
Can anyone share fastboot img files?
I especially need stock wear 2.0 recovery img or all images for wear 1.5.
Also a noob question: is it safe to relock after flashing twrp? When I used Huawei 6P, its bootloader shouldn't be unlocked unless every file(boot, recovery, system, etc...) is completely stock. Is it the same with Hwatch?
Click to expand...
Click to collapse
Sorry for the late response, but here is the factory image for 1.5 build M6E69F (not the most recent build of 1.5): https://www.androidfilehost.com/?fid=745425885120748838
Here are the three OTAs that will take you from M6E69F to M9E42C (do not flash directly, extract the three zips within and flash those in order): https://www.androidfilehost.com/?fid=745425885120732730
I'm not aware of any other official factory images other than the 2.0 dev preview images, but I didn't hang on to those.
Also, note that if you take an OTA from ANY version of 1.5 using your watch's official OTA function, you will be directly updated to 2.0. You can't use the OTA function to get to the latest version of 1.5. The only options are using the official OTAs that I posted or flashing the TWRP package that takes you straight there.
TheSt33v said:
Sorry for the late response, but here is the factory image for 1.5 build M6E69F (not the most recent build of 1.5): https://www.androidfilehost.com/?fid=745425885120748838
Here are the three OTAs that will take you from M6E69F to M9E42C (do not flash directly, extract the three zips within and flash those in order): https://www.androidfilehost.com/?fid=745425885120732730
I'm not aware of any other official factory images other than the 2.0 dev preview images, but I didn't hang on to those.
Also, note that if you take an OTA from ANY version of 1.5 using your watch's official OTA function, you will be directly updated to 2.0. You can't use the OTA function to get to the latest version of 1.5. The only options are using the official OTAs that I posted or flashing the TWRP package that takes you straight there.
Click to expand...
Click to collapse
Thanks for kindly answering my nooby question!
So in theory, if I want to set my watch to completely stock 2.0, I have to flash 1.5 factory image and OTA it to 2.0, right? Again, Thanks!
ddaggebi said:
Thanks for kindly answering my nooby question!
So in theory, if I want to set my watch to completely stock 2.0, I have to flash 1.5 factory image and OTA it to 2.0, right? Again, Thanks!
Click to expand...
Click to collapse
Yes
I was on Android Wear 2.0 with a locked bootloader.
Now I just tried this method to downgrade from 2.0 to 1.5.
I installed TWRP, then pushed the zip file to /sdcard/
Flashed the zip in TWRP. Now it's stuck on the google animation for like 20mins now.. is this normal?
I installed the 8.1 dp on my pixel 2 xl and I have decided to go back to android 8.0. I signed out of the beta and the OTA showed up as it was supposed to, from there I tried to install the downgrading OTA but it came up with a generic error (update was not able to be installed) from there I decided to try flashing the factory image and this error came up
writing 'bootb'...
FAILED (remote: No such partition.)
and when I rebooted it booted fine but was still on android 8.1. I also tried manually flashing the system partition as I noticed the script made no mention of flashing system, it came up with the error
sending sparse 'systemb' 1/4 (524284 KB)...
OKAY [ 16.552s]
writing 'systemb' 1/4...
FAILED (remote: No such partition.)
and once again after a reboot it went back to android 8.1. Any help is appreciated, thanks.
Download and flash the entire Factory image from Google's factory image page. That should work. However, this will wipe your phone.
I did flash the factory image which is what resulted in the partition error.
If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.
Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.
Moostafa29 said:
If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.
Click to expand...
Click to collapse
I already tried downgrading through the OTA, it came up with a generic error.
clnzx2 said:
Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.
Click to expand...
Click to collapse
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.
I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).
I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,
TheSt33v said:
I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).
Click to expand...
Click to collapse
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
TheDonXR said:
I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,
Click to expand...
Click to collapse
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.
Afriendlytrashcan said:
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.
Click to expand...
Click to collapse
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.
Afriendlytrashcan said:
I already tried downgrading through the OTA, it came up with a generic error.
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.
Click to expand...
Click to collapse
That is your problem. Update to latest tools and it will work. :good:
TheSt33v said:
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.
Click to expand...
Click to collapse
clnzx2 said:
That is your problem. Update to latest tools and it will work. :good:
Click to expand...
Click to collapse
Sounds good! I'll try it a bit later, my fingers have never been more crossed.
It worked! After updating fastboot the flash-all zip worked perfectly. Thanks everyone for your help!
Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock
TimeTurn said:
Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock
Click to expand...
Click to collapse
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???
Badger50 said:
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???
Click to expand...
Click to collapse
He said he was tired...
galaxys said:
He said he was tired...
Click to expand...
Click to collapse
Well shucks! ???
so actualy there is option to go back in versions?
that's nice!
I7210I said:
so actualy there is option to go back in versions?
that's nice!
Click to expand...
Click to collapse
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 ?
Badger50 said:
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 [emoji50]
Click to expand...
Click to collapse
so it's not quite works now?
in nexus it was worked right away
Sent from my Pixel 2 XL using Tapatalk
•••••• Qualcomm Moto E (4th Gen) Perry ••••••
Factory Firmware & Flashing/Restoration Guide
MetroPCS / T-Mobile Moto E4 (XT1765)
OVERVIEW:
This guide provides factory firmware for both the MetroPCS and T-Mobile branded variants of the Moto E4 Perry (xt1765). While these two packages appear to be similar and multi-compatible, I do not own the xt1765 and cannot confirm this. So, to be safe, use only the firmware package for your branded carrier. This guide can be used to repair a device which is buggy, unstable, or stuck in a boot loop. Likewise, device owners wishing to restore their device to an unmodified, stock factory state will also find this guide beneficial. Installing this firmware will remove any custom mods from your device, such as root binaries, BusyBox binaries, Xposed framework, etc. Also, force encryption and verified boot (dm-verity/avb) will be enabled. If you have TWRP custom recovery installed, it will be replaced by the stock recovery image.
DISCLAIMER:
You are using this guide and flashing firmware to your device solely at your own risk. While these firmwares have been tested and confirmed to work on their respective variants, by proceeding further, you are absolving me of any liability or responsibility in the event you brick your device or otherwise render it inoperable. Follow the simple instructions carefully and things should go smoothly.
SPECIFICATIONS:
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•MetroPCS Moto E4 (xt1765) Perry
•Android Version: 7.1.1 Nougat
•Build No. NCQS26.69-64-3
•System Version: 26.261.9.perry_metropcs.en.US
•Radio Version: M8917TMO_18.08.04.18R
•Security Patch Level: March 1, 2018
•Kernel Version: Linux 3.18.31-perf
•Build Date: March 16, 2018
•Firmware Package Size: 1.36 GB
•Download Link: https://drive.google.com/file/d/17sJS8VpxSAHupqiqJQQb4wa1jHIP61uT/view?usp=drivesdk
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
•T-Mobile Moto E4 (xt1765) Perry
•Android Version: 7.1.1 Nougat
•Build No. NCQS26.69-64-6
•System Version: 26.271.7.perry_tmo.tmo.en.US
•Radio Version: M8917TMO_18.08.04.18.01R
•Security Patch Level: May 1, 2018
•Kernel Version: Linux 3.18.31-perf
•Build Date: May 2, 2018
•Firmware Package Size: 1.33 GB
•Download Link: https://drive.google.com/file/d/1C21fgdBVn6hhPtAo5yult-PdB6DSr4HS/view?usp=drivesdk
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
REQUIREMENTS:
This guide assumes that you have the latest version of the Minimal ADB & Fastboot utilities installed on your PC or laptop. If you do not, you can download the latest version, v1.4.3, from this MediaFire link: http://www.mediafire.com/file/ccnnv843a20tqbn/minimal_adb_fastboot_v1.4.3.zip It is also a good idea to have at least a rudimentary understanding of fastboot command line execution. There are some excellent guides here on XDA which outline the subjects of fastboot mode & fastboot commands.
In addition, to ensure that up-to-date USB device drivers are installed on your PC, download & install the latest Motorola Device Manager. You can get the latest version directly from this Motorola support link: https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
NOTE:
Because these are factory firmware packages, in theory, xt1765 owners should be able to flash these packages, using the below instructions, to devices with a locked bootloader. Please note, however, that these firmwares were leaked by the manufacturer and may or may not be digitally signed by the OEM. In sum, I cannot confirm whether these firmwares will flash to a locked bootloader device. I can only confirm that the firmware will install normally on a device with an unlocked bootloader. As confirmation becomes available from other members in this regard, I will add the info to this thread.
On a second note, flashing this factory firmware does not re-lock an already unlocked bootloader. Also, contrary to popular misbelief, re-locking your bootloader IS NOT required in order for your device to be able to install OTA update packages. To enable your device to install OTA updates, you need only install the firmware package for your variant using the below instructions.
WARNING: The below instructions include a command for wiping your /userdata partition (fastboot erase userdata) which will effectively wipe all of your saved files, photos, videos, app data and other media. This is recommended for a clean install of the firmware, and to ensure optimal results. However, if you are stuck in a boot loop, for example, and have important files saved to internal storage that you want to try and salvage, simply skip over the "fastboot erase userdata" command and give it a try.
INSTRUCTIONS:
• 1. Download the firmware package for your branded carrier on your PC or laptop. Extract the contents of the package to your ADB/Fastboot directory;
• 2. Boot your device into fastboot mode and connect your device to your PC with the OEM or a quality equivalent micro USB to USB sync cable;
• 3. Open a command window in the path of your ADB/Fastboot directory and execute:
fastboot devices
If your device and PC are properly connected, the command window will return an alphanumeric value synonymous of your device serial number;
• 4. Once a proper connection has been established, execute the following commands, preferably in this order:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
Done. Now execute:
fastboot reboot
Upon reboot, your device should be restored to unmodified stock condition, and your device will be capable of installing pending or future OTA update packages.
Thanks for posting this! Looks very comprehensive and nOObproof.... I'm going to try this out in the next few days and I will report back if I had any trouble following the instructions and let your know if I feel anything needs to be clarified. I don't foresee having any problems with this though. I appreciate you and your hard work to put this together
AesopRock127 said:
Thanks for posting this! Looks very comprehensive and nOObproof.... I'm going to try this out in the next few days and I will report back if I had any trouble following the instructions and let your know if I feel anything needs to be clarified. I don't foresee having any problems with this though. I appreciate you and your hard work to put this together
Click to expand...
Click to collapse
No problem. I've been reading a lot of posts of members needing more up-to-date xt1765 stock firmware, so I hope it helps some members. These are the same instructions and structural format that I use on all of my Moto/Lenovo firmware threads. The order of the command lines are set out exactly the same as those used in certified Motorola/Lenovo service centers. If you follow the instructions to the letter, there is no doubt that you'll have your device fully restored to stock factory condition.
When I have the time to do so, I'll use these firmwares with my Android Kitchen to cook up TWRP flashable stock ROMs for the MetroPCS & T-Mobile xt1765 models.
MotoJunkie01 said:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
My question is if i want to keep twrp as my recovery is it as simple as not running the command fastboot flash recovery recovery.img?
AesopRock127 said:
My question is if i want to keep twrp as my recovery is it as simple as not running the command fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Yes. It is that simple. Just be advised that an OTA will not install normally unless stock recovery is in place. The OTA installation script runs checksums for stock recovery.
The best policy is to flash the firmware in full, install any pending OTAs while running unmodified stock, then reinstall TWRP once you're up to date on the latest firmware build.
MotoJunkie01 said:
Yes. It is that simple. Just be advised that an OTA will not install normally unless stock recovery is in place. The OTA installation script runs checksums for stock recovery.
The best policy is to flash the firmware in full, install any pending OTAs while running unmodified stock, then reinstall TWRP once you're up to date on the latest firmware build.
Click to expand...
Click to collapse
Shiiiiiit I didn't think about that I have an update I'm going to try to do it if it doesn't work guess I'll redo the full process all over again..... By the way I pmd you
EDIT: 69-64-6 updated no problem And immediately offered me 69-64-9 so maybe these updates aren't large enough to worry about twrp instead of stock recovery? Only time will tell I guess
Sent from my Motorola XT1765 using XDA Labs
AesopRock127 said:
Shiiiiiit I didn't think about that I have an update I'm going to try to do it if it doesn't work guess I'll redo the full process all over again..... By the way I pmd you
EDIT: 69-64-6 updated no problem And immediately offered me 69-64-9 so maybe these updates aren't large enough to worry about twrp instead of stock recovery? Only time will tell I guess
Click to expand...
Click to collapse
To simplify things, just keep installing OTAs until you are on the current build. Then, reinstall TWRP. You shouldn't have to redo the whole thing as long as you haven't mounted system as r/w in TWRP. And as long as you haven't flashed Magisk or SuperSU for root. Just reboot into fastboot and flash the stock recovery and OTAs should be fine.
so i know im a pain in the ass but i followed this guide with no issues and updated fully before installing twrp and root and then couldnt install xposed and ran into a bootloop so decided to go nuclear and start over. My only issue now is after fully following this guide again my OTA updates are failing in stock recovery and when i reboot i get tons of tmobile and moto app FC issues and it says im fully updated even though i started on 69-64-3 and it failed in stock recovery it still says im on 69-64-6 and ive been on 69-64-9 before so not only do i know im not fully updatedd but these FC are driving me nuts. Trying again but does anyone have any clues what could be causing my issues? im having a lot of problems with noverity flashing right and getting the newest twrp to flash instead of only temp boot as well and i feel these issues are all cnnected somehow. I might go back to RR if possible because i was able to get my phone the way i wanted on there for the most part im not sure why stock is giving me such issues? Unfrotunately i cant provide any logs or anything because i am retrying this guide again and see how it goes and didnt think until after the fact to post this
AesopRock127 said:
so i know im a pain in the ass but i followed this guide with no issues and updated fully before installing twrp and root and then couldnt install xposed and ran into a bootloop so decided to go nuclear and start over. My only issue now is after fully following this guide again my OTA updates are failing in stock recovery and when i reboot i get tons of tmobile and moto app FC issues and it says im fully updated even though i started on 69-64-3 and it failed in stock recovery it still says im on 69-64-6 and ive been on 69-64-9 before so not only do i know im not fully updatedd but these FC are driving me nuts. Trying again but does anyone have any clues what could be causing my issues? im having a lot of problems with noverity flashing right and getting the newest twrp to flash instead of only temp boot as well and i feel these issues are all cnnected somehow. I might go back to RR if possible because i was able to get my phone the way i wanted on there for the most part im not sure why stock is giving me such issues? Unfrotunately i cant provide any logs or anything because i am retrying this guide again and see how it goes and didnt think until after the fact to post this
Click to expand...
Click to collapse
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
MotoJunkie01 said:
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
Click to expand...
Click to collapse
Ok thanks. I will try redownloading if it persists but is there any log or anything that would help out in identifying the problem if it still persists after a redownloading of the firmware? It's annoying that stock recovery says error! With no code to help identify the issue
AesopRock127 said:
Ok thanks. I will try redownloading if it persists but is there any log or anything that would help out in identifying the problem if it still persists after a redownloading of the firmware? It's annoying that stock recovery says error! With no code to help identify the issue
Click to expand...
Click to collapse
When stock recovery says ERROR during installation of an OTA, the problem is with the checksums. In other words, the OTA installer is telling stock recovery that you are not running an unmodified stock setup. You can get an error like that from just mounting /system or /oem as r/w. The installer checks your /boot, /recovery, /system and /oem partitions to make sure they are untouched, unmodified stock.
Also, @AesopRock127, there is a quicker and simpler method to install stock firmware to a Moto/Lenovo device called RSD Lite. You can Google for the basic instructions.
Here's a link to RSD Lite v6.2.4: https://drive.google.com/file/d/1MwZPdifKVpR4ZTsE3SSNAFBNr6KU29wY/view?usp=drivesdk
MotoJunkie01 said:
Also, @AesopRock127, there is a quicker and simpler method to install stock firmware to a Moto/Lenovo device called RSD Lite. You can Google for the basic instructions.
Here's a link to RSD Lite v6.2.4: https://drive.google.com/file/d/1MwZPdifKVpR4ZTsE3SSNAFBNr6KU29wY/view?usp=drivesdk
Click to expand...
Click to collapse
Okay so I redid this and the updates are sticking like you said I must have changed something and made it non-stock.... So I do not need the RSD Lite as of yet but I did download it. Looking into it it seems that I may use it to root my device when I get to that point? For now I'm just setting everything up the way I like it and fully intalling stock updates before I get into TWRP and rooting. The goal is a up to date stock, rooted, debloated, and running Xposed and gravitybox. Last time everything went smoothly until I hit xposed. I think it's due to my crappy understanding of selinux permissions, encryption and dm verity.... The best thing about struggling to install stuff like this is it gives you an opportunity to learn. In the past I've been able to follow guides and everything worked as stated so I had no need to get technical and delve into some of the things I've needed to on my xt1765. Thank God for XDA and helpful people like @MotoJunkie01 or I would have hit this phone with a Sledge hammer or chop it in half with a chop saw like I did with the Samsung j3 ?
AesopRock127 said:
Okay so I redid this and the updates are sticking like you said I must have changed something and made it non-stock.... So I do not need the RSD Lite as of yet but I did download it. Looking into it it seems that I may use it to root my device when I get to that point? For now I'm just setting everything up the way I like it and fully intalling stock updates before I get into TWRP and rooting. The goal is a up to date stock, rooted, debloated, and running Xposed and gravitybox. Last time everything went smoothly until I hit xposed. I think it's due to my crappy understanding of selinux permissions, encryption and dm verity.... The best thing about struggling to install stuff like this is it gives you an opportunity to learn. In the past I've been able to follow guides and everything worked as stated so I had no need to get technical and delve into some of the things I've needed to on my xt1765. Thank God for XDA and helpful people like @MotoJunkie01 or I would have hit this phone with a Sledge hammer or chop it in half with a chop saw like I did with the Samsung j3 ?
Click to expand...
Click to collapse
That's good news. I intend on making a TWRP flashable stock ROM for the xt1765 in the very near future. Once you are on the latest stock build, if you could make a TWRP backup of your system image and boot image and upload them, I could use the images to cook up an up-to-date stock ROM for the xt1765.
MotoJunkie01 said:
That's good news. I intend on making a TWRP flashable stock ROM for the xt1765 in the very near future. Once you are on the latest stock build, if you could make a TWRP backup of your system image and boot image and upload them, I could use the images to cook up an up-to-date stock ROM for the xt1765.
Click to expand...
Click to collapse
Absolutely. will do this ASAP. Seems best if I do nothing except boot into TWRP and make the backup? Or can I flash it and it will still work? Basically is the stock recovery needed or can I flash TWRP before I make the backup
so system and boot only or system, system image, and boot? making one now with both systems and one with just normal system since im not sure which you need and dont want to give you to much **** to sift through. also does data need to be decrypted for this to be helpful to you? sorry dont know much about it but am willing to help lol
AesopRock127 said:
Absolutely. will do this ASAP. Seems best if I do nothing except boot into TWRP and make the backup? Or can I flash it and it will still work? Basically is the stock recovery needed or can I flash TWRP before I make the backup
so system and boot only or system, system image, and boot? making one now with both systems and one with just normal system since im not sure which you need and dont want to give you to much **** to sift through. also does data need to be decrypted for this to be helpful to you? sorry dont know much about it but am willing to help lol
Click to expand...
Click to collapse
System image and boot backup with TWRP. Encryption of data isn't relevant to the backups. Whether you boot into TWRP or flash TWRP ....either will work
@MotoJunkie01 Nanodroid backup of encrypted fully uptodate stock system and boot.img only https://ufile.io/b0x6q
uploading the one with the system image too
MotoJunkie01 said:
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.
If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
Click to expand...
Click to collapse
Also verify checksums (MD5, SHA-1, etc) when offered. Fastest way to validate large file integrity. As a matter of practice I never flash critical partitions sans checksum validation.
Davey126 said:
Also verify checksums (MD5, SHA-1, etc) when offered. Fastest way to validate large file integrity. As a matter of practice I never flash critical partitions sans checksum validation.
Click to expand...
Click to collapse
Excellent point. A corrupt flash to a critical partition can equal lights out -- the proverbial hard brick.
this happens to me for the 2nd time, i clean reflashed factory image of android 10, then installed a kernel, twrp and magisk, after installing some magisk mods device bootloops in restarts directing me to twrp recovery, i deleted them using file manager but still the device bootloops and they are not the reason behind the bootloop as they we working before,
something to add is that device selinux is set to permissive and not enforcing, idk if this is the case or no
Fastboot image first then boot the OS. Get back to the bootloader then fastboot twrp image. Flash the twrp installer zip when booted in the twrp image. Reboot to recovery and then flash kernel and magisk last.
wolfeyes30 said:
Fastboot image first then boot the OS. Get back to the bootloader then fastboot twrp image. Flash the twrp installer zip when booted in the twrp image. Reboot to recovery and then flash kernel and magisk last.
Click to expand...
Click to collapse
not working still bootloops
something causing the device to bootloop even enabling core mode only in twrp doesnt work, im fed up i reclean flashed sotfware dozen times, when there was no twrp installed the device bootloops then returns you to stock reocvery or twrp, once i didnt flashed twrp yet so in factory recovery the error was that system cant read data partiton or something like that
latest canary build bootloops after installing any modules and if i installed twrp
im using the version before the latest i made the same behaviour after installing some modules
bootlogs attached in here
Nightf0x_007 said:
not working still bootloops
something causing the device to bootloop even enabling core mode only in twrp doesnt work, im fed up i reclean flashed sotfware dozen times, when there was no twrp installed the device bootloops then returns you to stock reocvery or twrp, once i didnt flashed twrp yet so in factory recovery the error was that system cant read data partiton or something like that
latest canary build bootloops after installing any modules and if i installed twrp
im using the version before the latest i made the same behaviour after installing some modules
bootlogs attached in here
Click to expand...
Click to collapse
I don't know how to read android logs but my IT experience is telling me the OS is having problems with the hardware for some reason, lots of errors at the end freaking out about sensors and hardware.
I would suggest a clean start with just the OS to see if it bootloops before adding twrp or magisk. Use Deuces script to flash the factory image to both slots and get everything setup. Run that way for a day then move on to adding one or the other and gradually add things to see where the loops start. Also, be careful with modules since they aren't all updated for 10 yet.
wgrant said:
I don't know how to read android logs but my IT experience is telling me the OS is having problems with the hardware for some reason, lots of errors at the end freaking out about sensors and hardware.
I would suggest a clean start with just the OS to see if it bootloops before adding twrp or magisk. Use Deuces script to flash the factory image to both slots and get everything setup. Run that way for a day then move on to adding one or the other and gradually add things to see where the loops start. Also, be careful with modules since they aren't all updated for 10 yet.
Click to expand...
Click to collapse
this happens after installing modules they was working before, before all this happens
how to flash factory image to both slots using deuces
Nightf0x_007 said:
this happens after installing modules they was working before, before all this happens
how to flash factory image to both slots using deuces
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...tloop-recovery-flashing-t3704761/post74507988
Download the script, put it in your adb tools folder with the factory image then run it. It'll launch and proceed through the steps to flash the image. If you boot to bootloader before running the script you can hit enter when it says it can't find any adb devices, that's normal because you'll already be in fastboot which it checks next.
Also, I saw in your other thread that you're using the Canary builds. I'm using magisk 19.3 without issue and twrp 3.3.0 with the system mount error that comes up but it still flashes what ask it to. For twrp I flashes the img file to the recovery partition and it's working just fine, no need to use the zip.
wgrant said:
https://forum.xda-developers.com/pi...tloop-recovery-flashing-t3704761/post74507988
Download the script, put it in your adb tools folder with the factory image then run it. It'll launch and proceed through the steps to flash the image. If you boot to bootloader before running the script you can hit enter when it says it can't find any adb devices, that's normal because you'll already be in fastboot which it checks next.
Click to expand...
Click to collapse
yes i know all this and i used the script, but im asking about flashing to both slots should i do something in here or it is automatically done by the script
Nightf0x_007 said:
yes i know all this and i used the script, but im asking about flashing to both slots should i do something in here or it is automatically done by the script
Click to expand...
Click to collapse
The script flashes to both slots instead of just the active slot like the flash-all file Google offers. They're essentially the same thing but Deuces automates a lot of the commands you would need to know and instead let's you reply yes or no to questions. I find it super handy and saves me time.
wgrant said:
The script flashes to both slots instead of just the active slot like the flash-all file Google offers. They're essentially the same thing but Deuces automates a lot of the commands you would need to know and instead let's you reply yes or no to questions. I find it super handy and saves me time.
Click to expand...
Click to collapse
the script only flashes slot B in here is that normal ?
Nightf0x_007 said:
the script only flashes slot B in here is that normal ?
Click to expand...
Click to collapse
No, it's not. The script should flash your active slot then switch to flash the other. You could manually flash using the flash-all that Google gives and manually switch to the other slot. I believe the command is set active slot - a or set active slot - b then run the script while in each one. You may have to Google that command since I don't use it.
wgrant said:
No, it's not. The script should flash your active slot then switch to flash the other. You could manually flash using the flash-all that Google gives and manually switch to the other slot. I believe the command is set active slot - a or set active slot - b then run the script while in each one. You may have to Google that command since I don't use it.
Click to expand...
Click to collapse
Yes i did this but then got error device is corrupted and wont boot, so i flashed the flash all file in the factory image it flashed slot b and flashed one thing only (system) in slot a, so thats right?
Or should i manually switch between slots and run the flash all ?
Nightf0x_007 said:
Yes i did this but then got error device is corrupted and wont boot, so i flashed the flash all file in the factory image it flashed slot b and flashed one thing only (system) in slot a, so thats right?
Or should i manually switch between slots and run the flash all ?
Click to expand...
Click to collapse
It seems like you're misunderstanding. The flash-all file that Google provides will only flash to one slot. So if you wanted to flash to both you have to switch slots manually then run it again. Deuces script does both slots, it won't do only one of them because of the way it is written. Since you can get into fastboot I would just use what comes from Google and flash it then switch and flash again. This should put you in a clean OS on both slots so no matter where you boot from its good. Once that is taken care of you can move on to other twrp and magisk.
All of this sounds like you have old stuff on one slot and keep ending up on there. The A/B structure of the pixel phones is supposed to allow see less updating of the OS so when an update is installed switches you to the new slot for active booting and then the next update it switches to the other slot so on and so on.
wgrant said:
It seems like you're misunderstanding. The flash-all file that Google provides will only flash to one slot. So if you wanted to flash to both you have to switch slots manually then run it again. Deuces script does both slots, it won't do only one of them because of the way it is written. Since you can get into fastboot I would just use what comes from Google and flash it then switch and flash again. This should put you in a clean OS on both slots so no matter where you boot from its good. Once that is taken care of you can move on to other twrp and magisk.
All of this sounds like you have old stuff on one slot and keep ending up on there. The A/B structure of the pixel phones is supposed to allow see less updating of the OS so when an update is installed switches you to the new slot for active booting and then the next update it switches to the other slot so on and so on.
Click to expand...
Click to collapse
this is what i did, i flashed factory image in slot b then manually switched to slot a as active and reflashed image without -w, when booting os, phone shows corrupted device message and wont boot, reset active to b slot phone boots
i will try something now, will flash .019 in slot a then adb sideload .20 ota afaik it should install in opposite slot (b), and will see what happens
Nightf0x_007 said:
this is what i did, i flashed factory image in slot b then manually switched to slot a as active and reflashed image without -w, when booting os, phone shows corrupted device message and wont boot, reset active to b slot phone boots
i will try something now, will flash .019 in slot a then adb sideload .20 ota afaik it should install in opposite slot (b), and will see what happens
Click to expand...
Click to collapse
You data partition may be corrupt and needs to be wiped.
wgrant said:
You data partition may be corrupt and needs to be wiped.
Click to expand...
Click to collapse
i flashed .19 to slot b with wipe userdata, then boot twrp sideloaded ota .20, then erased all data factory reset, setuping device now will see what happens
Nightf0x_007 said:
i flashed .19 to slot b with wipe userdata, then boot twrp sideloaded ota .20, then erased all data factory reset, setuping device now will see what happens
Click to expand...
Click to collapse
Did you manage to get it to work?
leqacy said:
Did you manage to get it to work?
Click to expand...
Click to collapse
Yes, i flashed .19 image then sideloaded .20 ota, tell now things good returning my data step by step
But after i did this intalling twrp after that when i boot os then reboot phone bootloops so i didnt install twrp after that (reflashed .19 ........)
Yesterday it happend suddenly: Battery 5% left, just a quick newsarticle before bed and it left me.
At first it didn't even take any charge. Booted in recovery and it's at 40% now.
But booting doesn't work.
OP Logo, bootanimation for around 20 seconds, repeat...
What I tried:
Power off, reboot
changed active slot
Flash the boot image what was last downloaded by me a while ago (semed to be Boot 12.C44_BA, not sure)
Flash the magisk image
Flashed a C47 image
no difference at all, same boot pattern.
A little sidenote:
I have magisk on my op9p, worked fine. a recent ota update failed repeatedly installing in defaulkt way. at boot i had to switch active slot in fastboot a few times. then it booted to current firmware.
I am wondering why i get the same issue independent from the boot.img.
Why did the low battery started this problem at all? How can i be sure to have the right boot.img flashed.
And most important: how can i boot into andoird again?
let me know if you need more information.
Thanks in advance!
edit:
is it possible to install twrp and backup/restore later the important data?
use msm tool and make all new
ChrisFeiveel84 said:
use msm tool and make all new
Click to expand...
Click to collapse
thanks for the hint! I read about this tool. But this means a full wipe of system and user data, right? any chance to avoid this and rescue images before setting up new?
I see a few possibilities to get closer:
i can boot twrp via fastboot. wiping data seemed to not help.
mounting userdata doesn't work because it needs a pin code which is not my system code.
maybe i have the wrong boot.img? can i find out which firmware version is installed via twrp and flash the right image afterwards?
Speaka said:
I see a few possibilities to get closer:
i can boot twrp via fastboot. wiping data seemed to not help.
mounting userdata doesn't work because it needs a pin code which is not my system code.
maybe i have the wrong boot.img? can i find out which firmware version is installed via twrp and flash the right image afterwards?
Click to expand...
Click to collapse
TWRP doesn't work with A12 only A11 at the moment.
Have you tried getting your hands on the C.62 firmware to local update?
luckylui said:
TWRP doesn't work with A12 only A11 at the moment.
Have you tried getting your hands on the C.62 firmware to local update?
Click to expand...
Click to collapse
thanks for pointing that out!
did not try yet. can you please point me to a howto thread?
what would be the way to update if i have no system access?
Speaka said:
thanks for pointing that out!
did not try yet. can you please point me to a howto thread?
what would be the way to update if i have no system access?
Click to expand...
Click to collapse
Google search "Tool ALL IN ONE" download it and install. Download the C.62 firmware from one of the threads in the forum. Open the tool you installed earlier select generic device from the pop-up. Click on "advanced options" in the tool and that'll bring you to "adb sideload". I hope that works for you!
This sounds promising. I will try that later. To be sure: This will keep personal data like an usual ota update?
Edit: I'm still stuck. Heres what i do: Boot twrp (not install) from fastboot. in twrp start adb sideload. open the toolaio, generic device, advanced options, select firmware.zip and click flash under sideload. Than it prompts "phone is not in adb or fastboot mode". In the main window it show the device id and "adb sideload".
what am i missing?