[Q] How To Add Root How A Custom Rom? - Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble

Hello Everyone,
I'm ik4evr. (Making the SM-T520 rom) =)
Anyway, i'm trying to add root to my custom rom. However, every time I do it using the kitchen, and flash the rom and try to open SuperSU it says binary not installed. I tried manually putting the root files in my room too. Can anyone out there help me with this. Thanks!

ik4evr said:
Hello Everyone,
I'm ik4evr. (Making the SM-T520 rom) =)
Anyway, i'm trying to add root to my custom rom. However, every time I do it using the kitchen, and flash the rom and try to open SuperSU it says binary not installed. I tried manually putting the root files in my room too. Can anyone out there help me with this. Thanks!
Click to expand...
Click to collapse
welcome to my world...it took me about a week of research before i found anything that helped & dont even remember where i read it at now. Long story short....there seems to be an issue with the binaries that the kitchen uses so in the end i finally just copied the su/busybox/init.d files from cleanrom for the T320 & havent had a problem since

THEDEVIOUS1 said:
welcome to my world...it took me about a week of research before i found anything that helped & dont even remember where i read it at now. Long story short....there seems to be an issue with the binaries that the kitchen uses so in the end i finally just copied the su/busybox/init.d files from cleanrom for the T320 & havent had a problem since
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately, that didn't work still =(
Anything else?

ik4evr said:
Thanks for the reply. Unfortunately, that didn't work still =(
Anything else?
Click to expand...
Click to collapse
If that didnt work then it might be your updater-script...once again just copy the one from a known working deice with an exynos cpu & 4.4.2 (N9000 MAYBE?) then u should be ok. Also...did u swap the daemonsu file in xbin as well? Another thing...delete the su located in "bin" & make sure its in "xbin". The last thing i can think of...did u unpack the boot.img & change the value in the dfault.prop to make it non-secure?
edit: I was just thinking...i noticed u said "supersu" but every guide ive seen added "superuser" instead so swap that too. U should be able to include either but mine didnt work either until i switched them although it could have been coincidence since i also made all of the rest of the alterations around the same time...if u notice in my thread i told users to go download supersu AFTER they flash just to be safe but now that i have it working i'll probably try changing apps again for the next version to eliminate a step

where do I dl twrp for tab pro 10.1 wifi?
I only see 10.1 tab pro lte ...not wifi?
Thanks

Related

[Q] Help with sprint lovers rom

