SafetyNet FAILED after stock rom and relocked bootloader? (Cant use Google Pay) - G4 Q&A, Help & Troubleshooting

I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?

ntelas said:
I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?
Click to expand...
Click to collapse
Just an idea, take a look at your build.prop and see if anything looks off. Maybe you need to format some partitions before flashing the stock zip?
Cheers!

Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?

ntelas said:
Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?
Click to expand...
Click to collapse
I think that certain partitions need to be formatted you might want to search about that. I think TWRP can access the build.prop but not sure. I suggested checking build.prop because it will show different models, builds and basically would be an easy way to see if you are truly back to stock.
Good luck!

Thanks! I would have to install TWRP again maybe ?

ntelas said:
Thanks! I would have to install TWRP again maybe
Click to expand...
Click to collapse
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.

uweork said:
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.
Click to expand...
Click to collapse
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive

ntelas said:
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive
Click to expand...
Click to collapse
Then You didn´t read Properly.
I didn´t mean Root itself more Remnant parts of Root, that cause ur Saftynet fail.
on Samsung S2 once i thought so too, but banking app said no no no...
Only an Option

a user from this forum said that you need to take the line "ro.build.firgenprint=..." of the any MM/LP build.prop and insert it into the N build.prop (including reboot btw) and try again if google pay works for you...
I don't know if it works, I don't tried it, but you say us.

Related

What happens if flash fails?

I'm somewhat certain I already know the answer to this but I just need confirmation.
With a locked bootloader, flashing anything other than stock will be unsuccessful, right? I've just rooted my t807a and am looking to get xposed running. I just don't want to brick this thing now that I've FINALLY got it rooted.
So what's the bad? What happens if I try to flash a custom recovery? Will it flash and then not work? Will it fail to flash? Will I be bricked/caught in a bootloop?
Right off the bat, let me make one thing abundantly clear: I do not care if I trip Knox. I assume the warranty is voided as soon as I take a new device out of the box so I really don't care if Samsung or AT&T finds out that I've been misbehaving.
In case it matters:
Model: SAMSUNG-SM-T807A
Android version: 5.0.2
Baseband version: T807AUCU1BOD4
Kernel version: 3.4.39-4727547
Build number: LRX22G.T807AUCU1BOD4
Device Status: Custom
Okay I'm no genius, but maybe do a search on using the app flashify to flash custom recovery (twrp) ......obviously the right file for your device.
I've used thus before on other devices and it work well but do your research . Flash at own risk.
Sent from my SM-T800 using Tapatalk
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
ashyx said:
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
Click to expand...
Click to collapse
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
thorvindr said:
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
Click to expand...
Click to collapse
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
ashyx said:
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
Click to expand...
Click to collapse
Having trouble finding documentation on this device's partitions, which are (it seems) not quite the same as most Android devices. To make sure I can recover from (for example) a bad ROM flash, what should I backup? Is flashfire the thing to use for making such a backup?
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
ashyx said:
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
If I can boot to recovery, won't I be able to access the flashfire backup on my microsd card? As long as I don't try to flash a custom recovery, shouldn't I always be able to work from that backup? Or does a flashfire backup need the flashfire app to be useable?
thorvindr said:
Or does a flashfire backup need the flashfire app to be useable?
Click to expand...
Click to collapse
You just answered your own question.
ashyx said:
You just answered your own question.
Click to expand...
Click to collapse
No, I didn't. I assume you're telling me the answer to my first question is no?
ashyx said:
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
thorvindr said:
No, I didn't. I assume you're telling me the answer to my first question is no?
Click to expand...
Click to collapse
I quoted your last question. The answer is you need flashfire.
---------- Post added at 07:24 PM ---------- Previous post was at 07:06 PM ----------
thorvindr said:
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
Click to expand...
Click to collapse
Tbh I don't use kies/smart switch much, but you will find information on it on the net.

Flashed faulty [System] from recovery

