[Q] Why is there no dev's working on samsung galaxy discover sch-r740c roms - General Questions and Answers

Hey all im just curious why nobody is working on roms and such for samsung discover sch-r740c? seems like it should get a little love for our cricket brothers. a couple roms and such would be sweet.

darkskywalker said:
Hey all im just curious why nobody is working on roms and such for samsung discover sch-r740c? seems like it should get a little love for our cricket brothers. a couple roms and such would be sweet.
Click to expand...
Click to collapse
Currently attempting a cw-9/10 port to this device, however; we're still needing a stock rom for it, if you happen to have the phone I would be more than willing to help walk you trough data dumps of the systems primary partitions recovery/modem/system/boot.
This is important to have a 'default return to' unfortunately I'm unable to use my phone as a stock image as I heavily modified the system partition shortly after rooting the device thinking there would be roms forthcoming soon..
Note to self: in the future always always always get a stock restore FIRST!
CowboyEnvy

cowboyenvy said:
Currently attempting a cw-9/10 port to this device, however; we're still needing a stock rom for it, if you happen to have the phone I would be more than willing to help walk you trough data dumps of the systems primary partitions recovery/modem/system/boot.
This is important to have a 'default return to' unfortunately I'm unable to use my phone as a stock image as I heavily modified the system partition shortly after rooting the device thinking there would be roms forthcoming soon..
Note to self: in the future always always always get a stock restore FIRST!
CowboyEnvy
Click to expand...
Click to collapse
yes i actually do have one although im not a dev if you write some instructions i will try to get you the info you need maybe ill learn some new stuff and have some fun helping. thank you for quick response.