Hi All, admitted newbie here. Sorry if this is misplaced, but I've searched and can't find the answer.
I've rooted my evo, dowloaded the all in one sprint lovers rom and installed it using rom manager. however, after install, i can find no signs of it being SL - no wifi tether app, no % battery indicator, no power control from pull-down window. from all outward appearances it is vanilla sense/froyo.
how do i verify exactly what installed? do i have to somehow seperately install/enable the SL features mentioned above?
help is appreciated..... thanks.
To check what you have just go to settings then at the bottom about phone, then software and look around it should say what rom you have
Sent from my PC36100 using XDA Premium App
you don't flash it from rom manager.
name it to pc36img.zip EXACLTY and make sure it is on the root of the sdcard. save anything worth saving. then power off phone. then hold volume down and power, and you should see a white screen w/ skating droids. it'll ask if you want to updat.e hit folume up for yes. once it is done, it'll ask you if you want to reboot. also hit volume up for yes.
i'd reccomend you also try some roms like myns, mik's, koni's, and maybe some aosp cm7 action as well.
welcome to the root world.
any other quesitons, don't be afraid to ask.
peakay said:
Hi All, admitted newbie here. Sorry if this is misplaced, but I've searched and can't find the answer.
I've rooted my evo, dowloaded the all in one sprint lovers rom and installed it using rom manager. however, after install, i can find no signs of it being SL - no wifi tether app, no % battery indicator, no power control from pull-down window. from all outward appearances it is vanilla sense/froyo.
how do i verify exactly what installed? do i have to somehow seperately install/enable the SL features mentioned above?
help is appreciated..... thanks.
Click to expand...
Click to collapse
Download Amon 2.3 for recovery you can also use this later to flash things and backups. Now place the sprint lovers rom in the root of sd card turn phone off.
Hold volume button down and hit the power button while holding down to get into bootloader it will then boot the pc36img.
Then when you get that all done remove it from your sd card and copy amon 2.3 pc36img over do the same thing. Then remove it from the sd card and bingo your set man. Easy as pie. Any more directions PM me.
First of all, thanks to those who have posted already - very much appreciated.
I think i found the problem (but not the solution yet) and it is very weird. After having problems getting sprint lovers loaded, I went ahead and tried cm7 using the version downloaded from rom manager. It installed and I've been using it a couple days. very nice.
However, I still wanted sprint lovers so I tried it again today. Downloaded the all in one fresh again to my mac so i was sure of the right file, moved it to my sd card root, verified it is there in finder, then did an install from sdcard using rom manager. it goes through the whole process and what do I get? CM7 again?!?
So... I think what was happening was that installing from sdcard in rom manager is resulting in the already existing rom being reinstalled. weird.
Further to this problem, if I manually boot into recovery and try to install from sdcard, I am able to see all the usual folders, etc. on the sdcard, but not the zip rom file. I can see the rom file when the phone is mounted to my mac and I can also see it when I use a file manager on the phone. However, in recovery, no dice. This is why I initially used rom manager to install as I wasn't seeing rom files when browsing in recovery.
Does anyone have a solution? I am totally confused as to why this is happening and its caused hours of confusion already. Is it a Mac file thing?? I kept installing Sprint Lovers and finding that there were no new features (about 3 times), which is why I originally made this posting.
Thanks in advance!
peakay said:
First of all, thanks to those who have posted already - very much appreciated.
I think i found the problem (but not the solution yet) and it is very weird. After having problems getting sprint lovers loaded, I went ahead and tried cm7 using the version downloaded from rom manager. It installed and I've been using it a couple days. very nice.
However, I still wanted sprint lovers so I tried it again today. Downloaded the all in one fresh again to my mac so i was sure of the right file, moved it to my sd card root, verified it is there in finder, then did an install from sdcard using rom manager. it goes through the whole process and what do I get? CM7 again?!?
So... I think what was happening was that installing from sdcard in rom manager is resulting in the already existing rom being reinstalled. weird.
Further to this problem, if I manually boot into recovery and try to install from sdcard, I am able to see all the usual folders, etc. on the sdcard, but not the zip rom file. I can see the rom file when the phone is mounted to my mac and I can also see it when I use a file manager on the phone. However, in recovery, no dice. This is why I initially used rom manager to install as I wasn't seeing rom files when browsing in recovery.
Does anyone have a solution? I am totally confused as to why this is happening and its caused hours of confusion already. Is it a Mac file thing?? I kept installing Sprint Lovers and finding that there were no new features (about 3 times), which is why I originally made this posting.
Thanks in advance!
Click to expand...
Click to collapse
YOU CAN NOT USE ROM MANAGER TO INSTALL THE ALL IN ONE VERSION OF SPRINT LOVERS!!!!!!!!!!!!!!!!!!
The all in one version of sprint lovers must be installed from the boot loader not recovery. You copy sprint lovers PC36IMG.zip to the root of the sd card and enter the boot loader, then follow the instructions on the screen when it asks if you want to update.
If you insist on using ROM manager then you have to install the stand alone version of Sprint Lovers. This will require you to also install the updated radios unless you have already updated the radios.
PC36IMG.zip use bootloader, any other .zip is installed using recovery and rom manager uses recovery.
peakay said:
First of all, thanks to those who have posted already - very much appreciated.
I think i found the problem (but not the solution yet) and it is very weird. After having problems getting sprint lovers loaded, I went ahead and tried cm7 using the version downloaded from rom manager. It installed and I've been using it a couple days. very nice.
However, I still wanted sprint lovers so I tried it again today. Downloaded the all in one fresh again to my mac so i was sure of the right file, moved it to my sd card root, verified it is there in finder, then did an install from sdcard using rom manager. it goes through the whole process and what do I get? CM7 again?!?
So... I think what was happening was that installing from sdcard in rom manager is resulting in the already existing rom being reinstalled. weird.
Further to this problem, if I manually boot into recovery and try to install from sdcard, I am able to see all the usual folders, etc. on the sdcard, but not the zip rom file. I can see the rom file when the phone is mounted to my mac and I can also see it when I use a file manager on the phone. However, in recovery, no dice. This is why I initially used rom manager to install as I wasn't seeing rom files when browsing in recovery.
Does anyone have a solution? I am totally confused as to why this is happening and its caused hours of confusion already. Is it a Mac file thing?? I kept installing Sprint Lovers and finding that there were no new features (about 3 times), which is why I originally made this posting.
Thanks in advance!
Click to expand...
Click to collapse
dude wtf.
srry but i told you how in my first post ^^^^^
sprintlovers is a ruu style flash, which is mostly unused. rom manager uses update.zips.
if you're going to ask a question, plz dont ignore a perfectly good answer.
i get where you might have gotten confused, because the rest of the people told you how to flash an update.zip rom, which won't work with sprintlovers. but you didn't even try mine, even though i gave you perfectly good instructions.
if you need help, dont be afraid to ask.
but don't ignore the answer.
dkdude36 said:
if you need help, dont be afraid to ask.
but don't ignore the answer.
Click to expand...
Click to collapse
Sorry dk, no disrespect, I just didn't understand what you were telling me exactly. Please keep in mind there are a lot of moving parts to this with the roms, kernals, radio updates, etc. and whats obvious to you may not be to someone who just started. I actually did follow your directions yesterday once it sank in and Cruise replied to make it crystal clear and all is well now. SL is installed and working perfectly.
I left thanks to you both...thank you!
One question: Is there a rom like sprint lovers, but is stripped down and crap free? I don't like having to go back and delete everything and not know what i might step on that affects the phone later. I really liked cm7 a lot for the couple days I used it, but with gps being flaky (i know it is fixable) and some random lags and weirdness I got on certain apps, I am not sure if it is solid enough. I use this phone daily as my main business phone for all incoming and outgoing calls, so it has to be solid.
Thanks again.
I suggest that you download and install the Titanium Backup app. Whatever rom you decide to flash, you can use the aforementioned app to "freeze" an app you don't want. If you later find that you do want it or need it, you can always "defrost" it with Titanium Backup. As for what is safe to remove, see the following list:
browser.apk (if you use a different browser)
mail.apk (if you use gmail)
amazonmp3.apk
appsharing.apk
calculator.apk
FMRadioWidget.apk
NewsReaderWidget.apk
StockWidget.apk
TwitterWidget.apk
DCSStock.apk
Flashlight.apk
Flickr.apk
Geniewidget.apk
GoogleQuickSearchBox.apk
htcbookmarkwidget.apk
HtcCalculatorWidget.apk
HtcCarPanel.apk
HtcFootprints.apk
HtcFootprintsWidget.apk
htcmailwidgets.apk
HTCMobileGuide.apk
htcsmswidgets.apk
HtcPhotoWidget.apk
HtcProfilesWidget.apk
HtcRingtoneTrimmer.apk
HtcRingtoneWidget.apk
HTCSetupWizard.apk
HtcSoundRecorder.apk
HtcStreamPlayer.apk
HtcTwitter.apk
HTMLViewer.apk
IQRD.apk
MagicSmokeWallpapers.apk
Mail.apk
Maps.apk (reinstall from market)
Mode10Wallpapers.apk NewsReader.apk
PicoTts.apk (needed for navigation)
QuickLookup.apk
Quickoffice.apk
Rss.apk
SocialNetworkProvider.apk
Sprint_NASCAR.apk
Sprint_Navigation.apk
Sprint_NFL.apk
Sprint_Promotion.apk
Sprint_Qik.apk
Sprint_TV.apk
Sprint_VVM.apk (if you use google voice)
SprintTVWidget.apk
Stock.apk
Street.apk
teeter.apk
TelephonyProvider.apk
TtsService.apk
VisualizationWallpapers.apk
VoiceDialer.apk
VoiceSearch.apk
WidgetDownloadManager.apk
WifiRouter.apk
posting & replying via the XDA Premium app.
Thanks Doug - very helpful.
However, am still interested if there is a clean, crap-free rom where you do not have to go through and delete so many items. Anyone know of one?
That will depend on your definition of "crap-free". If crap free means the removal of all Sprint apps then yes, most custom sense roms have them removed and stored in a special folder on your SD card in case you decide to install one or more of them later. Some people see the Sense overlay as crap. If you do, too, then there are numerous AOSP roms available. Salvage-Mod and CyanogenMod are just two of the more popular ones. There is even a sense-removal script floating around. Keep in mind, however, that the devs initially create their roms to suit their own tastes. They then alter their work to satisfy fans of their work as best as they can. Furthermore, what you consider crap may be a necessity to the next person. Know what I mean? Anyway, I hope I was helpful. Take care and enjoy the rest of your day....
posting & replying via the XDA Premium app.
peakay said:
Sorry dk, no disrespect, I just didn't understand what you were telling me exactly. Please keep in mind there are a lot of moving parts to this with the roms, kernals, radio updates, etc. and whats obvious to you may not be to someone who just started. I actually did follow your directions yesterday once it sank in and Cruise replied to make it crystal clear and all is well now. SL is installed and working perfectly.
I left thanks to you both...thank you!
One question: Is there a rom like sprint lovers, but is stripped down and crap free? I don't like having to go back and delete everything and not know what i might step on that affects the phone later. I really liked cm7 a lot for the couple days I used it, but with gps being flaky (i know it is fixable) and some random lags and weirdness I got on certain apps, I am not sure if it is solid enough. I use this phone daily as my main business phone for all incoming and outgoing calls, so it has to be solid.
Thanks again.
Click to expand...
Click to collapse
hey man. sorry for the disrespectful/pushy post. i had just come back from an undeserved loss in volleyball, and i sorta was hurrying as well. no disrespect meant. agian, welcome to the root world...
Hi everyone , i have a little problem when i try to flash the all in one sprint lovers rom PC36IMG.ZIP bootloader scans for it and (no image or bad image or wrong image) something like that , i rooted my phone with unrevocked 3.3 . Thank you guys
diegol76 said:
Hi everyone , i have a little problem when i try to flash the all in one sprint lovers rom PC36IMG.ZIP bootloader scans for it and (no image or bad image or wrong image) something like that , i rooted my phone with unrevocked 3.3 . Thank you guys
Click to expand...
Click to collapse
Are you certain the file isn't named PC36IMG.zip.zip? Remove the .zip portion and try again, just in case. Also, are you certain the file is suppose to be flashed from the bootloader and not from within recovery? If you are and removing the .zip from the filename didn't work, redownload the file.
posting & replying via the XDA Premium app.
Yes i.m sure it is named PC36IMG.ZIP and when bootloader serch for it (wrong image) and i did download few times but with the same results , what else could it be? just in case i'm going to download it one more time
Again ( no image or wrong image ) WTF is wrong? now i noticed that when bootloader is searching or loading the image first says ( loading PC36DIAG.ZIP ) and then ( no image or wrong image ) and after that loads the PC36IMG.ZIP but again ( no image or wrong image )
yea dude it's named wrong. windows hides file extensions sometimes so it may be named pc36img.zip.zip but you just don't know it. try removing .zip then try again.
dkdude36 said:
yea dude it's named wrong. windows hides file extensions sometimes so it may be named pc36img.zip.zip but you just don't know it. try removing .zip then try again.
Click to expand...
Click to collapse
Good call. That's why I just tell people to name it PC36IMG, since I already know its a .zip extension.
diegol76 said:
Hi everyone , i have a little problem when i try to flash the all in one sprint lovers rom PC36IMG.ZIP bootloader scans for it and (no image or bad image or wrong image) something like that , i rooted my phone with unrevocked 3.3 . Thank you guys
Click to expand...
Click to collapse
I am having the same issue.....keeps saying no image. I've made sure the file name is correct (only 1 extension) and it's sitting in the root of my sdcard. Any other ideas? Is the file case sensitive? Windows files usually aren't but I don't know what the bootloader is written in so not too sure. Please help as I've found the process up to this point to be pretty painless but didn't want something this small to hold me up.
Thanks a bunch!
Edit: I've also downloaded and tested the .zip several times (using WinRAR) and it seems ok. the file size is 225,430 KB.
robertfah said:
I am having the same issue.....keeps saying no image. I've made sure the file name is correct (only 1 extension) and it's sitting in the root of my sdcard. Any other ideas? Is the file case sensitive? Windows files usually aren't but I don't know what the bootloader is written in so not too sure. Please help as I've found the process up to this point to be pretty painless but didn't want something this small to hold me up.
Thanks a bunch!
Edit: I've also downloaded and tested the .zip several times (using WinRAR) and it seems ok. the file size is 225,430 KB.
Click to expand...
Click to collapse
try just removing the extenstion altogether then. just pc36img (no period either). that might work.

