Related
I have been compiling the cm7 source and sharing. Gapps and rom boots and work. It is more basic gingerbread aosp then cm7. Cyanogen and teamdouche have been working to get this together and this is more kinda like a nightly
www.crackflashers.com
You will need to flash the new recovery.img to flash/get working gapps.
after flashing gapps, run fix permissions to get gapps to work.
This is cause of cm7 going to ext4 based system unlike older roms that are ext3
The new recovery does make it so you can not use older pre gingerbread roms so find a older recovery to fastboot back to anything like froyo or restore old backups
Sent from my HTC Vision using XDA App
Apn might be missing if you can not connect to data. You can find a apn list here at the end of the op http://forum.xda-developers.com/showthread.php?t=892808
Guide to flashing on emmc devices (vision,ace, glacier) change vision to ace for this
http://forum.xda-developers.com/showthread.php?t=909714
So this does not include gapps?
Do you know when cwmr 3.0 will be avail in rom manager?
nandihno said:
So this does not include gapps?
Do you know when cwmr 3.0 will be avail in rom manager?
Click to expand...
Click to collapse
The gapps are posted on on that link also not built in, building in causes bootloops. Don't have any clue when it will be in rom manager, the one uploaded is the recovery.img built with the source
Sent from my HTC Vision using XDA App
so how is this compile compared to kali's release?
Omg more roms to flash. Cheers buddy.
hehe m0x your getting busy
maybe you should start up a review site lets us know whats good and bad
capychimp said:
so how is this compile compared to kali's release?
Click to expand...
Click to collapse
Yea i want to know the same thing, as kalis version has gapps bundle into it.which i think is a better solution given that cam 3 i not out in rmom manage yet
Am guessing video is not yrt supported right ?
nandihno said:
Yea i want to know the same thing, as kalis version has gapps bundle into it.which i think is a better solution given that cam 3 i not out in rmom manage yet
Am guessing video is not yrt supported right ?
Click to expand...
Click to collapse
I don't know cali's version. I just posted it cause I built it for someone else and he confirmed working. It is repo synced from the cm7 gingerbread source at about 7pm.
I don't have a desire hd so I can not confirm what is or isn't working
Sent from my HTC Vision using XDA App
nandihno said:
Yea i want to know the same thing, as kalis version has gapps bundle into it.which i think is a better solution given that cam 3 i not out in rmom manage yet
Am guessing video is not yrt supported right ?
Click to expand...
Click to collapse
The first RC0 version that was posted wasn't built by kali-
Anyone tired this ?
mero01 said:
Anyone tired this ?
Click to expand...
Click to collapse
Its slightly more advanced along in development than the other version. ADW is now the default launcher. Haven't noticed any difference apart from that.
dr.m0x said:
Its slightly more advanced along in development than the other version. ADW is now the default launcher. Haven't noticed any difference apart from that.
Click to expand...
Click to collapse
seem more stable ?
mero01 said:
seem more stable ?
Click to expand...
Click to collapse
Really it seems the same. Looking good.
dr.m0x said:
Really it seems the same. Looking good.
Click to expand...
Click to collapse
so how did u flash the gapps? via cwm recovery 3.0? or is there another way..
if there is no other way i preffer to wait till rom manager has cwm 3.0...makes things easier and safer
also ..is video camera still not working?
I have just flashed this new Rom using cmw 3.
I had to manually configure my apn.
The video-camera is still not working...
But beside this it is looking good!
Ok, it's not usable for me because i cann't get the network to work
New version up guys.
dr.m0x said:
New version up guys.
Click to expand...
Click to collapse
Where do you find that? Followed the link in first post and its just the same as before. Can you share a link maybe
How do you flash img file normally do it by zip?
HTC HERO - HTC HD2 - NOW HTC DESIRE HD & SAMSUNG GALAXY S Bring on the modding.
nickwarn said:
Where do you find that? Followed the link in first post and its just the same as before. Can you share a link maybe
Click to expand...
Click to collapse
I meant new version since thread started. The 11.30am version. Sorry for any confusion.
Sent by the air.
Anyone tried Bluetooth with this build?
I cant get pairing with my car working with any cyan build yet ...
Just wanted to know if anyone tested this yet
Thx ahead
Sent from my Desire HD using XDA App
Hi,
I was trying to install the CM9/10 for my device and I found a link on how to install here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V/Installing_CyanogenMod_9
I am following the steps, but i am stuck at a place where i have to install CWM 5.0.2.x or higher. I checked their website http://www.clockworkmod.com/rommanager and found version 3.2.0.0. Could you guys please let me know where to find 5.0.2.8?? or suggest an alternative. I am sorry if there was a post similar to this, as i have done extensive search before posting this thread. Thanks in advance, waiting for a reply.
As stated on the wiki page you linked to, you need a kernel with CWM Recovery preinstalled (don't use ROM Manager!)
This page shows you how to flash a kernel onto the device to give you the proper recovery.
Keep reading the wiki, there's lots of good stuff in there to teach you how this device works as far as flashing goes
Thank you!! I was able to install the Kernel and the CM9 ROM....
adithveeresh said:
Thank you!! I was able to install the Kernel and the CM9 ROM....
Click to expand...
Click to collapse
No JB/CM10 yet. Soon as we fix the aries stuff, we'll be on our way!
adithveeresh said:
Thank you!! I was able to install the Kernel and the CM9 ROM....
Click to expand...
Click to collapse
could u tell me where you found the ClockwordMod Recovery (CWM) 5.0.2.x or greater?
crazykidguy said:
could u tell me where you found the ClockwordMod Recovery (CWM) 5.0.2.x or greater?
Click to expand...
Click to collapse
He flashed a kernel that already has it pre-installed. As was suggested in the above post.
Sent from my SGH-T959V using xda premium
Kernel name?
Which kernel did you flash?
SGS4G
Mod version: Octaine Team Acid
Firmware version: 2.3.5
Kernel version: 2.6.35.7-T959vuvki3-cl611444
adithveeresh said:
Thank you!! I was able to install the Kernel and the CM9 ROM....
Click to expand...
Click to collapse
jwgoku said:
Which kernel did you flash?
SGS4G
Mod version: Octaine Team Acid
Firmware version: 2.3.5
Kernel version: 2.6.35.7-T959vuvki3-cl611444
Click to expand...
Click to collapse
Look for bhundven's Blast Off kernel or AntonX's Basic with a Twist in the Development section to then flash CM9 from.
I know there are a lot of new ROMs coming now with the Aries kernel source now available for our little phone,my question is,is there the possibility of someone perhaps putting together a CWM flash able TWRP recovery that can substitute the CWM in place on a lot of these builds. I currently have Eric's beanstalk however the newest is sadly CWM.
sent from my t959w running Beanstalkv2
I saw FB mention he has a pull request to maybe get something going. I'd be willing to merge it into my Git and try a build with that, as I use the TeamUserDebug Git when I build.
This is alternative to cwm and twrp if somebody wants to port it to this device. I prefer it to either of the two previously mentioned recoveries.
http://forum.xda-developers.com/showthread.php?t=2201860
Sent from my Nexus 4
limeaide said:
This is alternative to cwm and twrp if somebody wants to port it to this device. I prefer it to either of the two previously mentioned recoveries.
http://forum.xda-developers.com/showthread.php?t=2201860
Sent from my Nexus 4
Click to expand...
Click to collapse
Bumper cars are fun.
Seriously guys look at this. You can slap aroma file manager in and have a built in FM from recovery.
I do not think there will be much problem building this into the sgs4g's kernel/recovery.
limeaide said:
This is alternative to cwm and twrp if somebody wants to port it to this device. I prefer it to either of the two previously mentioned recoveries.
http://forum.xda-developers.com/showthread.php?t=2201860
Sent from my Nexus 4
Click to expand...
Click to collapse
Looks fairly effortless to port. I will attempt this when I have internets.
Too bad not all the source code is open though... For anyone wondering the dev didn't make his touch code open source.
I think that is because that part of the recovery is tied to the paid version of rom manager.
I liked twrp it was the first recovery I used on my N4. But I ran across this and have used it since. I think you guys will end up liking it. After you add the aroma file manager it is pretty awesome.
Hi. As you propably know, there is no TWRP 2.7 for saga. This is why:
Saga would need a number of updates in order to make it work with 4.4 Kit Kat ROMs. 4.4 ROM support really doesn't depend on the recovery itself. The kernel and other parts of the ramdisk have to support SELinux contexts in order for the set_metadata functions to work. I don't have a saga myself and at this point I have no plans to continue to support the device. I've been building saga in a CM7 / gingerbread tree which doesn't support the things needed for SELinux. The device would need to be compiled with an updated kernel in at least a 4.1 and preferably a 4.3 or 4.4 tree to support installing Kit Kat ROMs.
I plan to drop official support for any device that I've been building in ICS or Gingerbread trees which includes saga. If people want to see continued support for those devices, then hopefully developers for those devices will step up and build TWRP themselves and maybe offer their updated device files to us so that we can extend official support.
Click to expand...
Click to collapse
So basically we need developers who would like to help with that. I'm not that techy to understand what the problem is but I would like you to tell me and help.
BTW! Why our device is not available in DevDB! How do we change that?
Hm. I might take a shot at this. Though I personally prefer 4ext
devil-kin said:
Hm. I might take a shot at this. Though I personally prefer 4ext
Click to expand...
Click to collapse
It would be really splendid thing to do sir
Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.
devil-kin said:
Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.
Click to expand...
Click to collapse
That's great! It would be even better if you could somehow share some of your work here so maybe someone else could take a look (i don't know if it's possible. But you use github right?) I would love to add this project to DevDB but it seems that our phone is not there and i don't know how to add it.
My github repos are at https://github.com/jdeluyck - I haven't uploaded anything yet save for the changes to the repo file to pull in TWRP.
Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know
PERFECT!
devil-kin said:
Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know
Click to expand...
Click to collapse
I flashed it, I backed up my rom, I wiped, I flashed my rom clean, it booted, I went to recovery and I restored my rom. Everything went perfect, no problems whatsoever! Now there are 2 questions left to ask.
1. May I update TWRP for saga developement thread and attach this build?
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Anyway great work devil-kin :highfive: Personally I see TWRP as the best recovery and I'm on it from 2.2. Seeing it still working in its latest iteration on my beloved DS makes little tears appear in the corners of my eyes. I absolutely love this phone for it's size, specs, build quality and weird survability (many screen to sidewalk encounters and no broken glass Only praiseworthy scars). LONG LIVE DS! <3
VnnAmed said:
1. May I update TWRP for saga developement thread and attach this build?
Click to expand...
Click to collapse
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
VnnAmed said:
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Click to expand...
Click to collapse
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?
devil-kin said:
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?
Click to expand...
Click to collapse
Thank you very much If you could, i would like you to PM Dees_Troy and tell him that you have succesfully compiled 2.7 for saga, so if he has some more technical questions you can answer them I'm updating TWRP for saga thread right away
This thread is for updates of temasek cm12.1 built by myself. I will be building for hlte and hltespr.
Temasek made this all possible and it is all his work I am just taking the time to build and upload.
V19.3+ root removed, you will need to flash SuperSU zip to achieve root.
Downloads:
Hlte or Hlte on my BasketBuild
Hltespr or Hltespr on my BasketBuild
Credits: @temasek
XDA:DevDB Information
Temasek cm-12.1 unofficial cyanogenmod, ROM for the Samsung Galaxy Note 3
Contributors
trader418, Temasek
Source Code: https://github.com/temasek/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2016-03-26
Last Updated 2016-03-26
Thanks for keeping support for the Note 3 alive.
Great, good to see 12.1 back alive. Anything I can do to help, just say so.
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Buslova said:
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Click to expand...
Click to collapse
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Straw poll whether to include root in the build here http://strawpoll.me/7191529
trader418 said:
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Click to expand...
Click to collapse
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Buslova said:
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Click to expand...
Click to collapse
Ota isn't too bad, I'll probably use it soon tbh, but I won't promise anything
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
redfuryjr55 said:
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
Click to expand...
Click to collapse
Start with which device you have
trader418 said:
Start with which device you have
Click to expand...
Click to collapse
haha sorry! htlespr!
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
trader418 said:
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
Click to expand...
Click to collapse
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
redfuryjr55 said:
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
Click to expand...
Click to collapse
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
trader418 said:
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
Click to expand...
Click to collapse
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
swukjay said:
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
Click to expand...
Click to collapse
Either change weather provider to another or customize your location. Sometimes yahoo weather isn't working well.
As for WiFi, check your dev options.
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
eseregin said:
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
Click to expand...
Click to collapse
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Hmm, still no luck eh? I tried helping ya last night in the other thread. I'm also a hltespr user. I'm still running OH1 baseband however OK2 is the latest. Also, as I told you last night, I'm using an older version of TWRP recovery (ver. 2.8.7) however the latest is 3.0.0.
What baseband are YOU running? Go to settings, "About phone", and look for "Baseband version" and let us know. =)
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Sorry, I have different phone..
Might be the latest here
https://idlekernel.com/flash-tools/firmware/hltespr_SM-N900P/N900PVPUEOK2/
But I am far away from sure