i have a question, if you unroot the tablet, it will restore it to stock rom? even if i do have a custom rom on it like virtuous prime or so?
nope that is not true
if you rooted your device you can still be on stock Rom
but it seems like you unlocked your device which means you cannot get the stock Rom
is there any way to come back to stock?
nope
unlocking is a one way street
just wondering, why are you trying to go back to stock?
there seems to be a problem with my wifi when i installed virtuous prime rom, it shows grey instead of blue... and my google talk app stopped working because of that or something...
-thanks for helping anyway
Added this to my faq:
Unwinding - Unroot/Relock
Rooting is reversable. In effect, root requires you to add a couple of files to the normally read-only /system area. These files may be included in a ROM which you flash, and you could easily un-root any ROM if you needed to. Some apps may check for the presence of root, for example.
On the prime, bootloader unlock is a one-way street. First, your serial number is logged by ASUS. 2nd, the process of unlocking is to replace your bootloader with one which no longer checks that it is loading a signed kernel - you are still unable to replace the bootloader. This makes it impossible for any dev to easily re-lock your prime. Unlocked can still flash any ROM (custom one or re-packaged stock) - just never a stock ROM direct from ASUS (either OTA or as a full-wipe).
djcasao said:
there seems to be a problem with my wifi when i installed virtuous prime rom, it shows grey instead of blue... and my google talk app stopped working because of that or something...
-thanks for helping anyway
Click to expand...
Click to collapse
the wifi icon showing grey instead of blue usually is just a bug i have that sometimes on my stock ROM
i suggest you try seraching on the virtous prime thread to see if there is anything fix or even give a post there and see if there is a solution
if not you can always try flashing another ROM onto your prime
Related
are running a custom ROM? My friend just called me & said he just got a phone call from 5print & they wanted him to download a file to update his OS. He did not do this yet because he is running a custom ROM & not sure if it will brick his phone or corrupt the OS. Any ideas?
anyone?....anyone?
Turns out they just wanted him to downgrade back to the older ROM, they also confirmed the new ROM will be out soon...so nothing new.
well assuming that his phone is hard-spl then he can flash whatever he wants. as long as its for his device he will be fine.
What is a five print ROM?
Also, if they come out with a five print ROM (heh) with rev A and GPS enabled will we be able to custom ROM it onto a five erizon phone?
Mods, I'd have liked to have posted this as a reply to Andybones' thread, but I'm under 10 posts, so please move as needed.
So, I got my Rezound from eBay and figured I'd root it and update it.
Went through the HTC Unlock Bootloader process.
Setup Perm Root
Installed Amon Ra Recovery 3.1.3
Allowed OTA to take place to get to 2.01.605.11.
Went into Amon Ra and had it install superuser and su.
Figured it was an eBay phone and should be wiped clean, so from bootloader did a Factory Reset
After it rebooted a few times, phone came up and "Wifi Error". Everything else working perfectly- 3g, 4g, voice, bluetooth... just no WiFi. Unable to stop or start it in settings GUI.
Hunted online for "WiFi Error" and Rezound and found a few posts asking about clearing cache and dalvik; another few were referencing Kernel and/or module installs.
Cleared cache and dalvik to no avail.
Searched for 2.01.605.11 Kernel and found Andybones post. Installed the Kernel and Wifi was working with everything else again.
So the question-- now that it is fixed and working-- what the heck happened to have broken my WiFi for that duration? Was it when I did the Factory Reset that I somehow screwed up my Wifi Kernel Module? If so, how? Did Factory Reset install some older module or Kernel? Or, was there something broken in my OTA? I saw mention of one other person whose WiFi was broken after OTA to 2.01.605.11-- he also resolved by using the Andybones post to install the Kernel.
Unfortunately, after seeing that the WiFi wasn't working, I didn't think to check what Settings showed for my Kernel, or to try checking mass storage for file dates or versions-- I know those could probably have helped in ascertaining what occurred.
Anybody else experience WiFi broken after OTA?
Thanks in advance!
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
feralicious said:
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
Click to expand...
Click to collapse
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
andybones said:
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
Click to expand...
Click to collapse
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
feralicious said:
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
i had this problem a few times...the last two times i think it was because i had wifi tether on then stupidly i turned on verizon tether app and so wifi and verizon mobile hotspot/wifi tether stopped working and kept giving an error message...i had to flash a version of incredikernel i had laying on my card and everything worked fine..kind of wierd but whatever lol and once i believed it just happened out of nowhere so i just reflashed everything..that time wiping and flashing the rom all over again worked but all other times i needed to flash a kernel. i believe i was running clean rom all those times and once happened on ICS i think..running the latest clean rom 1.6.5 and havent had those issues yet( knock on wood)
feralicious said:
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
Click to expand...
Click to collapse
That's what I'd have thought, too. I am/was completely stock and my update was OTA. Didn't touch any 3rd party kernels or ROMs. I want to make sure phone works as intended before considering messing with other ROMs/Kernels.
EDIT: Found this older thread which is very similar -- mods can probably close mine or migrate the posts over to the older one since my query resembles what SquireSCA experienced.
feralicious said:
Are you willing to factory reset again?
Click to expand...
Click to collapse
Yeah, tempted to give it a shot after doing an Amon Ra backup to see if it was the factory reset that did me in. I can head back to the Andybones kernel thread to recover again if needed. Probably not going to test it right away though. Still settling in with the phone.
One variable that I didn't consider-- when I did my OTA-- I did not re-lock the bootloader prior. Any possibility of correlation?
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
I have a nand of my phone from right after I did my OTA without relocking. When I get around to doing my fresh installs I will restore that and check it to see if I have the same issue. I'll probably do it when I get back home later tonight. I'll post back afterwards to let you know.
So I just restored my nand from when I went back to stock recovery, ROM and kernel (all 1.x) and then accepted OTA. wifi was broken until I flashed the new 2.x stock kernel. That was from when I got the OTA without relocking the phone. I meant to check what the kernel said before I flashed the 2.x stock one but forgot. Argh... now I want to go back to Ineff and do this again to check it.
EDIT: Well, I went back to my stock OTA nand again and the kernel shows as dsb. So I can't replicate what I did earlier since I had flashed the stock kernel before getting the OTA and I guess the nand doesn't back up/restore the kernel.
I don't know what condition wifi was in when I made the nand since I didn't know to check and I just made that as a safety copy and went back to Ineffabilis right away.
I did flash the stock 2.x kernel to get wifi working on stock OTA, then restored my Ineffabilis nand and again, the only way to get my wifi back was to flash the dsb kernel. The stock rooted kernel that came with Ineffabilis didn't do it. Gonna go post on the dsb forum and see what they say. Also, tomorrow I'm going to run the RUU and factory reset and try to get this thing totally clean and see if I can use a different kernel than dsb. Ineff was just updated to 2.x so perhaps flashing the new ROM will break the chains.
feralicious said:
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
Click to expand...
Click to collapse
Soooo... I was reading some of the ICS threads and getting really curious about installing. Saw a post by someone mentioning they're on baseband 0.95.00.1118r. Went to check mine, and I'm on 0.95.00.1017_2r . Checked the Verizon site and OTA 2.01.605.11 provides 0.95.00.1118r . Did some more digging to figure out how I got left behind using the official OTA and came upon this post:
Baseband does not update without a re-lock first.
EDIT: found plan of attack via http://forum.xda-developers.com/showthread.php?t=1467329 and will give it a shot this evening.
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
EmerikL said:
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
Click to expand...
Click to collapse
Thanks!
Off-topic: Any alternatives to using Filefactory or Dev-host to download the RUU? Has anyone done a sniff during the OTAs to see what URL is used to download the RUU? Does VZW restrict what IPs/MACs can download the updates? Or do they use a proprietary protocol? Or are the updates strictly via their CDMA/LTE, without WiFi?
Mission accomplished-- I now have radio 0.95.00.1118r on my 2.01.605.11.
I did follow the http://forum.xda-developers.com/showthread.php?t=1467329 directions, and I'm posting the commands used for future ref in case needed again:
1) downloaded vigorOTAStockRooted.zip after midnight pacific time (download didn't die) and then copied it to the sdcard.
2) {boot into Amon Ra} adb reboot recovery
a. backup everything
b. install vigorOTAStockRooted.zip
3) {install drops the ph98img.zip file on external sdcard-- but it won't install with unlocked bootloader. need to lock the bootloader} fastboot oem lock
4) {installation finished up, let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
5) {go into bootloader} adb reboot bootloader
6) {get token to submit to htcdev.com; once displayed, plop in the token, and wait for email} fastboot oem get_identifier_token
7) {once email with token received, flash it} fastboot flash unlocktoken Unlock_code.bin
8) {let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
9) {reboot into bootloader to install Amon Ra Recovery} adb reboot bootloader
10) {install Amon Ra} fastboot flash recovery recovery-ra-vigor-3.14-gnm.img
11) {enter recovery - from HTC bootloader, go to recovery} select menu item to go to recovery
12) {restore} from Amon Ra recovery, restore the backup from step 2a and then reboot
I bought a Rezound on ebay, pre-rooted/unlocked with the leaked ICS / Sense 3.6 ROM (besides that, pretty much bone-stock)
I decided I wanted to try out a different ROM and make sure I am familiar with the process before I try to do the S-OFF process....
Well, I found that the first thing I needed to do to upgrade to (insert ICS/Sense 4 Rom here) was to upgrade to the newest Firmware (3.11.605.22), and I am currently on 3.11.605.01 ... I followed their instructions closely to update the firmware ( re-lock , load new FW as PH98IMG.zip , flash it , unlock, etc)
Well, that didn't work for me, when I got to loading up hboot and it automatically updating the FW, it didn't do what the instructions said it would, it showed a dark blue bar near the top/right, waited for that to complete, then same thing but yellow, that completed and asked to reboot, but would only reboot to fastboot...
eventually I unlocked it again and it allowed me to return to my ROM (normal ICS/sense 3.6)
Sorry about this short story... lol ^
Basically I cannot for the life of me install any rom with success... I can't even restore the nandroid I made last night (before any of this) with success..
the CLOSEST thing to success I got was installing newts One XxX sense 4 rom, it booted, and will sit on the lock screen just fine, but when I try to unlock and go to settings to turn off animations (like instructed) it will freeze and reboot....
DO I need to install the newest FW???
OR what do I need to dooo?
Pls help! I am fairly familiar with android, as I had a D Inc before this, evervolv ICS etc etc....
Thanks alot anyone !
x70xchallengerx said:
I bought a Rezound on ebay, pre-rooted/unlocked with the leaked ICS / Sense 3.6 ROM (besides that, pretty much bone-stock)
I decided I wanted to try out a different ROM and make sure I am familiar with the process before I try to do the S-OFF process....
Well, I found that the first thing I needed to do to upgrade to (insert ICS/Sense 4 Rom here) was to upgrade to the newest Firmware (3.11.605.22), and I am currently on 3.11.605.01 ... I followed their instructions closely to update the firmware ( re-lock , load new FW as PH98IMG.zip , flash it , unlock, etc)
Well, that didn't work for me, when I got to loading up hboot and it automatically updating the FW, it didn't do what the instructions said it would, it showed a dark blue bar near the top/right, waited for that to complete, then same thing but yellow, that completed and asked to reboot, but would only reboot to fastboot...
eventually I unlocked it again and it allowed me to return to my ROM (normal ICS/sense 3.6)
Sorry about this short story... lol ^
Basically I cannot for the life of me install any rom with success... I can't even restore the nandroid I made last night (before any of this) with success..
the CLOSEST thing to success I got was installing newts One XxX sense 4 rom, it booted, and will sit on the lock screen just fine, but when I try to unlock and go to settings to turn off animations (like instructed) it will freeze and reboot....
DO I need to install the newest FW???
OR what do I need to dooo?
Pls help! I am fairly familiar with android, as I had a D Inc before this, evervolv ICS etc etc....
Thanks alot anyone !
Click to expand...
Click to collapse
If you want to go back to a GB rom you need to reflash the boot image that came with it. If you want a sense 4.0 to work you need to flash the old firmware patch. For the patch I have attached it. Flash it via recovery and your rebooting on a sense 4.0 rom/ new firmware rom should be gone. (don't forget to follow the OP for Newts rom about disabling animations btw) for the boot images look to the op of the rom you are running.
cstrife999 said:
If you want to go back to a GB rom you need to reflash the boot image that came with it. If you want a sense 4.0 to work you need to flash the old firmware patch. For the patch I have attached it. Flash it via recovery and your rebooting on a sense 4.0 rom/ new firmware rom should be gone. (don't forget to follow the OP for Newts rom about disabling animations btw) for the boot images look to the op of the rom you are running.
Click to expand...
Click to collapse
Ok thanks for the reply, I did install the "old firmware patch" included with Newts XxX Sense 4 ROM, and I can successfully get the ROM to boot, it doesn't operate very well, and only for a few minutes because it will freeze and reboot. It doesn't allow me to get to the settings, no matter how fast I try to get there, it ALWAYS freezes before I can access the setting :/ ...
x70xchallengerx said:
Ok thanks for the reply, I did install the "old firmware patch" included with Newts XxX Sense 4 ROM, and I can successfully get the ROM to boot, it doesn't operate very well, and only for a few minutes because it will freeze and reboot. It doesn't allow me to get to the settings, no matter how fast I try to get there, it ALWAYS freezes before I can access the setting :/ ...
Click to expand...
Click to collapse
Hmm.. wow I'm lost. I had the same issues before I installed the patch, but after I didn't and it went fine. I'm going to have to think about this one for awhile.
cstrife999 said:
Hmm.. wow I'm lost. I had the same issues before I installed the patch, but after I didn't and it went fine. I'm going to have to think about this one for awhile.
Click to expand...
Click to collapse
Okay after flashing the ^above^ patch, the rom seems to work now, it didn't freeze so I was able to turn off animations and now it works might fine
Do you know by chance any good kernels for an ICS/Sense 4 ROM?
the stock one was draining faster than it was charging (while plugged in lol)
So I tried out the 1.836 OC kernel and it seems to be working fine, but I am interested more in battery life than performance right now, coming from the DInc, this phone is buttery smooth and doesn't REALLY need OC just yet (for me anyway)
Thanks for the help by the way!
So I've rooted my phone less than a month ago, and I get this bug where the phone just freezes for 10-60 seconds, pressing the power button does nothing, I just have to wait until it sorts itself out. It happens quite often, and it's really annoying. One guy mentioned the same bug in the HTCDev unlock/root thread, but he was lucky enough to have the AT&T version, so he was able to get back to stock with the ruu.
I've already performed a factory reset twice, but it didn't help.
Does anyone know what my course of action should be? Should I download one of the back-ups, which one and so on. Also, how to get back to stock recovery, because TWRP doesn't let me do OTA upgrades.
I bought the device in Croatia, if that means anything, because I've seen dozens of different twrp backups so far.
Thanks in advance guys
HTC Desire 610 AT&T and EU is not 100% same phone, firmware also have pretty different version numbers: latest AT&T is 1.53.502.1* EU 1.31.401.3(Croatia).
So you cannot expect that everything will go without any problems.
Sorry I replied before I fully read your question.
You're on the stock Rom and kernel?
Stock rom, JMZ's kernel.
JMZ probably took source code from HTCDEV for US(AT&T) version of phone, some people with EU/International version of phone have similar problems like you (member DulinDuskhawk) with JMZ Kernel.
Please go to thread "Jmz A3UL Kernel v1" and ask someone for stock EU kernel or send message to member DulinDuskhawk, maybe he found a solution.
TomoBero said:
JMZ probably took source code from HTCDEV for US(AT&T) version of phone, some people with EU/International version of phone have similar problems like you (member DulinDuskhawk) with JMZ Kernel.
Please go to thread "Jmz A3UL Kernel v1" and ask someone for stock EU kernel or send message to member DulinDuskhawk, maybe he found a solution.
Click to expand...
Click to collapse
Hi TomoBero, I'm not 100% sure but I think jmz's kernel is made from 1.30..... international htc sorces (I'll check soon for exact version) as there where no at&t sources available at the time he did it. I think most problems with flashing other kernels is the fact that HTC built kernels are configured to only be able to load modules that were compiled specifically for that kernel. This is definately what has caused wifi to stop working for many people who have flashed other peoples backups or at&t rom(withut backing up atleast the own /system/lib/modules from their origianal rom as when gong back to their original kernel the modules no longer match the kernel). I have a build environment set up for compiling the kernel and have local sources for 1.29.... asia ,1.31...... EU_international, and 1.30.....US at&t. I can (and have) compiled these kernels as stock with just the flag changed to allow loading of modules that don't match version. If you let me know the software version number you (or others) are running I can supply a kernel update.zip and seperate /system/lib/modules.zip that matches software version and you to return to stock and experiment with modules if still having promlems. I havn't merged jmz's insecure /system code into these sorces so apart from allowing the kernel to load non-matching modules they are comletely stock.
MiniBlu
Hi MiniBlu, it's 1.31.401.2
Do you by any chance know how I could return my device to stock recovery, so i can install OTAs?
Thank you so much dude
I'm in the same boat. I'm trying to get back to stock, somehow.
I really need to go back to stock as soon as possible, the sim card locking mechanism doesn't work all of the sudden, and I've read it has happened to hundreds of 610s already. Because I'm unsure if my guarantee will work after root (although it's a hardware fail), i really need to get rid of the red disclaimer at boot (although I sadly think it can only be achieved with S-OFF). :c
I just rooted my phone (Samsung S6 Edge [SM-G925P] running Android 6.0.1) this Friday and I have a couple of questions about using the CyanogenMod ROM and installing Xposed. To note, I am pretty, pretty new (I literally just rooted 2 days ago.
So my question about CyanogenMod is will it run on my rooted Samsung and is it dedoxed? I already have TWRP and SuperSU flashed and installed on my phone.
And my question about Xposed is will it run on my phone, as well with CyanogenMod, TWRP and SuperSU? I tried installing it with the original ROM on my phone, but that provided to be disasterous since it soft-bricked my phone, but I heard that was because my ROM was deodexed.
Hi NovaViper ! It depends. Cyanogenmod and other ROMS can come in two flavors: odexed or deodexed. The one on the official Cyanogenmod Website is deodexed. If you go on Cyanogemod's official website they don't have a ROM for Samsung Galaxy S6 / Edge. Check it out: http://download.cyanogenmod.org/ Look at the left to see supported devices. Unfortunately, it's not there. Some Galaxy S6 / Edge models do support Cyanogenmod but as for your model the SM-G925P there is still no official support for CM ROM. Check this link out: http://forum.xda-developers.com/gal...development/cyanogenmod-13-galaxy-s6-t3269984 Just out of curiosity, why do you want to install CM on your device?
I want to try CM because I heard it offers full customization.. I really would like to customize the lockscreen and colors of the UI especially and because it is deodexed, so I can also add Xposed. I have another ROM atm called Mostly Stock (its based on ROM but its deodexed and have a few changes to the stock UI, BUT it still has the parts I hate about the stock ROM). I specifically want CM because I haven't found any other ROM that offers full customization, deodxed for Xposed, and most importantly, is not like the stock ROM.
Oh, also with CM, I tried to install it but it said my device isn't support.. I tried the one from the link
If you want a full stable ROM for Samsung Galaxy S6 Edge and XPosed on it I would recommend this ROM: http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519. My friend has it on his ROOTED S6 Edge and it offers even more customization's then Cyanogenmod plus you can install XPosed on it. Give it a try.
Thanks I already flashed it but I notice that it isn't responsive to touch. I can interact with the buttons but no response to touch whatsoever. Seems like there isn't a ROM that works with my SM-G925P, the edge that rom works with is a G925F
Hmm, I thought it would work on your model. Try this: http://androidfreeroms.com/renegade-android-m-6-0-1-aroma-rom-sprint-samsung-s6-g925p/
I got the rom flashed and running.. but i cant seem to restore my messages from the samsung backup.. i can only get them from Textra (which doesnt export them). Also, i cant receieve text messages either.
Well, I finally got my messages backed up but.. I notice something else now. I had installed Xposed, which ended up giving me a bootloop and I had to factory and data reset, and reflash my stock rom. then I installed TWRP and then Renegade, but the mobile data isn't working anymore. Its just black the black bars.. I can't even find the Mobile Data enable button anywhere. (It works on stock rom though). To point out, mobile data WAS working before I installed Xposed. Right now, I'm reflashing my stock rom and seeing if it works.
--UPDATE 1--
Yeah, the stock mobile data works.. although I do have a theory on what could be going on
Theory 1: It could be I have to install my ROMS a certain way, initally, I had stock ROM, then I added the "Mostly Stock ROM" THEN I added Rengeade when you suggested it to me
Theory 2: Possibily signal strength/proxies (I'm doing this at on my school's wifi)
Theory 3: Something that Xposed has modified and its still there
--UPDATE 2--
I did the first theory and it worked successfully BUT.. I did remember that I had installed SuperSU soon after flashing twrp (which came after i flashed the stock rom).. Now I'm trying to see if that made a difference.
--UPDATE 3--
Ok, so it seems that it is a certain install order (tried with both superSU installed first and without). But I'm worried now about installing Xposed.. as I'm now nervous that it may end up messing up my phone again (It took a while for me to figure out how to get it back working.. as it ended up bricking with continuous looping and even factory resetting/clearing data off didn't work. I had to flash the stock rom for it to work again)
Interesting. My friends all have the International version which is G925F. Yours is Sprint ? Or some other cell phone provider ?
If your model goes haywire with simple custom rom installations and other apps than I wouldn't risk installing XPosed BUT if you do then try to follow these instructions... they work for your model:
https://xtremetricks.net/install-xposed-framework-android-6-0-6-0-1-marshmallow/
My phone is Sprint and I downloaded Xposed from the Magitsk app and it worked without bricking my phone.. I wonder why it was acting up
Strange thing, I seems I HAVE to install the 'Mostly Stock ROM' BEFORE I add Renegade.. the mobile data works to not work at all without installing Mostly Stock first.. How any idea how to fix this?
Well, I tried installing Magisk and it bricked my phone once again.. I'm really confused with whats going on. I have a backup of the stock ROM from SamMobile. What I want to do now is completely clear off ALL data from all of the roms and just start over, is that even possible? Also, if I delete the system files, do I HAVE to install the Stock ROM first, or can I just add the custom ROM and it will add the OS?
Well normally for rooted phones, you only add the custom ROM and it will automatically add the OS. I have no idea why you having so much problem with it. Did you unluck the bootloader ??
Yeah.. (I think), I made sure OEM Unlock is enabled and USB debugging is on.. Not sure what could be causing such problems with my phone.. I honestly wish I knew
What method did you use to root your phone and unlock the bootloader ?
I used the systemless method (installed TWRP, then installed the latest SuperSU which used the systemless method by itself) and I think I did.. there was an option where I had to enable (it was called OEM Unlocking, it was preventing me from flashing)
And I forgot to ask another question.. should I (and if such thing is possible) wipe the system/ folder and then install the custom ROM onto my phone without having to add the stock one at all?
What I would do if I were in your shoes is I would unroot and re-lock your bootloader again... see this article for unrooting: http://howunroot.com/unroot-supersu/samsung/galaxy+s6+edge+sm-g925p/5.0/ Now... once you unroot your phone... I don't think re-locking your bootloader will have any effect... but you can try to relock your bootloader and bring it to the original state meaning factory... once there just follow these instructions step by step: http://www.ibtimes.co.uk/skipsoft-toolkit-galaxy-s6-edge-root-unlock-restore-flash-stock-firmware-drivers-more-1517879 Once you root it and unlock your bootloader again, and after your install TWRP, go into TWPR, wipe dalvik cache, wipe system, wipe everything ... and then instlal the custom ROM that I gave you in the link, and it should be working find without problems. Try that and get back to me and update me... if you have any questions then just post it here and I will help you as much as i can.
I don't think I unlocked the bootloader because I looked up the instructions to how to unlock the bootloader and I didn't do that.. all I did was enable OEM unlock, is that the same thing as unlocking the bootloader? If not, how do I unlock the bootloader?