Related
I don't know what happened. Or why it won't work.
When Safestrap was originally finished, I installed Hyperdrive without a problem. An update came, I downloaded and installed. It made it so I couldn't use HotSpot anymore. So, I figured it was the Rom, and I installed Jellybean Rom. I didn't like it. I tried to install the original Hyperdrive I had, and once its installed and reboots, the lights come on for one second and shut off. Downloaded the newest Hyperdrive, same issue.
The instructions say wait for 10 minutes. I did, and longer. (Range usually 20-40 minutes)
Last night I wanted to try again, (downloaded newest hyperdrive. I have sloooooow internet. Took 5 hours to finish). So, I tried installing today following the instructions, same issue. It installs and says everything is fine, reboot, safestrap pops up, loads normally through that, and the lights are on after like it starts with Stock, lights shut off, phone stops working.
When this happens, the phone does not respond to anything. Power does nothing. I waited 45 minutes the 3rd time trying to reboot after install. The phone will not turn on, respond, or anything unless I pop the battery out and put it back in. I can get back into Safestrap that way.
I really want to use Hyperdrive, but it just won't reboot for my phone.
I do have the Verizon i545 version, ME7, Safestrap, Rooted, and newest Hyperdrive Rom. Used the Safestrap Kernel, but the phone locks up.
I've tried default settings, different Rom settings, (2gb and 3gb), removing almost everything from install, adding what I want, adding what I like, etc. No combination of settings will let me phone boot into Hyperdrive.
Any thoughts?
Are you completely removing then re-creating the slot when trying all these flashes?
Are you flashing the ME7 kernel module.zip ?
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Have you tried to re-download the module? Preferably on the computer then transfer to your ExtSDCard with the ROM.
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
While you were trying to install did you notice if zip signature was checked if so uncheck when you install and uncheck when you install module other than that don't know what else to say. When i first started i found that to be my problem.
The zip signatures were not checked. : /
Sent from my SCH-I545 using xda app-developers app
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Excessumcarcer said:
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Click to expand...
Click to collapse
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
!Led*Eyes! said:
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
Click to expand...
Click to collapse
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
!Led*Eyes! said:
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
Click to expand...
Click to collapse
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Excessumcarcer said:
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Click to expand...
Click to collapse
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
!Led*Eyes! said:
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
Click to expand...
Click to collapse
Well...nothing has worked.
Update for everyone, I was using the older SS, 3.60.
I killed everything, put the original Verizon ME7 Rom on the phone, re-rooted, put 3.62 SS on, (Done like it), installed the HDrls10, Installed the module, (both successful), restarted, exact same thing. Right after Safestrap Enabled pops up, the phone goes dark and the battery needs to be removed and put back in for it to turn on again.
So, I tried something crazy and for whatever reason it worked as far as HD is concerned...but...I went outside of the instructions.
I have the HD rls9 Final. I installed it through SS, used the modded Kernel, (non SS), and restarted. It popped right up in about 45 seconds. (Wasnt working before I reset everything and started over)
I tried HD rls10 Final that way, and nothing.
I will be redownloading it tonight to make sure it isn't the download. (I have slow internet, itll take all night likely.) : /
If anyone is looking to actually uninstall SS (which you need to do to roll back a version) you need to use the commands hashcode has provided. Using Terminal Emulator on the stock side will accomplish that. Read up on hashcode's SS OP.
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Excessumcarcer said:
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Click to expand...
Click to collapse
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
lazer9 said:
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
Click to expand...
Click to collapse
I just double checked the MD5. It matches the download. How frustrating. Double checked the build, double checked the MD5, double checked install procedure, etc. It flat doesn't work on my phone, and there is no logical reason to it. I tried from a fresh build twice now, doing the rooting and SS install from stock everything.
It locks up right after SS, still.
Electronics hate me, it has been determined before. This is just further proof.
: /
So, I've done pretty much everything feasible. Guess Ill have to stick with an older HD or different rom. : (
Also, hotspot doesn't work HD 9 for me, (nor Jellybeans). I installed the module when I did the rom, but there is no hotspot for one. And two, when I download and use FoxFi, which I paid for to use on the Stock Rom before SS, it will try to turn it on and then it freezes and crashes.
All I want is a non-Verizon Rom with working Hotspot!!!! AHHHHH!!!! Looks like that aint happening.
Well played Verizon...well played. Perahps I should get an international phone and go to another company. Expensive, but tempting.
So, the final verdict for those following -
Hyperdrive 10 - Does not work on my i545 no matter what I tried.
Hyperdrive 9 - Works but the hotspot is glitched and froze no matter what I tried.
Jellybean - Works the same as HD 9
Synergy - Works. Everything on it works, hotspot, install, etc.
Not sure why the others did not work. But, for whatever reason Synergy works flawlessly for my i545. Installed and downloaded the same ways as the others, yet it worked.
: /
I was planning on trying a few others first, but Synergy claims to block Samsung from logging information from my phone. I realize this doesn't stop every company from doing it, but its the thought that counts. lol. So, Im trying this Rom out now. It's no hyperdrive, but it works.
After a BUNCH of tries I finally got it to work!!
I have a Verizon i545 with ME7. I basically started as if I'd never installed HD 9.1 in the first place.
Here's what I did.
1. Double check that your device is rooted. I used Root Checker Basic. I actually re-rooted my device just to be sure (I venture to guess it might have been unnecessary) and it worked.
2. I used a 4GB SD formatted to ex-fat and put the HD RLS10 AND the ME7 modules .zip file on it (Both on the SD)
3. I then booted into recovery.
4. Make a new ROM slot.
5. Name it whatever you like.
6. When you go to flash HD, hit the add zip button and select the ME7 modules.zip
7. When HD gets done flashing UNCHECK the "Reboot" box up top and then hit the reboot tab at the bottom right.
8. It will automatically flash the ME7 modules next. When it says 'Successful', then reboot.
9. Give it a few seconds and hopefully it will work for you as well. Good luck.
Latest installable version for Me7?
What is the latest installable version of HD for verizon locked Me7 bootloader, i currently have rls10.0 installed and ive tried 10.1, 10.2, and now 12 and none of them boot up.
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
r1k1v1 said:
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
Click to expand...
Click to collapse
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
kunal1540 said:
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmm, I don´t remember that the BlackBox 2.0.2 had any Framework...thats why I did a manual installation. But I will try the new version 2.1. Hopefully the problems may have been solved.
boomboomer said:
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Interesting. So I have to apply mods one by one? Or can I add multiple mods because corruption has already been solved?
On a side note, when I boot the phone the red exclamation mark that used to appear has disappeared. Does that means that I somewhat reseted the flash counter to 0?
My partner's S III recently developed a problem using the standard Samsung 4.3 OS, it kept halting in the the middle of an application and later started continuously rebooting. As the phone was as far as I was aware, out of warranty and someone suggested there could be a s/w issue, I decided to root the phone and install a custom 4.4.2 ROM (I initially went for the one of the cyanogenmod 4.4.2 ROMs), to see whether that would resolve the problem. Initially, the ROMs I tried all generated error messages and failed to install,until I tried the Revolutioniary S5 V2 ROM, which installed perfectly.
However, it states that iti is a 4.3, rather than 4.4.2 ROM. I ran the ROM for 5 days without any major issues, so decided to try the V3 ROM, as ir was stated that this was 4.4.2 in a number of articles.. Again the ROM installed really quickly and without a hitch. However, again the ROM said it was 4.3, and as soon as I tried to install applications (well it was the third install, Skype if I remember), and the phone turned itself off. Then it started continuously rebooting, which is what was happening before the V2 ROM was installed. managewd to stop this by removing and then putting back the battery, and managed to get the V2 ROM installed again. Ther are three questions:
1) Does anyone have any idea what the initial problem might have been?
2) Why did the V3 ROM actually cause the problem to reoccur?
3) Is there a genuine 4.4.2 release of the Revolutionary S5 ROM (which I am genuinely impressed by and happy with), and will it work with my phone? (specific model i9300)?
[email protected] said:
My partner's S III recently developed a problem using the standard Samsung 4.3 OS, it kept halting in the the middle of an application and later started continuously rebooting. As the phone was as far as I was aware, out of warranty and someone suggested there could be a s/w issue, I decided to root the phone and install a custom 4.4.2 ROM (I initially went for the one of the cyanogenmod 4.4.2 ROMs), to see whether that would resolve the problem. Initially, the ROMs I tried all generated error messages and failed to install,until I tried the Revolutioniary S5 V2 ROM, which installed perfectly.
However, it states that iti is a 4.3, rather than 4.4.2 ROM. I ran the ROM for 5 days without any major issues, so decided to try the V3 ROM, as ir was stated that this was 4.4.2 in a number of articles.. Again the ROM installed really quickly and without a hitch. However, again the ROM said it was 4.3, and as soon as I tried to install applications (well it was the third install, Skype if I remember), and the phone turned itself off. Then it started continuously rebooting, which is what was happening before the V2 ROM was installed. managewd to stop this by removing and then putting back the battery, and managed to get the V2 ROM installed again. Ther are three questions:
1) Does anyone have any idea what the initial problem might have been?
2) Why did the V3 ROM actually cause the problem to reoccur?
3) Is there a genuine 4.4.2 release of the Revolutionary S5 ROM (which I am genuinely impressed by and happy with), and will it work with my phone? (specific model i9300)?
Click to expand...
Click to collapse
1) Not doing a full wipe/ formating system cache data etc or not using the latest recovery or combination of both
2) Not doing a full wipe/ formating system cache data etc or not using the latest recovery or combination of both
3) No
Also I find if switching between 4.3 roms and 4.4 roms (which I do alot) it is good idea to backup internal sd card and to format it (not all the time just if phone becomes really slow or has random reboots)
So I downloaded safestrrap after realizing my baseband won't let me run CM13. I have tried multiple ROMS and NONE of them seem to boot after installation. Everything seems fine during install, but once it reboots, i Get the Saestrap Enabled screen, then blank. My phone happens to be FUNC5 (I think the most updated baseband from vzw) if that makes ANY difference.
Id like to run something other then stock, but it only seams to boot into the stock ROM fine. Very aggrivating. Tried 4 different ROM's all the same.
I upgraded to Safestrap 3.75 and now when i boot into a rom slot, i just get a blue slow flashing LED...
I tried Echoe and have been stuck on boot screen for 15 mins
Get any where?
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?