Hello
So firstly look at the image i attached....
Now i want to know if it is possible to root this phone and install CM12 or another custom rom or even an official lollipop rom that i will receive updates on ?
Thanks in advance
It looks to me like you have a Verizon S5, although the model number states otherwise and the DONGCHAO.617 build number seems custom. You do have a Verizon S5 though, so you can root on NCG, which you are running, through towelroot. However, ROMs like CM12 can't be installed without an unlocked bootloader, which is impossible currently on the VZ S5. You can get a Lollipop ROM with root by following these instructions.
mrjiggywiggy said:
It looks to me like you have a Verizon S5, although the model number states otherwise and the DONGCHAO.617 build number seems custom. You do have a Verizon S5 though, so you can root on NCG, which you are running, through towelroot. However, ROMs like CM12 can't be installed without an unlocked bootloader, which is impossible currently on the VZ S5. You can get a Lollipop ROM with root by following these instructions.
Click to expand...
Click to collapse
Thanks for the reply, just one question is this lollipop rom and official firmware that can be updated?
..also if i keep this software running and don root etc will it get lollipop eventually?
PCFervent said:
Thanks for the reply, just one question is this lollipop rom and official firmware that can be updated?
..also if i keep this software running and don root etc will it get lollipop eventually?
Click to expand...
Click to collapse
What you're currently running is not official. The build number isn't official, anyway, so it won't get the lollipop update. The firmware that I'm telling you about can be updated, but I'm not 100% sure about the ROM.
Ok Thank you I will give it a try either today or tomorrow cheers for the info
very similar issue
Good day,
I have a similar issue with phone bought in china (dong chao)
However my extra problem is low wifi signal (smart switch off).
just updated to 6.01 verizon and the issue persisits. It is very strange as the phone seemed to be verizon but labeled as 900F...
very strange...
Any recommendations ? thank you
Related
Hello
I recently got my S4 i9505. I'm planning to root it
I have Android version 4.3
I used to flash costum roms on my s2 but I'm not really planning to do much flashing on my S4. not soon anyway
So as I connected the phone to Kies to make sure the drivers were downloaded so I can proceed with rooting
Firmware update popped up
I'm not sure what the best option for me now.
Should I root now and then I'd be able to flash a costume KK rom? and are there any stable ones that are better than the stock?
Can I use kies to update my rooted phone?
Maybe I should stick with JB 4.3? Which one is better 4.3 or 4.4.2?
I remember facing some issues when I update my s2 back. So I searched for the KK Update for the s4 and some people weren't so happy with their KK update
I know that doesn't represent the majority but still it could happen to me
So I confused myself
What is your advice to me?
sorry for the long post
Also I have an extra question What is KNOX? and do I need it?
egy_b0y said:
Hello
I recently got my S4 i9505. I'm planning to root it
I have Android version 4.3
I used to flash costum roms on my s2 but I'm not really planning to do much flashing on my S4. not soon anyway
So as I connected the phone to Kies to make sure the drivers were downloaded so I can proceed with rooting
Firmware update popped up
I'm not sure what the best option for me now.
Should I root now and then I'd be able to flash a costume KK rom? and are there any stable ones that are better than the stock?
Can I use kies to update my rooted phone?
Maybe I should stick with JB 4.3? Which one is better 4.3 or 4.4.2?
I remember facing some issues when I update my s2 back. So I searched for the KK Update for the s4 and some people weren't so happy with their KK update
I know that doesn't represent the majority but still it could happen to me
So I confused myself
What is your advice to me?
sorry for the long post
Also I have an extra question What is KNOX? and do I need it?
Click to expand...
Click to collapse
First, the most problems in 4.4.2 are fixed, so if you flash the officical, latest firmware of your country you shouldn't have any problem.
An important thing: if you flash a custom rom, your warranty will be set 0x1, that means, you lost your garanty if you flash a custom rom, that's the so called KNOX. You can use knox like a second system on your phone, with all secure data in it, you can only access with a passwort and all datas are locked without this passwort.
Root your phone after the software update if you want to root it.
Tkkg1994 said:
First, the most problems in 4.4.2 are fixed, so if you flash the officical, latest firmware of your country you shouldn't have any problem.
An important thing: if you flash a custom rom, your warranty will be set 0x1, that means, you lost your garanty if you flash a custom rom, that's the so called KNOX. You can use knox like a second system on your phone, with all secure data in it, you can only access with a passwort and all datas are locked without this passwort.
Root your phone after the software update if you want to root it.
Click to expand...
Click to collapse
the fact is that 4.4.2 GNG8 international version cannot be rooted....
christty31 said:
the fact is that 4.4.2 GNG8 international version cannot be rooted....
Click to expand...
Click to collapse
That's wrong, just not with towelroot.
thank you for your input
Hey everyone, I've been completely out of the loop for about a year now as far as updating and rooting is concerned, so if somebody could help me out I'd really appreciate it! I have a rooted Verizon galaxy S5 with Kit Kat 4.4.2, and it seems like Lollipop is now available to the S5. I haven't gotten any updates from Verizon or any other source for my phone for about a year now because I wanted to keep root and I know that updating often kills root. I literally disabled/froze all the Verizon updater apps with Titanium backup.
So what I want to know is what is the newest android version I can update to and still keep root, and what is the process of updating to ensure that I still maintain root permissions? Also, I use the xposed framework, so will that continue to work? I might have a custom recovery, I'm not sure but I can check if it matters.
Thanks so much for anyone's help.
Check sammobile dot com, instructions and ODIN to flash are under the download
*Detection* said:
Check sammobile dot com, instructions and ODIN to flash are under the download
Click to expand...
Click to collapse
Thanks man, would you recommend updating to lollipop? Is it a better version of Android in your opinion?
For me, it's much better, for others it's worse
I've switched back to KK to test, and I lasted 10 minutes before flashing back to Lollipop, much smoother, faster, and better looking IMO
Hey Guys,
today i got a Galaxy s4 black edition and there is a ROM called: Phoenix Rom. So i want to flash back to Stock ROM but im really not sure which one i want to flash on it because i dont want to brick my phone or something. Can i flash this http://www.handy-faq.de/forum/galaxy-s4-i9505xxugng8-kk-4-4-odin-kies-dbt-1t-23-07-2014-t306745/ without any problems?
Phone: GT-I9505
Basisbandversion: I9505XXUGNG8
Buildnumber: KOT49H.I9505XXUGNF1
That ROM will work without a problem. However, that may not have the added wallpapers and sounds the black edition devices have. Is there a reason you're not wanting Android 5.0.1 on your device?
Strephon Alkhalikoi said:
That ROM will work without a problem. However, that may not have the added wallpapers and sounds the black edition devices have. Is there a reason you're not wanting Android 5.0.1 on your device?
Click to expand...
Click to collapse
Thanks for your Answer, i flashed that rom and it works perfectly. There is also an OTA update for Lollipop but im not sure to do that because i heard that lollipop has a lot of bugs like battery draining and so on. Im afraid if i upgrade it to lollipop i cannot downgrade it to KK. But do u think i should update?
I'm inclined to believe Samsung patched the battery drain bug, but you'd have to try it and find out. If you end up not liking it, going back down to the earlier version shouldn't be an issue, especially as you already have a Knox-enabled bootloader on your S4. There are tutorials on the forums here that I believe walk you through the process. Take a look at them before doing the OTA update.
Strephon Alkhalikoi said:
I'm inclined to believe Samsung patched the battery drain bug, but you'd have to try it and find out. If you end up not liking it, going back down to the earlier version shouldn't be an issue, especially as you already have a Knox-enabled bootloader on your S4. There are tutorials on the forums here that I believe walk you through the process. Take a look at them before doing the OTA update.
Click to expand...
Click to collapse
Is it really that my knox bootloader is enabled or not if i do the OTA update? And how can i see that it is enabled or not? Anyway can i root my phone if im on lollipop with CF auto root trough odin ?
You installed Android 4.4.2. 100% positive you have Knox, as all Samsung firmware from 4.3 on has it. Installing the OTA update will restore the Knox apps. Fortunately, CF-AutoRoot still works so you'll have no issues rooting if you install the update.
Ok thank you for your helpful advises, i will flash a kernel on my s4 to stop this overheating issue.
Just noticed that Bell released the 6.0.1 update for my phone (at least I think Bell is BMC, since sammobile stopped displaying the carrier names I'm not sure anymore http://www.sammobile.com/firmwares/database/SM-N910W8/BMC/). How would I go about doing that? I'm assuming there's more to this update than software, they usually include stuff like radio/modem/bootloader firmware updates that I can't get by just using some custom MM build. So I have to install their update to get that. But I'm running 5.1.1, using some custom debloated version of COK3.
I've got lots of questions that I couldn't answer with my google-fu. Is the 6.0.1 build rootable? Does xposed work on it? Can I use Chainfire's Flashfire to update it? https://flashfire.chainfire.eu/ Or do I have to completely downgrade to stock to apply the OTA update? Chainfire's Flashfire says it won't work with a locked bootloader, but that only applies to Verizon Note 4's, right, not Bell? I'm pretty sure my bootloader is unlocked or I wouldn't have a rooted phone with a custom rom and recovery. And it says "things get tricky with a modified /system partition like if you're running xposed", which I am, so what does that mean for me?
Thanks for any help! I know a lot of these questions can be vaguely answered by google if I look hard enough, but I like to be absolutely sure of all the steps for my exact phone before I go do anything that could possibly hard-brick it.
I almost feel bad asking, since I know some people would love to have an S4 that is still on MDL. However...my S4 needs an update and it is in fact still on android 4.2.2 and baseband MDL.
Anyway, I bought my S4 back in late June/early July 2013 and right before the locked/non-exploitable firmware's rolled out. So, I used the "CASUAL w/TWRP Recovery" method to root it and then I froze the update apps using Titanium Backup (AT&T SW Update v42, FWUpgrade 1.2.0, LocalFOTA v2). My intention at the time was to flash different ROMs on it, etc. Only...I never did.
So here I am, 3+ yrs later, no need for a "new" phone...but desperately wanting to update my phone to a new android release at the very least. So, I need some input and advice.
1. What is the latest version of android that AT&T pushed an OTA for? Is it only a version of Lollipop?
2. If AT&T is only at lollipop, what are the pros/cons of going to a stock AT&T Lollipop rom vs. a Marshmallow or Nougat unofficial rom?
3. I will be leaving AT&T (at least postpaid) for either an AT&T Go plan, or for T-Mobile, Cricket, or H2O wireless. Will that affect my android version / rom choice? (Note: I am not SIM unlocked yet, but well qualified for AT&T to give me the code with no issues.)
4. A friend with an S5 Active on AT&T has WiFi Calling available on his phone. Is that available on the S4 with newer android versions or alternate roms?
5. Similar question re: using the S4 as a mobile hotspot...is that an android version or rom setting?
Honestly, given the fact that I never ended up flashing roms, I'm tempted to just get it to stock AT&T even if that means I give up my exploited and rooted status. I feed bad saying that since so many here are just the opposite, but that is just the way things worked out.
Thanks for any feedback / guidance that you can give.
Phone INFO (v3.25)
Device Type: jflteatt
Knox Warranty Void: Warranty bit not found
Bootloader: I337UCUAMDL
Baseband Version: I337UCUAMDL
PDA Version: I337UCUAMDL
CSC Version: I337UCUAMDL
Android Version: 4.2.2
Build Number: JDQ39.I337UCUAMDL
Well, no one ever replied, but here is what I've done:
1. updated my recovery to TWRP 3.0.0-0 by JDCTeam
2. did my various backups...though as for apps, there are quite a few I probably won't bother to reinstall
3. flashed JDCTeam's 7.1.1 LineageOS (20 Jan) w/gapps
4. had an initial issue with SuperSu but was able to fix
I'm still on bootloader MDL.
I'm still on baseband/modem MDL.
I may experiment with a newer modem but haven't yet.
I have my SIM Unlock code from AT&T but don't have an alternate SIM to pop in yet.
I'm still figuring out how things work/where they are in this build, and the real test will be when I get out to my car to make sure bluetooth pairs. But so far, so good.
texasniteowl said:
Well, no one ever replied, but here is what I've done:
1. updated my recovery to TWRP 3.0.0-0 by JDCTeam
2. did my various backups...though as for apps, there are quite a few I probably won't bother to reinstall
3. flashed JDCTeam's 7.1.1 LineageOS (20 Jan) w/gapps
4. had an initial issue with SuperSu but was able to fix
I'm still on bootloader MDL.
I'm still on baseband/modem MDL.
I may experiment with a newer modem but haven't yet.
I have my SIM Unlock code from AT&T but don't have an alternate SIM to pop in yet.
I'm still figuring out how things work/where they are in this build, and the real test will be when I get out to my car to make sure bluetooth pairs. But so far, so good.
Click to expand...
Click to collapse
Ah, so that was your Reddit post.
You should be set. 7.1.1 will inevitably have its issues, but who knows, my Nexus 5 is running it fine (not a great comparison but whatever ).
I'm actually on the MF3 baseband (bootloader-locked S4) in order to use AWS (3G+) bands under T-Mobile, but the MDL baseband should work fine for that. There's nothing you need to do besides never flashing a stock >MDL ROM.
negusp said:
Ah, so that was your Reddit post.
You should be set. 7.1.1 will inevitably have its issues, but who knows, my Nexus 5 is running it fine (not a great comparison but whatever ).
I'm actually on the MF3 baseband (bootloader-locked S4) in order to use AWS (3G+) bands under T-Mobile, but the MDL baseband should work fine for that. There's nothing you need to do besides never flashing a stock >MDL ROM.
Click to expand...
Click to collapse
lol! yep! that was me!
7.1.1 is looking good so far. I had no problems pairing with my car for phone calls today and the battery life so far is great. I hope I don't find any serious problems!
I figure if I made 3+ years on stock 4.2.2 TW rom, surely I can make it a couple more years running 7.1.1. I'm pretty much over constantly upgrading phones. It basically looks like a new phone right now considering the change from 4.2.2 (jelly bean?) to Nougat! :laugh:
DELETED
---------- Post added at 06:39 PM ---------- Previous post was at 06:29 PM ----------
texasniteowl said:
I almost feel bad asking, since I know some people would love to have an S4 that is still on MDL. However...my S4 needs an update and it is in fact still on android 4.2.2 and baseband MDL.
Anyway, I bought my S4 back in late June/early July 2013 and right before the locked/non-exploitable firmware's rolled out. So, I used the "CASUAL w/TWRP Recovery" method to root it and then I froze the update apps using Titanium Backup (AT&T SW Update v42, FWUpgrade 1.2.0, LocalFOTA v2). My intention at the time was to flash different ROMs on it, etc. Only...I never did.
So here I am, 3+ yrs later, no need for a "new" phone...but desperately wanting to update my phone to a new android release at the very least. So, I need some input and advice.
1. What is the latest version of android that AT&T pushed an OTA for? Is it only a version of Lollipop?
2. If AT&T is only at lollipop, what are the pros/cons of going to a stock AT&T Lollipop rom vs. a Marshmallow or Nougat unofficial rom?
3. I will be leaving AT&T (at least postpaid) for either an AT&T Go plan, or for T-Mobile, Cricket, or H2O wireless. Will that affect my android version / rom choice? (Note: I am not SIM unlocked yet, but well qualified for AT&T to give me the code with no issues.)
4. A friend with an S5 Active on AT&T has WiFi Calling available on his phone. Is that available on the S4 with newer android versions or alternate roms?
5. Similar question re: using the S4 as a mobile hotspot...is that an android version or rom setting?
Honestly, given the fact that I never ended up flashing roms, I'm tempted to just get it to stock AT&T even if that means I give up my exploited and rooted status. I feed bad saying that since so many here are just the opposite, but that is just the way things worked out.
Thanks for any feedback / guidance that you can give.
Phone INFO (v3.25)
Device Type: jflteatt
Knox Warranty Void: Warranty bit not found
Bootloader: I337UCUAMDL
Baseband Version: I337UCUAMDL
PDA Version: I337UCUAMDL
CSC Version: I337UCUAMDL
Android Version: 4.2.2
Build Number: JDQ39.I337UCUAMDL
Click to expand...
Click to collapse
You have the same phone I do! MDL bootloader for the win! To answer your questions:
1. Lollipop for the s4....s5 and s6 have marshmallow and nougat.
2. This is a user preference, some like touch wiz others don't.
3. It shouldn't as long as you're sim unlocked.
4. Not too sure on this one, I would say it's Samsung or at&t adding in that feature.
5. I also think this is an at&t or Samsung thing because my s3 has this feature and it's stuck on stock Android kit kat 4.4.2