Hi guys, Im new to the GS 5 forums, I had a nexus 4 which I rooted and havent had any problems but I wanted to know if rooting in the GS 5 would break anything on the phone as the fingerprint scanner or private mode, I am aware that S Health can be fixed.
Also, if I install Xposed Framework will it break anything too?
Thanks in advance
anyone
Anyone???
Private mode is broken and the files you had in there are irrecoverable I think.
S Health has a fix, it's broken unless you change some lines in build.prop
Fingerprint scanner still works.
Knox is dead, OTA as well.
I haven't seen or heard any problems that rooting causes, and so far from the little I've used Xposed all seems well.
Related
Hi,
the last cupple of days i figured out that my camera flashlight is not working any more
I have currently CM10.2 installed wich is working greate but the flashled is dead.
It is also not working any more with any other app than the camera.
Does anybody else have/had the same problem?
Is there a hidden Service menue i can acces somehow where i can do some kind of Hadrdware testing?
If this is a hardware issue, does anybody know an approved way to get back the waranty as i heard it is void if you custom rom your phone. At the S3 there was just the triange wich could be flashed away, how is this with the LG.
Thanks a lot for your help.
Best regards
Nimanic
To fix titleHello everyone thanks for trying to help heres my problem in not from the us I actually live in a country called Trinidad. I got this at&t galaxy s5 from someone and the phone is amazing it works good and I had all but one problem I wanted it rooted. Now I have had all the other galaxys but this one I didn't know anything about locker boot leaders and stuff like that cause I'm really acustomed to my phones being unlocked this one is but with slot of complications so here's what I did. I read slot of articles and I saw my phone was on baseband of july but in order for me to root it with towelroot by geohot I downgrade to get a baseband of march now all was well until I realised my fingerprint scanner wasn't working anymore so I desperatly tried everything to get it back now I got a break through I downloaded busy box and safestrap and got a customer recover for this locked bootloader and eurika I download the vision x rom and flashed it and regained my fingerprint scanner all was well and randy and I was happy as hell until I opens my camera soon as I opened my famer the first thing I saw was a green flash and then the camera would work but it would have computer duplicated of what the camera was seeing on the screen but there is a temorary soloutiom I found I would just open my panel turn hdr off or on and the camera would work and function normal the phone records video without a hitch please help I tried everything I did factory reset I restarted the phone I cleared camera cache and still nothing its annoying the heck out of me I took some screen shots so I'll post it.
please help
C'mon does anyone know an answer to this please
Did you ever fix this? I'm having the same problem on stock rooted rim 4.4.4.
So
I just fixed my broken Screen on my Nexus 4 (i earn money repairing phones), and i got a problem. The Proximity Sensor and Light sensors werent working so i just took them off and tried to boot up again. But my phone isnt booting anymore. It just keeps bootin inside a bootloop. Device was never rooted or unlocked. So i tried resetting but didnt work. Then unlocked the device and flashed a custom recovery and several different roms but didnt work either.
Now i wanted you guys help, if you could tell me if nexus devices dont boot up with missing hardware. Because my experience tells me that almost every smartphone even boot up with mossing hardware like the sensors and things.
Dont know if anyone ever had a problem like this, but i hope you guys can help me.
I dont want to huy a new proxysensor before being sure its about the missing hardware, cause the sensors are like 20 $ and that phone isnt much worth anymore.
abdullah30539 said:
So
I just fixed my broken Screen on my Nexus 4 (i earn money repairing phones), and i got a problem. The Proximity Sensor and Light sensors werent working so i just took them off and tried to boot up again. But my phone isnt booting anymore. It just keeps bootin inside a bootloop. Device was never rooted or unlocked. So i tried resetting but didnt work. Then unlocked the device and flashed a custom recovery and several different roms but didnt work either.
Now i wanted you guys help, if you could tell me if nexus devices dont boot up with missing hardware. Because my experience tells me that almost every smartphone even boot up with mossing hardware like the sensors and things.
Dont know if anyone ever had a problem like this, but i hope you guys can help me.
I dont want to huy a new proxysensor before being sure its about the missing hardware, cause the sensors are like 20 $ and that phone isnt much worth anymore.
Click to expand...
Click to collapse
Try flash stock rom 4.2/4.2.1/4.2.2
aliberti98 said:
Try flash stock rom 4.2/4.2.1/4.2.2
Click to expand...
Click to collapse
I'm having the same problem with my Nexus 4. It just went into bootloop and i've tried flashing these stock roms. The phone turns on normally after flashing these roms but the radio doesn't work. It shows baseband unknown and no imei.
If anyone can help then it would be great.
moonkhan said:
I'm having the same problem with my Nexus 4. It just went into bootloop and i've tried flashing these stock roms. The phone turns on normally after flashing these roms but the radio doesn't work. It shows baseband unknown and no imei.
If anyone can help then it would be great.
Click to expand...
Click to collapse
I have the same problem too! I'm searching a method to restore imei but qpst can't find the nexus 4; if someone find a method please post it!
Sorry for my bad english!
Did anyone's Nexus 4 fell or got damaged before getting stuck into bootloop?
In one Thread i read that there was some issue with the vibrator in the phone and after removing it and reflashing the phone worked perfectly normal.
I guess my Nexus 4 fell the day before it got stuck into bootloop.
But i don't know how right i am so if anything like this happened then do post it here to let us know.
Has this been resolved??? I have same issue as OP, replaced screen for nexus 4 proximity sensor problem, then tried to fix it and now in bootloop even after unlocking device and flashing android 4.4.4 and 4.3
Could someone try this and post the result here? http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sorry for my bad english
Bootloop
same problem
Hey guys i don't know about the bootloop problem but i have changed my screen on my nexus 4 too and i had the proximity problem, i found a fix on the internet you just need to take the little rubber thing on the sensors with two holes and turn it around. I don't know why but it works. Hope this helps at least somebody.
If someone have another nexus 4, please backup EFS folder whit this http://forum.xda-developers.com/nexus-4/general/efs-nexus-4-imei-efs-backup-restore-t2740788, use it, move backup to compiter, open m9kefs1.img with an hex editor, find the place for IMEI code and change it to the original IMEI for not be illegal; maybe can work also from backup of another device that use EFS folder for IMEI.
If work please upload it without your IMEI
Sorry for my bad english
nexus 4 no sim detected unknown baseband no imei
my phones screen was not working got replaced after that this problem started. its not only problem with unknown baseband and null imei its problem with also speakers no voice and no sim card recognized and I have nexus 4 android 5.1.1 flashed older roms no luck. some one told lollipop needs new baseband version to work fine all these things. but can't find any baseband on web. I think its all stupid fault of google android software OR LG fault OR fault of flashing new os on these LG phones. if any body got any correct fix or answer please post it thanks. pleaseeeeeeee post a FIXXXXXXX.
danial212k said:
my phones screen was not working got replaced after that this problem started. its not only problem with unknown baseband and null imei its problem with also speakers no voice and no sim card recognized and I have nexus 4 android 5.1.1 flashed older roms no luck. some one told lollipop needs new baseband version to work fine all these things. but can't find any baseband on web. I think its all stupid fault of google android software OR LG fault OR fault of flashing new os on these LG phones. if any body got any correct fix or answer please post it thanks. pleaseeeeeeee post a FIXXXXXXX.
Click to expand...
Click to collapse
Lollipop boot?
Inviato dal mio Nexus 4 con XDA Forums Pro.
Did lg repair the phone? Sounds like the motherboard was damaged during the screen replacement.
After buying my edge plus I immediately rooted my phone using the kernel of arter97. I also had to flash the firmware after installing xprivacy as my phone didn't boot anymore. Cause of that I don't know if my problem is the result of rooting or existed from the beginning.
Now everything seems to work fine except the edge. If I want to add a contact it switches into the contact-menue, I choose a contact and nothing happens. The space in the edge doesn't show the choosen contact and keeps the plus-symbol instead. The same if I want to add an app.
In the edge-menue I can't make changes like to switch off the vip or the app or the light. It behaves as if I wouldn't have the right to overwrite the settings.
Does anyone has the same problem? How to solve?
Thanks!
My configuration:
Modell SM-G928F
Android-Version 5.1.1
Kernel 3.10.92-arter97
Nobody? Who knows which system-files are responsible for the edge? Maybe I just would have to change the rights to write?
Would be very grateful for an answer.
I tyred to have some help by the Samsung-Hotline. I described my problem but they even don't want to give me a little hint cause they don't give service to a rooted system. And anyway they wouldn't know the responsible files.
Nobody here with the same problem? Am I the only one with a rooted edge+ ?
mvm007 said:
I tyred to have some help by the Samsung-Hotline. I described my problem but they even don't want to give me a little hint cause they don't give service to a rooted system. And anyway they wouldn't know the responsible files.
Nobody here with the same problem? Am I the only one with a rooted edge+ ?
Click to expand...
Click to collapse
Hey man. Making the 'Edge services work' is not easy. First of all which firmware/custom rom do you use currently? I flashed a custom note5 rom which hasnt got edge screen feature and wanted to bring it again. Digged and found something, flashed one of versions(Edge feature_forN5.zip) (3 version remain) and got back the Side apps and contacts feature(I got BOOTLOOPS with v0.3 and DIDNT try OJ5v). Night clock and information stream never worked btw. I got bored of tryin bla bla. Now using Audax Plus rom and all edge features are fully workin. Whatever have a look at the link;
https://www.androidfilehost.com/?w=files&flid=39847
and his thread is in;
http://forum.xda-developers.com/note5/themes-apps/mod-enable-edge-features-s6-edge-t3206289
Good luck..
Hey Konsstantine,
first I want to thank you a lot for your support. I will try it the next days and give feedback.
As far as I see this work was done for the galaxy note 5 edge. Do you think it works with the S6 edge +?
Forgot to write my firmware:
I installed G928FXXU2AOJ5
Android 5.1.1
mvm007 said:
Hey Konsstantine,
first I want to thank you a lot for your support. I will try it the next days and give feedback.
As far as I see this work was done for the galaxy note 5 edge. Do you think it works with the S6 edge +?
Click to expand...
Click to collapse
Hey. Yeah Im s6 edge plus user. It was working good for my Tekxodus Note5 rom installed s6e+ That rom havent got the edge features in old versions. But that does not enough to understand that why your edge features dont work. Btw you can see which apps related to edge things in that zip. I think you missed somehing, maybe you should try(if didnt) factory reset, wipe cache/dalvik.
I want to thank you again.
By coincidence I just found the reason for my problem - its a bit embarassing ...
I blocked the rights of the service "PeopleStripe" on my rooted phone. Giving it back its rights the edge is working fine.
This is a weird one and I have a case with Google open, unfortunately you need to talk with all the levels of support before you can talk to someone that actually knows anything.
Got a Galaxy S8 SM-G950F, decided to play around with it so unlocked the bootloader and flashed a few ROMs and such. Decided to use it for work so I returned it to stock flashing the original stock rom for my carrier with Odin and then disabled OEM Unlock.
All good and peaches but when I tried to use my work G Suite account I got a cannot create work profile error blaming a Custom OS install (first attached image).
Keep in mind I am the G Suite Admin for my company and I know we don't check for unlocked bootloaders, custom roms and root and we have lots of people on custom roms, there is a specific option for that so I am sure we don't enforce that. But even if, the device has knox triggered but is now fully stock as you can see in the second attached image.
I have since tried a Samsung Smart Sync restore as well, but it didn't fix the issue, everything on my device says it is stock and in an official status, Google is clueless as well so far.
Not much hope anyone met this as it seems to be fairly mind blowing and unique, but worth a try
bubbl3 said:
This is a weird one and I have a case with Google open, unfortunately you need to talk with all the levels of support before you can talk to someone that actually knows anything.
Got a Galaxy S8 SM-G950F, decided to play around with it so unlocked the bootloader and flashed a few ROMs and such. Decided to use it for work so I returned it to stock flashing the original stock rom for my carrier with Odin and then disabled OEM Unlock.
All good and peaches but when I tried to use my work G Suite account I got a cannot create work profile error blaming a Custom OS install (first attached image).
Keep in mind I am the G Suite Admin for my company and I know we don't check for unlocked bootloaders, custom roms and root and we have lots of people on custom roms, there is a specific option for that so I am sure we don't enforce that. But even if, the device has knox triggered but is now fully stock as you can see in the second attached image.
I have since tried a Samsung Smart Sync restore as well, but it didn't fix the issue, everything on my devices says it is stock and in an official status, Google is clueless as well so far.
Not much home anyone met this as it seems to be fairly mind blowing and unique, but worth a try
Click to expand...
Click to collapse
Wouldn't be surprised if this is Knox related. Once Knox is tripped it is permanent. That's why if you try to open s health on a Knox tripped stock firmware it says it won't open because it's rooted even though it's not rooted
sofir786 said:
Wouldn't be surprised if this is Knox related. Once Knox is tripped it is permanent. That's why if you try to open s health on a Knox tripped stock firmware it says it won't open because it's rooted even though it's not rooted
Click to expand...
Click to collapse
Never been a problem in the past with Google, unless they started to check for Knox. Still, we have the "Compromised Devices" check disabled, should be considered a bug if their app is triggered by that
bubbl3 said:
Never been a problem in the past with Google, unless they started to check for Knox. Still, we have the "Compromised Devices" check disabled, should be considered a bug if their app is triggered by that
Click to expand...
Click to collapse
The thing is, a lot of the newer Samsung's once Knox is tripped that's it, it can't be hidden unless by custom rom and kernel, older devices like the s3 and s4 you could reset the Knox counter, and most other phones root is easily hidden, and bypassed. But Knox is on a boot loader level, the app can't do anything to change that, and I doubt it will ever be fixed.
yes it is true, since the galaxy s7 , knox counter is hardware so once its broken its permanent, no matter if you are on custom/stock/rooted/unrooted rom or firmware. once knox is broken I highly suggest to use custom rom
I actually got in touch with Samsung and they confirmed that Knox shouldn't matter for Google Apps unless they check for it, but we have the option to check for it disabled on the admin side.
We also have 2 users with rooted S7 that don't have this issue.
I bet this one will be messy to sort out, if ever...
Solution?
bubbl3 said:
I actually got in touch with Samsung and they confirmed that Knox shouldn't matter for Google Apps unless they check for it, but we have the option to check for it disabled on the admin side.
We also have 2 users with rooted S7 that don't have this issue.
I bet this one will be messy to sort out, if ever...
Click to expand...
Click to collapse
Did you ever solve this issue? I have more or less same problem on S8 with Pie
DRDSVK11 said:
Did you ever solve this issue? I have more or less same problem on S8 with Pie
Click to expand...
Click to collapse
Did not resolve and sold the phone before any custom rom was available. After being escalated to an engineer, we used apt to check the events in real time on the phone and we noticed that Samsung intercept the request from G Suite MDM to encrypt the storage to use its own knox based encryption and becuase of the knox counter it fails.
Nothing Google can do, not sure if a custom rom would solve, definitely you would need at least a completely custom kernel to avoid this trick that Samsung is pulling off, good luck!
probably knox is stipped but that shouldnt affect google apps as safetynet doesnt rely on knox maybe you could try actually using a custom rom with custom kernel that spoofs knox 0x0
I dont know if this work on all devices, but i know the solution, replace ManagedProvisioning apk, usually on /system/priv-app/ , take a replacement from stock aosp gsi from phhuson (you must pick correct gsi for example like your android version and architecture must be the same). this little trick is working on my stock j7 prime oreo.