What happened:
1. Used TWRP to flash an earlier System backup
2. Boots but two system apps force close and phone reboots
3. This goes on indefinitely
4. Can no longer go to either recovery
I'm thinking I should use FlashTool and flash a default System for 14.5.A.0.270 but I can't seem to find any firmware image for it. Does anybody have this/better idea to get me out of the boot loop?
Edit: found the file, will report back.
another complication: I can't go into flashmode
ctap001 said:
another complication: I can't go into flashmode
Click to expand...
Click to collapse
Bl locked or unlocked?
levone1 said:
Bl locked or unlocked?
Click to expand...
Click to collapse
locked. Am I SOTL?
ctap001 said:
locked. Am I SOTL?
Click to expand...
Click to collapse
Probably not. Are you wanting to save data, etc?
levone1 said:
Probably not. Are you wanting to save data, etc?
Click to expand...
Click to collapse
If possible, yes. My last complete backup was on September. I'm still waiting for the firmware download to finish, however if I that doesn't work (won't allow me to flash) I am completely OK with wiping everything.
ctap001 said:
If possible, yes. My last complete backup was on September. I'm still waiting for the firmware download to finish, however if I that doesn't work (won't allow me to flash) I am completely OK with wiping everything.
Click to expand...
Click to collapse
I wasn't sure from the first post. Does the phone stay on if you don't do anything or does it automatically reboot? I was thinking a good first try might be NUT dual recovery installer, but won't work if phone won't stay on. Check back after your flash attempt - note that you will likely wipe all of your data if flashing with FT.
levone1 said:
I wasn't sure from the first post. Does the phone stay on if you don't do anything or does it automatically reboot? I was thinking a good first try might be NUT dual recovery installer, but won't work if phone won't stay on. Check back after your flash attempt - note that you will likely wipe all of your data if flashing with FT.
Click to expand...
Click to collapse
It won't stay on. It will crash then reboot.
Can't proceed with flashtool because I am having trouble installing the drivers (on w10)
ctap001 said:
It won't stay on. It will crash then reboot.
Can't proceed with flashtool because I am having trouble installing the drivers (on w10)
Click to expand...
Click to collapse
If you can't boot, you might be able to save data through adb. If you give up on saving data, either Emma or PC Companion can repair phone if you can't get FT to work. Since they're both official Sony programs, they may be easier to get working with Win10.
levone1 said:
If you can't boot, you might be able to save data through adb. If you give up on saving data, either Emma or PC Companion can repair phone if you can't get FT to work. Since they're both official Sony programs, they may be easier to get working with Win10.
Click to expand...
Click to collapse
I have flashed System from an unrooted FTF. Still can't access recovery though
ctap001 said:
I have flashed System from an unrooted FTF. Still can't access recovery though
Click to expand...
Click to collapse
Which fw did you flash? If it's 5.1, (368 at least, not sure about 216), I've read that Kingroot method is working now. Look here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 . If 5.0, there is a root tool that will work. Once rooted, flash NUT's installer for recovery.
levone1 said:
Which fw did you flash? If it's 5.1, (368 at least, not sure about 216), I've read that Kingroot method is working now. Look here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 . If 5.0, there is a root tool that will work. Once rooted, flash NUT's installer for recovery.
Click to expand...
Click to collapse
>5.1
I tried flashing the early pre-rooted 5.1s and they gave me problems with NFC so I reverted to 5.0.1
Looking for the 5.0 root tool right now.
edit: kingroot doesn't work
ctap001 said:
>5.1
I tried flashing the early pre-rooted 5.1s and they gave me problems with NFC so I reverted to 5.0.1
Looking for the 5.0 root tool right now.
edit: kingroot doesn't work
Click to expand...
Click to collapse
Haven't tried it myself, but it seems like they've got it working. I noticed in the thread that there seems to be different instructions for 368 and 216....
levone1 said:
Haven't tried it myself, but it seems like they've got it working. I noticed in the thread that there seems to be different instructions for 368 and 216....
Click to expand...
Click to collapse
I got everything back to 270 now. Currently at the optimizing apps part. This all began because I upgraded SD cards and while everything was carried over through a plain copy-paste, my Walkman playlists and favorites didn't make it. I somehow equated the System portion as a possible fix.
Anyway are you on 5.1? Does NFC unlock works? Thanks for pointing me at the right direction.
ctap001 said:
I got everything back to 270 now. Currently at the optimizing apps part. This all began because I upgraded SD cards and while everything was carried over through a plain copy-paste, my Walkman playlists and favorites didn't make it. I somehow equated the System portion as a possible fix.
Anyway are you on 5.1? Does NFC unlock works? Thanks for pointing me at the right direction.
Click to expand...
Click to collapse
Haven't had any problems with 5.1. I flashed stock .216 few a week ago, and have since rooted, modded, etc., and everything good. Your problems were probably related to PRF. I've read the same from others
levone1 said:
Haven't had any problems with 5.1. I flashed stock .216 few a week ago, and have since rooted, modded, etc., and everything good. Your problems were probably related to PRF. I've read the same from others
Click to expand...
Click to collapse
> .216
The latest I tried was .380
King root
I had a similar problem last night. Installed stock firmware off flashtool then loaded it up and King Root worked perfectly. Having trouble getting a recovery on the phone now.
wwwjunkboywww said:
I had a similar problem last night. Installed stock firmware off flashtool then loaded it up and King Root worked perfectly. Having trouble getting a recovery on the phone now.
Click to expand...
Click to collapse
Use 'installer' option from Z1c downloads on NUT's download page. It's never failed for me. Just watch phone screen and grant 'OK' for adb access and for root. Besides that, if you have unlocked bl, use fastboot or Rashr.
Thanks
levone1 said:
Use 'installer' option from Z1c downloads on NUT's download page. It's never failed for me. Just watch phone screen and grant 'OK' for adb access and for root. Besides that, if you have unlocked bl, use fastboot or Rashr.
Click to expand...
Click to collapse
Yeah i had tried that. The BAT right? I ended up flashing multi twrp and then using that to get NUT's, he's made a sweet recovery.

What Steps Do I Take To Update From 2.19.40.20?

So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?

How can I unroot my Pixel XL?

A summary of my situation:
- Got Pixel XL
-Downloaded snapchat
-Logged into snapchat
-Rooted phone
-Accidentally logged out of snapchat
-Snapchat checks for root before it lets you log in
-I cannot log in until I first unroot
I have tried searching the Pixel XL reddit as well as the XDA Pixel XL forums, but I could not find a guide/program for unrooting the phone. If anyone knows how I could go about this, please let me know. Thank you.
Open SuperSu, cgo to settings, click on Unroot, reboot. Done
Why does Snapchat not like root? Been reading it a lot on other posts but not why.
FFutstuFF said:
A summary of my situation:
- Got Pixel XL
-Downloaded snapchat
-Logged into snapchat
-Rooted phone
-Accidentally logged out of snapchat
-Snapchat checks for root before it lets you log in
-I cannot log in until I first unroot
I have tried searching the Pixel XL reddit as well as the XDA Pixel XL forums, but I could not find a guide/program for unrooting the phone. If anyone knows how I could go about this, please let me know. Thank you.
Click to expand...
Click to collapse
you cant youre stuck forever
*sarcasm*
ZeroHart said:
Open SuperSu, cgo to settings, click on Unroot, reboot. Done
Click to expand...
Click to collapse
This doesn't work. Uninstall fails.
I mean, ultimately you can choose to flash the factory image or sideload the full OTA update which will reset you back to stock. (Be careful with the flashall bat file in the factory image...edit it and remove the -w from the fastboot update command if you don't want to wipe data). That is a cannon, yes.
FFutstuFF said:
This doesn't work. Uninstall fails.
Click to expand...
Click to collapse
Just flash a kernel and you should lose root
jjayzx said:
Why does Snapchat not like root? Been reading it a lot on other posts but not why.
Click to expand...
Click to collapse
Makes it easier to get around notifications that you have watched a post or the notification that you have performed a screen shot.
Instead of going after the exploits individually they go after the "root" of the cause. Pun so intended.
cwalker0906 said:
Just flash a kernel and you should lose root
Click to expand...
Click to collapse
Oh that's right, Chainfire fixed it so it's a boot img only patch now. Yea, do this and you're good to go.
Say I needed to remove root and relock the bootloader to return this phone in exchange for the 128gb model. Is that possible? I've read that relocking will instantly brick my phone. I'm nervous about doing anything to this phone now haha.
Anthony825 said:
Say I needed to remove root and relock the bootloader to return this phone in exchange for the 128gb model. Is that possible? I've read that relocking will instantly brick my phone. I'm nervous about doing anything to this phone now haha.
Click to expand...
Click to collapse
Relocking if you have modified it MAY soft brick it. If you changed anything just go ahead and restore using a stock image and then relock.
The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?
Anthony825 said:
The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?
Click to expand...
Click to collapse
Any luck with un-rooting it?
Haven't attempted it yet. Going to call around at all the Verizon in my area to see if any of them have the 128gb in either size pixel on my break at work today first. If they do, then I'll attempt unroot this evening and let you guys know what happens.
Anthony825 said:
The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?
Click to expand...
Click to collapse
Why not just download the factory image flash back to stock. Longer process because you have to download that file but ultimately you probably want the stock image laying around just in case anyway..
https://developers.google.com/android/images
I have it downloaded as of last night. That's what I'll end up doing if I find a store with the 128gb in stock.
Turns out there are no stores around in my whole state that have the 128gb in stock. So no point in removing root for me unless I want my bluetooth connectivity with my car back.
Just flash the stock boot.img from the version you're currently on. Then uninstall the SU app.
spaceman860 said:
Just flash the stock boot.img from the version you're currently on. Then uninstall the SU app.
Click to expand...
Click to collapse
I can confirm that this works
I downloaded the factory image: marlin-nde63v-factory-a66866ba.zip
Found boot.img inside and extracted it and then flashed by
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Snapchat now opens then i rerooted via chainfires steps here
https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F?sfc=true
I had rooted with with boot to root. I use fastboot to flash stock boot.img to boot_a and boot_b. When my phone rebooted it wiped it self. Was I supposed to get boot.img from the OTA image> Ws there something that I could have done to avoid the wipe? I'm very sad to have lost lots of data.
Thanks.
~Josh

New 10 Owner - what to do first?

Just got a 10 Factory Unlocked. I do need to root for Xprivacy and AdAway, etc. and of course, to make a nandroid. I suppose I could use ADB for such a thing, but TWRP surely does make life easier.
Since this is the first phone I've ever had that was already unlocked, I'm not quite sure where to start with rooting. I'm a little concerned because I'm seeing posts discussing how the radio might go wonky. Not ready to flash a custom ROM yet, I just want to dip my toe in the water for now.
I'd be grateful if someone could point the way.
BTW, the faceplate on my 10 is white, I was expecting black based on all the photos I've seen. Is this because I got the Factory Unlocked edition?
Thanks in advance!
is it on nougat or still marshmallow? i think nougat right? Xposed won't work on nougat anyway and you don't need to worry about the radio. if it's unlocked already and want to just root and you need to pass safetynet, get magisk v12. first you need to flash twrp and then flash the magisk zip to get root and be able to pass safetynet, be sure to not flash anything which modifies directly the system, otherwise no stock OTA and some apps won't work even if you use magisk hide
DeeZZ_NuuZZ said:
is it on nougat or still marshmallow? i think nougat right? Xposed won't work on nougat anyway and you don't need to worry about the radio, just unlock bootloader using htcdev.com
then flash a latest twrp and install a custom rom, but check first which main version is installed
Click to expand...
Click to collapse
Haven't even turned the phone on yet - letting her charge to 100% before I do anything. I'm confused - why would I need to unlock the bootloader if I already have an unlocked phone? Or by 'Factory Unlocked' do they mean SIM unlocked, versus bootloader unlocked?
BillTheCat said:
Haven't even turned the phone on yet - letting her charge to 100% before I do anything. I'm confused - why would I need to unlock the bootloader if I already have an unlocked phone? Or by 'Factory Unlocked' do they mean SIM unlocked, versus bootloader unlocked?
Click to expand...
Click to collapse
yea sorry, i've read way too fast and noticed it later, check my post now
DeeZZ_NuuZZ said:
if it's unlocked already and want to just root and you need to pass safetynet, get magisk v12. first you need to flash twrp and then flash the magisk zip to get root and be able to pass safetynet, be sure to not flash anything which modifies directly the system, otherwise no stock OTA and some apps won't work even if you use magisk hide
Click to expand...
Click to collapse
Not familiar with 'safetynet', and yes - I do need Xposed therefore it will modify the /system partition so far as I understand.
In any event, it sounds like the starting point is TWRP for anything to do with root, correct?
BillTheCat said:
Not familiar with 'safetynet', and yes - I do need Xposed therefore it will modify the /system partition so far as I understand.
In any event, it sounds like the starting point is TWRP for anything to do with root, correct?
Click to expand...
Click to collapse
yes you need twrp, without it no root... the thing is there is no Xposed for nougat and I think your phone came with android 7/ nougat right? if yes, forget Xposed. but you can use apps like adaway with magisk too.
So that'S why you should search for the Magisk thread and read everything about it, before you proceed
DeeZZ_NuuZZ said:
I think your phone came with android 7/ nougat right?
Click to expand...
Click to collapse
No, the HTC 10 shipped with MM. I guess I'll have to fire her up and see where I'm at.
So, assuming that I'm on MM, then it's just TWRP, flash SuperSU from recovery, install Xposed and I'm off and running - nothing extra, correct?
How would I make a Nandroid of the current factory ROM (all partitions - not file based) using ADB just in case?
BillTheCat said:
No, the HTC 10 shipped with MM. I guess I'll have to fire her up and see where I'm at.
So, assuming that I'm on MM, then it's just TWRP, flash SuperSU from recovery, install Xposed and I'm off and running - nothing extra, correct?
How would I make a Nandroid of the current factory ROM (all partitions - not file based) using ADB just in case?
Click to expand...
Click to collapse
yea if MM then it's that easy.
full stock nandroid can be done in twrp, there you can backup system, data, boot and recovery
also the system image, but don't know if you need that, but you can try to backup it too, be sure to have enough space
I got my unit one year ago, now I want root, I got nougat us unlocked and I want stock ROM, how can I do?
Enviado do meu HTC 10 através de Tapatalk
symy said:
I got my unit one year ago, now I want root, I got nougat us unlocked and I want stock ROM, how can I do?
Enviado do meu HTC 10 através de Tapatalk
Click to expand...
Click to collapse
flash magisk v12 then you have root and also can use android pay and other apps which needs passed safetynet
if you don't mind safetynet, you can also use systemless supersu
To the OP, surely factory unlocked indicates unlocked to all networks rather than bootloader unlocked ? Check this first to save some hassle. If the bootloader isn't unlocked yet, you could consider sunshine s off , it will cost you but on mm firmware you can s off and stay locked which can be an advantage. Worth checking bootloader status first though
DeeZZ_NuuZZ said:
flash magisk v12 then you have root and also can use android pay and other apps which needs passed safetynet
if you don't mind safetynet, you can also use systemless supersu
Click to expand...
Click to collapse
Can you tell me the great advantages of doing root, I do not want to lose the updates via ota
Enviado do meu HTC 10 através de Tapatalk
Confirmed - the 10 shipped with MM, so I'm in good shape. Flashing TWRP now. Thanks!
timbohobbs said:
To the OP, surely factory unlocked indicates unlocked to all networks rather than bootloader unlocked ? Check this first to save some hassle. If the bootloader isn't unlocked yet, you could consider sunshine s off , it will cost you but on mm firmware you can s off and stay locked which can be an advantage. Worth checking bootloader status first though
Click to expand...
Click to collapse
Yeah, just crashed into that wall. Almost gave myself a soft brick.
So, sunshine it is. Did that with my M9 and it worked out great. Thanks.
BillTheCat said:
Confirmed - the 10 shipped with MM, so I'm in good shape. Flashing TWRP now. Thanks!
Click to expand...
Click to collapse
What exactly do you need xposed for? It won't work once you updated to Nougat. And Nougat is much better tan Marshmallow at least as far as I'm concerned. All I need I've been able to find on custom ROMs and or by additional root Apps.
Sent from my htc_pmeuhl using XDA Labs
BillTheCat said:
Yeah, just crashed into that wall. Almost gave myself a soft brick.
So, sunshine it is. Did that with my M9 and it worked out great. Thanks.
Click to expand...
Click to collapse
Probably worth updating via ota after sunshine to nougat, not before. You can stay locked and s off then. After ota you can root as usual
timbohobbs said:
Probably worth updating via ota after sunshine to nougat, not before. You can stay locked and s off then. After ota you can root as usual
Click to expand...
Click to collapse
Can't go Nougat until Xposed is up and running.
So far:
Unlocked bootloader and went S-off via Sunshine
Installed TWRP
Made the error of allowing modification before taking a backup - not sure if I'm hosed.
Flashed SuperSU SR3 following Chainfire's instructions to send command via ADB
Flashed Xposed
Next: TiBu and restoring apps.
5m4r7ph0n36uru said:
What exactly do you need xposed for? It won't work once you updated to Nougat. And Nougat is much better tan Marshmallow at least as far as I'm concerned. All I need I've been able to find on custom ROMs and or by additional root Apps.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Xprivacy.
BillTheCat said:
Can't go Nougat until Xposed is up and running.
So far:
Unlocked bootloader and went S-off via Sunshine
Installed TWRP
Made the error of allowing modification before taking a backup - not sure if I'm hosed.
Flashed SuperSU SR3 following Chainfire's instructions to send command via ADB
Flashed Xposed
Next: TiBu and restoring apps.
Click to expand...
Click to collapse
You won't ( probably ) be able to do further ota in the future with your modified backup as you're probably aware. But don't worry too much, it's likely the firmware you're after will be available elsewhere
timbohobbs said:
You won't ( probably ) be able to do further ota in the future with your modified backup as you're probably aware. But don't worry too much, it's likely the firmware you're after will be available elsewhere
Click to expand...
Click to collapse
No big deal. I'm not ready for Nougat until Xposed is running. However, HTC has an RUU available already, so we're good to go.
http://www.htc.com/us/support/htc-10/news/
And of course, if I get bored, there are any number of custom ROMs available. I was running Maximus on my M9, I'd probably go that route again.

Categories

Resources