Related
This is the newest version of Clockwork Recovery- 6.0.1.5 -non-touch
I claim no credit for any of this. I am only posting this because the latest version available on the official ClockworkMod page is still 6.0.1.0.
This recovery was compiled from source, along with a personal CM10 project I'm working on. Please note that this is included with the CyanogenMod source, so anyone building it will end up with the newest recovery image in their OUT folder.
So, for anyone still using Clockwork Recovery, (I do), here you are!
All credit to Koushik Dutta (Koush)--the creator of what I think is still a great recovery.
More info on his work can be found at http://www.ClockworkMod.com/rommanager
Thanks dude!
Here is the touch version of 6.0.1.5 http://d-h.st/1Kk. I built this last night using the recovery builder found here http://builder.clockworkmod.com/ with the 6.0.1.0 version as a base.
EDIT/ I FORGOT TO MENTION. I AM NOT RESPONSIBLE FOR ANYTHING WORKING OR NOT WORKING WITH THIS RECOVERY. I ASSUME NO RESPONSIBILITY FOR BROKEN DEVICES. USE AT YOUR OWN RISK. THANK YOU
myepicyear said:
This is the newest version of Clockwork Recovery- 6.0.1.5 -non-touch
I claim no credit for any of this. I am only posting this because the latest version available on the official ClockworkMod page is still 6.0.1.0.
This recovery was compiled from source, along with a personal CM10 project I'm working on. Please note that this is included with the CyanogenMod source, so anyone building it will end up with the newest recovery image in their OUT folder.
So, for anyone still using Clockwork Recovery, (I do), here you are!
All credit to Koushik Dutta (Koush)--the creator of what I think is still a great recovery.
More info on his work can be found at http://www.ClockworkMod.com/rommanager
Click to expand...
Click to collapse
Is 6.0.1.5 the version that has the option for tar (non-blob) backup?
Yes it has that option
Sent from my Galaxy Nexus using xda premium
TransWarp said:
Is 6.0.1.5 the version that has the option for tar (non-blob) backup?
Click to expand...
Click to collapse
Yes, this version includes both tar and dup (data blob) backup formats. Tar formatting was re-added in 6.0.1.2.
So you can have either quick, large backups; or slower, slimmer backups with this version.
There's also an interesting adb sideload option as well. Not useful for most casual users, however, the more adventurous users will have a purpose for it from time to time.
10characters
FrostyF7 said:
Thanks dude!
Click to expand...
Click to collapse
You are very welcome sir! Thank you for visiting the very first thread that I've ever posted on XDA. Never even started a question thread before. I'm working pretty freaking hard, on personal projects, as well as school stuff, so you should be seeing a lot more from me in the not-too-distant future. I've been looking forward to contributing more for a long time, and I'm excited to give back something with some more substance. I never stop learning at xda. I owe a lot to this place. :fingers-crossed:
myepicyear said:
You are very welcome sir! Thank you for visiting the very first thread that I've ever posted on XDA. Never even started a question thread before. I'm working pretty freaking hard, on personal projects, as well as school stuff, so you should be seeing a lot more from me in the not-too-distant future. I've been looking forward to contributing more for a long time, and I'm excited to give back something with some more substance. I never stop learning at xda. I owe a lot to this place. :fingers-crossed:
Click to expand...
Click to collapse
Thanks for this CWM. The touch version is nice to have, if your device supports it. I have one question though. Is this version still buggy? Any issues so far? Why hasn't it been posted on Koush's site yet? I would give it a whirl but I'm a bit wary; I wouldn't want to mess with my working 6.0.1.0 touch unless I'm 100% positive this has no issues.
Thanks again.
ezeuba said:
Thanks for this CWM. The touch version is nice to have, if your device supports it. I have one question though. Is this version still buggy? Any issues so far? Why hasn't it been posted on Koush's site yet? I would give it a whirl but I'm a bit wary; I wouldn't want to mess with my working 6.0.1.0 touch unless I'm 100% positive this has no issues.
Thanks again.
Click to expand...
Click to collapse
You're welcome. I wholeheartedly appreciate you visiting my thread.
To answer your questions- no, this version is nothing to be afraid of, and definitely not buggy. In fact, the first couple releases of 6.0.x.x were extremely buggy for many people, and 6.0.1.2 was were things seemed to get evened out. If you are still on 6.0.1.0, I would personally suggest updating to at least 6.0.1.2, as it is at least as stable as 6.0.1.0, while adding in a new feature or two. Most issues at the start of v6 releases were about people's backups being extremely slow, and it turned out to mainly be a conflict between Google Play Music and the way the data blob backup folders were executed/cleaned during backup. Google Play Music has a unique way of storing it's music, and it seemed to be responsible for terrible backup times and rebooting during backup(on some devices--never happened to me).
I was using 6.0.1.2 until a few days ago, and everything was always awesome. This version has backups in data blob format going considerably faster for me. It also has an adb-sideload option incorporated ( newest TWRP includes it too). These are the biggest differences, and there is nothing experimental to be wary of. I definitely understand any hesitation, and I think that it's better to be responsible/careful than to be sorry later. As for the exact reason why Koush hasn't put it on the website yet, I couldn't tell you for sure. He's always done releases this way, and if I had to guess, I'd say he waits for more "milestone" type releases to put a new official version up; which does cut down on the questions, help-requests, and other frantic stuff that new releases bring. 6.0.1.0 isn't the most polished or full-featured, but nothing is really wrong, and he probably just doesn't wanna cause a hype.
Again though, this is 100% safe to update to, and will just polish the experience up a bit. It only gets better, regardless of how significantly.
Let me know if you have any more questions. I'd be happy to help
Nick
myepicyear said:
You're welcome. I wholeheartedly appreciate you visiting my thread.
To answer your questions- no, this version is nothing to be afraid of, and definitely not buggy. In fact, the first couple releases of 6.0.x.x were extremely buggy for many people, and 6.0.1.2 was were things seemed to get evened out. If you are still on 6.0.1.0, I would personally suggest updating to at least 6.0.1.2, as it is at least as stable as 6.0.1.0, while adding in a new feature or two. Most issues at the start of v6 releases were about people's backups being extremely slow, and it turned out to mainly be a conflict between Google Play Music and the way the data blob backup folders were executed/cleaned during backup. Google Play Music has a unique way of storing it's music, and it seemed to be responsible for terrible backup times and rebooting during backup(on some devices--never happened to me).
I was using 6.0.1.2 until a few days ago, and everything was always awesome. This version has backups in data blob format going considerably faster for me. It also has an adb-sideload option incorporated ( newest TWRP includes it too). These are the biggest differences, and there is nothing experimental to be wary of. I definitely understand any hesitation, and I think that it's better to be responsible/careful than to be sorry later. As for the exact reason why Koush hasn't put it on the website yet, I couldn't tell you for sure. He's always done releases this way, and if I had to guess, I'd say he waits for more "milestone" type releases to put a new official version up; which does cut down on the questions, help-requests, and other frantic stuff that new releases bring. 6.0.1.0 isn't the most polished or full-featured, but nothing is really wrong, and he probably just doesn't wanna cause a hype.
Again though, this is 100% safe to update to, and will just polish the experience up a bit. It only gets better, regardless of how significantly.
Let me know if you have any more questions. I'd be happy to help
Nick
Click to expand...
Click to collapse
Top notch response. Thanks...
---------- Post added at 05:30 AM ---------- Previous post was at 05:22 AM ----------
One question. How does the sideload thingy work? What's it all about?
Anytime
myepicyear said:
Anytime
Click to expand...
Click to collapse
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
crossen0 said:
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
Click to expand...
Click to collapse
The same way you installed twrp? Boot into fast boot mode and fastboot flash recovery name-of-recovery.img. Replace name of with the actual name of the image. Or you could download and install flash GUI and flash the image through the app.
Sent from my Galaxy Nexus
crossen0 said:
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
Click to expand...
Click to collapse
Though your question may be a bit noobish, it is an absolutely essential process to learn in the custom Android world, and for fear of looking stupid, many beginners skip asking and learning about this very amazing tool. So before I go any further, I'd like to compliment you on being confident enough to ask for help when you need it. It's an extremely important skill that many of us forget around here, as we all want to be seen as a "know-it-all" sometimes, severely inhibiting our abilities to advance. So yeah, just wanted to mention that, lol.
Now, the tool to do this is fastboot. Are you familiar with the concepts of adb and/or fastboot in any way?
Also, what computer operating system do you use?
myepicyear said:
Though your question may be a bit noobish, it is an absolutely essential process to learn in the custom Android world, and for fear of looking stupid, many beginners skip asking and learning about this very amazing tool. So before I go any further, I'd like to compliment you on being confident enough to ask for help when you need it. It's an extremely important skill that many of us forget around here, as we all want to be seen as a "know-it-all" sometimes, severely inhibiting our abilities to advance. So yeah, just wanted to mention that, lol.
Now, the tool to do this is fastboot. Are you familiar with the concepts of adb and/or fastboot in any way?
Also, what computer operating system do you use?
Click to expand...
Click to collapse
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
crossen0 said:
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Definitely try to learn fast boot man. The toolkits are cool, but a minor mistake can make using one a nightmare. If you learn fastboot, you will always be able to fix your device. Plus it is the proper and preferred method for flashing a recovery, radio, or bootloader. It is an invaluable tool for for flashing.
Sent from my Galaxy Nexus using Tapatalk 2
crossen0 said:
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm happy to be able to help man.
If you want a quick fix until I have some time to more time to explain fastboot thoroughly, I can do that for the moment.
The toolkit that mkskip has put together for everyone is very handy. It is basically like having all the essential tools, like fastboot, installed for you in their most lean form, without needing the whole android SDK installed. It also gives you a logical interface to interact with all that stuff. The toolkit installs all these tools within a folder on the root of your C drive. If you go to the root of your C drive, you'll see that folder, which is called 'Galaxy Nexus Toolkit'(or something). If go inside that directory, there's a folder called put imgs to flash here. There are several ways to do things in the toolkit folders, but basically, this is one folder you can insert imgs in to fastboot flash them.
Let me know if you're with me so far. I'm going by my memory of all this stuff because I don't use toolkits or Windows anymore. I can guide you through this, and during the process, hopefully broaden your understanding of fastboot at the same time. I'll need you to do some searching of your own during the process, or it wont make any sense at all, but I can definetly guide you through.
There's no need for the toolkit to flash a recovery.
Literally just CD to the folder the .img is in and run "fastboot flash recovery (whatever your recovery is named).img".
063_XOBX said:
There's no need for the toolkit to flash a recovery.
Literally just CD to the folder the .img is in and run "fastboot flash recovery (whatever your recovery is named).img".
Click to expand...
Click to collapse
Dude, I'm not stupid. I'm trying to explain it in a way he is already familiar with.
Jesus.
So I just saw news that dual booting is in development, and with the nexus 4 being modeled after the LGOG, I thought why not try?
After playing around with the dual-boot installer, I got my hands on the installer's apk!
Anybody wanna take a crack at reverse-engineering the app to work on the Optimus G?
(Kinda new to android development so I'm not sure if that's possible, but it would be awesome if it worked!)
Edit: Changed the build.prop to appear as Nexus 4. App is now functional.
Edit2: IT WORKS (sorry for the caps) Installed and dual boot works.
Edit3: VERY IMPORTANT! Dual-booting also happens to remove your recovery.
(Which comes back after you uninstall Ubuntu, though it seems like your backups are erased?)
After installation, everything stays the same except you have the option to reboot into Ubuntu Touch from within the Installer app.
When you start up the phone normally, it boots straight into Android.
rino757 said:
So I just saw news that dual booting is in development, and with the nexus 4 being modeled after the LGOG, I thought why not try?
After playing around with the dual-boot installer, I got my hands on the installer's apk!
Anybody wanna take a crack at reverse-engineering the app to work on the Optimus G?
(Kinda new to android development so I'm not sure if that's possible, but it would be awesome if it worked!)
Click to expand...
Click to collapse
I saw the article earlier and thought I might play around with it just for sh*ts and giggles but I've already had Ubuntu working on my phone more than once, still no CDMA progress on their part so it still isn't very useful imo. Also the last time I installed it, a full wipe and reinstall of my backup somehow still left ubuntu system files behind and broke twrp(backups would take forever and say successful but would always fail on restore). Once I figured it out it was an easy enough fix and didn't soft brick my phone but it's still a lot of risk for not much payoff. Don't get me wrong, I love the idea, the only operating system I use on my pc is an ubuntu derivative. But until they support cdma, a lot of things won't work.
HPTesla said:
I saw the article earlier and thought I might play around with it just for sh*ts and giggles but I've already had Ubuntu working on my phone more than once, still no CDMA progress on their part so it still isn't very useful imo. Also the last time I installed it, a full wipe and reinstall of my backup somehow still left ubuntu system files behind and broke twrp(backups would take forever and say successful but would always fail on restore). Once I figured it out it was an easy enough fix and didn't soft brick my phone but it's still a lot of risk for not much payoff. Don't get me wrong, I love the idea, the only operating system I use on my pc is an ubuntu derivative. But until they support cdma, a lot of things won't work.
Click to expand...
Click to collapse
I absolutely agree that it has no use as a daily driver, though it will be fun to be able to quickly install and uninstall the newest versions and try them out.
rino757 said:
I absolutely agree that it has no use as a daily driver, though it will be fun to be able to quickly install and uninstall the newest versions and try them out.
Click to expand...
Click to collapse
Good point. I was planning on checking it out, probably tomorrow because I will have some free time. I have a few other projects but if I make any headway I will gladly post results.
Does everything work on the Ubuntu side?
Sent from my LG-LS970 using xda app-developers app
rino757 said:
Edit: Changed the build.prop to appear as Nexus 4. App is now functional.
Edit2: IT WORKS (sorry for the caps) Installed and dual boot works.
Edit3: VERY IMPORTANT! Dual-booting also happens to remove your recovery.
(Which comes back after you uninstall Ubuntu, though it seems like your backups are erased?)
After installation, everything stays the same except you have the option to reboot into Ubuntu Touch from within the Installer app.
When you start up the phone normally, it boots straight into Android.
Click to expand...
Click to collapse
So did you install this per their(ubuntu) instructions or just install the apk as a system app? I went through the source of the dualboot.sh file and also pulled the apk but haven't tried installing it yet. Thank you for letting me know that it erases backups, I'll make sure to copy it to my pc before installing. Could you check something for me after Ubuntu is unistalled? When I had Ubuntu installed before, after wiping and restoring my backup, some Ubuntu files remained. If Ubuntu is currently uninstalled for you, check to see if the /data/ubuntu folder is still there with a root file explorer.
If it is, TWRP 2.5.0.0 will NOT make a backup. Actually it will, but will take forever(20-25 mins) and fail on restore when it gets to the data part. Im not sure about other recoveries. Just a heads up from the times I've already played with Ubuntu Touch and I'm curious if it still does it. I keep saying Im gonna try this and KEEP getting sidetracked(today it's PSX 4.4.2 and AK kernel!) but thanks for the info!
ThatKawaiiGuy said:
Does everything work on the Ubuntu side?
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Depending one the build, some things may be sluggish.
At the moment, there aren't a lot of features and the ones that do work (like settings and home screen) are very limited in what they can do.
HPTesla said:
So did you install this per their(ubuntu) instructions or just install the apk as a system app? I went through the source of the dualboot.sh file and also pulled the apk but haven't tried installing it yet. Thank you for letting me know that it erases backups, I'll make sure to copy it to my pc before installing. Could you check something for me after Ubuntu is unistalled? When I had Ubuntu installed before, after wiping and restoring my backup, some Ubuntu files remained. If Ubuntu is currently uninstalled for you, check to see if the /data/ubuntu folder is still there with a root file explorer.
If it is, TWRP 2.5.0.0 will NOT make a backup. Actually it will, but will take forever(20-25 mins) and fail on restore when it gets to the data part. Im not sure about other recoveries. Just a heads up from the times I've already played with Ubuntu Touch and I'm curious if it still does it. I keep saying Im gonna try this and KEEP getting sidetracked(today it's PSX 4.4.2 and AK kernel!) but thanks for the info!
Click to expand...
Click to collapse
I just installed it as a regular app. The Ubuntu Touch installation itself requires root permissions though.
Sorry but I can't check on the residual files as I hard-bricked my Optimus G.
It was a stupid idea to try to turn it into a Nexus 4 and that thread should be closed.
rino757 said:
I just installed it as a regular app. The Ubuntu Touch installation itself requires root permissions though.
Sorry but I can't check on the residual files as I hard-bricked my Optimus G.
It was a stupid idea to try to turn it into a Nexus 4 and that thread should be closed.
Click to expand...
Click to collapse
That sucks dude!
rino757 said:
I just installed it as a regular app. The Ubuntu Touch installation itself requires root permissions though.
Sorry but I can't check on the residual files as I hard-bricked my Optimus G.
It was a stupid idea to try to turn it into a Nexus 4 and that thread should be closed.
Click to expand...
Click to collapse
Ok... so can you let me know how did you hard brick?
I mean... you were successfully able to get to dual boot right?
Then what happened?
Jaskaran498 said:
Ok... so can you let me know how did you hard brick?
I mean... you were successfully able to get to dual boot right?
Then what happened?
Click to expand...
Click to collapse
Yup, aside from the lag and lack of features in the Ubuntu Touch builds, there was no problem.
As far as I saw, installing/dual-booting Ubuntu Touch on the Optimus G does no harm and has no side-effects.
I bricked my phone with something completely different.
(I was stupid and tried to turn the LGOG into a Nexus 4)
rino757 said:
Yup, aside from the lag and lack of features in the Ubuntu Touch builds, there was no problem.
As far as I saw, installing/dual-booting Ubuntu Touch on the Optimus G does no harm and has no side-effects.
I bricked my phone with something completely different.
(I was stupid and tried to turn the LGOG into a Nexus 4)
Click to expand...
Click to collapse
Hopefully that's the case doing the dual boot install. Installing just ubuntu touch did have side effects for me, and what was weirder was that it took a few weeks. I had restored backups, made backups and flashed different roms for about 2 weeks after I installed ubuntu touch. Then all of a sudden, twrp stopped making backups and I stated the rest, lol. Have you hopped onto the irc #lg-optimus-g channel btw? Are you sure there is no hope for your lgog? Im guessing whatever you did wiped out the sbl and download mode with it?
HPTesla said:
Hopefully that's the case doing the dual boot install. Installing just ubuntu touch did have side effects for me, and what was weirder was that it took a few weeks. I had restored backups, made backups and flashed different roms for about 2 weeks after I installed ubuntu touch. Then all of a sudden, twrp stopped making backups and I stated the rest, lol. Have you hopped onto the irc #lg-optimus-g channel btw? Are you sure there is no hope for your lgog? Im guessing whatever you did wiped out the sbl and download mode with it?
Click to expand...
Click to collapse
I did go on the irc and no luck.
Yup, no download mode or sbl.
I'll send it in for a JTAG sometime.
HPTesla said:
Hopefully that's the case doing the dual boot install. Installing just ubuntu touch did have side effects for me, and what was weirder was that it took a few weeks. I had restored backups, made backups and flashed different roms for about 2 weeks after I installed ubuntu touch. Then all of a sudden, twrp stopped making backups and I stated the rest, lol. Have you hopped onto the irc #lg-optimus-g channel btw? Are you sure there is no hope for your lgog? Im guessing whatever you did wiped out the sbl and download mode with it?
Click to expand...
Click to collapse
twrp somehow s*cks at Ubuntu stuff (It just doesn't know how to handle it).
Use something like Philz (somehow, its able to handle it).
Jaskaran498 said:
twrp somehow s*cks at Ubuntu stuff (It just doesn't know how to handle it).
Use something like Philz (somehow, its able to handle it).
Click to expand...
Click to collapse
Thanks for the info! But until ubuntu touch supports cdma, there really isn't a reason for me to install it.
I've been trying to get dual boot **** to work all day. Any chance I could get the one you have :I
rino757 said:
So I just saw news that dual booting is in development, and with the nexus 4 being modeled after the LGOG, I thought why not try?
After playing around with the dual-boot installer, I got my hands on the installer's apk!
Anybody wanna take a crack at reverse-engineering the app to work on the Optimus G?
(Kinda new to android development so I'm not sure if that's possible, but it would be awesome if it worked!)
Edit: Changed the build.prop to appear as Nexus 4. App is now functional.
Edit2: IT WORKS (sorry for the caps) Installed and dual boot works.
Edit3: VERY IMPORTANT! Dual-booting also happens to remove your recovery.
(Which comes back after you uninstall Ubuntu, though it seems like your backups are erased?)
After installation, everything stays the same except you have the option to reboot into Ubuntu Touch from within the Installer app.
When you start up the phone normally, it boots straight into Android.
Click to expand...
Click to collapse
Fun side note: If you are using CyanogenMod it installs right away, but the cannels become inoperable to use. This booted right up on my LS970 on cm-11-20140210-SNAPSHOT-M3-ls970
No luck
Need help guys, it takes forever to install.
*******************************************************************************************************************************************************************************
SOLUTION FOUND, much thanks to @DocHoliday77
See here for "bootanimation", "bootsamsung", and "bootsamsungloop" files or bottom of this post.
I unziped and I copied "bootanimation" to /system/bin and changed the permissions, I only needed the "bootanimation" file, I had to change permissions to rwe-re-re, other combinations might work/be better. If someone needs to use the other two files, they go in /system/media
Again, credit to @DocHoliday77 for the files!
*******************************************************************************************************************************************************************************
Hey everyone,
So, I tried changing my boot animation, and now I don't have any (it's just a black screen with the original sound)
(I'm on Candian Telus, with 4.4.2)
Basically what I'm asking/looking for is someone to attach a couple files off there phone so I can replace the ones that were altered through this tutorial, and hopefully get a boot animation back.
I'm not 100% sure if I need all of these, or if I may need more, but I have a pretty good idea of what was likely altered:
/system/bin/bootanimation (the extension-less file, this is one that I'm positive that got altered)
/system/bin/samsungani (possibly just and additon fr tutorial, unsure if needed. Information on if others have it would be awesome)
Any information on my situation would be amazing!
Have you tried factory reset (you'll lose data this way)?
Can you flash your ROM again (data will be wiped though)?
OKAstro said:
Have you tried factory reset (you'll lose data this way)?
Can you flash your ROM again (data will be wiped though)?
Click to expand...
Click to collapse
No, I haven't tried either. I'm trying to avoid losing any data, if possible.
Also, I'm not sure if it will fix the problem since the files have been altered directly. (I'm not sure if it will just reset with the file it has now or not)
Any thoughts?
Factory resetting won't help since boot animation is on /system.
If you can't find them here you can always copy them from a stock rom.
Make sure the binary file is from the same build as your current rom. It might not matter, but it just might.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Factory resetting won't help since boot animation is on /system.
If you can't find them here you can always copy them from a stock rom.
Make sure the binary file is from the same build as your current rom. It might not matter, but it just might.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Yeah, I'm really hoping someone is nice enough to copy and paste their bootanimation file in here, but I doubt it'll happen...
Any tips/ideas on how to go about copying from a stock rom? (I'm new to a lot of this stuff, so I'm unsure of how to go about this)
you can search on google and download boot animations.
but like doc said , ' make sure is from same build cause it might just matter. i DL cm 10.1 from internet and works great .
just a thought.
err on the side of kindness
@mrrocketdog
It's not so much a boot animation itself that I'm having trouble with, but the actual system file called "bootanimation".
I believe when I tried to install a custom animation I/the files from a tutorial I was using altered it, and now it doesn't work whatsoever.
If you know of any boot animation tutorials/files that could fix this though that would be sick!
Either way thanks for the input!
You can try these if you like. I'm running Likewise rom right now, but they should work fine for you.
http://forum.xda-developers.com/attachment.php?attachmentid=2969141&stc=1&d=1413149765
Solved
DocHoliday77 said:
You can try these if you like. I'm running Likewise rom right now, but they should work fine for you.
http://forum.xda-developers.com/attachment.php?attachmentid=2969141&stc=1&d=1413149765
Click to expand...
Click to collapse
I love you. At first it didn't work but I changed some permission and now it's back to stock! Thank you sooo much!
Not to to add further trouble, but to prevent any future mishaps, could you point me in the right direction to getting a custom boot animation running?
maybe here..
http://forum.xda-developers.com/showthread.php?t=2843830
if you use search a whole lot pops up.
good luck. :thumbup:
err on the side of kindness
There should be a thread(s) in the Themes and Apps section. I wouldn't use any not confirmed or made for the S3 though. And I wouldn't mess with that binary file either. (Unless specifically told to do so in one of our threads.) Any we have here should work fine just using the actual animation files.
Some threads may also have a return to stock zip file you can flash in recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
think thats o.k. doc ? so maybe be REAL FREAKIN CAREFUL.
err on the side of kindness
Alright guys, sounds like a plan. I'll make sure to be a whole lot more careful this time around! Thanks a bunch!
mrrocketdog said:
think thats o.k. doc ? so maybe be REAL FREAKIN CAREFUL.
err on the side of kindness
Click to expand...
Click to collapse
Are you referring to the one you linked to? To be perfectly honest I wouldn't try it. It was for the HTC One, right? I just don't know enough about HTC devices. It might be safe to use the animation, but it may just not work. (I doubt there'd be much danger of a hard brick though, but better safe....)
Sent from my SAMSUNG-SGH-I747 using Tapatalk
yup, thats the one. i forget sometimes : READ READ READ. thanks for double checking behind me. will be more careful in future. dont want to cause xtra problems !!!!!!
err on the side of kindness
No problem. It could be perfectly ok to use, but since I don't know, I consider it a higher risk is all. Another thing to consider is if it's dpi is different the images probably wouldn't display correctly.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
@DocHoliday77
So after a while of researching I was thinking of downloading CyanogenMod, and the using that to do boot animation stuff, thoughts?
As long as it's from the S3 versions of cm, I believe it would be safe to try. Probably the worst that might occur would be no animation, like you already experienced. I don't use CM though, and don't really mess with the boot animation much to begin with, so it is possible it wouldn't work as expected, I'm just not sure on that. But it should be simple enough to get back to the stock animation with the files I posted before.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Yeah, I guess that's really the worse that could happen, I've made a backup of my stock ROM so I should be able to go back if needed. Again, thanks for all the help!
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. ??
ATTN: I NEED EVERYONE'S HELP!!! PLEASE!!!Here's what I need you to do!Find and Search through your PC's and look for any complete or decently stable ROM's, RECOVERY's, KERNEL's and any possible missing links / files / documents for the LG Optimus V regardless of it's version or kernel and Send me WORKING links, files, of anything you got. All the links for this phone are dead... I've checked all over the web. This is still a great phone, and can still be used either with Boost Mobile or simply with a Credit or Debit card. A friend and I plan on revamping this phone to see if we can't bring it back to it's glory. But in order to do so.... Got to have the Archives! Every link is dead.... PLEASE PLEASE PLEASE search around for anything LG Optimus V, VM670, Thunderc Optimus S is also appreciated.
THANK YOU FOR YOUR TIME AND PATIENCE
Send them to me, in a PM and or share them with me to my Google Drive via email.... PM for email... thanks
You may post links here only as long as the owner hasn't pulled the files for TOS Violations.
To be honest.... if your unsure, just PM the links.
I'm taking any and all files that are DEAD links
anything I can redownload as of today's date, will be unwanted.
But don't let that discourage you from SHARING THEM AWESOME FILES AND RE-UPLOADED LINKS!
THANK YOU THANK YOU THANK YOU!!!
:good::laugh:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Here's some Optimus S stuff I used to use,was able to download from here today, https://archive.midnightchannel.net/zefie/files/cell/LGLS670/
bigsupersquid said:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Click to expand...
Click to collapse
So the JB rom boots okay,how do i setup Sprint apn/keylayout?
bigsupersquid said:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Click to expand...
Click to collapse
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files!!
timjames474 said:
So the JB rom boots okay,how do i setup Sprint apn/keylayout?
Click to expand...
Click to collapse
I might be able to help you, Tell me what ROM exactly and what it says is WORKING and NOT WORKING on the main page of the post... or a link... It could be like you said a simple set up.
But I do remember having to change something to get other carriers to work. Because it was only a CDMA phone. No GSM. If I remember correctly
redbaron2005 said:
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files
Click to expand...
Click to collapse
you have to crack open the boot.img and replace just the kernel with a working one. it's "fun."
and finding a working kernel for the newer screens now as a standalone download is really iffy. (actually, see next post. I found /one./)
if you have another jb rom with working screen you can split that boot.img and yoink its kernel for the one that doesn't have more than a backlight. you can also plop that picasticks kernel from below into any blackscreen recovery images too, they split and recombine just like a boot image.
a lot of people call the boot.img a kernel, but it's actually a combination of kernel and ramdisk.
you can use osm0sis AIK tools to disassemble and reassemble boot.img relatively painlessly.
I'm happy to promote osm0sis's work. he does great things. drop him a donation if you're so inclined, he certainly deserves it.
by the way, don't try to insert the 3.0 kitkat kernel into anything else... it probably won't boot. jb is the best bet to try it on though, thekraven nudged me into porting that kernel from the p500 for his jb roms. I'm glad he did, because the experience has been very useful on other devices.
ok, here's my gift to y'all.
https://www.androidfilehost.com/?w=files&flid=317344
archive of the primary goodies from my old failing NTFS external drive. We'll see how long it takes for androidfilehost to arbitrarily delete them like they did every other file I ever uploaded there for the optimus S/V with no warning or acknowledgment. they never even answered multiple support requests trying to find out why... I'm guessing they decided to clean their servers of things uploaded before a certain date, but no telling since they wouldn't answer.
in the kernels subfolder is a picasticks kernel i built for the old/new screens.
multiple recoveries. some are old and may blackscreen on newer devices, fair warning. some roms will be the same way. the twrp's may or may not have reversed system/userdata like my os2sd twrp, try and see. they should at least be good on any model optimus s/v screen.
several roms, including one harmonia, and PAC-rom from thekraven.
others folder has V drivers... and swype flashable zip, ripped probably from GB stock, maybe from froyo stock.
also multirom recoveries and installer if you like multiboot. thread here
have fun.
redbaron2005 said:
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files!!
I might be able to help you, Tell me what ROM exactly and what it says is WORKING and NOT WORKING on the main page of the post... or a link... It could be like you said a simple set up.
But I do remember having to change something to get other carriers to work. Because it was only a CDMA phone. No GSM. If I remember correctly
Click to expand...
Click to collapse
i got data fine it was more the keys that was bugging the **** outta me
this one here from another link posted here,i use Tello,which uses Sprints MMSC,and yes i figured out actvating data just last week! Downgrade to ZVD and let HFA run. Thats literally it
forgot the link https://sites.google.com/site/bobzhomeroms/vm670jb
timjames474 said:
i got data fine it was more the keys that was bugging the **** outta me
this one here from another link posted here,i use Tello,which uses Sprints MMSC,and yes i figured out actvating data just last week! Downgrade to ZVD and let HFA run. Thats literally it
forgot the link https://sites.google.com/site/bobzhomeroms/vm670jb
Click to expand...
Click to collapse
you need the correct .kl file, I've probably got one stashed somewhere.
it switches the two keys in software.
it's funny, because both the virgin and sprint phones have the same board, but the firmware reverses which key is read as which.
I'll look around and try to find the .kl file for you. androidfilehost deleted my flashable zips with those along with everything else for the S/V a while back as I was complaining about above, or I'd just point you there.
bigsupersquid said:
you need the correct .kl file, I've probably got one stashed somewhere.
it switches the two keys in software.
it's funny, because both the virgin and sprint phones have the same board, but the firmware reverses which key is read as which.
I'll look around and try to find the .kl file for you. androidfilehost deleted my flashable zips with those along with everything else for the S/V a while back as I was complaining about above, or I'd just point you there.
Click to expand...
Click to collapse
if you manage to find it,do let me know! TIA
timjames474 said:
if you manage to find it,do let me know! TIA
Click to expand...
Click to collapse
I can pull the one from the rom on my V and switch the keys.
no flashable zip, you'll have to use adb to install it, I'll post the commands
it's home and menu that are swapped if I remember right, is that correct?
it's actually a .kcm file, I've messed with so many devices I mix things up sometimes.
Sorry for being gone so long,yes those are the keys,my Optimus S had been dropped one time too many but i finally replaced it and am still interested in getting those files and commands
alright, I'll pull the file and swap those two keys.
I don't remember any oddball locations for the file across different roms... but since it has been a while since I did anything much with this device, just to make sure, I'll add a test to the instructions to make sure it's going into the right location.
bigsupersquid said:
alright, I'll pull the file and swap those two keys.
I don't remember any oddball locations for the file across different roms... but since it has been a while since I did anything much with this device, just to make sure, I'll add a test to the instructions to make sure it's going into the right location.
Click to expand...
Click to collapse
Seems that it always goes to /system/usr and the two folders are keylayout and key(something else idr) the one that i cannot remember the name for is where the .kcm files are at
since harmonia has two applicable .kl files, thunder.kl and thunder_keypad.kl I'm not sure which to mess with.
they're in /system/usr/keylayout/
the process is to adb pull the thunder*.kl file from your working ROM (whichever file it is, thunder.kl or thunder_keypad.kl,) back it up on computer with a copy in case you mess it up, then:
change all instances of HOME to MENU and MENU to HOME. I can't remember how much difference the WAKE and WAKE_DROPPED field makes, but you can switch those too, or leave that alone and try it.
if you're using M$ window$, don't push the enter/return key while editing unless you're editing with notepad++, the default editor screws up carriage return line feed character codes. mac or linux shouldn't dork up the CRLFs.
chmod 644 the file after pushing it back, and chown root:root
I'd have to grab it from one of the cm rom files I uploaded for a better reference, and I'd rather not re-download them or try to get my failing external drive they're on to mount at the moment.
bigsupersquid said:
since harmonia has two applicable .kl files, thunder.kl and thunder_keypad.kl I'm not sure which to mess with.
they're in /system/usr/keylayout/
the process is to adb pull the thunder*.kl file from your working ROM (whichever file it is, thunder.kl or thunder_keypad.kl,) back it up on computer with a copy in case you mess it up, then:
change all instances of HOME to MENU and MENU to HOME. I can't remember how much difference the WAKE and WAKE_DROPPED field makes, but you can switch those too, or leave that alone and try it.
if you're using M$ window$, don't push the enter/return key while editing unless you're editing with notepad++, the default editor screws up carriage return line feed character codes. mac or linux shouldn't dork up the CRLFs.
chmod 644 the file after pushing it back, and chown root:root
I'd have to grab it from one of the cm rom files I uploaded for a better reference, and I'd rather not re-download them or try to get my failing external drive they're on to mount at the moment.
Click to expand...
Click to collapse
I was able to pull from CM7 for LS670 and swap,fix perms and voila! Also noticed getting gapps to work on BobzHomes jb is a PITA,as there appears to be no setupwizard so it thinks its in setup,but its not. i looked at build.prop and shut off the setupwizard bypass but nothin. Nearing the point where i say frick gapps at this point
timjames474 said:
I was able to pull from CM7 for LS670 and swap,fix perms and voila! Also noticed getting gapps to work on BobzHomes jb is a PITA,as there appears to be no setupwizard so it thinks its in setup,but its not. i looked at build.prop and shut off the setupwizard bypass but nothin. Nearing the point where i say frick gapps at this point
Click to expand...
Click to collapse
yeah, gapps suck. and it's even worse dealing with them on a device which has such a small system and data partition.
you might look into microg. I prefer it anyway.
glad you got the keyswap to work.
bigsupersquid said:
yeah, gapps suck. and it's even worse dealing with them on a device which has such a small system and data partition.
you might look into microg. I prefer it anyway.
glad you got the keyswap to work.
Click to expand...
Click to collapse
MicroG has a broken login,the login box is all the way off screen for me,but ive since gotten a modern phone at the gentle prodding at Tello anyway