Related
PLEASE READ EVERYTHING BEFORE ATTEMPTING TO INSTALL
This is a rooted, de-odexed, busybox, nano, ad-blocking hosts file, uncensored DNS resolv.conf but otherwise completely stock version of the 2.15.531.3 OTA for the T-Mobile G-2. This is not an update. It is a complete ROM.
I built this for my own use but anyone can take it and customize it as they see fit. I am a "Privacy and Security by Default" minded person so I have built it with a few alterations along those lines.
The ad blocking hosts file is to block known adware/malware from first boot. Updates to the hosts file as new threats are learned can be done by installing AdFree from Market or manually updating the hosts file yourself. I am not affiliated with the creators of AdFree in anyway. You can install it or not if you want or manually update your hosts file manually or not if you want.
The uncensored DNS resolv.conf I have included is because many ISP's and networks censor the Internet by controlling what you get directed to through DNS that is not what the official DNS record would require. They also hijack bad requests and typos through DNS redirects to their own search and ad pages. Google logs all DNS queries and what IP address it came from if you use the "open" Google DNS servers. I have included alternate secure and uncensored DNS settings as that is what I use myself.
I have now included a link to download a version of this ROM without those two customizations. I have not tested it myself but it should work fine for you if you choose to install it.
I used dsixda's kitchen to do the modifications and without that, I would probably not have done this at all. http://forum.xda-developers.com/showthread.php?t=633246
You will need to be rooted with S-OFF, Clockworkmod Recovery and engineering hboot to install this.
See this wiki guide for all information on rooting and downgrading the G2: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
See this thread for general information on the G2 also: http://forum.xda-developers.com/showthread.php?t=916431
THIS ROM IS SET TO WIPE THE SYSTEM BEFORE INSTALLING. MAKE SURE YOU HAVE A BACKUP OF ANYTHING IMPORTANT BEFORE INSTALLING THIS! The reason for this is that I can see potentially major problems if it is installed like an update. THIS IS FOR CLEAN INSTALLS ONLY.
You will need to install the radio that came with this OTA manually before installing this ROM. The radio version to install is 12.52.60.25U_26.08.04.30_M3.
Download the radio here: http://www.mediafire.com/file/51rr1vff4wamedg/TMOUS_G2_12.52.60.25U_26.08.04.30_M3_radio.img
Rename the file to radio.img and install it from fastboot. You need the Android SDK tools and platform tools installed on your computer and the engineering hboot installed on your G2 to do this. Shutdown the phone completely. Then hold the trackpad button while powering the phone back on. Connect the phone with the USB cable. Open a command prompt and change to the directory where the radio.img file is. Issue the following command:
fastboot flash radio radio.img
Wait for the radio to update completely and successfully and then disconnect the USB cable. Select "REBOOT BOOTLOADER" and verify from the fastboot screen afterwards that the radio is installed. Then select "BOOTLOADER" and from the bootloader select "RECOVERY" to proceed to install the ROM.
INSTALL THIS AT YOUR OWN RISK. I am not responsible for what you do with this and there is no implied warranties and guarantees.
I recommend a full wipe/factory reset from within recovery before installing this just to be safe. ***This does not revert you to S-ON or un-root the G2.***
MAKE SURE YOU HAVE BACKUPS OF ANYTHING AND EVERYTHING BEFORE INSTALLING THIS.
I do not plan to do any customizations of this but I will try to answer any questions that may come up.
***Update: I may post a version without the uncensored DNS setting and ad blocking hosts file as it is a simple tweak and there seems to be a calling for it. Stay tuned...***
***Update: There is now a link to download a version without the ad blocking hosts file and the uncensored DNS resolv.conf.***
Download: http://www.mediafire.com/file/b4w4a...d_S_TMOUS_2.15.531.3_signed_080311_215742.zip
Download without ad blocking hosts and uncensored DNS resolv.conf (untested by me, please let me know if there are any errors): http://www.mediafire.com/file/mh1zk...d_S_TMOUS_2.15.531.3_signed_080411_152226.zip
Good luck and have fun!
Awesome! Thanks!
Hey, can you tell us how you temp-rooted? That is actually all I'm interested in; I've been running Visionary on 2.2 to temp-root on boot, and that serves my purposes. I'd just like to be able to keep doing the same thing, although I realize Visionary won't work, but would you be able to put together a Visionary-like app that does give us temp-root on the new 2.3.4?
Thanks again!
Thanks bro! Can't wait to give it a go
Sent from my HTC Vision using XDA App
RebelScum75 said:
Awesome! Thanks!
Hey, can you tell us how you temp-rooted? That is actually all I'm interested in; I've been running Visionary on 2.2 to temp-root on boot, and that serves my purposes. I'd just like to be able to keep doing the same thing, although I realize Visionary won't work, but would you be able to put together a Visionary-like app that does give us temp-root on the new 2.3.4?
Thanks again!
Click to expand...
Click to collapse
In the DZ/G2 wiki are instructions for downgrading the 2.3.x factory installs using fre3vo to gain temp-root. As far as I know, there isn't any way to gain permanent root on an installed 2.3.x system.
spookievision said:
This is a rooted, de-odexed, busybox, nano, ad-blocking hosts file, uncensored DNS resolv.conf but otherwise completely stock version of the 2.15.531.3 OTA for the T-Mobile G-2. This is not an update. It is a complete ROM.
I built this for my own use but anyone can take it and customize it as they see fit.
I used dsixda's kitchen to do the modifications and without that, I would probably not have done this at all.
You will need to be rooted with S-OFF, Clockworkmod Recovery and engineering hboot to install this.
See this wiki guide for all information on rooting and downgrading the G2: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
THIS ROM IS SET TO WIPE THE SYSTEM BEFORE INSTALLING. MAKE SURE YOU HAVE A BACKUP OF ANYTHING IMPORTANT BEFORE INSTALLING THIS! The reason for this is that I can see potentially major problems if it is installed like an update. THIS IS FOR CLEAN INSTALLS ONLY.
You will need to install the radio that came with this OTA manually before installing this ROM. The radio version to install is 12.52.60.25U_26.08.04.30_M3.
INSTALL THIS AT YOUR OWN RISK. I am not responsible for what you do with this and there is no implied warranties and guarantees.
I recommend a full wipe/factory reset before installing this just to be safe.
MAKE SURE YOU HAVE BACKUPS OF ANYTHING AND EVERYTHING BEFORE INSTALLING THIS.
I do not plan to do any customizations of this but I will try to answer any questions that may come up.
Download: http://www.mediafire.com/file/b4w4a...d_S_TMOUS_2.15.531.3_signed_080311_215742.zip
Good luck and have fun!
Click to expand...
Click to collapse
I have a couple of questions. You say that we need to have a rooted phone already, but at the bottom you say that you recommend a full swipe/factory reset before installing this ROM. Wouldn't a factory reset get rid of the root and s-off?
Also, how do you install a radio and where would we get it from?
Thanks!
konoplya said:
I have a couple of questions. You say that we need to have a rooted phone already, but at the bottom you say that you recommend a full swipe/factory reset before installing this ROM. Wouldn't a factory reset get rid of the root and s-off?
Also, how do you install a radio and where would we get it from?
Thanks!
Click to expand...
Click to collapse
Flashing a radio: http://forum.xda-developers.com/showthread.php?t=896597
I would get the radio that is designed for this ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1202429
A factory reset will get rid of the entire ROM image on your phone. It will not change the s-off factor.
spookievision said:
In the DZ/G2 wiki are instructions for downgrading the 2.3.x factory installs using fre3vo to gain temp-root. As far as I know, there isn't any way to gain permanent root on an installed 2.3.x system.
Click to expand...
Click to collapse
spookievision,
To make this a "turn-key" pure vanilla stock GB rom, can you include the radio that seems to be missing, take away AdFree, and that other thing with config file you mentioned (forgive my noobness) and make a "white-wall" clean stock rom that can be flashed using CWM?
I want to experience this "stock" for myself, but i'm from CM7 and don't have any experience with flashing radios, and this config, AdFree files.. I would like to simply download, do a nan-backup (of my old CM7 rom), then flash without having to worry about any of the other stuff.
Thanks,
lawalty said:
spookievision,
To make this a "turn-key" pure vanilla stock GB rom, can you include the radio that seems to be missing, take away AdFree, and that other thing with config file you mentioned (forgive my noobness) and make a "white-wall" clean stock rom that can be flashed using CWM?
I want to experience this "stock" for myself, but i'm from CM7 and don't have any experience with flashing radios, and this config, AdFree files.. I would like to simply download, do a nan-backup (of my old CM7 rom), then flash without having to worry about any of the other stuff.
Thanks,
Click to expand...
Click to collapse
I have updated the first post with additional information about the radio and some more links. Unfortunately, I do not know how to get the radio to update through recovery so it has to be manually installed separately.
I have posted a new link and more information in the first post.
Who has successfully OC the official GB??
Need a link to proper kernal that wont breakanything
mike102871 said:
Who has successfully OC the official GB??
Need a link to proper kernal that wont breakanything
Click to expand...
Click to collapse
Any alternate kernel can potentially break things as they aren't what the system is compiled to work with originally. HTC hasn't released the kernel source for this version yet to my knowledge so alternates that would be the most compatible won't be available until they do.
I just flashed this rom through clockwork without wiping anythingfirst. It does install as a clean rom just like a new phone. Is rooted, Very nice. Ididnt install the radio suggested as the one i hadinstalled was a newer one than listed.
mike102871 said:
Ididnt install the radio suggested as the one i hadinstalled was a newer one than listed.
Click to expand...
Click to collapse
How'da have the radio? What version do you have, and how can I get my hands on it? Can you spare a link? Is so, how do I know what to flash?
Thanks.
mike102871 said:
I just flashed this rom through clockwork without wiping anythingfirst. It does install as a clean rom just like a new phone. Is rooted, Very nice. Ididnt install the radio suggested as the one i hadinstalled was a newer one than listed.
Click to expand...
Click to collapse
Without the proper radio, you might run into issues with data connectivity and WiFi Calling and potentially battery life issues. Let us know what you find.
And I'm glad you like it.
spookievision said:
I have updated the first post with additional information about the radio and some more links. Unfortunately, I do not know how to get the radio to update through recovery so it has to be manually installed separately.
Click to expand...
Click to collapse
I suspect that is what the fotaBoot "file" is for. I think it forces reboot to bootloader to flash the firmware.zip. just a theory and keep in mind, my rooted rom broke everything but the bootloader.
sent from my cyanogen(mod) vision
gee one said:
I suspect that is what the fotaBoot "file" is for. I think it forces reboot to bootloader to flash the firmware.zip. just a theory and keep in mind, my rooted rom broke everything but the bootloader.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
That is why I have manual radio instructions as I don't quite understand the factory update method yet. Which rooted ROM broke?
spookievision said:
That is why I have manual radio instructions as I don't quite understand the factory update method yet. Which rooted ROM broke?
Click to expand...
Click to collapse
It was my own attempt to make a rooted rom. I applied the system patches through CWM, modded the boot and recovery to use the new kernel, but did not flash the hboot nor radio. Stuck on boot screen with a broken recovery! It's still a work in progress.
sent from my cyanogen(mod) vision
gee one said:
It was my own attempt to make a rooted rom. I applied the system patches through CWM, modded the boot and recovery to use the new kernel, but did not flash the hboot nor radio. Stuck on boot screen with a broken recovery! It's still a work in progress.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I see. You have to break a few before you learn. And I've broken plenty in the past myself.
lawalty said:
How'da have the radio? What version do you have, and how can I get my hands on it? Can you spare a link? Is so, how do I know what to flash?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=970809&highlight=radio
The first one in the list. Came out 7/14
mike102871 said:
http://forum.xda-developers.com/showthread.php?t=970809&highlight=radio
The first one in the list. Came out 7/14
Click to expand...
Click to collapse
FYI: If you are looking for the radio that came with this OTA, I put a link to it in the first post of this thread.
Hi all, new to all of this. Please keep this in mind as you read this thread.
Well first of all I have been reading about Cyanogenmod and how it helps saves battery. I also wanted to use cputuner to overclock my phone a little. I have in the past rooted this phone and installed cputuner not knowing that it could damage your phone if you didn't have a custom kernel that supported overclocking. After I found that out I uninstalled it and unrooted in fear of damage to my phone. Anyways I have a few questions and was looking knowledge, resources, and help about a few things.
Questions:
Is installing a custom rom and things needed to install a custom rom possible with a PC?
Can I safely reroot my device since I unrooted through #SU?
What do I need to do besides reroot my device in order to install a custom rom? (Cyanogenmod)
Thanks in advance!
Other INFO:
My device is a Samsung Galaxy S3 I-747
Firmware 4.4.2 KitKat
Device was rooted before using towelroot but I unrooted using #SU.
.
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
jason2678 said:
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
KentuckyGuy447 said:
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
Click to expand...
Click to collapse
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
dawgdoc said:
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
Click to expand...
Click to collapse
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
KentuckyGuy447 said:
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
Click to expand...
Click to collapse
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
dawgdoc said:
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
Click to expand...
Click to collapse
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
KentuckyGuy447 said:
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
Click to expand...
Click to collapse
I'm stuck.
You can install a custom recovery without having root, if you have a PC. You would use either Odin, Heimdall, or maybe adb.
You can install a custom recovery without a PC if you have root. You would use an app Like Flashify, Rom Manager, or Goo Manager (if it still exists).
You can flash a rom without a PC if you have a custom recovery, root is not needed.
Some roms, usually stock, can be flashed without a custom recovery if you have a PC.
I don't know the solution until you have access to a PC. I could see it being possible using a live USB with persistence of a Linux distribution, but you still have need for a PC. It's been a while since I created a live USB. The method I used required a small installation on the PC. so I don't see this as an immediate solution for you.
Oh sorry. I don't think towelroot works once you're on nj1, unless it has been updated.
If you get access to a PC, rooting is still fairly easy. You can use download mode and odin or heimdall to flash a custom recovery (be sure to uncheck reboot if using odin, or be really ready to pull battery). Don't let your phone reboot normally, you'll have to pull battery once odin is done.
Reboot to custom recovery, then flash supersu and you'll be rooted again, and set up to do whatever you want with your phone.
Sent from my LG-V410 using XDA Free mobile app
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
KentuckyGuy447 said:
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
Click to expand...
Click to collapse
excuse for butting in .... but if you dont know your bootloader/modem info. here is an app called 'samsung info' that should tell you.
your question "...... but theres no bootloader for my phone model right?" kinda worried me. its important to know because they should match AND trying to downgrade can brick your device. on the plus side ; i've never seen a custom ROM include bootloader/modem in it.
again , just a thought and not trying to butt in.:good:
https://www.dropbox.com/s/4ka74x02tg1rrn1/org.vndnguyen.phoneinfo-1.apk?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"
As mrrocketdog stated, the Samsung Info app will tell you your bootloader and modem. If what you previously stated is correct, they should both be NJ1. You can get the same info by issuing these commands in a terminal emulator on the phone:
Code:
getprop ro.bootloader
and
Code:
getprop | grep version.baseband
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
KentuckyGuy447 said:
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
Click to expand...
Click to collapse
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
You have lifted a burden off my shoulders friend! Ever since I wanted to flash a custom Rom I've been worried if my phones bootloader was locked! I can now be at ease now that I know its unlocked. Will check upon that info about bootloader/modem.
Here is the info mrrocketdog
Is there a reason you can't use a PC to install a ROM?
I'm asking because I also do not know of a way to install a ROM without having root.
If you are able to root, you could try using the CM installer again.
audit13;5898140 said:
Thanks friend no worries, mrrocketdog helped me figure it out, than to all who helped!
Click to expand...
Click to collapse
KentuckyGuy447 said:
Here is the info mrrocketdog
Click to expand...
Click to collapse
Those are the latest versions of the bootloader and modem. You will be good for CM 12 or CM 11, and other custom ROMs based on CM. Older versions will work with them, but you probably need to edit the updater-script. (The older versions are not likely to include the NJ1 versions in the checks as they were not out when the ROMs were last updated.) NJ1 will also work with any of the ROMs based on the KitKat TouchWiz releases by Samsung.
As soon as you can find a PC to borrow you should be in business. Any chance of using one at a public library?
Appreciate all the help you gave me too friend, providing the links to cm and gapps, gonna borrow my friends laptop Sunday and try to root flash C-F Root through Odin. Thats the part that scares me but I should be good as people has confirmed it works for NJ1. Wish me luck friend. Would you recommend installing CM12? I personally like kit Kat and I know CM11 is based on that but is CM12 better? I guess its based on Lollipop
Took the stock ODIN ROM from the N910A. This ROM works without many bugs! Data, camera, etc all work without any patches required. In fact, the ROM can be completely used root-less as is. Stock kernel and errything. There might be some remnants of KNOX still intact. I haven't been able to check yet. If there is, I will add a script to remove the KNOX containers.
So, basically, this is the AT&T edition of the N910T3 ROM. Yet, it's debloated by a lot..
And yes, of course, no wifi calling or VoLTE.
Edit (10:30 @ October 25th: my piehole is a liehole. To remove any KNOX-y things left, just go into /system, and delete "containers". Inside TWRP.)
!NEW!: CSC folder now available to fix the ROM from being just a generic international thing.
NOTE ABOUT CSC: You will have to manually place it inside the system folder. It should look like this:
/system/csc/
IF THE FOLDER NAME IS NOT CORRECT, CSC FEATURES WILL NOT WORK.
CSC download link: https://www.androidfilehost.com/?fid=24269982087007357
Bugs: None, as I am aware. (Unless you count having the AT&T logo on startup.)
Some test screenshots: http://imgur.com/a/7d8DA
Modified build.prop with original AT&T values (and none of the Korean junk): https://www.dropbox.com/s/ug90i926pw51hgo/build.prop.nokorea?dl=0
Download: https://www.androidfilehost.com/?fid=24052804347846707
Installation instructions:
1. Unzip.
2. Place folder inside your TWRP backup folder.
3. Wipe everything except internal 2-3x
4. Restore Boot+System.
5. Reboot into the new ROM and enjoy, I think.
Root instructions:
1. Install a CUSTOM 5.1.1 KERNEL. If you don't install a custom kernel, you will BOOTLOOP.
2. Run the root script inside TWRP.
3. Enjoy root, I guess.
What's the benefit to using this ROM over a n910t3 5.1.1 rom?
McMichael96 said:
What's the benefit to using this ROM over a n910t3 5.1.1 rom?
Click to expand...
Click to collapse
There may not be one, really. But hey, it's nice to have choices.
-
I did, however notice lighter RAM usage upon initial setup. After adding a few apps, it's still lighter than some other ROMs I've used. That might be because this ROM is odexed, though.
eduardog131 said:
There may not be one, really. But hey, it's nice to have choices.
-
I did, however notice lighter RAM usage upon initial setup. After adding a few apps, it's still lighter than some other ROMs I've used. That might be because this ROM is odexed, though.
Click to expand...
Click to collapse
Oh alright, I'm waiting for it to download. Can't wait to install
McMichael96 said:
What's the benefit to using this ROM over a n910t3 5.1.1 rom?
Click to expand...
Click to collapse
Well the T3 5.1.1 rom has some bugs particularly surrounding the fingerprint unlock. Perhaps someone could use this rom to fix the bug in the Tmo 5.1.1 roms.
i cant get rom to show up in my backup folder in recovery
blane3298 said:
i cant get rom to show up in my backup folder in recovery
Click to expand...
Click to collapse
Place the ROM inside your TWRP backup ID folder. (I.E. /TWRP/backups/(youridhere)/2015..../
I don't want to sound like a douchebag or anything, but WHY would anyone ever want to run AT&T firmware on anything ever in life if they don't have to??
freeza said:
I don't want to sound like a douchebag or anything, but WHY would anyone ever want to run AT&T firmware on anything ever in life if they don't have to??
Click to expand...
Click to collapse
The word today is choices....simple do or don't lol
Sent from my SM-910T using Tapatalk
freeza said:
I don't want to sound like a douchebag or anything, but WHY would anyone ever want to run AT&T firmware on anything ever in life if they don't have to??
Click to expand...
Click to collapse
I was messing around with random firmwares. I just ODIN'ed the AT&T stock firmware without changes and it worked pretty snappy. Even with the bloat. So I thought, why not just package this as a complete stock (debated) firmware?
Also, I am currently messing around with the Korean N910S (SKTelecom) firmware. Fun stuff. Currently the stock kernel doesn't work. Just out of boredom.
eduardog131 said:
I was messing around with random firmwares. I just ODIN'ed the AT&T stock firmware without changes and it worked pretty snappy. Even with the bloat. So I thought, why not just package this as a complete stock (debated) firmware?
Also, I am currently messing around with the Korean N910S (SKTelecom) firmware. Fun stuff. Currently the stock kernel doesn't work. Just out of boredom.
Click to expand...
Click to collapse
Keep doing your thing man
Sent from my SM-910T using Tapatalk
It seems that the ROM from the N910S doesn't boot. Flashing the boot.img automatically makes it go into "Could not do normal boot" mode. Flashing any other custom kernel just makes it bootloop. I can't figure out what's wrong with it though. Really sad about it, since the Korean versions of these phones have features hidden away that other countries can't use or access.
-
Was thinking that it was due to it being a firmware for the N910C. I checked and of course, the N910S doesn't have an Exynos chip. So that's not why it doesn't boot...I'm really stumped.
I think VoLTE has been fixed. Adding the T-mobile CSC to /system from the 5.0.1 firmware adds the option to use or disable VoLTE. However, I have not been able to use it yet, because I think it requires another T-Mobile user that has VoLTE as well.
-
The IMS settings required for VoLTE to work are also included inside the imsprofile.xml for the CSC. The system decides what to use via the sales code from that CSC. Basically, this is a ramble post and I might make the CSC a separate zip that yall can add to /system.
This is definitely a great DevBase
Any way to deodex this?
blane3298 said:
Any way to deodex this?
Click to expand...
Click to collapse
The first time I tried to deodex, it failed*.
The second time, it failed*.
So, you probably can, run it through the lollipop deodexer. I don't recommend it however, as odex'ed gives faster speed in some cases.
*It never went past the AT&T logo, and just bootlooped
do you know if xposed works on this rom
blane3298 said:
do you know if xposed works on this rom
Click to expand...
Click to collapse
Since it's odex, no
Sent from my SM-N910T using Tapatalk
I'm already at N910A 5.1.1. You think that'll work?
Those instructions are not noob-friendly. Thanks anyways. Hopefully a deodoxed version will come out so it's an easier installation.
frankie1220 said:
I'm already at N910A 5.1.1. You think that'll work?
Those instructions are not noob-friendly. Thanks anyways. Hopefully a deodoxed version will come out so it's an easier installation.
Click to expand...
Click to collapse
N910A has a locked bootloader. You need TWRP in order to restore this backup. I don't know if the N910A has a special TWRP available for it or not...
Hello,
I want to root my friends sprint note 4 (lolipop i believe). I was looking at this guide http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4note-edge-on-android-5-1-1/ and it seems straightforward. A little different than what I had to do with my phone becuase I had to unlock the bootloader and then flash the recovery and supersu. (I've never used odin) Does this mean the bootloader is already unlocked by default since all I have to do is install the recovery and then the kernel?
I'm a little confused, once I get the recovery, can I flash roms to it? Do I have to change the kernel again if I want to install a ROM? I don't plan on putting a custom ROM on his phone but I want reflash the stock rom or a debloated stock rom because he said even after a factory reset it was buggy (if you can link me to a proper stock rom that supports xposed I would be grateful).
And I also want xposed to work, is there a specific xposed version I should install?
And also, if I do flash something, is this method correct?
Backup data
factory reset
flash
clear cache
restore data
reboot
or do I restore the data later?
The thread and video are dated. A few key elementary facts are still relevant but as a whole, just not up to date. I wouldn't trust it and it lends to repeated help threads in this forum. If one read the OPs and threads of current ROMs in development and recent help threads, maybe less questions and help would be needed.
He omits current ROMs, didn't mention where the reactivation lock is for TW Android ROMs: Settings/Security/Reactivation lock (should be disabled). He doesn't mention Chainfire Auto root for Note 4 has been updated for 5.1 and will be key again for marshmallow (but that's only needed for rooting stock Odex). He also didn't tell you how to get to those old ROMs on his site. Some think you just Odin an old update but not so. That requires a 5.1 kernel matched with current bootloader rather than Odin downgrade.
The bootloader, while not locked to block root, is considered unlocked but actually is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Kernels should be kept in zip form because backing up a kernel in TWRP doesn't backup /system/lib/modules to restore and some custom kernels modify or add modules which may not work restored boot.img And restoring stock kernel on a rooted phone would cause a boot loop. So to restore that, you'd need to full un-root in SuperSU to avoid the boot loop there as well as restore the stock /system/lib/modules.
Root methods: unless you're using the full un-root or wiping everything but extSdCard (particularly user data and internal memory), you don't fully remove systemless root. Flashing a ROM or SuperSU with system based SuperSU over systemless root without the wipes would break things like root. Not seeing the SuperSU app or loss of ability to add new apps to superuser would be impacted but also a boot loop is possible if but patching stock kernel su.img to boot.
The basic principal is that to flash the custom deodexed ROM you need for Xposed, just make sure you're on the right update, Odin TWRP and follow the OP closely. If wiping internal memory is suggested by OP, I'd suggest that. To keep things simple, I backup and wipe everything but extSdCard for ports or where Xposed or systemless SuperSU is used. I typically do the same for stock tar updates as well.
As to recommended ROMs, I'd suggest any deodexed OK1 ROM for Xposed. tx_dbs_tx has a variety of OK1 ROMs. Freeza has one with Xposed integrated with Xposed modules in system. If Note 5 Moar port is a good fit, I'd recommend trying without Xposed until you determine the minimum of Xposed mods you're lacking so you're not overlapping features and you're getting to know the stability of it, first.
Rooting a friend's phone? IMO, you should be very sure and confident before proceeding and advise rather than do all the work and take the risks yourself. Use the correct USB driver, not just one that works. Setup his computer to root and sustain that phone.
Sent from my SM-N910P using Tapatalk
How is it dated exactly? I thought 5.1 is highest OTA for Note 4? Do OTA security patches change how things work now? I wouldn't know about security patches since I have a moto x 2013, we are left in the dust.
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version? Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
rapiollymega said:
How is it dated exactly? I thought 5.1 is highest OTA for Note 4?
Click to expand...
Click to collapse
I answered that in detail.
rapiollymega said:
Do OTA security patches change how things work now?
Click to expand...
Click to collapse
No; it's the bootloader and updates that did that.
rapiollymega said:
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
Click to expand...
Click to collapse
Good choice.
rapiollymega said:
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version?
Click to expand...
Click to collapse
Answered. Use Phone Info from Google Play or Galaxy Tools.
rapiollymega said:
Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
Click to expand...
Click to collapse
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
samep said:
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Click to expand...
Click to collapse
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
rapiollymega said:
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
Click to expand...
Click to collapse
It's the INTERNET that's ambiguous towards Touchwiz Android 5.1 There has been a few updates and each changed the way we do things. So when you say you're on Android 5.1, I say you need to be on the latest 5.1 update to have the greatest compatibility with the ROM you're choosing to flash.
Yes. You use Odin to install TWRP when rooting from full stock un-root to custom pre-rooted ROM. Perhaps my direction to Odin TWRP was ambiguous? Flash this in Odin AP slot with auto reboot unchecked- use the other option defaults from latest Odin:
https://dl.twrp.me/trltespr/twrp-3.0.0-0-trltespr.img.tar.html
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
I would restore data after installing Xposed. Keep in mind that these installation boots of custom ROM and Xposed take time. The less apps and data, the shorter the boot times will be. Plus the ROM will have more time to stabilize. After you've verified the last three of the bootloader and modem matches OK1, you can proceed with TWRP, then install ROM per the 1st post and immediate posts from OP. When you get to the Wi-Fi connection in setup wizard, make sure you have radio signal before connecting Wi-Fi. Make sure everything is stable and functional before Xposed installation.
Again, about the long boot times on installation. Best to keep case off the phone and ventilate phone with not too cool or ambient air. This will speed the process and possibly prevent component failure.
When your ready for Xposed, you need the Wanam unofficial Xposed framework.
http://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
You'll need sdk22 arm for Lollipop, not 64 bit Exynos or MM.
Currently it's the one labeled: xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip
Grab the uninstaller too, just in case. You shouldn't need it but be prepared.
Edit: be sure to get the deodexed version of that ROM. Makes things easier for Xposed and Xposed compatibility when adding system applications, if that applies to anytime later.
Sent from my SM-N910P using Tapatalk
Thanks for all the help, did it over the weekend and everything went smoothly. Well except for one part before installing the new ROM, I deleted everything in data/system and forgot that the zip was In the internal storage instead of the sd card . And for whatever reason the PC usb connection wasn't working in TWRP so I had to use a flash drive and otg cable to put the zip ROM back in the phone.
Hey, guys, I wanted to ask if someone tried OTA updates working with the new method of rooting released with magisk 14- a rooting method in which we do not need root or custom recovery beforehand, we just need to provide stock boot image dump to the magisk manager. This method will do us good because if OTA's still work after root we can be rooted on the stock roms without having to download full OTA's when a new update arrives. If someone can confirm working OTA's on the OOS open beta with this root method, it would be really helpful. Thank you!
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Puddi_Puddin said:
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Click to expand...
Click to collapse
Bro, I know how to work with TWRP. Your comment does not answer the question.
blaze95rs said:
Bro, I know how to work with TWRP. Your comment does not answer the question.
Click to expand...
Click to collapse
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Puddi_Puddin said:
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Click to expand...
Click to collapse
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
blaze95rs said:
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
Click to expand...
Click to collapse
See it for yourself! Its something most people do not recommend.
Puddi_Puddin said:
See it for yourself! Its something most people do not recommend.
Click to expand...
Click to collapse
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
blaze95rs said:
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
Click to expand...
Click to collapse
That doesn't matter. I get that it can be installed without a custom recovery. But that doesn't mean it won't conflict with possible ota's. Again, see it for yourself. Most people including me do rather play it the safe way.
I have recently updated to the lateset Oxygen OS Beta i had Magisk installed, i use Sparks Latest twrp version, with this you can install OTA updates. I dit not unlinstalled Magisk first, you do need the full rom file, but for me when i wanted to install the OTA, it found i had rooted and autmatacly downloaded the full rom. After you installed the update you can install the latest version of Magisk.