Samsung r740c img dump - Howto
- Check samsung settings > about phone - baseband version and build number should end in r740CVV???? and should match, also check for kernel version 4.1.2
- Enabled USB debugging on the phone (system settings > developer options)
- Install Samsung USB driver pack(http://downloadcenter.samsung.com/content/SW/201211/20121129051929115/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe)
- Install UnlockRoot Pro (free version - http://downloadcdn.betterinstaller.com/installers/9/9/UnlockRoot_downloader_by_UnlockRoot.exe)
(read everthing and and 'skip' the unwanted software)
- Plug phone into PC and get past lock screen if enabled
- Open UnlockRoot and click "Root"
(skip unwanted software(apps) again)
- download ADB create a directory either on the desktop or c:\ for easy access I suggest c:\sch-r740c
- extract the files of sch-r740.zip into the folder
- click start and search for cmd
- right click cmd.exe run as administrator
- at the command window execute the following commands.
cd c:\sch-r740c
adb shell
su
dd if=/dev/block/mmcblk0p12 of=/mnt/extSdCard/recovery.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/mnt/extSdCard/boot.img bs=4096
dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/modem.img bs=4096
dd if=/dev/block/mmcblk0p16 of=/mnt/extSdCard/system.img bs=4096
exit
exit
adb pull /mnt/extSdCard/recovery.img ./recovery.img
adb pull /mnt/extSdCard/boot.img ./boot.img
adb pull /mnt/extSdCard/modem.img ./modem.img
adb pull /mnt/extSdCard/system.img ./system.img
Click to expand...
Click to collapse
note these commands may take a while to process
when your done, you can zip and upload the files to an upload service, or Google drive and share them.
I'll create an odin recovery

Hello no need for you to pull flash files from your device, I've finally been able to restore my phone to stock 4.1.2 through a somewhat convoluted process so I'll now be able to create a stock restore
Sent from my SCH-R740C using xda app-developers app

thank you
cowboyenvy said:
Hello no need for you to pull flash files from your device, I've finally been able to restore my phone to stock 4.1.2 through a somewhat convoluted process so I'll now be able to create a stock restore
Sent from my SCH-R740C using xda app-developers app
Click to expand...
Click to collapse
Thank you sorry I had some family issues or I would have been quick on it plus couldn't log in for a day hmm anyway last night there was an ota update seemed the size of whole os is there somewhere in root files or elsewhere we can extract this? And if so would it help us in anyway I would like to start working on learning more and helping teams build custom ROMs and seems like this might help.

darkskywalker said:
Thank you sorry I had some family issues or I would have been quick on it plus couldn't log in for a day hmm anyway last night there was an ota update seemed the size of whole os is there somewhere in root files or elsewhere we can extract this? And if so would it help us in anyway I would like to start working on learning more and helping teams build custom ROMs and seems like this might help.
Click to expand...
Click to collapse
No worries, first off check your build number if it end in I1 or F1 we have that update already saved and uploaded to shared services, if you are VVBNA5 you have a new update we have not seen yet.
In any case, install OTA rootkeeper available on market or you will loose root, and have to odin flash (custom) to re-root.
Also, updates can be found at /cache/FOTA/update.zip
local caches up updates can help developers fiddle with multiple versions of the OS without relying on updates via OTA updates. or backups etc.
So far, all the patches that have come out for this device are 'patch based' only IE not much help other than to allow people to download the update manually, or for devs to check out potential 'mods' against multiple versions.

cowboyenvy said:
No worries, first off check your build number if it end in I1 or F1 we have that update already saved and uploaded to shared services, if you are VVBNA5 you have a new update we have not seen yet.
In any case, install OTA rootkeeper available on market or you will loose root, and have to odin flash (custom) to re-root.
Also, updates can be found at /cache/FOTA/update.zip
local caches up updates can help developers fiddle with multiple versions of the OS without relying on updates via OTA updates. or backups etc.
So far, all the patches that have come out for this device are 'patch based' only IE not much help other than to allow people to download the update manually, or for devs to check out potential 'mods' against multiple versions.
Click to expand...
Click to collapse
Got a new one I'll post pic

Here is pic I been trying to post all day my app acting stupid
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

K that is your current rom and you have a large update file?
Sent from my SCH-R740C using xda app-developers app

darkskywalker said:
Here is pic I been trying to post all day my app acting stupid
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
current build pre-update or current-build post-update?
---------- Post added at 05:34 PM ---------- Previous post was at 05:30 PM ----------
http://forum.xda-developers.com/showthread.php?t=2617484

cowboyenvy said:
current build pre-update or current-build post-update?
---------- Post added at 05:34 PM ---------- Previous post was at 05:30 PM ----------
http://forum.xda-developers.com/showthread.php?t=2617484
Click to expand...
Click to collapse
Did this move to a new thread or something?

No never got a response from this and I have moved to a Samsung Galaxy s4 on Verizon

cowboyenvy said:
No never got a response from this and I have moved to a Samsung Galaxy s4 on Verizon
Click to expand...
Click to collapse
i have this phone i rooted it via cwm even tho its a temp. recovery

Related

Unofficial Guide To Installing K-exec and CM9 & CM10

Unofficial K-EXEC & CM9\10 Guide
cm9 Required Files / Downloads
CM9 ROM: http://goo.im/devs/BeansTown106/SGS3vzw/cm9/cm-9-20120719-UNOFFICIAL-d2vzw.zip
K-Exec Clockwork Mod: http://goo.im/devs/BeansTown106/SGS3vzw/cm9/d2vzw_recovery.img
ICS Gapps: http://goo.im/gapps/gapps-ics-20120429-signed.zip
cm10 Required Files / Downloads
CM10 Rom: http://goo.im/devs/BeansTown106/SGS3vzw/CM10/cm-10-20120721-UNOFFICIAL-d2vzw.zip
JB Gapps: http://goo.im/devs/BeansTown106/SGS3vzw/CM10/gapps-4.1.1-Kejar31-20120711.zip
K-Exec Clockwork Mod: http://goo.im/devs/BeansTown106/SGS3vzw/cm9/d2vzw_recovery.img
Click to expand...
Click to collapse
Setup Instructions
Step 1.- Transfer the CM9 or Cm10 Rom, ICS or JB Gapps, and d2vzw_recovery.img to the root of you emmc
Step 2.- push the kexec cwm to sdcard and install
Code:
adb push d2vzw_recovery.img /sdcard/
adb shell
su
dd if=/sdcard/d2vzw_recovery.img of=/dev/block/mmcblk0p18 bs=256k
sync
reboot recovery
Step 3.- reboot into recovery
Step 4.- wipe data factory reset
Step 5.- Install cm9 or Cm10 zip
Step 6.- Install ICS or JB Gapps
Step 7.- Profit You Should Be Booting into CM9 or Cm10
Click to expand...
Click to collapse
Credits
I take no credit for this.. its all cvpcs's work and the cyanogenmod team.. **the jb zip was also made by dhacker it is 100% stable i think better than ics ** i was just impatient and merged the data fix before it went live , Build now has kexec intergrated so all u need to do is flash this new recovery and the cm9 zip it will auto Kexec thanks to cvpcs
Click to expand...
Click to collapse
DISCLAIMER
Neither me or team cyanogenmod take any responsibility if u brick your phone doing this, make a backup and read over instructions 2-3x
Click to expand...
Click to collapse
Edit* just wanted to apologize for my previous post! I thought you were posting a guide in the oe development thread...when in reality your posting cm9/10 roms that you helped develop. I would suggest editing the title of the thread to reflect that its rom development and not just a guide. I do appreciate your work!!!
droidstyle said:
Sweet write up....but derp, what on earth made you determine this is original development?
Click to expand...
Click to collapse
This is meant for the newest roms ie: aosp, cm, aokp source builds. no?
I'm giving this a shot. Thank you for the write...I don't think even I scan even screw this up!
I know this is early stage so not a complaint here, just having data drops on 3G. Besides those I am in heaven! lol
Sent from my Galaxy Nexus using Tapatalk 2
So there's data now?
EM2_Rob said:
So there's data now?
Click to expand...
Click to collapse
Yeah I am as well curious, though it seems that if there are drops it would suggest that data is available... I assume this is the build that cvpcs posted about having shaky 4g? (And 3g it seems)
Please pardon the noobish question but is there a way to push these files with terminal emulator? I haven't been able to get ADB to work. I have it and the SDK installed but when i try to push something it says ADB is not a recognized command
Dcox28 said:
Please pardon the noobish question but is there a way to push these files with terminal emulator? I haven't been able to get ADB to work. I have it and the SDK installed but when i try to push something it says ADB is not a recognized command
Click to expand...
Click to collapse
Sure..just skip the first two ADB commands (make sure you have the files on your EMMC/internal storage). Start with the "su" command to get root and follow the rest of the directions.
Hello data is not dropping for me at all. Actually better signal then stock touchwiz. I recommend flashing this and trying.
Sent from my SCH-I535 using Tapatalk 2
papi92 said:
Hello data is not dropping for me at all. Actually better signal then stock touchwiz. I recommend flashing this and trying.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Nice... do you live in a 4g area? My experience has been this device is shaky on 4g, so I might hold out.... but I'm definitely tempted!
Marcismo55 said:
Sure..just skip the first two ADB commands (make sure you have the files on your EMMC/internal storage). Start with the "su" command to get root and follow the rest of the directions.
Click to expand...
Click to collapse
Thank you very much. I am almost scared to ask the next question but when plugging my phone in to the pc i get the window that pops up and lets me go to Card or Phone. Obviously emmc/internal storage would mean for me to copy these files to Phone but I also am rooted and have CWM installed. If I did a nandroid right now before installing CM9, would I be able to restore it if needed after installing the Kexec touch CWM?
Thanks again for all help.
Yeah, I would also like to know what the LTE situation is with this. Not really pressed, though, as it's early in development. Great to see work like this happening.
Any chance for a CM10 build?
edit*
My 4g is solid. I haven't dropped yet.
Sent from my SCH-I535 using Tapatalk 2
papi92 said:
My 4g is solid. I haven't dropped yet.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Whoa, really?! I didn't know CM9 for the S3 now had data! That's awesome, I'm so tempted to try it out now...
---------- Post added at 01:05 PM ---------- Previous post was at 12:49 PM ----------
Double post, but dumb question: What is "emmc"? Is that the folder that opens when you double-click "Phone" on the Card and Phone folder, which opens when you link the phone to a PC? That's where my previous img's were located...
My data shut off after about a half hour. Now I can't get it past No Service and Roaming (No SMS/MMS, Voice, nothing); just a heads up for those who want a preemptive taste of CM9.
Dcox28 said:
Thank you very much. I am almost scared to ask the next question but when plugging my phone in to the pc i get the window that pops up and lets me go to Card or Phone. Obviously emmc/internal storage would mean for me to copy these files to Phone but I also am rooted and have CWM installed. If I did a nandroid right now before installing CM9, would I be able to restore it if needed after installing the Kexec touch CWM?
Thanks again for all help.
Click to expand...
Click to collapse
I still have access to my backups using the included touch recovery so restoring nandroids should be fine.
minmongoblin said:
Whoa, really?! I didn't know CM9 for the S3 now had data! That's awesome, I'm so tempted to try it out now...
---------- Post added at 01:05 PM ---------- Previous post was at 12:49 PM ----------
Double post, but dumb question: What is "emmc"? Is that the folder that opens when you double-click "Phone" on the Card and Phone folder, which opens when you link the phone to a PC? That's where my previous img's were located...
Click to expand...
Click to collapse
The EMMC is the internal storage. Just place the files on the root of your internal storage (not in any folders)
minmongoblin said:
[/COLOR]Double post, but dumb question: What is "emmc"? Is that the folder that opens when you double-click "Phone" on the Card and Phone folder, which opens when you link the phone to a PC? That's where my previous img's were located...
Click to expand...
Click to collapse
https://www.google.com/search?sugex....,cf.osb&fp=3a50ef9c1ec22192&biw=1280&bih=623

Samsung Galaxy Rugby Pro (SGH-547) Root / CWR / Other Hacks

There is now a super thread over here with this root information and some more recoveries. I plan on expanding as more things are developed for the Rugby Pro.
I have added other hacks to this thread below the root download links. Enjoy.
The below guide outlines how to gain root on the Samsung Galaxy Rugby Pro (SGH-I547 ATT / Bell (Yes, Canada works!) / commanche). Please read through the full guide before attempting to root your device.
You will need ODIN v3.04 in order to gain root on the Rugby Pro (comanche), I will not post a link due to the nature of the package. Google has plenty of links for it.
BIG thanks to utkanos for all the help and making this a reality
Install instructions -- goldenlederhosen has provided some further information and detail about the below procedure here
Please read his post as well as the instructions before attempting this procedure
Install drivers from link below
Download necessary packages (clockwork recovery, root update) from the links below
Copy root update to your devices sdcard(s) -- Copy to both if external SD card is present
Charge phone to at least 80%
Power off the phone
Unplug from USB / Charger
Boot into download mode (Home + Volume Down + Power)
When asked if you want to continue, press Volume Up to enter download mode
Plugin phone and
Launch ODIN
Check the checkbox next to "PDA"
Click the PDA button
Select the comanche_cwr_6015_utkanos.tar.md5 file
Make sure only "Auto Reboot" and "F. Reset Time" are selected
Click start
Your phone will reboot one the flash is complete
You now have Clockwork Recovery, continue with the steps to get root
Power off your phone
Unplug from USB / Charger
Boot into Clockwork Recovery (Home + Volume Up + Power -- Release when Samsung logo appears)
Select "Install zip from sd card"
Select "Choose zip from sd card"
Navigate to zip
Select zip
Confirm
Reboot
You should now have root
I am not responsible for anything bad that comes to your device when using the information posted in this thread. Everything here is dangerous, may cause a brick, will void a warranty and has the potential to just plain wreak havoc. Do not complain you followed my instructions and met with a dead device. Consider yourself warned
I've tested to the best of my ability, but I am one person with one device, I cannot catch all potential failure modes. If you find a problem and a fix, or have information that should be added let me know and I will update the necessary information.
Download Links
Head over to the super thread here (link) for links.
CWR Touch / ODIN
Courtesy of childrenofthehorn there is a now a Clockwork Recovery Touch and ODIN images for the ATT varient. The thread is: http://forum.xda-developers.com/showthread.php?t=1990519
Rootz Wiki Forum
childrenofthehorn has gotten a dedicated forum setup over at Rootz Wiki. Check it out: http://rootzwiki.com/forum/556-galax...o-development/
Works like a charm!
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.
dweide9 said:
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.
Click to expand...
Click to collapse
Thank you much for the donation
Would you be willing to pull an image of the stock boot partition (dd if=/dev/block/mmcblk0p7) and PM me a link?
Also: check the OP, I've added some info on how to get tethering (after rooting) without the need for a dedicated ATT tethering plan.
re: post-root stuff
>Would you be willing to pull an image of the stock boot partition (dd >if=/dev/block/mmcblk0p7) and PM me a link?
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
>Also: check the OP, I've added some info on how to get tethering (after rooting) without >the need for a dedicated ATT tethering plan.
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?
dweide9 said:
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
Click to expand...
Click to collapse
You can copy the contents of boot by:
Install a terminal emulator from the market
Launch terminal
su
Accept request for root
dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/mmcblk0p7_boot.img
Transfer mmcblk0p7_boot.img to your favorite cloud storage provider
Share link
If you run into trouble or have any questions let me know.
dweide9 said:
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?
Click to expand...
Click to collapse
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Sent from my SAMSUNG-SGH-I547 using Tapatalk 2
boot partition image
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
So what fun stuff can you do with this file & how would my image be any different then yours? Or is it another issue, like uploading being restricted because you're a developer?
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.
kemonine96 said:
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Click to expand...
Click to collapse
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.
dweide9 said:
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
Click to expand...
Click to collapse
Thanks for the file. I just finished pulling it.
dweide9 said:
So what fun stuff can you do with this file
Click to expand...
Click to collapse
I plan on using a stock boot image so I can put together an ODIN image that will flash the phone back to a stock state. If you root your phone or have a custom recovery / system / boot OTA updates will generally fail to apply. The best way to get an OTA update applied is to rollback to stock and install the OTA.
dweide9 said:
how would my image be any different then yours?
Or is it another issue, like uploading being restricted because you're a developer?
Click to expand...
Click to collapse
The boot partition should be the same across devices unless you make modifications.
I had to blindly update the boot partition on my device to get root, so I do not have an un-changed copy of it. In order to get an OTA update applied and to work with some Cyanogen / Clockwork Recovery stuff I will need a clean boot partition image.
dweide9 said:
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.
Click to expand...
Click to collapse
I worked with a few people to get help putting together an ODIN image that allowed me to get custom recovery and the clockwork recovery update.zip. There is no general guide on the steps necessary.
If you are interested in diving into the custom rom / recovery stuff I will be doing some work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully working on a Cyanogenmod 10 (JellyBean) port in the future. I am working on some items for the Rugby Smart (apache) at present, as soon as that stuff is taken care of I'll be focusing more on the Rugby Pro (commanche). If you are interested in taking a shot at updating the clockwork recovery for the commanche let me know and I can maybe point you in a few directions to get you going.
stuff
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.
dweide9 said:
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
Click to expand...
Click to collapse
I pulled that package as well. Unfortunately it is only the GPL components they are required to release, not the full ROM sources. It does contain the kernel sources which will be very helpful down the line.
dweide9 said:
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Click to expand...
Click to collapse
There is a lot of testing work and guess/check for the ROM building stuff. I was thinking of setting up an IRC channel on FreeNode for discussing work on the device. Would you be interested / willing to move some of the interactive discussion over there once I have a channel setup?
dweide9 said:
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.
Click to expand...
Click to collapse
Keep me in the loop. I tend to only tether for the purpose of my tablet when I'm not near a WiFi AP. I wanted to point it out just in case, better to have it working before it's necessary.
Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.
IRC channel on FreeNode is setup: #rugby-pro-dev for those that are interested.
Motorhead1991 said:
Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.
Click to expand...
Click to collapse
I think we should be covered at the moment. The first priority will likely be getting a recovery nailed down and 100% before working on a customized kernel. I'm hoping to get recovery nailed sooner than later so we can do things like nandroid and similar before starting in on CM10 or another ROM.
I am also working on the Rugby Smart (apache) CM9/3.0 Kernel/CM10 stuff as well so my time with the Pro is limited at the moment. Hopefully the Smart stuff moves quickly so I can loop back around to the Pro quickly.
>I pulled that package as well. Unfortunately it is only the GPL components they are >required to release, not the full ROM sources.
Ah, learn something new every day.
>I was thinking of setting up an IRC channel on FreeNode for discussing work on the >device. Would you be interested / willing to move some of the interactive discussion >over there once I have a channel setup?
Sure, I already monitor #opennic on freenode, so I can just open another channel.
kemonine96 said:
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.
Click to expand...
Click to collapse
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."
MCKINLEC said:
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."
Click to expand...
Click to collapse
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?
kemonine96 said:
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?
Click to expand...
Click to collapse
Thanks, but I made a backup copy, Think the issue could be because it was deleted instead of frozen?
ETA, help, donation etc
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
@kemonine96 et.al.:
When do you think a beta CM port will be ready?
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....
goldenlederhosen said:
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
Click to expand...
Click to collapse
You are not alone in that sentiment. I won't run a device I know won't receive a CyanogenMod port. The good news is as long as there is root, CyanogenMod can be made to work.
goldenlederhosen said:
When do you think a beta CM port will be ready?
Click to expand...
Click to collapse
"Soon". Myself and a couple others are working on a set of changes for the Rugby Smart (predecessor to the Pro) and once they are further along I will be looking into starting the CyanogenMod port for the Pro.
goldenlederhosen said:
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Click to expand...
Click to collapse
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
goldenlederhosen said:
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....
Click to expand...
Click to collapse
As much as I may appreciate a donation, please hold off as I cannot commit to working on CyanogenMod for the Pro in a paid capacity I am comfortable with. I am working 50-60 hour work weeks at my day job so my free time is severely limited. I have every intention on bringing CyanogenMod to the Pro but it is a free time problem more than anything else.
Foreign anglopu
kemonine96 said:
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
Click to expand...
Click to collapse
Okay, will do.

[APP] QuickRemote IR Blaster for AOSP roms

Hi everybody! I've switched over to CM 10.2 M1 as my daily driver, but I missed being able to change the volume on my tv with my phone. So, I've managed to get the QuickRemote app from the stock ROM working on Cyanogenmod (and hopefully other AOSP roms). There is nothing carrier-specific in this, so it should work on all variants.
Luckily there is no kernel module involved in driving the IR hardware. Instead the IR chip is a black box that is controlled via an internal serial port interface. The QuicksetSDK.apk package includes the code to control the IR chip. It creates a Service that the LGQRemote.apk app binds to to send commands to the IR hardware.
Installation
This will only work on rooted devices.
To get this working you'll need to install two APKs:
QuicksetSDK.apk
LGQRemote.apk
You'll also need to add a script that runs on device boot.
You can download mine here: 10QuickRemote
Or just make one yourself, containing this code:
Code:
#!/system/bin/sh
chmod 666 /dev/ttyHSL1
setprop persist.sys.lge.eula_agreement true
This makes the serial port accessible to non-system processes. On the LG stock rom the QuicksetSDK package runs as the system user, but here we're running it as a normal unprivileged user, so we need to make the serial port world-readable and writable. We also use the 'setprop' command to tell the QuickRemote app that we've agreed to LG's EULA, otherwise it will attempt to launch a non-existent EULA activity and crash.
I'm not 100% sure how the init.d system works on other AOSP roms, but on Cyanogenmod, you can place this script in the /data/local/userinit.d directory (creating the userinit.d directory if necessary). The script should not have an extension, and should be executable.
A quick method that works on CM, assuming you've downloaded my 10QuickRemote script to your current directory:
Code:
adb root
adb shell "mkdir -p /data/local/userinit.d"
adb push 10QuickRemote /data/local/userinit.d
adb shell "chmod 755 /data/local/userinit.d/10QuickRemote
For the above to work, you'll need to enable root for adb in Settings > Developer Options > Root Access
After a reboot, you should be able to use the QuickRemote app just like on the stock ROM!
If the app crashes right away, or if it launches but won't send any IR commands or learn new ones, your start-up script probably isn't being executed properly. Try running it manually and see if things work:
Code:
adb shell
--- inside adb, as root:
# sh /data/local/userinit.d/10QuickRemote
# ls -l /dev/ttyHSL1
-- result should be:
crw-rw-rw- system system 245, 1 2013-11-06 08:20 ttyHSL1
# getprop persist.sys.lge.eula_agreement
-- result should be:
true
If running it manually works, make sure the script is executable or it won't be called automatically on boot:
Code:
-- inside a root shell
# chmod 755 /data/local/userinit.d/10QuickRemote
If it is executable and still doesn't work after a reboot, and you're running a non-Cyanogen ROM, they probably do init scripts differently. Hopefully you can google up how to make it work
If everything looks correct and it still won't work, send me a logcat and I'll try to figure it out.
Enjoy!
sefnap said:
Hi everybody! I've switched over to CM 10.2 M1 as my daily driver, but I missed being able to change the volume on my tv with my phone. So, I've managed to get the QuickRemote app from the stock ROM working on Cyanogenmod (and hopefully other AOSP roms). There is nothing carrier-specific in this, so it should work on all variants.
Luckily there is no kernel module involved in driving the IR hardware. Instead the IR chip is a black box that is controlled via an internal serial port interface. The QuicksetSDK.apk package includes the code to control the IR chip. It creates a Service that the LGQRemote.apk app binds to to send commands to the IR hardware.
Enjoy!
Click to expand...
Click to collapse
thanks so much!!
would it be possible to make this into a flashable zip?
just a quick question am i suppose to see the list of make and models? if so i dont see it... the remote is installed though
nvm... some how the list came out.. not sure what i did. thx for the mod
blkghost22 said:
just a quick question am i suppose to see the list of make and models? if so i dont see it... the remote is installed though
nvm... some how the list came out.. not sure what i did. thx for the mod
Click to expand...
Click to collapse
I have the same issue. You just keep playing around with it?
Sent from my LG-VS980 using Tapatalk
steveo17 said:
I have the same issue. You just keep playing around with it?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.
blkghost22 said:
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.
Click to expand...
Click to collapse
Right i installed it by clicking the apk and installed it like normal. And now it works
Sent from my LG-VS980 using Tapatalk
steveo17 said:
Right i installed it by clicking the apk and installed it like normal. And now it works
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
for some reason tho... once i reboot my phone. i need to install that again.
awesome job!
I've been leery of flashing a custom rom for the lack of IR and other features. Plus I'm really digging the stock rom.
But with AOKP coming soon, I am might be tempted. Good to know that the application works with directly with the IR blaster.
I thought AOSP 4.4 was suppose to have support for IR blasters, but it seems noone has them working on CM yet.
blkghost22 said:
for some reason tho... once i reboot my phone. i need to install that again.
Click to expand...
Click to collapse
Same here
Sent from my LG-VS980 using Tapatalk
blkghost22 said:
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.
Click to expand...
Click to collapse
The list is actually downloaded by the QuicksetSDK app at runtime. I guess they did it that way so they could add models after shipping the phone.
I hope make flash.zip it is easy
Set this up on my D801, works great! It's a little difficult to navigate sometimes because some of the coloring of menus is designed for the stock rom. It seems to be missing the Comcast cable box settings though, it could be possible the app is different on different phones. Either way I just made it "learn" buttons over my TV remote which works way better than the short while I had it on the stock rom. This is the only feature I miss at all from stock, now my phone has every feature I want!
It's really not difficult to use a little terminal/command prompt, people are scared of putting in commands for some silly reason. If you've used ioroot, you already have adb to use too.
nice job!
i made a quick flashable zip package:
http://www43.zippyshare.com/v/86147127/file.html (new slim mod)
-> http://forum.xda-developers.com/showpost.php?p=47500016&postcount=94
(installs in data partition so it should survive a rom update)
RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
I get this
Sent from my LG-G2 using XDA Premium 4 mobile app
RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
I tried flashing this zip and working fine on mine thank you!
Sent from my LG-D802 using xda app-developers app
RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
Flashable works gr8 here as well.... have not rebooted to make sure everything sticks though... tnx guys!
zplit said:
I get this
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
which recovery?
which rom?
did you do a manual installation before flashing the zip?
thank you SO MUCH sefnap! and thank you RieGo for the flashable zip. just flashed on PA 4.3 for D801 and everything is working beautifully.
and as mentioned above- if there's any way you could get the lg camera to work, too, you would be the king. it looks like some sort of progress has been made over in this thread. the AOSP camera works well, but i'd love to have the manual focus option, and so on.
thanks again for adding this great functionality back for us! :good:
Thanks. Flashable zip works perfectly with slimbean on D801. This was the only thing I was missing with AOSP. Thanks again
LG D801 on Slimbean
A camera port with official firmware LG can not? If you can, do it please.
And that zip up to 160 MB? Driver? Replacing the files?

(needed) Developer willing to port custom recovery to the galaxy tab 4 8.0

Hi there are a few version of the Galaxy Tab 4 8.0 that have no support for a custom recovery.
Source files have been found and are ready to be worked with.
The devices we would like to bring support to are the:
T330NU source file:
http://www.4shared.com/zip/UG28maH2ce/SM-T330NU_NA_KK_Opensource.html
T335K source file:
http://www.4shared.com/zip/9Y4qzw1zce/SM-T335K_KK_Opensource.html
T335L source file:
http://www.4shared.com/zip/nZ4xmfNgba/SM-T335L_KK_Opensource.html
T337a source file:
http://www.4shared.com/zip/21kf9dZYce/SM-T337A_NA_KK_Opensource.html
Boot.img dumped from device T330NU:
http://www.4shared.com/file/nOAtJQbCba/boot.html
Recovery.img dumped from device T330NU:
http://www.4shared.com/file/mSkFIM0Bce/recovery.html
If ANYONE is willing or knows someone who could be willing to port a custom recovery to these devices it would be greatly appreciated if you could pass on the message and spread the word. If we all do work together we should be able to get this done.
There are many people who are willing to test the final work. Thanks in advance.
Hey, I am dedicated to get a recovery for this device also. I am pretty good with computers but have never worked on a recovery project. I do have Linux and can help if needed on anything.
There should be a guide on xda
smknutson said:
There should be a guide on xda
Click to expand...
Click to collapse
I tried recovery builder but had no luck. Was not able to download files after building. Says build has been queud or something like that. Was having trouble getting the stock recovery img off of the phone.
Leonidas87 said:
I tried recovery builder but had no luck. Was not able to download files after building. Says build has been queud or something like that. Was having trouble getting the stock recovery img off of the phone.
Click to expand...
Click to collapse
I have my stock recovery.img if needed
pre4speed said:
I have my stock recovery.img if needed
Click to expand...
Click to collapse
Which Galaxy tab version do you have?
And have did you extract your stock recovery img?
Leonidas87 said:
Which Galaxy tab version do you have?
And have did you extract your stock recovery img?
Click to expand...
Click to collapse
I have the 337a and yup pulled recovery.img and boot.img
pre4speed said:
I have the 337a and yup pulled recovery.img and boot.img
Click to expand...
Click to collapse
My last message had a spelling mistake sorry about that. How did you pull those files tho? I've been having trouble on this device
Leonidas87 said:
My last message had a spelling mistake sorry about that. How did you pull those files tho? I've been having trouble on this device
Click to expand...
Click to collapse
In terminal, type su dd if=/dev/emmc/"boot partition" of=/sdcard/recovery.img
I think you need to enter after su. It will save it to your sd. This is assuming root. You enter your boot partition in the quotes. Use this to find your partitions.
https://play.google.com/store/apps/details?id=com.cls.partition
pre4speed said:
In terminal, type su dd if=/dev/emmc/"boot partition" of=/sdcard/recovery.img
I think you need to enter after su. It will save it to your sd. This is assuming root. You enter your boot partition in the quotes. Use this to find your partitions.
https://play.google.com/store/apps/details?id=com.cls.partition
Click to expand...
Click to collapse
Thanks for the help I think I understand. I have terminal ready and the app installed. Just not sure which partition is the one to fill in the quotations in the terminal.
I'm attaching pictures if that helps.
Also I'm sure I do not include the actual quotes when typing in terminal just to save myself from confusion. I do have root by the way
UPDATE:
THESE PICTURE WERE FOR MY GALAXY NOTE 3 DISRAGAURD THESE PHOTOS. My mistake I was on my phone when I read the message and tried to jump right into it
THERE ARE THE PHOTOS FROM MY GALAXY TAB 4.
These would be the correct locations I need clarification so I know which ones are boot and recovery for pulling/extracting in terminal.
These two represent your recovery and boot partitions. So in the quotes you'll put the mmcblk0p15 for recovery.img.
I found that pulling the recovery is that exact code, whereas pulling the boot was a different code, but found easily on the internet. I got the recovery easy, the boot was a little more work, but did get it.
pre4speed said:
These two represent your recovery and boot partitions. So in the quotes you'll put the mmcblk0p15 for recovery.img.
I found that pulling the recovery is that exact code, whereas pulling the boot was a different code, but found easily on the internet. I got the recovery easy, the boot was a little more work, but did get it.
Click to expand...
Click to collapse
Think I am not typing it exactly how it needs to be. Even tried copy and pasting. So close but yet so far lol. I really think we have all been making progress the last few days. This would help if I could get it to work. Would be useful and handy to have a backup for each device variation.
Pic did not upload for me the first time. Backup did not work yet. I must be typing or copy and pasting wrong
I'm trying to remember how I did it. I believe you open terminal, type su then press enter, then type the rest. Let me do it again and see what my steps were.
---------- Post added at 01:26 PM ---------- Previous post was at 01:13 PM ----------
Ok, I'm sorry. The code I gave you is actually for the boot.img not recovery. Here is the right code. Sorry again.
Type it exactly as I did and you'll find the backup on your sdcard (not external). I actually found the correct code in the 7.7" tab thread. Lol http://forum.xda-developers.com/showthread.php?t=1540641
pre4speed said:
I'm trying to remember how I did it. I believe you open terminal, type su then press enter, then type the rest. Let me do it again and see what my steps were.
---------- Post added at 01:26 PM ---------- Previous post was at 01:13 PM ----------
Ok, I'm sorry. The code I gave you is actually for the boot.img not recovery. Here is the right code. Sorry again.
Type it exactly as I did and you'll find the backup on your sdcard (not external). I actually found the correct code in the 7.7" tab thread. Lol http://forum.xda-developers.com/showthread.php?t=1540641
Click to expand...
Click to collapse
I'm just out right now but will give it a try as soon as I get home. Thanks again much help. Will report back.
Leonidas87 said:
I'm just out right now but will give it a try as soon as I get home. Thanks again much help. Will report back.
Click to expand...
Click to collapse
Ok I have got both recovery and boot.img backed up/pulled. Finally lol thanks a lot
I think we have most of the necessary files to get the job done. If you say you have got you boot.img and recovery backed up and so do I. We have source files also. All we need now is for the recovery to be compiled. For a skilled experienced developer to finish up what we started probably would not be too hard. If only we had someone to really take the time with us with some of the next key steps. I am looking up guides and resources all over the Internet but nothing concrete to get the job done ?
Leonidas87 said:
I think we have most of the necessary files to get the job done. If you say you have got you boot.img and recovery backed up and so do I. We have source files also. All we need now is for the recovery to be compiled. For a skilled experienced developer to finish up what we started probably would not be too hard. If only we had someone to really take the time with us with some of the next key steps. I am looking up guides and resources all over the Internet but nothing concrete to get the job done ?
Click to expand...
Click to collapse
Yeh, I hear that. Like I said before, I've got my buddies looking at it, but these devices that they don't own aren't a priority for them. I don't feel right bugging them about it every day. I'll see if there's anything I can find. I'm not a developer and get lost with code, but guides I can help to find if you have the build environment.
http://rootzwiki.com/topic/23903-how-to-compile-twrp-from-source/
http://forum.xda-developers.com/showthread.php?t=1943625
I am so lost with all that[emoji30]
Leonidas87 said:
Hi there are a few version of the Galaxy Tab 4 8.0 that have no support for a custom recovery.
If ANYONE is willing or knows someone who could be willing to port a custom recovery to these devices it would be greatly appreciated if you could pass on the message and spread the word. If we all do work together we should be able to get this done.
There are many people who are willing to test the final work. Thanks in advance.
Click to expand...
Click to collapse
if you are able to install an omnirom build environment on linux i will make you a local_manifest and show how to build.

Kyocera DuraForce Super Thread

Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
There is a Lollipop update available for the device as of early February, 2016. I have found a way for users to update if the OTA fails (see below). I've also updated the below posts with information regarding the Lollipop update and moved the KitKat notes to another location (link for old notes is below)
Ota - lmy47v1218_2217
For those who are having trouble applying a FOTA on the DuraForce, check /cache/fota/xyz_fotalog_123.dat It's a text file that contains a lot of really good info on what is going on during a FOTA. Including errors. Keep a look out for signature mismatch errors.
I had errors with the following files. Took me a few tries to get the OTA applied as each attempt resulted in one error.
Uninstall Xposed (moar hacks)
/system/usr/keylayout/gpio-keys.kl (disable PTT/Speaker buttons)
/system/etc/permissions/platform.xml (sd card "fix")
If trying to address the issues manually does not work, follow the procedure below.
Download "vanilla" system image from HERE (link)
Extract zip file
Ensure at least 2Gb of storage is available for internal data
adb push mmcblk0p21_KVT49L_0617_0132 /storage/sdcard0/
adb shell
su
dd if=/storage/sdcard0/mmcblk0p21_KVT49L_0617_0132 of=/dev/block/mmcblk0p21
Reboot phone once it completes. It will take awhile and not report anything during the process.
After phone boots, run "adb reboot recovery"
Wipe data / factory reset
Wipe cache
Reboot
Run software update
General Notes - Lolipop
Force Reboot: Pwr + Vol Up + Vol Dn + Back + Home + App Switcher buttons for ~10-30 seconds
Root: Use KingRoot from http://king-root.net/ -- I used the android APK successfully
SD cards bigger than 32Gb still do not work correctly on stock firmware
Known Working Customizations
To be determined
KitKat Notes
All previous notes for KitKat have been moved to a document in box. The notes can be found HERE (link)
Sources / Mirror(s)
The OSS drop is available on Kyocera's developer site: http://www.kyoceramobile.com/support/developers/
Misc file mirror: https://nuskunetworks.box.com/s/p5hwq3hboctl0saze0wkcv3jzfefuw45
Do you trust Kingo?
I'm THRILLED to hear you were able to root and freeze all the AT&T crapware. I can't wait to do the same. But how do you feel about Kingo? I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
kemonine96 said:
Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
If you're looking for root, look no further than Kingo. I can confirm the Windows version of Kingo is working on the AT&T varient of the DuraForce.
Click to expand...
Click to collapse
tomzweifel said:
How do you feel about Kingo?
Click to expand...
Click to collapse
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
tomzweifel said:
I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
Click to expand...
Click to collapse
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Components to clean up?
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
kemonine96 said:
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Click to expand...
Click to collapse
tomzweifel said:
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
Click to expand...
Click to collapse
Unfortunately I don't have notes on what Kingo leaves around on /system... Some searching online or poking about /system should yield results.
New OTA Update
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
tomzweifel said:
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
Click to expand...
Click to collapse
Please do. I haven't gotten any notifications yet and I'm kinda curious what the OTA will contain.
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Dkesler76 said:
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Click to expand...
Click to collapse
Thanks for the heads up. Too bad it's not L.
kemonine96 said:
Thanks for the heads up. Too bad it's not L.
Click to expand...
Click to collapse
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to free up some time this weekend and I'm going to be pulling the OTA and seeing what I can do for re-packing it for those of us who are rooted and/or de-bloated.
Will post back with more info after I've had some time to poke at the OTA some.
Edit 1: Looks like this has patches for system and boot. /cache/delata looks like the directory where everything was downloaded. Hopefully binwalk and some other tools will yield useful information on what's contained within.
Edit 2: Looks like I was able to install the OTA despite being rooted. I'm waiting for 1st boot to verify root persisted and I'm also working on mirroring a number of partitions that can be used to "go back" to stock as well as images for updated partitions post-OTA.
Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Good news everybody! The ATT OTA doesn't remove root and can be installed as-is provided you've not de-bloated the ROM or installed Xposed. If you've de-bloated (see below) you'll need to restore the missing bloatware and if you've installed Xposed, you'll need to uninstall it prior to applying the OTA.
In one of the early OP's there's a link to the "misc file mirror" that contains partition images for boot and system partitions. These are from an ATT device and can be used to restore back to a state that'll allow the OTA to apply.
Happy hacking and OTAing everyone.
kemonine96 said:
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Click to expand...
Click to collapse
weird i tried dd and busy box and no go not showing up on device
Dkesler76 said:
weird i tried dd and busy box and no go not showing up on device
Click to expand...
Click to collapse
What isn't showing up?

Categories

Resources