Related
I'm not sure if this is going to end up as a fix or a cautionary tale, but here goes.
Was looking to root my g4, so I successfully unlocked the bootloader & installed TWRP using this method: http://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
Things were going pretty good there, but when I tried to install the SU image through TWRP, the phone wouldn't boot.
Naturally, I didn't do a backup of the stock state of the phone (BECAUSE I'M AN IDIOT!) so I figured, what the hell, might as well install cyanogen mod, and see what that's all about. There's a cyanogenmod beta for the G4+. It went on smooth through the TWRP installer and was behaving ok, but wouldn't see the SIM. I check the IMEI number and the phone does not have a value set, just blank space.
I then tried to re flash stock firmware on the phone, thinking that might restore the IMEI.
It was a bear to get on there, but I was pretty proud of myself when it booted.
Trouble is: still no IMEI number. Also no wifi and it can't see the SIM card (probably because no IMEI number).
So, I figured I'd go back to the cyanogenmod, and see if I could somehow trick it into an IMEI number, BUT! re-loading the firmware re-locked the bootloader.
I went through the unlock process at motorola again, but this time she won't unlock. The console is throwing me
Code:
...
(bootloader) invalid boot state
OKAY [ 0.005s]
.
So, from here, I don't know where to go. Try re-flashing cyanogenmod on it manually I guess, but I don't know if that will work with the bootloader perpetually locked.
Can anyone help me sort this out?
Please?
How did u flash the stock ROM? Did u flash the right one for your device.
Sent from my Moto G⁴ Plus using Tapatalk
Silesh.Nair said:
How did u flash the stock ROM? Did u flash the right one for your device.
Sent from my Moto G⁴ Plus using Tapatalk
Click to expand...
Click to collapse
I flashed the stock rom on manually from the terminal using fastboot. Evidently: it isn't the right version. After careful inspection, it seems like I loaded the Indian / Asian version, whereas my device is the Canadian version.
Unfortunately, the Canadian stock firmware is still listed as a work in progress.
And the file names are confusing as hell. My device model is xt1643 but my stock ROM doesn't even mention 1643 in the file name. What's your model number?
Sent from my Moto G⁴ Plus using Tapatalk
Silesh.Nair said:
And the file names are confusing as hell. My device model is xt1643 but my stock ROM doesn't even mention 1643 in the file name. What's your model number?
Sent from my Moto G⁴ Plus using Tapatalk
Click to expand...
Click to collapse
it's model XT1641, bought in Canada.
Did you turn on unlock bootloader option in Dev settings ?
W0000000ooooooooooooooooooHooooooo00000000000000000000000000!!!:victory:
We're back in business, kids!
Found the stock rom for the Canadian Retail build (not locked to carrier) here: https://mirrors.lolinet.com/firmware/moto/athene/official/RETCA/
It took forever to download, but once it showed up, I flashed it on with fastboot, fired 'er up, and it's the same old stock G4 with working wifi, that can see the SIM & Connect to the network, complete with IMEI number AND - I believe - an unlocked bootloader.... at least I get the unlocked bootloader warning screen on boot.
Varun: I saw your message when I was getting set to flash the firmware on and got set to put my palm through my head. You're right: it could have been just the switch in developer options. But I checked and it was on.
Maybe the mods can add that firmware to the big firmware download links post.
Now, you'd think that having just brought this thing back from the dead I'd leave well enough alone and quit fiddling with this thing, but...
Maybe the owner of the newbie thread should add a post with "take a backup through twrp"
varun.katoch said:
Did you turn on unlock bootloader option in Dev settings ?
Click to expand...
Click to collapse
had the same issue. forgot to turn on usb debugging
Can anybody help?I am S Off. Unlocked. Rooted. I am currently on Nu Sense Rom. Need to get back to stock for warranty purposes. I try flashing the Verizon zip and get mismatch issues. 7 RU CID FAIL. Thanks for your help.
artpena2323 said:
Can anybody help?I am S Off. Unlocked. Rooted. I am currently on Nu Sense Rom. Need to get back to stock for warranty purposes. I try flashing the Verizon zip and get mismatch issues. 7 RU CID FAIL. Thanks for your help.
Click to expand...
Click to collapse
Did you make a backup of the stock system image before flashing a custom rom? I haven't tried going back to stock any other way, but I'm fairly certain that the only way to RUU back to stock is if you have a completely stock copy of your system image to restore in TWRP.
Out of curiosity, what issue are you having that require warranty service?
I'm also having trouble finding a guide to this; I've bricked phones in the past, or had issues with reverting to sell that ended up costing me 3 hours of troubleshooting.
Basically I've now found that Android Pay is something that I wish to use again; and with the N update for VZW coming out very soon I might as well go back to full stock with my bootloader locked again now that the main reason I went to s-off/unlocked was for N.
Anyone know where the guide is? If there isn't one, I will outline the steps that I think I need to take, but could use some help to make sure I don't jank it up.
1. Get the RUU from the stock ruu thread.
2. Flash said RUU
3. Factory Reset
4. ???
5. Profit?
As you can see, I'm missing the parts where I re-lock the bootloader, change the tamper flag, fix potential LTE problems (I've read that might be an issue), and whatever else might need to be done to full revert it to legit VZW.
If it matters; I have a (rooted) stock backup from 1.85.605.8 I can flash to make this easier, as I recall having to do that for prior HTC phones (I think).
Has anyone received Google Assistant on their phones yet? Just curious.
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
I'm surprised to hear some people still don't have GA natively. I'm a long time HTC user, but I just bought my 10 last Fri. it's pretty sweet. although, I must say, I still REALLY like my One M8.
SilverZero said:
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
Click to expand...
Click to collapse
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
SilverZero said:
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
Click to expand...
Click to collapse
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
"OK Google" Always on!!??
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
misfiremind said:
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
Click to expand...
Click to collapse
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
this is from my Bolt, so it may be different, but I can disable just fine...
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
misfiremind said:
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
Click to expand...
Click to collapse
Ill try that but I flashed N using the RUU and then clean installed OMJ's badboys rom so no app data would have been there during M to N
---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------
OMJ said:
this is from my Bolt, so it may be different, but I can disable just fine...
Click to expand...
Click to collapse
Thats strange, i dont have all those menu entries... could be cause I have work email on my phone via activesync which restricts certain security and lockscreen options.
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
Click to expand...
Click to collapse
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
SilverZero said:
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
Click to expand...
Click to collapse
yes, merely having the bootloader unlocked even w/ 100% stock ROM, safetynet will fail....the beauty of magisk is that it hides it
I think at this point I'd rather relock my bootloader and go back to using my Galaxy S4 while I try to sell my HTC 10 and then put that money towards a Pixel. Anybody wanna buy a phone? ?
It's here! I literally just this minute got Google Assistant!
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I think I am going to give this a shot. I am running your stock rooted with TWRP while S-on. Can I just install your Magisk Full Rom and go from there or is that too easy to believe? Thanks OMJ!
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
Is magisk a ROM or more of a mod? And what is magisk su? I'm going to try and get my phone rooted this weekend but I can't find a tutorial thread, it seems to be scattered everywhere. It seems like I fastboot TWRP, flash SuperSU, flash magisk then install magisk manager from Google Play?
misfiremind said:
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
Click to expand...
Click to collapse
im running viper due to lack of cm/aosp st the moment.. so i have magisk but i have no idea what it is or how to use it. very little instruction out there.
Has anyone been successful in editing their build.prop file to activate (or deactivate) Google Assistant? I actually want to deactivate Google Assistant but I can't seem save changes to my build.prop file.
I have root on stock ROM.
Set SE Linux to permissive.
Tried using Root Explorer and build.prop Editor. Both give me an error message stating it can't save the build.prop file.
Suggestions?
Ok so I am just going to say I am a idiot and need some help. Please don't hate on me. I am not good with phone technology, but I followed directions to root my phone with TWRP & Magisk 12.0 and everything is working ok for the most part. The problem is I need a specific app to work for my job, but it fails to start due to the failed Safety Net. I would probably be able to figure out how to unroot it & relock the bootloader, but in my haste to root my phone, I did not backup the stock ROM image 1st. If anyone can help me figure out the next step to go back to a factory phone, I would forever be indebted to you. My specific model is an XT-1681 dual sim which I believe is from Brazil. I am in the US and not sure if I can use a different stock rom because I have tried searching to no avail. Please help if you can.
Thanks for your time.
There's a flash file for magisk which allows it to pass safety net. I saw it in the Lineage thread a few days back, but I don't know the exact origin.
Secondly, you can't relock the bootloader anyways. I don't know for sure if that in itself would cause safety net issues.
Karlinski said:
There's a flash file for magisk which allows it to pass safety net. I saw it in the Lineage thread a few days back, but I don't know the exact origin.
Secondly, you can't relock the bootloader anyways. I don't know for sure if that in itself would cause safety net issues.
Click to expand...
Click to collapse
I appreciate the response, but I was able to finally locate the stock rom from a site linked on here & flashed and relocked the bootloader using ADB. Basically my phone is stock again & working like I need it to. I tried hiding the app in Magisk, but was unsuccessful. So I guess this post can be locked.
ronefx said:
I appreciate the response, but I was able to finally locate the stock rom from a site linked on here & flashed and relocked the bootloader using ADB. Basically my phone is stock again & working like I need it to. I tried hiding the app in Magisk, but was unsuccessful. So I guess this post can be locked.
Click to expand...
Click to collapse
Which phone version you have retin?
Sent from my Moto G (5) Plus using Tapatalk
I've decided that I'm not really ready for Oreo on this phone until Lineage 15.1 is final with all features ported. I'm going back to stock and I'm wondering - are there any side effects to doing so? I've heard that people have permanently lost VoLTE, had IMEI issues, etc. I'm very wary of trying anything that I'm not sure about... does anyone have information on this?
Many thanks.
Make sure you use latest software for your region, also whether retail version or not.
Other than that good luck
Ray
I flashed the stock ROM for my device and it's running just fine with no errors. I pass SafetyNet and my bootloader says I'm on the official firmware.
The IMEI issue seems to be related to stock fastboot.
So you can either skip flashing that or flash a TWRP flashable stock ROM.
bornlivedie said:
The IMEI issue seems to be related to stock fastboot.
So you can either skip flashing that or flash a TWRP flashable stock ROM.
Click to expand...
Click to collapse
By saying "skip flashing that" what do you mean?
Jrhotrod said:
By saying "skip flashing that" what do you mean?
Click to expand...
Click to collapse
Fastboot ROM, I think
If you fastboot flash stock rom and have Oreo 8.1 as your system now, don't do it!. You will lose voLTE and will most likely lose 4g (avoidable by skipping the two modem wipe commands). Until official Oreo, there may be no way to get voLTE back for those (myself included) who lost it. Unfortunately, even official Oreo may not fix the voLTE, it could be borked forever.
As said above, right now, safest way to go stock is to flash the twrp version, however, you still lose 4g unless the modem commands are removed from the updater-script or, you backup your efs partition in twrp of your current working system, restoring it over stock rom.
I didn't notice any side effects. Though I probably lost VoLTE, but since I didn't even know it existed or that people used voices to communicate on these things, it didn't really affect me I guess.
Yesterday though, I went like this -> Unlocked Stock -> Pixel XP -> OmniRom - Unlocked Stock NO IMEI -> Pixel XP -> Locked Stock. And I think I'm going back to Pixel XP today lol.
C--Dog said:
I didn't notice any side effects. Though I probably lost VoLTE, but since I didn't even know it existed or that people used voices to communicate on these things, it didn't really affect me I guess.
Yesterday though, I went like this -> Unlocked Stock -> Pixel XP -> OmniRom - Unlocked Stock NO IMEI -> Pixel XP -> Locked Stock. And I think I'm going back to Pixel XP today lol.
Click to expand...
Click to collapse
Wait - so locking your bootloader after flashing stock fixes the issue?
Fixes what issue? The IMEI thing? There's a whole thread on it. And one way was to flash Pixel, then flash stock. It's a little more complicated than that, but that's the gist.
I think VoLTE is not getting fixed, if that's what you meant.
C--Dog said:
Fixes what issue? The IMEI thing? There's a whole thread on it. And one way was to flash Pixel, then flash stock. It's a little more complicated than that, but that's the gist.
I think VoLTE is not getting fixed, if that's what you meant.
Click to expand...
Click to collapse
You may be about to save me. You got a link to that thread?
Edit: And no, I really don't care about VoLTE. Only reason I would is if I sell this phone to some Indian (which I won't, this phone is amazing)
Jrhotrod said:
You may be about to save me. You got a link to that thread?
Edit: And no, I really don't care about VoLTE. Only reason I would is if I sell this phone to some Indian (which I won't, this phone is amazing)
Click to expand...
Click to collapse
Here ya go:
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
Even the TWRP Stock ROM destroyed my IMEI. Don't try