[Q] [MetroPCS MMS Fix]

I have used many different roms with my metro-flashed evo, and gotten the mms scripts to work. however, i'm trying to use this rom:
http://forum.xda-developers.com/showthread.php?t=1586396
based on SOS/sense 1.0 (i believe..) and I can't figure out why mms isnt working.
i've swapped apns (with the metropcs 3128..) and flashed the 4.67 script, but nothing. any help would be awesome. thanks.
(I would have posted this in Bloody's thread, but I'm a noob/not enough posts)
johnny.dalvik-cache said:
I have used many different roms with my metro-flashed evo, and gotten the mms scripts to work. however, i'm trying to use this rom:
http://forum.xda-developers.com/showthread.php?t=1586396
based on SOS/sense 1.0 (i believe..) and I can't figure out why mms isnt working.
i've swapped apns (with the metropcs 3128..) and flashed the 4.67 script, but nothing. any help would be awesome. thanks.
(I would have posted this in Bloody's thread, but I'm a noob/not enough posts)
Click to expand...
Click to collapse
I couldn't get the script to execute on SOS fo some reason....this, however, did the trick for me:
In root explorer look to see if the script file (metropcs.sh)is in the right place in the internal memory...if not place it there then execute.
Can u guide me to that file from root? Sorry, i have no idea where to go. And how do I execute it? Do i just long press and select "execute" ? I had this same issue with SOS and I don't think I ever got it working on a sense 1.∅ rom
atljatl said:
Can u guide me to that file from root? Sorry, i have no idea where to go. And how do I execute it? Do i just long press and select "execute" ? I had this same issue with SOS and I don't think I ever got it working on a sense 1.∅ rom
Click to expand...
Click to collapse
Sadly, I cannot. Which is why I asked bloodyk. where it was in his rom thread....thinking it disappeared. I cannot locate it in my root or sd.
I know I pulled it from the zip and placed it in root and then executed it within.
To execute, d/l script manager freê from store. Open script manager, locate sh file, ensure su is selected in top row, and touch run (also top row). That should do it.
Thanks Mex. Saw your post just now on bk's thread. If you find anything please let me know. I'm running aosp cuz I really need mms for work. Would love to try the new sos
atljatl....
Did you try doing what JD did to get it going? I am going to give it a try...
JD2589 said:
...And for those of you having trouble getting MMS working on a 4.67 sense rom, Just flashed Bloodys 4.67 MMS script through Amon RA Recovery, For some reason its not flashing in ClockWork Recovery. Here is a link to that specific script only for sense 4.67 roms (successfully tested on Swagstr latest SOS X rom):
http://www.mediafire.com/download.php?5gs5wtgn2jgauj7
JD
Click to expand...
Click to collapse
As for executing/finding bloody's script:
Bloodykiller86 said:
well in my latest scripts its called mpcs.sh and also its not in the root of the phone but in the zip. unzip it and youll see its not inside the folders
Click to expand...
Click to collapse
mexigga said:
atljatl....
Did you try doing what JD did to get it going?...
Click to expand...
Click to collapse
Don't know how I missed that. I'll give it a go... ugh.... Ive been running decks 1.3d for 3 days straight (sort of an eternity....) have everything like i want it! Smh...have u confirmed this fix works?
atljatl said:
Don't know how I missed that. I'll give it a go... ugh.... Ive been running decks 1.3d for 3 days straight (sort of an eternity....) have everything like i want it! Smh...have u confirmed this fix works?
Click to expand...
Click to collapse
JD has...I will try later.
(see you hit JD up also...great)
EDIT: confirmed working.

How to flash d2spr Lollipop Roms on the d2lterefreshspr (SPH-L710T Tri-Band Model)

