Hello! Just god my phone out of service today (screen replacement) and I saw that the capacitive buttons weren't working all the time. I looked up on the internet and found an option (dial *#2663#) and it'll open up a menu. From there, you can see 2 important things that leads to this problem.
Phone's Touch key FW version :0x10
Part's Touch key FW version : 0x06
When I press on the Touch key FW update, a popup message appears on the screen saying (Now Updating... Warning! Do not turn off!). Because of multi-tasking I can use the phone at the same time and when this message is showed, the capacitive buttons are working without problem. The thing is, the message never disappears so it never completes the update. I've changed to stock GS4 ROM but still the same. Any help? Tried looking up on the internet but didn;t find anything useful.
Thank you!
P.S: Btw, they are working fine in Recovery mode. Isn't there anyway to restore the keys' FW to default? Also the Phone's FW is bigger than the Part's shouldn't they be reversed? I'm really desperate, thanks...!
P.P.S: Not only in recovery, but also on CM 12 (lollipop) it works without problems. What should I do? I don't really want to use CM my whole life, I'm more into TW.
Just did more "testing" on CM it is ok on the launcher, but it also has problems while being in some apps like internet they are pressed by themselves. How can I upgrade/downgrade the touch FW, I found some posts but they were htc only. I can't believe no1 knows what to do on here. help please
Have you tried kies?
Or
Install an older official samsung rom (like the one before the latest update) and then upgrade using ota.
Hopefully this will also upgrade any older firmware.
Ok, so after hours of pain, I ended up downgrading from HOA7 ROM (Lollipop) to 4.2.2. It took me some time, but meh... Anyway, after the downgrade, I accessed the same menu again, and the update for key FW have finished this time. I restarted the device, but it was still 0x10 and 0x6, nothing had changed. What should I do now?
dgcyears said:
Ok, so after hours of pain, I ended up downgrading from HOA7 ROM (Lollipop) to 4.2.2. It took me some time, but meh... Anyway, after the downgrade, I accessed the same menu again, and the update for key FW have finished this time. I restarted the device, but it was still 0x10 and 0x6, nothing had changed. What should I do now?
Click to expand...
Click to collapse
When I said update using ota, I was talking about the rom.
The firmware for the touch keys should come bundled with the update.
And I didn't mean you to downgrade as far as jellybean. Some older kitkat build would've sufficed.
Try updating the rom to the newest variant using that OTA. If it works.
Also, the dialer code doesn't work on my lollipop GPE rom.
GDReaper said:
When I said update using ota, I was talking about the rom.
The firmware for the touch keys should come bundled with the update.
And I didn't mean you to downgrade as far as jellybean. Some older kitkat build would've sufficed.
Try updating the rom to the newest variant using that OTA. If it works.
Also, the dialer code doesn't work on my lollipop GPE rom.
Click to expand...
Click to collapse
Hey! Thanks for your answer again! I know you didn't mean jelly bean, but I had troubles downgrading from lollipop (damn bootloader). Just finished installing Kies, will come back with a follow up. Thanks again!
Btw, which method would you recommend me more, OTA or Kies?
Both get their updates from samsung, I guess. So I don't think it matters.
But my instinct tells me to use OTA
Ok, then I need to fix the Wi-Fi first, flashing NON-HLOS.bin and modem.bin didn't help atm.
I can't find a way to fix the Wi-Fi on this version. Should I go for Kies?
dgcyears said:
I can't find a way to fix the Wi-Fi on this version. Should I go for Kies?
Click to expand...
Click to collapse
Obviously
Damn, this thing really pisses me off. Kies 2.6 is stuck at "connecting" and kies 3 says it's not supported (4.2.2). O.O
dgcyears said:
Damn, this thing really pisses me off. Kies 2.6 is stuck at "connecting" and kies 3 says it's not supported (4.2.2). O.O
Click to expand...
Click to collapse
It doesn't matter. There my be a fatal flaw in this idea.
The phone's firmware version might be provided by samsung, but the part's firmware version is provided by the manufacturer. And I don't know if samsung manufactured that.
Are you sure it not a hardware issue?
You said that they replaced the screen. Are you talking about the glass only?
The digitizer is connected to the motherboard (and I guess that's where the firmware for it is stored) So there shouldn't be any reason why it would have a different version if you replace just the glass.
It was the entire screen (LCD/Digitizer too). In recovery, the buttons work perfectly.
dgcyears said:
It was the entire screen (LCD/Digitizer too). In recovery, the buttons work perfectly.
Click to expand...
Click to collapse
The firmware seems to be stored on a partition that is not affected by changing roms. That's why it is the same even after all this rom flashing.
Even if it is in recovery, it uses the same firmware.
I would check mine but I can't since that code doesn't work.
Yea, I know, it only works on stock. Am I able to change it somehow?
dgcyears said:
Yea, I know, it only works on stock. Am I able to change it somehow?
Click to expand...
Click to collapse
It works on stock samsung firmware but not on any touchwiz based roms?
It works on stock, but on TouchWiz based ROMs as well.
dgcyears said:
It works on stock, but on TouchWiz based ROMs as well.
Click to expand...
Click to collapse
Ahh, wait. I thought you're talking about the buttons. But you were talking about code.
Yes, I was talking about the codes . As for the buttons, they work flawlessly in 2 cases: 1. In recovery and 2. When I enter the menu by typing that code and choosing to update the touch key's FW.
I think this is what I'd need. The bad thing is that this is for nexus. http://forum.xda-developers.com/showthread.php?t=2800308
Related
hello everyone hope someone can help I did the update for the 4.3 and a few days I realized that sometime I'm trying to make calls or receive calls and there's no sound no out And no in on the other side is answering but no sound either he doesn't hear me I don't hear him either and what I have to do is reset the phone mains take the battery off and put it back and turn it back on And it works again and tell it's happening again this is driving me nuts because it can happen twice a day by the way my phone is flashed to boost mobile and this is a sprin Phone Everything works beautiful until the last update: thank you guys hope someone can help
Not nearly enough info to help.
you say you
did the update for the 4.3
Click to expand...
Click to collapse
.
Question is HOW? - via OTA? via flashing ROM from dev section? If you flashed a ROM, which one? And how did you do it - steps you took.
leaderbuilder said:
Not nearly enough info to help.
you say you .
Question is HOW? - via OTA? via flashing ROM from dev section? If you flashed a ROM, which one? And how did you do it - steps you took.
Click to expand...
Click to collapse
I didn't do anything or changing the Rom the phone was flashed 7 months ago I never have problems I just lately I did the update for the 4.3 and I start having those problems that's why I was checking if there is any issue with the update and if you recommend to do anything I would love to know thank you for the response
and if you think to go back to the 4.2 will Help and how can I do it thanks
eli7477 said:
I didn't do anything or changing the Rom the phone was flashed 7 months ago I never have problems I just lately I did the update for the 4.3 and I start having those problems that's why I was checking if there is any issue with the update and if you recommend to do anything I would love to know thank you for the response
and if you think to go back to the 4.2 will Help and how can I do it thanks
Click to expand...
Click to collapse
Okay.
Again I'm still not quite getting what you did.
So I'll assume that when you say,
I did the update for the 4.3
Click to expand...
Click to collapse
you mean you took the Over The Air update - the one from Sprint; your phone says Firmware update available.... etc.
IS THAT CORRECT?
If so you CANNOT go back to 4.2 period. End of story on that route.
You can however, If my above assumption is correct, and you didn't apply the update in some other way re-flash MJA or flash a custom ROM. For that you'll need to root your phone (CF-Autoroot works), install custom recovery (for 4.3 Philz is the one to use) and then flash the ROM as per the developers instructions.
leaderbuilder said:
Okay.
Again I'm still not quite getting what you did.
So I'll assume that when you say, you mean you took the Over The Air update - the one from Sprint; your phone says Firmware update available.... etc.
IS THAT CORRECT?
If so you CANNOT go back to 4.2 period. End of story on that route.
You can however, If my above assumption is correct, and you didn't apply the update in some other way re-flash MJA or flash a custom ROM. For that you'll need to root your phone (CF-Autoroot works), install custom recovery (for 4.3 Philz is the one to use) and then flash the ROM as per the developers instructions.
Click to expand...
Click to collapse
Thank you I will work on it I will let u know
I have Verizon Galaxy Note 3, and my problem is that Wifi button is greyed out and simply wouldnt turn on.
I have done a lot of homework so far, and before, I had 4.3 Jelly Bean, and Wifi being greyed out started around 2 weeks ago (early Dec/2014 - until then, it worked fine).
So I updated to 4.4.2 Kitkat thinking software issue, but wifi is still not working.
I had already searched for hours, and did many things to try to isolate the problem.
*I tried Safe mode
*Reset Cache/Factory several times
*Battery in-n-out, SD card in-n-out, any external peripherals i had alrdy taken everything off and tried
*Tried Alliance/Jasmine/Eclipse ROMs, but still same
*Not router issue @ home since Phone Wifi simply wouldn' turn on
I thought of downgrading back to 4.3 Jelly Bean, but there were many articles saying I can not downgrade, so I think it's out of option.
I now think it's hardware issue, but can not confirm... went to Verizon store too, and the guy just feels it's more software by 51/49, but the ultimate problem is that I just can not 100% ID what the exact problem is - software or hardware.
I really don't want to spend $ for another phone... I also feel it is Kitkat since I also found many articles with Note 3 Kitkat wifi problem, and I read a lot of them, but couldn't really find any solution to my specific issue.
My understanding is that I have 2 options - wait for proper fix by Dev/Samsung for Kitkat firmware or get a new phone
I really did everything I can within my power, and making this post is my last resort...
Hope I can shed some light from experts or anyone who knows any more beneficial details so that @ least i can try to sort my options and situation more clearly...
Thanks much in advance!
Have you tried using Samsung Kies to return to complete stock? Why didn't the Verizon tech offer this choice and flash stock firmware?
My guess is you have a baseband/firmware mismatch somewhere. 4.4.2 firmware and baseband can be found in this thread.
Or flash nc4 in odin.
KennyG123 said:
Have you tried using Samsung Kies to return to complete stock? Why didn't the Verizon tech offer this choice and flash stock firmware?
My guess is you have a baseband/firmware mismatch somewhere. 4.4.2 firmware and baseband can be found in this thread.
Click to expand...
Click to collapse
mmm no, and i got this phone from Amazon (not from Store), and the store workers really didnt know how to Root nor XDA forum, so it was talking to a wall...
Lemme check our your link and see
Gl2u81 said:
mmm no, and i got this phone from Amazon (not from Store), and the store workers really didnt know how to Root nor XDA forum, so it was talking to a wall...
Lemme check our your link and see
Click to expand...
Click to collapse
ok, i did already check out your thread before, and when i had tried to download 4.3 (1st one), it had me download like .exe file, and these kind of files tend to be virus/spyware so i just didn't... i also read many posts about how i can NOT downgrade to 4.3 from 4.4 so software wise, my current understanding is that I am **** out of luck until someone fixes firmware... or am i wrong? I guess I am trying to be proven wrong, and hope someone can show me a solution to my weird unique problem...
Btw, already on NC4 (I had updated to NC2 firstly, and Jasmine got stuck on bootloop, so I got NC4 and used Odin, then it fixed the bootloop)
Merry Xmas, huh?
P.S. Thanks for replying on Xmas day, lol
Correct you can not downgrade. Flash nc4 in odin.
https://www.androidfilehost.com/?fid=23487008491963309
Gl2u81 said:
mmm no, and i got this phone from Amazon (not from Store), and the store workers really didnt know how to Root nor XDA forum, so it was talking to a wall...
Lemme check our your link and see
Click to expand...
Click to collapse
You specifically stated in the OP that you went to the Verizon store. They should have just flashed the most recent firmware/OS at that time.
You need to just Odin the latest stock tar or use Kies to do the same. Somewhere along the way the baseband, firmware and ROM OS have been mixed which causes the wifi problem.
drewcam888 said:
Correct you can not downgrade. Flash nc4 in odin.
https://www.androidfilehost.com/?fid=23487008491963309
Click to expand...
Click to collapse
Yes, running nc4 right now
KennyG123 said:
You specifically stated in the OP that you went to the Verizon store. They should have just flashed the most recent firmware/OS at that time.
You need to just Odin the latest stock tar or use Kies to do the same. Somewhere along the way the baseband, firmware and ROM OS have been mixed which causes the wifi problem.
Click to expand...
Click to collapse
Yes i did go, and i feel we are getting somewhere...
iam not like total expert on micro details on flashing, but from what i understand, baseband version and firmware are same, and firmware is like BIOS for computer while ROM is like Windows, Linux or an Operating System.
so wut i understood is that u are saying that my firmware (BIOS) and ROM (OS) are incompatible?
http://forum.xda-developers.com/showthread.php?t=2553357
I am running this Alliance rom, and also NC4 i got from XDA forum for my phone... so i think I am on Kitkat firmware running ROM that was made to run on this firmware?
Please point anything out to me if i had something wrong - open to anything to try to resolve this so that i dont have to dump $ for another phone...
Gl2u81 said:
Yes, running nc4 right now
Yes i did go, and i feel we are getting somewhere...
iam not like total expert on micro details on flashing, but from what i understand, baseband version and firmware are same, and firmware is like BIOS for computer while ROM is like Windows, Linux or an Operating System.
so wut i understood is that u are saying that my firmware (BIOS) and ROM (OS) are incompatible?
http://forum.xda-developers.com/showthread.php?t=2553357
I am running this Alliance rom, and also NC4 i got from XDA forum for my phone... so i think I am on Kitkat firmware running ROM that was made to run on this firmware?
Please point anything out to me if i had something wrong - open to anything to try to resolve this so that i dont have to dump $ for another phone...
Click to expand...
Click to collapse
In your phone settings, what does it say in about phone for baseband and software versions? It should all end in NC4 then.
I directed you to a link for nc4 then flash in odin. That is the correct step to try right now
Gl2u81 said:
Yes, running nc4 right now
Yes i did go, and i feel we are getting somewhere...
iam not like total expert on micro details on flashing, but from what i understand, baseband version and firmware are same, and firmware is like BIOS for computer while ROM is like Windows, Linux or an Operating System.
so wut i understood is that u are saying that my firmware (BIOS) and ROM (OS) are incompatible?
http://forum.xda-developers.com/showthread.php?t=2553357
I am running this Alliance rom, and also NC4 i got from XDA forum for my phone... so i think I am on Kitkat firmware running ROM that was made to run on this firmware?
Please point anything out to me if i had something wrong - open to anything to try to resolve this so that i dont have to dump $ for another phone...
Click to expand...
Click to collapse
You have lots of things wrong in the above. So to keep it simple just get OFF of the alliance ROM, get back on the NC4 ROM and modem. If nothing else...go back to the Verizon store and have them totally wipe and reflash the phone. You can also do that at the Samsung section of a Best Buy store.
Sent from my Note 3 via Tapatalk
KennyG123 said:
In your phone settings, what does it say in about phone for baseband and software versions? It should all end in NC4 then.
Click to expand...
Click to collapse
baseband ends in nc4 and base version also nc4...
drewcam888 said:
I directed you to a link for nc4 then flash in odin. That is the correct step to try right now
Click to expand...
Click to collapse
I successfully flashed this via Odin, but wifi is still an issue... and safestrap 3.75 doesnt work any more
Gl2u81 said:
I successfully flashed this via Odin, but wifi is still an issue... and safestrap 3.75 doesnt work any more
Click to expand...
Click to collapse
If you successfully flashed Odin and factory reset the phone (important), and tried wifi immediately after and it still will not turn on (without adding anything else) then it must be some hardware failure.
KennyG123 said:
If you successfully flashed Odin and factory reset the phone (important), and tried wifi immediately after and it still will not turn on (without adding anything else) then it must be some hardware failure.
Click to expand...
Click to collapse
yeah... wifi doesnt turn on... i'll settle as hardware issue, not software and move on with my life...
Warranty replace it and be done.
I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...
Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.
BNerd89 said:
Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.
Click to expand...
Click to collapse
No mate tried all that, makes no difference. Even in safe mode its still behaves the same. And installed stock firmware many times, also without battery too. No improvement. Even the stock recovery isn't installed, thats the biggest question i have in that process.
malakalofung said:
I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...
Click to expand...
Click to collapse
Have you tried to update the firmware of the touchscreen? Enter *#2663# into the dialer with your S pen and then click TSP FW Update.
Oh my God. Bro u saved my life. Thank you so much for replying and suggesting this. U r post was the 1st thing I read and did and it worked. Thanks man. Thanks so very much. U don't know how delighted I am now. Thank you again.....
Sent from my SM-N910G using XDA Free mobile app
Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk
coolfire said:
Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Well im sure i followed the process right but now i doubt it used an incorrect file (CWM) to flash on odin, which caused this. Anyhow thank God its fine now lol. I Was literally in tears man. Ha ha
I can totally understand how you felt. Glad all is great now!
Sent from my SM-N910G using Tapatalk
This problem has nothing to do with rooting or installing a custom recovery. Only when upgrading or downgrading firmwares the touchscreen firmware can sometimes bypass the update.
Good one... Hackberrybold
I've been trying some AOSP Roms and Note 5 Roms to see what kind of features I like. I've gone back to Stock, as several Apps I like don't work in Custom and I'm due for an upgrade soon. I have SM-N900W8 (Canada\Telus).
My Back Key doesn't work and my menu button is doing SFinder stuff instead in Lollipop. Here is the messed up part. If I restore back to KitKat, no issues, but even if I upgrade to Lollipop from Kit Kat, issue comes back. I've tried OTA, ODIN Flash, and Samsung Switch\Kies, nothing. If I go back to custom ROM (Most were Darklord Note 5 base, all really good work). The soft keys work.
Be aware I'm still learning the ropes here. I even used Odin to wipe my EFT and NAND my data partition, still nothing. I'm out of ideas. Can anyone point me the right way?
R2pclaw said:
I've been trying some AOSP Roms and Note 5 Roms to see what kind of features I like. I've gone back to Stock, as several Apps I like don't work in Custom and I'm due for an upgrade soon. I have SM-N900W8 (Canada\Telus).
My Back Key doesn't work and my menu button is doing SFinder stuff instead in Lollipop. Here is the messed up part. If I restore back to KitKat, no issues, but even if I upgrade to Lollipop from Kit Kat, issue comes back. I've tried OTA, ODIN Flash, and Samsung Switch\Kies, nothing. If I go back to custom ROM (Most were Darklord Note 5 base, all really good work). The soft keys work.
Be aware I'm still learning the ropes here. I even used Odin to wipe my EFT and NAND my data partition, still nothing. I'm out of ideas. Can anyone point me the right way?
Click to expand...
Click to collapse
Hey im in the same boat as you, and was doing the same things as you, have you found a fix?
lilr said:
Hey im in the same boat as you, and was doing the same things as you, have you found a fix?
Click to expand...
Click to collapse
Not Entirely, but I found a Work Around. If I get back to Lollipop, reroot (I use TWRP and SuperSU), and then install a Custom Kernel (I've tested LeanKernel and Arter97), then it works again. I'm going to now try to reflash back to Stock Kernel later this week, and test the results.
Update: Reflashed Stock Kernel provided here: http://forum.xda-developers.com/galaxy-note-3/general/direct-download-bootloaders-modems-t3258803 (Thanks to @jcadduono , very convenient) and same issue, back to Arter97 or Lean Kernel for now. Hoping someone has a fix soon.
I just made a post. Did not see this one. I'm having the same issue
Sent from my SM-N900W8 using XDA Free mobile app
Soft brick maybe?
R2pclaw said:
I've been trying some AOSP Roms and Note 5 Roms to see what kind of features I like. I've gone back to Stock, as several Apps I like don't work in Custom and I'm due for an upgrade soon. I have SM-N900W8 (Canada\Telus).
My Back Key doesn't work and my menu button is doing SFinder stuff instead in Lollipop. Here is the messed up part. If I restore back to KitKat, no issues, but even if I upgrade to Lollipop from Kit Kat, issue comes back. I've tried OTA, ODIN Flash, and Samsung Switch\Kies, nothing. If I go back to custom ROM (Most were Darklord Note 5 base, all really good work). The soft keys work.
Be aware I'm still learning the ropes here. I even used Odin to wipe my EFT and NAND my data partition, still nothing. I'm out of ideas. Can anyone point me the right way?
Click to expand...
Click to collapse
I think this might have to do with soft bricking the device, because I updated my rooted n900w8 from 4.4.3 (If im remembering correctly) to 5.0 while still rooted and ended up softbricking it. I think. But I also had to mess around with the BL, AP, and CSC to get it working again. could it be because of that ? has anyone else dealt with this as well?
I've posted my solutions here
rocked_out said:
I've posted my solutions here
Click to expand...
Click to collapse
Thank you so much, rocked_out! that worked for me!
Hey guys, I have been out of the android world for a couple of years, I would appreciate some guidance.
I I'm currently living in US
T-mobil
Model number: SM-G935T
Android version: 6.0.1
Updated right now
So my question is, since I don't have any backup or anything, can someone provide me with the steps to get me started? Like what post to root it on this specific carrier and how everything? please
Thanks
Arturofm2 said:
Hey guys, I have been out of the android world for a couple of years, I would appreciate some guidance.
I I'm currently living in US
T-mobil
Model number: SM-G935T
Android version: 6.0.1
Updated right now
So my question is, since I don't have any backup or anything, can someone provide me with the steps to get me started? Like what post to root it on this specific carrier and how everything? please
Thanks
Click to expand...
Click to collapse
Of course we can get your started but see
But first you must answer us these question three.
Why do you want root?
Do you have a computer? (This is a must for root.)
Are you ready to be disappointed?
https://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
follow this (use odin to flash rooted kernel) ......you should search before posting things like this.....google is your friend bro.
GOOD LUCK - BTW use flash fire app in play store to make backups and flash roms
Okay okay.
A quick glance at T-Mobile Samsung Galaxy S7 Edge Guides, News, & Discussion would have led you to the "How to root the S7 EDGE" thread.
I'd take a look in there if I were you.
Binary100100 said:
Of course we can get your started but see
But first you must answer us these question three.
Why do you want root?
Do you have a computer? (This is a must for root.)
Are you ready to be disappointed?
Click to expand...
Click to collapse
Well while I was waiting I just rooted it. So what do you think that would be the next step towards installing a rom? To answer your survey questions :laugh: :
1- Because a phone without being rooted is like a bird without wins.
2- I do
3- Oh well... tell me more
Arturofm2 said:
Well while I was waiting I just rooted it. So what do you think that would be the next step towards installing a rom? To answer your survey questions :laugh: :
1- Because a phone without being rooted is like a bird without wins.
2- I do
3- Oh well... tell me more
EDIT: I just checked and the root didn't go through... even though ODIN said it was successful
Click to expand...
Click to collapse
Well then.
Rooting the phone (as I'm sure you had already found out) was fairly easy.
BUT... since we do not have an unlocked bootloader then we cannot have any custom recovery. Which means we can only (for now) use adb and Fireflash to flash any custom firmwares. And while we're on the subject of that... there is only one custom rom. Well... technically there are two but only one for you since you updated to the latest firmware.
Echoe ROM which was updated (ummm...) September 9th (not including the Verizon version which might work but with no promises)
Tekxv2 which was updated back in July. Unfortunately, that is flashed by adb (computer required) and only supports G935TUVS3APD8 which is... pretty old.
Things that you may notice with root.
Battery life may be shorter.
Strange icons on your status bar.
Might start to have random reboots for absolutely no reason.
Can't use Samsung Pay and some other apps.
Phone might be laggy.
Phone might feel hot.
Some of those can be resolved by flashing the only custom rom that we have (Echoe ROM... which is a rather nice rom) but it's not "there" yet.
Or you can use the guide in my signature to resolve issues like the lag and the strange icons. Yet even after the "fix" you might still experience both again from time to time.
You might even have the IMS force close issue which I used to get about once a month. It would piss me off because no sooner that you click the button, it'll pop up again and you don't have time to do anything. You're pretty much forced to reflash stock, wipe, re-root, restore a latest backup... which can take hours and is rather inconvenient if it happens to you while you're at work like it always seemed to happen for me.
SO...
All in all... root is okay. It's better than nothing I suppose. But until we get more developer support for this phone then in my opinion it's kinda pointless in my opinion.
Too many drawbacks. I eventually unrooted two weeks ago and I love my phone now. I'm using the heck out of Samsung Pay especially since their promotions are pretty nice right now! Plus a few members are testing the Nouget update which probably won't be getting root at all since rooting requires an engineering kernel which we don't have and might not get. Or an unlocked bootloader which we've pretty much given up on.
A lot of members that are testing the Nouget beta firmware are extremely satisfied with it so if we can't root Nouget then having a rooted S7 will probably fade away as more people update to Android 7+. That's where I see this going anyway.
Binary100100 said:
What you wrote above
Click to expand...
Click to collapse
So for what I understood the dev support for this phone is very limited... I know the issues I may encounter, I had them with the galaxy note. but any way... If something I'll unroot it but I want to try it out Thank for you time. I've rooted it.
EDIT: Damn... I really don't like the visual style of Echoe... is that one the only one I can flash??
Binary100100 said:
Well then.
Rooting the phone (as I'm sure you had already found out) was fairly easy.
BUT... since we do not have an unlocked bootloader then we cannot have any custom recovery. Which means we can only (for now) use adb and Fireflash to flash any custom firmwares. And while we're on the subject of that... there is only one custom rom. Well... technically there are two but only one for you since you updated to the latest firmware.
Echoe ROM which was updated (ummm...) September 9th (not including the Verizon version which might work but with no promises)
Tekxv2 which was updated back in July. Unfortunately, that is flashed by adb (computer required) and only supports G935TUVS3APD8 which is... pretty old.
Things that you may notice with root.
Battery life may be shorter.
Strange icons on your status bar.
Might start to have random reboots for absolutely no reason.
Can't use Samsung Pay and some other apps.
Phone might be laggy.
Phone might feel hot.
Some of those can be resolved by flashing the only custom rom that we have (Echoe ROM... which is a rather nice rom) but it's not "there" yet.
Or you can use the guide in my signature to resolve issues like the lag and the strange icons. Yet even after the "fix" you might still experience both again from time to time.
You might even have the IMS force close issue which I used to get about once a month. It would piss me off because no sooner that you click the button, it'll pop up again and you don't have time to do anything. You're pretty much forced to reflash stock, wipe, re-root, restore a latest backup... which can take hours and is rather inconvenient if it happens to you while you're at work like it always seemed to happen for me.
SO...
All in all... root is okay. It's better than nothing I suppose. But until we get more developer support for this phone then in my opinion it's kinda pointless in my opinion.
Too many drawbacks. I eventually unrooted two weeks ago and I love my phone now. I'm using the heck out of Samsung Pay especially since their promotions are pretty nice right now! Plus a few members are testing the Nouget update which probably won't be getting root at all since rooting requires an engineering kernel which we don't have and might not get. Or an unlocked bootloader which we've pretty much given up on.
A lot of members that are testing the Nouget beta firmware are extremely satisfied with it so if we can't root Nouget then having a rooted S7 will probably fade away as more people update to Android 7+. That's where I see this going anyway.
Click to expand...
Click to collapse
How are you doing with the ads? Like youtube, pandora, spotify? I just installed xposed and the phone feels very hot, and If I unroot it (which I'm thinking to do) I won't be able to get things without ads (I know about vpns and browsers). Also how can I install teaks for apps? Installing apks from pages that promise you this and you have to log in is very untruthful. Any suggestions to all this?
Arturofm2 said:
How are you doing with the ads? Like youtube, pandora, spotify? I just installed xposed and the phone feels very hot, and If I unroot it (which I'm thinking to do) I won't be able to get things without ads (I know about vpns and browsers). Also how can I install teaks for apps? Installing apks from pages that promise you this and you have to log in is very untruthful. Any suggestions to all this?
Click to expand...
Click to collapse
I just put up with them.
In all reality, I don't use my phone for the purposes that require my viewing of ads to begin with.
Sure when I was rooted I had adblocker. But honestly, I had completely forgotten all about that benefit of being rooted until now.
I suppose if you absolutely need to be rid of ads then by all means, retain root. However ads don't effect my daily use one bit.
Binary100100 said:
I just put up with them.
In all reality, I don't use my phone for the purposes that require my viewing of ads to begin with.
Sure when I was rooted I had adblocker. But honestly, I had completely forgotten all about that benefit of being rooted until now.
I suppose if you absolutely need to be rid of ads then by all means, retain root. However ads don't effect my daily use one bit.
Click to expand...
Click to collapse
Could you help me unroot it? I was following a guide here to unroot it and downloaded the firmware but when I click flash, it didn't work, I'm having travel reverting it, can you help me? The model is: SM-G935T
Arturofm2 said:
Could you help me unroot it? I was following a guide here to unroot it and downloaded the firmware but when I click flash, it didn't work, I'm having travel reverting it, can you help me? The model is: SM-G935T
Click to expand...
Click to collapse
I just flash the appropriate firmware that you had prior to rooting with ODIN.
Never had any issues. Which "guide" are you referring to?
Binary100100 said:
I just flash the appropriate firmware that you had prior to rooting with ODIN.
Never had any issues. Which "guide" are you referring to?
Click to expand...
Click to collapse
bro now I'm friking out, I followed this guide and when I click in flash it says Fail. I followed it step by step, I don't don't what's going on and when I reset the phone it says custom and doesn't even load, so tmobil would know that I rooted it...
fff.... can you give me the link, guide, whatever you used to revert it?
Arturofm2 said:
bro now I'm friking out, I followed this guide and when I click in flash it says Fail. I followed it step by step, I don't don't what's going on and when I reset the phone it says custom and doesn't even load, so tmobil would know that I rooted it...
fff.... can you give me the link, guide, whatever you used to revert it?
Click to expand...
Click to collapse
You're probably trying to flash a firmware with a V3 bootloader over G935TTMB4APK1.
If you were seriously following that (outdated) guide step by step then you tried flashing TMB_G935TUVU3APG1.zip over a PK1 firmware. Yeah... that doesn't work.
Download the latest firmware from sammmobile.
https://www.sammobile.com/firmwares/database/SM-G935T/
Try it again.
IF that doesn't work... try using Smart Switch.
I haven't done it before but I think it's the Emergency Software Recovery and Initialization.
forum.xda-developers.com/tmobile-s7-edge/how-to/odin-apk1-tmobile-tmbg935ttmb4apk1-t3494724
Odin this to return to stock firmware.
Binary100100 said:
You're probably trying to flash a firmware with a V3 bootloader over G935TTMB4APK1.
If you were seriously following that (outdated) guide step by step then you tried flashing TMB_G935TUVU3APG1.zip over a PK1 firmware. Yeah... that doesn't work.
Download the latest firmware from sammobile.
https://www.sammobile.com/firmwares/database/SM-G935T/
Try it again.
IF that doesn't work... try using Smart Switch.
I haven't done it before but I think it's the Emergency Software Recovery and Initialization.
Click to expand...
Click to collapse
You have no idea the help you gave me. I went to sammobil before but since it said that the download speed was too slow, I didn't do it through that page. Now I did it and it's working fine thanks bro.
But when I start it, it says: custom in the log in, how can I totally put it original?
tduquefjc said:
forum.xda-developers.com/tmobile-s7-edge/how-to/odin-apk1-tmobile-tmbg935ttmb4apk1-t3494724
Odin this to return to stock firmware.
Click to expand...
Click to collapse
If I want to remove everything and just leave it plain how it comes from factory when you buy it, do I just flash the AP file?
Arturofm2 said:
You have no idea the help you gave me. I went to sammobil before but since it said that the download speed was too slow, I kept it. Now I did it and it's working fine thanks bro.
But when I start it, it says: custom in the log in, how can I totally put it original?
Click to expand...
Click to collapse
Arturofm2 said:
If I want to remove everything and just leave it plain how it comes from factory when you buy it, do I just flash the AP file?
Click to expand...
Click to collapse
You should flash everything.
BL= Bootloader (which should be V4 since you updated to the latest firmware already. Anything less than V4 will fail.)
AP= Is for System, Cache, kernel, etc.
CP= Is for modems
CSC is for your HOME_CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 file.
Important! If you use the CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 (doesn't have the word "HOME" in the name) then it'll wipe your phone!
If your phone still says "CUSTOM" on it then make sure that reboot and check again. If it still says custom then make sure that you don't still have the engineering kernel. Re-flash the AP files again if so. It shouldn't though if it's 100% stock. Also note if you saw the unlocked padlock on the S7 Edge splash screen (before the bootanimation).
Good luck and happy New Year.
Binary100100 said:
You should flash everything.
BL= Bootloader (which should be V4 since you updated to the latest firmware already. Anything less than V4 will fail.)
AP= Is for System, Cache, kernel, etc.
CP= Is for modems
CSC is for your HOME_CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 file.
Important! If you use the CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 (doesn't have the word "HOME" in the name) then it'll wipe your phone!
If your phone still says "CUSTOM" on it then make sure that reboot and check again. If it still says custom then make sure that you don't still have the engineering kernel. Re-flash the AP files again if so. It shouldn't though if it's 100% stock. Also note if you saw the unlocked padlock on the S7 Edge splash screen (before the bootanimation).
Good luck and happy New Year.
Click to expand...
Click to collapse
Perfect! All I did was reboot it, and the unlocked padlock went away, thank you very much for all your help! Happy new year!