Related
Hey guys. I have a problem and not sure how to go about this. My Evo was at 2.2 rooted for a long while and all of a sudden it started acting up. It would always freeze and had to be rebooted constantly. So I had a back that I went back to successfully but it is at 2.1 now (Baseband 2.15.00.09.01)
Now I'm not getting the OTA update to 2.2. I go into HTC software update and it says no available updates for my phone.
So how do I get to 2.2 or 2.3 rooted?
FYI after going into bootlaoder and choosing Recovery, I get Clockworkmod Recovery. Is this normal?
You need to flash the stock rooted ROM for the latest OTA update. I would suggest trying out some different Roms, though. That's the best part of rooting.
And ClockworkMod is the most popular recovery for the Evo, so yeah that's probably right.
http://forum.xda-developers.com/showthread.php?t=838448
Sounds like the perfect time to throw CM7 on there and see what you think about AOSP Gingerbread.
blackroseMD1 said:
Sounds like the perfect time to throw CM7 on there and see what you think about AOSP Gingerbread.
Click to expand...
Click to collapse
You are speaking a different language to me lool. I'm new to this so I don't know exactly what your talking about or how to go about doing that.
nawaf88 said:
You are speaking a different language to me lool. I'm new to this so I don't know exactly what your talking about or how to go about doing that.
Click to expand...
Click to collapse
It's pretty easy actually. Once you have root again (if you don't already), go to http://mirror.teamdouche.net/?device=supersonic and download either the newest nighly (30) or RC2 to your memory card.
Boot into Clockwork and go to backup and restore, and choose nandroid backup or backup (I'm not using clockwork, so I don't know the exact verbiage). Once the backup is complete, do a full system wipe by clicking on wipe data/factory reset.
Once that is done, choose install zip from sdcard, scroll down to cm_supersonic_full-30.zip and select it. It will install and then ask you to reboot. Go ahead and reboot.
Once your phone is up and running again, you'll want to get back into recovery so that you can flash GoogleApps, which you can find here: http://goo-inside.me/gapps/latest/7/universal/.
You'll flash these just like you did CyanogenMod 7 a minute ago, although you will want to wipe your cache and dalvik cache (which is located under "advanced" in the Clockwork menu) first.
All you have to do then is boot back up, go through the walkthrough to set up your google account, and then you'll be running (close to) stock Gingerbread 2.3.
If you need any help, feel free to ask.
Awesome!!! Thanks blackroseMD1!! I'll give it a try when I get home from work tonight. I'm not rooted right now. The last time I rooted I used unrevoked because it was so easy. Would that be good enough to get the process rolling?
nawaf88 said:
Awesome!!! Thanks blackroseMD1!! I'll give it a try when I get home from work tonight. I'm not rooted right now. The last time I rooted I used unrevoked because it was so easy. Would that be good enough to get the process rolling?
Click to expand...
Click to collapse
I'd actually use the link that CheesyNutz posted up there. Universal Auto Root works better than Unrevoked, from what I've heard.
blackroseMD1 said:
I'd actually use the link that CheesyNutz posted up there. Universal Auto Root works better than Unrevoked, from what I've heard.
Click to expand...
Click to collapse
Ok thanks. I'll try that and will keep you updated. Hopefully I have enough time tonight to do this.
nawaf88 said:
Ok thanks. I'll try that and will keep you updated. Hopefully I have enough time tonight to do this.
Click to expand...
Click to collapse
Shouldn't take long. Probably a half hour, tops, not counting download times. Let me know if you have any issues, and I'll see what I can do to help.
blackroseMD1 said:
Shouldn't take long. Probably a half hour, tops, not counting download times. Let me know if you have any issues, and I'll see what I can do to help.
Click to expand...
Click to collapse
I really appreciate your help. I just bought a xoom so I want wireless tethering working on my evo.
So you're good to go now?
blackroseMD1...I just followed your instructions and I'm up and running on CM7. Wow its so different then what I had before. You are the man!!! Thanks a lot for your help and everyone elses input in this thread.
I was scared going in, but wow was it easy to do. Thanks again to everyone and the hard work you put in to provide us noobs with a great experience
nawaf88 said:
blackroseMD1...I just followed your instructions and I'm up and running on CM7. Wow its so different then what I had before. You are the man!!! Thanks a lot for your help and everyone elses input in this thread.
I was scared going in, but wow was it easy to do. Thanks again to everyone and the hard work you put in to provide us noobs with a great experience
Click to expand...
Click to collapse
Awesome! Glad to hear it man. Everyone should take an AOSP rom out for a spin at least once, and CM7 is the best one out there. If you have any questions about it, feel free to hit me up. Glad I could help.
blackroseMD1 said:
Awesome! Glad to hear it man. Everyone should take an AOSP rom out for a spin at least once, and CM7 is the best one out there. If you have any questions about it, feel free to hit me up. Glad I could help.
Click to expand...
Click to collapse
Yea it looks great and loving the change so far
One last question. Is there a tethering app built into CM7 or do I need to get wireless tether from the marketplace?
Edit...Nevermind I think I found it right underneath bluetooth settings
nawaf88 said:
Yea it looks great and loving the change so far
One last question. Is there a tethering app built into CM7 or do I need to get wireless tether from the marketplace?
Edit...Nevermind I think I found it right underneath bluetooth settings
Click to expand...
Click to collapse
Yeah, built in tethering works fine. Seems like you found it. Enjoy Gingerbread.
Many recommend wiping data/factory reset (which I know was suggested and you've done), but also cache and dalvik BEFORE flashing any new ROM. Also, with CM, is it not suggested that you use Format_All?
totalanonymity said:
Many recommend wiping data/factory reset (which I know was suggested and you've done), but also cache and dalvik BEFORE flashing any new ROM. Also, with CM, is it not suggested that you use Format_All?
Click to expand...
Click to collapse
I only started using Format All recently, and never had any trouble before that with just a factory reset. Different phones react differently though...
another question is voicemail is not working. I get a text message saying Android has sent younansprint voice message and to call a number. Then it has this long string of letters and numbers. So how do inset this up
nawaf88 said:
another question is voicemail is not working. I get a text message saying Android has sent younansprint voice message and to call a number. Then it has this long string of letters and numbers. So how do inset this up
Click to expand...
Click to collapse
Your best bet is to use YouMail, which is free in the market. It's a lot like Sprint's Visual VoiceMail that you have on Sense roms, but with more features. I use it, and I love it.
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
Hello,
I am considering updating my gingerbread based ROM on my old EVO 4g (I am currently running Cyanogen mod 7.1)...
Its been a very long time since I've flashed a ROM to my phone, but I have been wanting to upgrade to an ICS/JB ROM for a while because (amongst other things) I hear that these android 4.0 ROMs are better when it comes to battery life.. As you can probably tell, I am not one of these folks that re-flashes their rom every week so I may be a bit rusty with this and I am a little bit intimidated. While I would like to try something new I also am a bit worried that my lack of experience may cause me to make a mis-step and mess up my phone..
The ROM I am looking at right now is the new release of MotoBlur'd, found here: .. I understand that this ROM is based on CyanogenMod 10, and since it seems I cannot get a version of the raw CM10 directly to install on my phone, perhaps MotoBlur'd is the next best thing...
But before I open up this can of worms and go off and wipe my phone and flash this new rom, I had 3 questions which I hope someone with experience can answer
1) All other things being equal, would this actually help with the battery life, over the Gingerbread based CM 7.1?
2) Is it still the case that Netflix and other video viewing apps do not work with this (or any other ICS/JB) ROM?? They mention it in the android dev thread, but no one has confirmed that these things work or not work.
3) Do I have to peroform any extra steps or install anything else (other than what is shown in the instructions) to move the phone from CM 7.1 to the latest Motoblur'd ?? For example do I need to install an ICS based ROM first before JB? Or can I just flash directly to this ROM??
Hopefully I can do this without causing too much damage or requiring too much help from the users in this forum... Of course any advice or suggestions anyone can give me would help...
Thanks
TPK2013
For number 3 just make sure your using the smelkus 4.3 recovery and for sure wipe the sd-ext to make sure you get a clean flash..
Sent from my PC36100 using xda app-developers app
hondafreak513 said:
For number 3 just make sure your using the smelkus 4.3 recovery and for sure wipe the sd-ext to make sure you get a clean flash..
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
1. battery life will be worse. most likely
2. That is stil lthe case
3. Read the Guide in my signature (Evo Superguide). It'll help you a lot
HipKat said:
1. battery life will be worse. most likely
2. That is stil lthe case
3. Read the Guide in my signature (Evo Superguide). It'll help you a lot
Click to expand...
Click to collapse
Excellent guide, Hipcat... I think this will really be helpful to me... As someone who doesn't do this all the time, it can really help to have a guide like that to cover all the bases.. I know we are supposed to try to search for the stuff that we need to know, but sometimes its hard to know even what we need to know, and sometimes the multitudes of information we find is contradictory or out of date, so this really helps..
I found a broken link on it, so I posted that as a reply in your thread (I hope thats okay)...
I think I may just stick with my GB based rom, as much as I would like to monkey around with ICS or JB.. I guess I don't see the sense of switching if it won't help my battery life and if it will prohibit the use of video playing apps (which, I know, suck a lot of battery)..
The biggest problem for me is the battery life (I found several contradictory explainations on how to calibrate the battery, I will try the one found in your guide next), but mainly I believe my problem is that I have too much garbage loaded on the phone (not reloading after a year and a half can do that), and a lot of stuff loads in the background so that is probably affecting my battery life.. Also I don't think I am using the most up-to-date radio, which is probably causing the most battery drain of all... So I am going to try the following...
1) I am going to (actually I already have) upgrade my radio to 2.15.00.01.15
2) As per your, and honda's suggestion I will try to update my recovery to smelkus 4.3 (I think I am using clockwork recovery right now, although I am not sure if that is the same thing or not)..
3) I will try to re-format and re-partition my SD card and attempt to install A2SD so I can have more room for apps (can I use A2SD with CM 7?)
4) I will wipe everything, and reload to CyanogenMod 7.2 (perhaps this will work better than 7.1) and reload about half the apps I have on there now (only the stuff I am using now)..
If battery life is my main concern, is there a better ROM I should be using??? I picked CM in the first place because it was an AOSP (no frills, no extra garbage) ROM, however I haven't been able to update my PRL (havent ever updated it, probably)...
Thanks again for your response... You and your guide have been quite helpful...
TPK2013
TPK2013 said:
Excellent guide, Hipcat... I think this will really be helpful to me... As someone who doesn't do this all the time, it can really help to have a guide like that to cover all the bases.. I know we are supposed to try to search for the stuff that we need to know, but sometimes its hard to know even what we need to know, and sometimes the multitudes of information we find is contradictory or out of date, so this really helps..
I found a broken link on it, so I posted that as a reply in your thread (I hope thats okay)...
I think I may just stick with my GB based rom, as much as I would like to monkey around with ICS or JB.. I guess I don't see the sense of switching if it won't help my battery life and if it will prohibit the use of video playing apps (which, I know, suck a lot of battery)..
The biggest problem for me is the battery life (I found several contradictory explainations on how to calibrate the battery, I will try the one found in your guide next), but mainly I believe my problem is that I have too much garbage loaded on the phone (not reloading after a year and a half can do that), and a lot of stuff loads in the background so that is probably affecting my battery life.. Also I don't think I am using the most up-to-date radio, which is probably causing the most battery drain of all... So I am going to try the following...
1) I am going to (actually I already have) upgrade my radio to 2.15.00.01.15
2) As per your, and honda's suggestion I will try to update my recovery to smelkus 4.3 (I think I am using clockwork recovery right now, although I am not sure if that is the same thing or not)..
3) I will try to re-format and re-partition my SD card and attempt to install A2SD so I can have more room for apps (can I use A2SD with CM 7?)
4) I will wipe everything, and reload to CyanogenMod 7.2 (perhaps this will work better than 7.1) and reload about half the apps I have on there now (only the stuff I am using now)..
If battery life is my main concern, is there a better ROM I should be using??? I picked CM in the first place because it was an AOSP (no frills, no extra garbage) ROM, however I haven't been able to update my PRL (havent ever updated it, probably)...
Thanks again for your response... You and your guide have been quite helpful...
TPK2013
Click to expand...
Click to collapse
Yep, I fixed that link and what you said is why I wrote that guide; because searching can be a real pain in the @ss sometimes. It's like a teacher telling you to look up a word you can't spell. Well how do you search for an answer if you're not really sure of the question?? lol
You cant update your PRL on any non-stock rom. It has to be stock for you to be able to do that
Well if battery life is your main concern I always suggest a good sense 3.0 ROM. If you are worried about bloat that can be removed. If you want I can hook you up with a rom/kernel combo with everything you want.
When I am not testing or making a new rom I use sense 3.0 and can get 8 hrs of heavy use on stock battery. Thats netflix with 3-4 hrs use plus web surfing and calls during the rest. On my extended battery with light use I can get 4+ days.
If you would like to try my rom pm me before you partion your sdcard. There are certain things you need to do for it to work right.
Sent from my PC36100 using xda app-developers app
CNexus said:
You cant update your PRL on any non-stock rom. It has to be stock for you to be able to do that
Click to expand...
Click to collapse
Perhaps I will go to stock and try to update the PRL before I go ahead and update the ROM to custom... However, this Evo is on Boost Mobile (not Sprint) network, so I am not sure how to appropriately update the PRL... Should I just update it as if it were a regular Sprint Evo 4g or does it matter?
CNexus said:
You cant update your PRL on any non-stock rom. It has to be stock for you to be able to do that
Click to expand...
Click to collapse
Umm updating prl only requires the *228 call from the phone and it works on any rom. Now to put a custom or older prl it takes a bit more. Updating your profile now that I do believe you have to be on a Sprint rom but I don't have Sprint so I can't say for sure.
Sent from my PC36100 using xda app-developers app
jlmancuso said:
Umm updating prl only requires the *228 call from the phone and it works on any rom. Now to put a custom or older prl it takes a bit more. Updating your profile now that I do believe you have to be on a Sprint rom but I don't have Sprint so I can't say for sure.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Never heard of that *228, so cant say anything about that
Updating profile and prl I've always seen and heard can only be done on stock, unless you use this ##codes apps I saw somewhere....
The ## codes only work on the sprint roms. To change prls on AOSP roms you need a windows pc with qpst setup and prl files on the pc. Then you have to enable diagnostic mode through adb or a terminal emulator. There is a thread here on our EVO forum to do it. I will bump it so you can check it out. It sure beats all the backing up and restoring to do it.
Edit: I bumped it. It is in the dev section.
jlmancuso said:
The ## codes only work on the sprint roms. To change prls on AOSP roms you need a windows pc with qpst setup and prl files on the pc. Then you have to enable diagnostic mode through adb or a terminal emulator. There is a thread here on our EVO forum to do it. I will bump it so you can check it out. It sure beats all the backing up and restoring to do it.
Edit: I bumped it. It is in the dev section.
Click to expand...
Click to collapse
Yeah. Theres an app that uses scripts to emulate the ##code functions.
Really? I can't believe I have not heard of that till now. Do you know what it is called? I would love to check it out.
Sent from my PC36100 using xda app-developers app
jlmancuso said:
The ## codes only work on the sprint roms. To change prls on AOSP roms you need a windows pc with qpst setup and prl files on the pc. Then you have to enable diagnostic mode through adb or a terminal emulator. There is a thread here on our EVO forum to do it. I will bump it so you can check it out. It sure beats all the backing up and restoring to do it.
Edit: I bumped it. It is in the dev section.
Click to expand...
Click to collapse
Found the thread, thanks!!
Now I just have to figure out which PRL file to use for my Evo on Boost, and where to find it (I think this is what stopped me from updating the PRL before, not knowing if I should use a sprint PRL or something else)...
Edit: I did find this thread regarding boost PRLs on EVO
And if there is indeed an app that emulates the ## commands, I would like to know what that is...
... TPK2013
Heck if your on boost you need a boost prl. You can Google boost prls and find dozens of them. I would suggest using the latest one. Just dial *228 and it will update your prl. After it finishes reboot your phone. It is really that simple. I do it on my cricket flashed EVO but it works for every service provider.
Sent from my PC36100 using xda app-developers app
I just bought one! and love CM since the release of my first android phone, the Samsung Galaxy S2
There are only custom roms for the 8.4 and the 10.1 version.
There are no custom ROMs available for this device now, and i hate the slurpy/fancy samsung interface.
I am willing to pay for it, for the first nice and clean nightly CM 11 rom + CWM/TWRP recovery and working Gapps for this device.
This device is out for a while now and there are still no custom roms for.
So i hope there is somebody who can help, to get the custom roms madness for this device getting started.
I got you covered.
I can make a stock custom rom which has all the samsung junk removed so the tablet can go faster.
I want a rooted aosp rom, like cyanogenmod or something.
Are you able to do that?
ExoRRSmits said:
I want a rooted aosp rom, like cyanogenmod or something.
Are you able to do that?
Click to expand...
Click to collapse
Unfortunately, I can't. (I have a 10.1 and I want the same thing). The thing is the processor is a exynos 5 or something like that and it is (as I have read and understood) quite hard to do. I've tried to learn about making it but trust me it is much more harder than it seems. Even my 10.1 doesn't have CM yet. Still if you like I can make a you a stock debloated rom so it will at least run faster than what you have now.
ik4evr2 said:
I got you covered.
I can make a stock custom rom which has all the samsung junk removed so the tablet can go faster.
Click to expand...
Click to collapse
I am very much interested in this thanks!
nickster1 said:
I am very much interested in this thanks!
Click to expand...
Click to collapse
No problem at all. It will take me a day or two.
ik4evr2 said:
No problem at all. It will take me a day or two.
Click to expand...
Click to collapse
Can you make deodex please? I already have the stock debloate, but would be nice to have deodexed rom.
ik4evr2 said:
Unfortunately, I can't. (I have a 10.1 and I want the same thing). The thing is the processor is a exynos 5 or something like that and it is (as I have read and understood) quite hard to do. I've tried to learn about making it but trust me it is much more harder than it seems. Even my 10.1 doesn't have CM yet. Still if you like I can make a you a stock debloated rom so it will at least run faster than what you have now.
Click to expand...
Click to collapse
Well for now it sounds ok to me.
Is it rooted as well?
How debloated is it? Is samsung touchwiz removed?
That's what i'm hating the most. The settings app with tabs, i like the whole settings menu in cm.
And how fast can it see the light?
If its very nice, i can donate something for your good and hard work.
There might be a debloated deodexed rom already here?: http://forum.xda-developers.com/showthread.php?t=2776206
Ludespeed said:
There might be a debloated deodexed rom already here?: http://forum.xda-developers.com/showthread.php?t=2776206
Click to expand...
Click to collapse
No, I tried it, and unfortunately it doesn't work for the 12.2 version. The internal, as well as the external sd card both are locked, meaning you can't even update any apps, or saving any data... you get an error message 110, from Play Store.
ik4evr2 said:
No problem at all. It will take me a day or two.
Click to expand...
Click to collapse
Any luck ?
ExoRRSmits said:
Any luck ?
Click to expand...
Click to collapse
+1!
What about an overclock kernel? I debloated my Galaxy tab 12.2 already but have yet to successfully overclock it. I've been looking everywhere for an improved kernel or something to improve the performance, debloating didn't help it that much so a kernel or custom rom would be the next bet. Anyone point me in the right direction?
In school atm, but had a few mins so I built this: https://drive.google.com/file/d/0B5kaDFDMK0TYci14Nm1EOFFnX2s/edit?usp=sharing
Can't reply to any question atm but will when I get home. Not sure if it will boot.
Download, advance wipe in TWRP (except internal/external storage) and see if it boots to CM. Then post what's working and what's not
Enjoy if it works!
Gotta go
Shaheer said:
In school atm, but had a few mins so I built this: https://drive.google.com/file/d/0B5kaDFDMK0TYci14Nm1EOFFnX2s/edit?usp=sharing
Can't reply to any question atm but will when I get home. Not sure if it will boot.
Download, advance wipe in TWRP (except internal/external storage) and see if it boots to CM. Then post what's working and what's not
Enjoy if it works!
Gotta go
Click to expand...
Click to collapse
Great initiative,
I tried making an install. Unfortunately everything halts at the cm welcome screen with the message "Unfortunately, the process com.android.phone has stopped", Maybe, I'm not too surprised since we're using a wifi-version. But, it actually boots up, so there are great expectations for a cm11 port, within short.
Thanks for all your efforts.
arcadia2uk said:
Great initiative,
I tried making an install. Unfortunately everything halts at the cm welcome screen with the message "Unfortunately, the process com.android.phone has stopped", Maybe, I'm not too surprised since we're using a wifi-version. But, it actually boots up, so there are great expectations for a cm11 port, within short.
Thanks for all your efforts.
Click to expand...
Click to collapse
Hey everyone,
So here is an update: (At school so don't have much time but...) This should fix the phone error. :good: However, I am pretty sure Wi-Fi isn't going to work ATM. Since i'm at school can't download things internet is tooo slow, so what someone can do if they want is to download a touchwiz rom for your device or just plain stock rom. Then, on the download go to /system/etc and there should be a folder called Wi-Fi. Copy that to system/etc in the CM rom. And then flash the CM Rom. If Wi-Fi works go ahead and upload the link and post it here.
Download: https://drive.google.com/file/d/0B5kaDFDMK0TYRmNGUVUxVDloeWc/edit?usp=sharing
Shaheer said:
Hey everyone,
So here is an update: (At school so don't have much time but...) This should fix the phone error. :good: However, I am pretty sure Wi-Fi isn't going to work ATM. Since i'm at school can't download things internet is tooo slow, so what someone can do if they want is to download a touchwiz rom for your device or just plain stock rom. Then, on the download go to /system/etc and there should be a folder called Wi-Fi. Copy that to system/etc in the CM rom. And then flash the CM Rom. If Wi-Fi works go ahead and upload the link and post it here.
Download: https://drive.google.com/file/d/0B5kaDFDMK0TYRmNGUVUxVDloeWc/edit?usp=sharing
Click to expand...
Click to collapse
Just as you suspected the wifi didn't work initially. However, I followed your instructions for the update, and there it was. Here's the link to the updated cm11-4.4.4 w. wifi Currently, there seems to be no access to the internal SD card, as well as the external.
I also have difficulties in finding a compatible gapps, any ideas? Could it be due to the SD card issue? It starts up, but playstore crashes at first search.
arcadia2uk said:
Just as you suspected the wifi didn't work initially. However, I followed your instructions for the update, and there it was. Here's the link to the updated cm11-4.4.4 w. wifi Currently, there seems to be no access to the internal SD card, as well as the external.
I also have difficulties in finding a compatible gapps, any ideas? Could it be due to the SD card issue? It starts up, but playstore crashes at first search.
Click to expand...
Click to collapse
Will post an answer in a while. Leaving school in a min so I was just checking the thread. :fingers-crossed:
After homework and all that i'll upload the updated file when I get a chance to work on it.
Shaheer said:
Will post an answer in a while. Leaving school in a min so I was just checking the thread. :fingers-crossed:
After homework and all that i'll upload the updated file when I get a chance to work on it.
Click to expand...
Click to collapse
Great start Shaheer, apparently I'm running into a lot of the same problems that you initially ran into building the T-520 port.
Could I suggest that you start a thread in the development section for this ROM? I believe that I'm one of the few people having noticed your work, and that's only due to your message. Then we can get a few more people to chip in for heavy testing, at least the initial runs.
It would be good if the gapps along with the SDcard and PC-mount issues could have priority. Once they're up you can at least flash back and forth from the same ROM, without passing through an intermediary stock ROM. Notably, as each flash takes close to 30 min, if not more...However, I can believe they are all the result of the fact that the ROM can't detect the internal SDcard; no card = no mount, no card = no play store download.
On the good side, it seems like the GPS is working, and the bluetooth discovers surrounding devices and besides the mentioned SDcard issue, I have not seen much missing at least mot that can be tested at this point. There's no camera, but that seems to be something most AOSP ROM's for the Samsung tablets are struggling with currently.
Anyway, thanks again, I really appreciate your efforts.
arcadia2uk said:
Great start Shaheer, apparently I'm running into a lot of the same problems that you initially ran into building the T-520 port.
Could I suggest that you start a thread in the development section for this ROM? I believe that I'm one of the few people having noticed your work, and that's only due to your message. Then we can get a few more people to chip in for heavy testing, at least the initial runs.
It would be good if the gapps along with the SDcard and PC-mount issues could have priority. Once they're up you can at least flash back and forth from the same ROM, without passing through an intermediary stock ROM. Notably, as each flash takes close to 30 min, if not more...However, I can believe they are all the result of the fact that the ROM can't detect the internal SDcard; no card = no mount, no card = no play store download.
On the good side, it seems like the GPS is working, and the bluetooth discovers surrounding devices and besides the mentioned SDcard issue, I have not seen much missing at least mot that can be tested at this point. There's no camera, but that seems to be something most AOSP ROM's for the Samsung tablets are struggling with currently.
Anyway, thanks again, I really appreciate your efforts.
Click to expand...
Click to collapse
Hey!,
So I was really busy yesterday evening writing a 3 page essay and doing other homework so I didn't get anytime to work on the rom. My thoughts too were to start a new thread in the dev section for this.
I haven't gotten too far with the T520 port either as i'm still learning CM development. (I'm more used to touchwiz ) I have some time right now so give me a bit and i'll try to get a thread started and update the rom to get SD Card working.
EDIT: Actually, I can't proceed till someone can make sure that Google Play downloads app properly. If it doesn't then I need to work on that before anything or it's going to cause major issues.
1st let me just say I'm not a developer at all just someone who enjoys custom roms as much as everyone else here! I'm not very good at explaining things so please try to bear with me and try to understand this the best you can! If any real developers read this please help us by adding support for our device and if any developers can explain this better please do so! For anyone with the d2lterefreshspr (SPH-L710T Tri-Band) wanting to flash almost any Lollipop Roms made for the d2spr you can flash them! You might 1st have to unzip the rom and go to the updater-script and delete the 1st part where it checks the recoveries build to see if your device is the d2spr or the d2lte and so on. Then repack the rom back into a zip file the flash it in recovery as you normally would. Then once the Rom boots you won't have a baseband or service or anything but I will tell you why and how to fix this. The d2spr's modem-image file are labeled different from our modem! At the bottom of this I will show you the list of each modems links so you can see which 1s are different and what you have to delete and resymlink to get the Rom to reconize your baseband and get your service working! But using a file manager with root access navigate to the files in "/system/etc/firmware/ " and delete the wrongly symlinked modem-images! Once you have done that navigate to "/firmware-mdm/images/" folder and start symlinking the correct files to "/system/etc/firmware/" folder. After this you might want to modify the buid.prop and change all parts that say d2spr to d2lterefreshspr but only if you want. Once you have done this reboot to recovery and flash the Lte apn fix zip then reboot. Now everything should work with service and everything! I have tried this on the latest SlimLP 5.1.1. Beta and A..I.C.P. Lollipop and a few other Lollipop Roms for the d2spr. If you would like to download some of the Roms I have modified the updater-scripts so they will flash on our device and the APN zip I flash with a flashable build.prop I have already modified just send me a message and I will send you a link to my drive account. I'm trying to create a zip we can flash in recovery that will delete the wrong symilinked files and symlink the correct files to help save us the trouble of this process and for people that don't know how to create a symlink file! But as I stated I'm not a developer so I might be able to but if any developers that could help us by creating 1 for us please please feel free to do so and let us know! But take a look at the 2 lists of symlinked files and delete the necessary files and create the new symlinks that our device needs! If the files show the correct symlinks on 1st boot but you still don't have service click on the symlinks and view its details and you will see it'ssymlinked to the wrong files. Just delete all symlinks and create the correct new 1s.
Example of the d2spr modem symlinked images are:
symlink("/firmware-mdm/image/dsps.b00", "/system/etc/firmware/dsps.b00");
symlink("/firmware-mdm/image/dsps.b01", "/system/etc/firmware/dsps.b01");
symlink("/firmware-mdm/image/dsps.b02", "/system/etc/firmware/dsps.b02");
symlink("/firmware-mdm/image/dsps.b03", "/system/etc/firmware/dsps.b03");
symlink("/firmware-mdm/image/dsps.b04", "/system/etc/firmware/dsps.b04");
symlink("/firmware-mdm/image/dsps.b05", "/system/etc/firmware/dsps.b05");
symlink("/firmware-mdm/image/dsps.mdt", "/system/etc/firmware/dsps.mdt");
symlink("/firmware-mdm/image/modem.b00", "/system/etc/firmware/modem.b00");
symlink("/firmware-mdm/image/modem.b01", "/system/etc/firmware/modem.b01");
symlink("/firmware-mdm/image/modem.b02", "/system/etc/firmware/modem.b02");
symlink("/firmware-mdm/image/modem.b03", "/system/etc/firmware/modem.b03");
symlink("/firmware-mdm/image/modem.b04", "/system/etc/firmware/modem.b04");
symlink("/firmware-mdm/image/modem.b05", "/system/etc/firmware/modem.b05");
symlink("/firmware-mdm/image/modem.b06", "/system/etc/firmware/modem.b06");
symlink("/firmware-mdm/image/modem.b07", "/system/etc/firmware/modem.b07");
symlink("/firmware-mdm/image/modem.mdt", "/system/etc/firmware/modem.mdt");
symlink("/firmware-mdm/image/modem_f2.b00", "/system/etc/firmware/modem_fw.b00");
symlink("/firmware-mdm/image/modem_f2.b01", "/system/etc/firmware/modem_fw.b01");
symlink("/firmware-mdm/image/modem_f2.b02", "/system/etc/firmware/modem_fw.b02");
symlink("/firmware-mdm/image/modem_f2.b03", "/system/etc/firmware/modem_fw.b03");
symlink("/firmware-mdm/image/modem_f2.b04", "/system/etc/firmware/modem_fw.b04");
symlink("/firmware-mdm/image/modem_f2.b05", "/system/etc/firmware/modem_fw.b05");
symlink("/firmware-mdm/image/modem_f2.b06", "/system/etc/firmware/modem_fw.b06");
symlink("/firmware-mdm/image/modem_f2.b07", "/system/etc/firmware/modem_fw.b07");
symlink("/firmware-mdm/image/modem_f2.b08", "/system/etc/firmware/modem_fw.b08");
symlink("/firmware-mdm/image/modem_f2.b09", "/system/etc/firmware/modem_fw.b09");
symlink("/firmware-mdm/image/modem_f2.b10", "/system/etc/firmware/modem_fw.b10");
symlink("/firmware-mdm/image/modem_f2.b13", "/system/etc/firmware/modem_fw.b13");
symlink("/firmware-mdm/image/modem_f2.b14", "/system/etc/firmware/modem_fw.b14");
symlink("/firmware-mdm/image/modem_f2.b21", "/system/etc/firmware/modem_fw.b21");
symlink("/firmware-mdm/image/modem_f2.b22", "/system/etc/firmware/modem_fw.b22");
symlink("/firmware-mdm/image/modem_f2.b23", "/system/etc/firmware/modem_fw.b23");
symlink("/firmware-mdm/image/modem_f2.b25", "/system/etc/firmware/modem_fw.b25");
symlink("/firmware-mdm/image/modem_f2.b26", "/system/etc/firmware/modem_fw.b26");
symlink("/firmware-mdm/image/modem_f2.b29", "/system/etc/firmware/modem_fw.b29");
symlink("/firmware-mdm/image/modem_f2.mdt", "/system/etc/firmware/modem_fw.mdt");
symlink("/firmware-mdm/image/q6.b00", "/system/etc/firmware/q6.b00");
symlink("/firmware-mdm/image/q6.b01", "/system/etc/firmware/q6.b01");
symlink("/firmware-mdm/image/q6.b03", "/system/etc/firmware/q6.b03");
symlink("/firmware-mdm/image/q6.b04", "/system/etc/firmware/q6.b04");
symlink("/firmware-mdm/image/q6.b05", "/system/etc/firmware/q6.b05");
symlink("/firmware-mdm/image/q6.b06", "/system/etc/firmware/q6.b06");
symlink("/firmware-mdm/image/q6.mdt", "/system/etc/firmware/q6.mdt");
symlink("/firmware-mdm/image/tzapps.b00", "/system/etc/firmware/tzapps.b00");
symlink("/firmware-mdm/image/tzapps.b01", "/system/etc/firmware/tzapps.b01");
symlink("/firmware-mdm/image/tzapps.b02", "/system/etc/firmware/tzapps.b02");
symlink("/firmware-mdm/image/tzapps.b03", "/system/etc/firmware/tzapps.b03");
symlink("/firmware-mdm/image/tzapps.mdt", "/system/etc/firmware/tzapps.mdt");
symlink("/firmware-mdm/image/vidc.b00", "/system/etc/firmware/vidc.b00");
symlink("/firmware-mdm/image/vidc.b01", "/system/etc/firmware/vidc.b01");
symlink("/firmware-mdm/image/vidc.b02", "/system/etc/firmware/vidc.b02");
symlink("/firmware-mdm/image/vidc.b03", "/system/etc/firmware/vidc.b03");
symlink("/firmware-mdm/image/vidc.mdt", "/system/etc/firmware/vidc.mdt");
The correct modem images you need to symlink for the d2lterefreshspr are:
symlink("/firmware-mdm/image/dsps.b00", "/system/etc/firmware/dsps.b00");
symlink("/firmware-mdm/image/dsps.b01", "/system/etc/firmware/dsps.b01");
symlink("/firmware-mdm/image/dsps.b02", "/system/etc/firmware/dsps.b02");
symlink("/firmware-mdm/image/dsps.b03", "/system/etc/firmware/dsps.b03");
symlink("/firmware-mdm/image/dsps.b04", "/system/etc/firmware/dsps.b04");
symlink("/firmware-mdm/image/dsps.b05", "/system/etc/firmware/dsps.b05");
symlink("/firmware-mdm/image/dsps.mdt", "/system/etc/firmware/dsps.mdt");
symlink("/firmware-mdm/image/modem.b00", "/system/etc/firmware/modem.b00");
symlink("/firmware-mdm/image/modem.b01", "/system/etc/firmware/modem.b01");
symlink("/firmware-mdm/image/modem.b02", "/system/etc/firmware/modem.b02");
symlink("/firmware-mdm/image/modem.b03", "/system/etc/firmware/modem.b03");
symlink("/firmware-mdm/image/modem.b04", "/system/etc/firmware/modem.b04");
symlink("/firmware-mdm/image/modem.b06", "/system/etc/firmware/modem.b06");
symlink("/firmware-mdm/image/modem.b07", "/system/etc/firmware/modem.b07");
symlink("/firmware-mdm/image/modem.b08", "/system/etc/firmware/modem.b08");
symlink("/firmware-mdm/image/modem.b09", "/system/etc/firmware/modem.b09");
symlink("/firmware-mdm/image/modem.b10", "/system/etc/firmware/modem.b10");
symlink("/firmware-mdm/image/modem.mdt", "/system/etc/firmware/modem.mdt");
symlink("/firmware-mdm/image/modem_fw.b00", "/system/etc/firmware/modem_fw.b00");
symlink("/firmware-mdm/image/modem_fw.b01", "/system/etc/firmware/modem_fw.b01");
symlink("/firmware-mdm/image/modem_fw.b02", "/system/etc/firmware/modem_fw.b02");
symlink("/firmware-mdm/image/modem_fw.b03", "/system/etc/firmware/modem_fw.b03");
symlink("/firmware-mdm/image/modem_fw.b04", "/system/etc/firmware/modem_fw.b04");
symlink("/firmware-mdm/image/modem_fw.b05", "/system/etc/firmware/modem_fw.b05");
symlink("/firmware-mdm/image/modem_fw.b09", "/system/etc/firmware/modem_fw.b09");
symlink("/firmware-mdm/image/modem_fw.b10", "/system/etc/firmware/modem_fw.b10");
symlink("/firmware-mdm/image/modem_fw.b11", "/system/etc/firmware/modem_fw.b11");
symlink("/firmware-mdm/image/modem_fw.b12", "/system/etc/firmware/modem_fw.b12");
symlink("/firmware-mdm/image/modem_fw.b13", "/system/etc/firmware/modem_fw.b13");
symlink("/firmware-mdm/image/modem_fw.b15", "/system/etc/firmware/modem_fw.b15");
symlink("/firmware-mdm/image/modem_fw.b16", "/system/etc/firmware/modem_fw.b16");
symlink("/firmware-mdm/image/modem_fw.b17", "/system/etc/firmware/modem_fw.b17");
symlink("/firmware-mdm/image/modem_fw.b18", "/system/etc/firmware/modem_fw.b18");
symlink("/firmware-mdm/image/modem_fw.b23", "/system/etc/firmware/modem_fw.b23");
symlink("/firmware-mdm/image/modem_fw.b24", "/system/etc/firmware/modem_fw.b24");
symlink("/firmware-mdm/image/modem_fw.b25", "/system/etc/firmware/modem_fw.b25");
symlink("/firmware-mdm/image/modem_fw.b27", "/system/etc/firmware/modem_fw.b27");
symlink("/firmware-mdm/image/modem_fw.b28", "/system/etc/firmware/modem_fw.b28");
symlink("/firmware-mdm/image/modem_fw.b31", "/system/etc/firmware/modem_fw.b31");
symlink("/firmware-mdm/image/modem_fw.fli", "/system/etc/firmware/modem_fw.fli");
symlink("/firmware-mdm/image/modem_fw.mdt", "/system/etc/firmware/modem_fw.mdt");
symlink("/firmware-mdm/image/q6.b00", "/system/etc/firmware/q6.b00");
symlink("/firmware-mdm/image/q6.b01", "/system/etc/firmware/q6.b01");
symlink("/firmware-mdm/image/q6.b03", "/system/etc/firmware/q6.b03");
symlink("/firmware-mdm/image/q6.b04", "/system/etc/firmware/q6.b04");
symlink("/firmware-mdm/image/q6.b05", "/system/etc/firmware/q6.b05");
symlink("/firmware-mdm/image/q6.b06", "/system/etc/firmware/q6.b06");
symlink("/firmware-mdm/image/q6.mdt", "/system/etc/firmware/q6.mdt");
symlink("/firmware-mdm/image/tima_key.b00", "/system/etc/firmware/tima_key.b00");
symlink("/firmware-mdm/image/tima_key.b01", "/system/etc/firmware/tima_key.b01");
symlink("/firmware-mdm/image/tima_key.b02", "/system/etc/firmware/tima_key.b02");
symlink("/firmware-mdm/image/tima_key.b03", "/system/etc/firmware/tima_key.b03");
symlink("/firmware-mdm/image/tima_key.mdt", "/system/etc/firmware/tima_key.mdt");
symlink("/firmware-mdm/image/tima_lkm.b00", "/system/etc/firmware/tima_lkm.b00");
symlink("/firmware-mdm/image/tima_lkm.b01", "/system/etc/firmware/tima_lkm.b01");
symlink("/firmware-mdm/image/tima_lkm.b02", "/system/etc/firmware/tima_lkm.b02");
symlink("/firmware-mdm/image/tima_lkm.b03", "/system/etc/firmware/tima_lkm.b03");
symlink("/firmware-mdm/image/tima_lkm.mdt", "/system/etc/firmware/tima_lkm.mdt");
symlink("/firmware-mdm/image/tima_pkm.b00", "/system/etc/firmware/tima_pkm.b00");
symlink("/firmware-mdm/image/tima_pkm.b01", "/system/etc/firmware/tima_pkm.b01");
symlink("/firmware-mdm/image/tima_pkm.b02", "/system/etc/firmware/tima_pkm.b02");
symlink("/firmware-mdm/image/tima_pkm.b03", "/system/etc/firmware/tima_pkm.b03");
symlink("/firmware-mdm/image/tima_pkm.mdt", "/system/etc/firmware/tima_pkm.mdt");
symlink("/firmware-mdm/image/tzapps.b00", "/system/etc/firmware/tzapps.b00");
symlink("/firmware-mdm/image/tzapps.b01", "/system/etc/firmware/tzapps.b01");
symlink("/firmware-mdm/image/tzapps.b02", "/system/etc/firmware/tzapps.b02");
symlink("/firmware-mdm/image/tzapps.b03", "/system/etc/firmware/tzapps.b03");
symlink("/firmware-mdm/image/tzapps.mdt", "/system/etc/firmware/tzapps.mdt");
symlink("/firmware-mdm/image/vidc.b00", "/system/etc/firmware/vidc.b00");
symlink("/firmware-mdm/image/vidc.b01", "/system/etc/firmware/vidc.b01");
symlink("/firmware-mdm/image/vidc.b02", "/system/etc/firmware/vidc.b02");
symlink("/firmware-mdm/image/vidc.b03", "/system/etc/firmware/vidc.b03");
symlink("/firmware-mdm/image/vidc.mdt", "/system/etc/firmware/vidc.mdt");
symlink("/firmware-mdm/image/wcnss.b00", "/system/etc/firmware/wcnss.b00");
symlink("/firmware-mdm/image/wcnss.b01", "/system/etc/firmware/wcnss.b01");
symlink("/firmware-mdm/image/wcnss.b02", "/system/etc/firmware/wcnss.b02");
symlink("/firmware-mdm/image/wcnss.b04", "/system/etc/firmware/wcnss.b04");
symlink("/firmware-mdm/image/wcnss.mdt", "/system/etc/firmware/wcnss.mdt");
For anyone unsure about creating the symlinks I have a very simple zip file to flash in recovery to delete the bad symlinks and make the right 1s! I have tested on SlimLP, A.I.C.P., Exodusand Pac-Man d2spr Roms. It will not mess up anything on your S3! It only does as stated. If you wanna check it its all in the script-updater. Just flash this after flashing a d2spr Lollipop rom and if you are also confused on modifying the script-updater for the rom so it will flash on the d2lterefreshspr then just flash the TWRP 2.8.7.0 recovery from TWRP's website and you wont have to worry about changing it!
Fixing Modem Symlinks For SPH-L710T.zip
https://drive.google.com/file/d/0B-Zg_yh4ytvLaS1xSzZ3bWhuTVk/view?usp=docslist_api
Hey man this is great! This opens up a whole new world of wonders for this device. You have any idea how I can fix having to manually select apn after each reboot?
triband
RootSuperSU said:
For anyone unsure about creating the symlinks I have a very simple zip file to flash in recovery to delete the bad symlinks and make the right 1s! I have tested on SlimLP, A.I.C.P., Exodusand Pac-Man d2spr Roms. It will not mess up anything on your S3! It only does as stated. If you wanna check it its all in the script-updater. Just flash this after flashing a d2spr Lollipop rom and if you are also confused on modifying the script-updater for the rom so it will flash on the d2lterefreshspr then just flash the TWRP 2.8.7.0 recovery from TWRP's website and you wont have to worry about changing it!
Fixing Modem Symlinks For SPH-L710T.zip
https://drive.google.com/file/d/0B-Zg_yh4ytvLaS1xSzZ3bWhuTVk/view?usp=docslist_api
Click to expand...
Click to collapse
now that i found it, are you going to be around for me to throw questions at. i know what to do but the problems ive had made me leery of flashing.
pgellen said:
now that i found it, are you going to be around for me to throw questions at. i know what to do but the problems ive had made me leery of flashing.
Click to expand...
Click to collapse
Yea man i work til 4-5pm but after that i can try to help ya! My S3 bricked on me and i dont have a 16gb sd to flash the unbrick image to but im always willing to try and help if i can
Sent from my LGLS885 using XDA Labs
rom flashing
RootSuperSU said:
Yea man i work til 4-5pm but after that i can try to help ya! My S3 bricked on me and i dont have a 16gb sd to flash the unbrick image to but im always willing to try and help if i can
Sent from my LGLS885 using XDA Labs
Click to expand...
Click to collapse
well, come to find out flashing octos, made for triband,,,,who knew, not me until today, anyway, its very easy. haha probably easier than ANYTHING i've done up to this point. i dont remember how much i've told you but the triband that i was fighting with so much may have had a problem from the very beginning. getting into recovery continually got harder and harder until it just wouldn't go. i tried about 8 times and it completely died. i mean its dead.im sad for that. that drops me to one sph-l710 with a crumpled usb and so i have to charge it wirelessly which is cool but its fragile. so ive got another refurb triband which im about to flash. WHY? ill be damned if i know why. this phone is rooted and cleaned out and runs beautifully. but, i want more. i guess or im just stupid which by reading this i may be. ill let you know.
triband
pgellen said:
well, come to find out flashing octos, made for triband,,,,who knew, not me until today, anyway, its very easy. haha probably easier than ANYTHING i've done up to this point. i dont remember how much i've told you but the triband that i was fighting with so much may have had a problem from the very beginning. getting into recovery continually got harder and harder until it just wouldn't go. i tried about 8 times and it completely died. i mean its dead.im sad for that. that drops me to one sph-l710 with a crumpled usb and so i have to charge it wirelessly which is cool but its fragile. so ive got another refurb triband which im about to flash. WHY? ill be damned if i know why. this phone is rooted and cleaned out and runs beautifully. but, i want more. i guess or im just stupid which by reading this i may be. ill let you know.
Click to expand...
Click to collapse
tonight if your not busy with other people ill have some questions for you. im looking forward to it. i loaded the rom, gapps and now theupdate has been in a holding cycle for half an hour. it vibrates a little every so often. so i guess ill let it go. i want in so i can finish setting it up. ive got a lot of work to do. i know you must.
Will this zip work for KK roms too? Or is it only Lollipop? I'm willing to test it out but I just want to be sure that I won't brick my S3 since I can't afford a new phone right now.
octos
yakob97 said:
Will this zip work for KK roms too? Or is it only Lollipop? I'm willing to test it out but I just want to be sure that I won't brick my S3 since I can't afford a new phone right now.
Click to expand...
Click to collapse
hey, supersu, help me fix this s3 triband when you get home and you feel like it. i can wait if you need. don't you come from work? let me know however, the biggest problem im having is my bluetooth doesnt work for music. works for everything else,that's a strange one. i'll wait for a reply.
yakob97 said:
Will this zip work for KK roms too? Or is it only Lollipop? I'm willing to test it out but I just want to be sure that I won't brick my S3 since I can't afford a new phone right now.
Click to expand...
Click to collapse
Yes it should work and no flashing it wont brick ur device at all! Nothing is flashed or installed it only deletes the wrong symlinks and creates the correct ones!
Sent from my LGLS885 using XDA Labs
pgellen said:
hey, supersu, help me fix this s3 triband when you get home and you feel like it. i can wait if you need. don't you come from work? let me know however, the biggest problem im having is my bluetooth doesnt work for music. works for everything else,that's a strange one. i'll wait for a reply.
Click to expand...
Click to collapse
Idk how to fix the bluetooth problem! Im not a developer or programmer i just google search alot and read very thoroughly and spend alot of time using FX File Explorer to study my system files! But whats the problem ur having other then bluetooth
Sent from my LGLS885 using XDA Labs
octos
RootSuperSU said:
Idk how to fix the bluetooth problem! Im not a developer or programmer i just google search alot and read very thoroughly and spend alot of time using FX File Explorer to study my system files! But whats the problem ur having other then bluetooth
Sent from my LGLS885 using XDA Labs
Click to expand...
Click to collapse
its about time you showed up again. i thought like these other senior members that once you dealt with the senior citizen with debatable alzheimer's you had fled the country also. hehe man i don't know. on my other triband i had no music at well, no sound at all, none. and i had no cell service. now everything works except the bluetooth on the music. as soon as i boot it up the music locks up. its weird. i was just prepping my phone to go back to stock. i think these tribands are better stock with the bloatware removed and not too much of that. ya, i spend alot of time with my file manager. have you tried total commander? its great. you get it from gizmos freeware. im just getting to know it but i have it on the computer and its pretty good.
pgellen said:
its about time you showed up again. i thought like these other senior members that once you dealt with the senior citizen with debatable alzheimer's you had fled the country also. hehe man i don't know. on my other triband i had no music at well, no sound at all, none. and i had no cell service. now everything works except the bluetooth on the music. as soon as i boot it up the music locks up. its weird. i was just prepping my phone to go back to stock. i think these tribands are better stock with the bloatware removed and not too much of that. ya, i spend alot of time with my file manager. have you tried total commander? its great. you get it from gizmos freeware. im just getting to know it but i have it on the computer and its pretty good.
Click to expand...
Click to collapse
Idk wat to say about that never had that problem! What room are u running? If oct os then ask them about it! I like the Slim Roms and S.O.K.P. the best but thats just me!
Sent from my LGLS885 using XDA Labs
I just flashed the final d2lte CM11 snapshot and your zip file, and it worked! After flashing everything the ROM runs super fast and runs wonderfully! So far as I can tell everything works perfectly. Camera, SMS and MMS, GPS, Mobile Data, and Screen Rotation all work perfectly. My steps for flashing were:
Modify Updater-scripts file to remove device checking
Wipe system, dalvik and cache, and data.
Flash CM11 snapshot
Boot to system
Reboot into recovery and flash Gapps and APN fix (I'm on virgin mobile)
yakob97 said:
I just flashed the final d2lte CM11 snapshot and your zip file, and it worked! After flashing everything the ROM runs super fast and runs wonderfully! So far as I can tell everything works perfectly. Camera, SMS and MMS, GPS, Mobile Data, and Screen Rotation all work perfectly. My steps for flashing were:
Modify Updater-scripts file to remove device checking
Wipe system, dalvik and cache, and data.
Flash CM11 snapshot
Boot to system
Reboot into recovery and flash Gapps and APN fix (I'm on virgin mobile)
Click to expand...
Click to collapse
I never liked CM myself! I prefer Slim or S.O.K.P. Roms more then any other! You can use alot of the non triband roms kernels and tweaks but just not the bootloaders or modems!
Sent from my LGLS885 using XDA Labs
octos
RootSuperSU said:
I never liked CM myself! I prefer Slim or S.O.K.P. Roms more then any other! You can use alot of the non triband roms kernels and tweaks but just not the bootloaders or modems!
Sent from my LGLS885 using XDA Labs
Click to expand...
Click to collapse
guess what? my second triband died last night. just running, fine. so, went to turn it on and it wouldn't come back on. is there any kind of a reset for the samsungs thAT I DONT KNOW ABOUT? the exact same thing happened with the other triband i had. so i take the phone back to the store and they give me another triband, they said. so i get it home and looked at it and immediately knew that it wasn't a triband. it was the original sph-l710 that i bought", to begin with. these guys dont know what they are selling. id like to complain but to who? this is truly a beautiful phone wit the brushed blue metal look and its one of the "grade A" refurbished phone so i guess maybe i have faith that this one will work.however im a little short on faith right now.
Wow! Good luck man. Honestly, if I had to choose I'd want the original one over the tri-band.
broken tribands
canodroid15 said:
Wow! Good luck man. Honestly, if I had to choose I'd want the original one over the tri-band.
Click to expand...
Click to collapse
ill tell you what, when it ran it ran very well. so what i want to know is tell me what you would do with this phone rom wise and maybe point me where to go get it. also i need all the stock files in case i have to flash this. this phone is very easy to fix. way easier than the triband but those had the same problem and i didn't know it until they up and died. so, if you have a minute. i've got all rooted. i've got selinux fixed and so, ....what is the latest liquid out there? by the way i watch the tide religiously. have for years. i also just noticed your logo. are you part of octos? ah, i think i saw your name. so i had octos on my triband when it died but i didnt have bluetooth on music. it worked on phone. tell me how to set up octos. man i liked it but i have to have that bluetooth music. how do i fix that?
rom flashing
RootSuperSU said:
For anyone unsure about creating the symlinks I have a very simple zip file to flash in recovery to delete the bad symlinks and make the right 1s! I have tested on SlimLP, A.I.C.P., Exodusand Pac-Man d2spr Roms. It will not mess up anything on your S3! It only does as stated. If you wanna check it its all in the script-updater. Just flash this after flashing a d2spr Lollipop rom and if you are also confused on modifying the script-updater for the rom so it will flash on the d2lterefreshspr then just flash the TWRP 2.8.7.0 recovery from TWRP's website and you wont have to worry about changing it!
Fixing Modem Symlinks For SPH-L710T.zip
https://drive.google.com/file/d/0B-Zg_yh4ytvLaS1xSzZ3bWhuTVk/view?usp=docslist_api
Click to expand...
Click to collapse
are you active this night? im about to flash octos. first, i want to ask a couple questions,,,first, what about xposed, is that runnable on a sph-l710? what about dirty? i know it wouldn't run on a triband but this 710? ok enough. how about googles N? is it.
pgellen said:
are you active this night? im about to flash octos. first, i want to ask a couple questions,,,first, what about xposed, is that runnable on a sph-l710? what about dirty? i know it wouldn't run on a triband but this 710? ok enough. how about googles N? is it.
Click to expand...
Click to collapse
Since you're not on a triband just flash the d2spr build, not the d2refresh build. You can run xposed on our ROM if you wish. We always recommend a clean flash, especially if coming from stock or any other ROM. Even if its Oct-L to Oct-M. ??