1st let me just say I'm not a developer at all just someone who enjoys custom roms as much as everyone else here! I'm not very good at explaining things so please try to bear with me and try to understand this the best you can! If any real developers read this please help us by adding support for our device and if any developers can explain this better please do so! For anyone with the d2lterefreshspr (SPH-L710T Tri-Band) wanting to flash almost any Lollipop Roms made for the d2spr you can flash them! You might 1st have to unzip the rom and go to the updater-script and delete the 1st part where it checks the recoveries build to see if your device is the d2spr or the d2lte and so on. Then repack the rom back into a zip file the flash it in recovery as you normally would. Then once the Rom boots you won't have a baseband or service or anything but I will tell you why and how to fix this. The d2spr's modem-image file are labeled different from our modem! At the bottom of this I will show you the list of each modems links so you can see which 1s are different and what you have to delete and resymlink to get the Rom to reconize your baseband and get your service working! But using a file manager with root access navigate to the files in "/system/etc/firmware/ " and delete the wrongly symlinked modem-images! Once you have done that navigate to "/firmware-mdm/images/" folder and start symlinking the correct files to "/system/etc/firmware/" folder. After this you might want to modify the buid.prop and change all parts that say d2spr to d2lterefreshspr but only if you want. Once you have done this reboot to recovery and flash the Lte apn fix zip then reboot. Now everything should work with service and everything! I have tried this on the latest SlimLP 5.1.1. Beta and A..I.C.P. Lollipop and a few other Lollipop Roms for the d2spr. If you would like to download some of the Roms I have modified the updater-scripts so they will flash on our device and the APN zip I flash with a flashable build.prop I have already modified just send me a message and I will send you a link to my drive account. I'm trying to create a zip we can flash in recovery that will delete the wrong symilinked files and symlink the correct files to help save us the trouble of this process and for people that don't know how to create a symlink file! But as I stated I'm not a developer so I might be able to but if any developers that could help us by creating 1 for us please please feel free to do so and let us know! But take a look at the 2 lists of symlinked files and delete the necessary files and create the new symlinks that our device needs! If the files show the correct symlinks on 1st boot but you still don't have service click on the symlinks and view its details and you will see it'ssymlinked to the wrong files. Just delete all symlinks and create the correct new 1s.
Example of the d2spr modem symlinked images are:
symlink("/firmware-mdm/image/dsps.b00", "/system/etc/firmware/dsps.b00");
symlink("/firmware-mdm/image/dsps.b01", "/system/etc/firmware/dsps.b01");
symlink("/firmware-mdm/image/dsps.b02", "/system/etc/firmware/dsps.b02");
symlink("/firmware-mdm/image/dsps.b03", "/system/etc/firmware/dsps.b03");
symlink("/firmware-mdm/image/dsps.b04", "/system/etc/firmware/dsps.b04");
symlink("/firmware-mdm/image/dsps.b05", "/system/etc/firmware/dsps.b05");
symlink("/firmware-mdm/image/dsps.mdt", "/system/etc/firmware/dsps.mdt");
symlink("/firmware-mdm/image/modem.b00", "/system/etc/firmware/modem.b00");
symlink("/firmware-mdm/image/modem.b01", "/system/etc/firmware/modem.b01");
symlink("/firmware-mdm/image/modem.b02", "/system/etc/firmware/modem.b02");
symlink("/firmware-mdm/image/modem.b03", "/system/etc/firmware/modem.b03");
symlink("/firmware-mdm/image/modem.b04", "/system/etc/firmware/modem.b04");
symlink("/firmware-mdm/image/modem.b05", "/system/etc/firmware/modem.b05");
symlink("/firmware-mdm/image/modem.b06", "/system/etc/firmware/modem.b06");
symlink("/firmware-mdm/image/modem.b07", "/system/etc/firmware/modem.b07");
symlink("/firmware-mdm/image/modem.mdt", "/system/etc/firmware/modem.mdt");
symlink("/firmware-mdm/image/modem_f2.b00", "/system/etc/firmware/modem_fw.b00");
symlink("/firmware-mdm/image/modem_f2.b01", "/system/etc/firmware/modem_fw.b01");
symlink("/firmware-mdm/image/modem_f2.b02", "/system/etc/firmware/modem_fw.b02");
symlink("/firmware-mdm/image/modem_f2.b03", "/system/etc/firmware/modem_fw.b03");
symlink("/firmware-mdm/image/modem_f2.b04", "/system/etc/firmware/modem_fw.b04");
symlink("/firmware-mdm/image/modem_f2.b05", "/system/etc/firmware/modem_fw.b05");
symlink("/firmware-mdm/image/modem_f2.b06", "/system/etc/firmware/modem_fw.b06");
symlink("/firmware-mdm/image/modem_f2.b07", "/system/etc/firmware/modem_fw.b07");
symlink("/firmware-mdm/image/modem_f2.b08", "/system/etc/firmware/modem_fw.b08");
symlink("/firmware-mdm/image/modem_f2.b09", "/system/etc/firmware/modem_fw.b09");
symlink("/firmware-mdm/image/modem_f2.b10", "/system/etc/firmware/modem_fw.b10");
symlink("/firmware-mdm/image/modem_f2.b13", "/system/etc/firmware/modem_fw.b13");
symlink("/firmware-mdm/image/modem_f2.b14", "/system/etc/firmware/modem_fw.b14");
symlink("/firmware-mdm/image/modem_f2.b21", "/system/etc/firmware/modem_fw.b21");
symlink("/firmware-mdm/image/modem_f2.b22", "/system/etc/firmware/modem_fw.b22");
symlink("/firmware-mdm/image/modem_f2.b23", "/system/etc/firmware/modem_fw.b23");
symlink("/firmware-mdm/image/modem_f2.b25", "/system/etc/firmware/modem_fw.b25");
symlink("/firmware-mdm/image/modem_f2.b26", "/system/etc/firmware/modem_fw.b26");
symlink("/firmware-mdm/image/modem_f2.b29", "/system/etc/firmware/modem_fw.b29");
symlink("/firmware-mdm/image/modem_f2.mdt", "/system/etc/firmware/modem_fw.mdt");
symlink("/firmware-mdm/image/q6.b00", "/system/etc/firmware/q6.b00");
symlink("/firmware-mdm/image/q6.b01", "/system/etc/firmware/q6.b01");
symlink("/firmware-mdm/image/q6.b03", "/system/etc/firmware/q6.b03");
symlink("/firmware-mdm/image/q6.b04", "/system/etc/firmware/q6.b04");
symlink("/firmware-mdm/image/q6.b05", "/system/etc/firmware/q6.b05");
symlink("/firmware-mdm/image/q6.b06", "/system/etc/firmware/q6.b06");
symlink("/firmware-mdm/image/q6.mdt", "/system/etc/firmware/q6.mdt");
symlink("/firmware-mdm/image/tzapps.b00", "/system/etc/firmware/tzapps.b00");
symlink("/firmware-mdm/image/tzapps.b01", "/system/etc/firmware/tzapps.b01");
symlink("/firmware-mdm/image/tzapps.b02", "/system/etc/firmware/tzapps.b02");
symlink("/firmware-mdm/image/tzapps.b03", "/system/etc/firmware/tzapps.b03");
symlink("/firmware-mdm/image/tzapps.mdt", "/system/etc/firmware/tzapps.mdt");
symlink("/firmware-mdm/image/vidc.b00", "/system/etc/firmware/vidc.b00");
symlink("/firmware-mdm/image/vidc.b01", "/system/etc/firmware/vidc.b01");
symlink("/firmware-mdm/image/vidc.b02", "/system/etc/firmware/vidc.b02");
symlink("/firmware-mdm/image/vidc.b03", "/system/etc/firmware/vidc.b03");
symlink("/firmware-mdm/image/vidc.mdt", "/system/etc/firmware/vidc.mdt");
The correct modem images you need to symlink for the d2lterefreshspr are:
symlink("/firmware-mdm/image/dsps.b00", "/system/etc/firmware/dsps.b00");
symlink("/firmware-mdm/image/dsps.b01", "/system/etc/firmware/dsps.b01");
symlink("/firmware-mdm/image/dsps.b02", "/system/etc/firmware/dsps.b02");
symlink("/firmware-mdm/image/dsps.b03", "/system/etc/firmware/dsps.b03");
symlink("/firmware-mdm/image/dsps.b04", "/system/etc/firmware/dsps.b04");
symlink("/firmware-mdm/image/dsps.b05", "/system/etc/firmware/dsps.b05");
symlink("/firmware-mdm/image/dsps.mdt", "/system/etc/firmware/dsps.mdt");
symlink("/firmware-mdm/image/modem.b00", "/system/etc/firmware/modem.b00");
symlink("/firmware-mdm/image/modem.b01", "/system/etc/firmware/modem.b01");
symlink("/firmware-mdm/image/modem.b02", "/system/etc/firmware/modem.b02");
symlink("/firmware-mdm/image/modem.b03", "/system/etc/firmware/modem.b03");
symlink("/firmware-mdm/image/modem.b04", "/system/etc/firmware/modem.b04");
symlink("/firmware-mdm/image/modem.b06", "/system/etc/firmware/modem.b06");
symlink("/firmware-mdm/image/modem.b07", "/system/etc/firmware/modem.b07");
symlink("/firmware-mdm/image/modem.b08", "/system/etc/firmware/modem.b08");
symlink("/firmware-mdm/image/modem.b09", "/system/etc/firmware/modem.b09");
symlink("/firmware-mdm/image/modem.b10", "/system/etc/firmware/modem.b10");
symlink("/firmware-mdm/image/modem.mdt", "/system/etc/firmware/modem.mdt");
symlink("/firmware-mdm/image/modem_fw.b00", "/system/etc/firmware/modem_fw.b00");
symlink("/firmware-mdm/image/modem_fw.b01", "/system/etc/firmware/modem_fw.b01");
symlink("/firmware-mdm/image/modem_fw.b02", "/system/etc/firmware/modem_fw.b02");
symlink("/firmware-mdm/image/modem_fw.b03", "/system/etc/firmware/modem_fw.b03");
symlink("/firmware-mdm/image/modem_fw.b04", "/system/etc/firmware/modem_fw.b04");
symlink("/firmware-mdm/image/modem_fw.b05", "/system/etc/firmware/modem_fw.b05");
symlink("/firmware-mdm/image/modem_fw.b09", "/system/etc/firmware/modem_fw.b09");
symlink("/firmware-mdm/image/modem_fw.b10", "/system/etc/firmware/modem_fw.b10");
symlink("/firmware-mdm/image/modem_fw.b11", "/system/etc/firmware/modem_fw.b11");
symlink("/firmware-mdm/image/modem_fw.b12", "/system/etc/firmware/modem_fw.b12");
symlink("/firmware-mdm/image/modem_fw.b13", "/system/etc/firmware/modem_fw.b13");
symlink("/firmware-mdm/image/modem_fw.b15", "/system/etc/firmware/modem_fw.b15");
symlink("/firmware-mdm/image/modem_fw.b16", "/system/etc/firmware/modem_fw.b16");
symlink("/firmware-mdm/image/modem_fw.b17", "/system/etc/firmware/modem_fw.b17");
symlink("/firmware-mdm/image/modem_fw.b18", "/system/etc/firmware/modem_fw.b18");
symlink("/firmware-mdm/image/modem_fw.b23", "/system/etc/firmware/modem_fw.b23");
symlink("/firmware-mdm/image/modem_fw.b24", "/system/etc/firmware/modem_fw.b24");
symlink("/firmware-mdm/image/modem_fw.b25", "/system/etc/firmware/modem_fw.b25");
symlink("/firmware-mdm/image/modem_fw.b27", "/system/etc/firmware/modem_fw.b27");
symlink("/firmware-mdm/image/modem_fw.b28", "/system/etc/firmware/modem_fw.b28");
symlink("/firmware-mdm/image/modem_fw.b31", "/system/etc/firmware/modem_fw.b31");
symlink("/firmware-mdm/image/modem_fw.fli", "/system/etc/firmware/modem_fw.fli");
symlink("/firmware-mdm/image/modem_fw.mdt", "/system/etc/firmware/modem_fw.mdt");
symlink("/firmware-mdm/image/q6.b00", "/system/etc/firmware/q6.b00");
symlink("/firmware-mdm/image/q6.b01", "/system/etc/firmware/q6.b01");
symlink("/firmware-mdm/image/q6.b03", "/system/etc/firmware/q6.b03");
symlink("/firmware-mdm/image/q6.b04", "/system/etc/firmware/q6.b04");
symlink("/firmware-mdm/image/q6.b05", "/system/etc/firmware/q6.b05");
symlink("/firmware-mdm/image/q6.b06", "/system/etc/firmware/q6.b06");
symlink("/firmware-mdm/image/q6.mdt", "/system/etc/firmware/q6.mdt");
symlink("/firmware-mdm/image/tima_key.b00", "/system/etc/firmware/tima_key.b00");
symlink("/firmware-mdm/image/tima_key.b01", "/system/etc/firmware/tima_key.b01");
symlink("/firmware-mdm/image/tima_key.b02", "/system/etc/firmware/tima_key.b02");
symlink("/firmware-mdm/image/tima_key.b03", "/system/etc/firmware/tima_key.b03");
symlink("/firmware-mdm/image/tima_key.mdt", "/system/etc/firmware/tima_key.mdt");
symlink("/firmware-mdm/image/tima_lkm.b00", "/system/etc/firmware/tima_lkm.b00");
symlink("/firmware-mdm/image/tima_lkm.b01", "/system/etc/firmware/tima_lkm.b01");
symlink("/firmware-mdm/image/tima_lkm.b02", "/system/etc/firmware/tima_lkm.b02");
symlink("/firmware-mdm/image/tima_lkm.b03", "/system/etc/firmware/tima_lkm.b03");
symlink("/firmware-mdm/image/tima_lkm.mdt", "/system/etc/firmware/tima_lkm.mdt");
symlink("/firmware-mdm/image/tima_pkm.b00", "/system/etc/firmware/tima_pkm.b00");
symlink("/firmware-mdm/image/tima_pkm.b01", "/system/etc/firmware/tima_pkm.b01");
symlink("/firmware-mdm/image/tima_pkm.b02", "/system/etc/firmware/tima_pkm.b02");
symlink("/firmware-mdm/image/tima_pkm.b03", "/system/etc/firmware/tima_pkm.b03");
symlink("/firmware-mdm/image/tima_pkm.mdt", "/system/etc/firmware/tima_pkm.mdt");
symlink("/firmware-mdm/image/tzapps.b00", "/system/etc/firmware/tzapps.b00");
symlink("/firmware-mdm/image/tzapps.b01", "/system/etc/firmware/tzapps.b01");
symlink("/firmware-mdm/image/tzapps.b02", "/system/etc/firmware/tzapps.b02");
symlink("/firmware-mdm/image/tzapps.b03", "/system/etc/firmware/tzapps.b03");
symlink("/firmware-mdm/image/tzapps.mdt", "/system/etc/firmware/tzapps.mdt");
symlink("/firmware-mdm/image/vidc.b00", "/system/etc/firmware/vidc.b00");
symlink("/firmware-mdm/image/vidc.b01", "/system/etc/firmware/vidc.b01");
symlink("/firmware-mdm/image/vidc.b02", "/system/etc/firmware/vidc.b02");
symlink("/firmware-mdm/image/vidc.b03", "/system/etc/firmware/vidc.b03");
symlink("/firmware-mdm/image/vidc.mdt", "/system/etc/firmware/vidc.mdt");
symlink("/firmware-mdm/image/wcnss.b00", "/system/etc/firmware/wcnss.b00");
symlink("/firmware-mdm/image/wcnss.b01", "/system/etc/firmware/wcnss.b01");
symlink("/firmware-mdm/image/wcnss.b02", "/system/etc/firmware/wcnss.b02");
symlink("/firmware-mdm/image/wcnss.b04", "/system/etc/firmware/wcnss.b04");
symlink("/firmware-mdm/image/wcnss.mdt", "/system/etc/firmware/wcnss.mdt");
For anyone unsure about creating the symlinks I have a very simple zip file to flash in recovery to delete the bad symlinks and make the right 1s! I have tested on SlimLP, A.I.C.P., Exodusand Pac-Man d2spr Roms. It will not mess up anything on your S3! It only does as stated. If you wanna check it its all in the script-updater. Just flash this after flashing a d2spr Lollipop rom and if you are also confused on modifying the script-updater for the rom so it will flash on the d2lterefreshspr then just flash the TWRP 2.8.7.0 recovery from TWRP's website and you wont have to worry about changing it!
Fixing Modem Symlinks For SPH-L710T.zip
https://drive.google.com/file/d/0B-Zg_yh4ytvLaS1xSzZ3bWhuTVk/view?usp=docslist_api
Hey man this is great! This opens up a whole new world of wonders for this device. You have any idea how I can fix having to manually select apn after each reboot?
triband
RootSuperSU said:
For anyone unsure about creating the symlinks I have a very simple zip file to flash in recovery to delete the bad symlinks and make the right 1s! I have tested on SlimLP, A.I.C.P., Exodusand Pac-Man d2spr Roms. It will not mess up anything on your S3! It only does as stated. If you wanna check it its all in the script-updater. Just flash this after flashing a d2spr Lollipop rom and if you are also confused on modifying the script-updater for the rom so it will flash on the d2lterefreshspr then just flash the TWRP 2.8.7.0 recovery from TWRP's website and you wont have to worry about changing it!
Fixing Modem Symlinks For SPH-L710T.zip
https://drive.google.com/file/d/0B-Zg_yh4ytvLaS1xSzZ3bWhuTVk/view?usp=docslist_api
Click to expand...
Click to collapse
now that i found it, are you going to be around for me to throw questions at. i know what to do but the problems ive had made me leery of flashing.
pgellen said:
now that i found it, are you going to be around for me to throw questions at. i know what to do but the problems ive had made me leery of flashing.
Click to expand...
Click to collapse
Yea man i work til 4-5pm but after that i can try to help ya! My S3 bricked on me and i dont have a 16gb sd to flash the unbrick image to but im always willing to try and help if i can
Sent from my LGLS885 using XDA Labs
rom flashing
RootSuperSU said:
Yea man i work til 4-5pm but after that i can try to help ya! My S3 bricked on me and i dont have a 16gb sd to flash the unbrick image to but im always willing to try and help if i can
Sent from my LGLS885 using XDA Labs
Click to expand...
Click to collapse
well, come to find out flashing octos, made for triband,,,,who knew, not me until today, anyway, its very easy. haha probably easier than ANYTHING i've done up to this point. i dont remember how much i've told you but the triband that i was fighting with so much may have had a problem from the very beginning. getting into recovery continually got harder and harder until it just wouldn't go. i tried about 8 times and it completely died. i mean its dead.im sad for that. that drops me to one sph-l710 with a crumpled usb and so i have to charge it wirelessly which is cool but its fragile. so ive got another refurb triband which im about to flash. WHY? ill be damned if i know why. this phone is rooted and cleaned out and runs beautifully. but, i want more. i guess or im just stupid which by reading this i may be. ill let you know.
triband
pgellen said:
well, come to find out flashing octos, made for triband,,,,who knew, not me until today, anyway, its very easy. haha probably easier than ANYTHING i've done up to this point. i dont remember how much i've told you but the triband that i was fighting with so much may have had a problem from the very beginning. getting into recovery continually got harder and harder until it just wouldn't go. i tried about 8 times and it completely died. i mean its dead.im sad for that. that drops me to one sph-l710 with a crumpled usb and so i have to charge it wirelessly which is cool but its fragile. so ive got another refurb triband which im about to flash. WHY? ill be damned if i know why. this phone is rooted and cleaned out and runs beautifully. but, i want more. i guess or im just stupid which by reading this i may be. ill let you know.
Click to expand...
Click to collapse
tonight if your not busy with other people ill have some questions for you. im looking forward to it. i loaded the rom, gapps and now theupdate has been in a holding cycle for half an hour. it vibrates a little every so often. so i guess ill let it go. i want in so i can finish setting it up. ive got a lot of work to do. i know you must.
Will this zip work for KK roms too? Or is it only Lollipop? I'm willing to test it out but I just want to be sure that I won't brick my S3 since I can't afford a new phone right now.
octos
yakob97 said:
Will this zip work for KK roms too? Or is it only Lollipop? I'm willing to test it out but I just want to be sure that I won't brick my S3 since I can't afford a new phone right now.
Click to expand...
Click to collapse
hey, supersu, help me fix this s3 triband when you get home and you feel like it. i can wait if you need. don't you come from work? let me know however, the biggest problem im having is my bluetooth doesnt work for music. works for everything else,that's a strange one. i'll wait for a reply.
yakob97 said:
Will this zip work for KK roms too? Or is it only Lollipop? I'm willing to test it out but I just want to be sure that I won't brick my S3 since I can't afford a new phone right now.
Click to expand...
Click to collapse
Yes it should work and no flashing it wont brick ur device at all! Nothing is flashed or installed it only deletes the wrong symlinks and creates the correct ones!
Sent from my LGLS885 using XDA Labs
pgellen said:
hey, supersu, help me fix this s3 triband when you get home and you feel like it. i can wait if you need. don't you come from work? let me know however, the biggest problem im having is my bluetooth doesnt work for music. works for everything else,that's a strange one. i'll wait for a reply.
Click to expand...
Click to collapse
Idk how to fix the bluetooth problem! Im not a developer or programmer i just google search alot and read very thoroughly and spend alot of time using FX File Explorer to study my system files! But whats the problem ur having other then bluetooth
Sent from my LGLS885 using XDA Labs
octos
RootSuperSU said:
Idk how to fix the bluetooth problem! Im not a developer or programmer i just google search alot and read very thoroughly and spend alot of time using FX File Explorer to study my system files! But whats the problem ur having other then bluetooth
Sent from my LGLS885 using XDA Labs
Click to expand...
Click to collapse
its about time you showed up again. i thought like these other senior members that once you dealt with the senior citizen with debatable alzheimer's you had fled the country also. hehe man i don't know. on my other triband i had no music at well, no sound at all, none. and i had no cell service. now everything works except the bluetooth on the music. as soon as i boot it up the music locks up. its weird. i was just prepping my phone to go back to stock. i think these tribands are better stock with the bloatware removed and not too much of that. ya, i spend alot of time with my file manager. have you tried total commander? its great. you get it from gizmos freeware. im just getting to know it but i have it on the computer and its pretty good.
pgellen said:
its about time you showed up again. i thought like these other senior members that once you dealt with the senior citizen with debatable alzheimer's you had fled the country also. hehe man i don't know. on my other triband i had no music at well, no sound at all, none. and i had no cell service. now everything works except the bluetooth on the music. as soon as i boot it up the music locks up. its weird. i was just prepping my phone to go back to stock. i think these tribands are better stock with the bloatware removed and not too much of that. ya, i spend alot of time with my file manager. have you tried total commander? its great. you get it from gizmos freeware. im just getting to know it but i have it on the computer and its pretty good.
Click to expand...
Click to collapse
Idk wat to say about that never had that problem! What room are u running? If oct os then ask them about it! I like the Slim Roms and S.O.K.P. the best but thats just me!
Sent from my LGLS885 using XDA Labs
I just flashed the final d2lte CM11 snapshot and your zip file, and it worked! After flashing everything the ROM runs super fast and runs wonderfully! So far as I can tell everything works perfectly. Camera, SMS and MMS, GPS, Mobile Data, and Screen Rotation all work perfectly. My steps for flashing were:
Modify Updater-scripts file to remove device checking
Wipe system, dalvik and cache, and data.
Flash CM11 snapshot
Boot to system
Reboot into recovery and flash Gapps and APN fix (I'm on virgin mobile)
yakob97 said:
I just flashed the final d2lte CM11 snapshot and your zip file, and it worked! After flashing everything the ROM runs super fast and runs wonderfully! So far as I can tell everything works perfectly. Camera, SMS and MMS, GPS, Mobile Data, and Screen Rotation all work perfectly. My steps for flashing were:
Modify Updater-scripts file to remove device checking
Wipe system, dalvik and cache, and data.
Flash CM11 snapshot
Boot to system
Reboot into recovery and flash Gapps and APN fix (I'm on virgin mobile)
Click to expand...
Click to collapse
I never liked CM myself! I prefer Slim or S.O.K.P. Roms more then any other! You can use alot of the non triband roms kernels and tweaks but just not the bootloaders or modems!
Sent from my LGLS885 using XDA Labs
octos
RootSuperSU said:
I never liked CM myself! I prefer Slim or S.O.K.P. Roms more then any other! You can use alot of the non triband roms kernels and tweaks but just not the bootloaders or modems!
Sent from my LGLS885 using XDA Labs
Click to expand...
Click to collapse
guess what? my second triband died last night. just running, fine. so, went to turn it on and it wouldn't come back on. is there any kind of a reset for the samsungs thAT I DONT KNOW ABOUT? the exact same thing happened with the other triband i had. so i take the phone back to the store and they give me another triband, they said. so i get it home and looked at it and immediately knew that it wasn't a triband. it was the original sph-l710 that i bought", to begin with. these guys dont know what they are selling. id like to complain but to who? this is truly a beautiful phone wit the brushed blue metal look and its one of the "grade A" refurbished phone so i guess maybe i have faith that this one will work.however im a little short on faith right now.
Wow! Good luck man. Honestly, if I had to choose I'd want the original one over the tri-band.
broken tribands
canodroid15 said:
Wow! Good luck man. Honestly, if I had to choose I'd want the original one over the tri-band.
Click to expand...
Click to collapse
ill tell you what, when it ran it ran very well. so what i want to know is tell me what you would do with this phone rom wise and maybe point me where to go get it. also i need all the stock files in case i have to flash this. this phone is very easy to fix. way easier than the triband but those had the same problem and i didn't know it until they up and died. so, if you have a minute. i've got all rooted. i've got selinux fixed and so, ....what is the latest liquid out there? by the way i watch the tide religiously. have for years. i also just noticed your logo. are you part of octos? ah, i think i saw your name. so i had octos on my triband when it died but i didnt have bluetooth on music. it worked on phone. tell me how to set up octos. man i liked it but i have to have that bluetooth music. how do i fix that?
rom flashing
RootSuperSU said:
For anyone unsure about creating the symlinks I have a very simple zip file to flash in recovery to delete the bad symlinks and make the right 1s! I have tested on SlimLP, A.I.C.P., Exodusand Pac-Man d2spr Roms. It will not mess up anything on your S3! It only does as stated. If you wanna check it its all in the script-updater. Just flash this after flashing a d2spr Lollipop rom and if you are also confused on modifying the script-updater for the rom so it will flash on the d2lterefreshspr then just flash the TWRP 2.8.7.0 recovery from TWRP's website and you wont have to worry about changing it!
Fixing Modem Symlinks For SPH-L710T.zip
https://drive.google.com/file/d/0B-Zg_yh4ytvLaS1xSzZ3bWhuTVk/view?usp=docslist_api
Click to expand...
Click to collapse
are you active this night? im about to flash octos. first, i want to ask a couple questions,,,first, what about xposed, is that runnable on a sph-l710? what about dirty? i know it wouldn't run on a triband but this 710? ok enough. how about googles N? is it.
pgellen said:
are you active this night? im about to flash octos. first, i want to ask a couple questions,,,first, what about xposed, is that runnable on a sph-l710? what about dirty? i know it wouldn't run on a triband but this 710? ok enough. how about googles N? is it.
Click to expand...
Click to collapse
Since you're not on a triband just flash the d2spr build, not the d2refresh build. You can run xposed on our ROM if you wish. We always recommend a clean flash, especially if coming from stock or any other ROM. Even if its Oct-L to Oct-M. ??

Porting LineageOS 14 to the d710

Disclaimer: I am not a ROM developer. I am a developer and Linux user, but I know next to nothing about creating Android ROMs. Whole other world to me.
I'm wondering if all three of us Epic 4G Touch users left might be able to get a working port of LineageOS 14 on our aging handsets.
The good news:
I just loaded the Official LineageOS 14 for i9100 20170419 nightly on my d710, and IT WORKS
...almost.
The bad news:
The ROM boots up, everything works and looks normal except for:
Wi-Fi - Settings app spins with message "Turning Wi-Fi on..."
Menu Button
Home Button
Now, I'm wondering if there is a way to fix these problems. I prefer on-screen navigation anyway, so that's probably an easy "fix." But Wi-Fi will probably be trickier. I assume it's kernel related, but I can't find any Nougat kernels for this device, so that will likely be the most difficult part.
Thoughts? Anyone else out there have any input or want to give this a crack?
Links:
https://wiki.lineageos.org/devices/i9100/build
https://wiki.lineageos.org/devices/i9100/install
https://web-beta.archive.org/web/20161224202958/https://wiki.cyanogenmod.org/w/Build_for_d710
https://web-beta.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
https://github.com/LineageOS/android_device_samsung_d710/tree/cm-12.0
https://github.com/LineageOS/androi...4.1/arch/arm/configs/lineageos_d710_defconfig
https://github.com/Lanchon/TWRP-Patcher-SGS2
https://github.com/Lanchon/REPIT
https://forum.xda-developers.com/ep.../rom-cyanogenmod-11-official-nightly-t2852074
Can you pm me your rom you used, i may be able to figure out how to get wifi to work, i dont have access to a computer right now but i can take a look at the rom you used when i get to one
svaethier said:
Can you pm me your rom you used, i may be able to figure out how to get wifi to work, i dont have access to a computer right now but i can take a look at the rom you used when i get to one
Click to expand...
Click to collapse
Link is in the OP. Here it is again: https://forum.xda-developers.com/galaxy-s2/general/rom-t3555834
Direct link to the download page: https://download.lineageos.org/i9100
How did you get past the 07 error then? Ive tried clearing everything from system to dalvik cache and nothing gets me to install the rom to look into the wifi issue properly
svaethier said:
How did you get past the 07 error then? Ive tried clearing everything from system to dalvik cache and nothing gets me to install the rom to look into the wifi issue properly
Click to expand...
Click to collapse
I don't know what you're talking about. I don't get an error.
The ROM flashes without modification. Make sure you have an up-to-date TWRP with the i9100 crossflash patch: https://github.com/Lanchon/TWRP-Patcher-SGS2
Ive tried flashing twrp onto my device using the guide that tells you how, even after editing the installer script to have the SPH-D710 line in it it aborts the installation
svaethier said:
Ive tried flashing twrp onto my device using the guide that tells you how, even after editing the installer script to have the SPH-D710 line in it it aborts the installation
Click to expand...
Click to collapse
I followed lots of advice from this thread: https://forum.xda-developers.com/epic-4g-touch/help/help-getting-stock-rooted-4-1-2-to-cm11-t3384832
I believe the method that finally worked for me was: Odin to EL29 rooted, Philz recovery, TWRP, CM11.
That's where I was before I tried the i9100 LOS 14.1 ROM.
I can get a twrp with a different rom then cm11 but that twrp doesnt have the img installation feature on it
svaethier said:
I can get a twrp with a different rom then cm11 but that twrp doesnt have the img installation feature on it
Click to expand...
Click to collapse
If you have root in CM11, you can use Flashify to flash the new TWRP .img file.
My E4GT still works, more than glad to throw my hand in the pot to make something happen. Haven't used the S2 in years so it's not updated, currently running an old build of CWM and a CM11 nightly with iso-rec support. If you could bring me up to speed on what I need to get from where I am to a newer recovery(TWRP preferred) and your ROM I'll start playing around with it. Last time I searched all of this to update left me more confused than anything with it being mixed up with the i9100 and i777 information as well.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
My E4GT still works, more than glad to throw my hand in the pot to make something happen. Haven't used the S2 in years so it's not updated, currently running an old build of CWM and a CM11 nightly with iso-rec support. If you could bring me up to speed on what I need to get from where I am to a newer recovery(TWRP preferred) and your ROM I'll start playing around with it. Last time I searched all of this to update left me more confused than anything with it being mixed up with the i9100 and i777 information as well.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
You should be able to flash the latest TWRP (for i9100) using Flashify. Beware that I have not been able to get TWRP to mount my external SD card, so any files you want to flash in TWRP need to be stored on internal memory. Everything else works perfectly. Mounting USB storage in TWRP works well, and that's how I've been able to get new files on the phone when I needed to.
After installing TWRP, make sure you run Lanchon's crossflash patch on it: https://github.com/Lanchon/TWRP-Patcher-SGS2
I used
Code:
lanchon-twrp-patcher-20160417-crossflash-d710.zip
to enable flashing d710 and i9100 ROMs.
flamadiddle said:
You should be able to flash the latest TWRP (for i9100) using Flashify. Beware that I have not been able to get TWRP to mount my external SD card, so any files you want to flash in TWRP need to be stored on internal memory. Everything else works perfectly. Mounting USB storage in TWRP works well, and that's how I've been able to get new files on the phone when I needed to.
After installing TWRP, make sure you run Lanchon's crossflash patch on it: https://github.com/Lanchon/TWRP-Patcher-SGS2
I used
Code:
lanchon-twrp-patcher-20160417-crossflash-d710.zip
to enable flashing d710 and i9100 ROMs.
Click to expand...
Click to collapse
Yeah, I took another look last night, the information available now clarifies things that seemed a mess back when I first looked into this.
Have you made any progress with your ROM? If the hardware keys are still not working it's because key mapping is different on i9100, also rotation is backwards or at least it was years back when I flashed a i9100 ROM on my D710. You can remap the hardware keys so that they function correctly. Other than that there should be no differences.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Yeah, I took another look last night, the information available now clarifies things that seemed a mess back when I first looked into this.
Have you made any progress with your ROM? If the hardware keys are still not working it's because key mapping is different on i9100, also rotation is backwards or at least it was years back when I flashed a i9100 ROM on my D710. You can remap the hardware keys so that they function correctly. Other than that there should be no differences.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I haven't done anything yet except try to load the unmodified i9100 ROM and report what works/doesn't. Really the only thing I need fixed is the Wifi, and I have no clue how to do that.
flamadiddle said:
I haven't done anything yet except try to load the unmodified i9100 ROM and report what works/doesn't. Really the only thing I need fixed is the Wifi, and I have no clue how to do that.
Click to expand...
Click to collapse
I'll reach out to some developer associates and see what I can find out about the WiFi.
Sent from my SM-S903VL using Tapatalk
I'm not a developer, but I have a D710 lying around and I am willing to do testing if you need me
I also have an Epic 4g touch that im willing to test stuff
So... I guess nothing ever happened with this ROM? I have a SCH - R760 from US Cellular that AFAIK is compatible with d710 roms. I would still be interested in running Nougat on my device - even though my eMMC seems to have issues at the moment.
chrismin13 said:
So... I guess nothing ever happened with this ROM? I have a SCH - R760 from US Cellular that AFAIK is compatible with d710 roms. I would still be interested in running Nougat on my device - even though my eMMC seems to have issues at the moment.
Click to expand...
Click to collapse
Never had any real interest, and I don't know enough to do it myself.
flamadiddle said:
Never had any real interest, and I don't know enough to do it myself.
Click to expand...
Click to collapse
Understood. So you said that the buttons didn't work and the wifi wasn't turning on. Were there any other major bugs that you noticed? I might try and make it work for our device, because why not!
Thanks for still responding after so many months!
chrismin13 said:
Understood. So you said that the buttons didn't work and the wifi wasn't turning on. Were there any other major bugs that you noticed? I might try and make a for for our device, because why not!
Thanks for still responding after so many months!
Click to expand...
Click to collapse
Those were the only two things I noticed. Bluetooth worked. I didn't see any apps crash (but I couldn't load new ones because no wifi). I didn't try cell service because I don't even have Sprint anymore, but I suspect that probably didn't work for the same reason wifi was killed.
Thanks for looking into this! I'm still interested if we can find a way to make it work. I just don't know much about creating ROMs. I'm not an Android dev.

[Rom] [Ufirm_Flat_QE2_Hybrid_Nougat_Rom_FlashFire_Install][Status Official For All]

Latest Ufirm QE2 Nougat Firmware For The S7 Flat Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up​
Files To Download
Odin.zip
ADB_Root_G930U_QE2Files.zip
UFIRM_G930_Odin_Firmware.zip
FlashFire_Flashable_G930UFirmware.zip
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G930_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Goto Step 3 Below
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G930_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G930U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. Im not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
6. Unzip FlashFire_Flashable_G930UFirmware.zip
7. Copy AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 to your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip to your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source
In the OP I had the ADB_Root_G930U_QE2Files.zip linked to the ADB_Root_G935U_QE2Files.zip zip so please make sure you have the ADB_Root_G930U_QE2Files.zip when downloading. Its fixed in the OP now so just double check
Wonderful. Can't thank you enough. Installed and setting up.
I recommend everyone put the Flashfire AP zip and Rom Zip on your internal storage as the AP file is so large that it may not be read properly do too limitations of some SD Cards. When you select AP file in Firmware there should be 4 partitions that are selected. If not then you have a bad download or need to have AP file on internal storage
Can this ROM be subsequently rooted?
aarongaudette said:
Can this ROM be subsequently rooted?
Click to expand...
Click to collapse
If you want but I recommend trying as is first for a few days you probably won't miss root
aarongaudette said:
Wonderful. Can't thank you enough. Installed and setting up.
Click to expand...
Click to collapse
Did LTE work ok for you
Since only 2 people between this and edge thread. Have even tried it's obvious there is zero interest over here at AT&T for Rom development. I probably won't waste anymore time
jrkruse said:
Since only 2 people between this and edge thread. Have even tried it's obvious there is zero interest over here at AT&T for Rom development. I probably won't waste anymore time
Click to expand...
Click to collapse
Yea, there ain't much activity over here anymore. I'm debating on even releasing my other rom I'm building.
dirtydodge said:
Yea, there ain't much activity over here anymore. I'm debating on even releasing my other rom I'm building.
Click to expand...
Click to collapse
I figured it would be worth it since AT&T people are on my Verizon thread a lot trying to flash that and it's not even for their phones and especially now that there is a way to have custom Rom without using engboot or root. People ask my why I don't make Sprint or AT&T roms well this is why. I was even going too make this rom and use AT&T firmware so everything worked
Hello. I know this forum is not as active as the Verizon thread for this mod, but I did have a question if anyone is willing to answer.
I was wondering what the process is for using adb to make an application a system app?
I saw others talking about doing this in the Verizon thread, as well as several posts mentioning a guide for how to do this without needing to root. I looked over several pages in the Verizon thread for how to accomplish this, but could only find bits and pieces scattered through several different pages. I probably didn't look hard enough, but I was wondering if someone could explain the process that works with this ROM.
Thank you.
jrkruse said:
I figured it would be worth it since AT&T people are on my Verizon thread a lot trying to flash that and it's not even for their phones and especially now that there is a way to have custom Rom without using engboot or root. People ask my why I don't make Sprint or AT&T roms well this is why. I was even going too make this rom and use AT&T firmware so everything worked
Click to expand...
Click to collapse
I'm currently flashing, ill get back later
---------- Post added at 07:03 AM ---------- Previous post was at 07:02 AM ----------
Devman-0903 said:
I'm currently flashing, ill get back later
Click to expand...
Click to collapse
ill be constantly checking the roms thread.
Crossbows said:
Hello. I know this forum is not as active as the Verizon thread for this mod, but I did have a question if anyone is willing to answer.
I was wondering what the process is for using adb to make an application a system app?
I saw others talking about doing this in the Verizon thread, as well as several posts mentioning a guide for how to do this without needing to root. I looked over several pages in the Verizon thread for how to accomplish this, but could only find bits and pieces scattered through several different pages. I probably didn't look hard enough, but I was wondering if someone could explain the process that works with this ROM.
Thank you.
Click to expand...
Click to collapse
The threads not inactive I just can't seem to get any feedback or participation so it makes it hard too want to spend time for nothing. For your question. Adb method only works on my nonrooted roms
Devman-0903 said:
I'm currently flashing, ill get back later
---------- Post added at 07:03 AM ---------- Previous post was at 07:02 AM ----------
ill be constantly checking the roms thread.
Click to expand...
Click to collapse
Thanks I can't improve or fix problems without feedback. I don't have AT&T service so I need your guys help
jrkruse said:
Thanks I can't improve or fix problems without feedback. I don't have AT&T service so I need your guys help
Click to expand...
Click to collapse
Hey, I love this rom. It only took one time to finish
I have had issues with system where I would make edits using rom control and system would fail, I will try all your roms , I have been waiting for something on 7.0, very stable and fast!, would be glad to try betas
Omigawd I love this! I did end up rooting so as to modify string to give me data toggle. Working amazingly well. You are a hero. Everything seems to be working flawlessly. I am sure to mess something up though as I love to play.
aarongaudette said:
Omigawd I love this! I did end up rooting so as to modify string to give me data toggle. Working amazingly well. You are a hero. Everything seems to be working flawlessly. I am sure to mess something up though as I love to play.
Click to expand...
Click to collapse
Although I lost Always On Display. My fault?
aarongaudette said:
Omigawd I love this! I did end up rooting so as to modify string to give me data toggle. Working amazingly well. You are a hero. Everything seems to be working flawlessly. I am sure to mess something up though as I love to play.
Click to expand...
Click to collapse
I forgot to add data toggle. I was going too
jrkruse said:
I forgot to add data toggle. I was going too
Click to expand...
Click to collapse
Ok, I will update when you do, I rooted mine with your on-demand governor, runs smoothly
---------- Post added at 03:54 PM ---------- Previous post was at 03:51 PM ----------
Devman-0903 said:
Ok, I will update when you do, I rooted mine with your on-demand governor, runs smoothly
Click to expand...
Click to collapse
Is WI-FI Calling not working for you
I guess my aggravation with running like butter on the original root process for a while, then taking a nose dive out of no where, re flashing, re rooting, editing build props, re editing build props, re flashing,...blah, blah, blah...I kind of over looked these roms. I mean, I had to rooted. Period. Been rooted on U using the 2.82 SU with tweaks (I think you tweaked it jrkruse?) for a good while, then out of no where, it crashes. Its crazy. I was just about to flash back to stock, and I saw this thread. Kanged or not (or whatever you said in another post on a different thread..lol) this is to cool. I got it going just before I had to go work this afternoon so I didn't get to mess with it much, but the fact that all the bs is gone, is enough for me. All I want is a choice of what to put on my phone. Definately have that now. Nice job jrkruse. I'm liking it. Only issue I'm having is calling out. Pretty sure i know what the deal is. Should only be a flesh wound. I'm going to mess around with it now. I'll post results if I figure it out. Thanks again jrkruse!! I know that it has to be pain to make a rom like this and only have a few posting about it, but dude, I really do appreciate it. I think if folks would give it a try, they would like it better than original root.

Categories

Resources