Related
I have adb and fastboot installed, and using rumrunner, I am trying to s-off/root my HTC One M7. Is anyone else having issues with it getting stuck on the first pouring <1>... message? Mine has been sitting here for about an hour with no change. I made sure to go in an disable 'verify apps by adb' in the phone's settings, and started again, and yet it still gets stuck on this first pour.
Any ideas?
MReprogle said:
I have adb and fastboot installed, and using rumrunner, I am trying to s-off/root my HTC One M7. Is anyone else having issues with it getting stuck on the first pouring <1>... message? Mine has been sitting here for about an hour with no change. I made sure to go in an disable 'verify apps by adb' in the phone's settings, and started again, and yet it still gets stuck on this first pour.
Any ideas?
Click to expand...
Click to collapse
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Okay so my first question: Is it a VERIZON One?
Second question: Did you properly install the drivers for fastboot on the phone?
1st suggestion: Add an exception in your firewall for soju.exe
2nd suggestion: open a command window in your platform tools folder of your adb installation and type adb devices to see if it comes up
Sent from my One using XDA Premium 4 mobile app
cstrife999 said:
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Click to expand...
Click to collapse
Ok maybe I missed that, where is verifying apps off?
Never mind, found it under developer options.
sanjeeva7 said:
Ok maybe I missed that, where is verifying apps off?
Never mind, found it under developer options.
Click to expand...
Click to collapse
Under security. It's a 4.2 and up thing to prevent malware from being installed on the phone.
Ok still not working.
I am on VZW with stock. Zero mods made to the phone. I just got it a few days ago. I am on the .10 version.
adb works:
C:\miniadb_m7>adb reboot bootloader
C:\miniadb_m7>fastboot devices
FA37K------- fastboot
C:\miniadb_m7>fastboot reboot
rebooting...
finished. total time: 0.044s
C:\miniadb_m7>adb devices
List of devices attached
FA37K------- device
C:\miniadb_m7>
Loaded the HTC only drivers for Windows 7. Run as admin directly from the program, and in DOS which was run as admin. At first I was getting the "WTF" error. I have disabled my antivirus and added the "soju.exe" to allow in my firewall settings. So then I rebooted. I am using the OEM cable and usb 2.0 port.
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (34/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (36/120)
Waiting for device
Waiting for device
pouring (1)...........
.................................
Waiting for device
pouring (2)...........
.................................
Waiting for device
pouring (3)...........
.................................
Waiting for device
pouring (4)...........
................................
Waiting for device
pouring (5)...........
................................
Waiting for device
pouring (6)...........
................................
Waiting for device
pouring (7)...........
................................
Waiting for device
pouring (8)...........
.................................
Waiting for device
pouring (9)...........
.................................
Waiting for device
pouring (10).....
...
If you're getting the pouring (10) error, run the .08 software. that fixed it for me.
What worked for me was to right click soju.exe and run as administrator. After that it worked like a charm.
Sent from my HTC6500LVW using Tapatalk 4
Wow, 10 pours? With all these random numbers of pours I'm reading (mine was 3), I'm thinking this exploit keeps trying until it works and I imagine theres a bit of timing or trial and error involved?
skiman10 said:
What worked for me was to right click soju.exe and run as administrator. After that it worked like a charm.
Sent from my HTC6500LVW using Tapatalk 4
Click to expand...
Click to collapse
Make sure debugging is check marked every time the phone reboots during the process.
I had to manually mark it the first few times.
Sent from my HTC6500LVW using Tapatalk 2
My suggestion is to use Linux to do the process , I did it first attempt . Just make sure you sudo get adb and fastboot and you are good to go . If you don't have linux I suggest dual booting it will get the job done .
Sent from my HTC6500LVW using Tapatalk now Free
kookahdoo said:
Make sure debugging is check marked every time the phone reboots during the process.
I had to manually mark it the first few times.
Sent from my HTC6500LVW using Tapatalk 2
Click to expand...
Click to collapse
It seems when you turn that fast boot option OFF it kept USB debugging on. At least it did for me.
I'm not sure why it would make any difference, but I wiped adb and fastboot from Windows, then reinstalled both of them. After that, everything went perfectly fine, and now I just have to figure out what ROM to put on this thing.
Any suggestions for the Verizon version?
USB ports
I was having the exact same problem, dumping out to a WTF error on Pouring 1. I tried everything on the planet, but what eventually fixed it for me was switching USB ports.
Ironically, it was a USB 3.0 port that worked for me. But my tower has, easily 10 USB ports on the backside. Try different ports. That's the only change I made, and it went from that exact failure to a first try success.
MReprogle said:
I'm not sure why it would make any difference, but I wiped adb and fastboot from Windows, then reinstalled both of them. After that, everything went perfectly fine, and now I just have to figure out what ROM to put on this thing.
Any suggestions for the Verizon version?
Click to expand...
Click to collapse
I am running VANIR and liking it so far. I'm sure I'll try them all eventually. Never had much luck with PAC on any of my previous devices and Liquid was always good but lacked some features I wanted. CM is always another option as well. Whatever you pick now, you will probably change as now that we have a simple S-Off my guess is we will have a LOT more choices soon. What I'd really love to see is a Team Sourcery ROM but doubt it will happen.
I really like Blinkfeed, so I went with BoneStock.
cstrife999 said:
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Click to expand...
Click to collapse
Where did you get the stock recovery to flash?
Verizon HTC One software version & rumrunner
Prior to implementing any Rumrunner S-OFF mod, I notice that Verizon pushed a "minor" OTA upgrade last week. It might have been .8 prior to the OTA and is now showing a long string for the ID; both revs are being shown.
When I query my software on the phone now, I see: "...1.10.605.10-1.10.605.8_R2". I'm not sure what it showed prior to receiving the OTA push...
Question, which version of the software should be downloaded, at least initially? The .10 or the .8? I assume the .8_R2 implies the tweak to .8 and the .10 means the push is applied... Any recommendations?
Thanks, bj
clivusmul said:
Prior to implementing any Rumrunner S-OFF mod, I notice that Verizon pushed a "minor" OTA upgrade last week. It might have been .8 prior to the OTA and is now showing a long string for the ID; both revs are being shown.
When I query my software on the phone now, I see: "...1.10.605.10-1.10.605.8_R2". I'm not sure what it showed prior to receiving the OTA push...
Question, which version of the software should be downloaded, at least initially? The .10 or the .8? I assume the .8_R2 implies the tweak to .8 and the .10 means the push is applied... Any recommendations?
Thanks, bj
Click to expand...
Click to collapse
if i were you, i'd try .8
Aggies1288 said:
Where did you get the stock recovery to flash?
Click to expand...
Click to collapse
I provided a .zip somewhere
let me find it
http://d-h.st/sdg
use fastboot.
Hi I'm trying to sideload the 5.0 lollipop update to my 2013 N7 using adb. I've downloaded the correct file. I have the correct drivers installed, and adb recognizes my N7 just fine. I am able to use the commands to get into the recovery. When I type in "adb sideload <filename.zip>" I keep getting the following message "the syntax of the command is incorrect" Any help would be great. My N7 is unrooted, stock recovery.
Thanks.
evltwn72 said:
Hi I'm trying to sideload the 5.0 lollipop update to my 2013 N7 using adb. I've downloaded the correct file. I have the correct drivers installed, and adb recognizes my N7 just fine. I am able to use the commands to get into the recovery. When I type in "adb sideload <filename.zip>" I keep getting the following message "the syntax of the command is incorrect" Any help would be great. My N7 is unrooted, stock recovery.
Thanks.
Click to expand...
Click to collapse
I didn't get that particular error last night when I tried, but I wa going from 5.0 to 5.0.1 and the sideload first told me the ADB version was too old (I was on 1.0.31 and needed 1.0.32 or something), then it told me that the file check failed (rooted, and non-stock recovery will do that).
I ended up using the factory image instead, which worked great.
Download the factory image, unzip it in your ADB folder and edit the flash-all.bat file. Remove the -w flag near the end of the file. This flag tells the script to wipe your user data, so removing it keeps your data. I did this for both 5.0 and 5.0.1 and all my data/apps/etc were fine.
Once you edit it, save it and double click it with the phone in the bootloader. Took about 2 minutes to flash mine, then about 10-15 minutes to optimize apps. I then ran Chainfire Auto Root and I was back in business. Whole process took about 20 minutes (optimizing apps being nearly all of that).
fury683 said:
I didn't get that particular error last night when I tried, but I wa going from 5.0 to 5.0.1 and the sideload first told me the ADB version was too old (I was on 1.0.31 and needed 1.0.32 or something), then it told me that the file check failed (rooted, and non-stock recovery will do that).
I ended up using the factory image instead, which worked great.
Download the factory image, unzip it in your ADB folder and edit the flash-all.bat file. Remove the -w flag near the end of the file. This flag tells the script to wipe your user data, so removing it keeps your data. I did this for both 5.0 and 5.0.1 and all my data/apps/etc were fine.
Once you edit it, save it and double click it with the phone in the bootloader. Took about 2 minutes to flash mine, then about 10-15 minutes to optimize apps. I then ran Chainfire Auto Root and I was back in business. Whole process took about 20 minutes (optimizing apps being nearly all of that).
Click to expand...
Click to collapse
Well I'm still having no luck. I already had the factory image, I tried what you recommended, and still no luck. Thanks for your help. :highfive: I guess I'll wait until Google decides to push it out. I did call them prior to my 1st post on here, and of course, they were not much help.
evltwn72 said:
Well I'm still having no luck. I already had the factory image, I tried what you recommended, and still no luck. Thanks for your help. :highfive: I guess I'll wait until Google decides to push it out. I did call them prior to my 1st post on here, and of course, they were not much help.
Click to expand...
Click to collapse
I followed this guide which worked great : http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
If you still get the error, maybe deinstall adb, drivers etc and try again
Sent from my Nexus 5 using XDA Free mobile app
chrismast said:
I followed this guide which worked great : http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
If you still get the error, maybe deinstall adb, drivers etc and try again
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That was my next suggestion. If sideload and factory images aren't working, seems like it's a PC issue. Worth a shot.
My drivers are working just fine. I made sure they were update. I'm just gonna wait until I get the OTA update. Thanks for your help guys.
Sent from my HTC One M8 using XDA app
Well Google just pushed 5.0.1 to my N7. Happy days.
Sent from my Nexus 7 using XDA app
hello
i have rooted the device using the "1 CLICK ROOT TOOL" and now i have the dead android bot with error when i enter recovery.
i have tried the "fastboot erase cache" command at fastboot mode but it did not help
is their a way to fix it?
Try pressing Volume + key and Power. Don't hold just press. It might take a few goes to get it right. I had the same problem. That means that the update you have downloaded (saved on your system) fails to install.
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
koby058 said:
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
Click to expand...
Click to collapse
Awh sorry, I thought you can't get into recovery.
Try sideloading the stock Firmware. Go to official ASUS website and download it from there. It's about 1 GB. On this website you can find instructions on how to do it. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 Section 3.2)
After that you can download OTA updates and install them using method described here http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835, "Steps to Apply OTA manually".
OTA can be downloaded from there (look at the later posts for newer OTA) http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
I had a very similar problem few days ago. That solved it. Had a similar problem a few days ago coz I messed up my build.prop
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
koby058 said:
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
Click to expand...
Click to collapse
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
rlaw said:
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
Click to expand...
Click to collapse
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
NiKiToS-04 said:
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
Click to expand...
Click to collapse
No worries, I've made the same mistake before. We've all been there, still learning new things about this phone after months of using it!
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
koby058 said:
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
Click to expand...
Click to collapse
The 2.20.40.58 OTA was bugged and pulled from release. Just flash the full stock 2.20.40.59 firmware available from ASUS site and stop modifying your phone if you want to remain trouble-free with OTA updates. Or if you choose to continue to root and tinker with your phone accept that some things might get broken.
I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.
johncro13 said:
I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.
Click to expand...
Click to collapse
I'm not certain why that happens, But I have a guess.
On each update that I have looked at, the recovery gets and update too. So different signatures and such.
Maybe the "stock" recovery you have re-flashed, is not correct version for your installed and update rom.
I cannot confirm this as I am missing the update app.
If you could help me with my missing files , I could help you with your update problem.
You could help me by pulling a list of packages installed so I can see what apps I have missing, and hopefully get them back (stock only, preferably done after a fresh factory reset.)
Directions for this on this thread.
See attached.
johncro13 said:
See attached.
Click to expand...
Click to collapse
thank you that helps.
I see I am missing an entire folder.
/data/hw_init
Could you see if it is accessible .
Code:
mkdir %userprofile%\Desktop\hw_init
adb pull /data/hw_init %userprofile%\Desktop\hw_init
I think it is not permitted though.
Uploaded. See referenced thread. I hope it helps!
johncro13 said:
Uploaded. See referenced thread. I hope it helps!
Click to expand...
Click to collapse
I will see what I can do with that. And hopefully can get past any file verification. And if I figure that out it should help you too.
Or , with my luck, the moment I figure it out , the stock firmware will come out.
I pushed the hw_init folder to /data while in twrp, then put stock recovery back(the version I expect should be correct) and I got same update failed error, as the OP.
That tells me maybe is probably some other reason , besides the version of stock recovery is causing this trouble.
Not sure if there is confirmation of successful update while bootloader is unlocked or not. Too late for me to try tonight, but next I will re-lock bootloader and try again.
My last (really current) phone needed to be re-locked in order to take updates.
**UPDATE**
re-locking bootloader did not help any at all. I still have error failed to check file, please download again.
On the manual update to oreo thread, they are using a "stock-ish" recovery named "no-check"
I am thinking I might flash that recovery to try and force this update to install.
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
tried it earlier today. Same error. will not finish update
johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
I have ordered a second 7x. I plan to pull the hw_init folder , and the remainder of /data that might be missing from this device , because of a result of formating it in twrp. I plan to restore that as an image, in hopes of getting updater to complete properly. And if that works, you will be able to use my backup and update your phone too.
If not , well , doesn't hurt to try.
I'm comparing the images pulled from my device and the images available for the Indian "return to stock thread. And I see the problem with the USA L24 version.
The cust.img for usa has no app folder.
It did not make sense to me before why there was apps only installed in /data. Because /data should be able to be fully wiped and your system will recreate the file structure. But The apps should have been on one of the images.
My second phone arrived today. I pulled the hw_init folder from it.
did a diff comparison on the updater app from the new phone and and the one that I had to apply patches to , to bring it up from b101 to b140. The result was 100% same.
and three more apps where in the hw_init folder as well. (bloat apps really)
now the bad news.
My original phone (the one that I had formatted /data on). Now has the same /data/hw_init folder as the brand new device. But always shows no update available.--It showed update once, the first time checked, install failed , now shows nothing available.
And the new phone does show an update available (B150) , but fails to install. Then after the failed install, now it shows no update available.
That's insane.
So... in summary, neither will update? Neither the original nor the unaltered brand-new device?
If anyone else has had this issue but has since resolved it, would you mind letting us know how? @mrmazak is working on it and I've also been told by the FUT team that I should expect some kind of communication from "Oscar Felix."
(If you've searched the forums for other Honor or Huawei devices, you probably already know that there is some speculation about whether or not Oscar Felix is a real person.)
I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root
Sonny1732 said:
I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root
Click to expand...
Click to collapse
Did you get the Oreo update today?
No I didn't, did you find out what can we do about this?
Is it a way I can update my phone manually
I'm watching this thread , myself. That might be the key.
Hopefully something comes up soon or is there a rom I can get if I reroot my phone?
First things first. I surrender. I'm a noob with android. I had windows phone previously and only now came to android.
Here's the scenario:
1. My z2 force was properly rooted with magisk and twrp. I followed the guide in xda only.
2. My device was brought from India so carriers like sprint, t-mobile are not applicable I think.
What I Did:
0. Wanted to unroot my device. So, I decided to first uninstall the modules in magisk that I had installed.
1. Tried to uninstall magisk modules and rebooted from the magisk application.
2. Got into Boot loop, so went to recovery mod and wiped everything. Hard reset was done.
3. Installed magisk app again and clicked uninstall to remove root. I wanted to install the latest security update. Update kept failing so I decided to unroot. I choose uninstall completely option.
4. Rebooted the phone manually after clicking uninstall in magisk manager. Using the 'root checker' app I checked if unrooting was successful but it said, 'root was not properly installed' or something like that. So, I installed magisk manager again and again uninstalled root completely.
5. Still same issue. Root checker said the same thing again. So, installed magisk manager again and this time I wanted to remove root using ES file manager as I saw in an online guide. But I couldn't give it root permission because it was not properly installed as said by root checker. So, I decided to root my phone properly but stupid me, clicked 'install' in magisk manager and chose the recommended option (don't remember exactly what it was). It downloaded magisk zip and did some changes and asked to reboot. After rebooting, my phone went straight to the black screen with an android icon and 'no command' written below it. It kept going there again and again.
6. I assume that is the recovery mode. I press volume up and power button and choose the wipe everything again(Like I did before) to hard reset phone. Wiping was successful but it still kept booting to that black screen.
Additional Info:
1. Phone wasn't carrier version. It was bought in India. It is running Oreo 8.0.
2. In bootloader menu : (Not stating all)
BL: MBM-3.0-nash_retail-641a15b-180306
Product/Variant: nask xt1789-06 64GB PVT
Console[NULL] :null
Tools Mode Config: DISABLED
Power OK
flashing_unlocked
Software Status : Modified
Transfer Mode : USB Connected.
3. Yes, Bootloader menu is accessible.
4. Choosing recovery mode in bootloader menu reboots phone and takes me to that blank screen I mentioned before.
5. Connecting to USB to my PC when in bootloader menu, it connects as 'Fastboot nash S'. ADB terminal says no devices found.
What I want:
1. Boot into OS.
2. Remove root completely so I can install system update.
Please help or offer suggestions as I do not have a secondary device with me. If I have to absolutely go to a service center, I will.
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Code:
fastboot devices
and you should see your serial# like you do in adb.
That should put you back to stock and good to go.
41rw4lk said:
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Code:
fastboot devices
and you should see your serial# like you do in adb.
That should put you back to stock and good to go.
Click to expand...
Click to collapse
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Sparkzz27 said:
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Click to expand...
Click to collapse
Did you look to see if the May Security Update has been released for your specific device? When you downloaded the stock firmware did you look to see what month security patch it contained? Have you tried to perform a system update to see if you can OTA to the latest security patch?
Now, if you completely flashed back to stock then root is removed. Root checker says that because root access is not installed at all. Flashing back to stock removes any trace of root, IIRC.
Sent from my Moto Z2 Force using XDA Labs
Don't forget, if you followed the flashing instructions from the other post they were omitting the gpt.bin and bootloader. So if you didn't flash those then that's why you're probably not seeing any updates, you need to be on full stock all matched up. Just reflash the firmware you downloaded in its entirety. @fast69mopar is right, once you flash a new boot.img root is gone, and since you flashed back to stock it's definitely gone.
Sparkzz27 said:
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Click to expand...
Click to collapse
If you flash with factory image you should be unroot completely and root checker will keep telling you "root not properly installed" if you are not rooted just ignore root checker if you not planning to be rooted.
Hi there I have a xt1789-06 I was not getting updates and flashed the first Oreo update from here https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/
My phone now does the updates and everything works fine.
However I did try to flash a custom ROM and root I made a mistake and ended up both a hard brick, because I was on Oreo I thought that flashing the Oreo blank flash would rectify the problem, but it was not working so I tried flashing the N blank flash and it worked.
I've come from using Samsung phones so I'm use to Odin and have not used fastboot commands. After reading many threads I know what I had done was not decrypting my device which ended up with a hard brick I will in the future flash a custom ROM now I know a little bit more.
Blank flash files are here
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/
Then once back to fastboot flash the flash all from the link at the top of my post.
41rw4lk said:
Don't forget, if you followed the flashing instructions from the other post they were omitting the gpt.bin and bootloader. So if you didn't flash those then that's why you're probably not seeing any updates, you need to be on full stock all matched up. Just reflash the firmware you downloaded in its entirety. @fast69mopar is right, once you flash a new boot.img root is gone, and since you flashed back to stock it's definitely gone.
Click to expand...
Click to collapse
Hi, sorry I was busy with work. I managed to use my phone that way. I didn't use the instructions in that post. Instead, I download flashallutilities (In how to return to stock post in xda for z2 force), then ran the batch file which did all the work. I noticed other problems too,
1. My Jio sim(4g LTE) does not show 'enhanced LTE mode' in options. Also when I call someone, it fails immediately saying 'call failed. try another method.' However, internet connection works from the sim. My other sim works fine for calls and data.
2. I'm seeing other keyboards in manage keyboards section. I don't recall seeing google pinyin input, zhuyin input, etc before. What's worse is my office's app shows option to switch to chinese version of the website for logging in. My language and time zone are set correctly though - English India and GMT +5:30.
3. The web browser I used before couldn't be found in the play store anymore. My launcher still shows the icon with a green arrow in left bottom of the icon to direct me to playstore to download it but playstore says item not found. The app name is simply 'browser'. I searched for it on desktop website too (without logging in), still couldn't find it. Guess it's a coincidence,
Also: Herehttps://www.getdroidtips.com/moto-z2-z2-play-z2-force-stock-rom/#Moto_Z2_Force_Android_80_Oreo_Firmware, the carrier global version says 'OCX' instead of 'OPX'. Any idead about that?
Sparkzz27 said:
Hi, sorry I was busy with work. I managed to use my phone that way. I didn't use the instructions in that post. Instead, I download flashallutilities (In how to return to stock post in xda for z2 force), then ran the batch file which did all the work. I noticed other problems too,
1. My Jio sim(4g LTE) does not show 'enhanced LTE mode' in options. Also when I call someone, it fails immediately saying 'call failed. try another method.' However, internet connection works from the sim. My other sim works fine for calls and data.
2. I'm seeing other keyboards in manage keyboards section. I don't recall seeing google pinyin input, zhuyin input, etc before. What's worse is my office's app shows option to switch to chinese version of the website for logging in. My language and time zone are set correctly though - English India and GMT +5:30.
3. The web browser I used before couldn't be found in the play store anymore. My launcher still shows the icon with a green arrow in left bottom of the icon to direct me to playstore to download it but playstore says item not found. The app name is simply 'browser'. I searched for it on desktop website too (without logging in), still couldn't find it. Guess it's a coincidence,
Also: Herehttps://www.getdroidtips.com/moto-z2-z2-play-z2-force-stock-rom/#Moto_Z2_Force_Android_80_Oreo_Firmware, the carrier global version says 'OCX' instead of 'OPX'. Any idead about that?
Click to expand...
Click to collapse
Your Z2 is a xt1789-06 correct? It's an international version, the flashall in the utilities zip from the return to stock thread is for US based phones, TMO and Sprint specifically. What was or wasn't flashed using that flashall I couldn't tell you, I don't have an international phone. That's why I linked to the post that deals with that version of the Z2 and has all the answers and links you need to sort your phone. Others in that thread might be better suited to help you along. This is the thread that deals with the xt1789-06.
As for calling and sim, might be related to how you flashed or simply an apn issue. You can go to network settings, mobile, access point names, and reset those to default. That should pull the apns from your sim so you'll have the correct apns.
As for keyboards and browsers, I don't know what is included in the international stock versions, but they are subject to change based on initial setup/default language and rom version. As for the OCX vs OPX, I'm not sure what the difference is. I know 'O' is for Oreo but for the rest I don't know. Maybe one is gsm one is cdma? I don't know. I do know that the thread I linked to will have more info and be able to help you better since it's for your version of the Z2. Sorry I can't help you more, but post any questions you have over there and they should be able to sort you out.