Related
Hi Friends
Now You can see your Black Screen Recovery!!
NO More tension of flashing Rom's With Black Screen Recovery.
But again a bad News This is only visual with PC Not in phone .
Days are gone with BLACK SCREEN RECOVERY
Here how it works!!
You need some files.
1.Download Adb Files form here
2.Download This [email protected] Tool,Thanks To RiboComments
3.Extract Adb "c:\ " on your pc Creating Folder Adb.
4.Copy [email protected] From your Downloaded folder to desktop.
5.Double click on [email protected] ,and locate the adb.exe form c:\ when asked.
6.Connect you phone using "Charge only mode" with usb debug on.
7.Follow The UI of [email protected] and when will you get your phone screen appearing.
8.Now restart your phone in Recovery mode.
And enjoy The Pleasure Of CWM.
REMEMBER: PLEASE DISABLE ANY FIREWALL (If Getting connecting error) IN YOUR PC AND INSTALL THE LATEST JAVA SDK TO MAKE WORKING THIS SOFTWARE.
Sometime if not working in CWM .
Do the following Troubleshoot .
1. Disconnect your phone.
2. Close [email protected] And
3. Delete all Files In temp Directory Of your PC. (Type " %temp% " Under search box of Start Menu or Under Run Command window) to navigate to Tempdirectory Directly .
4. Now connect Your phone With CWM recovery screen and START [email protected]
5.Click on Restart ADB . (More than once if needed)
This Tool Is Not Mine.
Original Thanks Goes to creator of this Tool RiboComments For his Great Work.
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
BigChillin said:
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
Click to expand...
Click to collapse
Hello, you will not have that problem, but I have a Wildfire S with the black screen recovery problem, and I'm not the only.
And rajanand is the only one that provides a solution.
I'll try the solution of rajanand and I will post the results
Greetings.
Sorry for my bad English.
rajanand said:
Hi Friends
Now You can see your Black Screen Recovery!!
NO More tension of flashing Rom's With Black Screen Recovery.
But again a bad News This is only visual with PC Not in phone .
Click to expand...
Click to collapse
Works great ! Thanks again.
Works great ! You're the BOSS.:good::good:
Thanks a lot.
Aww yeah! Great job sir!
BigChillin said:
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
Click to expand...
Click to collapse
little knowledge it always dangerous to health, so tk care of ur health.
Thanks aunto for commenting on my useful post.
Whatever kid, I saw how many other forums you posted this in. Can we get a REAL member of the community to confirm we need this file, and that it's not brickware.
Sent from my Marvelc
Do not download! Maybe a VIRUS!
Never heard something about this iusses.
Why should I disable my FIREWALL?
Sounds like a virus.
matt5eo said:
Never heard something about this iusses.
Why should I disable my FIREWALL?
Sounds like a virus.
Click to expand...
Click to collapse
sometimes it disconnects itself due to continuous Data transfer in between adb and phone......so
To avoid interruption between ADB and Your phone.
i personally recommend it, rest is on your side.
BigChillin said:
Whatever kid, I saw how many other forums you posted this in. Can we get a REAL member of the community to confirm we need this file, and that it's not brickware.
Sent from my Marvelc
Click to expand...
Click to collapse
Go to market and purchase brand new Lot of WFS,you will surely find black screen problem in that.
Please Stop Arguing..further ,i am not here to entertain such comments.
rajanand: This works great!! thanks
To those who are saying this thread is fake shut up because you dont face our problems with black recovery and rajanand is the only one trying to help
Anto2 said:
Hello, you will not have that problem, but I have a Wildfire S with the black screen recovery problem, and I'm not the only.
Click to expand...
Click to collapse
You are not the one with this problem I have blank CWM Recovery too.
Rajanand helped me many times.
ngoralph said:
rajanand: This works great!! thanks
To those who are saying this thread is fake shut up because you dont face our problems with black recovery and rajanand is the only one trying to help
Click to expand...
Click to collapse
Thanks for your support.
marchelius said:
You are not the one with this problem I have blank CWM Recovery too.
Rajanand helped me many times.
Click to expand...
Click to collapse
Thanks dear for support , hope you all be with me always .
rajanand said:
Thanks dear for support , hope you all be with me always
Click to expand...
Click to collapse
Of course I will
But, I have now another problem to solve: please look : http://forum.xda-developers.com/showthread.php?t=1785689
I have blank screen with older versions of CM 7 !!!
marchelius said:
Of course I will
But, I have now another problem to solve: please look : http://forum.xda-developers.com/showthread.php?t=1785689
I have blank screen with older versions of CM 7 !!!
Click to expand...
Click to collapse
try these steps and try to replace boot.img
(by copying boot.img file only inside the folder),from any other working roms
http://forum.xda-developers.com/showthread.php?t=1749212
older version of boot.img incompatible with black screen devices.
I've never had a recovery with a black screen [on any of my devices and I've tested my share of crappy recoveries]. The stock RUU recovery option sounds better OR flash a working recovery through fastboot. The whole point of a recovery is to have a tool by which you can reset/recover your device. If I have to drive in to a workstation and do an adb plug-in anytime I want to use recovery.. I'm sorry, but I'd seek a better solution. And that's without considering the security risks associated with dropping a firewall and adding a java dev kit. I would in fact, if I had experienced such, find out:
1. Why the blackscreen occurred
2. Fix it
3. Take preventative measures so that it would not occur again.
But that's just me. I wouldn't build a tool to propigate my device's bad behavior.
Rob
Sent from my HTC_A510c using Tapatalk 2
rajanand said:
try these steps and try to replace boot.img
(by copying boot.img file only inside the folder),from any other working roms
http://forum.xda-developers.com/showthread.php?t=1749212
older version of boot.img incompatible with black screen devices.
Click to expand...
Click to collapse
Not working, same sh*it
insink71 said:
I've never had a recovery with a black screen [on any of my devices and I've tested my share of crappy recoveries]. The stock RUU recovery option sounds better OR flash a working recovery through fastboot. The whole point of a recovery is to have a tool by which you can reset/recover your device. If I have to drive in to a workstation and do an adb plug-in anytime I want to use recovery.. I'm sorry, but I'd seek a better solution. And that's without considering the security risks associated with dropping a firewall and adding a java dev kit. I would in fact, if I had experienced such, find out:
1. Why the blackscreen occurred
2. Fix it
3. Take preventative measures so that it would not occur again.
But that's just me. I wouldn't build a tool to propigate my device's bad behavior.
Rob
Sent from my HTC_A510c using Tapatalk 2
Click to expand...
Click to collapse
its fully upon users ,weather they are using it on firewall on or off.(it will work on both the conditions if the "adb" have the access to the port)
its just a recommendation from my side. That's it
Its fully safe from my end and free from any type of virus.
as i have already said this tool is not mine.Please consult the owner of this tool linked on first page of this Thread For future reference.
i don't know why this "black screen recovery" Problem is there with all the newly manufactured WFS.
Why occurred?
1. I am rooting and reflashing CWM on old wfs without any problem.(even rooted for the first time)
2. the same above is not working with any newly manufactured devices.(all working well but With a black CWM recovery)
3. My doubts are pointing, its a fault of hardware,or any kind of display adapters Upgradation from HTC Side.(May be HTC is planning to give supports like ICS etc for future)
4.Also Some rooting errors can be the catch,(Again if HTC upgraded something)
4.CWM is fully working without any error.(Blindly)
5.only the four keys are lighting up,
6.This tool is The only option in that case to flash any custom ROMS.
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.
Hi guys. So my GF has this Samsung Galaxy S (Sprint Epic SPH-D700) ... I think I've got the right section. (EDIT: nope. ty kennyglass123. sorry about that :/)
She drops her phone, display stops functioning. However, the device still works - touchscreen is responsive, boots well, etc. The only thing she needs from it is her contacts. "Easy, Google has it, right babe?" ... "No, when it asked me if I wanted to sync with Google I said 'no'" ...
So, I'm wondering if there's a way to grab the contacts that are theoretically stored on internal memory without seeing the screen. Can't connect to PC because device requires input on it, which I can't see. Cell stores can't help because their transfer machines require the same input. Basically I'm wondering if it's possible to do 1 of 2 things before going ahead with an LCD replacement (which I'm comfortable with doing, just a question of money given that she has a different device she can use and she's off-contract now).
Is there a way to extract using something like ODIN or some command-line tool that forgoes the need for too much device-screen input?
Can anyone possibly provide screenshots of the usb-plugin process as it looks on the device? (once USB cable is plugged in and my PC makes the connected ding, if I could see the relative location of the necessary selections I could just hit it blind). My device is a SGS3 and the process is very different, I just have no clue what parts of her screen to touch. This is only helpful if I can use something (Like KIES) on the PC-end to extract something from the device.
Any other ideas would be phenomenal
Please post questions in Q&A
Thread moved
FNM
Sent from my SPH-L710 using xda premium
Got an idea. Suppose you have USB debugging already on. Connect to PC (make sure driver's installed) and use ADB to copy the contact database out for use on other Android devices (maybe it'll work, maybe it won't)
I'll get you some detailed commands and operations if you need more help.
Sent from Nokia N900 w/ Android 2.3.7
Export to SD card
Well, simple way would be to work off of screenshots from a stock Epic, then export the contacts to the SD card. This way you could work blindly on the touchscreen itself, but orient your finger via the screenshots.
I used stock FC09 multiboot, since I'm on AOKP M6.
Step 1: View attachment 1481544
Step 2: View attachment 1481545
Step 3: View attachment 1481546
Step 4: View attachment 1481547
Step 5: View attachment 1481551
you guys rock ty so much for replying.
USB debugging is apparently not enabled . this is probably the most ideal way to go though.
Very awesome of you to provide screenshots. i've tried this a number of times and i have a feeling she doesn't actually know where here contacts icon is. and no touch feedback. any chance you would be so kind as to provide screenshots for enabling USB debugging? assuming menu key from homescreen allows for settings, you can start from there. I would then be able to use the ADB method. if i'm asking for too much please don't feel obligated or anything.
Got an idea. You're on stock ROM? Then flash CWM via Odin download mode, reboot into recovery. CWM has ADB enabled by default. Try it. I may not be able to provide further details but I think this will work if you're familiar with the steps of Odin
Oh yeah, and you may have to manually mount /system and /data to access files... If you need to know how to use CWM in the blind I could flash back to CM7 (recovery's almost the same) and tell ya how you should navigate to the correct items with the directional keys on the QWERTY keyboard.
Would like to be of help
Sent from Nokia N900 w/ Android 2.3.7
Stock roms have keyboard short cuts and I'm pretty sure one of them is to open contacts. If someone can tell u what that shortcut is then u can use it along with the screenshots to export them to ur sd card.
Sent from my SPH-D700 using xda app-developers app
:highfive: ooh that's perfect! i'm still with you guys, really appreciate the advice. going through some other heavy stuff atm, don't want you guys to think i'm abandoning this thread. will update this post when the madness ends
AndyYan said:
Got an idea. You're on stock ROM? Then flash CWM via Odin download mode, reboot into recovery. CWM has ADB enabled by default. Try it. I may not be able to provide further details but I think this will work if you're familiar with the steps of Odin
Oh yeah, and you may have to manually mount /system and /data to access files... If you need to know how to use CWM in the blind I could flash back to CM7 (recovery's almost the same) and tell ya how you should navigate to the correct items with the directional keys on the QWERTY keyboard.
Would like to be of help
Sent from Nokia N900 w/ Android 2.3.7
Click to expand...
Click to collapse
Hey, I have a similar situation to the OP as my Epic 4G also has a broken display. If I follow your advice, then would I be able to somehow get the phone into diag/modem mode without seeing the dialer on the screen?
KillerFurby said:
Hey, I have a similar situation to the OP as my Epic 4G also has a broken display. If I follow your advice, then would I be able to somehow get the phone into diag/modem mode without seeing the dialer on the screen?
Click to expand...
Click to collapse
Huh? My suggestion is for times when you want your system files backed up without display... And you maybe trying to use it normally as a phone? Rethink.
However if you know what your ROM looks like after boot (requires you to be VERY familiar with the phone) you should be able to blind operate well. Best of luck to ya.
Sent from my Incredible S using xda premium
AndyYan said:
Huh? My suggestion is for times when you want your system files backed up without display... And you maybe trying to use it normally as a phone? Rethink.
However if you know what your ROM looks like after boot (requires you to be VERY familiar with the phone) you should be able to blind operate well. Best of luck to ya.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
No, actually I am trying to read the profile information in CDMA Workshop.
KillerFurby said:
No, actually I am trying to read the profile information in CDMA Workshop.
Click to expand...
Click to collapse
Tough then... From what I understand you're trying to grab modem-related info for use on other phones? No good idea, but anyway it's possible if you post your ROM, version, we flash it and give ya screenshots. See for yaself and good luck
Sent from my Incredible S using xda premium
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links (US variants)
Now: one common recovery for all: jflte
The below specific variants are no more updated, use jflte common variant
AT&T: jflteatt
Sprint: jfltespr
T-Mobile: jfltetmo
Verizon: jfltevzw
Canada/Bell: jfltecan
Cricket: jfltecri
US Cellular: jflteusc
Last version can be found here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Loki patched during install
Click to expand...
Click to collapse
Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links (US variants)
Click to expand...
Click to collapse
I'm not seeing any files in the US Variants folder...are they somewhere else possibly?
i like the look of this, but it would be great if it auto-Loki patched also...
Is it that hard to flash loki doki patch?
*a lot of stupid people with smart phones*
looking forward to this.... will check back today to see if the us variants are uploaded
Great work Phil. Awesome to see this work for jflteatt.
It would absolutely make my day if this supports SDXC cards. Otherwise, I'll be doing some extra reformatting when I get home. Either way, I'll flash it. Good stuff.
Christopher3712 said:
It would absolutely make my day if this supports SDXC cards. Otherwise, I'll be doing some extra reformatting when I get home. Either way, I'll flash it. Good stuff.
Click to expand...
Click to collapse
It was reported by users to work on 64Gb cards since a while now
h3r3tic said:
Is it that hard to flash loki doki patch?
*a lot of stupid people with smart phones*
Click to expand...
Click to collapse
it is when your laptop has gone out and you're doing all your downloading|flashing|etc. via your phone only....
h3r3tic said:
Is it that hard to flash loki doki patch?
*a lot of stupid people with smart phones*
Click to expand...
Click to collapse
Smart auto loki is more of a security thing more than convinience
Sent from my SGH-I337 using xda premium
Aftashok said:
it is when your laptop has gone out and you're doing all your downloading|flashing|etc. via your phone only....
Click to expand...
Click to collapse
loki-doki is a flashable zip, no need for a computer as long as you already have it on your phone and it is a tiny file so It should be easy to keep on the phones sdcard.
Being that I'm only on an hour of sleep and have been at work for 8 hours so far, there's a chance I'm missing something here...
That said, flashing philz_touch_5.06.6-jflteatt.zip to my AT&T S4 yields the 'Unauthorized Firmware' error, prompting me to ODIN my phone (a few times now) again. Luckily I'm still on stock and not losing data. I've flashed from internal storage on CWM recovery and external storage on TWRP to the same results. Someone smack me in the head if i'm missing something here...
**Edit - I also tried inserting your recovery.img into the CASUAL one-click solution and still got the same results.
Christopher3712 said:
Being that I'm only on an hour of sleep and have been at work for 8 hours so far, there's a chance I'm missing something here...
That said, flashing philz_touch_5.06.6-jflteatt.zip to my AT&T S4 yields the 'Unauthorized Firmware' error, prompting me to ODIN my phone (a few times now) again. Luckily I'm still on stock and not losing data. I've flashed from internal storage on CWM recovery and external storage on TWRP to the same results. Someone smack me in the head if i'm missing something here...
**Edit - I also tried inserting your recovery.img into the CASUAL one-click solution and still got the same results.
Click to expand...
Click to collapse
Nope I did the same... nothing
Christopher3712 said:
Being that I'm only on an hour of sleep and have been at work for 8 hours so far, there's a chance I'm missing something here...
That said, flashing philz_touch_5.06.6-jflteatt.zip to my AT&T S4 yields the 'Unauthorized Firmware' error, prompting me to ODIN my phone (a few times now) again. Luckily I'm still on stock and not losing data. I've flashed from internal storage on CWM recovery and external storage on TWRP to the same results. Someone smack me in the head if i'm missing something here...
**Edit - I also tried inserting your recovery.img into the CASUAL one-click solution and still got the same results.
Click to expand...
Click to collapse
jetlitheone said:
Nope I did the same... nothing
Click to expand...
Click to collapse
Whew... I'm running on a 12 hour energy drink and was just positive I'd managed to screw something up.
Christopher3712 said:
Whew... I'm running on a 12 hour energy drink and was just positive I'd managed to screw something up.
Click to expand...
Click to collapse
I tried installing loki doki afterwards and still doesnt work :|
Also now I have custom padlock again lol damn it
i dont use foul language often...
but i ****ing hate that padlock/custom screen.
Slade8525 said:
i dont use foul language often...
but i ****ing hate that padlock/custom screen.
Click to expand...
Click to collapse
Me too, it makes the phone seem crappy lol idk..
AT&T has a locked bootloader
You have to ask in FAQ how to flash cwm on these locked bootloaders for AT&T and Verizon
Phil3759 said:
LoL
2 pages and no one talking about the recovery working as expected or not
What kind of dev forum is here
Sorry, but have no idea of your loki things
All this is done on one phone: old i9100
So, keep in mind that I entirely rely on detailed feedback and description +logs from users to push it where it is now
edit: if you have a locked recovery partition, you must flash using odin or maybe HTC dumlock, but I am really not sure
How to flash a recovery should be something related to FAQ forums...
Click to expand...
Click to collapse
Sorry Phil, we've already gotten used to our recovery work-arounds and assumed your recovery was modified to suit our phones. There's more information here, although I'm not knowledgeable enough about what measures need to be taken to modify your recovery correctly.
Christopher3712 said:
Sorry Phil, we've already gotten used to our recovery work-arounds and assumed your recovery was modified to suit our phones. There's more information here, although I'm not knowledgeable enough about what measures need to be taken to modify your recovery correctly.
Click to expand...
Click to collapse
Argh
So, I need to read there and add some loki files to ramdisk it seems
If any dev/advanced user pops up here to make me spare my time, would be great
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. ??