Related
Hello, I have a problem with apps that need safetynet passed to get it working. Such as Snapchat or Pokemon GO. Second one actually does work sometimes, but the first one is giving me massive headache. I'm asking how to pass this test on roms based on LineageOS. I have tried to unroot it with no luck. Unrooting and systemless root also doesn't work. I've heard somewhere that locking bootloader could be a possible solution to that. But, how to lock it?
N910F + 7.1.1
As far as I know, Snapchat only has a problem with Xposed. Unable to comment on pokemon, never used it.
I installed and logged in to snapchat on a phone without Xposed, then used TB and copied the files to my phone with Xposed.
Everything works as it should. If that's not possible then uninstall Xposed first and reinstall it after you have snapchat.
JagDave said:
As far as I know, Snapchat only has a problem with Xposed. Unable to comment on pokemon, never used it.
I installed and logged in to snapchat on a phone without Xposed, then used TB and copied the files to my phone with Xposed.
Everything works as it should. If that's not possible then uninstall Xposed first and reinstall it after you have snapchat.
Click to expand...
Click to collapse
I do not have Xposed. The trick with TB doesn't work for me anymore. I've tried to do backup on Touchwiz and CM 13 and then restore them on Lineage 14.1. No one worked, Snapchat tells to log in first. it is the only app I need to use, but I'm in love with Lineage.
Graivite said:
I do not have Xposed. The trick with TB doesn't work for me anymore. I've tried to do backup on Touchwiz and CM 13 and then restore them on Lineage 14.1. No one worked, Snapchat tells to log in first. it is the only app I need to use, but I'm in love with Lineage.
Click to expand...
Click to collapse
did you fix this bro?
entwicklun said:
did you fix this bro?
Click to expand...
Click to collapse
Kind of. We are not able to log in into Snapchat on Lineage OS 14 yet. However, I've discovered a possible way to use the app,. This method has been working for me for last couple of days.
Every single time you want to install Lineage and use Snapchat you have to install Touchwiz based firmware that you can log in into the app on, simply log in, root the device, install Titanium Backup and make a backup of Snapchat. Copy the backup on the sd card. Then install Lineage OS, Snapchat, Titanium Backup, try to log in into Snapchat. I know it will say it can't connect to the server. Now restore backup of Snapchat via Tïtanium Backup - data only. Enjoy working Snapchat.
From what I've seen Snapchat makes little updates of user stats every 24h. Because you can't use backup older than 24hours otherwise it will not work. I am not sure about the exact time it's collecting stats. But a fresh backup works every time. It is very important to do a fresh backup and do a one try to log in into Snapchat.
I do not use Android Pay or Pokemon anymore.
Graivite said:
Kind of. We are not able to log in into Snapchat on Lineage OS 14 yet. However, I've discovered a possible way to use the app,. This method has been working for me for last couple of days.
Every single time you want to install Lineage and use Snapchat you have to install Touchwiz based firmware that you can log in into the app on, simply log in, root the device, install Titanium Backup and make a backup of Snapchat. Copy the backup on the sd card. Then install Lineage OS, Snapchat, Titanium Backup, try to log in into Snapchat. I know it will say it can't connect to the server. Now restore backup of Snapchat via Tïtanium Backup - data only. Enjoy working Snapchat.
From what I've seen Snapchat makes little updates of user stats every 24h. Because you can't use backup older than 24hours otherwise it will not work. I am not sure about the exact time it's collecting stats. But a fresh backup works every time. It is very important to do a fresh backup and do a one try to log in into Snapchat.
I do not use Android Pay or Pokemon anymore.
Click to expand...
Click to collapse
thanks bro. so I'm gonna get my new note 4. can you walk me through that alittle?
like which roms on snapdragon can I use?
step 1 install recovery twrp
step 2 flash rom
step 3 install and log in snaphat
step 4 root phone or am I supposed to turn on the phone now stock (it's brand new my note 4), install snapshat log in, root then install titanium and back it up. back up snapchat.
I don't need twrp to root do I? sorry for being clueless man
entwicklun said:
thanks bro. so I'm gonna get my new note 4. can you walk me through that alittle?
like which roms on snapdragon can I use?
step 1 install recovery twrp
step 2 flash rom
step 3 install and log in snaphat
step 4 root phone or am I supposed to turn on the phone now stock (it's brand new my note 4), install snapshat log in, root then install titanium and back it up. back up snapchat.
I don't need twrp to root do I? sorry for being clueless man
Click to expand...
Click to collapse
It depends on whether you want to stick with Touchwiz or flash LineageOS. Every stock firmware let you log in to Snapchat without installing or flashing anything. Snapchat works on phone straight out of box.
Guide for snapdragon touchwiz
As I mentioned earlier, Snapchat works on every stock firmware. You do not need anything else. Just install Snapchat and log in, simple as that. Now, if you want to flash a custom TOUCHWIZ based rom it shouldn't be a problem to log in to the app. Even though it's custom rom, you're still able to log in. You do not need any backups at all.
Guide for snapdragon LineageOS
LineageOS is not a touchwiz based rom. Snapchat will never work on it until it gets official and be signed. If you want to install one of the builds and have Snapchat working you need to fo following steps:
1. Your phone needs to have a stock firmware (that is the one that comes out of the box, but also the ones you flash with odin)
2. Log in to Snapchat
3. Root your phone (for example using CF-Auto Root), you do not need recovery twrp to root your phone.
4. Turn your phone on
5. Install Titanium Backup, open it, do a backup of Snapchat
6. Open "My Files" that's stock file manager for Samsung's phones, go to your phone's storage search for Titanium Backup folder, open it and you'll see three files.
7. Copy all of them to your sd card.
8. Install custom recovery (like twrp), flash LineageOS, gapps
9. Log in to your Google account, download Snapchat, try to log in (I know it's going to fail, but it's important)
10. Go to LineageOS -> About phone -> Click a few times on Build number until it say you unlocked developer options
11. Go back to main settings menu, scroll down to the bottom, you'll see now Developer options, click on it
12. Search for "Root Access", click on it and select Apps and ADB
13. Install Titanium Backup, open it and close.
14. Open "Files" app, that's stock LineageOS file manager
15. Go to your sd card, select the files you backup (three files) and copy them to phone's storage -> Titanium Backup folder
16. Open Titanium Backup again, click on Snapchat -> restore -> data only.
17. Now you can open Snapchat and enjoy it.
Hope that help you
Graivite said:
It depends on whether you want to stick with Touchwiz or flash LineageOS. Every stock firmware let you log in to Snapchat without installing or flashing anything. Snapchat works on phone straight out of box.
Guide for snapdragon touchwiz
As I mentioned earlier, Snapchat works on every stock firmware. You do not need anything else. Just install Snapchat and log in, simple as that. Now, if you want to flash a custom TOUCHWIZ based rom it shouldn't be a problem to log in to the app. Even though it's custom rom, you're still able to log in. You do not need any backups at all.
Guide for snapdragon LineageOS
LineageOS is not a touchwiz based rom. Snapchat will never work on it until it gets official and be signed. If you want to install one of the builds and have Snapchat working you need to fo following steps:
1. Your phone needs to have a stock firmware (that is the one that comes out of the box, but also the ones you flash with odin)
2. Log in to Snapchat
3. Root your phone (for example using CF-Auto Root), you do not need recovery twrp to root your phone.
4. Turn your phone on
5. Install Titanium Backup, open it, do a backup of Snapchat
6. Open "My Files" that's stock file manager for Samsung's phones, go to your phone's storage search for Titanium Backup folder, open it and you'll see three files.
7. Copy all of them to your sd card.
8. Install custom recovery (like twrp), flash LineageOS, gapps
9. Log in to your Google account, download Snapchat, try to log in (I know it's going to fail, but it's important)
10. Go to LineageOS -> About phone -> Click a few times on Build number until it say you unlocked developer options
11. Go back to main settings menu, scroll down to the bottom, you'll see now Developer options, click on it
12. Search for "Root Access", click on it and select Apps and ADB
13. Install Titanium Backup, open it and close.
14. Open "Files" app, that's stock LineageOS file manager
15. Go to your sd card, select the files you backup (three files) and copy them to phone's storage -> Titanium Backup folder
16. Open Titanium Backup again, click on Snapchat -> restore -> data only.
17. Now you can open Snapchat and enjoy it.
Hope that help you
Click to expand...
Click to collapse
ok thanks bro, I have one more question, what is lineageOS all about, is it new or something? how come I would choose lineageOS over say touchwiz. what is the major differences? is it like CM roms vs normal roms, quicker, less bloatware, better battery life etc? or am I wrong about CM roms vs normal roms? tbh I don't even know the difference between auroa/cm/touchwiz.
do you have a short explanation of lineageOS for me? because from what I can tell, I should be definitely going lineageOS as it's more supported right now. I used to use omega rom on my old note 4 but support left, and I liked that rom except for random reboots and slightly poor battery life that I can kind of remember.
I'm so sorry man for asking stupid questions. I love customing my note 4 but I don't know exactly what I'm doing haha. I just know I love the extra features that aren't on stock, xposed being a major.
thank you man!
entwicklun said:
ok thanks bro, I have one more question, what is lineageOS all about, is it new or something? how come I would choose lineageOS over say touchwiz. what is the major differences? is it like CM roms vs normal roms, quicker, less bloatware, better battery life etc? or am I wrong about CM roms vs normal roms? tbh I don't even know the difference between auroa/cm/touchwiz.
do you have a short explanation of lineageOS for me? because from what I can tell, I should be definitely going lineageOS as it's more supported right now. I used to use omega rom on my old note 4 but support left, and I liked that rom except for random reboots and slightly poor battery life that I can kind of remember.
I'm so sorry man for asking stupid questions. I love customing my note 4 but I don't know exactly what I'm doing haha. I just know I love the extra features that aren't on stock, xposed being a major.
thank you man!
Click to expand...
Click to collapse
LineageOS is a continuation of CM, since CM stopped being developed and die. It's just CM with new name. LineageOS 14.1 is based on Android 7.1.1, which is the latest you can get right now. The major differences are speed, no bloatware, battery life is the same as stock touchwiz rom. The most important one is speed, I've never seen anything that fast as this is. The builds these days can be daily drivers since our developers fixed 95% of bugs. I can recommend you builds by @ripee he got links to them in the signature(triltexx), download pico google gapps and you're good to go.
The difference between auroa/cm/touchwiz. Correct way to list them is port roms/lineageOS/note 4 roms based on stock firmware. Port roms are ones that people port from other device such as S7, Note 5. It's still touchwiz right, but it's a port. That means it's made to work on our Note 4's. These days ports like Aurora / Norma are pretty much fully working apart from things like fingerprint scanner. LineageOS(old name - CM) - just read above. Note 4 roms based on stock firmware - that means developers use stock Note 4 firmware and they edit it. An example of that kind of rom is rom by ALEXNDR. It's a rock solid rom. Stock firmware, options to install with/without root or xposed and debloated. it is fully working because it's made on stock firmware for our devices.
I think you're be very happy with ripee builds of LineageOS, he makes them every day and uploads. Not a single random reboot or freeze, battery life 4-5 hours of SOT.
If you got any further questions, just ask. I'd love to answer you the best I can.
Graivite said:
LineageOS is a continuation of CM, since CM stopped being developed and die. It's just CM with new name. LineageOS 14.1 is based on Android 7.1.1, which is the latest you can get right now. The major differences are speed, no bloatware, battery life is the same as stock touchwiz rom. The most important one is speed, I've never seen anything that fast as this is. The builds these days can be daily drivers since our developers fixed 95% of bugs. I can recommend you builds by @ripee he got links to them in the signature(triltexx), download pico google gapps and you're good to go.
The difference between auroa/cm/touchwiz. Correct way to list them is port roms/lineageOS/note 4 roms based on stock firmware. Port roms are ones that people port from other device such as S7, Note 5. It's still touchwiz right, but it's a port. That means it's made to work on our Note 4's. These days ports like Aurora / Norma are pretty much fully working apart from things like fingerprint scanner. LineageOS(old name - CM) - just read above. Note 4 roms based on stock firmware - that means developers use stock Note 4 firmware and they edit it. An example of that kind of rom is rom by ALEXNDR. It's a rock solid rom. Stock firmware, options to install with/without root or xposed and debloated. it is fully working because it's made on stock firmware for our devices.
I think you're be very happy with ripee builds of LineageOS, he makes them every day and uploads. Not a single random reboot or freeze, battery life 4-5 hours of SOT.
If you got any further questions, just ask. I'd love to answer you the best I can.
Click to expand...
Click to collapse
quality help mate, I really appreciate it. I'll go with lineageOS and go through the snapchat process on it (already worried I'm gonna screw up lol) but I'll give it a go.
one thing I've always hated was updates, I'd always had to fresh install, losing my calendar setup and over phone layout setup, settings, everything. I always wanted to dirty flash on an update but people said don't, what are your thoughts on ripees build?
so I'm gonna go through the process and do it over the next week, I got a lot on so can't transfer over from my lg v20 to note 4. I got the wrong damn lg v20 which has no roms or support lol...
I'm looking at emotionOS, what are your thoughts on it? I kind of want the extra features that a basic CM won't have. what you reckon?
---------- Post added at 10:47 PM ---------- Previous post was at 09:52 PM ----------
Graivite said:
It depends on whether you want to stick with Touchwiz or flash LineageOS. Every stock firmware let you log in to Snapchat without installing or flashing anything. Snapchat works on phone straight out of box.
Guide for snapdragon touchwiz
As I mentioned earlier, Snapchat works on every stock firmware. You do not need anything else. Just install Snapchat and log in, simple as that. Now, if you want to flash a custom TOUCHWIZ based rom it shouldn't be a problem to log in to the app. Even though it's custom rom, you're still able to log in. You do not need any backups at all.
Guide for snapdragon LineageOS
LineageOS is not a touchwiz based rom. Snapchat will never work on it until it gets official and be signed. If you want to install one of the builds and have Snapchat working you need to fo following steps:
1. Your phone needs to have a stock firmware (that is the one that comes out of the box, but also the ones you flash with odin)
2. Log in to Snapchat
3. Root your phone (for example using CF-Auto Root), you do not need recovery twrp to root your phone.
4. Turn your phone on
5. Install Titanium Backup, open it, do a backup of Snapchat
6. Open "My Files" that's stock file manager for Samsung's phones, go to your phone's storage search for Titanium Backup folder, open it and you'll see three files.
7. Copy all of them to your sd card.
8. Install custom recovery (like twrp), flash LineageOS, gapps
9. Log in to your Google account, download Snapchat, try to log in (I know it's going to fail, but it's important)
10. Go to LineageOS -> About phone -> Click a few times on Build number until it say you unlocked developer options
11. Go back to main settings menu, scroll down to the bottom, you'll see now Developer options, click on it
12. Search for "Root Access", click on it and select Apps and ADB
13. Install Titanium Backup, open it and close.
14. Open "Files" app, that's stock LineageOS file manager
15. Go to your sd card, select the files you backup (three files) and copy them to phone's storage -> Titanium Backup folder
16. Open Titanium Backup again, click on Snapchat -> restore -> data only.
17. Now you can open Snapchat and enjoy it.
Hope that help you
Click to expand...
Click to collapse
I've rooted, installed flashify to flash twrp but it doesn't install it properly. I restart my phone and it goes automatically to download screen and says at the top in red phone could not boot normally. when in download mode I can't even vol up home power to get to twrp, nothing happens. any ideas why? so I'm stuck on download mode. I can get out if I install twrp on odin but then again when I try to get into recovery it instead goes to download mode and says phone could not boot normally.
I haven't got to flash the rom yet because I can't get twrp installed properly.
you know why? thanks man
entwicklun said:
quality help mate, I really appreciate it. I'll go with lineageOS and go through the snapchat process on it (already worried I'm gonna screw up lol) but I'll give it a go.
one thing I've always hated was updates, I'd always had to fresh install, losing my calendar setup and over phone layout setup, settings, everything. I always wanted to dirty flash on an update but people said don't, what are your thoughts on ripees build?
so I'm gonna go through the process and do it over the next week, I got a lot on so can't transfer over from my lg v20 to note 4. I got the wrong damn lg v20 which has no roms or support lol...
I'm looking at emotionOS, what are your thoughts on it? I kind of want the extra features that a basic CM won't have. what you reckon?
---------- Post added at 10:47 PM ---------- Previous post was at 09:52 PM ----------
I've rooted, installed flashify to flash twrp but it doesn't install it properly. I restart my phone and it goes automatically to download screen and says at the top in red phone could not boot normally. when in download mode I can't even vol up home power to get to twrp, nothing happens. any ideas why? so I'm stuck on download mode. I can get out if I install twrp on odin but then again when I try to get into recovery it instead goes to download mode and says phone could not boot normally.
I haven't got to flash the rom yet because I can't get twrp installed properly.
you know why? thanks man
Click to expand...
Click to collapse
I think it is the right time to chat a little through private messeges. I do not want to spam, just a kind of respect for moderators.
Graivite said:
Hello, I have a problem with apps that need safetynet passed to get it working. Such as Snapchat or Pokemon GO. Second one actually does work sometimes, but the first one is giving me massive headache. I'm asking how to pass this test on roms based on LineageOS. I have tried to unroot it with no luck. Unrooting and systemless root also doesn't work. I've heard somewhere that locking bootloader could be a possible solution to that. But, how to lock it?
N910F + 7.1.1
Click to expand...
Click to collapse
If you can get Pokemon Go to work, can you plz send me a pm on how thanks?
Or wright it here and pm me so i don't miss it
Tesla said:
If you can get Pokemon Go to work, can you plz send me a pm on how thanks?
Or wright it here and pm me so i don't miss it
Click to expand...
Click to collapse
I am going it write it here if anyone is interested.
From what I've heard and read, you can't get Pokemon Go to work on LineageOS now. I've tested it and it's true. We have to wait till LineageOS get official. It will be signed, unrooted and every app that is based on Safetynet test would probably work just fine.
Snapchat works only if you have a backup of it.
Graivite said:
I am going it write it here if anyone is interested.
From what I've heard and read, you can't get Pokemon Go to work on LineageOS now. I've tested it and it's true. We have to wait till LineageOS get official. It will be signed, unrooted and every app that is based on Safetynet test would probably work just fine.
Snapchat works only if you have a backup of it.
Click to expand...
Click to collapse
Okey. Good to know.
Can i root stock and do the root things i want and then unroot and play Pokemon Go?
Debloat would be nice.
Tesla said:
Okey. Good to know.
Can i root stock and do the root things i want and then unroot and play Pokemon Go?
Debloat would be nice.
Click to expand...
Click to collapse
I think it is possible and should work. You can also use Package Disabler. You can debloat your phone using it, it doesn't require root.
I've gotten around the xposed snapchat thing by using the SudoHide app and hiding the xposed installer and supersu.
Rooted Note 4 with xposed on 6.0.1
Graivite said:
Hello, I have a problem with apps that need safetynet passed to get it working. Such as Snapchat or Pokemon GO. Second one actually does work sometimes, but the first one is giving me massive headache. I'm asking how to pass this test on roms based on LineageOS. I have tried to unroot it with no luck. Unrooting and systemless root also doesn't work. I've heard somewhere that locking bootloader could be a possible solution to that. But, how to lock it?
N910F + 7.1.1
Click to expand...
Click to collapse
First off, I am no expert at all on this matter. But maybe a different kernel, if ones even available. I haven't had the time to even test lineage out yet, so I'm not familiar as to whether their kernel is permissive or enforcing? But that possible might have something to do with it.
Maybe someone with more details can answer that for us?
Edit: wow, bro. My xda was all fudge up. It was not showing any of these replies that are here. I hope you got that solved. I thought that was a new post, as it showed 0 replies. Didn't mean to reply to old, answered question.
Hi!
I rooted my galaxy s7 edge that had stock version of android 7 (nougat) on it using this tutorial: http://www.droidviews.com/install-twrp-root-galaxy-s7-and-s7-edge-on-nougat-g935fxxu1dplt/. Now when I open built-in camera app it shows me a black screen for few seconds and then it says "Camera has stopped" and it offers me to "Open app again" and "send feedback" And it keeps happening over and over again.
Lemma: The reason is rooting.
Proof: Camera app worked perfectly. After I rooted my phone it started to crash like I described above. Then I tried to force quit camera app and delete it's cache/data. It did not help. After that I wiped entire cache partition. Still no help. After that I wiped all partitions except system. That did not work either. Then I re-flashed unmodified original stock ROM. Then camera worked perfectly again. Then again I rooted my phone the using tutorial I linked above. And again exactly the same issue. Camera app show black screen for few seconds and then crashes with exact same error message. ∎
Does anyone know fix for that? And why it happens? Is it some kind of samsung's anti-root thing that prevent camera fromworking on rooted phones or what?
Update [SOLUTION]:
In case someone else has same problem.
My solution was to skip restarts in TWRP steps. No restart between format and installing packages. Restart once when everything in TWRP part is done.
Root doesn't break your camera
I just Rooted my G935F that had Nougat as official firmware and had zero problems with the camera.
Sent from my SM-G935F using Tapatalk
I have international version of samsug with exynos CPU. Maybe this changes anything?
Root doesn't break your camera
Click to expand...
Click to collapse
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
I downloaded original firmware from here: https://www.sammobile.com/firmwares/database/SM-G935F/ (I chose baltic (only 1 occurrence in the table))
Maybe that specific tutorial I linked is bad one? Could anyone check that?
Rooted my G935F and no problems here for me.
I suggest you follow the tutorial here on xda and try again.
Could you post link to tutorial please? Then I could be sure I used the same tutorial as you did.
PS! Now I also noticed that with rooting I lost auto brightness adjusting and also manually changing brightness didnt do anything. Right now I am back on un-rooted rom because I need camera functionality to work. But would love to get it rooted. Is there any info on cf-auto-root and android 7 yet?
sysctl said:
Could you post link to tutorial please? Then I could be sure I used the same tutorial as you did.
PS! Now I also noticed that with rooting I lost auto brightness adjusting and also manually changing brightness didnt do anything. Right now I am back on un-rooted rom because I need camera functionality to work. But would love to get it rooted. Is there any info on cf-auto-root and android 7 yet?
Click to expand...
Click to collapse
A simple search here you'll find all you need. You are the only person I've ever read of that had camera problems like you've stated after Root. Again rooting won't break your camera.
I've Odin to stock literally hundreds of times testing Rom/Mods/themes as a tester for several teams from my s3 up to and including my G935F.
I've also flashed every Rom available for the G935F and the only ones with camera problems are the Lineage or AOSP Roms which more than likely are kernel related. Start here https://forum.xda-developers.com/announcement.php?a=81
Then this
Here's one
https://forum.xda-developers.com/showthread.php?t=3489011
sysctl said:
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Again rooting won't break your camera.
Click to expand...
Click to collapse
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
sysctl said:
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
Click to expand...
Click to collapse
Ok here is what you need to do.
Download a logcat app and get a logcat of it forceclosing.
I can't magically look in your device and see what, if anything is wrong.
As far as you saying you've searched well if you really did you would've found several tutorials.
How do I know?? Because I've used them myself.
It took me less than 5 minutes to root my new G935F using the TWRP Guide here on XDA
You seem to be the only one in hundreds that's claiming root broke your camera.
Provide a logcat in the Q&A and maybe a dev can help you.
sysctl said:
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
Click to expand...
Click to collapse
Sent from my SM-G935F using Tapatalk
You could try to reset your settings
Same issue on smg935w8 lost camera and screen brightness. Also can't mount micro sd... we're you able to fix? I thought it was a bad root then I re flashed and the issue came back...twrp 3.1.0 supersu 2.79 and no verity 5.1
---------- Post added at 10:15 PM ---------- Previous post was at 09:50 PM ----------
im re flashing stock and tomorrow ill redo twrp and super su and skip dm verity patch think that might be the issue as it worked before for me last week and i then messed up by turning dev mode off and disabling oem and when i reflashed after that i have been flashing the dm verity patch....
give that a try if your still having issues
had similar issue, my camera app keeps crashing, i went to settings, applications then cleared cache after stopping it, i hope that will fix your camera too
Gray.Fox said:
had similar issue, my camera app keeps crashing, i went to settings, applications then cleared cache after stopping it, i hope that will fix your camera too
Click to expand...
Click to collapse
Thanks I've tried clearing cache for everything no luck. I originally thought it was because I might have deleted a system app with titanium but when I reflashed it all (firmware,tarp,supersu,no small verity disable 5.1) I still had the issue.
Lastnight I wiped and flashed the entire firmware. Everything works. Tonight I'm goi g to try and only flash twrp then supersu as I only want root. Hopefully that fixes my issues.
OP have your issues been resolved?
I'll let you know once I get it working on mine and we'll get you sorted out. I believe it's something with the steps or order as I had root fine for a day then had to reflash due to messing around and didn't do it my original way and that caused my issues.
flashed twrp 3.1.0 from odin with auto reboot off.
then booted to twrp. swiped right to mount system,
wipe data(format data) type yes.
mount microsd as mtp copy supersu 2.79 over if its not already on you microsd card.
else just install it from zip
cleared cache/delvik
rebooted to system
log in and setup everything and restore
camera and auto brightness...stilll doesnt work.
ok so after multiple tries to fix this (flash stock) everything works,, root and it breaks tried clearing all cache in system and twrp no difference... then i loaded phone info and used the secret codes to find out that my camera firmware is not installed....so im trying Flashfire to reflash the AP only while injecting supersu and maintaining root.... it is just booting up.....and OMG!!!!it works!!!!
so....for some reason...firmware was corrupting..... no clue why tired multiple methods and nothing... and im not a noob either.....
what finallllllllly worked was.... flash your rom and get root how you would normally. camera/auto brightness/and mounting usb doesnt work....boot to twrp. get your ap md5 file on your internal storage
reboot to system,. get flashfire from playstore or chainfires website
install and then click the + select firmware and select the tar file
only install system....uncheck boot and cp
then in the everroot select injject supersu, preserve recovery
and flash.... it will start flshing and boot to syteem once done..
everything is working nice
finalllyyyy!!!!
hope this can atleast help OP
no clue why i was losing firmware on the flashes
@unit68 Tnx for sharing. This time I got camera and brightness adjustment work out of box. But if in any point of time I happen to need your tutorial, I'll give it a try and let you know.
I am not sure if it is by chance or not but what I did differently this time was:
1) I paid attention to step where it asked to disable auto reboot (can anyone explain why?)
Previously I thought it shouldnt matter so I kept auto reboot for convenience.
2) I did format data, install no-verity-opt-encrypt-5.0 and SuperSU-v2.79-201612051815 and wipe dalvik cache with out rebooting between (Anyone know if that matters?).
Previously I had done it: format - reboot - install no enc - wipe dalvik cache- reboot - install super su - wipe dalvik cache - reboot .
Now I did it format - intall no enc - install super su - wipe dalvik cache - reboot.
I'll see for few days if anything else comes up or if camera breaks down again. Btw @unit68 what happens when you try some bloatware remover that run with root access? Do you get rid of bloatware or not? I tried few of them such as no bloat for example. Some complain that uninstall failed some seem to uninstall the app but when they reload app the app is still there and it's also still in app menu. Just curious if you have the same same issue. And is it safe to delete apk file manually? Or would it cause phone to crash/boot loop? When I ran supersu it complained about knox and asked me to disable it but it never managed to (however root checker tells me I am root). Maybe knox is protecting bloatware? Any ideas?
Flash your able too get it working! It was soooo frustrating. So for Knox supersu asks to disable then seems to hang so I go about my business reopen supersu it'll ask again and then is successful.
To remove bloat I normally just go to titanium and remove the ones I don't want
No issues on that and all my apps that require root work fine (titanium,adaway, flashfire)
This time disabling knox worked too... It turned out that all 3 apps that I used were note able to remove bloatware. App you named worked and also ROM toolbox lite works.
Btw when I google bloatware, the lists are incomplete.... Do you happen to know list of apps that must not be uninstalled? I guess white list would be better idea than black list.
Is installing/uninstalling app same as removing/adding apk files? So that I could cut and paste everything expect file manager and launcher to usb memory stick and then start adding required apps back one by one?
ive seen some samsung debloating software around. i honestly just remove stuff based on manually debloating for last fewyears. if i dont know what theapp is for i google it to see if its ok to remove. normally i remove samsung knox, few other samsung apps, some google apps (music, games, videio), briefings some edge panels, live wallpaper, and carrier branding apps(for me rogers) stuff like that. if you are going to i recommend you do a backup first as it ccan mess up your phone if you uninstall an important app. . also once your do uninstall you need to reboot ... the paid version of titanium allows you to freeze applications so you can try that first before removing it.
I had the exact same issues: camera crashing, blue light filter not working, brightness not working, etc. It was supersu. You need the right version of supersu, it's 2.79 SR0. It's checksum is f4ecbf5814215bf569ff3324fc1c91f5
ScreAmeR01 said:
I had the exact same issues: camera crashing, blue light filter not working, brightness not working, etc. It was supersu. You need the right version of supersu, it's 2.79 SR0. It's checksum is f4ecbf5814215bf569ff3324fc1c91f5
Click to expand...
Click to collapse
Interesting..ill check that if I need to to Flash. I have 2.79 but maybe I grabbed an old version or a beta. Mine says 20161205 I think it may have been sr3
Edit _ just checked I grabbed sr0 the stable release from 20161215 not the sr3 beta
Maybe it was corrupt when I flashed
Hello all,
today I would like to first tell about my successfull installation of 2 ROMs and ask a important question.
1. Successfull ROM installation
Using the guides from loquenz at https://www.chinamobilemag.de/tutorials/nubia-z17-twrp-root-google-play.html and from furiousjay at https://geekaxe.com/root-nubia-z17-unlock-bootloader-flash-twrp-recovery/ I successfully flahed the TWRP and installed the ....CNCommon_V2.39 and the ...CNCommon_V2.44 ROm and upgrade to it (!).
It alll went well and the phone is running.
I then installed the GAPPS onto it and it went fiine too, but I am still having issues (see later).
2. Question 1 FIRMWARE:
When I run on my V2.44 level of firmware the phone tells me that there is the V2.48 level of firmware waiting to be installed. I downloaded (in the phone, not TWRP) it and have it install. It rebootet. But after reboot it ended up in TWRP. There i said reboot and rebooted my phone. I was able to get into the phone but there is a little one to the upper right at the settings icon which brings me to system update and again downloading the same update.
I can install it again, but still end up in TWRP and after rebooting the system, with the update (2.48) not installed. And the system telling me that there is an update waiting for me.
This goes on and on. I have not found a way to end this circle.
Q: Is there a way to hvae a reboot NOT end up in TWRP? Or is this not the culprit?
Any ideas of what went wqrong and what I can do?
3. Question 2 GAPPS:
(this is separate from the above)
I also installed the Full_Dynamic_GApps-7.1.x-20170121.zip package via TWRP.
The GAPPS worked fine, but then started to aks me for reloging into my account (and didn'T let me).
Playing the filght mode trick helped, but only for a while, then the same again, that I needed to log in to my account.
Any ideas here? How can I uninstall the GAPPS and reinstall another package?
4. Question3 Permissions:
The phone didn't let me remove my Google account, saying that my adminsitrator wouldn't allow this!! How can I remove my Google account and re-add it? Which permission do I need to change and where?
Thanks a lot in advance for any light you can shed on this!
Thomas
I forgot to say that this successful installation means that you can go to a stock ROM and will get OTAs for the phone. I received the V2.48 via OTA!!
Not sure about qn1, but:
Qn2 GApps - when I tried to flash different versions from Open GApps, they automatically removed the old one as part of the flashing process. I think people seem to find the 'full' version works best.
Qn3 - I removed my Google account on the computer, I think it's somewhere on your Google account where you manage your devices/log-ins
tsiebold said:
Hello all,
today I would like to first tell about my successfull installation of 2 ROMs and ask a important question.
1. Successfull ROM installation
Using the guides from loquenz at https://www.chinamobilemag.de/tutorials/nubia-z17-twrp-root-google-play.html and from furiousjay at https://geekaxe.com/root-nubia-z17-unlock-bootloader-flash-twrp-recovery/ I successfully flahed the TWRP and installed the ....CNCommon_V2.39 and the ...CNCommon_V2.44 ROm and upgrade to it (!).
It alll went well and the phone is running.
I then installed the GAPPS onto it and it went fiine too, but I am still having issues (see later).
2. Question 1 FIRMWARE:
When I run on my V2.44 level of firmware the phone tells me that there is the V2.48 level of firmware waiting to be installed. I downloaded (in the phone, not TWRP) it and have it install. It rebootet. But after reboot it ended up in TWRP. There i said reboot and rebooted my phone. I was able to get into the phone but there is a little one to the upper right at the settings icon which brings me to system update and again downloading the same update.
I can install it again, but still end up in TWRP and after rebooting the system, with the update (2.48) not installed. And the system telling me that there is an update waiting for me.
This goes on and on. I have not found a way to end this circle.
Q: Is there a way to hvae a reboot NOT end up in TWRP? Or is this not the culprit?
Any ideas of what went wqrong and what I can do?
3. Question 2 GAPPS:
(this is separate from the above)
I also installed the Full_Dynamic_GApps-7.1.x-20170121.zip package via TWRP.
The GAPPS worked fine, but then started to aks me for reloging into my account (and didn'T let me).
Playing the filght mode trick helped, but only for a while, then the same again, that I needed to log in to my account.
Any ideas here? How can I uninstall the GAPPS and reinstall another package?
4. Question3 Permissions:
The phone didn't let me remove my Google account, saying that my adminsitrator wouldn't allow this!! How can I remove my Google account and re-add it? Which permission do I need to change and where?
Thanks a lot in advance for any light you can shed on this!
Thomas
Click to expand...
Click to collapse
1. you better download the China ROM v2.44 and install it via TWRP, dont forget to wipe chace and dalvik. It will make your phone like new
2. Go to Update and update your phone to v. 2.48
3. Unlock Bootloader, instal TWRP and root your devices using TWRP
4. Install Gapps Full
5. Wipe chace / Dalvik again.
So far, Google will running but with some issues like sometimes you need to re-authentucating google account again by go to flight mode by several minutes, gmail, photos and some other google apps. This is what we shoudl overcome while waiting for international rom
How do you prevent Twrp from jumping in (point 1 and 2) at the Reboot for the update?
I do have the China Rom V2.44 installed as explained in my post.
tsiebold said:
How do you prevent Twrp from jumping in (point 1 and 2) at the Reboot for the update?
I do have the China Rom V2.44 installed as explained in my post.
Click to expand...
Click to collapse
This is what I can suggest:
1. Do a NANDROID backup
2. Wipe all and flash 2.44
3. Update via OTA to 2.48
4. Install TWRP, Root and Gapps
5. Restore your data partition
Please do it at your own risk. I have not tried it yet.
OK, one additional day of trying...
I have reapplied the V2.44 update ROM through >setting>system update>local update
The following reboot did NOT stop in TWRP.
When the system was up it told me about the V2.48 update being available, downloaded it and I applied it normally (not using local update).
The following reboot also did not stop in TWRP but went through to the upgrade process.
So now I am at V2.48.
As said in other entries I did not (yet) manage to get Google Playstore to run.
I did not apply any Google distribution.
My phone has now updated to V2.54 via the OTA update system.
GAAPS still do not work, but I have personalized my phone to not use Google apps when the do not work, but use Nubia apps.
The support people in Germany and India were not helpful.. They refused saying that the phone is "only" (!!) sold in China.
I wonder whether we will see an international ROM at all, especially with the ZTE branch being sold.
tsiebold said:
My phone has now updated to V2.54 via the OTA update system.
GAAPS still do not work, but I have personalized my phone to not use Google apps when the do not work, but use Nubia apps.
The support people in Germany and India were not helpful.. They refused saying that the phone is "only" (!!) sold in China.
I wonder whether we will see an international ROM at all, especially with the ZTE branch being sold.
Click to expand...
Click to collapse
Working in a software company, I can understand why the Indian or German people would not help. I do less technical support than I did in previous years but I already had enough customers on my own so it would have been very problematic if I also had to answer to foreign customers (that and also the fact that a license purchased in foreign countries does not give us a dime so we are not inclined to help customers from foreign offices ).
Regarding the global firmware, the more time passes, the less I feel we're gonna have one. There are only speculations about an Indian release in September but nothing official. The phone is still on my wait list but it may not be the case anymore in October or November.
Somehow I have received malware on my stock, untouched G5 plus. I've performed a wipe of user data and performed factory reset from the boot option (power and volume key at startup) Still, the malware exists and redirects webpages to pop-ups even with fresh install.
Does anyone have an untouched factory ROM, that will receive all OTA updates ? Lenovo will not provide! Help very much appreciated.
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738 here
vantastic415 said:
Somehow I have received malware on my stock, untouched G5 plus. I've performed a wipe of user data and performed factory reset from the boot option (power and volume key at startup) Still, the malware exists and redirects webpages to pop-ups even with fresh install.
Does anyone have an untouched factory ROM, that will receive all OTA updates ? Lenovo will not provide! Help very much appreciated.
Click to expand...
Click to collapse
If you have a stock, untouched Moto G5 then there is something else going on... It is not possible for malware to infect the system after a factory reset, unless it is coming from an app you are reinstalling or your SD card.
acejavelin said:
If you have a stock, untouched Moto G5 then there is something else going on... It is not possible for malware to infect the system after a factory reset, unless it is coming from an app you are reinstalling or your SD card.
Click to expand...
Click to collapse
That's not quite true. There have been a number of vulnerabilities (like the Dirty Cow one) that can be used to get root, and then cause havoc on your system. In general, if you just get regular apps from the Play Store you'll be fine, but if you get external sources, who the hell knows.
You might want to contact Motorola support and see if they have steps. I would think flashing the stock rom would solve it.
I also didn't believe this to be possible, but unfortunately that's the situation.
I barely even install apps on my phone, or use my phone for much. I'm one of those weird people that stay largely disconnected from tech. I have whatsapp, color note, good budget, swype, and Amazon music. That's it. All from the play store.
The virus had to originate from the web. Occasionally I click on ads or "news" with interesting looking content. You know, the sort with 20 pages to click through and ads everywhere. I know better, but that's where it came from.
First virus in 31 years of computing. I guess now I get to learn about rooting Android and flashing ROMs. :good:
Thank you for the replies and link to a clean ROM. Very appreciated!
Edit: No SD card in the phone, and I've factory reset from within Android, and during boot. Erase cache, data, everything. Virus persists. =( oh well, no biggie now.
You have not got the dodgy whatsapp, should be removed from playstore now, but that was a advertising machine.
Perhaps I'm not understanding. In the provided link I don't see many ROM, just 4.
I have the standard G5 Plus (non Amazon) on T-Mobile. Model: XT1687. Build number NPN25.137-83. Any idea where I could get a stock ROM for this and get my phone back to virus free?
I've searched but can only come up with a TWRP flashable ROM, and I've no idea what TWRP means, but I see that for some reason it doesn't receive OTA updates, so that's unfortunately a no-go.
Thanks so much for the help! You all rock.
vantastic415 said:
Perhaps I'm not understanding. In the provided link I don't see many ROM, just 4.
I have the standard G5 Plus (non Amazon) on T-Mobile. Model: XT1687. Build number NPN25.137-83. Any idea where I could get a stock ROM for this and get my phone back to virus free?
I've searched but can only come up with a TWRP flashable ROM, and I've no idea what TWRP means, but I see that for some reason it doesn't receive OTA updates, so that's unfortunately a no-go.
Thanks so much for the help! You all rock.
Click to expand...
Click to collapse
If your phone is stock and with a locked bootloader, you need to contact Lenovo/Moto customer support and send it in for repair or replacement.
If your bootloader is unlocked, your warranty is void and you might as well learn about TWRP, root, and flashing ROMs.
The possibility of someone to code a virus that persists through complete flashing of the stock rom is not very likely... When you flash stock rom (correctly, via fastboot) you are completely wiping your phone and either erasing (formatting) each partition or flashing that partition back to its original factory image. If you are experiencing webpage redirects after flashing, it is far more likely that you are connecting to a network that has been in some way compromised. It is not uncommon for malware to redirect traffic in a network, and trivial to implement such redirections if you have privileged access. Think about how a business/hotel WiFi network redirects all traffic to their login page when you try to connect to a website. Just my 2 cents, but it's highly unlikely that someone targeted you with such a specific, sophisticated virus that it somehow found a way to survive when the entire phone is flashed, only to redirect you to ad sites.
---------- Post added at 06:15 AM ---------- Previous post was at 06:11 AM ----------
As for flashing, if you really want to return to stock you should relash stock images with fastboot instead of Twrp images. This will COMPLETELY wipe your device (user data, etc). When I read your first post I had thought you had already done this. If not, it should fix your problem. Here is a guide with links to firmware images: https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
I have a Samsung Galaxy Tab A - SM-P580. After trashing everything and starting from scratch, I was finally was able to get Lineage installed- lineage-19.1-20220824-UNOFFICIAL-gtanotexlwifi. When I tried to install MindTheGapps-12.1.0-arm64-20220605_112439, I was greeted with an error (Updater process ended with Error: 1. Error installing zip file etc. etc.). I had originally installed Lineage 19 and had rebooted and then found out app the Google apps install. I initially installed a version of NikGapps. I performed a factory reset from with the OS and reinstalled Lineage and then MindTheGapps, before booting into the OS and got the same error when installing MindTheGapps. I noticed that even after the factory reset from within the OS, it still retained my Google account information. And still at this point, even though I was able to connect to the Internet on my WiFi, I could not access the Internet at all. HELP - before this tablet get skimmed across the water like a flat rock. Thank you!!
Why haven't you posted this in my thread? Barely anyone would see this here. There's a greater chance someone could've helped you in my thread.
The factory reset function in Android's settings might not work, which I'm guessing it wouldn't have in your case. It's untested. Factory resets should be done in recovery.
Can't really help with Google app issues since I don't use them, but you should do a factory reset within recovery, format system, reinstall my build, and then install NikGapps (use the core package by the way, if what you have is a heavier package).
TALUAtXDA said:
Why haven't you posted this in my thread? Barely anyone would see this here. There's a greater chance someone could've helped you in my thread.
The factory reset function in Android's settings might not work, which I'm guessing it wouldn't have in your case. It's untested. Factory resets should be done in recovery.
Can't really help with Google app issues since I don't use them, but you should do a factory reset within recovery, format system, reinstall my build, and then install NikGapps (use the core package by the way, if what you have is a heavier package).
Click to expand...
Click to collapse
Thank you for the input. I've made some progress and am closing to a working tablet.
I posted in your thread a little while ago. Thanks again!