Related
Here is the update that everyone has been waiting for At the moment, I'm only providing the modem, and rooted, stock, deodexed version of the ROM. There will be a cleaned up version to go along with all of this in due time, but we're currently working out some problems with it. I would like to note that despite this being the Froyo update, it is not without its own set of problems, and odds are you may never see another update outside of this from anywhere. However, the benefits of getting Froyo will outweigh the problems with it for most people, so have at it.
You will need a few things to get this, first, the downloads list here will be needed (obviously). You'll also need to have CWM setup and know how to use Odin. Heimdall will also work for those of you not on Windows, but I'm not providing any instructions for flashing using Heimdall. Also note that you will want to wipe data or perform a factory reset before booting into Froyo to avoid any problems. While you may get away with not doing it, you could end up with several problems, so my recommendation is to wipe data. Also, you can flash the ROM first, or flash the modem first, which ever you want to do. There isn't really a required order for it, as long as you do both parts.
[size=+1]Instructions[/size]
Download everything you need.
Odin
Froyo Radio
ROM+Kernel
CWM Kernel
CWM update.zip
Put the ROM zip and CWM update.zip on your SD Card
Flash the Radio via Odin in the PDA box
Enter CWM and flash the ROM+Kernel
Wipe Data in CWM before restarting your phone
Restart and enjoy Froyo
[size=+1]Downloads[/size]
Modem
ROM+Kernel
FAQ
How can I donate to you for this?
You can either click the "Donate to me" button above my avatar, or go through this link. Don't feel obligated to donate though, as Verizon should have given this to you (the users) long ago.
Can I still receive updates after flashing this?
You cannot receive updates after flashing this unless you revert back to DL17, which is the latest official software released by Verizon and Samsung.
If I can receive updates on this, how can I restore back to DL17?
I've been sending this to several people already that have had problems with their phones. If you need to revert back to DL17 for any reason, download this. You will need 7-zip or similar to extract it. Once you have the .tar.md5 file, flash it in Odin via PDA like you did for flashing the modem to get Froyo.
Can I return my phone to Verizon for warranty repair/service with this on my phone?
No. If you need any sort of help with your phone from Verizon, you will need to have the stock DL17 ROM on your phone. Anything else and you have voided your warranty and Verizon and/or Samsung will not have to do anything to help you. See the above question for a package to restore your phone to the latest stock software.
Are there any bugs in this release?
Yes there are, just as there is with any software. I do not know what the bugs are though off hand though as I have not been using this update. I also cannot say whether any of the problems you may have will ever get fixed, seeing as you can't even get a straight answer on why the update has been taking so long.
Is xxx modification/theme compatible with this?
Odds are that it isn't. All of the current themes and modifications for DL17 will not work on this package. They will all need to be updated to be able to work. Given that this is a relatively new release, this could take some time, especially given that it is the summer and people are on vacation (I'm looking at you trailblazer ). We will work though to try and get all of the mods ported from DL17 to EC03 so that you don't have to give up anything to upgrade.
Will you release a "clean ROM" based on this?
Yes, and it is already in progress. I have sent it out to a couple people already to ask for feedback and any issues. Once they say it is ok, I'll create a new thread with the cleaned up version. There is currently no ETA on when it will be released though.
Are there any other kernels I can use with this besides the one that comes with it?
At the moment, there isn't. I'm trying to get a custom kernel to work, but it has some problems. At the very least, we can customize the stock kernel some, but I do not know if a full source built kernel will ever be available.
Can I flash this if I am on the voodoo kernel?
No, if you are running the voodoo lagfix kernel, you will want to disable voodoo prior to doing anything. If you don't, you'll be in for some fun times with Odin getting your phone back in a usable state.
Can I get something included in the FAQ?
Yes you can. Just create a post with the following template, and I'll try to keep the FAQ updated. If I don't see it or add it right away, don't worry, I'll try and update it. If it has been a week or two and I still haven't responded, just send me a message with a link to what you want included. Here is the format to use:
Code:
[PLAIN][b]Question goes here?[/b][/PLAIN]
Answer goes here.
I'm getting ready to download it
When I go to flash the radio, Odin says it's an invalid image type
circa881 said:
When I go to flash the radio, Odin says it's an invalid image type
Click to expand...
Click to collapse
It should work You aren't extracting or renaming it at all are you?
Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt
circa881 said:
Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt
Click to expand...
Click to collapse
Your phone is in download mode when you're attempting to flash via Odin?
XD Now I feel like a ruh-tard. I forgot about that part
Wait, it's still saying invalid image type
I'm in shock... I'm on this forum every day and I missed this?! I'm going to install this and mess around with it. Ill post any bugs I find later this evening..
Kudos @imnuts for the effort!
Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?
jaizero said:
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
Does it really matter?
No... No it doesnt.. Its working perfectly by the way.. But Im sure you already knew that lol..
If jaizero got it to work, why couldn't I?
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
jaizero said:
Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
It came from heaven!!!
Sent from my Mind
^ lolololol
Sent from my SCH-I400 using XDA Premium App
FROYO
i think i love you (no homo)
I successfully loaded the ROM.
It hang a bit longer than usual on the verizon logo but after that no issues.
Thanks imnuts and anyone else that worked to make this possible.
Kay, how are people getting this to work when I couldn't get the radio flashed
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
Ok I dl'd both files, I have Odin1.3 both blue n yellow CWM update.zip but what is CWM kernal?
P.S. I totally love you guys and many thanks to nuts for confirming my faith in opensource and saving my phone
Sent from my SCH-I400 using XDA Premium App
Hello!
Im wondering about JellyTime, Is it good or bad/very buggy?
Since im very intrested about it i want others opinion.
Also im new to this rooting and new ROM installs.
Thanks!
Well, it is a beta Rom, so it will have bugs. I use it as my main rom knowing it has some minor flaws. If you need a full running device you might want to read the thread a little before flashing this. Most of us flashing this are "Flashaholics" and don't mind flashing a new version everyday if needed. I'd say flash it to see what it's like, and then make your own decision. Only you will know if you like it. This goes for any Rom.
Edit:
Welcome to the forum!
TheJokah said:
Well, it is a beta Rom, so it will have bugs. I use it as my main rom knowing it has some minor flaws. If you need a full running device you might want to read the thread a little before flashing this. Most of us flashing this are "Flashaholics" and don't mind flashing a new version everyday if needed. I'd say flash it to see what it's like, and then make your own decision. Only you will know if you like it. This goes for any Rom.
Edit:
Welcome to the forum!
Click to expand...
Click to collapse
Ohhh okay ^^ is it possible to install the rom at the sametime as i root? sorreh im newb at this :3:highfive:
After you root, make a backup of your rom. Before flashing (download rom to sd card-remember where it was stored), reboot in recovery.
Wipe data/factory reset.
Wipe dalvik.
Format all partitions (except sd card).
Install from sd card.
Flash rom (search for the download)
Reboot.
The above is sorta the correct way of doing it afterwards. Most of us don't do it.
Wait 5-10 minutes.
Reboot.
Configure all you need to configure.
Install your apps.
Reboot.
If you want to know the issues of a rom, read the op(first page) and read the last 5-10 pages.
All ics - jb roms have bugs. Won't be long till they are fixed.
Gb roms are stable on the most part.
Search for 4ext touch recovery, it's the prefered one.
Sent from a dream.
TheJokah said:
Well, it is a beta Rom, so it will have bugs. I use it as my main rom knowing it has some minor flaws. If you need a full running device you might want to read the thread a little before flashing this. Most of us flashing this are "Flashaholics" and don't mind flashing a new version everyday if needed. I'd say flash it to see what it's like, and then make your own decision. Only you will know if you like it. This goes for any Rom.
Edit:
Welcome to the forum!
Click to expand...
Click to collapse
Teichopsia said:
After you root, make a backup of your rom. Before flashing (download rom to sd card-remember where it was stored), reboot in recovery.
Wipe data/factory reset.
Wipe dalvik.
Format all partitions (except sd card).
Install from sd card.
Flash rom (search for the download)
Reboot.
The above is sorta the correct way of doing it afterwards. Most of us don't do it.
Wait 5-10 minutes.
Reboot.
Configure all you need to configure.
Install your apps.
Reboot.
If you want to know the issues of a rom, read the op(first page) and read the last 5-10 pages.
All ics - jb roms have bugs. Won't be long till they are fixed.
Gb roms are stable on the most part.
Search for 4ext touch recovery, it's the prefered one.
Sent from a dream.
Click to expand...
Click to collapse
Ive installed JellyTime but when ive installed the rom it just says loading and is keeping to load. nothing happens for 20 mins.
any idéa what can cause this?
Valentia007 said:
Ive installed JellyTime but when ive installed the rom it just says loading and is keeping to load. nothing happens for 20 mins.
any idéa what can cause this?
Click to expand...
Click to collapse
Either a bad download or a bad wipe procedure.
Sent from a dream.
Teichopsia said:
Either a bad download or a bad wipe procedure.
Sent from a dream.
Click to expand...
Click to collapse
I got it to work now, BUT how do i get google play? <.< ive downloaded it but it dont work.. so how do i get to my Paid apps?
Edit: Also IF i want to have my old HTC Rom do i just use the Root program again? or do i have to download it from their site?
Valentia007 said:
I got it to work now, BUT how do i get google play? <.< ive downloaded it but it dont work.. so how do i get to my Paid apps?
Click to expand...
Click to collapse
Alright buddy, last one. After this you nees to start reading and searching for your own answers. Almost anything you can think of has already been posted.
It's called gapps. It's a zip file with several google apps. Flash the same as when you flash a rom. No wipe necessary.
Sent from a dream.
Teichopsia said:
Alright buddy, last one. After this you nees to start reading and searching for your own answers. Almost anything you can think of has already been posted.
It's called gapps. It's a zip file with several google apps. Flash the same as when you flash a rom. No wipe necessary.
Sent from a dream.
Click to expand...
Click to collapse
Okay thanks for all the help man! appreciate it
I tried to install it the same tho but it says the Zip file dont exists. But ill figure this one out
Valentia007 said:
Okay thanks for all the help man! appreciate it
I tried to install it the same tho but it says the Zip file dont exists. But ill figure this one out
Click to expand...
Click to collapse
If you have problems just pm (private message) me.
Sent from a dream.
Teichopsia said:
If you have problems just pm (private message) me.
Sent from a dream.
Click to expand...
Click to collapse
Thanks man ive sorted it out tho :3 thanks for all the help ^^
jellytime is moving very fast towards stability...
Even now its beta 110 could be used as a daily driver if you ignore some minor things..Bluetooth is the only major problem in it..other than that,it is smooth and really good
TOTAL NOOB here been reading for months now [in the background] and just joined as i think ive finally worked up the courage to brick my HD. :laugh:
I did see a question asking about "best roms" am after an easy stable and fully working combination tho, would love jellybean and fully understand its still in beta. I think more noobs would attempt stuff if it wasnt so damn confusing with regards options and bolt ons.
Ive been Useing JellyTime since yesterday and i love it, the only complaint i have at this moment is that when i lock the screen and unlock it after more than 5 min it takes up to 5-10 seconds for it to start. Maby fixed in new Beta 10. ill try install it later today or tomorrow.
Jimpy0 said:
TOTAL NOOB here been reading for months now [in the background] and just joined as i think ive finally worked up the courage to brick my HD. :laugh:
I did see a question asking about "best roms" am after an easy stable and fully working combination tho, would love jellybean and fully understand its still in beta. I think more noobs would attempt stuff if it wasnt so damn confusing with regards options and bolt ons.
Click to expand...
Click to collapse
The Desire HD/Inspire 4G are virtually un-brickable as long as you are not ENG-OFF. Once you start flashing roms it all will become like second nature. Everything will start to get easier(more confidence comes too ) Just keep doing what you are doing (reading the threads). I wish some people did this more before posting.
Valentia007 said:
Ive been Useing JellyTime since yesterday and i love it, the only complaint i have at this moment is that when i lock the screen and unlock it after more than 5 min it takes up to 5-10 seconds for it to start. Maby fixed in new Beta 10. ill try install it later today or tomorrow.
Click to expand...
Click to collapse
This is kernel related issue..also found in virtuous infinity sense 4 rom..
Bluetooth also is broken in beta 10..I still miss the smoothness of beta 7..that kinnda smoothness is yet to be seen on this new kernel
saeedyasir91 said:
This is kernel related issue..also found in virtuous infinity sense 4 rom..
Bluetooth also is broken in beta 10..I still miss the smoothness of beta 7..that kinnda smoothness is yet to be seen on this new kernel
Click to expand...
Click to collapse
One of the fun things tho is that when i have my headset in my phone the "lock screen" is opening as soon i press the button, and without the headset it takes 5-10 seconds like i posted earlier :3
1st step grabbed h/kit - more reading :cyclops:
just a quickie as well do i need to do the catchpa thing everytime i post ?
Jimpy0 said:
1st step grabbed h/kit - more reading :cyclops:
just a quickie as well do i need to do the catchpa thing everytime i post ?
Click to expand...
Click to collapse
You need to use catchpa for about the first 10 posts. then it should disapear.
This ROM is outstanding. I started with Beta 8 and it was great–at least for the first few days before Beta 9 came out. And now that Beta 10 is out, I'm going to flash that ASAP.
Then great thing about this ROM is that Randomblame just can't seem to give himself any downtime, although he does find time to spend with his family. As long as the ROM works and he isn't going crazy from it, that's alright with me.
Sent using Jelly Time: Sweet, Sugary Goodness!
I have been using Cyanogenmod 11 Nightlies for my device for about as long as they have been out, so I know it is still a work in progress, and most of the issues I have faced have gone away as newer nightly builds have been released, so I have not reported any issues as of yet.
Within the last month or so, I have noticed a new issue. The mobile data has been randomly cutting out, allowing only emergency phone calls. It only goes out for about a minute or two, but it is still a huge inconvenience. It seems to happen randomly, except after I finish a phone call -- it almost always cuts out immediately after (very frustrating for when calls are dropped, because I need to wait a minute or two before I can call back).
Has anyone else experienced this or know of a fix? I just tried re-flashing the latest radio and that did not seem to help. I have also tried full system/data wipes as well and none of the Nightly builds for the last month or so have been able to fix it.
Thanks, everyone.
You need to flash any touchwiz rom in order reset your nvram.
Corvetrims77 said:
You need to flash any touchwiz rom in order reset your nvram.
Click to expand...
Click to collapse
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.
pravus87 said:
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.
Click to expand...
Click to collapse
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).
Corvetrims77 said:
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).
Click to expand...
Click to collapse
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.
pravus87 said:
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.
Click to expand...
Click to collapse
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.
Corvetrims77 said:
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.
Click to expand...
Click to collapse
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.
pravus87 said:
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.
Click to expand...
Click to collapse
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.
mreadshaw said:
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.
Click to expand...
Click to collapse
I actually did not use Odin at all. I was able to find a thread that posted a 4.1.1 stock .zip, a .zip to keep root, and a .zip to keep custom recovery. (I have tried searching for the thread to share with you but am unable to find it). I was definitely over-thinking it. Just install the .zips from TWRP or CWM as you would any other custom ROM -- just make sure you do not have the 4.3 bootloader installed. That's it.
Sorry for the delayed response!
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.