Related
ROOTSide ROM
Base Flipside ROM with root/busybox/unknown sources enabled. Only thing different in this rom than rooting it yourself is you get to check/uncheck unknown sources. Yes, that means you can turn unknown sources ON and OFF! I have a clockworkmod recovery folder zipped up for distribution, but I want to post a full-fledged ROM zip file for the masses. PM me, and I will send you the ZIP file that I have right now.
What you get:
base install for the flipside (AT&T) with motoblur ready to set up. It is the exact same thing as doing a factory reset, but you get all the benefits of superuser with busybox and the addead feature of having unknown sources checkbox in the settings.
I will work towards a deoxed version this weekend as well.
No custom bootscreen (yet). No custom anything, really.
Almost There
I am currently in the middle of Deodexing the image. I have added in wifi tethering, and ensured it will have superuser and busybox pre-packaged. Next step is pushing this to my wife's phone and not having her get a pretty brick in return. If all goes well, I will be posting the image by morning light (CST).
Fingers Crossed!
Well
Things didn't go too well with my first build attempt. Appears to be a permission issue with the /system folder. I will sleep on it, and give it a second go in the morning. Sorry for the apparent "tease". If you want a faster build, I could use some other devs working with me.
Hey man, sounds like you're doing great! Keep it up...I already found a way to get the root with unknown sources checked, so i'm just gonna wait for the deoxed version! Hope it goes well as you try again.
Current Issues
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Me too...good luck!!
jonsjava said:
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Click to expand...
Click to collapse
Both of those files are att/moto bloat... just be rid of them
Sent from my MB508 using XDA App
Glad to see some work on this device, I love the form factor but it's obviously not very popular with devs...
Very interested to see this come around. I would like to streamline the wife's phone. Her battery life is a 1/3 of my rooted and flashed X10. Sadly though I am NOT a Dev nor even a cook.
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
so I was curious, I was able to get to unlock mode with an sqlite thing and it worked just fine for me, but have you been able to knock out the bloat and stuff? cause it sounds like the makings of a custom rom lol
you know what the turtle said.. slowly but surely I will win this race
jonsjava said:
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
Click to expand...
Click to collapse
Several ppl have said they have run into this problem...don't know what the deal is...
Is it possible to get CM7, or it's a problem with a locked kernel?
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
jonsjava said:
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
Click to expand...
Click to collapse
sounds good man, keep us posted on progress!!
So check this out...I messaged the guy at modmymobile and asked how things were going becuase I heard people were having problems getting an updated CMW and this is his response:
"been sittin on the updated cwm recovery binaries and been draggin my feet/takin a break the past week or 2. i'll throw something out soon, but cant commit to a timeframe, sorry."
Looks like things are on the up and up...stay patient everyone
GOOD JOB!!!,
We are waiting for the rom
Dukenukemx said:
Is it possible to get CM7, or it's a problem with a locked kernel?
Click to expand...
Click to collapse
I can't install CM7, it reboots and locks up, then I have to reinstall froyo. It never worked when I had eclair either.
Better Than LIfe
Future Echoes
7-15-11
Update #2 fr the day
Ok, stumbled across something today while trying to work some bugs.....
I managed to "inject" a recovery into the rom, and while it actually booted into recovery, and did recovery things, it even went so far as to boot the tab.
But that was it, didnt get a full boot.
So, I stumbled upon a Clockwork Recovery buy doing the right tricks i suppose, however alot needs to be ironed out. and this gets top priority this weekend, why? well ****, think about it, CWM for the CDMA Tabs for Gingerbread, and before Verizon releases GB, so this.......is great news.
Hope to have this done by end of weekend, and in doing so it might iron out the zip flash issue which means I can pump out those 2 roms.
Just wanted to share.
First, I'm removing the download link.
Second, yes I do get your PM's, and yes I do read them, and Yes, I agree....I am bad at getting back to people sometimes. Very busy trying to get GB out for the CDMA Tabs in a working fashion. I am sorry. Those of you who know me, just call, it does hurt my hands to type.
The Update.
I am yanking the download link as it is apparent that the release was/is a failure, how I managed to get it on my tab, no clue, however I cant duplicate it again.
I am working on the build, 1 for Sprint, 1 for VZW. I am trying to get it deodexed 100%, and at the same time get a VZW 3G build working.
However what is very important, that will take less time for me to flash a build to test.....is a recovery. We need a Gingerbread recovery. We do.
So I am doing a few things.....
1. doing my research on compiling a new kernal, and CWM for our tabs
2. asked for an recieved help in a new kernal and recovery
3. changing how i build these roms, no more "kitchens" or stupid "gui" based apps on Linux or Windslows that foul up the permissions, I am going 100% command line for a more effective result, and less need for revisions.
4. Working non stop through the weekend once my wife comes home from work today, so from noon today, to 3am sunday/monday I will be hard at work on all Better Than Life Releases.
I appreciate your patience in this botched release, next time, ill release a test build to a few people for a backup verification it will go without problem.
Until then, i gotta get to work.
Jim
Update..........7-12 6am
I just spent 5 hours trying every trick in the book... from extracting factory.rfs and trying to rebuild it to forcing a fake recovery... I got nothing. The problem is that ALL of the kernels that exist with CWM are ext4 froyo kernels, but the new kernel source for GB doesn't contain ext4 code... therefore, no flashy (unless by a fluke) because on reboot it tries to mount everything as rfs but it's in ext4 after you flash in an ext4 conversion kernel. I would have to design a new GB kernel with CWM and EXT4 modules in the source or revert a froyo kernel to pre-ext4 and put in a new cwm... either would take a couple of days... but I'm swamped right now. The only choice is for you to set it back up on your device like you had it and then pull a roto. Did what I could, sorry.
Click to expand...
Click to collapse
So, we tried (spacemoose and I) to get the extracted rom from my device to install on several others and ran across the same problems everyone else was having. however, the extracted rom being deodexed and zipalilgned, my device not.
So today I am going to try to get the 3G working, make the mods to the rom, and extract it, then try to inject the deodexed system and framework back in (which is always a ***** on a live device) and ill have no choice for now but to release a Heimdall flashable version of the rom.
I am waiting for that VZW release because with the sprint in my hands, and with a VZW version, all thats lacking is a Sprint tab to start making GB roms for both devices, however today will be a different story.
Oh, I did get TW4.0 to slightly work on the tab, itll either be released later, or maybe in an alpha build. I found it....well interesting. I tried it on the Psirens Rom (I have a TouchWiz4 version of Psirens) but it was way to damn buggy to release.
Ill keep yall posted today. Painpill time
Verizon wants to take their time, fine, screw them.
Gingerbread 2.3.4
Based on the Sprint update
Deodexed
Zipaligned
a little de-bloating
added CDMA/3G Verizon (3G with Verizon right now is a 50/50 shot
Kernal included in flashable zip
Just drop on SD Card, wipe everything
flash
enjoy
I am running this on my daily driver Verizon, to test and work bugs out and get 3G fully working, so expect alot...ALOT of updates and new versions of Gingerbread for Verizon.
This will be a constant updating project. So please expect bugs, and this is a last minute slap together thing tonight.
Enjoy.
More to come
Link
PULLED LINK FOR NOW 7-15-11
Omg thanks
Is this any faster/snappier than the stock SprintGB? I just finished getting it working on my vzw tab and it took me a while to get set up. Is it worth switching?
And btw thank you for all the work you do for the CDMA community, we greatly appreciate it!!
juanv145 said:
Is this any faster/snappier than the stock SprintGB? I just finished getting it working on my vzw tab and it took me a while to get set up. Is it worth switching?
Click to expand...
Click to collapse
Nandroid and try it out. That's what I'll be doing in a few minutes. Thanks Oldmacnut!
dammit. i just got Psirens 2.5 the way i like it. and now i wanna try this. i'm torn with overwhelmingly indecisive ennui now.
when u say 50/50 chance do u mean it may/may not work or itll only work sometimes?
damn seriously lol im trying to check the latest siren and i see this y bother with sirens lol
Macnut, this isent working at all for me. im flashing from your original psyrens mod and it wont flash at all. it said opening package....... cannot open sip,(bad) installation aborted.
wolfie083188 said:
Macnut, this isent working at all for me. im flashing from your original psyrens mod and it wont flash at all. it said opening package....... cannot open sip,(bad) installation aborted.
Click to expand...
Click to collapse
the link just updated. try re-download
indeed I'm lookin for the phone*.apk of VZW GB. is there an update of VZW?
Awesome, am giving this a try now.
Couple of questions:
1. Is this ext4?
2. Can we overclock with this kernel?
Thanks, this is huge for us suffering VZW tab owners!
When trying to install I got an error...something along the lines of, "error at line 11, can't symlink"
djf8 said:
When trying to install I got an error...something along the lines of, "error at line 11, can't symlink"
Click to expand...
Click to collapse
got the same error, it wont install for me
any solution to this? im tired of trying to get it to work. im now back to psyrens rc1 untill any update on this.
wolfie083188 said:
any solution to this? im tired of trying to get it to work. im now back to psyrens rc1 untill any update on this.
Click to expand...
Click to collapse
My "solution" was to just flash the Sprint rooted rom, which works with the VZW tab (not sure about 3g, though, I just use wifi anyway).
Would love it if we could get an ext4 and overclockable kernel working w/ GB for the VZW folks.
Going to download this today. This is almost more exciting than hcomb . I am glad someone is working on a vzm gbread rom.
Thanks Oldmacnut
Sent from my SCH-I800 using XDA App
Same here...
Sent from my ADR6400L using XDA Premium App
wolfie083188 said:
got the same error, it wont install for me
Click to expand...
Click to collapse
Same here...
Sent from my ADR6400L using XDA Premium App
Yeah, I'm sure something was just missed when oldmacnut compiled the zip for us. He'll get it worked out soon enough just hold off for now until there is word from him.
Getting the error as well. I am using the Sprint GB ROM in the meantime...
Oldmacnut can you give us more info on your custom ROM? I am assuming you have it rooted but the Sprint ROM is 190M while yours is 360M. Just wondering what kind of bloatware you removed and what if anything has been added to account for almost 2x the file size. Thanks
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
masterpker2 said:
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
Click to expand...
Click to collapse
AFAIK that was one the things thrown around for the Nook Tablet which also had a locked and signed bootloader. Maybe someone with the necessary skills should take a look and see if its viable? it looks like quite the undertaking though.
how can dumb people help
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
RobbandJenica said:
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
Click to expand...
Click to collapse
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
crossix said:
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
littleemp said:
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
Click to expand...
Click to collapse
I don't know if there is anyone that is actually working on a solution to unlock it or find a work around such as 2nd-init or kexec. I don't know if we have any experienced devs that have done that sort of thing in the past with other devices that actually own an a100 and are working on it. If we don't I'd suggest that someone contact someone that does have experience (ie. koush or possibly sc2k) and see if they would be willing to help.
I am not a bootloader / recovery guy and have never personally developed a working solution to a problem like this. I barely know how they work in conjunction with each other. I know that recovery runs it's own kernel and in order to get cwm to work you have to compile a kernel for your device and cwm uses it. I have tried several solutions that others have created but none of them have worked so far.
sc2k from the a500 forum created itsmajic for their device and I attempted to install it along with cwm but almost borked recovery on my tab in the process.
The recovery partition does some sort of checking (I dunno if its a checksum validation or what) but its obvious that the p7 partition in our device doesn't do the same thing as it does on the a500. So the bootloader hack for the a500 will not work for our device.
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
crossix said:
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
Click to expand...
Click to collapse
2nd-Init might be possible, we just need to find a binary that starts within init/init.rc that can be hijacked. On Motorola phones it is logwrapper, at this line in init.rc is the first it executes.
Code:
exec /system/bin/logwrapper /system/bin/mount_ext3.sh userdata /data
For this to work logwrapper has to be renamed to something else (logwrapper.bin , .orig) and executed in a new executable script called, logwrapper. In the script just about anything can be done. To run cwm, / gets remounted rw new init files replace the old. busybox, other binaries and a hacked adbd are unzipped. 2nd-Init then goes to work killing process 1 (init) and starts cwm. I believe in this case cwm is 2nd-Init rather than a recovery partition.
The a100 init.rc doesn't use logwrapper. One idea, which may be too far fetched and too far into init, is hijacking the bootanimation binary, but it runs as user 'graphics' which doesn't have elevated privileges. So could an su binary, compiled without requesting SuperUser.apk, be used in the hijacked bootanimation??... If it's too far in the boot process maybe we could atleast get init.d tweaks.
Hashcode has come up with an inventive new approach to cwm bootstrap called safestrap. A different partition is used to hold the rom keeping stock intact making it almost impossible to brick. For anyone interested I recommend reading his blog to see how it works hash-of-codes.blogspot.com/p/how-to-safestrap.html?m=0/. Attached is the logwrapper script from my Droid3 to get an idea of how it starts cwm. The safestrap.apk can also be downloaded from hashcode's blog for a better understanding. DO NOT install it, it can be unzipped and analyzed.
At this point theres no reason we can't deodex then make a custom rom/theme with just replacing atleast the system apps and the framework. With the update.zips theres no reason not to.
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Icewyng said:
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
Click to expand...
Click to collapse
True. I used edify script before to get my updates to work w/ CWR and I was formatting cache, userdata and system before reinstalling.
Perhaps working on an Acer update with the DSIDXA kitchen could help to get something workable?
Sent from my A100 using xda premium
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful.
Click to expand...
Click to collapse
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
crossix said:
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Oh good, should be able to make backups of /data, it umounts clean and dd works so that's a step forward. I was worried about partition overlap. tar might be useful too cwm uses it and Titanium and AppExtractor both can restore the data.
Hopefully this weekend I can try that along with possible init.d
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Its nice to see a possibility of methods popping up. Hopefully we make some hedge-way here.
crossix said:
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Click to expand...
Click to collapse
I'll look into it over the weekend as well. also, I will look into an update file and see if there are anything special in those as well.
Let us know how it goes with the kernel.
Did anyone ever experiment with NVFlash btw? or tried the Acer update decrypter?
Oh...and it seems the ICS ROM for the A200 has already leaked.
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
mvan4310 said:
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
Click to expand...
Click to collapse
GL, you'll probably get an android with an exclamation point when you try and flash it due to different signing keys used between tablets.
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
mvan4310 said:
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
Click to expand...
Click to collapse
You should post the last_log file from /cache/recovery, that'll tell you why it died.
On another note, the acer supplied kernel didnt include the config file they used to build so I'm having to roll my own Tried compiling with a minimal amount of settings, but the compile died..
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. ??
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.