I was able to take a base from another XDA Dev (Thanks graffixnyc)
Script Modifications:
Mount points
Build.Prop check was removed until I find the correct ID for the Verizon M8
boot.img was removed
Working:
Boots
Bluetooth
Not working:
Camera
No cellular connection (No Data/Text/Calls)
GPS
Download: Link
MD5: bc44801ce43752e36375cfa6fb43ae1d
I think this will make a good base to help with further GPE development on the Verizon M8!
Flash at your own risk - I am not responsible for bricked devices. CWM Backup is HIGHLY recommended.
Correct ro.build.product name: htc_m8wl (Will be added on next update)
SELECT YES WHEN CWM ASKS YOU ABOUT RECOVERY REPLACEMENT.
Originally from @myn in your other thread OP
myn said:
Love to see threads like this
For the data/cell, move over the libril* file(s) in /system/lib from our Verizon stock ROM to the GPE ROM (do one at a time) and see if that fixes the issue with data. Also may want to verify the build.prop references the appropriate RIL ffilename if different from in GPE build.prop.
For SMS/MMS, try moving the *apns* files from /system/etc on our Verizon stock rom to GPE and again see if that fixes the SMS/MMS issue. If that doesn't resolve it, it's probably buried in the framework-res.apk under /xml/. You could try extracting the contents of the Verizon framework-res.apk and simply copy over the /xml/apns.xml into the GPE framework-res.apk.
Biggest advice I can give you is only move and test 1 file at a time. Sounds Tedious but it will save you sooo much time in the long run.
Good to see you working on this
Click to expand...
Click to collapse
Sent from my XT1060 using Tapatalk
If you needed the mount points for our device, I pulled them a while back.
http://forum.xda-developers.com/showthread.php?p=51479859
[MOUNTPOINTS] HTC One M8
Not sure if they are different from the base device in which this gpe base came from
-HTC One m8-
I was waiting for this! Thanks for kicking it off, I will be more than happy to test for you when it gets to that point.
chriskader said:
I was able to take a base from another XDA Dev (Thanks graffixnyc)
Script Modifications:
Mount points
Build.Prop check was removed until I find the correct ID for the Verizon M8
boot.img was removed
Working:
Boots
Bluetooth
Not working:
Camera
No cellular connection (No Data/Text/Calls)
GPS
Download: Link
MD5: bc44801ce43752e36375cfa6fb43ae1d
I think this will make a good base to help with further GPE development on the Verizon M8!
Flash at your own risk - I am not responsible for bricked devices. CWM Backup is HIGHLY recommended.
Click to expand...
Click to collapse
I will get working on this tonight when I get home.
JWhetstone02 said:
If you needed the mount points for our device, I pulled them a while back.
http://forum.xda-developers.com/showthread.php?p=51479859
[MOUNTPOINTS] HTC One M8
Not sure if they are different from the base device in which this gpe base came from
-HTC One m8-
Click to expand...
Click to collapse
The needed mountpoints where modified in the install script but thanks for the info!
And here we go.
Sent from my HTC One M8!
U WOT M8?
Will this work with data for a Verizon m8 on tmobile
Sent from my HTC6525LVW using Tapatalk
sgtmedeiros said:
Will this work with data for a Verizon m8 on tmobile
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Data is not working period....will be soon though. Give it time.
I didn't know if gsm was broken as well. No problem man take time
Sent from my HTC6525LVW using Tapatalk
sgtmedeiros said:
I didn't know if gsm was broken as well. No problem man take time
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
It is not the cdma or the gsm radio.......basically it is like the drivers for it. The hardware it there and it works, but without the drivers you can't use it. But we will have it working soon...I'll be on it all night and tomorrow since I finally get a day off. So unless someone beats me to it you can expect most of it to be working tomorrow.
Hey, you beat me to it! I started working on a GPE port last night, but didn't get anything finished. I'm downloading this now, and have gobs of experience fixing data between carrier versions of HTC devices - down to rewriting most of telephony-common.jar from scratch for my MIUI port.
In short...today is my birthday so I'll be out celebrating, but I'll see what I can do with this if time allows. I've got a good idea which bins and libs are required to make data happen, so I'll see if I can't help out.
androidoholic said:
It is not the cdma or the gsm radio.......basically it is like the drivers for it. The hardware it there and it works, but without the drivers you can't use it. But we will have it working soon...I'll be on it all night and tomorrow since I finally get a day off. So unless someone beats me to it you can expect most of it to be working tomorrow.
Click to expand...
Click to collapse
I have been copying .lib files from stock to GPE without luck. Since this is my main device I have to be careful about how much down time this phone has
androidoholic said:
It is not the cdma or the gsm radio.......basically it is like the drivers for it. The hardware it there and it works, but without the drivers you can't use it. But we will have it working soon...I'll be on it all night and tomorrow since I finally get a day off. So unless someone beats me to it you can expect most of it to be working tomorrow.
Click to expand...
Click to collapse
There's been occasions where the drivers have to be written from scratch for HTC because they are not open source. Hopefully we don't get stuck there
Sent from my HTC6525LVW using Tapatalk
digitalhigh said:
Hey, you beat me to it! I started working on a GPE port last night, but didn't get anything finished. I'm downloading this now, and have gobs of experience fixing data between carrier versions of HTC devices - down to rewriting most of telephony-common.jar from scratch for my MIUI port.
In short...today is my birthday so I'll be out celebrating, but I'll see what I can do with this if time allows. I've got a good idea which bins and libs are required to make data happen, so I'll see if I can't help out.
Click to expand...
Click to collapse
happy birthday!! i have it downloaded ima take a peak inside also. thanks for the bring up Op!
Is it just me or is this like a 4 hour download?
androidoholic said:
Is it just me or is this like a 4 hour download?
Click to expand...
Click to collapse
Pick a different mirror. Il number eight is usually pretty quick.
Sent from my HTC6525LVW using xda app-developers app
Ok
Sent from my HTC6525LVW using Tapatalk
I ordered a SIM adapater. Once it comes in I can swap between my M8, S4 and Galaxy Nexus. That will let me work and get this thing going faster as I Do not need to worry about my phone being down. 2 M8s would be even better though
This wouold be aweseome @scrosler would be good at this I know it has to do with porting modems and such he needs to stop slacking
Related
I don't have one, but should work out just fine.
Let me know if you have problems.
These ROMs are the T-Mobile Stock ROMs with a few additions:
- Deodexed for custom skins and ease of portability
- Root
- BusyBox Added
4.0.4
http://goo.im/devs/childofthehorn/espresso10tmo/ROMS
Thanks Child, hope your weekend is going well.
Sent from my ADR6400L using xda app-developers app
Getting errors when trying to flash this. Ignore the md5 mismatch, sadly my backup decided to die and now I can get to recovery but stuck there. Hope I can get the rom to flash with help.
Sent from my ADR6400L using xda app-developers app
There is no md5 sum present, so yeah.... Just a signed zip!
The assert is at the top and based off what was in the ATT variant.
If you remove that assert in the updater script, should be fine.
However, those values match what I saw in the build.prop......hmmmmm. I'll have it in the morning for yah!
Sent from my Galaxy Nexus using Tapatalk 2
Childofthehorn said:
There is no md5 sum present, so yeah.... Just a signed zip!
The assert is at the top and based off what was in the ATT variant.
If you remove that assert in the updater script, should be fine.
However, those values match what I saw in the build.prop......hmmmmm. I'll have it in the morning for yah!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I know the md5 is me trying to restore a backup and it failing. I tried to flash the from afterwards to take the picture as once I realized I wanted to show you. No worries or rush at all, I am just thankful for any help
Sent from my ADR6400L using xda app-developers app
Glad to see a start
I just ordered a tab 2 and was kind of sad nobody was working on it at all...and saw this post today and jumped for joy and thought "atleast someone is doing some sort of work on it..and this is a great start....did the t-mo version get 4.1 yet? I hope someone kangs an AOSP rom for some 4.2.1 love...(prob to high of a hope) but I'm glad to see this atleast...so atleast i'll have some wiggle room..but saw a poster was having issues..and don't want to get stuck in his shoes..so i'll wait to flash...and or do anything..seen as there is no odin restore stuff or lots of roms that are known to work and stable and the like.....
Thanks for starting the game tho!!!!
Hellation,
That updater script is 100% correct. Had a user PM me.
Your Backup must have failed and/or you flashed something you shouldn't have.
You need to remove the "assert" line in the top of the updater script (unzip /META-INF/com/google/updater-script. Your issue could be that it cannot read itself right now.
Re-zip the whole thing and try again.
You have no readable props right now, or the readable props are wrong...
Childofthehorn said:
Hellation,
That updater script is 100% correct. Had a user PM me.
Your Backup must have failed and/or you flashed something you shouldn't have.
You need to remove the "assert" line in the top of the updater script (unzip /META-INF/com/google/updater-script. Your issue could be that it cannot read itself right now.
Re-zip the whole thing and try again.
You have no readable props right now, or the readable props are wrong...
Click to expand...
Click to collapse
I ended up reverting back to bare stock through odin, will give this another shot soon as I'm home again and can fully sit down. I'm sure it works and I feel might of been my tablet, all are different. Thank for all our time and I will report back once I manage to get back and tinker with my tablet once more.
Re: No wifi
Hey Bro, sorry 2 bug again but I got the new uploaded zip file you uploaded (thanks for that) and it works but now the wifi doesnt work...ive tried wiping the device then tried flashing the rom again but still no wifi PLEASE HELP
Maybe if u have a nandroid back up u can upload that would be great or maybe a stock zip?
thanks alot
EDIT: IM SORRY I POSTED IN THE WRONG THREAD..i HAVE the AT&T tab 2 10.1...
Hellation said:
I ended up reverting back to bare stock through odin, will give this another shot soon as I'm home again and can fully sit down. I'm sure it works and I feel might of been my tablet, all are different. Thank for all our time and I will report back once I manage to get back and tinker with my tablet once more.
Click to expand...
Click to collapse
did you ever get this to work? I haven't seen any posts from Childofthehorn in a while, but i wanted to try this out.
rmancl said:
did you ever get this to work? I haven't seen any posts from Childofthehorn in a while, but i wanted to try this out.
Click to expand...
Click to collapse
Getting back to you, I sold my T-Mobile model and got a Wi-Fi only one. I was never able to get it to flash. Kept getting Status 7 each time I did.
Sent from my ADR6400L using xda app-developers app
Hellation said:
Getting back to you, I sold my T-Mobile model and got a Wi-Fi only one. I was never able to get it to flash. Kept getting Status 7 each time I did.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
thanks for letting me know, i am going to work on my own rom now. I want to port over cm10
I finally got wifi calling extracted, ported and flashable. Currently for "stock" custom Sense 4+ ROMs and Sense 5 as well.
Haven't tried trickdroid or viper, but i'll get a version for viper posted soon.
Make a nandroid first, then flash the appropriate zip in recovery. Let me know if there are any issues.
T-Mobile wifi calling for Sense 5
T-Mobile wifi calling for Sense 4+
I'm sure this will be very useful for all the TMoUS users that miss the ability of WiFi calling on Sense 5 ROMs
deleted
Trying this out on TrickDroid sense 5. Will report back.
Sent from my HTC One S using xda app-developers app
This is what I get after flashing on TrickDroid:
Sent from my HTC One S using xda app-developers app
ryanshew said:
I finally got wifi calling extracted, ported and flashable. Currently for "stock" custom Sense 4+ ROMs and Sense 5 as well.
Click to expand...
Click to collapse
Did you extract from the HTC one t-Mobil version to ?
Flashalot said:
Did you extract from the HTC one t-Mobil version to ?
Click to expand...
Click to collapse
Yes, sense 5 is from the one.
ryanshew said:
Yes, sense 5 is from the one.
Click to expand...
Click to collapse
But I decompiled our framework2.jar and added the necessary smali to it. Otherwise wifi calling would work, but would not connect to regular phone network, kept scanning the Sim every 30secs or so.
I'm gonna try with an aosp ROM just to see what happens, maybe collect that bounty:beer:
I don't even have T-Mobile, but everyone said it can't be done and I like a challenge, just couldn't get it out of my head, same with the small apps and the volume cursor on my ROM. My first adventures in the horrible land of smali.
cougzzz said:
This is what I get after flashing on TrickDroid:
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
You need one of the newer sims, call T-Mobile. For more info, do a search on xda or Google...it seems to be somewhat common issue.
I wasn't sure if trickdroid had a modified framework2.jar, that's why I wasn't sure if it would work, but I can modify almost any framework2.jar if someone had a particular one they want done, just post it for me.
ryanshew said:
I'm gonna try with an aosp ROM just to see what happens, maybe collect that bounty:beer:
I don't even have T-Mobile, but everyone said it can't be done and I like a challenge, just couldn't get it out of my head, same with the small apps and the volume cursor on my ROM. My first adventures in the horrible land of smali.
Click to expand...
Click to collapse
Well it has been done by a Great dev (he should not be not named ) But lets not start this again
And hope you get it to
Sent from my Infected Evo 3D
Just to let you know, just flashed into viper 2.2.0 and it is working well. Thank you.
Sent from my HTC One S using Tapatalk 4
ryanshew said:
But I decompiled our framework2.jar and added the necessary smali to it. Otherwise wifi calling would work, but would not connect to regular phone network, kept scanning the Sim every 30secs or so.
I'm gonna try with an aosp ROM just to see what happens, maybe collect that bounty:beer:
I don't even have T-Mobile, but everyone said it can't be done and I like a challenge, just couldn't get it out of my head, same with the small apps and the volume cursor on my ROM. My first adventures in the horrible land of smali.
Click to expand...
Click to collapse
Way way way prefer smali to APKTool, doesn't even work for me. I had fun removing this tweak from my ROM, took effort but was worth it in the end.
/OT
usaff22 said:
Way way way prefer smali to APKTool, doesn't even work for me. I had fun removing this tweak from my ROM, took effort but was worth it in the end.
/OT
Click to expand...
Click to collapse
I was talking about smali code in general. I always use apk tool to decompile for smali edits as well as xml.
ryanshew said:
I was talking about smali code in general. I always use apk tool to decompile for smali edits as well as xml.
Click to expand...
Click to collapse
Ah, OK. I use a different tool for smali since APKTool spews out errors when attempting to do anything.
Sent from my HTC One S using Tapatalk 4
ryanshew said:
I was talking about smali code in general. I always use apk tool to decompile for smali edits as well as xml.
Click to expand...
Click to collapse
Why not use vts by diamondback its a great tool
Sent from my HTC VLE_U using Tapatalk 2
I tried on magio Rom but keep getting invalid sim. Thanks for the work thou hopefully there can be a fix for this.
rc420head said:
I tried on magio Rom but keep getting invalid sim. Thanks for the work thou hopefully there can be a fix for this.
Click to expand...
Click to collapse
Ryan said we need a new sim card from tmobile.
Sent from my HTC One S using xda app-developers app
cougzzz said:
Ryan said we need a new sim card from tmobile.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
This is a brand new simple card. WiFi calling works fine on Mkinney88's tmous jb rom
rc420head said:
This is a brand new simple card. WiFi calling works fine on Mkinney88's tmous jb rom
Click to expand...
Click to collapse
Ah Icic then hopefully we see a fix for this. Would love to use wifi calling in my reception depleted area.
Sent from my HTC One S using xda app-developers app
Well, I can safely say this doesn't work on ASOP ROMs, ended up really dorking up my HOS running Odyssey. But I'm hopefully it can somehow be modified for them as well. TMOUS is horrible in my area....but the pricing is great.
Not working speaker during call,FC sometimes.
Is expected 3G version?
BrateloSlava said:
Is expected 3G version?
Click to expand...
Click to collapse
Yes.Its for both version
Well done, great!
You plan to release a test build?
God even more good news. Hope to see more of this. Keep up the great work!
Sent from my HTC One SV using xda app-developers app
Until the moment finishing this version to a healthy state ... Sources and collected version given to those who can really assist in improvement.
Those who want to help - write to me or rollon76.
Best way. I think you will get it work!
Great work guys! I cannot wait for the first release let's get rid of the HTC sense malware
Nice work men! I didn't expect such good news these days. I'm waiting..
Sent from my HTC One SV using Tapatalk 4 Beta
Just wow
You will make my day! I thought everyone forgot ONE sv but seems like I might get rid of Sense and get 4.3 after all--man can dream
Faith in htc one sv devs restored xD
I have high hopes now
*waiting impatiently*
Post the alpha version of CyanogenMOD 4.1.2 to identify errors and identify what is not working.
Logs and reported issues upload here.
To install, backup everything, after that make all the wipe.
At the moment does not work:
Bluetooth
Camera
Camcorder
LTE
What works
-Phone(with working incall speaker and mic)
-Wifi
-Sound
-Data (inside file manager)
-SMS
-Video Playback
-Charging
I do not advise to install this who do not understand what is Android!
Firmware is made for version with LTE (k2_ul).How it will work on version without LTE (k2_U) i dont know.
Install this at your own risk!
When you return to the Sense, LTE will not work. To restore it - reflash the radio.
https://docs.google.com/file/d/0B9DrEEiA1eKRaXBOc2xUbW9xVW8/edit?usp=sharing
rollon76, please keep us informed of any progress happily looking forward to your work!
Sent from my HTC One SV using Tapatalk
esp7 said:
rollon76, please keep us informed of any progress
Click to expand...
Click to collapse
The project is on hold. The author do not have time for it.
BrateloSlava said:
The project is on hold. The author do not have time for it.
Click to expand...
Click to collapse
So is it maybe possible to set up a github tree so someone else can have a look at it?
https://github.com/vl197602/vendor_onesv
https://github.com/vl197602/k2_ul
https://github.com/vl197602/local_manifest/tree/master
https://github.com/awid777/android_local_manifest/blob/htc_one_SV/local_manifest.xml
my manifest for 4.1.2 k2_cl
Any movement?! Any sign of life??
I think all gone for working on cm10.1, HOPEFULLY!
J.ali.li said:
Any movement?! Any sign of life??
I think all gone for working on cm10.1, HOPEFULLY!
Click to expand...
Click to collapse
We need a lot of kernel work and unfortunately this takes time on the plus side the kernel work being done is for 4.3
Sent from my C525c using xda app-developers app
waiting.
awidawad said:
We need a lot of kernel work and unfortunately this takes time on the plus side the kernel work being done is for 4.3
Sent from my C525c using xda app-developers app
Click to expand...
Click to collapse
Hope to get this soon.
There are now (at least) two working ROMs, here are links!
The general consensus of issues so far:
• SD card not working for some, others have it working
• Blutooth audio crackles a bit but functions
• Proximity sensor for phone calls doesn't turn screen off
Step 1: Download a ROM
Step 2: Download a 4.4 gapps file
Step 3: Download Loki-doki (only need to flash if you're using a ROM not specifically labelled AT&T)
Step 4: Wipe wipe wipe, Flash your ROM, GAPPs, and Loki if needed
Kejar31's Official Gummy ROM (pre-Loki'd)
http://forum.xda-developers.com/showthread.php?t=2524372
albinoman887's Unofficial CM11 ported by jamal2367 to the JFLTEXX (Loki Doki this ROM)
http://forum.xda-developers.com/showthread.php?t=2521384
Noobdev's Unofficial CM11 ported by bots to the JFLTEATT (pre-Loki'd)
http://sourceforge.net/projects/unofficial-cm/files/Nightlies/jflteatt/
XDA:
http://forum.xda-developers.com/showthread.php?t=2383143
Note:
The 11/12 (most recent as of now) update wasn't pushed to the servers on SF for Noobdev, here's a direct link -
s4.warpfactor10.com/jflteatt/20131112/cm-11-20131112-EXPERIMENTAL-noobdev-jflteatt.zip
Assuming builds will be uploaded here, you may want to use this link in the future for ATT builds if they're not on SF
http://s4.warpfactor10.com/jflteatt/
Paranoid Android GAPPS
(http://forum.xda-developers.com/showthread.php?t=2397942)
Loki-doki (Attached at bottom of OP)
(http://forum.xda-developers.com/showthread.php?t=2295557)
REMINDER
This is not a development thread, this is just me trying to get you guys a list of ROMs to use while the AT&T boards don't have any in them. If you find issues on the ROMs and want to bring their attention to the developers, post in the appropriate threads listed above. I am not a developer and I cannot code. I can try my best to help you with issues on your end though!
First
Sent from my SAMSUNG-SGH-I337 using Xparent Skyblue Tapatalk 2
I flashed albino mans latest in the tmo thread itvhas working camera. Just change the update script to jflteatt and flash latest supersu.
Switching from dalvik to art makes this thing suuuper fast. :good:
Flashed the latest on 1337m and it has working camera but no ext sdcard support so smooth and flawless
Sent from my SGH-M919 using xda app-developers app
I think that is no exfat support, if you format fat32 should be ok
I haven't got into the linked threads too much yet. But, that was the issue on some other roms.
Only speculating atm--
rugmankc said:
I think that is no exfat support, if you format fat32 should be ok
I haven't got into the linked threads too much yet. But, that was the issue on some other roms.
Only speculating atm--
Click to expand...
Click to collapse
if this is the same one from the TMO s4 thread. I had a question that seemingly was ignored over and over again. Snotty people over there *****ing about you ATT guys, but mine is a i337m jftlecan vs the jftlemob which it fails on when flashing because of being the wrong type of hardware. Is it simply a matter of switching the type in build prop or is there something I am missing?
phil.W said:
if this is the same one from the TMO s4 thread. I had a question that seemingly was ignored over and over again. Snotty people over there *****ing about you ATT guys, but mine is a i337m jftlecan vs the jftlemob which it fails on when flashing because of being the wrong type of hardware. Is it simply a matter of switching the type in build prop or is there something I am missing?
Click to expand...
Click to collapse
99%sure you just gotta fix the buildprop
Sent from my SGH-I337 using xda app-developers app
phil.W said:
if this is the same one from the TMO s4 thread. I had a question that seemingly was ignored over and over again. Snotty people over there *****ing about you ATT guys, but mine is a i337m jftlecan vs the jftlemob which it fails on when flashing because of being the wrong type of hardware. Is it simply a matter of switching the type in build prop or is there something I am missing?
Click to expand...
Click to collapse
Yeah, noticed the politeness or lack thereof. But, we have ours too.
I really don't know the answer. There was buildprop talk and a script change early on in one of the threads. But, that may have all changed. I am waiting a few days and hope to see something att flashable. Hopefully for yours too. On att we just have to flash loki-doki. I still may try if nothing comes out specifically for att soon. I didn't like the launcher on 4.4 when I was installing just some of the apk's on a GPE rom.
phil.W said:
if this is the same one from the TMO s4 thread. I had a question that seemingly was ignored over and over again. Snotty people over there *****ing about you ATT guys, but mine is a i337m jftlecan vs the jftlemob which it fails on when flashing because of being the wrong type of hardware. Is it simply a matter of switching the type in build prop or is there something I am missing?
Click to expand...
Click to collapse
Open the rom zip and you will see a meta folder. open com/google/android then copy the update script because if you try to edit within the zip it won't stick. (you can do this from your phone, i use file manager) and exit out and paste it somewhere outside the zip. edit the first three lines you'll see jfltetmo to jfltecan. now move back into the zip and delete the original and you should be good to flash.
Airtioteclint said:
Open the rom zip and you will see a meta folder. open com/google/android then copy the update script because if you try to edit within the zip it won't stick. (you can do this from your phone, i use file manager) and exit out and paste it somewhere outside the zip. edit the first three lines you'll see jfltetmo to jfltecan. now move back into the zip and delete the original and you should be good to flash.
Click to expand...
Click to collapse
What do you mean edit first 3 lines? Im on Canadian Rogers. Thanks
zecstone said:
What do you mean edit first 3 lines? Im on Canadian Rogers. Thanks
Click to expand...
Click to collapse
Have you got the update script open as a text? Once you do you will see at the very top where it says jfltetmo. There shoukd be three of them. Change all three to your model number. I'm assuming your model number is jfltecan?
Airtioteclint said:
Have you got the update script open as a text? Once you do you will see at the very top where it says jfltetmo. There shoukd be three of them. Change all three to your model number. I'm assuming your model number is jfltecan?
Click to expand...
Click to collapse
No this is my first three lines of the updater-script
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-
name/system", "/system");
package_extract_file("system/bin/backuptool.sh",
zecstone said:
No this is my first three lines of the updater-script
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-
name/system", "/system");
package_extract_file("system/bin/backuptool.sh",
Click to expand...
Click to collapse
Are you sure you downloaded the tmo rom? The international one probably don't have a security check which it looks like yours doesn’t. The reason we're flashing the tmo one is because it has working camera. The international one could have been updated by now with working camera though I'm not sure i don't go in there often. In any case you don't have to edit anything, just flash.
zecstone said:
What do you mean edit first 3 lines? Im on Canadian Rogers. Thanks
Click to expand...
Click to collapse
You are right I had the international rom, its running smooth. Will try the tmo version. Thanks
why go through so much trouble just to get a 90% working CM ROM?, just install a 4.3 GE edition, install the KitKat Apk's and you will get the same experience plus it will be %100 working no issues whatsoever. CM Roms have never been 100% working ROMS i think since version 7 they always have something not working or missing.
eortizr said:
why go through so much trouble just to get a 90% working CM ROM?, just install a 4.3 GE edition, install the KitKat Apk's and you will get the same experience plus it will be %100 working no issues whatsoever. CM Roms have never been 100% working ROMS i think since version 7 they always have something not working or missing.
Click to expand...
Click to collapse
That will get you the same expierience UI-wise, but there are under-the-hood changes that you cannot have until you are on 4.4 - such as ART as opposed to Dalvik, wireless printing built in, etc.
eortizr said:
why go through so much trouble just to get a 90% working CM ROM?, just install a 4.3 GE edition, install the KitKat Apk's and you will get the same experience plus it will be %100 working no issues whatsoever. CM Roms have never been 100% working ROMS i think since version 7 they always have something not working or missing.
Click to expand...
Click to collapse
That wouldn't do much but give you the launcher and maybe some new app features. When you upgrade to Android 4.4, you get more of the "under the hood" sort of changes. Speed and even the option to change from the Dalvik engine to Google's new ART engine. You also will basically just get the whole authentic experience in general. You don't get one from changing around the launcher and apps. If you could truly get the same experience with just changing those things, I'm sure Google would just change those through the Play Store with a few app updates. But they don't do this.
Sent from my GT-I9505G using XDA Premium 4 mobile app
Just curious, with leaked 4.3 there was issues with installing a few apps from play store...anyone having issues with anything like that on here?
DreenHotdog said:
That wouldn't do much but give you the launcher and maybe some new app features. When you upgrade to Android 4.4, you get more of the "under the hood" sort of changes. Speed and even the option to change from the Dalvik engine to Google's new ART engine. You also will basically just get the whole authentic experience in general. You don't get one from changing around the launcher and apps. If you could truly get the same experience with just changing those things, I'm sure Google would just change those through the Play Store with a few app updates. But they don't do this.
Sent from my GT-I9505G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
True and my Chrome never worked on using the apk's
This is why we are here to flash and experiment--need the RUSH--
So what rom are you guys using ? This one or one posted in another forum ?
Sent from my SGH-I337 using Tapatalk
This thread is for development of the Lte versions of the Tab 3.
They have a msm8930 cpu found the in the galaxy s4 mini as well. I have started to work on the device trees based on s4 mini.
I would like this topic to stay in general so everyone can post even newcomers.
device:
https://github.com/TeamRegular/android_device_samsung_lt02ltespr
Common for Att & Sprint
https://github.com/TeamRegular/android_device_samsung_lt02lte-common
Vendor blobs:
https://github.com/TeamRegular/android_vendor_lt02lte-common
@barberboy420
Let me know how the update goes because a file seems to be missing . At least from the dump I was provided
Code:
service secril-daemon /system/bin/sec-ril
class main
user root
group radio cache inet misc audio sdcard_rw diag log
https://github.com/TheMuppets/propr...lob/cm-10.1/d2-common/proprietary/bin/sec-ril
Unjustified Dev said:
@barberboy420
Let me know how the update goes because a file seems to be missing . At least from the dump I was provided
Code:
service secril-daemon /system/bin/sec-ril
class main
user root
group radio cache inet misc audio sdcard_rw diag log
https://github.com/TheMuppets/propr...lob/cm-10.1/d2-common/proprietary/bin/sec-ril
Click to expand...
Click to collapse
I didn't except the update. Later ill go in the settings and manually do it
kick @SS S3 M.O.A.R better!
I got cM-10.2 built and booted on my T217. Main issues so far are the touchscreen touches and the tablet layout. I think I need to port more T217 code to the CM kernel sources. That's all to report for now.
cougarcougar said:
I got cM-10.2 built and booted on my T217. Main issues so far are the touchscreen touches and the tablet layout. I think I need to port more T217 code to the CM kernel sources. That's all to report for now.
Click to expand...
Click to collapse
If you need any additional testers, please let me know.
cougarcougar said:
I got cM-10.2 built and booted on my T217. Main issues so far are the touchscreen touches and the tablet layout. I think I need to port more T217 code to the CM kernel sources. That's all to report for now.
Click to expand...
Click to collapse
where's my credit . I'll help you out.
There's no need to call cdma.mk it's empty now
https://github.com/CyanogenMod/android_vendor_cm/blob/cm-10.2/config/cdma.mk
I guess "no news" is "good news". Hope all is well.
btvolta said:
I guess "no news" is "good news". Hope all is well.
Click to expand...
Click to collapse
I looked on the guy's github. The changes that were made weren't helpful . I will continue working some day. I am too busy now
Sent from my SPH-D710 using Tapatalk
Learning
I'm about to get a sprint galaxy tab 3 7 inch, and since there has been much development on this device, I thought maybe i'd pitch in. Except I don't know how. Anyone know of some good literature on what goes into compiling a rom for a device? I'd be very interested in contributing what I can. Thanks! Also, if anyone can think of a reason for me not to get the Sprint tab 3, speak now or forever fuel my regret.
Dannybhoy03 said:
I'm about to get a sprint galaxy tab 3 7 inch, and since there has been much development on this device, I thought maybe i'd pitch in. Except I don't know how. Anyone know of some good literature on what goes into compiling a rom for a device? I'd be very interested in contributing what I can. Thanks! Also, if anyone can think of a reason for me not to get the Sprint tab 3, speak now or forever fuel my regret.
Click to expand...
Click to collapse
I would say get it. It is easier to work on than the non lte versions. Faster too.
Sent from my SCH-I500 using Tapatalk
Unjustified Dev said:
I would say get it. It is easier to work on than the non lte versions. Faster too.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I pulled the trigger on it. On to root!!
Dannybhoy03 said:
I pulled the trigger on it. On to root!!
Click to expand...
Click to collapse
very cool. Looking for root on 217. Seems kingo app risky per other thread. How did you get root for 217 model?
triune1001 said:
very cool. Looking for root on 217. Seems kingo app risky per other thread. How did you get root for 217 model?
Click to expand...
Click to collapse
For what is worth i used the kingo app with no problems
Sent from my SPH-D710 using XDA Premium 4 mobile app
Uploaded a CM-10.2 build for the sm-t217 for something to play around with.
Fixed screen touches via build.prop value
Charges via usb.
Built kernel and wlan module from Cyanogen kernel msm8930-common as a base.
-still needs charging, usb drivers, sound, camera ported over from the sprint source.
Bugs: Not working so far: wifi, no network, no sound, no camera, no bootanimation, no usb mounting
Download: http://goo.im/devs/thekraven/LT02LTE-SPR/build4-cm-10.2-20131209-UNOFFICIAL-lt02ltespr.zip
mirror1: http://www.androidfilehost.com/?fid=23252070760974519
No gapps yet as wifi and network are not working yet.
Install: Factory reset in cwm recovery and wipe system. Install the zip file.
THanks to TeamRegular, Unjustified Dev, gr8nole
cougarcougar said:
Uploaded a CM-10.2 build for the sm-t217 for something to play around with.
Fixed screen touches via build.prop value
Charges via usb.
Built kernel and wlan module from Cyanogen kernel msm8930-common as a base.
-still needs charging, usb drivers, sound, camera ported over from the sprint source.
Bugs: Not working so far: wifi, no network, no sound, no camera, no bootanimation, no usb mounting
Download: http://goo.im/devs/thekraven/LT02LTE-SPR/build4-cm-10.2-20131209-UNOFFICIAL-lt02ltespr.zip
mirror1: http://www.androidfilehost.com/?fid=23252070760974519
No gapps yet as wifi and network are not working yet.
Install: Factory reset in cwm recovery and wipe system. Install the zip file.
THanks to TeamRegular, Unjustified Dev, gr8nole
Click to expand...
Click to collapse
what DOES work? Seriously though, I'm glad someone is working on it. It's a start
Before, the touchscreen was all over the place. This is just a very alpha build to show progress. It still needs kernel work and more ramdisk work.
CM10.1 would have been a better place to start to fix bugs.
cougarcougar said:
Before, the touchscreen was all over the place. This is just a very alpha build to show progress. It still needs kernel work and more ramdisk work.
CM10.1 would have been a better place to start to fix bugs.
Click to expand...
Click to collapse
Best of luck... I can't wait to ditch TW
Update Build 5: Got audio working. Now trying to get wifi working.
http://www.androidfilehost.com/?fid=23252070760974860
cougarcougar said:
Update Build 5: Got audio working. Now trying to get wifi working.
http://www.androidfilehost.com/?fid=23252070760974860
Click to expand...
Click to collapse
I wouldn't even care if you never get lte working. A stable WiFi only cm would make my day.
Sent from my SPH-L710 using XDA Premium HD app
mrocklewitz said:
I wouldn't even care if you never get lte working. A stable WiFi only cm would make my day.
Sent from my SPH-L710 using XDA Premium HD app
Click to expand...
Click to collapse
Same here. I took my SIM out.
Sent from my SM-T217S using Tapatalk 4