Related
Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This
Have you done a factory reset? that solves most problems.
jazf78 said:
Hi,
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
Click to expand...
Click to collapse
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dialer doesn't filters out contacts I decided to not show on the Contact app.
-(Not really a MM issue, but instead related to Cyanogenmod.) No call recording (another essential feature for me)!
The phone part of our "smart" devices is becoming worse and even more worse every update . Maybe it's time to come back to a Nokia 3310 or a Qtek 9090 like in the good old days
jazf78 said:
Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This
Click to expand...
Click to collapse
If your using Indian XT1550 please take TWRP backup and give me the download link I need it very badly.
ethaniel said:
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dial
no idea what this all meant. plz stay on topic, thanks
Click to expand...
Click to collapse
Nazeerchauhan said:
If your using Indian XT1550 please take TWRP backup and give me the download link I need it very badly.
Click to expand...
Click to collapse
im from México.
eemgee said:
Have you done a factory reset? that solves most problems.
Click to expand...
Click to collapse
i haven´t but i read somewhere else that a factory reset would not downgrade android version. since it also changed its firmware..
dont know if thats true or false.. did you or anyone reading this has actually done a factory reset and their android device downgraded itself? need to be sure, dont want to waste time, backing **** up, doing factory reset
only to notice it still marshmallow and then redownload and restore everything so i can use the phone and still have the problem.
thanks
jazf78 said:
ethaniel said:
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dial
no idea what this all meant. plz stay on topic, thanks
Click to expand...
Click to collapse
I wasn't so much off-topic, it was something related to the thread title (Marshmallow piece of crap), but OK! I respect your statement. Last reply I make on this thread.
Hope tomorrow will be a better and happier day for you
Click to expand...
Click to collapse
jazf78 said:
Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This
Click to expand...
Click to collapse
I think downgrading will be a more difficult task than a factory reset. A factory reset should clear all your issues.
When an app asks for permissions, Allow and Deny options show up (regardless if for storage, or camera, etc.) but the allow button does not work. Deny works fine. So far i have unlocked the bootloader via Huawei website method (i guess you call that official) and flashed twrp. I have not rooted the phone yet (getting to that, but one problem at a time) and this is the first one.
I also saw someone else ask, but with now answer. Is there a way to get rid of the splash scren about the phone being unlocked and not trustable, press power button again to boot?
Do you have an special theme activated? Use the standard theme and try again
My 1st question to you is... when the window prompts, do you flag the option "don't ask to me again" or not? Because if yes, the only option avalaible becomes the "deny" one. This mechanism confused me too some time ago, when i wasn't understanding why it was blacked out; Android takes your flag as an "what a bore, just shut up and go **** ya' self leavin' me alone" answer, so it automatically deactivate the possibility to let it pass even one more time. If you didn't checked the flag, i have another question for you. Did you maybe recently made an update OTA, or with an update package found online? If the 2nd answer is what u've done, do a check for being sure that you have updated the phone with the correct package model. (BLN-21, BLN-22, ecc.) If neither this is your case, begin to tell us something more 'bout your phone configuration and start to think to backup your data and do a factory reset for eliminate this weird issue.
For the question of yours about the Nag screen (the splash one, for being clear) at the moment there is nothing that we can do to avoid it to pop out; just skip it pressing immediately the power button, is the best advice that i can do so far
I'll attempt to answer all these at once since I just got home from work. I wouldn't believe rooting the phone would cause this issue, but the problem happened before i unlocked the bootloader so I think that rules that out. I do not use a special theme, but I do use squarehome launcher for my phone, not the standard android launcher. Problem there is, the problem occurs with either launcher being active. And theme wise, I have a 3-d live aquarium for a background (which if turned off and just a static wallpaper, the same behavior occurs). As far as the phone update goes, it was an OTA update from 6 to 7, so still using stock, nothing sideloaded or flashed (yet). My data is all backed up via My backup pro, and doing a full backup with TWRP onto OTG is not a problem. I prefer not throwing in the towel, since setting up squarehome perfectly is a pain in the ass, but if it has to happen, it is better than manually setting permissions for every app that needs them. Not sure what a screenshot would do, think of any app asking for permission to use phone storage, both the allow button and the deny button visible (in white, nothing grey) and allow doesn't respond where deny responds fine. and then i have to go in manually and grant the permission after the fact. I suppose I could just root my phone and give that a whirl, seems some bloatware needs to be removed anyway, and i have the SU sitting on my hard drive already. Thanx for the responses, and let me know what you may have come up with before I just factory reset it which as mentioned, I am dreading doing.
Rommco05 said:
Hi, so you have unlocked bootloader but not rooted? This is maybe problem, you need to have rooted phone if you have unlocked bootloader for fully using phone. Can you post some screeshots?
Click to expand...
Click to collapse
Well, I didn't think that would be the answer, but you, sir were right. I rooted my phone and it seemed to have fixed the problem. I don't believe I made any other change whatsoever. Thank you very much. Glad I tried it anyway as you suggested even though I didn't think it would be the answer. I am not above saying thank you, and I was wrong. Kudos. Maybe this will help someone else. Good thing is, I planned on rooting it anyway, and you just kicked me in the pants to do it.
Rooted but allow button is still not activated
Hello guys,
I wanted to activate app twin so I rooted my phone BLN-L21 android 7.0
Allow button still deactivated.
Also the boot screen that asks to press power button still exist.
I noticed that if I activate whatsapp twin it won't work simultaneously .
I.e : when you open whatsapp you get all missed calles & messeges.
Also I was able to download themes through themes app ,but now it just views the local themes.
Note: superSu is installed.
Any help will be appreciated.
Thank you
Well, I think this is not related to OP (or at least partially), but when unlocking bootloader after setting up SD card as the default storage can break some things, like default themes.
Try to restore your firmware, and then unlock the bootloader.
If successful, you can now set up SD card as default storage.
jackmeat said:
When an app asks for permissions, Allow and Deny options show up (regardless if for storage, or camera, etc.) but the allow button does not work. Deny works fine. So far i have unlocked the bootloader via Huawei website method (i guess you call that official) and flashed twrp. I have not rooted the phone yet (getting to that, but one problem at a time) and this is the first one.
I also saw someone else ask, but with now answer. Is there a way to get rid of the splash scren about the phone being unlocked and not trustable, press power button again to boot?
Click to expand...
Click to collapse
Its happened to me before i just wiped the phone. I even sometimes cant click install when installing an apk unless i lock and unlock the screen.
I have reclaimed ownership of my phones 'bixby' button with an app called bxActions and it works pretty nice, however the app claims it can work even better if I grant it permissions by running something on my PC through USB. It sounds sketchy.. Does anyone know what happens when you do it?
I'm mainly concerned about permanently locking it into a bxActions button, and perhaps even voiding warranty (does this count as rooting?).
Is it safe/worth it?
It is safe for you to do that, it doesn't count as rooting since it's only executing adb commands. I don't know about warranty though if you ever have to send your phone away for warranty I'd delete the app and the folder just in case
Ok, so nothing is permanent or invasive enough for Samsung to have a fit over it?
In that case ill just do it. Because frik bixby.
Just do it. Its ok
Sokonomi said:
I have reclaimed ownership of my phones 'bixby' button with an app called bxActions and it works pretty nice, however the app claims it can work even better if I grant it permissions by running something on my PC through USB. It sounds sketchy.. Does anyone know what happens when you do it?
I'm mainly concerned about permanently locking it into a bxActions button, and perhaps even voiding warranty (does this count as rooting?).
Is it safe/worth it?
Click to expand...
Click to collapse
I did it long time ago. Using all samsung features happily... Infact have provided many other apps spl permissions... doesn't break anything...
omega_warrior said:
I did it long time ago. Using all samsung features happily... Infact have provided many other apps spl permissions... doesn't break anything...
Click to expand...
Click to collapse
Can you tell me some other mods for the s8 without root? Pls
I just ordered a Pixel 3a and I was gone for a while from the world of Google phones (since Nexus 4).
I know Magisk hides any trace of root and unlocked bootloader, but is there any disadvantages unique to Pixel devices when rooting, like disabled features or is hiding good enough that there won't be any difference? Just to be sure
Artim_96 said:
I just ordered a Pixel 3a and I was gone for a while from the world of Google phones (since Nexus 4).
I know Magisk hides any trace of root and unlocked bootloader, but is there any disadvantages when rooting, like disabled features or is hiding good enough that there won't be any difference? Just to be sure
Click to expand...
Click to collapse
Nothing as far as i know.
Unstroofy said:
Nothing as far as i know.
Click to expand...
Click to collapse
That sounds great. Wasn't sure if they might have done something through the Titan M or else
Rooting means unlocking your bootloader. This makes your phone at greater risk of being compromised - especially if someone has physical access to your phone (ie you lost it and someone finds it). Therefore you don't want to leave your bootloader unlocked if you have any sort of sensitive, illegal, or secret information on your phone. That's the #1 issue you have to live with. Of course for 99% of the population, there isn't anything really sensitive on their phones.
Google Pay can be hard to get working when rooted. There are ways to make it work, but it's always a cat and mouse game with Google and it may not always work in the future if Google changes something until the developers can catch up. If you can't live without Google Pay, rooting may not be the best choice for you.
There are other apps that can be temperamental when rooted - usually finance apps and some games (because they don't want players cheating). However, the Magisk hide functionality usually works with most of these apps now.
For me, the added functionality that being rooted brings (via modules and apps) is far better than the potential issues.
sic0048 said:
Rooting means unlocking your bootloader. This makes your phone at greater risk of being compromised - especially if someone has physical access to your phone (ie you lost it and someone finds it). Therefore you don't want to leave your bootloader unlocked if you have any sort of sensitive, illegal, or secret information on your phone. That's the #1 issue you have to live with. Of course for 99% of the population, there isn't anything really sensitive on their phones.
Google Pay can be hard to get working when rooted. There are ways to make it work, but it's always a cat and mouse game with Google and it may not always work in the future if Google changes something until the developers can catch up. If you can't live without Google Pay, rooting may not be the best choice for you.
There are other apps that can be temperamental when rooted - usually finance apps and some games (because they don't want players cheating). However, the Magisk hide functionality usually works with most of these apps now.
For me, the added functionality that being rooted brings (via modules and apps) is far better than the potential issues.
Click to expand...
Click to collapse
Tl;dr: nothing new. And never had a problem with any apps. Magisk Hide is working well enough, deleting apps data always works as last resort. And on custom ROMs just use MagiskHide Props Config. And if you are concerned about your data, just use the lockscreen passport as bootup protection. Then it's simply impossible to get to the data through that "insecurity", no matter what you do. And since fingerprint readers a more complex password isn't a problem.
Artim_96 said:
Tl;dr: nothing new. And never had a problem with any apps. Magisk Hide is working well enough, deleting apps data always works as last resort. And on custom ROMs just use MagiskHide Props Config. And if you are concerned about your data, just use the lockscreen passport as bootup protection. Then it's simply impossible to get to the data through that "insecurity", no matter what you do. And since fingerprint readers a more complex password isn't a problem.
Click to expand...
Click to collapse
I'm not sure exactly what you mean by lock screen passport. Can you share some more details?
The insecurity comes from the fact that a person that has physical access to your phone can simply turn the phone off and then start it and hold the power and volume up buttons. This will boot the device into the bootloader. Because the bootloader is unlocked, it allows that person the ability to flash anything and gives that person access to anything they want. That super secure lockscreen password or fingerprint won't help keep them out and does nothing but give users a false sense of security.
When the FBI paid a 1 million dollar bounty to someone to access an iPhone, they were paying someone to get around the bootloader. If you unlock your bootloader, you give this access right from the beginning - for free, and without any effort required.
I'm not trying to be argumentative either. You asked what the drawbacks to rooting were and I was simply trying to give a thorough answer. It's up to the individual user to decide if the the positives of unlocking the bootloader and rooting outweigh the negatives. If you look at my signature, you can see what side of the fence I fall on.
sic0048 said:
I'm not sure exactly what you mean by lock screen passport. Can you share some more details?
The insecurity comes from the fact that a person that has physical access to your phone can simply turn the phone off and then start it and hold the power and volume up buttons. This will boot the device into the bootloader. Because the bootloader is unlocked, it allows that person the ability to flash anything they want. That super secure lockscreen password or fingerprint won't help keep them out.
Again, I'm not familiar with this lockscreen passport you mention, so perhaps there is a way to secure the phone that I am not aware of.
I'm not trying to be argumentative either. You asked what the drawbacks to rooting were and I am simply trying to give an thorough answer. It's up to the individual user to decide if the the positives or rooting and unlocking the bootloader outweigh the negatives. If you look at my signature, you can see what side of the fence I fall on.
Click to expand...
Click to collapse
Was a typo,I meant lockscreen password. Android should ask you, if you set up a lock method other than Swipe to unlock, if you want to be asked for it on bootup.
So no matter what you are able to flash through an unlocked bootloader, /data and with it anything that could be relevant stays encrypted until you enter the lockscreen pin/pattern/password, no matter if you do this on the screen that will interrupt bootup after a few seconds or in TWRP. So it doesn't matter what you could come up flashing, as long as you don't find a way to extract the encryption key from the secure storage either in Titan M or any ARM processor, there is no way to get your hands on user data. The only thing you can do is simply wipe /data. Then you can start up new, but the users data will be gone.
And no, I never asked for disadvantages of root itself since there are little to none, I just asked for Pixel unique stuff since Google always adds stuff that other OEMs won't use for years to come.
Artim_96 said:
And no, I never asked for disadvantages of root itself since there are little to none, I just asked for Pixel unique stuff since Google always adds stuff that other OEMs won't use for years to come.
Click to expand...
Click to collapse
I misunderstood your initial post then, but the title of the thread says, "Disadvantages of rooting?"
sic0048 said:
I misunderstood your initial post then, but the title of the thread says, "Disadvantages of rooting?"
Click to expand...
Click to collapse
Fixed that. Hope the text is more clear now.
But could you reproduce what I explained? Because I would be very surprised if that was unique to Motorola and not AOSP
Hello everyone. I would like to know if anyone experienced this, and if anyone has a solution (or at least an idea why).
The power button of my Samsung Galaxy A7 (2018) (SM-A750G) phone does not work at unlocking the screen (if it works in the rest of the functions such as opening the shutdown menu, entering recovery, etc.) when I am using stock firmware, but it works perfectly when using a GSI or any other custom OS.
Do you have any idea what could happen? It should be noted that this happened to me when my phone had the stock firmware and I had never modified my equipment at all... It just happened suddenly and for that reason I switched to a GSI. But now I would like to use the stock firmware, but I will not be able to do it with this "bug".
Thanks 4 the help
You mean unlocking or just turning the screen on an unlocked phone?
The app DoubleTap does away with using any buttons to turn the screen on/off. Simply 2x tap it. https://play.google.com/store/apps/...apk&pcampaignid=APPU_1_oD7zX7-SMMvesAWsh5_ADA
blackhawk said:
You mean unlocking or just turning the screen on an unlocked phone?
The app DoubleTap does away with using any buttons to turn the screen on/off. Simply 2x tap it. https://play.google.com/store/apps/details?id=com.vinance.lockdown&hl=en_US&gl=US&referrer=utm_source=google&utm_medium=organic&utm_term=double+tap+apk&pcampaignid=APPU_1_oD7zX7-SMMvesAWsh5_ADA
Click to expand...
Click to collapse
I mean turning on a phone screen. Since if it allows me to unlock it, but not turn it on.
P.S: I did not know the app you mention (it did not occur to me to look for something like that XD) I will try it, thanks for the link
gsosacristian said:
I mean turning on a phone screen. Since if it allows me to unlock it, but not turn it on.
P.S: I did not know the app you mention (it did not occur to me to look for something like that XD) I will try it, thanks for the link
Click to expand...
Click to collapse
That's strange. Have you tried remapping the button? Are there options to do so in settings?
Possibly another 3rd party apk remapped without you being aware of it?
I been using this app for over a year. To spite the ad warnings, it has none. Uses almost zero battery, never connects with the internet and is rock solid stable. Saves button life just keep the screen pointed away from your flesh when in your pocket to avoid accidentally taps.
Note: I never gave it administrator privileges as I never use a lock screen. So not sure about its behavior in that mode of operation.
blackhawk said:
That's strange. Have you tried remapping the button? Are there options to do so in settings?
Possibly another 3rd party apk remapped without you being aware of it?
I been using this app for over a year. To spite the ad warnings, it has none. Uses almost zero battery, never connects with the internet and is rock solid stable. Saves button life just keep the screen pointed away from your flesh when in your pocket to avoid accidentally taps.
Note: I never gave it administrator privileges as I never use a lock screen. So not sure about its behavior in that mode of operation.
Click to expand...
Click to collapse
I tried the app a few moments ago and it seems to work fine, the flesh thing is apparently configurable (assign the volume key, which is the most similar).
Regarding the mapping or 3rd party apks using the button, I see it almost impossible, not only because I don't use any app of this type (that reassigns keys) but in completely clean installations of stock firmware this happens to me (and I don't have any option key remapping that I know of).
It's very weird, at least for me. Because not only does it "break" to unlock, but it is only with stock firmware and even if I change the kernel (I tried using the quantum kernel) the key does not work when turning on the screen. But with the GSI it works without problems.
I even googled questions related to Always in display, power or something similar and nothing, there seems to be no conflicts.
gsosacristian said:
I tried the app a few moments ago and it seems to work fine, the flesh thing is apparently configurable (assign the volume key, which is the most similar).
Regarding the mapping or 3rd party apks using the button, I see it almost impossible, not only because I don't use any app of this type (that reassigns keys) but in completely clean installations of stock firmware this happens to me (and I don't have any option key remapping that I know of).
It's very weird, at least for me. Because not only does it "break" to unlock, but it is only with stock firmware and even if I change the kernel (I tried using the quantum kernel) the key does not work when turning on the screen. But with the GSI it works without problems.
I even googled questions related to Always in display, power or something similar and nothing, there seems to be no conflicts.
Click to expand...
Click to collapse
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
blackhawk said:
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
Click to expand...
Click to collapse
hehe, if it is true that there are really hidden things XD
Anyway, I am testing this app and if I see that it works I will be encouraged to install the stock firmware and by the way I will try to dig deep into the configuration in search of an option that I have overlooked
blackhawk said:
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
Click to expand...
Click to collapse
Update:
I have installed the stock firmware and used the app you recommended, but no results: / The same thing keeps happening.
I have checked the accessibility options and there is nothing blocking the button :O
gsosacristian said:
Update:
I have installed the stock firmware and used the app you recommended, but no results: / The same thing keeps happening.
I have checked the accessibility options and there is nothing blocking the button :O
Click to expand...
Click to collapse
You enabled the appropriate buttons in it's settings?
I'm running Pie; it may not be compatible with 10 and up because of the overlay crap.
blackhawk said:
You enabled the appropriate buttons in it's settings?
I'm running Pie; it may not be compatible with 10 and up because of the overlay crap.
Click to expand...
Click to collapse
Oh! There is the problem, the firmware is Android 10
Bad luck for me, it will be time to return to a GSI momentarily XD
gsosacristian said:
Oh! There is the problem, the firmware is Android 10
Bad luck for me, it will be time to return to a GSI momentarily XD
Click to expand...
Click to collapse
Can't verify that but suspect it... Q sucks.
Lol, Google wants to protect you... I feel safer already. Not.
gsosacristian said:
Hello everyone. I would like to know if anyone experienced this, and if anyone has a solution (or at least an idea why).
The power button of my Samsung Galaxy A7 (2018) (SM-A750G) phone does not work at unlocking the screen (if it works in the rest of the functions such as opening the shutdown menu, entering recovery, etc.) when I am using stock firmware, but it works perfectly when using a GSI or any other custom OS.
Do you have any idea what could happen? It should be noted that this happened to me when my phone had the stock firmware and I had never modified my equipment at all... It just happened suddenly and for that reason I switched to a GSI. But now I would like to use the stock firmware, but I will not be able to do it with this "bug".
Thanks 4 the help
Click to expand...
Click to collapse
It seems like I have a similar problem. Do you have any recommendations ROM for SM - A750GN?
droidz94 said:
It seems like I have a similar problem. Do you have any recommendations ROM for SM - A750GN?
Click to expand...
Click to collapse
Personally, the one that I liked the most (and the one that works best) is the Google official (Android 10): https://developer.android.com/topic/generic-system-image/releases But one problem is that it is very outdated.
Anyway, here is a list of some GSIs that you can check and test which one works on your device: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And here is a tutorial that worked well for me to install GSI: https://forum.xda-developers.com/t/guide-workings-gsi-best-treble-gsi-roms-for-a7-2018.4069121/
gsosacristian said:
Personally, the one that I liked the most (and the one that works best) is the Google official (Android 10): https://developer.android.com/topic/generic-system-image/releases But one problem is that it is very outdated.
Anyway, here is a list of some GSIs that you can check and test which one works on your device: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And here is a tutorial that worked well for me to install GSI: https://forum.xda-developers.com/t/guide-workings-gsi-best-treble-gsi-roms-for-a7-2018.4069121/
Click to expand...
Click to collapse
Thanks! I'll try that
EXACTLY same problem here. I will not repet your words, I'll just say you described EXACTLY what is happening with my phone, a Galaxy A7 2018 (128GB RAM, Brazilian model - A750G/DS).
I can confirm that:
1 - Problem of screen never turning on after being turned off for the first time happens at all stock ROMs. Tried at android 10, downgraded to 9, couldn't downgrade to 8 because odin would not write the image, but the problem persisted on ALL stock ROMs up untill now.
2 - Problem DOES NOT happen at the TWRP recovery. Flashed TWRP just now, so I can flash a GSI, and I can turn the screen on or off as many times as I wish at TWRP screen, without any problem.
These informations corroborate, almost without a shadow of doubt, the idea that this is actually a software problem, not a hardware one. I'm gonna flash the google 10 GSI now, with quantum kernel V3 (seems to be a requirement, I would like to make as litle changes as possible) and post the results.
Having a hard time installing the GSI, gets stuck at bootloop all athe time...
joaodalvi said:
Having a hard time installing the GSI, gets stuck at bootloop all athe time...
Click to expand...
Click to collapse
[GUIDE][A-ONLY][A750x] Guide on How to flash GSI (Updated: 10.06.2019)
I'm not responsible for whatever damage this could possibly cause to your device. If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal Welcome to GSI For Galaxy A7 2018 ONLY FOR A750F/A750FN/A750GN Some...
forum.xda-developers.com
Try this. You need flash a "GSI Boot Fix" to use a GSI on A750.