Related
I'm looking to root my Note 3, and I'm curious what the safe guidelines are, I can't seem to find a definitive answer on this.
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
My current details are as follows:
Model: SM-N900V
Build: JSS15J.N900VVRUBMJ7
Am I SoL?
Thanks for the help.
NOTE: I tried searching , but it seems the search function is temporarily unavailable :crying:
crizznaig said:
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
Click to expand...
Click to collapse
Yes, you can either use the Kingo root tool or wait until "Root de la Vega" gets a fix.
Personally, I would wait instead of using Kingo: there is some privacy concerns with using Kingo since we don't actually know how/what it does.
DroidModderX said:
The verdict is still out as to whether Kingo App is anything other than a malicious virus ridden software, or an innocent one click root method for many devices. If you do decide to use this app you should do so at your own risk. This root method is completely close sourced so we aren't sure of everything contained with in it. If this bothers you then steer clear. If you don't mind your data potentially being at risk this method is a one click method that works for a long list of devices. It has been confirmed via an XDA thread that this method will work with the Verizon Galaxy Note 3 after the latest OTA update.
Click to expand...
Click to collapse
Yeah I've read the recent situations with Kingo and Vroot as well. I'm cool with waiting, I'd prefer to not have my IMEI data mined for root
I've waited thus far.
So basically I should be following developments on the Root de la Vega stuff.
Appreciate the response
Yeah I've read the recent situations with Kingo and Vroot as well. I'm cool with waiting, I'd prefer to not have my IMEI data mined for root
I've waited thus far.
So basically I should be following developments on the Root de la Vega stuff.
Appreciate the response
Bricked
bummer, i didnt see this yesterday, and i am now bricked and looking to restore somehow back to factory via odin or whatever
crizznaig said:
I'm looking to root my Note 3, and I'm curious what the safe guidelines are, I can't seem to find a definitive answer on this.
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
My current details are as follows:
Model: SM-N900V
Build: JSS15J.N900VVRUBMJ7
Am I SoL?
Thanks for the help.
NOTE: I tried searching , but it seems the search function is temporarily unavailable :crying:
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2498850
I also just received my Note3 with that build number. Any update yet on root?
lieutenantglorp said:
I also just received my Note3 with that build number. Any update yet on root?
Click to expand...
Click to collapse
I have MJ7 and used Kingo
http://forum.xda-developers.com/showthread.php?t=2521581
Kingo Can't Connect
I have just tested Kingo with a Note 3 Verizon (N900V Firmware MJ7) and can't connect.
Thing is, I can see it find in ADB and I can issue commands via ADB. Of course USB debugging is enabled and working fine through ADB.
I'm running the latest version of Kingo 1.1.2.1770, and it just reads "Connecting service" in the bottom-right and the big "Not Connected" in the middle.
I've also attempted to connect my G-III phone which I access via ADB with no problem, and Kingo doesn't see that either.
This is my first test with a one-click root solution. I haven't found any instructions for rooting the N900V any other way (eg directly via command line) .. Anyone have any idea what I could be doing wrong, or how to root the N900V running MJ7 without Kingo?
Thank you in advance
RKM
I would assume you can use odin with stock original firmware and pit file to downgrade your phone from MJ7, use de la vega, use supersu+ "preserve superuser" functionality, then OTA update. Using supersu+/preserve option/OTA/re-enable is how I updated and kept root.
I'd be willing to bet it's your anti-virus or firewall software and that you are doing this on either Win 7 or Win 8.
Sent from my SM-N900V using Tapatalk
Also, having just read up on the latest Kingo stuff, just use it. It's fine. The latest versions don't send your IMEI. I'd still use it if they did, personally. IMEI+serials are sent around all the time when you buy/sell phones online since you need to confirm clean IMEI before paying to be sure the phone hasn't been reported stolen. Nothing bad to worry about. It's your phone, if someone could possibly do anything weird, Verizon would swap you a new one.
bigillz said:
I would assume you can use odin with stock original firmware and pit file to downgrade your phone from MJ7, use de la vega, use supersu+ "preserve superuser" functionality, then OTA update. Using supersu+/preserve option/OTA/re-enable is how I updated and kept root.
Click to expand...
Click to collapse
Doing this will soft brick your device. You cannot go back to MI9 if you are already on MJ7. Do not try to flash back to stock MI9 if you are already on MJ7.
HAZA12D_HYPERDRIVE_NOTE3
haza12d said:
Doing this will soft brick your device. You cannot go back to MI9 if you are already on MJ7. Do not try to flash back to stock MI9 if you are already on MJ7.
HAZA12D_HYPERDRIVE_NOTE3
Click to expand...
Click to collapse
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
bigillz said:
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
Click to expand...
Click to collapse
Not positive, but I think they were having to use the pit file with MJ7 after they had tried MI9. Just flashing MJ7 wouldn't work. I've been wrong before though.
G8orDroid said:
Not positive, but I think they were having to use the pit file with MJ7 after they had tried MI9. Just flashing MJ7 wouldn't work. I've been wrong before though.
Click to expand...
Click to collapse
Yes, that's what I've read too.
I'd be willing to bet it's your anti-virus or firewall software and that you are doing this on either Win 7 or Win 8.
Click to expand...
Click to collapse
Unfortunately I don't run any AV software other than the intrinsic Win7, and I had already setup exceptions for the app, disabled, it -- and I've been running Kingo "As Administrator" explicitly in each case.
It just seems so weird that ADB works flawless, and Kingo does not. They're basically the same thing (I believe Kingo is just running everything through ADB, right?)
Ugh .. so I can't downgrade to root, and I can't get Kingo to connect despite it not being related to AV apps and ADB working fine. Leave it to tech to turn a thirty minute project into days!!
Thanks again for any ideas
bigillz said:
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
Click to expand...
Click to collapse
Yes, even with the pit. You cannot go back to MI9 once you update.
HAZA12D_HYPERDRIVE_NOTE3
---------- Post added at 01:50 PM ---------- Previous post was at 01:46 PM ----------
rkmFL said:
Yes, that's what I've read too.
Unfortunately I don't run any AV software other than the intrinsic Win7, and I had already setup exceptions for the app, disabled, it -- and I've been running Kingo "As Administrator" explicitly in each case.
It just seems so weird that ADB works flawless, and Kingo does not. They're basically the same thing (I believe Kingo is just running everything through ADB, right?)
Ugh .. so I can't downgrade to root, and I can't get Kingo to connect despite it not being related to AV apps and ADB working fine. Leave it to tech to turn a thirty minute project into days!!
Thanks again for any ideas
Click to expand...
Click to collapse
Do you have developer options enabled and have USB debugging enabled?
HAZA12D_HYPERDRIVE_NOTE3
haza12d said:
Do you have developer options enabled and have USB debugging enabled?
Click to expand...
Click to collapse
Absolutely, yes.
I mentioned back in the original thread, I have USB debugging enabled and successfully using ADB, which requires this along with the cert approval (required as of Android 4.2 or 4.3, can't remember now).
As a developer, I use ADB on a daily basis and have never had any issue connecting to the phones.
I've re-installed Kingo, etc -- nothing. I can even fire up a command prompt while Kingo is running and send an ADB devices to see my phone successfully connected with the (with the latest Samsung drivers, right from Kingo's site stating the requirement).
Thanks again for the ideas
rkmFL said:
Absolutely, yes.
I mentioned back in the original thread, I have USB debugging enabled and successfully using ADB, which requires this along with the cert approval (required as of Android 4.2 or 4.3, can't remember now).
As a developer, I use ADB on a daily basis and have never had any issue connecting to the phones.
I've re-installed Kingo, etc -- nothing. I can even fire up a command prompt while Kingo is running and send an ADB devices to see my phone successfully connected with the (with the latest Samsung drivers, right from Kingo's site stating the requirement).
Thanks again for the ideas
Click to expand...
Click to collapse
I agree, it doesn't make a lot of sense that Kingo wouldn't connect if you can connect manually thru ADB. I believe it does use ADB to communicate. The software will take a while to run especially on a slow connection, but I am assuming from what you've said that it never gives you a "Device Connected" status, correct?
I mentioned firewall and AV earlier because some of them will block either the app or the communication. I had Trend Micro running on one of the computers I used and it wouldn't connect until I uninstalled it.
I have an SGH-I337 with Android version 4.4. I have the Knox bootloader (sadface). I attempted to root this phone previously using Saferoot but this caused problems (relevant thread).
I can connect to the data network but I can't get the wifi to work. It won't even turn on. As soon as I tap the switch it goes back off.
Please help.
You'll probably have to use the NB1 full ODIN to fix it. Make sure to back up your internal storage and anything that doesn't sync to your Google or Samsung account.
Sent from my GT-I9505 using xda app-developers app
DeadlySin9 said:
You'll probably have to use the NB1 full ODIN to fix it. Make sure to back up your internal storage and anything that doesn't sync to your Google or Samsung account.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ok, I'll try that.
While I have your attention, I have a couple other questions...
- Do you know if this phone is actively being worked on by developers? As in, are exploits being researched to unlock the bootloader?
- Can the phone be rooted with an update? What is the preferred method to do this? Recovery (I have teamwin) or ADB?
EDIT: Is it safe to flash just the modem or would you recommend the full phone firmware. I found a thread here with firmware.
goose90proof said:
Ok, I'll try that.
While I have your attention, I have a couple other questions...
- Do you know if this phone is actively being worked on by developers? As in, are exploits being researched to unlock the bootloader?
- Can the phone be rooted with an update? What is the preferred method to do this? Recovery (I have teamwin) or ADB?
EDIT: Is it safe to flash just the modem or would you recommend the full phone firmware. I found a thread here with firmware.
Click to expand...
Click to collapse
The phone is actively being worked on, most progress is kept between PM's or in a thread in the Verizon S4 section (they're in the same boat as us and chances are an exploit for one will work on both).
The phone can not be rooted with an update because we can't sign it once we add the su binary.
You can't flash the modem as those are recovery flashable zips and if you're on NB1 you can't get root or recovery without a more involved method first (no simple one click).
DeadlySin9 said:
The phone is actively being worked on, most progress is kept between PM's or in a thread in the Verizon S4 section (they're in the same boat as us and chances are an exploit for one will work on both).
The phone can not be rooted with an update because we can't sign it once we add the su binary.
You can't flash the modem as those are recovery flashable zips and if you're on NB1 you can't get root or recovery without a more involved method first (no simple one click).
Click to expand...
Click to collapse
Thanks much for verifying that for me. I'm content to wait until a solution is found. Just relieved to hear that the smarties are still tinkering with it. :good:
I guess I don't have TeamWin then? That's odd because after my failed root attempt, it was after I tried flashing teamwin that the phone booted back on after being softbricked. I guess that was coincidence then. At any rate, I will try to flash the NB1 firmware to fix the wifi. At least I have data. :silly:
WiFi issues with OTA firmware too
Just thought I'd add that the OFW has WiFi issues as well, at least for a few if us. When I updated OTA to 4.4 the WiFi worked for a couple of weeks then stopped working (reboot will allow it to work for a while until the unit sleeps, then it won't toggle). I tried the Odin tar.md5 image and the same thing crops up. This thread is relevant: [Q] OFW 4.4.2 WiFi Not Turning On. I like KitKat, hopefully we can figure out what the problem is.
goose90proof said:
Thanks much for verifying that for me. I'm content to wait until a solution is found. Just relieved to hear that the smarties are still tinkering with it. :good:
I guess I don't have TeamWin then? That's odd because after my failed root attempt, it was after I tried flashing teamwin that the phone booted back on after being softbricked. I guess that was coincidence then. At any rate, I will try to flash the NB1 firmware to fix the wifi. At least I have data. :silly:
Click to expand...
Click to collapse
You likely overwrote the stock recovery. Here is the NB! stock recovery. Flash in PDA slot in Odin:https://mega.co.nz/#!M9EQBT5A!ri4QeMYpgi-JjmUGZ3FY2gtogDBWPEL7zRCjASIcVe8
If you need the NB1 stock modem here it is. Also flash in PDA slot in odin: https://mega.co.nz/#!sstkFRiJ!d9zTRte0KcVFv7o-bjKFuFMM1Q9ivzDlqJKy2OlP_7o
Excellent thank you.
goose90proof said:
Excellent thank you.
Click to expand...
Click to collapse
did it work for you?
I haven't gotten around to trying it. The phone is working now so I'm a bit reluctant to do anything to it until future developments bear fruit.
Greetings,
My wife's S4 is on 4.2.2 (MF3) and it drives me nuts. I've been looking around the forums, but haven't found anything conclusive as to if there is a way to go from 4.2.2 to 4.4.2 and keep or reroot.
Normally I'd throw caution to the wind, close my eyes, and hit start... but, being that this is the wife's phone and that she is perfectly content with 4.2.2, the last thing I want to do is screw up her phone.
So I guess the question is: Does anyone know of a guide they can point me to that upgrades a rooted 4.2.2 to 4.4.2?
Thank you!
PS
I found this guide (http://forum.xda-developers.com/showthread.php?t=2728462), but it just seems strange that the thread was all but ignored, so there is no feedback from users/testers.
You can upgrade to 4.4.2, but you don't keep root. You'll have to re-root it. And you have to use Odin which means you'll wipe the phone. If it was my wife's phone I wouldn't want to put up with the complaining of having to setup everything again.
Sent from my Nexus 5 using XDA Free mobile app
tarikakleh said:
Greetings,
My wife's S4 is on 4.2.2 (MF3) and it drives me nuts. I've been looking around the forums, but haven't found anything conclusive as to if there is a way to go from 4.2.2 to 4.4.2 and keep or reroot.
Normally I'd throw caution to the wind, close my eyes, and hit start... but, being that this is the wife's phone and that she is perfectly content with 4.2.2, the last thing I want to do is screw up her phone.
So I guess the question is: Does anyone know of a guide they can point me to that upgrades a rooted 4.2.2 to 4.4.2?
Thank you!
PS
I found this guide (http://forum.xda-developers.com/showthread.php?t=2728462), but it just seems strange that the thread was all but ignored, so there is no feedback from users/testers.
Click to expand...
Click to collapse
You can first unroot then go to settings---->more----->about device----> software update and take the OTA to MK2. Once on MK2 take the OTA to NB1, then to NC1, then re-root using towelroot: http://forum.xda-developers.com/showthread.php?t=2783157
The above process will leave your current set-up intact and rooted.
muniz_ri said:
You can first unroot then go to settings---->more----->about device----> software update and take the OTA to MK2. Once on MK2 take the OTA to NB1, then to NC1, then re-root using towelroot: http://forum.xda-developers.com/showthread.php?t=2783157
The above process will leave your current set-up intact and rooted.
Click to expand...
Click to collapse
Would this method be the best way to unroot, starting with step 2 in my case since I still have root...or is there a different route I can take?
Originally Posted by ou812bkewl
So, here is what I did and what you must do:
1. Re-root again using the same method you did before for MF3, then:
--a) Reboot, update SuperSU app and it's binary
--b) Reboot again, verify device status is back to"Official"
--c) Reboot again, verifying that, this time, the boot screen is back to normal again
2. Download a file manager app in the Play Store called "Total Commander" and enable "Root functions everywhere" in its settings.
3. Navigate to a folder called "/system/xbin"
4. Delete ONLY files in that folder with the word "busybox" within its filename or symlink path. You should end up with three files left. I did. Two of them are SuperSU related. DO NOT DELETE ANY OF THEM!
5.Open SuperSU and, in its settings, select the "Full un-root" option. Once SuperSU closes, reboot.
When you reboot, wait a full minute and check on device status. It should still say "Official" and you will be fully un-rooted.
Why does it stay "Official" with Busybox present ONLY when SuperSU's most recently updated apk and binary are present? I have no clue... But I hope this helps you out.
Click to expand...
Click to collapse
Ok. So I've tried to ask this question before, and every time I get people telling me to do things I just don't understand. Sorry. Not trying to spam. If this question goes unanswered I will not post another and I apologize if this is too stupid. Just a noob trying to get help.
All I want is to update my phone (SM-G900F) to the most recent Android version. Like 3 weeks ago I got the prompt to update OTA because a new update was available. I've haven't modified my phone other than Towelrooting in July and having SuperSU and Titanium. Had planned to get way more root stuff but so far I haven't had the time.
OTA Update failed, told me my phone was modified in an unauthorized way and suggested to update through Kies.
Here's my question: What's the simplest, easiest way to update correctly? I'd rather do it one way or the other: Either, I unroot with SuperSU and remove Titanium, then download Kies and try to update, if successful I reroot with Towelroot OR: I can manage to update WITH Towelroot and SuperSU still there, if so, how?
That's all I'm asking. Would the first option work best? Is there a better way? I don't want to use Odin or anything like that, I don't want to use custom roms or anything, I'd just like to have the most recent update and root, that's it. Please put me out of my misery.
tempest22 said:
What's the simplest, easiest way to update correctly?
I don't want to use Odin or anything like that
Click to expand...
Click to collapse
You can't have it both ways. Odin is the easiest, otherwise try Kies.
Download NeatRom and you will get the latest Rom.
http://forum.xda-developers.com/showthread.php?t=2828562
Verstuurd vanaf mijn SM-G900F met Tapatalk
BLuFeNiX said:
You can't have it both ways. Odin is the easiest, otherwise try Kies.
Click to expand...
Click to collapse
So would it work if I unroot with SuperSU, then install Kies on my pc and update to most recent Anroid version?
Or, if I'm already going to unroot first with SuperSU, can I then just try the OTA update and if successful, can I reroot with Towelroot or will that be outdated with the most recent Android version?
Download odin 3.09. Download the latest official firmware for your device, search the forums to find the latest one. Extract the .tar file inside the firmware zip u downloaded. Make sure you have the drivers installed for your phone on your computer. Extract Odin and run the .exe to open the Odin program. Put your phone into download mode> While Powered off hold volume down.. Home.. And power button. Press continue when given the warning plug in your phone to the PC.. Within Odin click the ap slot. Load the .Tar file which is your firmware. Make sure Odin recognizes your phone is plugged. Hit start. Sit back and watch it flash.
Sent from my SM-G900T using XDA Free mobile app
Ok. I hope this does not sound arrogant. But I honestly can't believe why anyone on this forum can't directly answer my question instead of giving me other suggestions. I don't want to use Odin, it's too complex for me and I don't want to mod my phone to hell and back. I just want to get the most recent update released 2 or so weeks ago.
Nobody has said whether the Kies method works (letting Towelroot remain on my phone and trying to download most recent Android version with Kies on my pc), or whether I unroot with SuperSU, remove all root apps (I only have 3), then try the OTA update just with my phone and see if that works. Can somebody please just answer that? PLEASE
..
I think I'm correct in saying the most recent ota comprised on little more than minor tweaks and security updates.
The world's not going to come to an end if you don't have the very latest update.
Perhaps more research BEFORE choosing the root route would have been wise, at least then you would be more informed as to the outcome of your chosen option.
Having read the last few posts it's clear to me, even as a relative S5 noob that your questions been answered quite comprehensively. Just not the install an app and reboot option you were hoping for.
sent from SGS5 running NeatRom 0X1
---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------
Just before I get stuck into my pizza. .....
.......did you by any chance select ART rather than running a DALVIK system?
I did that before rooting and I got the same can't install ota due to modified yada yada.....
I reverted back to Dalvik and the ota installed no problem. As I said.... This was pre rooting so might not be relevant.
sent from SGS5 running NeatRom 0X1
does.the kies method i asked about.work.
tempest22 said:
does.the kies method i asked about.work.
Click to expand...
Click to collapse
from reading the replies above i think the answer is no it wont but why not just give it a try, if its not going to work it will just tell you so (like the ota update did)
your options as stated above are to either use odin and install the latest update or take it to a shop or find someone who is close to you who knows how to use odin and ask them if they wouldnt mind doing it for you and buy them a beer as a thankyou,
odin isnt hard to use in fact it couldnt be any easier to use for a noob just follow a couple of simple steps and your done
i hope you get this sorted
tempest22 said:
does.the kies method i asked about.work.
Click to expand...
Click to collapse
It should work as I have done that on my old device before but you have to re-root your s5 again after the update.
Sent from my SM-G900F using Tapatalk
Towelroot after latest OTA-Update doesn't work!
I don't know if the idea of an update is so good.
My SM-900F was Towelrooted to run Titanium, too.
My setup was "OTA when in a WIFI network" and clicked "update yes" - I was typing some notes very late,
the message box popped up and --- swoosh --- the Update was running. No need to say my notes weren't saved?
I don't even know what that update contained and what it was good for.
Now I run 4.4.2 ,
Baseband G900FXXU1ANG2
Kernel 3.4.0-2089850 [email protected] #1 July 3rd 2014
Build KOT49H.G900FFXXU1ANG2.
Root access has gone, Towelroot says "device not supported", Titanium doesn't work anymore.
No I have to start Windows only to run KIES - waf.
So be careful.
Dirk
Ok, so I have unrooted with supersu and removed Titanium. Supersu is still there. I've tried to do an OTA update, and surprisingly this time it actually went so far as to actually download the updates. Then after I press install, it goes into boot mode and says like 20% or more installed, then it goes black and reboots, everything is normal but the update failed.
What. Now.
They should really start telling people that rooting will cause updates to become a nightmare. Please help me, this is ridiculous.
tempest22 said:
They should really start telling people that rooting will cause updates to become a nightmare. Please help me, this is ridiculous.
Click to expand...
Click to collapse
Lack of common sense is my diagnosis.
Of course it's not always going to be plain sailing. And early days with any new handset means there are answers we just don't know yet.
That's why pretty much every thread has a precursor from the Dev that says "use at your own risk","read instructions fully before flashing" or " it's not my fault if your dog gets fleas or your nan pegs it" etc etc etc. If you have any doubts rooting your phone wasnt for you..... you shouldn't have rooted.
sent from SGS5 running NeatRom 0X1
tempest22 said:
They should really start telling people that rooting will cause updates to become a nightmare. Please help me, this is ridiculous.
Click to expand...
Click to collapse
Lack of common sense is my diagnosis.
Of course it's not always going to be plain sailing. And early days with any new handset means there are answers we just don't know yet.
That's why pretty much every thread has a precursor from the Dev that says "use at your own risk","read instructions fully before flashing" or " it's not my fault if your dog gets fleas or your nan pegs it" etc etc etc. If you have any doubts rooting your phone wasnt for you..... you shouldn't have rooted.
sent from SGS5 running NeatRom
bump, can somebody tell me conclusively for once and for all if the following will work: I have unrooted with supersu (originally rooted with Towelroot in July) supersu and titanium are removed, OTA update still doesn't work. if i install Kies on my pc, will an update work, AND will I be able to use towelroot again to reroot.
thank you.
please?
tempest22 said:
bump, can somebody tell me conclusively for once and for all if the following will work: I have unrooted with supersu (originally rooted with Towelroot in July) supersu and titanium are removed, OTA update still doesn't work. if i install Kies on my pc, will an update work, AND will I be able to use towelroot again to reroot.
thank you.
Click to expand...
Click to collapse
Did you use Triangle Away to reset the system status and binaries to official? If not reroot with Towelroot again, use Triangle Away to reset the counters (besides the KNOX flag), unroot with the superSU app, then flash a stock rom with Odin and after that factory reset. Your device is official now.
gee2012 said:
Did you use Triangle Away to reset the system status and binaries to official? If not reroot with Towelroot again, use Triangle Away to reset the counters (besides the KNOX flag), unroot with the superSU app, then flash a stock rom with Odin and after that factory reset. Your device is official now.
Click to expand...
Click to collapse
jesus ****ing christ. i'm not that kind of a phone pro guy. I just want to know if updating with Kies with allow me to reroot afterwards again (whether or not with Towelroot or ****ing Odin isn't important anyway). I rooted with towelroot in july, know isn't tripped or whatever. I have unrooted with supersu. Now I just want to know whether or not updating with Kies on my pc will be successful, and if it will allow me to reroot again, like with Towelroot...
PLEASE
tempest22 said:
jesus ****ing christ. i'm not that kind of a phone pro guy. I just want to know if updating with Kies with allow me to reroot afterwards again (whether or not with Towelroot or ****ing Odin isn't important anyway). I rooted with towelroot in july, know isn't tripped or whatever. I have unrooted with supersu. Now I just want to know whether or not updating with Kies on my pc will be successful, and if it will allow me to reroot again, like with Towelroot...
PLEASE
Click to expand...
Click to collapse
Well I know why no one can answer that simple question. Because no one has done it that way. That is why you can't get the answer you seek. So you have a choice, give up and stop asking, or be the first to try it. Then post here if it works or not.
Sent from my HTC One_M8 using Tapatalk
Hi all,
I have a AT&T Galaxy S4 i337. The WIFI doesn't work. It seems to be a very common problem as there are many fixes on the internet. I have tried them all and I don't know what to do now. It is running V. 4.3 and my baseband version is i337ucugoc4.
- Rooted. Installed Rom Manager, Terminal Emulator, SuperSU, and Reverse Tether so I could use the internet (because no wifi).
- Tried to install a new modem but could not find the exact modem file. I saw a list at http://forum.xda-developers.com/showthread.php?t=2496517 but didn't know which was good for my phone. I saw I337_UCUGOC3_Modem_RockRatt.zip but it ends in a 3 not a 4 as required for my modem.
- tried to update using the AT&T Software update. It stayed at "Checking for software updates...." and then said "Software update interrupted. No updates available. Check back in 24 hours". Don't know if that would have solved the WIFI problem anyhow.
- Tried again to install to 5.0 thru USB. Downloaded and installed it but when I rebooted, it was still 4.3
- Downloaded FXR wifi and ran it - no luck there.
- downloaded the modem file ATT_OC4_modules.zip and flashed it to the phone. It said SUCCESSFUL but there was no wifi afterwards.
- Adjusted the source code with terminal emulator as I saw in a youtube video. No success and I changed it back to the original.
- Downloaded wifi manager and tried turned off-then-on wifi.
- probably more things I have forgotten in the last three days.
I have tried everything I can find to try. It has been 3 days of trying - very frustrated. I would very much appreciate direction on this. To recap, I need to get wifi working and want to upgrade to lolipop.
Thanks so much,
Amber
amberblossom said:
Hi all,
I have a AT&T Galaxy S4 i337. The WIFI doesn't work. It seems to be a very common problem as there are many fixes on the internet. I have tried them all and I don't know what to do now. It is running V. 4.3 and my baseband version is i337ucugoc4.
- Rooted. Installed Rom Manager, Terminal Emulator, SuperSU, and Reverse Tether so I could use the internet (because no wifi).
- Tried to install a new modem but could not find the exact modem file. I saw a list at http://forum.xda-developers.com/showthread.php?t=2496517 but didn't know which was good for my phone. I saw I337_UCUGOC3_Modem_RockRatt.zip but it ends in a 3 not a 4 as required for my modem.
- tried to update using the AT&T Software update. It stayed at "Checking for software updates...." and then said "Software update interrupted. No updates available. Check back in 24 hours". Don't know if that would have solved the WIFI problem anyhow.
- Tried again to install to 5.0 thru USB. Downloaded and installed it but when I rebooted, it was still 4.3
- Downloaded FXR wifi and ran it - no luck there.
- downloaded the modem file ATT_OC4_modules.zip and flashed it to the phone. It said SUCCESSFUL but there was no wifi afterwards.
- Adjusted the source code with terminal emulator as I saw in a youtube video. No success and I changed it back to the original.
- Downloaded wifi manager and tried turned off-then-on wifi.
- probably more things I have forgotten in the last three days.
I have tried everything I can find to try. It has been 3 days of trying - very frustrated. I would very much appreciate direction on this. To recap, I need to get wifi working and want to upgrade to lollipop.
Thanks so much,
Amber
Click to expand...
Click to collapse
May I ask why is your bootloader is lollipop but your OS rom is still Jelly bean ( you said 4.3). It appears that you might have jelly bean kernel which will not work with lollipop modem and bootloader. Majority of the wifi problem is caused by the kernel and bootloader mismatched, assuming that your radio (modem) has no physical damage. Try to flash the OC4 kernel and see you still have the wifi problem.
If you want to upgrade to lollipop from Jelly bean, there are several guides on this forum explaining step by step.
I flashed the OC4 kernal - no change in wifi
sway8966 said:
May I ask why is your bootloader is lollipop but your OS rom is still Jelly bean ( you said 4.3). It appears that you might have jelly bean kernel which will not work with lollipop modem and bootloader. Majority of the wifi problem is caused by the kernel and bootloader mismatched, assuming that your radio (modem) has no physical damage. Try to flash the OC4 kernel and see you still have the wifi problem.
If you want to upgrade to lollipop from Jelly bean, there are several guides on this forum explaining step by step.
Click to expand...
Click to collapse
Thanks sway8966,
I flashed the OC4_update_from_OC3.zip file but there was no change - still no wifi. I wonder if I were to upgrade to lollipop would it automatically fix the problem because it would have the matching bootloader and OS rom? Do you think this might solve the problem?
Thanks again.
amberblossom said:
Thanks sway8966,
I flashed the OC4_update_from_OC3.zip file but there was no change - still no wifi. I wonder if I were to upgrade to lollipop would it automatically fix the problem because it would have the matching bootloader and OS rom? Do you think this might solve the problem?
Thanks again.
Click to expand...
Click to collapse
I do not know what included in the oc4 update from oc3.zip file. As I said before you could try flashing the OC4 kernel file and see whether your wifi is working or not.
Here is the link for the OC4 kernel. You need to flash it via odin.
If you do not have any particular reason to stick with Jelly bean you should upgrade to Lollipop or at least to Kit-kat.
Hi! I had an s4 variant with your problem the same, the wifi nope in none routers.
I gave this device to trash , because i discovered what "happened"
Some stock app, from samsung, masked as anything that i skipped to search (i have much precious time to loose, instead loose really, lost time BRITISH DEVICES IN EXT4 filesystem) what app exactly, is receiving data from samsung server to delete the /system/etc/wifi/bcmdhd.cal
I was obligated to reinstall this file 4 times, changed permission to r--r--r--T untill resolve. But was not sufficient, after this, my wifi, fixed again, but the phone at 8º reboot, after , received a remote conmand again to turn the phone ridiculously slower, i lost my head and crashed this device on the wall, and nevermore i will use this name. Sorry,
All this happened just exactly, after install cwm and root sucessfully, without touch anything on the firmware. Something from samsung inc, is programmed to "detect" these 2 events, and send a "tick" to begin the hell in fire on this devices GT S-Xx
Sent from my XT687 using xda premium
won't boot past the SAMSUNG screen
sway8966 said:
I do not know what included in the oc4 update from oc3.zip file. As I said before you could try flashing the OC4 kernel file and see whether your wifi is working or not.
Here is the link for the OC4 kernel. You need to flash it via odin.
If you do not have any particular reason to stick with Jelly bean you should upgrade to Lollipop or at least to Kit-kat.
Click to expand...
Click to collapse
I flashed the OC4 kernel and it won't boot past the SAMSUNG screen.
amberblossom said:
I flashed the OC4 kernel and it won't boot past the SAMSUNG screen.
Click to expand...
Click to collapse
Your phone is probably in soft-brick now. You need to flash the 4.3 firmware via odin or You need to update to full kit-kat.
If you want to go kit-kat flash this NB1 firmware via odin. It is NB1 but the kernel is NC1 so that you can use towel root to root the phone. Anyway flash that firmware and see the phone is normally booting and wifi is working.
IT WORKED!!!
sway8966 said:
Your phone is probably in soft-brick now. You need to flash the 4.3 firmware via odin or You need to update to full kit-kat.
If you want to go kit-kat flash this NB1 firmware via odin. It is NB1 but the kernel is NC1 so that you can use towel root to root the phone. Anyway flash that firmware and see the phone is normally booting and wifi is working.
Click to expand...
Click to collapse
Thank you so much. It worked. I got my phone back and the wifi is working. Pretty nice. Thanks again. Now to figure out towel root (is that the best for my phone?). You are awesome.
couple more questions
sway8966 said:
Your phone is probably in soft-brick now. You need to flash the 4.3 firmware via odin or You need to update to full kit-kat.
If you want to go kit-kat flash this NB1 firmware via odin. It is NB1 but the kernel is NC1 so that you can use towel root to root the phone. Anyway flash that firmware and see the phone is normally booting and wifi is working.
Click to expand...
Click to collapse
I rooted with towelroot (verified with root checker). I installed superuser but didn't see how to remove bloatware. There are no apps in the apps list. How do I do that? Also, now that it is rooted, is it possible to upgrade it to lollipop? Thanks again.
amberblossom said:
I rooted with towelroot (verified with root checker). I installed superuser but didn't see how to remove bloatware. There are no apps in the apps list. How do I do that? Also, now that it is rooted, is it possible to upgrade it to lollipop? Thanks again.
Click to expand...
Click to collapse
I am glad to hear that it fixes your problem. The NB1 firmware (cooked by muniz_ri) is a live saver. Keep that one. Down the line if your phone screwed up used that one to revive your phone.
Majority of bloatware are system app as such they will not show up in the app bar To remove those you need an admin rights (root) hence we need to root the phone.
To remove the bloatware there are many bloatware remove apps. However they are not written to the specific phone and OS version as such you need to be very careful when you are using them.
I use titanium backup pro to either freeze or remove the bloatware one by one. You can find the list of bloatware for each version on the net. Another way is to install the lean custom rom.
If you want to upgrade to Lollipop you can do it. If somethings screws up you can use that NB1 to come back to Kitkat.
The latest lollipop for the sgh-i337 is OK2 but OK2 gave me some problem that I could not live with it so I stay at OC4.
If you want to upgrade to OK2 or OC4 do let me know. I will point you the guide and necessary files.
CyanogenMod
sway8966 said:
I am glad to hear that it fixes your problem. The NB1 firmware (cooked by muniz_ri) is a live saver. Keep that one. Down the line if your phone screwed up used that one to revive your phone.
Majority of bloatware are system app as such they will not show up in the app bar To remove those you need an admin rights (root) hence we need to root the phone.
To remove the bloatware there are many bloatware remove apps. However they are not written to the specific phone and OS version as such you need to be very careful when you are using them.
I use titanium backup pro to either freeze or remove the bloatware one by one. You can find the list of bloatware for each version on the net. Another way is to install the lean custom rom.
If you want to upgrade to Lollipop you can do it. If somethings screws up you can use that NB1 to come back to Kitkat.
The latest lollipop for the sgh-i337 is OK2 but OK2 gave me some problem that I could not live with it so I stay at OC4.
If you want to upgrade to OK2 or OC4 do let me know. I will point you the guide and necessary files.
Click to expand...
Click to collapse
I guess I will pass on lollipop if there was a problem with it. I looked around for a rom and saw CyanogenMod. It looked pretty good but they discontinued the installer. Can I download it on my PC, move it to the ext card on the S4 and install it from there? Without any changes to my current configuration of the S4? Thanks again.
amberblossom said:
I guess I will pass on lollipop if there was a problem with it. I looked around for a rom and saw CyanogenMod. It looked pretty good but they discontinued the installer. Can I download it on my PC, move it to the ext card on the S4 and install it from there? Without any changes to my current configuration of the S4? Thanks again.
Click to expand...
Click to collapse
I did not say lollipop has a problem, what I meant was I had some problem with lollipop OK2 as such I stay with lollipop OC4.
I took it as you are talking about the CyanogenMoD for the locked bootloader .
You can install that one. You need to install the safestrap first to flash that rom, as mentioned on that link. However, the link also mentioned that you can not make a phone call with that rom as such they stop developing that rom.
sway8966 said:
I did not say lollipop has a problem, what I meant was I had some problem with lollipop OK2 as such I stay with lollipop OC4.
I took it as you are talking about the CyanogenMoD for the locked bootloader .
You can install that one. You need to install the safestrap first to flash that rom, as mentioned on that link. However, the link also mentioned that you can not make a phone call with that rom as such they stop developing that rom.
Click to expand...
Click to collapse
Oh, I didn't understand. I think I would like to try to get up to lollipop. Can you point me to the kernel for that? Also, I have been trying to install CyanogenMod but am running into roadblocks. I think I might have succeeded finally because I now have a yellow triangle and a notice about non-AT&T system software (with a tiny notice - secure fail: kernel). I also had a difficult time installing TWRP as the installer was asking for a file format that the installer didn't download. From what I gather, CyanogenMod looks like a good all around OS and was easy to install when the installer was in play. But if there is another that would suffice but is easier to install, I think that might be a better idea. Could you suggest one?
Sorry about all these questions. I don't know why this is so difficult for me. I feel like an idiot. Thanks again.
amberblossom said:
Oh, I didn't understand. I think I would like to try to get up to lollipop. Can you point me to the kernel for that? Also, I have been trying to install CyanogenMod but am running into roadblocks. I think I might have succeeded finally because I now have a yellow triangle and a notice about non-AT&T system software (with a tiny notice - secure fail: kernel). I also had a difficult time installing TWRP as the installer was asking for a file format that the installer didn't download. From what I gather, CyanogenMod looks like a good all around OS and was easy to install when the installer was in play. But if there is another that would suffice but is easier to install, I think that might be a better idea. Could you suggest one?
Sorry about all these questions. I don't know why this is so difficult for me. I feel like an idiot. Thanks again.
Click to expand...
Click to collapse
SGH-i377 has locked bootloader as such we can not install custom recovery like TWRP or CWM. The only installers we have are safestrap and flashfire. When I was in Kit-kat I used safestrap. It is very troublesome to work with safestrap in lollipop so when I upgrade to lollipop I use falshfire instead.
I have two devices that are on cyanogen mod. I like cyanogen mod but I prefer touch-wiz rom over AOSP though.
The only cyanogen mod you can install is the one that I mentioned in my previous message. You need to use safestrap to install it.
For SGH-I337 you can only install the touch-wiz rom which are written for either safestrap or flashfire. I do not see any AOSP rom written for safestrap or flashfire.
What I did was flash NB1 via odin. root with towl root and install the flashfire. Flash the OC4 rom via flashfire and flash the OC4 bootloader via odin. After my phone boot to lollipop OC4, Installed flashfire and flash the Albe95 S6 port rom. I like to use the S6 features and that custom rom is a stable one. Do you think the process is easy enough?
To upgrade to Lollipop,
I assumed that you are back on NB1 and rooted. If not do that process first. (you mentioned that you installed the cyanogenmode)
Here is the guide telling you step by step how to install lollipop from NB1.
The guide was originally written for OC4 but when OK2 came out it was updated with OK2. So if you want to go to OK2, use the files that mentioned on the guide. If you want to go to OC4 use the file I posted below instead.
I337_OC4_Stock_Rooted_ROM.zip
I337_OC4_Stock_Rooted_Deodexed_ROM
I337_OC4_Bootloader.tar.md5
The choice between using normal and deodexed_rom is your call.