Related
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
TWERP failed flash message
blairan said:
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
Click to expand...
Click to collapse
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
blairan said:
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
Click to expand...
Click to collapse
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
i'm part way there...
tdhite said:
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
Click to expand...
Click to collapse
OK, I have downloaded the 2 files. placed them in a directory near my root directory on my pc. placed the phone in fastboot usb, opened a command prompt window from that directory. typed in fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014
and I get error: cannot load 'fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014'
per a video showing how to flash recovery, I also tried the command adb reboot bootloader I get error : device not found
back to my pc, I open device manager, and I show a device labeled android device that is working properly.
stumped at this point.
is updating recovery the same as the initial install of a custom recovery?
do I need updated drivers for win 7? where are the latest? all videos say they are the latest, but that was when they were recorted.
thanks for help!
Yes u need updated drivers....any easy solution however is go and get the app flashify u will need root of course...it allows u to flash recovery that is on ur sd card. Just choose the img and flash recovery in the app then reboot into recovery and u will be good to go.
Sent from my HTCONE using Tapatalk
Thank you!
Thanks to both of you, updated TWERP did the trick and Flashify allowed me to install it without the fastboot, and PC hookup which was not working. Latest nightly installed, I am a happy camper!
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Slagathor01 said:
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Click to expand...
Click to collapse
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
luigi311 said:
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I got it with fastboot, I forgot I re installed windows since I did it initially, so I was pulling my hair out wondering why fastboot wouldnt see it, and I couldnt even get files to or from it till I installed HTC sync.....heh
thanks for the info.....
Hellos guys,
I am trying to find the stock recovery for T-mobile US 6.10.531.10 (NOT 6.10.531.9) . Does anybody has it or point me on the right direction? I want to update my phone through OTA so I can get lollipop however I cannot find the stock recovery.
I am S-On all stock except for the recovery, I had TWRP so I can make backups. Now I want to install back the stock recovery so i can upgrade but I don't seem to find it anywhere. I managed to find the RUU but the recovery image is not inside the "rom.zip" on my Temp folder when I run it. These are the only files that it shows:
android-info.txt
dzdata_16g.hdr
dzdata_32g.hdr
dzdata_64g.hdr
tp_HMX852XD.img
boot_signed.img
dzdata_16.img
dzdata_32.img
dzdata_64.img
Am I missing something? Please help. I have tried to find it the whole day with no luck.
Also see the the screenshot.
adtamez said:
Hellos guys,
I am trying to find the stock recovery for T-mobile US 6.10.531.10 (NOT 6.10.531.9) . Does anybody has it or point me on the right direction? I want to update my phone through OTA so I can get lollipop however I cannot find the stock recovery.
I am S-On all stock except for the recovery, I had TWRP so I can make backups. Now I want to install back the stock recovery so i can upgrade but I don't seem to find it anywhere. I managed to find the RUU but the recovery image is not inside the "rom.zip" on my Temp folder when I run it. These are the only files that it shows:
android-info.txt
dzdata_16g.hdr
dzdata_32g.hdr
dzdata_64g.hdr
tp_HMX852XD.img
boot_signed.img
dzdata_16.img
dzdata_32.img
dzdata_64.img
Am I missing something? Please help. I have tried to find it the whole day with no luck.
Also see the the screenshot.
Click to expand...
Click to collapse
just run the Lollipop RUU, same as the OTA but its the full thing rather than an OTA: http://www.htc.com/us/support/htc-one-t-mobile/news/ follow the manual update instructions, download is at the bottom.
edit: it will wipe your phone, so backup anything you want to keep first.
Seanie280672 said:
just run the Lollipop RUU, same as the OTA but its the full thing rather than an OTA: http://www.htc.com/us/support/htc-one-t-mobile/news/ follow the manual update instructions, download is at the bottom.
edit: it will wipe your phone, so backup anything you want to keep first.
Click to expand...
Click to collapse
Seanie, thank you for your reply. I need the stock recovery because precisely I was trying to avoid wiping my phone. I am just a very small step away to be able to update without wiping, I just can't find this stock recovery. Why is it that the recovery.img it is not inside the rom.zip RUU? Am I missing something?
Currently I flashed the stock recovery 6.10.5310.9 and i tried to install the OTA but when it gets to the recovery it looks like it starts installing moving the green line a little bit but soon after I get a red triangle and stops, which I am assuming it is because i do not have the proper recovery.
Any help so i do not need to wipe will be greatly appreciate it.
Thanks!
adtamez said:
Seanie, thank you for your reply. I need the stock recovery because precisely I was trying to avoid wiping my phone. I am just a very small step away to be able to update without wiping, I just can't find this stock recovery. Why is it that the recovery.img it is not inside the rom.zip RUU? Am I missing something?
Currently I flashed the stock recovery 6.10.5310.9 and i tried to install the OTA but when it gets to the recovery it looks like it starts installing moving the green line a little bit but soon after I get a red triangle and stops, which I am assuming it is because i do not have the proper recovery.
Any help so i do not need to wipe will be greatly appreciate it.
Thanks!
Click to expand...
Click to collapse
ok, you cant take it out of the RUU.zip as its an encrypted RUU, so take it out of the OTA.
download the OTA as normal, but select install later, then plug your phone into the computer and copy the OTA.zip to your computer from your phone, its in the internal storage, downloads folder, its just a zip file, so once its on your computer, open it with WinRAR or whatever you use to open zip files and in there you will see firmware.zip, open that too and take out recovery.img, flash it like any other recovery, then reboot and try and update again.
If the OTA then fails again, it will be down to modified system files or root, you will have no choice but to backup and use the full RUU.
Seanie280672 said:
ok, you cant take it out of the RUU.zip as its an encrypted RUU, so take it out of the OTA.
download the OTA as normal, but select install later, then plug your phone into the computer and copy the OTA.zip to your computer from your phone, its in the internal storage, downloads folder, its just a zip file, so once its on your computer, open it with WinRAR or whatever you use to open zip files and in there you will see firmware.zip, open that too and take out recovery.img, flash it like any other recovery, then reboot and try and update again.
Click to expand...
Click to collapse
oh I see. Thank you very much...quick question though: I am currently on version 6.10.513.10 the OTA is to upgrade to version 7.18.513.2, if i extract the recovery from this OTA i will be flashing the 7.18. recovery, isn't? Don't I need the recovery from 6.10 in order to be able to upgrade? If so, this is why i was looking also for the 6.10.513.10 OTA but I cannot find it.
Thank you again!
adtamez said:
oh I see. Thank you very much...quick question though: I am currently on version 6.10.513.10 the OTA is to upgrade to version 7.18.513.2, if i extract the recovery from this OTA i will be flashing the 7.18. recovery, isn't? Don't I need the recovery from 6.10 in order to be able to upgrade? If so, this is why i was looking also for the 6.10.513.10 OTA but I cannot find it.
Thank you again!
Click to expand...
Click to collapse
the OTA will check to see if you have 6.10.513.10 or 7.18.513.2 recovery, cant be anything earlier than those 2, current or previous, recovery update by the OTA will just be skipped.
Seanie280672 said:
the OTA will check to see if you have 6.10.513.10 or 7.18.513.2 recovery, cant be anything earlier than those 2, current or previous, recovery update by the OTA will just be skipped.
Click to expand...
Click to collapse
I see! Great news! Good to know. So the OTA can be install with a newer stock recovery (matching the OTA I presume).
I am currently at work without my cell phone but I will try this, as soon as I get back home and post the results.
One last thing, to flash the stock recovery is as simple as "fastboot flash recovery recovery.img" (or whatever the recovery file .img name is), correct?
I do not need to lock the bootloader in order to upgrade using the OTA as long as everything else is still stock. ...I do have root though, but I also read that this shouldn't be a problem either, correct?
Thank you sooo much!
adtamez said:
I see! Great news! Good to know. So the OTA can be install with a newer stock recovery (matching the OTA I presume).
I am currently at work without my cell phone but I will try this, as soon as I get back home and post the results.
One last thing, to flash the stock recovery is as simple as "fastboot flash recovery recovery.img" (or whatever the recovery file .img name is), correct?
I do not need to lock the bootloader in order to upgrade using the OTA as long as everything else is still stock. ...I do have root though, but I also read that this shouldn't be a problem either, correct?
Thank you sooo much!
Click to expand...
Click to collapse
No need to lock the bootloader for an ota, root might be a problem as it modifies system files, just give it a go, and yes, the flash of the recovery is the same as any other recovery file.
Seanie280672 said:
No need to lock the bootloader for an ota, root might be a problem as it modifies system files, just give it a go, and yes, the flash of the recovery is the same as any other recovery file.
Click to expand...
Click to collapse
Got it. I'll try and post results. Thank you very much.
adtamez said:
Got it. I'll try and post results. Thank you very much.
Click to expand...
Click to collapse
Seanie, all went as expected! It worked. I was able to extract the recovery.img file from the firmware.zip inside the 7.18 OTA zip file that was downloaded to the internal storage. Then proceed to flash it as any other recovery with fastboot. Afer that, the OTA update installed with o problem. Having root did not mattered. I did have to root it again though.
Thank you so much for your support!!! :good:
Worked for me as well, thank you.
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this
Wow and so it begins, great work thanks!
Thanks
Sent from my Pixel using XDA-Developers mobile app
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.
zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root
UPDATE 11-9-18: I have updated the FlashAll with the October edition of version 27.1.3. Yes, they updated the ROM but kept the same version number lol.
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from https://mirrors.lolinet.com (thank you!), unzipped it, used root junky's script to convert it (thank you!) and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Downloads
1. Updated October Flashall https://drive.google.com/open?id=1PczvmaVv19c91iOGhpNmhmfKyvDkz-ob (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall into a folder called "TMO Moto z2 force 27.1.3 flashall" Open a command prompt in the folder it created. Connect your phone to your computer via ADB.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit. This does not wipe user data.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above (if you use recovery).
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
Not Rooted and want to wipe everything?
Run flashall_erase.bat. It will boot into fastboot mode, update the partitions, and wipe everything.
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.
texasaggie1 said:
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from @xiyl (thank you!), unzipped it and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south.
Downloads
1. Flashall https://drive.google.com/open?id=1HK2zssCGlPTD5m2A_SAD-RjrQDfmZMTR (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall. It will create a folder called "NASH_TMO_27.1.3" Open a command prompt in the folder it created.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance,
Click to expand...
Click to collapse
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
kendallgreen said:
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
Click to expand...
Click to collapse
Sorry! It was late and I linked to the wrong thing. ? Try it now please.
texasaggie1 said:
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from @xiyl (thank you!), unzipped it and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Downloads
1. Flashall https://drive.google.com/file/d/1JKu5S7xvy8xvyCodLEt7olr8czP_8FUm/view?usp=drivesdk (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall. It will create a folder called "NASH_TMO_27.1.3" Open a command prompt in the folder it created.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.
Click to expand...
Click to collapse
I downloaded and unzipped the new NASH_TMO_27.1..3. I added the AdbWinApi.dll and AdbWinUsbApi.dll and got the flashall_then_recovery.bat to run. I didn't install the TWRP installer or Magisk but rebooted to recovery and then system. After several restarts due to unlocked bootloader warning, it came back to build number OCXS27.1.2 kernel [email protected]#1 Fri Apr 20 09:21:27 CDT 2018. Android security level May 1, 2018. Android version 8.0.0 However, all of my apps were retained except Messaging .
kendallgreen said:
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
Click to expand...
Click to collapse
kendallgreen said:
I downloaded and unzipped the new NASH_TMO_27.1..3. I added the AdbWinApi.dll and AdbWinUsbApi.dll and got the flashall_then_recovery.bat to run. I didn't install the TWRP installer or Magisk but rebooted to recovery and then system. After several restarts due to unlocked bootloader warning, it came back to build number OCXS27.1.2 kernel [email protected]#1 Fri Apr 20 09:21:27 CDT 2018. Android security level May 1, 2018. Android version 8.0.0 However, all of my apps were retained except Messaging .
Click to expand...
Click to collapse
So try it again but this time just do the regular flashall.bat. it should work this time.
It sounds like you are installing this to slot a but your phone is running in slot b. If doing it this way doesn't fix it just look on here for the command to switch your phone from one slot to another.
success. I tried the flashall.bat and got the system updated to 27.1.3. I noticed that when I fastboot --set-active=_a, I had 27.1.2 and with --set-active=_b, I had to restart the phone because it was stuck at the unlocked bootloader warning. thanks.
kendallgreen said:
success. I tried the flashall.bat and got the system updated to 27.1.3. I noticed that when I fastboot --set-active=_a, I had 27.1.2 and with --set-active=_b, I had to restart the phone because it was stuck at the unlocked bootloader warning. thanks.
Click to expand...
Click to collapse
awesome! The whole a/b partition thing can be quite annoying
great job man glad someone did this i was about to try thanks
worked great but i reflashed remove encryption oreo also i didnt know if it was a necessary was being safe you made it easy no fastboot lol great work
My Fellow Texan.....
THANK YOU.
My phone has been in a weird limbo for months. I was on AOSIP ROM but it wasn't rooted, I couldn't use any moto mods and I couldn't install anything because TWRP wasn't installed and it wouldn't let me install it, either. I now have TWRP, but it's showing no baseband. So I'm gonna attempt to fix that but I'm already in a better place than I was. Thanks again, brother.
if you need baseband its easy to fix i had the same issues i was testing kernel its eas fix if you need i can help fix ive bricked and tried everything works easy check last post put on this https://forum.xda-developers.com/z2-force/development/pantheon-kernel-alpha-t3805977
My Tmo box is rooted, presently running the original 27.1 release.. I've been getting the OTA update notifications for 27.1.2.
Do we know if I can skip 27.1.2 and jump straight to the 27.1.3 release? I'd love to be able to do this flash-all and put the update notifications to bed for a while.
dismembered3po said:
My Tmo box is rooted, presently running the original 27.1 release.. I've been getting the OTA update notifications for 27.1.2.
Do we know if I can skip 27.1.2 and jump straight to the 27.1.3 release? I'd love to be able to do this flash-all and put the update notifications to bed for a while.
Click to expand...
Click to collapse
It should be fine to skip revisions.
StonedYoda said:
My Fellow Texan.....
THANK YOU.
My phone has been in a weird limbo for months. I was on AOSIP ROM but it wasn't rooted, I couldn't use any moto mods and I couldn't install anything because TWRP wasn't installed and it wouldn't let me install it, either. I now have TWRP, but it's showing no baseband. So I'm gonna attempt to fix that but I'm already in a better place than I was. Thanks again, brother.
Click to expand...
Click to collapse
If you are on tmobile, flashing the firmware flashall from the aosip thread to get baseband back.
mookiexl said:
If you are on tmobile, flashing the firmware flashall from the aosip thread to get baseband back.
Click to expand...
Click to collapse
If that doesn't work let me know. It should though. You may have to re-root after his suggestion
I'd been avoiding updates because I just didn't want to deal with rooting again and restoring data, etc. This was great!
(bootloader) slot: not found this is what I get with every fastboot command.
I was having the same issue... I was on 27.1.2 and kept getting notified to update, but it kept failing. I'm rooting with Magisk (16.0 initially but then up to 17.1) and it wouldn't update. Thanks to this thread, I ran the flashall_then_recovery.bat and it worked a treat!!! Thank you TexasAggie!
TWRP Installer link is down
The link to the TWRP installer is timing out when loading and comes up with an error message. Is it possible to install the 27.3 update using adb and then flash magisk in the temp twrp? Thanks for your work bro!
UPDATE:
I tried and now I'm stuck in bootloop. I can still get to twrp using adb and did a wipe but it's still stuck in loop land. Do I need to be rebooting in TWRP from slot A or B? This is my first phone that has dual partitions and I am a bit confused by it. Any suggestions? THANK YOU!!
UPDATE:
Tried your flashall update a second time and it worked with no bootloop issue, was able to flash magisk and obtain root again too.
climbhigh77 said:
The link to the TWRP installer is timing out when loading and comes up with an error message. Is it possible to install the 27.3 update using adb and then flash magisk in the temp twrp? Thanks for your work bro!
UPDATE:
I tried and now I'm stuck in bootloop. I can still get to twrp using adb and did a wipe but it's still stuck in loop land. Do I need to be rebooting in TWRP from slot A or B? This is my first phone that has dual partitions and I am a bit confused by it. Any suggestions? THANK YOU!!
UPDATE:
Tried your flashall update a second time and it worked with no bootloop issue, was able to flash magisk and obtain root again too.
Click to expand...
Click to collapse
Glad to hear that!
So i already install pixel experience recovery on my phone, no error or anything but i cant seem to access it. when i tried to go into recovery mode, instead accesing pixel experience recovery it just go into miui recovery.
is the installation failed? or im doing something wrong?
Inhuman11 said:
So i already install pixel experience recovery on my phone, no error or anything but i cant seem to access it. when i tried to go into recovery mode, instead accesing pixel experience recovery it just go into miui recovery.
is the installation failed? or im doing something wrong?
Click to expand...
Click to collapse
PE recovery? Do you mean, an image?, if this is the case, you should need to proceed the same way as if TWRP is.
SubwayChamp said:
PE recovery? Do you mean, an image?, if this is the case, you should need to proceed the same way as if TWRP is.
Click to expand...
Click to collapse
and how to do it? install guide in their website didnt include anything after image instalation
I have the same problem. You should probably post this in the PE thread.
Inhuman11 said:
and how to do it? install guide in their website didnt include anything after image instalation
Click to expand...
Click to collapse
Not sure if you are referring only to the recovery image (I didn't usually saw it available to download it though), or to the ROM, to be flashed through it.
If you say for the PE recovery image, you have to boot to it, using fastboot, and then from PE recovery, flash it onto the ramdisk and reboot again to recovery to be sure you get it.
SubwayChamp said:
Not sure if you are referring only to the recovery image (I didn't usually saw it available to download it though), or to the ROM, to be flashed through it.
If you say for the PE recovery image, you have to boot to it, using fastboot, and then from PE recovery, flash it onto the ramdisk and reboot again to recovery to be sure you get it.
Click to expand...
Click to collapse
Here is the link to img file and the rom. https://download.pixelexperience.org/spes
And already tried it using fastboot, still going to miui recovery.
Is it because i install it on boot_a instead to boot_b ?
Inhuman11 said:
Here is the link to img file and the rom. https://download.pixelexperience.org/spes
And already tried it using fastboot, still going to miui recovery.
Is it because i install it on boot_a instead to boot_b ?
Click to expand...
Click to collapse
Firstly, you can't install it using fastboot, you should need, to boot to it, only.
And from the PE recovery screen, you should need to flash it on the ramdisk, not sure if this option is available, as it has limited options, in this case, if not, you'd need to boot (and probably flash) TWRP, and from there, flash the PE recovery image onto the ramdisk.
And for the next, an image you need to flash using fastboot (not available for recovery) you don´t need to target to any slot, unless you have a good reason, because the flashing process is done in the active slot.
I still have the same problem.
Any solution?
I have this same issue, I at least think. Here's where I'm at.
I downloaded the build and the recovery image for Pixel Experience, specified for my device. I got as far as to use "fastboot flash boot PixelExperience.img" onto the device.
The phone is now unable to reboot, and the OS stops responding whenever I do anything with it. I can't reboot to recovery, or reboot at all. I'm not sure if I'm supposed to wait, and for how long?
I followed the directions on the Pixel Experience website found here:
- https://wiki.pixelexperience.org/devices/fog/install/