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.
Related
Edit: This project has come to an end now that official nightlies have begun.
Remember - These builds are not official. They are being built from source on github, possibly with changes that may or may not end up in the official builds.
http://phones.crackflashers.com/glacier
Will need to know how to flash recovery through fastboot since you need to use clockwork 3.
I've attached a working recovery. (the attached recovery has been updated to 3.0.0.1, shoud fix some mounting issues. )
adb reboot bootloader
$fastboot flash recovery /path/to/recovery.img
If you 'd rather do it from the emulator follow http://forum.xda-developers.com/showpost.php?p=10131596&postcount=361
This is an alpha, so use at your own risk. And its definitely not official. So far no one has mentioned anything that doesn't work, but as usual, use at your own risk. Thatguy32404 and I are not responsible for anything that happens to your phone.
You also need gapps for 2.3, http://koush.tandtgaming.com//google/gapps-gb.zip
Alo, thanks to Grankin01, we now have a working gappps zip with the new market.
http://dl.dropbox.com/u/16719351/gapps-newmarket.zip
Also, if you decide to go back to a froyo rom, you'll need to flash the old recovery. Its also attached. If you need help flashing the recovery,
check this thread: http://forum.xda-developers.com/showthread.php?t=852905
Also, if you are having trouble with adb/usb drivers check out the below thread by b16a2smith
http://forum.xda-developers.com/showthread.php?t=896206
So far all I can tell is wifi isn't working. Still testing everything else.
GPS works.
Wifi wirked after a reboot, not sure if that means its gonna continue working.
Also, I cant get my computer to even recognize the phone through adb. Tried updating the drivers and still no luck.
I'm curious to see how your testing goes, please keep us updated!
Sent from my HTC Glacier using XDA App
option94 said:
So far all I can tell is wifi isn't working. Still testing everything else.
Click to expand...
Click to collapse
Could you possibly post some screenies when you get a chance, thanks
stlouie65 said:
Could you possibly post some screenies when you get a chance, thanks
Click to expand...
Click to collapse
Of course. Im still trying to get the market to work though, if I can do that, I'll start posting more info.
option94 said:
Of course. Im still trying to get the market to work though, if I can do that, I'll start posting more info.
Click to expand...
Click to collapse
Appreciate it very much, thanks
i just finished fastboot flashed the new CWM recovery V3 and now flashing CM7 hopefully i can help you as well. but im not a dev so i might not be as much help but i guess if we all pitch in we can finally get gingerbread for our phones hehehe
Good to know you guys are working on this for us. I can't wait for this to be good for daily bases.
Sent from my HTC Glacier
So far, Everything seems to work just fine, except I cant find a working gapps.
same here i tried the gingerbread gapps and the froyo based gapps but nothing shows up... but everything thats included in this rom works fine. you can tell this is a plain ASOP rom but it has extreme potential though
option94 said:
So far all I can tell is wifi isn't working. Still testing everything else.
GPS works.
Wifi wirked after a reboot, not sure if that means its gonna continue working.
Also, I cant get my computer to even recognize the phone through adb. Tried updating the drivers and still no luck.
Click to expand...
Click to collapse
Do you have the new SDK installed?
Here is working Gingerbread Gapps.. enjoy =D
http://koush.tandtgaming.com//google/gapps-gb.zip
Can't wait for this to reach the current CM6 usability.
the USB mass storage drivers dont work and just like the G2 the wifi doesnt work either well it does when it wants too lol
Screen shots ?
i would love to but without working usb drivers the phone wont connect to the computer to mount the sd card
cant wait to test tonight!
has any1 confirmed anything not working? aside from wifi and pc recognition?
aznpr1de808 said:
the USB mass storage drivers dont work and just like the G2 the wifi doesnt work either well it does when it wants too lol
Click to expand...
Click to collapse
Drivers work fine for linux. Reboot and wifi will work.
Sounds like this is very close to public release no?
Sent from my HTC Glacier
yup theyre right just a reboot will fix the wifi and for me i have windows 7 and my pc wont recognize my phone lol other than that everything seems fine oh and i noticed that this rom boots up pretty quick like under 10 seconds which is not bad at all and the gapps-gb.zip that Jeffmeister post above work just fine as well too
PS- but the market is the old style if you want the new 2.2.7 you will need to download the apk from the nexus s forum
Update twrp 2.7, see Dhackers link for the img. Use Recovery Tools from Play to flash from home.
Seems that only Dhackers latest TWRP is the one to use.
Thanks to cyanidium for making it evident to me anyway.
Dhackers msm8960 goodies: http://androidhosting.org/Devs/Dhacker29/msm8960/
BTW Does anyone know what "twrp263-M44.img" is?
Attachments: the ...M44 is 1 day newer & works.
Just extract these to get the fastboot img.
More details
http://forum.xda-developers.com/showthread.php?t=2612883
More conformation http://forum.xda-developers.com/showpost.php?p=49978993&postcount=79
This one is not Dhacker latest anyway :
http://forum.xda-developers.com/showpost.php?p=45688558&postcount=1
Md5 starts with 791.
Want to try Philz.
http://forum.xda-developers.com/showthread.php?t=2545120
Want The latest 2631? w/ SDext usb mount. What is the rub?
This Photon Q TWRP, with full SD mount & more, works on the M! See attachments for the flash-able ver. Now for the rub: screen input requires the mirror of the buttons. I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL.... It is really not that hard to use. Think of it as a game also.
Md5 : 7630baf88ec9d6c2a144a2ee86ec9bb7
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
No settings, just bad! Thanks for the conformation Watson! We on a train with a new engine!!!
Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
How long have you known about it?
aviwdoowks said:
How long have you known about it?
Click to expand...
Click to collapse
I came across this issues first time trying to flash Paranoid and Pacman.
Which left me soft Bricked or in Bootloops. At the time i was just too fed up and went back to stock
second time i encountered that, was with the first stable KitKat by Dhacker.
That's when i decided to start clean and deleted all my Pre downloaded files and I was forced to download the new E33 from Dhacker.
And along with that all my other Roms and Files. I kind of figured something was bad with my TWRP file. But never thought of it since 791 wasnt found by my search engine.
And this December when I was flashing my GFs phone that's when I confirmed that the 791 didn't work for any of my roms.
Because I couldn't find Dhackers E33 through Google.De search (Some odd way searches come up differently if you search from different country)
And it did the same issues I had the First time around. That's when i dug around more and found Dhackers TWRP.
After using that I was able to flash Roms like a mad man until I found a Rom that my GF was comfortable using and liked.
Germanese said:
I came across this ....GF was comfortable using and liked.
Click to expand...
Click to collapse
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Ohh well now we all know!
Thanks again for the history.
This screwed up my data partition & I could not determine if it was philz or this. Then I decided the stop one, as I would go to the other & then data restore failure, so I used just philz & the problem went away!
aviwdoowks said:
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Click to expand...
Click to collapse
Nah i didn't post about it back then and recent we were side tracked ahahaha.
And I actually just got back couple days ago ... work ugh hate it already ...
There maybe a post few months back, me asking somewhere about which TWRP people are using,
because I had my doubt on which one to use; but no one really bothered to respond.
Then i just decided to flash away with what ever, since most errors resulted in an Harmless SoftBrick.
Since i figured a way around to that soft-brick, my thought was, what worse could happen, I did worse before LOL
I won't take credit, just stumbled upon it... That's all you. Just here to Confirm that i did have issues with that version.
Since then I been trying to see CWM for KitKat LOL
Hmm...
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?
Twilla said:
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?
Click to expand...
Click to collapse
Yes or the e33.
Not sure which is better. Philz is newest & I have an ini file to help you set it up see #2 post.
Update.
Haha. But not a joke. PHOTON Q twrp 2631 up.
twrp 2631 maybe provided by arrrghhh!
http://forum.xda-developers.com/showpost.php?p=49857073&postcount=176
If you want to be synched to his Q versions, go thank him!
That means a good screen version for our m.
Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!
Coronado is dead said:
Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!
Click to expand...
Click to collapse
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.
aviwdoowks said:
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.
Click to expand...
Click to collapse
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.
Coronado is dead said:
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.
Click to expand...
Click to collapse
May I suggest philz new version just out.
Allows you to format many /'s now.
I use only it now.
Not pocket proof like twrp. Beware
New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907
aviwdoowks said:
New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907
Click to expand...
Click to collapse
It works fine (I have flashed Dhackers *img) but if we want to flash any ROM we must change updater.script and add moto_msm8960 to device list on it.
I have success flashed BeanStalk after I add moto_msm8960 to updater.script
P.S. Also unified ROMs flashed great!
P.P.S. Gummy is most stable for me from unified ones
Flash TWRP-2.7.0.0-moto_msm8960-hdpi.img with Recovery Tools. See OP.
Would anyone know if Dhacker's TWRP works on the XT905 model as well?
Yes. But that is just good advice. I do not have one.
I just bought one! and love CM since the release of my first android phone, the Samsung Galaxy S2
There are only custom roms for the 8.4 and the 10.1 version.
There are no custom ROMs available for this device now, and i hate the slurpy/fancy samsung interface.
I am willing to pay for it, for the first nice and clean nightly CM 11 rom + CWM/TWRP recovery and working Gapps for this device.
This device is out for a while now and there are still no custom roms for.
So i hope there is somebody who can help, to get the custom roms madness for this device getting started.
I got you covered.
I can make a stock custom rom which has all the samsung junk removed so the tablet can go faster.
I want a rooted aosp rom, like cyanogenmod or something.
Are you able to do that?
ExoRRSmits said:
I want a rooted aosp rom, like cyanogenmod or something.
Are you able to do that?
Click to expand...
Click to collapse
Unfortunately, I can't. (I have a 10.1 and I want the same thing). The thing is the processor is a exynos 5 or something like that and it is (as I have read and understood) quite hard to do. I've tried to learn about making it but trust me it is much more harder than it seems. Even my 10.1 doesn't have CM yet. Still if you like I can make a you a stock debloated rom so it will at least run faster than what you have now.
ik4evr2 said:
I got you covered.
I can make a stock custom rom which has all the samsung junk removed so the tablet can go faster.
Click to expand...
Click to collapse
I am very much interested in this thanks!
nickster1 said:
I am very much interested in this thanks!
Click to expand...
Click to collapse
No problem at all. It will take me a day or two.
ik4evr2 said:
No problem at all. It will take me a day or two.
Click to expand...
Click to collapse
Can you make deodex please? I already have the stock debloate, but would be nice to have deodexed rom.
ik4evr2 said:
Unfortunately, I can't. (I have a 10.1 and I want the same thing). The thing is the processor is a exynos 5 or something like that and it is (as I have read and understood) quite hard to do. I've tried to learn about making it but trust me it is much more harder than it seems. Even my 10.1 doesn't have CM yet. Still if you like I can make a you a stock debloated rom so it will at least run faster than what you have now.
Click to expand...
Click to collapse
Well for now it sounds ok to me.
Is it rooted as well?
How debloated is it? Is samsung touchwiz removed?
That's what i'm hating the most. The settings app with tabs, i like the whole settings menu in cm.
And how fast can it see the light?
If its very nice, i can donate something for your good and hard work.
There might be a debloated deodexed rom already here?: http://forum.xda-developers.com/showthread.php?t=2776206
Ludespeed said:
There might be a debloated deodexed rom already here?: http://forum.xda-developers.com/showthread.php?t=2776206
Click to expand...
Click to collapse
No, I tried it, and unfortunately it doesn't work for the 12.2 version. The internal, as well as the external sd card both are locked, meaning you can't even update any apps, or saving any data... you get an error message 110, from Play Store.
ik4evr2 said:
No problem at all. It will take me a day or two.
Click to expand...
Click to collapse
Any luck ?
ExoRRSmits said:
Any luck ?
Click to expand...
Click to collapse
+1!
What about an overclock kernel? I debloated my Galaxy tab 12.2 already but have yet to successfully overclock it. I've been looking everywhere for an improved kernel or something to improve the performance, debloating didn't help it that much so a kernel or custom rom would be the next bet. Anyone point me in the right direction?
In school atm, but had a few mins so I built this: https://drive.google.com/file/d/0B5kaDFDMK0TYci14Nm1EOFFnX2s/edit?usp=sharing
Can't reply to any question atm but will when I get home. Not sure if it will boot.
Download, advance wipe in TWRP (except internal/external storage) and see if it boots to CM. Then post what's working and what's not
Enjoy if it works!
Gotta go
Shaheer said:
In school atm, but had a few mins so I built this: https://drive.google.com/file/d/0B5kaDFDMK0TYci14Nm1EOFFnX2s/edit?usp=sharing
Can't reply to any question atm but will when I get home. Not sure if it will boot.
Download, advance wipe in TWRP (except internal/external storage) and see if it boots to CM. Then post what's working and what's not
Enjoy if it works!
Gotta go
Click to expand...
Click to collapse
Great initiative,
I tried making an install. Unfortunately everything halts at the cm welcome screen with the message "Unfortunately, the process com.android.phone has stopped", Maybe, I'm not too surprised since we're using a wifi-version. But, it actually boots up, so there are great expectations for a cm11 port, within short.
Thanks for all your efforts.
arcadia2uk said:
Great initiative,
I tried making an install. Unfortunately everything halts at the cm welcome screen with the message "Unfortunately, the process com.android.phone has stopped", Maybe, I'm not too surprised since we're using a wifi-version. But, it actually boots up, so there are great expectations for a cm11 port, within short.
Thanks for all your efforts.
Click to expand...
Click to collapse
Hey everyone,
So here is an update: (At school so don't have much time but...) This should fix the phone error. :good: However, I am pretty sure Wi-Fi isn't going to work ATM. Since i'm at school can't download things internet is tooo slow, so what someone can do if they want is to download a touchwiz rom for your device or just plain stock rom. Then, on the download go to /system/etc and there should be a folder called Wi-Fi. Copy that to system/etc in the CM rom. And then flash the CM Rom. If Wi-Fi works go ahead and upload the link and post it here.
Download: https://drive.google.com/file/d/0B5kaDFDMK0TYRmNGUVUxVDloeWc/edit?usp=sharing
Shaheer said:
Hey everyone,
So here is an update: (At school so don't have much time but...) This should fix the phone error. :good: However, I am pretty sure Wi-Fi isn't going to work ATM. Since i'm at school can't download things internet is tooo slow, so what someone can do if they want is to download a touchwiz rom for your device or just plain stock rom. Then, on the download go to /system/etc and there should be a folder called Wi-Fi. Copy that to system/etc in the CM rom. And then flash the CM Rom. If Wi-Fi works go ahead and upload the link and post it here.
Download: https://drive.google.com/file/d/0B5kaDFDMK0TYRmNGUVUxVDloeWc/edit?usp=sharing
Click to expand...
Click to collapse
Just as you suspected the wifi didn't work initially. However, I followed your instructions for the update, and there it was. Here's the link to the updated cm11-4.4.4 w. wifi Currently, there seems to be no access to the internal SD card, as well as the external.
I also have difficulties in finding a compatible gapps, any ideas? Could it be due to the SD card issue? It starts up, but playstore crashes at first search.
arcadia2uk said:
Just as you suspected the wifi didn't work initially. However, I followed your instructions for the update, and there it was. Here's the link to the updated cm11-4.4.4 w. wifi Currently, there seems to be no access to the internal SD card, as well as the external.
I also have difficulties in finding a compatible gapps, any ideas? Could it be due to the SD card issue? It starts up, but playstore crashes at first search.
Click to expand...
Click to collapse
Will post an answer in a while. Leaving school in a min so I was just checking the thread. :fingers-crossed:
After homework and all that i'll upload the updated file when I get a chance to work on it.
Shaheer said:
Will post an answer in a while. Leaving school in a min so I was just checking the thread. :fingers-crossed:
After homework and all that i'll upload the updated file when I get a chance to work on it.
Click to expand...
Click to collapse
Great start Shaheer, apparently I'm running into a lot of the same problems that you initially ran into building the T-520 port.
Could I suggest that you start a thread in the development section for this ROM? I believe that I'm one of the few people having noticed your work, and that's only due to your message. Then we can get a few more people to chip in for heavy testing, at least the initial runs.
It would be good if the gapps along with the SDcard and PC-mount issues could have priority. Once they're up you can at least flash back and forth from the same ROM, without passing through an intermediary stock ROM. Notably, as each flash takes close to 30 min, if not more...However, I can believe they are all the result of the fact that the ROM can't detect the internal SDcard; no card = no mount, no card = no play store download.
On the good side, it seems like the GPS is working, and the bluetooth discovers surrounding devices and besides the mentioned SDcard issue, I have not seen much missing at least mot that can be tested at this point. There's no camera, but that seems to be something most AOSP ROM's for the Samsung tablets are struggling with currently.
Anyway, thanks again, I really appreciate your efforts.
arcadia2uk said:
Great start Shaheer, apparently I'm running into a lot of the same problems that you initially ran into building the T-520 port.
Could I suggest that you start a thread in the development section for this ROM? I believe that I'm one of the few people having noticed your work, and that's only due to your message. Then we can get a few more people to chip in for heavy testing, at least the initial runs.
It would be good if the gapps along with the SDcard and PC-mount issues could have priority. Once they're up you can at least flash back and forth from the same ROM, without passing through an intermediary stock ROM. Notably, as each flash takes close to 30 min, if not more...However, I can believe they are all the result of the fact that the ROM can't detect the internal SDcard; no card = no mount, no card = no play store download.
On the good side, it seems like the GPS is working, and the bluetooth discovers surrounding devices and besides the mentioned SDcard issue, I have not seen much missing at least mot that can be tested at this point. There's no camera, but that seems to be something most AOSP ROM's for the Samsung tablets are struggling with currently.
Anyway, thanks again, I really appreciate your efforts.
Click to expand...
Click to collapse
Hey!,
So I was really busy yesterday evening writing a 3 page essay and doing other homework so I didn't get anytime to work on the rom. My thoughts too were to start a new thread in the dev section for this.
I haven't gotten too far with the T520 port either as i'm still learning CM development. (I'm more used to touchwiz ) I have some time right now so give me a bit and i'll try to get a thread started and update the rom to get SD Card working.
EDIT: Actually, I can't proceed till someone can make sure that Google Play downloads app properly. If it doesn't then I need to work on that before anything or it's going to cause major issues.
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. ??
Q&A for [ROM][N5110][KK4.4.2][July-17-2015]Stock Rooted Deodexed[Regular/Debloated]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][N5110][KK4.4.2][July-17-2015]Stock Rooted Deodexed[Regular/Debloated]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
No wifi
I love love love this ROM, it's incredibly fast, I've got the debloated version. But I have no wifi on it. The wifi stays off and when I try to turn it on it flips right back to off again. Any suggestions? I wiped, cache, dalvik, everything before and after and reinstalled once. Will reinstall again.
I'm using TWRP vs CWM-would that make a difference?
TwistedPenguin said:
I love love love this ROM, it's incredibly fast, I've got the debloated version. But I have no wifi on it. The wifi stays off and when I try to turn it on it flips right back to off again. Any suggestions? I wiped, cache, dalvik, everything before and after and reinstalled once. Will reinstall again.
I'm using TWRP vs CWM-would that make a difference?
Click to expand...
Click to collapse
Glad you like the rom, thanks for the feedback!
Not sure about the wifi, haven't had any trouble on mine. N5110, right?
I have Philz on mine but don't see why TWRP wouldn't be fine... What rom were you on before?
Sent from my SM-N910W8 using Tapatalk
sefrcoko said:
Glad you like the rom, thanks for the feedback!
Not sure about the wifi, haven't had any trouble on mine. N5110, right?
I have Philz on mine but don't see why TWRP wouldn't be fine... What rom were you on before?
Sent from my SM-N910W8 using Tapatalk
Click to expand...
Click to collapse
I had tried several, but wipe completely each time. It might've been one of the Lollipops right before. I wondered if it had anything to do with the kernal? I don't know much about that aspect of it.
TwistedPenguin said:
I had tried several, but wipe completely each time. It might've been one of the Lollipops right before. I wondered if it had anything to do with the kernal? I don't know much about that aspect of it.
Click to expand...
Click to collapse
Yes kernel controls hardware related things including wifi if I'm not mistaken. Which kernel are you using? The stock kernel included with the rom or a custom kernel?
Sent from my SM-N910W8 using Tapatalk
sefrcoko said:
Yes kernel controls hardware related things including wifi if I'm not mistaken. Which kernel are you using? The stock kernel included with the rom or a custom kernel?
Sent from my SM-N910W8 using Tapatalk
Click to expand...
Click to collapse
I didn't ever specifically change kernels (if that's possible). I just installed 4 or 5 different ROMs over the course of the past few wks to see which I liked. I made back ups of my original stock/rooted ROM and several that I liked. I've got SlimKat ROM on here now, would it do any good for me to go into settings and see which kernel it is? Probably not, I suspect.
TwistedPenguin said:
I didn't ever specifically change kernels (if that's possible). I just installed 4 or 5 different ROMs over the course of the past few wks to see which I liked. I made back ups of my original stock/rooted ROM and several that I liked. I've got SlimKat ROM on here now, would it do any good for me to go into settings and see which kernel it is? Probably not, I suspect.
Click to expand...
Click to collapse
Ok no that's cool. Yes it's possible to change kernels, but since you didn't flash a different one that means you had the stock kernel (which is included with the rom and works fine). Just to be sure, you have the N5110 model, right?
sefrcoko said:
Ok no that's cool. Yes it's possible to change kernels, but since you didn't flash a different one that means you had the stock kernel (which is included with the rom and works fine). Just to be sure, you have the N5110 model, right?
Click to expand...
Click to collapse
Yes, sorry. It's the N5110 model.
TwistedPenguin said:
Yes, sorry. It's the N5110 model.
Click to expand...
Click to collapse
Ok cool thanks. Really not sure what the wifi issue on your setup might be. Works fine here and for other users as far as I see. I did a quick Google searche and the top solutions seem to be a factory reset, the "wifi fixer" app in the Play Store, or possibly trying different settings/channels/reboot on your router. If nothing works, then it might be because something got corrupted in the base over time by flashing different TW/AOSP ROMs, in which case it might be worthwhile to Odin stock firmware from sammobile and then install this rom and test. Might be more hassle for you than it's worth (especially if your other ROMs already work fine), but just trying to provide options lol. You could also try Regular instead of Debloated to see if there is any difference in wifi for you there.
sefrcoko said:
Ok cool thanks. Really not sure what the wifi issue on your setup might be. Works fine here and for other users as far as I see. I did a quick Google searche and the top solutions seem to be a factory reset, the "wifi fixer" app in the Play Store, or possibly trying different settings/channels/reboot on your router. If nothing works, then it might be because something got corrupted in the base over time by flashing different TW/AOSP ROMs, in which case it might be worthwhile to Odin stock firmware from sammobile and then install this rom and test. Might be more hassle for you than it's worth (especially if your other ROMs already work fine), but just trying to provide options lol. You could also try Regular instead of Debloated to see if there is any difference in wifi for you there.
Click to expand...
Click to collapse
I appreciate your input very much! I love this rom. I've got it installed again messing around with it while the Regular version is downloading. (I'm bestowed with slow rural internet). I'll let you know if Regular works better. It's probably going to bug me enough as to why it doesn't work that I'll go to the trouble of going back to stock, re-downloading and trying it fresh
TwistedPenguin said:
I appreciate your input very much! I love this rom. I've got it installed again messing around with it while the Regular version is downloading. (I'm bestowed with slow rural internet). I'll let you know if Regular works better. It's probably going to bug me enough as to why it doesn't work that I'll go to the trouble of going back to stock, re-downloading and trying it fresh
Click to expand...
Click to collapse
Sounds good! Yeah it's a bit of a hassle but at least you have other roms to fall back on worst case, but i'll admit this is kinda bugging me too so if you get to the bottom of it please let me know . [emoji106] . Thanks again for the positive feedback btw, happy to hear the rom's working out (aside from your wifi)
Sent from my SM-N910W8 using Tapatalk
Enable Android Encryption
Has anyone been able to successfully enable android encryption using this rom? I tried with the Deodexed version, safe boot, turning off SuperSU and haven't been able to get it to start encrypting properly. I need it since I have policy looking for encrypted state before I can allow mail to be made available.
Many thanks in advance!
LD
diazlaz said:
Has anyone been able to successfully enable android encryption using this rom? I tried with the Deodexed version, safe boot, turning off SuperSU and haven't been able to get it to start encrypting properly. I need it since I have policy looking for encrypted state before I can allow mail to be made available.
Many thanks in advance!
LD
Click to expand...
Click to collapse
Not sure... does it work fine on other rooted deodexed roms?
wifi won't turn on
Hi, I've flashed both the regular version and the debloated version on my N5110 after clean wipes.
The wifi will not turn on in either case.
I've done factory resets from within settings.
Any ideas?
I've read the thread, the Q&A thread, and done a google search to no avail....
I'm coming from stock 4.2.2 (rooted and unlocked of course) where everything worked... it just seemed to have a pretty short battery life.
I've reinstalled the nandroid backup and wifi still works there.
I'd really like to try this.
Thanks for your hard work as a developer by the way
zippersmith said:
Hi, I've flashed both the regular version and the debloated version on my N5110 after clean wipes.
The wifi will not turn on in either case.
I've done factory resets from within settings.
Any ideas?
I've read the thread, the Q&A thread, and done a google search to no avail....
I'm coming from stock 4.2.2 (rooted and unlocked of course) where everything worked... it just seemed to have a pretty short battery life.
I've reinstalled the nandroid backup and wifi still works there.
I'd really like to try this.
Thanks for your hard work as a developer by the way
Click to expand...
Click to collapse
Not sure...Works fine here but I saw another user report this a while back. The others said all working fine so I'm assuming something may have got corrupted on your setup along the way. Perhaps you can try using odin to flash the latest stock firmware for your device from sammobile.com, then try installing twrp through odin and finally my rom through twrp. Best way to eliminate variables and start fresh
sefrcoko said:
Not sure...Works fine here but I saw another user report this a while back. The others said all working fine so I'm assuming something may have got corrupted on your setup along the way. Perhaps you can try using odin to flash the latest stock firmware for your device from sammobile.com, then try installing twrp through odin and finally my rom through twrp. Best way to eliminate variables and start fresh [/QUOTE
This^
Worked for me. Nice smooth Rom... thank you I hope this saves me from constant looping unrooted stock provided. Although battery life seems to still drain quickly. Any thoughts?
Edit to say im having a slight issue with the tablet shutting down on its own when not in use.
Click to expand...
Click to collapse
BBBlessed said:
sefrcoko said:
Not sure...Works fine here but I saw another user report this a while back. The others said all working fine so I'm assuming something may have got corrupted on your setup along the way. Perhaps you can try using odin to flash the latest stock firmware for your device from sammobile.com, then try installing twrp through odin and finally my rom through twrp. Best way to eliminate variables and start fresh [/QUOTE
This^
Worked for me. Nice smooth Rom... thank you I hope this saves me from constant looping unrooted stock provided. Although battery life seems to still drain quickly. Any thoughts?
Edit to say im having a slight issue with the tablet shutting down on its own when not in use.
Click to expand...
Click to collapse
Thanks for confirming! Yes flashing different roms can corrupt system files so a fresh odin install is always a good way to start clean. No issues here with the tablet shutting down..could possibly be due to a rogue app conflicting with something or an xposed module. As for battery life I agree. Not worse than stock but not better either. The built-in battery is now also probably less efficient than it used to be, as they all do over time. Sammy should have put a bigger battery in this tablet!
Click to expand...
Click to collapse
sefrcoko said:
BBBlessed said:
Thanks for confirming! Yes flashing different roms can corrupt system files so a fresh odin install is always a good way to start clean. No issues here with the tablet shutting down..could possibly be due to a rogue app conflicting with something or an xposed module. As for battery life I agree. Not worse than stock but not better either. The built-in battery is now also probably less efficient than it used to be, as they all do over time. Sammy should have put a bigger battery in this tablet!
Click to expand...
Click to collapse
I did a battery pull and that help a great deal with the battery life . Also I don't think I have had the issue of shutting down maybe the rom needed to settle in lol. I don't know but all is well now thank you so much for this rom. My tablet isn't trash anymore.
Click to expand...
Click to collapse
BBBlessed said:
sefrcoko said:
I did a battery pull and that help a great deal with the battery life . Also I don't think I have had the issue of shutting down maybe the rom needed to settle in lol. I don't know but all is well now thank you so much for this rom. My tablet isn't trash anymore.
Click to expand...
Click to collapse
Awesome, glad to hear it's all sorted out now. Cheers!
Click to expand...
Click to collapse
Hello sefrcoko
my Note N5110 currently has the stock fw 4.2.2.
Once I have root and custom recovery, can I directly flash your rom?
Or I have to flash the stock fw 4.4.2 before your rom?
Thanks a lot
Bye