Related
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
UPDATE 3/6/14
I installed a snapshot of CM 11 (KitKat) onto my device with little issues. I'll update this guide with the links to that firmware, and also update the existing links because of changes CyanogenMod made to how they aggregate their S4 devices now. They are treating them all as derivatives of 'jftle', so basically one firmware fits all devices, including the i9507! (even if not official yet).
Please read the bottom of this post if you wish to install KitKat on your device.
CUSTOM FIRMWARE ON SAMSUNG GALAXY S4 i9507 - Aus/HK
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
If you're looking to root this device, I found that by treating it essentially as an international i9505 I was able to fulfil all three of the things I mentioned above.
UPDATE: THIS WILL VOID YOUR WARRANTY AND RESULT IN 'KNOX WARRANTY VOID 0x1' BEING DISPLAYED WHEN YOU ENTER DOWNLOAD MODE ON THE DEVICE. PLEASE BE SURE YOU ARE OKAY WITH THIS HAPPENING BEFORE TRYING THIS FOR YOURSELF. AS IT STANDS, KNOX CANNOT BE RESET, IT IS AT A HARDWARE LEVEL.
[ROOT i9507]
Using Chainfire's guide to CF-Auto-Root in the Galaxy S 4 i9505 Original Android Development section of this forum; I was able to root my device despite it being an i9507. Being a new user, I wasn't sure exactly what things to test out whether the root worked/was permanent, but I did install AdBlock Plus and it asked me for Superuser privileges, then proceeded to work. I also restarted the device and tested whether the root was still present; it was.
[INSTALL CLOCKWORKMOD]
I decided to install CyanogenMod as I have heard from friends that have it; and read online about it being one of the more stable custom ROMs available. It has been a while since I last owned an Android device! So, continuing with my theme of treating this device as being an international i9505, I obtained CM 10.2.0, a stable release of the jfltexx CM, based on from their website (as of December 2013, this was the most recent). Their custom installer app on Windows did not support my phone, so I had to use their guide for manual installation.
Their guide contained steps to installing ClockworkMod Recovery as well as the ROM installation. Following the guide, I installed it without a hitch. When rebooting the phone from ClockworkMod, it prompted me about the fact that the phone may reflash its own recovery tool, but this did not happen. Once again, a success.
[INSTALL CYANOGENMOD]
The last task was to install CM. This was quite an endeavour as I decided to use someone else's Windows 8 laptop (being the only Windows device I had access to at the time) and I forgot how much of a struggle it can be! Again, I used CM's guide to installing 10.2.0 (which by the way is Android 4.3.1, whereas the stock firmware is bloated and heavy at 4.2.2). This went off without a hitch once I reminded myself how the ADT works. I also did as CM suggested and installed the Google Apps pack alongside the ROM.
So, currently this is where I'm at. The device boots and reboots fine. Some users in certain threads had issues with loading 4.4 (KitKat) ROMs or custom ROMs that they didn't allude to the names of, so I don't know if they were having issues with CM or not. There are other threads, but that was the one that kickstarted my attempts to get this all to work. Their issues with the custom ROMs seemed to be related to the 4.4 ROM not recognising the modem of the i9507; I'm not sure why this is but the i9507 was made specifically for Australian/Hong Kong networks so perhaps 4.4 has not been updated yet or something of the like. Anyway, on 4.3.1, or CM 10.2.0, my SMS, calling, and internet are working fine (it displays Virgin Mobile as my carrier). My 4G reception is somewhat iffy in this town (or in particular my house), and the reception seems to be switching between 3G and H so whether that is indicative of 4G not working, I'm not sure. LTE is definitely checked in the settings, however, and my area does have 4G, but my parents' iPhone 5Ss sometimes do not have 4G in this house either. I'll report back tomorrow after having tested the phone for a day to see if the 4G does activate.
As it stands, however, the phone seems to be functioning well. Oddly the Settings report that the phone is an i9505, I assume that's normal as I'm using a ROM for that particular phone!
[CONCLUSION]
So, I hope that anyone who has been looking for a way to remove the carrier/Samsung bloat from their i9507 device will have a good time using the guides I've used. I followed them to the letter and I had no issues.
DISCLAIMER: I had no troubles, but that's not to say you won't either. Please be careful, as you may potentially risk affecting your phone negatively. I'm simply telling you what I did, not giving you a 100% correct and flawless guide that will work no matter what.
Also if you're looking for a 4.4 ROM then you might be out of luck, least till some dev or coder takes notice of this device's existence and helps out to develop a specific way of rooting this phone/installing custom ROMs for this phone. Overall though, it seems to all work fine so perhaps the 4.3.1 CM isn't such a bad thing.
If you try this and want the original firmware back on your phone, use this link. I believe that OPS is the Australian firmware, the other one is for Hong Kong. So, for the second link, HK is Hong Kong, and the one without is for Aus.
UPDATE 3/6/14
I've successfully managed to install a Nightly build of CM 11, based on KitKat. Read my latest post in this forum for more info. I essentially found that upgrading from within the phone itself caused a number of issues so I did a fresh flash. Please note that such a flash of a new OS wipes all personal data but not things like images, videos, etc. I lost all my contacts, SMS, browsing history, apps etc. But my Gallery, Downloads folder, etc remained intact.
I followed my guide to flashing the phone again, but I used a Nightly build of CM 11, based on KitKat. As I write this, there are actually stable versions of CM that you can use in place of the CM 10.2.0 I used in the above guide. If you follow those steps but use this firmware you'll find no issue. Feel free to use CM's guide, but don't, under any circumstances, forget to flash Google Apps to your phone!!!
If you need a hand or want a question answered, feel free to post here and I'll do my best to help you out. Thanks!
kaiserwatson said:
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
If you're looking to root this device, I found that by treating it essentially as an international i9505 I was able to fulfill all three of the things I mentioned above.
[ROOT i9507]
Using Chainfire's guide to CF-Auto-Root in the Galaxy S 4 i9505 Original Android Development section of this forum; I was able to root my device despite it being an i9507. Being a new user, I wasn't sure exactly what things to test out whether the root worked/was permanent, but I did install AdBlock Plus and it asked me for Superuser privileges, then proceeded to work. I also restarted the device and tested whether the root was still present; it was.
[INSTALL CLOCKWORKMOD]
I decided to install CyanogenMod as I have heard from friends that have it; and read online about it being one of the more stable custom ROMs available. It has been a while since I last owned an Android device! So, continuing with my theme of treating this device as being an international i9505, I obtained the latest stable release of the jfltexx CM from their website (it was the most recent stable release at the time, may be out of date by the time you get to doing this yourself). Their custom installer app on Windows did not support my phone, so I had to use their guide for manual installation.
Their guide contained steps to installing ClockworkMod Recovery as well as the ROM installation. Following the guide, I installed it without a hitch. When rebooting the phone from ClockworkMod, it prompted me about the fact that the phone may reflash its own recovery tool, but this did not happen. Once again, a success.
[INSTALL CYANOGENMOD]
The last task was to install CM. This was quite an endeavour as I decided to use someone else's Windows 8 laptop (being the only Windows device I had access to at the time) and I forgot how much of a struggle it can be! Again, I used CM's guide to installing 10.2.0 (which by the way is Android 4.3.1, whereas the stock firmware is bloated and heavy at 4.2.2). This went off without a hitch once I reminded myself how the ADT works. I also did as CM suggested and installed the Google Apps pack alongside the ROM.
So, currently this is where I'm at. The device boots and reboots fine. Some users in certain threads had issues with loading 4.4 (KitKat) ROMs or custom ROMs that they didn't allude to the names of, so I don't know if they were having issues with CM or not. There are other threads, but that was the one that kickstarted my attempts to get this all to work. Their issues with the custom ROMs seemed to be related to the 4.4 ROM not recognising the modem of the i9507; I'm not sure why this is but the i9507 was made specifically for Australian/Hong Kong networks so perhaps 4.4 has not been updated yet or something of the like. Anyway, on 4.3.1, or CM 10.2.0, my SMS, calling, and internet are working fine (it displays Virgin Mobile as my carrier). My 4G reception is somewhat iffy in this town (or in particular my house), and the reception seems to be switching between 3G and H so whether that is indicative of 4G not working, I'm not sure. LTE is definitely checked in the settings, however, and my area does have 4G, but my parents' iPhone 5Ss sometimes do not have 4G in this house either. I'll report back tomorrow after having tested the phone for a day to see if the 4G does activate.
As it stands, however, the phone seems to be functioning well. Oddly the Settings report that the phone is an i9505, I assume that's normal as I'm using a ROM for that particular phone!
[CONCLUSION]
So, I hope that anyone who has been looking for a way to remove the carrier/Samsung bloat from their i9507 device will have a good time using the guides I've used. I followed them to the letter and I had no issues.
DISCLAIMER: I had no troubles, but that's not to say you won't either. Please be careful, as you may potentially risk affecting your phone negatively. I'm simply telling you what I did, not giving you a 100% correct and flawless guide that will work no matter what.
Also if you're looking for a 4.4 ROM then you might be out of luck, least till some dev or coder takes notice of this device's existence and helps out to develop a specific way of rooting this phone/installing custom ROMs for this phone. Overall though, it seems to all work fine so perhaps the 4.3.1 CM isn't such a bad thing.
If you try this and want the original firmware back on your phone, use this link or this one. I believe that OPS is the Australian firmware, the other one is for Hong Kong. So, for the second link, HK is Hong Kong, and the one without is for Aus.
If you have any questions, please feel free to ask. I'll post later tomorrow when I've tested the phone for a day to see if it's still working, and to see if the 4G/LTE does actually work. Fingers crossed nothing goes wrong in the meantime!
Click to expand...
Click to collapse
I've had my i-9507 rooted for about a month now with foxhound rom, also on the optus variant.
One thing i've noted is, its next to impossible to update the MODEM for it.
I think because our latest modem for this variant is the one we have stock. And new updates haven't been put in terms of modem specifically for our variant yet.
We should keep this thread stickied for Australian OPTUS GT-i9507 discussion.
OR open up a sub forum for it.
kaiserwatson said:
I'll post later tomorrow when I've tested the phone for a day to see if it's still working, and to see if the 4G/LTE does actually work. Fingers crossed nothing goes wrong in the meantime!
Click to expand...
Click to collapse
Firstly, thank you for creating this complete description of your experiences with customising the i9507.
Secondly, just wanted confirmation that you do now have the pesky "KNOX WARRANTY VOID: 0x1" displayed when your device is in Download mode, right?
Lastly, any updates, issues? All still working, including 4G/LTE?
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
I do have the Knox 0x1, which I assume means my warranty is void. There's conjecture as to whether that will actually affect warranty for this device in Australia, as I've read up on the Knox system but i think the ACCC would have serious issues with this system actually affecting the warranty. But yes, it would seem my warranty is void, let's hope the phone lasts two years!
I have been able to access 4G, the phone says 4G or LTE, sometimes switching between the two. Again, the reception in the town I'm currently staying in is pisspoor so I can't say for certain whether the antenna/modem is fully functioning to the degree it would be on the stock firmware, but I can definitely access the Optus 4G network.
One issue I did have was that I sent an SMS then immediately turned my screen off, 40 minutes later the message was still 'sending'. I have recreated the same scenario but I haven't been able to get it to happen again, perhaps just a weird tower-side quirk. I know people were having issues with the modem and the phone sleeping but this doesn't seem to be related. Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
kaiserwatson said:
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
I do have the Knox 0x1, which I assume means my warranty is void. There's conjecture as to whether that will actually affect warranty for this device in Australia, as I've read up on the Knox system but i think the ACCC would have serious issues with this system actually affecting the warranty. But yes, it would seem my warranty is void, let's hope the phone lasts two years!
I have been able to access 4G, the phone says 4G or LTE, sometimes switching between the two. Again, the reception in the town I'm currently staying in is pisspoor so I can't say for certain whether the antenna/modem is fully functioning to the degree it would be on the stock firmware, but I can definitely access the Optus 4G network.
One issue I did have was that I sent an SMS then immediately turned my screen off, 40 minutes later the message was still 'sending'. I have recreated the same scenario but I haven't been able to get it to happen again, perhaps just a weird tower-side quirk. I know people were having issues with the modem and the phone sleeping but this doesn't seem to be related. Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
Click to expand...
Click to collapse
That occurs because the modem signal cuts out after you switch your phone off, or lock it.
This issue can be resolved by updating our modems, but with our current variant we can't update it yet apparently, until the correct new modem for our specific variant has been released.
Hi guys,
I thought I would also post here.
I have the optus 9507 and I tried a couple of different kitkat 4.4 roms. They all worked perfectly except for the fact that they lost data completely as soon as the phone went to sleep. the weird thing is, the phone showed 0 bars but i could take calls just fine, just had data issues.
i tried the slimkat rom and the echoe rom with the same issue
i went back to stock firmware, rooted, ran a debloat script i found on xda, removed a bunch more apps, then unrooted again because i need to run good for enterprise for work.
im getting decent battery life with the debloated stock rom but i would like to move to 4.4 if theres a rom that works. ive been watching the optus and sammobile site hoping there will be a newer modem for the hk version because i think optus will take their time releasing 4.3 for this model.
kaiserwatson said:
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
......
Click to expand...
Click to collapse
Thanks for your experience sharing,
I also started with Cyanogen and shared about the same experience.
Just didn't know the Knox thing before I started.. should had read up more before doing it.
So you did the Recovery with Heimdall also? What has made you switch to the customized Rom camp
kaiserwatson said:
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
Click to expand...
Click to collapse
Hey, no worries at all, anyone who works weekends can take all the time they need...
But yes, it would seem my warranty is void, let's hope the phone lasts two years!
Click to expand...
Click to collapse
Yea, I've done some reading also and you're right, it seems to be all conjecture, I really doubt handset warranty refusal can be based on the KNOX Warranty chip. I think the Samsung Enterprise Security Group VP explains it well here.
Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
Click to expand...
Click to collapse
Great to hear, based on this I can ge ahead and 'burn out' my eFuse, happy in the knowledge that my Knox warranty has gone to a good cause. :fingers-crossed:
---------- Post added at 08:49 PM ---------- Previous post was at 08:40 PM ----------
opelcalibra said:
then unrooted again because i need to run good for enterprise for work.
Click to expand...
Click to collapse
I can only assume your "enterprise for work" has nothing to do with KNOX, right? Coz that option would be closed for you now...
CuriosityBrah said:
That occurs because the modem signal cuts out after you switch your phone off, or lock it.
This issue can be resolved by updating our modems, but with our current variant we can't update it yet apparently, until the correct new modem for our specific variant has been released.
Click to expand...
Click to collapse
That odd message not sending was the only issue I've had with this sort of thing; I can still download things, receive messages and calls just fine while my phone is sleeping, how do you know if the modem signal is cutting off? Perhaps it's just a selective thing, not sure. Don't know how to test if it's happening to me because it doesn't seem to be, lol.
opelcalibra said:
I have the optus 9507 and I tried a couple of different kitkat 4.4 roms. They all worked perfectly except for the fact that they lost data completely as soon as the phone went to sleep. the weird thing is, the phone showed 0 bars but i could take calls just fine, just had data issues.
Click to expand...
Click to collapse
Hey mate if you check the forum that I linked to the Knox issue; someone on there posted a fix for sound/WiFi issues post-Knox voiding, maybe that fix'll work for you. Sorry I can't link you to the exact post but it was about 10-20 pages in.
opelcalibra said:
i went back to stock firmware, rooted, ran a debloat script i found on xda, removed a bunch more apps, then unrooted again because i need to run good for enterprise for work.
im getting decent battery life with the debloated stock rom but i would like to move to 4.4 if theres a rom that works. ive been watching the optus and sammobile site hoping there will be a newer modem for the hk version because i think optus will take their time releasing 4.3 for this model.
Click to expand...
Click to collapse
Yeah I reckon they'll take ages, they have pretty much left everyone who's getting this phone in the next couple of months in the dark because of the (as I can tell) severe lack of devs etc in Aus who have Samsung phones and are willing to hack them to the ****. I wish I could help out somehow, but I don't have the time to learn so I figured I'd help out by putting up my experiences. I'm still learning as I go haha.
As for your KitKat problem, I have read that 4.4 didn't do so well in terms of battery life and bloat, what are your reasons for wanting to go to it? I wanted the most recent build also but I figured that if they're still having issues with it then it was better to go with something I knew would work (ie. 4.3.1).
phileasx said:
Thanks for your experience sharing,
I also started with Cyanogen and shared about the same experience.
Just didn't know the Knox thing before I started.. should had read up more before doing it.
So you did the Recovery with Heimdall also? What has made you switch to the customized Rom camp
Click to expand...
Click to collapse
I followed the Windows process on the CM wiki to the letter, so yeah I did the Heimdall also.
Mate legitimately I went from my stock firmware taking up so much space on the hard drive to the real lightweight CM, seeing as I haven't bought a micro SD yet that was a big deal. Also battery life was a major reason for me buying the S4 so to be able to further improve it is just hella.
siganid said:
Hey, no worries at all, anyone who works weekends can take all the time they need...
Yea, I've done some reading also and you're right, it seems to be all conjecture, I really doubt handset warranty refusal can be based on the KNOX Warranty chip. I think the Samsung Enterprise Security Group VP explains it well.Great to hear, based on this I can ge ahead and 'burn out' my eFuse, happy in the knowledge that my Knox warranty has gone to a good cause. :fingers-crossed:
Click to expand...
Click to collapse
In Australia I think we're pretty good. Funny that Samsung and Optus have given us this nice present and it's only a matter of time before someone cracks it open and remains above the warranty voiding
I have read that Knox may be software-based, which would make sense, and maybe it's a matter of time before someone cracks that too. Hehe.
Go ahead, post here if you have any issues and I'll see if I can help you out. What ROM would you be planning on using? A 4.3.x one?
kaiserwatson said:
I followed the Windows process on the CM wiki to the letter, so yeah I did the Heimdall also.
Mate legitimately I went from my stock firmware taking up so much space on the hard drive to the real lightweight CM, seeing as I haven't bought a micro SD yet that was a big deal. Also battery life was a major reason for me buying the S4 so to be able to further improve it is just hella.
Click to expand...
Click to collapse
Welcome to the rom flashing side
After read up more, I realize Odin is a more popular method for Galaxy S4 flashing,
Besides that, Stock rom battery life should also be all right. Samsung did quite some efforts to make the software user friendly.
Anyway, the Bloatware chunk are really irritating have to say.
because i cant keep still i have flashed my phone again lol.
i flashed the official CM 11 (4.4.2) and gapps for kitkat and all is working awesome so far.
no issues with losing signal when going to sleep. seems very fast. right now im happy with it.
Could someone please find new links for the original software posted in the OP?
Links are dead, would be greatly appreciated! =)
Also, Opelcalibra, you have no issues with network/signal on CM 4.4.2 with the Optus i9507?
I better give it a try then lol
RE: Signal issues
Hi,
I also have the AU i9507 Opus S4, I flashed the Omega based 4.4.2 KitKat (i9505 version) and had wifi problems (Greyed out) I tried various fixes and went back to 4.3 based Omega, this had its problems with cell signal being lost when locking the mobile.
I fixed this by going into settings and experimented with mobile networks i.e. Settings, more networks, mobile networks, network mode and tried all 4x options with (for me at least) the GSM ONLY option selected, great rom and worth losing the 4g which is very patchy in my part of Melbourne.
D
Anyone else had any sort of success rooting this phone without tripping Knox.
Also, is it just me, or does it suck pretty hard that we Aussies get stuck with an inferior version of a phone? (Snapdragon 600 in the I9507 vs the 800 in the other international versions)
Update
Hi
Just wondering if anyone has an update on this? Success or otherwise...
One of the main reasons I'm looking to root is to boost volume levels - I find the volume to be way too low. Does anyone know of a way to do that without rooting? Of course I'd like to remove bloatware but could live with it if volume was fixed.
Thanks in advance.
thestuntman80 said:
Anyone else had any sort of success rooting this phone without tripping Knox.
Also, is it just me, or does it suck pretty hard that we Aussies get stuck with an inferior version of a phone? (Snapdragon 600 in the I9507 vs the 800 in the other international versions)
Click to expand...
Click to collapse
Hey bro, no one has cracked without tripping Knox yet because as far as I can tell it's a phone specific fix/hack. So, because our phone is a different and 'rare' model, I doubt that the major heads in the Knox-proofing scene (CF comes to mind) will have the time to make a fix for the knox trip. So for now, either suffer in your jocks (QQ) get a different phone (uh, not likely) or wait for the minute chance that someone actually cares about Aussies )
As for your second point, yeah, it does suck. We get shafted with all sorts of things like prices, release dates, localization...the list goes on. Unfortunately the people who make these ploys know we're desparate and will pay the exorbitant prices anyway :/
jameshef said:
Hi
Just wondering if anyone has an update on this? Success or otherwise...
One of the main reasons I'm looking to root is to boost volume levels - I find the volume to be way too low. Does anyone know of a way to do that without rooting? Of course I'd like to remove bloatware but could live with it if volume was fixed.
Thanks in advance.
Click to expand...
Click to collapse
Hey mate, the rooting was probably the easiest part of the whole situation. You can follow my guide in the OP if you're having trouble. Just be aware about the warranty issues etc because your audio issue may be hardware related rather than software? Is the volume issue in the headphones or the speaker? Some apps may not utilise the phones full volume and also be sure to go into the settings of the phone and make sure the volume limiter is turned OFF. This **** me to tears for the longest time but once I figured out what the issue was, all good!
The only thing I'd say is just make sure its not a hardware issue because you don't want to root your phone, find out that it wasn't a software issue, take your phone into Samsung and have them tell you that your warranty is voided because you rooted. Obviously that's a worse case scenario but just be on the safe side.
I hope I helped you guys!
kaiserwatson said:
Hey mate, the rooting was probably the easiest part of the whole situation. You can follow my guide in the OP if you're having trouble. Just be aware about the warranty issues etc because your audio issue may be hardware related rather than software? Is the volume issue in the headphones or the speaker? Some apps may not utilise the phones full volume and also be sure to go into the settings of the phone and make sure the volume limiter is turned OFF. This **** me to tears for the longest time but once I figured out what the issue was, all good!
The only thing I'd say is just make sure its not a hardware issue because you don't want to root your phone, find out that it wasn't a software issue, take your phone into Samsung and have them tell you that your warranty is voided because you rooted. Obviously that's a worse case scenario but just be on the safe side.
I hope I helped you guys!
Click to expand...
Click to collapse
I'm fairly certain it's a software issue. I've done a fair bit of reading on it and the low volume is a very common complaint about the S4. My volute limiter is turned off - thanks for that tip though!
I'm going to try to root this weekend. I really hope that it works and I don't have any issues with reception dropping when the phone goes to sleep! Feels risky.
I've changed my firmware from Optus to XSA, but am still on 4.2.2, how do I upgrade now?
Kies says I have the latest release.
has anyone got links to newer modem files for this phone? been given one to update it to 4.4, but i know from experience that doing so without at least a 4.4 GSM modem, it wont behave right.
to the people without working wifi after updating: flash the Ktoonz kernel, he has a fix for that.
Hi All,
I recently updated to the new official 4.3 update from optus in order to update my baseband etc.
Then i immediately updated to the i9505 Goldeneye 4.4.2 rom. Ran a ebloat script to get rid of alot of the extras and its running very nicely.
Since updating the modem I get 4g at home which i never did before.
optus rom here
http://www.sammobile.com/firmwares/3/?download=27109
flashed via odin (will lose root and custom recovery). re-root and install recovery after flashing this room.
goldeneye rom here
http://forum.xda-developers.com/showthread.php?t=2313469
obviously this will flag knox, mine was flagged long ao
Hey all,
I'm thinking of buying a Mate 7 and switching over from my Moto X Pure. Mainly for the size, metal body, and the battery. Right now I can get it for ~$330 on Amazon. The only thing that's held me back is the software. I've read the stock software is very annoying with constant notifications about apps using up too much RAM/battery. But all these reviews were from the phone's release, I haven't been able to find much information since it's been updated to Marshmallow. I typically like very light ROMs like CM but I see there hasn't been a whole lot of development for this phone other than the KangVIP ROM which seems to have a lot of issues. So I guess my question is how do you all like the stock Marshmallow ROM and is it still good on battery life?
Also I've seen a lot of threads about how to downgrade the software to earlier versions of Android, is this just to install an earlier version of Cyanogenmod? I've not been able to find a "why" in all the threads I've seen on the subject. I've found plenty of Chinese phones that are ~6" with a big battery and metal body but LTE bands are always an issue. This is the only phone I've come across that seems to have everything, other than my concerns about the software. I'm also thinking of holding out and seeing if the Asus Zenfone 3 and the LeTV Max Pro end up having U.S. LTE bands.
Anyway, any thoughts or opinions would be greatly appreciated!
It's getting old now, still a really nice phone but I'd be looking at newer devices at this point. People regress to earlier versions of Android as the MM beta releases often dissapoint. I stuck with the latest release of Lollipop as I have some limited functionality with Xposed, got ViPER4Android working etc, it's smooth and stable. Battery is great. It's hard to describe just how much freedom that allows you compared to other devices. My Oppo Find 7 is a nice phone too, but it just doesn't last long enough and being used to the Mate 7, that annoys me greatly. I do find that the oppo at 5.5" is better to handle and fits a pocket easier. That extra half inch really is noticeable on the Mate. It is one device that does feel a little special though. Once it's optimised and personalised, it's gorgeous.
As for ROMs, not going to happen any time soon. I'm happy with stock, rooted and modded. Doesn't worry me apart from limiting lifespan, but if development did take off, I would be happy.
Huawei just don't understand the international market yet and if they did, and fostered good relations and supported development, they would be able to become #1 I think, but at this point their thinking is still very Chinese.
RobboW said:
It's getting old now, still a really nice phone but I'd be looking at newer devices at this point. People regress to earlier versions of Android as the MM beta releases often dissapoint. I stuck with the latest release of Lollipop as I have some limited functionality with Xposed, got ViPER4Android working etc, it's smooth and stable. Battery is great. It's hard to describe just how much freedom that allows you compared to other devices. My Oppo Find 7 is a nice phone too, but it just doesn't last long enough and being used to the Mate 7, that annoys me greatly. I do find that the oppo at 5.5" is better to handle and fits a pocket easier. That extra half inch really is noticeable on the Mate. It is one device that does feel a little special though. Once it's optimised and personalised, it's gorgeous.
As for ROMs, not going to happen any time soon. I'm happy with stock, rooted and modded. Doesn't worry me apart from limiting lifespan, but if development did take off, I would be happy.
Huawei just don't understand the international market yet and if they did, and fostered good relations and supported development, they would be able to become #1 I think, but at this point their thinking is still very Chinese.
Click to expand...
Click to collapse
Thanks for the quick reply RobboW! I've always had phones that had a lot of development so I've kind of taken it for granted. A couple years ago I wouldn't have even considered a phone without a lot of development but my ROM addiction has really subsided and I only recently put a custom ROM on my Moto X. Honestly I don't do much customization anymore, the thing that made me apprehensive about the Mate 7 was all the "battery saving" shenanigans. If there's some way to disable those while still keeping good battery life (which definitely should be possibly with the 4100 mAh battery) then I'll be happy with the ROM, provided there's no lag. I don't do any kind of gaming or anything, just browsing the web, videos, texts, and emails, but I can't stand any kind of lag.
Thanks again for your help, it's been a grueling process trying to find a phone that meets all my criteria for a reasonable price. The Mate 7's hardware hits it perfectly, so if I can live with the software I still think it's a good deal.
It sounds like your user case is much like mine then. The Mate 7 (get 32Gb version and insert a 128Gb uSD) should serve you well. Update it from kitkat to lollipop for UI smoothness, unlock bootloader, install TWRP recovery, root and do a little debloat, although there's really not much bloat, install Viper if sound is your thing. You will need a different launcher and icon pack to get away from Huawei launcher which is terrible.
For the notifications, it has a notification manager so you can customise that to your liking. Mine doesn't bombard me with warnings. The battery is awesome, just go to power saving settings, ignore the savings and set it to normal. It still easily goes a day with heavy use.
My son liked mine and wanted to update his galaxy S4 so got a Mate 7 32Gb and I did all these things to his. He has wifi and BT on all day, facebook messenger always on etc and it never has a battery problem. He is still gobsmacked by it. Says it's better in every way to the S4 other than maybe the lack of ir blaster (which he doesn't care about) and amoled screen in the S4 but the Mate 7 screen is really nice anyway. I actually like the IPS panel better than amoled as I think amoled is gharish, too colourful, just not realistic and the IPS seems much nicer, more realistic for photos and video. It's actually a warmish tint, unlike my oppo which has a very stark, cold tint and is harder on my eyes.
You can adjust the screen and I set it to it's coldest but it's still warmer than the oppo.
I've been toying with the idea to go back to using the Mate 7 as my daily phone instead of the oppo. I was going to use the Mate 7 as a tool, like a small tablet because it will be the database and interface (BT) between an electrical test tag machine and a label printer. The camera is really good at macro focus and reads barcodes very well.
I didn't want to talk it up to someone expecting a 6P and lot's of custom roms, but for the price they can be bought for now, and your user case, it will make a great daily driver. Just be very sure it works on the correct bands you need there in the US. It works great here in Australia.
Edit: I'm having an issue with my Oppo where sometimes I can't view an email when others work ok. The Mate 7 doesn't have the issue and I've been going through settings looking for differences as the two phones are set up almost the same. Cannot find the problem so I have my SIM in the Mate again (Titanium Backup is so handy for transfering sms and call data) and will try to get a custom ROM in the Oppo.
The Mate works great. No desire for a ROM in that unless I update to MM when/if I can get a stable final release that is originally OTA.
Well I went ahead and bit the bullet and I'm going for it. I'll probably need to be pointed in the right direction once it arrives as far as which ROM to install and how I go about downgrading it if I need to. Thanks again for your help! I'm excited to check it out.
@RobboW has said pretty much all there is that's worth mentioning about the device. If you're after stellar battery life and a solid daily driver you can't go wrong, but don't expect the flexibility of devices that are more open to customization.
I've updated to the official MM release and have yet to encounter any of the issues people complained about in the beta releases. While the LP release is fantastic (and Viper actually works on it, which I miss), the MM build offers even better responsiveness and an overall better-rounded software experience, although that's not saying I wouldn't flash something entirely different in a heartbeat (if only I could....).
The camera is also not very great. On paper it's decent, but photos almost always come out blurry (as there's no OIS) and washed out. A but of tinkering on Snapseed can make a big difference though, but don't expect anything too great.
If you already bought it I'd suggest that you immediately install a 3rd party launcher of your choice to avoid the stock launcher (which really is horrendous), and then root if that's your sort of thing.
Enjoy!
Scruffykid said:
The camera is also not very great. On paper it's decent, but photos almost always come out blurry (as there's no OIS) and washed out. A but of tinkering on Snapseed can make a big difference though, but don't expect anything too great.
Enjoy!
Click to expand...
Click to collapse
Scruffy, set the saturation in the camera app settings a notch higher. You can also set the brightness down a little if needed. I actually find the camera pretty good. It's not a flagship camera but it's also not a cheap one.
I've got my SIM back in my Oppo today, got OmniROM set up pretty nice now. So much better than ColorOS from Oppo. The B331 LP Mate 7 ROM is quite nice for a stock ROM IMO and I'm still happy to keep it. If the Oppo is stable on OmniROM, maybe I'll look at updating the Mate 7 to MM, but not if I can't have Xposed and ViPER4Android......
I'm on Marshmallow on the Oppo now and it's a PIA with some things. File explorers have issues with access, notifications are more intrusive, but it is a nice OS other than that. I actually found Lollipop easier to use.
---------- Post added at 10:54 AM ---------- Previous post was at 10:47 AM ----------
Prozart said:
Well I went ahead and bit the bullet and I'm going for it. I'll probably need to be pointed in the right direction once it arrives as far as which ROM to install and how I go about downgrading it if I need to. Thanks again for your help! I'm excited to check it out.
Click to expand...
Click to collapse
It will ship with Kitkat so you boot and see which firmware version it's on and what OTA update it wants to install when it goes online, but don't install it straight away, come back to the forum with the information and then the correct update tree can be looked at.
Don't leave it on Kitkat, IMO, you either use B331 Lollipop or a Marshmallow ROM. Nothing earlier. Some of the MM ROMS do need an earlier Lollipop version to update from, but sometimes you can flash the ROM anyway, as long as the phone is compatible with it.
RobboW said:
Scruffy, set the saturation in the camera app settings a notch higher. You can also set the brightness down a little if needed. I actually find the camera pretty good. It's not a flagship camera but it's also not a cheap one.
Click to expand...
Click to collapse
I can't seem to find the settings you're mentioning in my camera settings. Perhaps it was removed on the MM builds? Anyway I think simply installing 3rd party camera software should make a big difference. As you and I both said, most of what's wrong with the camera is software.
Haven't tried MM on my Mate 7 so couldn't speculate, but from Google Play, give Open Camera a try, it's free. See if pics match the viewing angle you expected.
For a paid app, Camera FV-5 is very good. It's supposed to mimmick a DSLR.
Edit:
Just installed Open Camera (by Mark Harmon) on both phones. Works well. Two things I like are the availability of grid lines and a level indicator. Makes quite a difference when doing landscape photography. I live in a seaside town and getting horizon level is so important with shots including ocean. If it had panorama mode I'd be a happy chappy!
I haven't been bothered with camera apps on my Mate 7 as it has a good camera on KK and LP and I had no need to look for better. The Oppo Find 7 is another matter. Oppo camera was good with ColorOS, but now on OmniROM, I needed to look at camera apps, but had already found the others with my previous phone as it was a THL W200 and stock software was pretty crap.
RobboW said:
It will ship with Kitkat so you boot and see which firmware version it's on and what OTA update it wants to install when it goes online, but don't install it straight away, come back to the forum with the information and then the correct update tree can be looked at.
Don't leave it on Kitkat, IMO, you either use B331 Lollipop or a Marshmallow ROM. Nothing earlier. Some of the MM ROMS do need an earlier Lollipop version to update from, but sometimes you can flash the ROM anyway, as long as the phone is compatible with it.
Click to expand...
Click to collapse
Alright so it arrived today with KK 4.4.2 build number 120SP04. I went to the updater and it said no updates are available. I don't have a SIM card in it so I don't know if that makes a difference. I didn't realize it didn't have a nano sim slot so I'll have to go to my carrier to get a micro. In the mean time, what are my upgrade paths to a good Lollipop or Marshmallow? I'm in North America and on the main page I only saw update packages for India, Europe, and China I believe. Would I just go with the European ones?
Prozart said:
Alright so it arrived today with KK 4.4.2 build number 120SP04. I went to the updater and it said no updates are available. I don't have a SIM card in it so I don't know if that makes a difference. I didn't realize it didn't have a nano sim slot so I'll have to go to my carrier to get a micro. In the mean time, what are my upgrade paths to a good Lollipop or Marshmallow? I'm in North America and on the main page I only saw update packages for India, Europe, and China I believe. Would I just go with the European ones?
Click to expand...
Click to collapse
Will you be using an SD card? Slot 2 takes either an SD or a nano SIM, not both at once though.
That's the same ROM my phone came on. It's the standard international ROM for a non carrier locked TL10 goldie.
It will update to B130 OTA
From B130 I flashed mine to B331 Lollipop (newest lollipop). Just a download of ROM and place in dload folder and point the updater to it, then it does it from within the OS. It won't go past B130 on an OTA.
If you want MM, that needs to be loked at as there are stacks of vesions. I'm inclined to think if it can be flashed up to MM from B331 it's reasonably new. That's my aim. I won't go to an older LP to get up to a buggy old beta MM.
Here's the download link where I got my stable Lollipop.
http://www.carbontesla.com/2016/01/download-ascend-mate-7-full-b331-lollipop-firmware-europe/
It seems to me that Huawei are still slowly releasing updates so I would rather sit on a stable LP and wait for the last MM rather than join the unhappy bunch of early flashers who have bugs or bricks.
B331 LP works well and can get some limited use of Xposed and full use of Viper4android.
You need to keep stock recovery to flash an update but unlocked bootloader is fine, so I'd look to unlock the bootloader after it gets B130 update.
It will have a choppy UI on KitKat, it's normal. Lollipop fixes that.
I reckon you'll last maybe 5 minutes trying to use the Huawei launcher. Don't fight that, just install another, lol. Have to go into settings and choose default launcher in the app management section.
RobboW said:
Will you be using an SD card? Slot 2 takes either an SD or a nano SIM, not both at once though.
That's the same ROM my phone came on. It's the standard international ROM for a non carrier locked TL10 goldie.
It will update to B130 OTA
From B130 I flashed mine to B331 Lollipop (newest lollipop). Just a download of ROM and place in dload folder and point the updater to it, then it does it from within the OS. It won't go past B130 on an OTA.
If you want MM, that needs to be loked at as there are stacks of vesions. I'm inclined to think if it can be flashed up to MM from B331 it's reasonably new. That's my aim. I won't go to an older LP to get up to a buggy old beta MM.
Here's the download link where I got my stable Lollipop.
http://www.carbontesla.com/2016/01/download-ascend-mate-7-full-b331-lollipop-firmware-europe/
It seems to me that Huawei are still slowly releasing updates so I would rather sit on a stable LP and wait for the last MM rather than join the unhappy bunch of early flashers who have bugs or bricks.
B331 LP works well and can get some limited use of Xposed and full use of Viper4android.
You need to keep stock recovery to flash an update but unlocked bootloader is fine, so I'd look to unlock the bootloader after it gets B130 update.
It will have a choppy UI on KitKat, it's normal. Lollipop fixes that.
I reckon you'll last maybe 5 minutes trying to use the Huawei launcher. Don't fight that, just install another, lol. Have to go into settings and choose default launcher in the app management section.
Click to expand...
Click to collapse
Awesome, thanks for your help! Since its saying "no updates available" should I manually update it to B130 and then to the link you provided for B331?
And yeah I've already got a launcher I've been using and like, I'm already sick of the stock launcher, lol. Also, strangely, the play store force closes after a few seconds of opening. I'm not too worried about it as I'll very soon be flashing different firmware, but still strange. Also, this is the MT7 L09 version, should I still update B130>B331?
And as far as Marshmallow is concerned I'm inclined to take your path with a stable Lollipop until they get MM all worked out.
Prozart said:
Awesome, thanks for your help! Since its saying "no updates available" should I manually update it to B130 and then to the link you provided for B331?
And yeah I've already got a launcher I've been using and like, I'm already sick of the stock launcher, lol. Also, strangely, the play store force closes after a few seconds of opening. I'm not too worried about it as I'll very soon be flashing different firmware, but still strange. Also, this is the MT7 L09 version, should I still update B130>B331?
And as far as Marshmallow is concerned I'm inclined to take your path with a stable Lollipop until they get MM all worked out.
Click to expand...
Click to collapse
L09, well that changes everything. You can go to B522 MM on that already. Update to B331, see how you like it. You can update to B522 from there anyway.
Google Play FC will be it trying to update itself whilst you're using it.
Check your ROM matches the number of the update. There are update notes included with it. If it doesn't match, it will fail to flash once most of the way through it. This is the CUST folder and is ROM specific for different areas of the world. It's where most naive users brick their phone.
For instance, mine is C900B331 and the original would have been C900B120SP04
That C900 is most important.
What many don't realise is that the number of the ROM doesn't always mean newer. It could be for a different region and that region has a different sequence of ROM designations.
RobboW said:
L09, well that changes everything. You can go to B522 MM on that already. Update to B331, see how you like it. You can update to B522 from there anyway.
Google Play FC will be it trying to update itself whilst you're using it.
Check your ROM matches the number of the update. There are update notes included with it. If it doesn't match, it will fail to flash once most of the way through it. This is the CUST folder and is ROM specific for different areas of the world. It's where most naive users brick their phone.
For instance, mine is C900B331 and the original would have been C900B120SP04
That C900 is most important.
What many don't realise is that the number of the ROM doesn't always mean newer. It could be for a different region and that region has a different sequence of ROM designations.
Click to expand...
Click to collapse
Thanks to you I successfully updated to B331. I got my launcher installed and now I just need to change the DPI as everything is huge, lol. So now I need to unlock bootloader and root it. But so far everything is smooth, no problems yet.
Edit: Quick question. I went into the APN settings and accidentally clicked on preferred network type. Before I went in there it was set to LTE (and I was successfully connected to LTE) but that wasn't an option to click on when I went into the settings. It's only showing me these three and so I'm not getting LTE anymore. Any ideas?
Check dual card settings for default 4G slot.
Edit: Why am I suggesting that for an L09, lol.
Have you done anything to upset the settings for APN?
Have a look in power saving settings to see if anything there cuts it back to 3G to save juice.
4G really sucks battery compared to 3G.
RobboW said:
Check dual card settings for default 4G slot.
Edit: Why am I suggesting that for an L09, lol.
Have you done anything to upset the settings for APN?
Have a look in power saving settings to see if anything there cuts it back to 3G to save juice.
4G really sucks battery compared to 3G.
Click to expand...
Click to collapse
I can't find anything i n the power settings regarding network modes, I believe the only thing I've changed is putting the power plan on Normal and turning off Power-intensive prompt.
Also on the keyboard, the keys aren't vibrating. I went into the keyboard settings and made sure it was turned on. Also tried toggling it off and on with no success. Are there any other vibration settings hidden somewhere that I'm missing?
I wonder if a factory reset is in order. Just to count out any leftovers. I do wonder though, if there is something funny about the bands the carriers allow to work in the US. I often see comments from US XDA members about bands. Like the US is really different than the rest of the world or something.
RobboW said:
I wonder if a factory reset is in order. Just to count out any leftovers. I do wonder though, if there is something funny about the bands the carriers allow to work in the US. I often see comments from US XDA members about bands. Like the US is really different than the rest of the world or something.
Click to expand...
Click to collapse
Yeah I may try that when I get home tonight. I need to unlock bootloader and root anyway so that'll wipe it. It's just so weird cause I had LTE up until the point when I went into settings and clicked on WDCMA or whatever and now there's no option to get back to LTE. It's also not connecting via bluetooth to my car. It had no problems connecting to my Moto 360, I don't know what would be different about my car. But it's not detecting it at all. Perhaps a factory reset would help solve that.
I spent about an hour last night reading up on unlocking the bootloader. I tried emailing Huawei and they directed me to log in to my Huawei account and I'd be able to get the code after 14 days. Is there any other way to do this? I mean I can survive a couple weeks without root, but it's not optimal, lol.
Don't root it yet and don't flash recovery.
Unlock the bootloader first. Read the following thread where I show the trick for getting your code easy and free.
http://forum.xda-developers.com/mate-7/general/bootloader-unlock-longer-anymore-t3296725
I've put mine back to stock B331 as much as possible tonight and flashed stock recovery then dirty flashed B331 back over it. About to factory reset it then attempt flashing Marshmallow.
Edit:
Reset went ok.
Edit:
Started the update, got to 96% and failed (CUST FAIL) and rebooted, sat on the start screen for quite a while and then booted. It's on C900B522 Marshmallow but I'm not sure what impact the cust fail has, but it seems to run fine. The dual card management settings are there so it is running as the TL10 that it is, although in settings it's calling itself a JAZZ.
RobboW said:
Don't root it yet and don't flash recovery.
Unlock the bootloader first. Read the following thread where I show the trick for getting your code easy and free.
http://forum.xda-developers.com/mate-7/general/bootloader-unlock-longer-anymore-t3296725
I've put mine back to stock B331 as much as possible tonight and flashed stock recovery then dirty flashed B331 back over it. About to factory reset it then attempt flashing Marshmallow.
Edit:
Reset went ok.
Edit:
Started the update, got to 96% and failed (CUST FAIL) and rebooted, sat on the start screen for quite a while and then booted. It's on C900B522 Marshmallow but I'm not sure what impact the cust fail has, but it seems to run fine. The dual card management settings are there so it is running as the TL10 that it is, although in settings it's calling itself a JAZZ.
Click to expand...
Click to collapse
I upgraded to 522 and so far it seems to be working well. Having some problems with Google Play Services (says it needs to update but the option isn't available in the play store) but otherwise seems great. Got LTE back and I've connected via Bluetooth to my car. I'm thinking about upgrading to 560 tonight. So I'm trying to follow your instructions on unlocking the bootloader but I don't understand where I need to go to type in the IMEI. I went to the website and logged in but then it takes me to this page (which doesn't seem to have an English version) and I have no idea where to go from there.
How to get work the Gear S3 on unsupported android devices with Gear App ->SOLVED!
I've thougt of this thread as a guide collection for anyone who has problems with the setup of his android phone by using a Gear S3
I had even pre-ordered the Gear S3, but it did not work with my Huawei MediPad / Honor X2, so I've already sent it back.
Also the Gear App is not shown in the Playstore, but I managed this by installing the .apk
(I think this is caused by the incorrect assignment as a tablet, but it's actually only a very large phone)
Bluetooth of the watch is recognized, however the Gear App crashes, when the watch will setup
But I can't accept this.
I would buy it a second time, if there is a way to make the Gear App work on the X2
(and other, not supported android devices, like the HTC 10)
So the behavior is identical to that described here:
http://forum.xda-developers.com/gear-s3/help/setup-gear-s3-frontier-htc-10-t3505529
or here
http://forum.xda-developers.com/showpost.php?p=69944929&postcount=54
or here
http://forum.xda-developers.com/showpost.php?p=69691127&postcount=25
SOLUTIONS
by @j to the 4n thankyou for this!
https://forum.xda-developers.com/showpost.php?p=70782233&postcount=41
https://forum.xda-developers.com/an...d-samsung-gear-app-android-n-samsung-t3547035
https://forum.xda-developers.com/showpost.php?p=70860684&postcount=36
https://forum.xda-developers.com/showpost.php?p=70681504&postcount=34
kajos said:
I've thougt of this thread as a guide collection for anyone who has problems with the setup of his android phone by using a Gear S3
I had even pre-ordered the Gear S3, but it did not work with my Huawei MediPad / Honor X2, so I've already sent it back.
Also the Gear App is not shown in the Playstore, but I managed this by installing the .apk
(I think, this caused by the wrong allocation as a tablet, it's actually only a very large phone)
Bluetooth of the watch is recognized, however the Gear App crashes, when the watch will setup
But I can't accept this.
I would buy it a second time, if there is a way to make the Gear App work on the X2 (and other, not supported android devices, like the HTC 10)
So the behavior is identical to that described here:
http://forum.xda-developers.com/gear-s3/help/setup-gear-s3-frontier-htc-10-t3505529
or here
http://forum.xda-developers.com/showpost.php?p=69944929&postcount=54
or here
http://forum.xda-developers.com/showpost.php?p=69691127&postcount=25
I now have a small idea, but I cant test it without the watch
In this video is shown, how to setup (Gear S2 ->S3 would be the same...):
?t=527
When Gear App crashed for me, here will be shown, that the app stops, while opening the Playstore for the Gear Plugin App
My suggestion, I havend tried:
I've installed the Gear Plugin App, before I setup the watch, along with the Gear App, but this was perhaps a mistake in this context.
Maybe setup will work, when Gear Plugin App is not already on the phone, when starting setup...
An other idea is to manipulate the build.prop, but I don't know the conditions of the Gear App ...
Has someone already found a solution and can be described here?
Click to expand...
Click to collapse
I have Gear S3
It was having exactly the same issue as you described of gear app force closes, I tried all different sequences whatever you thinking of as you mentioned.
My m8 custom rom is heavily tweaked to give most of HTC 10, so here is the similarity with HTC 10 people
So I restored my original unrooted backup and waooo it connect to gear S3, I'm enjoying now but no root no custom roms, may be will try another rom later.
It would be interesting, what kind of differences the build.prop shows between the m8 custom and the original.
Maybe, the key is buried there...
I read now, that a rooted phone prevented to connect the watch, especially also at the HTC10
Can someone confirm this?
And if so, how could you handle this?
Because of Samsung Pay I guess, it's not unlikely that root is undesirable
Yes, can confirm. HTC10 Viper 10.3
App crashes, when the watch will setup. Tried any installation sequences, but wasn't able to setup the Gear S3.
NOVodkA said:
Yes, can confirm. HTC10 Viper 10.3
App crashes, when the watch will setup. Tried any installation sequences, but wasn't able to setup the Gear S3.
Click to expand...
Click to collapse
I also had issues getting the Samsung Gear app installed on my HTC10 running Viper 3.5 (Android 6.0.1). I thought it was just because of Root, but I installed the Samsung Gear app on my Stock Rooted M8 and it worked perfect. So I then installed a stock port of rooted Android 7.0 and the Gear app installed fine. So it seems something in the custom ROM caused the app to not install.
For comparison I have a Verizon HTC 10, with a Dev Port of 7.0 rooted and the Samsung Gear app installed. I also have S Health and Samsung Pay working perfectly.
Ahowe125 said:
I also had issues getting the Samsung Gear app installed on my HTC10 running Viper 3.5 (Android 6.0.1). I thought it was just because of Root, but I installed the Samsung Gear app on my Stock Rooted M8 and it worked perfect. So I then installed a stock port of rooted Android 7.0 and the Gear app installed fine. So it seems something in the custom ROM caused the app to not install.
For comparison I have a Verizon HTC 10, with a Dev Port of 7.0 rooted and the Samsung Gear app installed. I also have S Health and Samsung Pay working perfectly.
Click to expand...
Click to collapse
Hi everyone, I can confirm that, It has nothing to do with root.
The connection of the Gear s3 works fine with the htc 10 and htc Stock installation.
Tested with Marshmallo and Nougat.
Maybe there are models and brands where the connection with the Gear s3 does not work even under stock installation, but that is different story.
There is something missing in custom roms.
I have now given up my favorite custom ROM, so I can use my watch with the phone.
Hopefully someone finds the solution, so it also works with custom roms.
I have logcats from both connection attempts, Custom rom and stock.
But I'm not an expert to read the logcat and find the Problem.
If someone has interest I can upload it .
There are obvious misunderstandings here!
I'm by no means concerned with identifying root as the main cause!
My only concern is to find the reason, or the concret causes for incompatibilitis or misbehavior of the gear app.
So my MediaPadX2 phone is completely stock, and it's only rooted, but Gear App crashes like described.
I would like to get the reason for this and find a solution.
If the issue is not caused by root, so all better (for me first)
Now we can summerize:
it is not necessarily to root, and does not occur only with some custom roms
So we are unfortunately not a step further.
But I'm still guessing that an unsatisfied query condition of the build.prop is the cause...
Toni10 said:
I have logcats from both connection attempts, Custom rom and stock.
But I'm not an expert to read the logcat and find the Problem.
If someone has interest I can upload it .
Click to expand...
Click to collapse
Unfortunately, I am also no expert
Hi guys,
I am new in this forum and hello to everyone
I have a xiaomi MI5 with the new rom nougat 6.12.15 from xiaomi.eu, it is impossible to connect a samsung gear S3 to a MI5 ?? when i open the gear app on the phone, it crashes and FC
Do you have a solution to make it work with the phone ??
Thank you
And merry christmas to all !!!
You had the Mi5 and the watch connected before the rom update?
Or did you buy the MI5 with nougat 6.12.15 so that it is all stock
You've problems with the pairing, too?
Maybe you have the possibility to compare with a working version on the same phone?
Please look, if there are differences of those parameters in the build.prop
http://ausdroid.net/howto/use-samsung-gear-fit-rooted-android-device/
I guess, that there would be a key to solve the pairing problems
https://forum.xda-developers.com/ht...tweaks-hub-t3379151/post69825479#post69825479
another log for anyone reading logs
Does someone get solution? I'm using HTC10 Android 7.0 Rooted (Viper 4.4 rom), the Samsung Gear app is forced close when pairing to S3.
According to this post by Leedroid, the Problem is the deodexed System.
Since he is a very experienced developer, I am sure he is right.
https://forum.xda-developers.com/showpost.php?p=70259624&postcount=646
From the first day I operated my phone with the Leedroid ROM and was very happy with it.
Now I reverted back to Stock ROM, to use the watch with the phone.
I don't think there is any other solution at the moment.
i don't think so!
My X2 has a odex stock rom 5.0, also some other stock shows the same issue
I guess that this idea a dead end, like some say the issue is caused by 7.. nougat...
kajos said:
i don't think so!
My X2 has a odex stock rom 5.0, also some other stock shows the same issue
I guess that this idea a dead end, like some say that has to be 7.. nougat...
Click to expand...
Click to collapse
Not entirely true.. I have the watch working on a Dev port of Android N for my HTC 10. Like others have stated, it would not work on a custom ROM like Viper. And that was when it was still on MM.
Sent from my HTC6545LVW using Tapatalk
And what does that prove?
kajos said:
And what does that prove?
Click to expand...
Click to collapse
In my situation I think it proves a few things. First, it doesn't seem like Root is an issue (as discussed earlier). Second, (in my situation) that something in a custom ROM causes issues. Either something with the build.prop as you have suggested, or something with the odex as others have said, but I have another theory.
What if it all boils down to which phones Samsung has deemed "compatible"? My HTC 10 is listed as compatible on the Samsung website, but maybe the identity of the phone is modified with the custom ROM?
I used this link related to the S2 to determine compatibility.
http://www.samsung.com/global/galaxy/gear-s2/device-compatibility/
I'm not a Dev, only a user who has basic understanding of how these things work, and can only report my situations in order to help others troubleshoot and hopefully find a way to enjoy this amazing watch.
Sent from my HTC6545LVW using Tapatalk
I just bought a new unlocked Verizon G920V phone from eBay to use with my Verizon prepaid account. (Well actually the hardware version under About Phone lists it as G920V.07). I can't say for sure if Marshmallow or Nougat shipped on this phone but it's currently running Nougat. As soon as I got it and it connected to my home wifi it wanted to update so I decided (maybe like an idiot) to let it. It appeared to download a giant file and flash itself a new firmware. This leads me to believe that it maybe shipped with Marshmallow but it obviously now has Nougat on it.
FWIW, I've rooted my own phones and a couple of my wife's phones in the past, but I'm by no means an expert. I'm fairly technically inclined in other areas of technology, but when it came to rooting various phones it amounted to carefully researching (usually through this site) and simply following a set of steps. I've always been successful. Long story short, I'm kind-of confused as to whether or not I can root. Like I said, I'm a bit confused, but it would appear that not only is there no root for the S6 running Nougat, but I believe I read where someone mentioned that Verizon released a security patch that prevents any sort of downgrading. Right after getting cellular service transferred the phone wanted to do a security patch so I assume that I've now got that patch installed as well.
So, can I downgrade this phone and root? I don't care about marshmallow I'll go to version 5 (whatever wonky name that one is called) if I have to. I would really just like to get root on this phone. Mainly so I can block ads more effectively and try to milk more battery life out of this thing because the battery life is horrible in my opinion.
Also FWIW, the software build/baseband number is G920VVRS4DQE1 if that helps or matters.
Anyway, this long-time lurker but first-time poster thanks you in advance for any replies.
It's been a few days and no replies, but from the additional information I've found since posting, I'm thinking that root ain't gonna happen. At this point I don't think it's even possible to roll back to an earlier version. Oh well I'll just live with this phone for awhile. I really like the phone despite not being able to get root. I suppose I'll just live with ads.
You can go to Samsung apps, if you have a Samsung account and download there ad block app. That is what I am using. It under Galaxy apps that came with phone
Sent from my Verizon Samsung Galaxy S6 using XDA Labs
You actually can downgrade your firmware should you so desire. The following two threads have links to firmwares flashable via odin.
https://forum.xda-developers.com/ve...20vvrs4dqd1-odin-nougat-7-0-firmware-t3597007
https://forum.xda-developers.com/verizon-galaxy-s6/general/downgrade-6-0-1-to-5-1-1-t3489816
At this point I don't think you can downgrade any lower than the OK7 firmware.
Hello,
Long time i didn t buy a new phone ( i am still on s9+) and there where a lot of rom for the s9+, but doesn t seem to find them for the s21+.
Where are they ?
I believe more people aren't interested to root, unlock bootloader and create custom roms. One of reasons you lost warranty, secondly you lost google pay, samsung pay, secure folder etc. No Updates OTA. And many more. Yes you can fix some of them by custom kernel or Magisk Hide etc. And android in nowadays is enought good. So are you interested in this?
@Itadiki What are you missing from OneUI? What would you want from a custom ROM that you don't have in the official ones?
As @Nettwerk was saying, nowadays OEM Android is good enough even for most of the people that in the past would run a custom ROM. So custom ROMs make little to no sense. Put the disadvantages on top (like loss of warranty or functionalities) and you get the current situation.
@Nettwerk My s9 was rooted and I still had access to google pay. We don t have samsung pay and never used secure folder but I don t see the reason why it would not work
As For @daniel_loft The same reason I wanted my all other devices rooted. Faster speed, no bloatware, optimization in general, and discover a lot of possibilities I didn t think about with all rooted software than can customize everything.
I can root the device myself, Remove the bloatware, install xposed framework and lots of other tools myself. But I am lazy, and not as knowledgable as the excellent people who spend hours and hours on giving us a way better rom than the stock one.
Yes the loss of warranty is a risk I am willing to take.
Secure folder checks knox. If efuse is trigered than it doesn't work. If I'm not wrong.
daniel_loft said:
@Itadiki What are you missing from OneUI? What would you want from a custom ROM that you don't have in the official ones?
As @Nettwerk was saying, nowadays OEM Android is good enough even for most of the people that in the past would run a custom ROM. So custom ROMs make little to no sense. Put the disadvantages on top (like loss of warranty or functionalities) and you get the current situation.
Click to expand...
Click to collapse
Custom roms are always a good option , they lead to many innovations that with time and popular demand are later integrated in official rom , my last two phone i have not rooted them , i have not missed a thing from not doing it either.
If you root you will miss out in Samsung pay or google pay but of course it may not be important to everyone
Itadiki said:
Hello,
Long time i didn t buy a new phone ( i am still on s9+) and there where a lot of rom for the s9+, but doesn t seem to find them for the s21+.
Where are they ?
Click to expand...
Click to collapse
Hi
I found one .
Hi,
there is a very good one for S21 Ultra -> https://drketanrom.com/samsung-s21ultra
TeLMiT92 said:
Hi,
there is a very good one for S21 Ultra -> https://drketanrom.com/samsung-s21ultra
Click to expand...
Click to collapse
yes I saw it ... but not for S21+ unfortunately
daniel_loft said:
@Itadiki What are you missing from OneUI? What would you want from a custom ROM that you don't have in the official ones?
It's not what's missing...it's what I *want* missing....I really want to get rid of the Bloat...nd fix a couple of issues that are plaguing my current s10+ (like the fact that any streaming is interrupted if *any* other resident program is in front of it, and needs an update....my Music cuts out when Waze needs to check in, for example (every 5 minutes).... and T-Mobile swears there is nothing wrong. (...then why did it start doing this *after* a forced Update that they refuse to roll-back?)
Click to expand...
Click to collapse
I could go on...but it's not additional functionality...it's control of my device (If I wanted to be told how to use my phone...I'd get an iPhone *ecccchh*)
Itadiki said:
Hello,
Long time i didn t buy a new phone ( i am still on s9+) and there where a lot of rom for the s9+, but doesn t seem to find them for the s21+.
Where are they ?
Click to expand...
Click to collapse
I know what you mean.
I remember back in the day when I had an HTC One X (still my favourite phone even though I got an s21) then later the M8 and there were tons of roms and mods available from a range of creators. My fav rom was the Viper range which had tons of features like tap to wake and customisable themes which didn't appear on official android for years and had OTA updates which got you on the latest android version before official release.
But I think, as said above, nowadays android has progressed to the point that you don't need to root to get roms with missing features and the likes of Samsung update their phones much faster than they used to. Even I haven't installed a custom rom since the S8 (the S6 & One M9 were the last ones I rooted. And the M9 was only to remove htc bloatware). And though rooting is still useful for removing baked in apps you don't need (Samsung, I'm looking at you!) but in general it's not needed anymore. Especially since manufacturers seem to have got 'inspiration' (interpret that as you will) from some of the fantastic indipendent developers found on sites like XDA.
The other problem is that these days more people use their phones for banking and paying in store and these functions are blocked on rooted phoned.
It is a shame though, the creativity, diversity of mods and general level of knowledge that was once found here back then was amazing.
That's not to say there isn't great talent still here, there is, simply back then there were much more developers creating full roms.
FerretPD said:
I could go on...but it's not additional functionality...it's control of my device (If I wanted to be told how to use my phone...I'd get an iPhone *ecccchh*)
Click to expand...
Click to collapse
Totally agree with you here.
This was once a clear distinction between android and iPhone. These days they are all trying to suck you into their own eco system.
What's funny is that on my Huawei Nova 5t I had much more control of an apps access to my data and no apps were 'baked in' like Samsung pay etc. We should not have to root a phone we own to remove apps we don't want or make changes to the functionality of a phone, especially after we have paid hundreds of £/$ or more for.
i like root for Root level Backup, Host File level adblocking see wakelocks, change CPU/GPU underclock/overclock/undervolt.. And to keep upgrading my phone to new versions long after the manufacturer stops providing updates.
I am looking at a S22.. though if no community support then maybe not..
Sage said:
i like root for Root level Backup, Host File level adblocking see wakelocks, change CPU/GPU underclock/overclock/undervolt.. And to keep upgrading my phone to new versions long after the manufacturer stops providing updates.
I am looking at a S22.. though if no community support then maybe not..
Click to expand...
Click to collapse
unless u buy an exynos s21, u'll be able to root and do whatever... but if u buy a qualcomm one., u wont be able to root, unless u pay... i suggest to stay away from samsung (qualcomm) if u're into the rooting scene
efebe said:
unless u buy an exynos s21, u'll be able to root and do whatever... but if u buy a qualcomm one., u wont be able to root, unless u pay... i suggest to stay away from samsung (qualcomm) if u're into the rooting scene
Click to expand...
Click to collapse
i avoid snapdragon like plague for some years already since the inability to root/titanium backup. as long as the phone can't be rooted, i don't buy it, even exypnos is hotter slower dumber etc but the freedom to block ads and freeze/unfreeze/backup app is totally unmatched. also nowadays there's knoxpatch module so i can pretty much use any samsung secured function (just lack samsung pay/pass)