Database Users

TWICS

Captivate currently had TWICS. Its base code from cm9 with TW launcher and Samsung gs3 add on with devil kernel. Running this o my cappy. Super fast and stable. Just an outstanding rom.
Can someone port this to vibrant please!
What are you looking at shortbus......

*NOT SURE/CONFIRMED
But since it is in the line of the original galaxy s, I think you can just flash it, and then change modem/kernel/key layout, which is done by a script (forgot what its called in our development section)
ok, i found it
http://forum.xda-developers.com/showthread.php?t=1623840
Using that, you SHOULD be able to flash any Galaxy S ROM (except the 4G)
If it doesn't work, nothing will go wrong, most likely you will
1) boot loop
2) key layout will be mixed up(easy fix)
3) no connection (change modem/kernel)
*you said this was TWICS, make sure it is ICS and not just themed to look like TWICS.
Link to rom please?

http://forum.xda-developers.com/showthread.php?t=1625619
What are you looking at shortbus......

hey, instead of using it from the captivate, use it from the i9000
http://forum.xda-developers.com/showthread.php?t=1608624
same thing, captivate guy ported from i9000, just you'll probably get updates etc faster.
P.S. tell us how it goes.

xriderx66 said:
hey, instead of using it from the captivate, use it from the i9000
http://forum.xda-developers.com/showthread.php?t=1608624
same thing, captivate guy ported from i9000, just you'll probably get updates etc faster.
P.S. tell us how it goes.
Click to expand...
Click to collapse
OK so I tried it from the captivate before I saw this post. Installed rom and before it gave install complete it auto rebooted. The rom was on my phone but up was down left was right ie screen was in landscape then when I turn it sideways it would go to normal view. I rebooted to recovery and ran patch then reboot and wouldn't get past vibrant screen. I will try again with i9000 rom and let you know the results.
Sent from my SGH-I897 using XDA

Tried it with i9000 rom but it aborted error status 7. I think my zip was bad. Going to try again.?
Sent from my SGH-T959 using xda premium
Edit: just read FAQ need to change some things in rom file. Will update after I try this

samsgun357 said:
Tried it with i9000 rom but it aborted error status 7. I think my zip was bad. Going to try again.?
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
Try to flash the Subzero kernel from here: (use build 80 not 128) http://rootzwiki.com/topic/22833-kernelics15-june-subzero-v14-build-128-brain-dead-and-loving-it/
If you already tried it from Subzero kernel; try the Glitch kernel, its on these dev sections.
Flash either of those to the ROM you currently have, and then try to flash it.
EDIT----------------
"if you are getting status 7 or getprop error then a little work from your side is needed
extract the rom to a folder then go to /extracted folder/META - INF/com/Google/Android from there open updater-script and remove all getprop lines
come back to META - INF folder and delete all three files
zip the file and flash it in recovery
NOTE:- to edit updater script use jota text editor(android), notepad (windows)"
It's in the patch's thread.
Do that.

I followed the thread exactly used jota changed everything and tried again. It just aborts install. I haven't given up. Gonna try again tomorrow. It beat me tonight but not for good! Thanks for everything x.
Sent from my SGH-T959 using xda premium

firstly I want to tell you that because of not having a vibrant to test the patch is in beta
what you can do is open updater script with jota text editor and remove all those getprop lines from the script and as a security step what you can do is press menu button then tap on file and tap on line break then select (lf for android/Linux) save the file go to meta-inf folder and remove all those cert files
zip the package again and flash no need to sign it again for further help you can ask me also in the patch thread

dhlalit11 said:
firstly I want to tell you that because of not having a vibrant to test the patch is in beta
what you can do is open updater script with jota text editor and remove all those getprop lines from the script and as a security step what you can do is press menu button then tap on file and tap on line break then select (lf for android/Linux) save the file go to meta-inf folder and remove all those cert files
zip the package again and flash no need to sign it again for further help you can ask me also in the patch thread
Click to expand...
Click to collapse
Thanks for input. I first tried it using a captivate port and it would install then I would run patch and it wouldn't boot past vibrant screen. Then I got the original galaxy s rom that the cappy rom was ported from. It gave the error so I proceeded to change the file as per op instructions. It would abort install with but no error status. I did it twice to make sure. If I changed all the get prop from i9000 to t959 would it work?
Sent from my SGH-T959 using xda premium

you should not replace them instead just remove them
after flashing if it gives error then reboot device and with any root explorer app go to /cache/recovery and upload both the files I will see what the error is and then I can troubleshoot better

So guys I'm the twics porter to the cappy twics will soon be called remics I've been a part of a team that took over twics and I will soon be releasing to captivate
Sent From My ICS Cappy Using Tapatalk 2

patrick8996 said:
So guys I'm the twics porter to the cappy twics will soon be called remics I've been a part of a team that took over twics and I will soon be releasing to captivate
Sent From My ICS Cappy Using Tapatalk 2
Click to expand...
Click to collapse
Do you think it'd be possible for you to release a version for Vibrant as well? Since not much will have to be changed from Captivate.
Just modem/kernel, and possibly build.prop

dhlalit11 said:
you should not replace them instead just remove them
after flashing if it gives error then reboot device and with any root explorer app go to /cache/recovery and upload both the files I will see what the error is and then I can troubleshoot better
Click to expand...
Click to collapse
I did remove and it just aborts with no explanation.
Sent from my SGH-T959 using xda premium

xriderx66 said:
Do you think it'd be possible for you to release a version for Vibrant as well? Since not much will have to be changed from Captivate.
Just modem/kernel, and possibly build.prop
Click to expand...
Click to collapse
Yes please! I love it on my cappy and want it on my vibrant also!
Sent from my SGH-T959 using xda premium

and what about uploading the error log from /cache/recovery

I took the twics add on from mr.mad for gs1 running cm9/slim and flashed on my vibrant running gummy 1.2.6 and it got stuck on boot . I reflashed gummy without wiping and now have all the apps from add on except for tw launcher. I guess that's a happy medium until we can get a port.
Sent from my SGH-T959 using xda premium

dhlalit11 said:
and what about uploading the error log from /cache/recovery
Click to expand...
Click to collapse
How do I extract it from root browser?
Posse magnet......

samsgun357 said:
How do I extract it from root browser?
Posse magnet......
Click to expand...
Click to collapse
Just go to that file, copy it and paste it into your SD or something, and then upload it from there.

Because I have flashed a new rom and kernel the recovery log doesn't have the abort/error info...
Posse magnet......

[Q] [ROM] Cyanogen(mod) 10.1 - symlink: somelinks failed

Hello,
after googling for about 20 hours, with some hours restless sleep between , i now decide to ask, because i am unable to solve the problem without help.
I can install [ROM] Cyanogen(mod) 10.1 beginning with Version 1 up to Version 2 Update 2. Every version after that fails with the following:
Code:
Installing Update...
symlink: somelinks failed
E:Error in /sdcard/*insert-failing-version-here*
<status 7>
Installation aborted.
I googled and found a lot i could have done wrong, i repartitioned my sys, cleaned, tried different recovery versions(cwm & twrp), got back to install [ROM] Aurora ICS 4.0.4 for u8800 - Version 5.0 update 21, which all worked out very well. but as soon as i try to install one of the versions 3 to 5 of the [ROM] Cyanogen(mod) 10.1 i hit the same problem over and over. I hope there is someone who knows what makes the difference betwenn the working versions and them who won't work, maybe even have a solution

bdgraue said:
Hello,
after googling for about 20 hours, with some hours restless sleep between , i now decide to ask, because i am unable to solve the problem without help.
I can install [ROM] Cyanogen(mod) 10.1 beginning with Version 1 up to Version 2 Update 2. Every version after that fails with the following:
Code:
Installing Update...
symlink: somelinks failed
E:Error in /sdcard/*insert-failing-version-here*
<status 7>
Installation aborted.
I googled and found a lot i could have done wrong, i repartitioned my sys, cleaned, tried different recovery versions(cwm & twrp), got back to install [ROM] Aurora ICS 4.0.4 for u8800 - Version 5.0 update 21, which all worked out very well. but as soon as i try to install one of the versions 3 to 5 of the [ROM] Cyanogen(mod) 10.1 i hit the same problem over and over. I hope there is someone who knows what makes the difference betwenn the working versions and them who won't work, maybe even have a solution
Click to expand...
Click to collapse
It has to do with carrier settings on your phone. Ex. AT&T and movelint but restrictions to certain partitions. I'm looking for a solution.
Sent from my U8800-51 using Tapatalk 2

same problem
in Finland. with sonera as operator. I. have the same problem......
it is driving. me mad.
:crying:

I have de same problem too

Have you tried Twrp to see if cwm is the problem?
Sent from my U8800-51 using Tapatalk 2

Somcom3X said:
Have you tried Twrp to see if cwm is the problem?
Sent from my U8800-51 using Tapatalk 2
Click to expand...
Click to collapse
I tried with twrp and the problem its the same

Somcom3X said:
Have you tried Twrp to see if cwm is the problem?
Click to expand...
Click to collapse
as you can read in my first post, i tried both
that was one of the many options i found in the net and tried out. i guess i tried nearly everything i could find and what was mostly save, ok inbetween i thought three times i have bricked my phone, but i could always convince it to come back to life
i dont know what the difference really between v1/v2 and the later not working versions is. i tried to compare the install-files and the relevant seemed to be the same in that case. but i am really a noob when it comes to android development :cyclops:

Version 6
bdgraue said:
Hello,
after googling for about 20 hours, with some hours restless sleep between , i now decide to ask, because i am unable to solve the problem without help.
I can install [ROM] Cyanogen(mod) 10.1 beginning with Version 1 up to Version 2 Update 2. Every version after that fails with the following:
Code:
Installing Update...
symlink: somelinks failed
E:Error in /sdcard/*insert-failing-version-here*
<status 7>
Installation aborted.
I googled and found a lot i could have done wrong, i repartitioned my sys, cleaned, tried different recovery versions(cwm & twrp), got back to install [ROM] Aurora ICS 4.0.4 for u8800 - Version 5.0 update 21, which all worked out very well. but as soon as i try to install one of the versions 3 to 5 of the [ROM] Cyanogen(mod) 10.1 i hit the same problem over and over. I hope there is someone who knows what makes the difference betwenn the working versions and them who won't work, maybe even have a solution
Click to expand...
Click to collapse
Same problem. with version 6.
:crying::crying::crying:

Doncra said:
Same problem. with version 6.
:crying::crying::crying:
Click to expand...
Click to collapse
ah... "good" to read that, i was just about to try it out
so maybe i'll wait till this issue is addressed

I had the same problem, but after repartition the system following this instructions ( http://forum.xda-developers.com/showthread.php?p=29505489 ), now I am able to install it.

alexmbra said:
I had the same problem, but after repartition the system following this instructions ( http://forum.xda-developers.com/showthread.php?p=29505489 ), now I am able to install it.
Click to expand...
Click to collapse
works thanks

alexmbra said:
I had the same problem, but after repartition the system following this instructions ( http://forum.xda-developers.com/showthread.php?p=29505489 ), now I am able to install it.
Click to expand...
Click to collapse
same here to. i don't know exactly wat went wrong the first time i repartitioned the phone. now it works, i have [ROM] Cyanogen(mod) 10.1Version 6 up'n'runing
many thanks for mention it again and kinda "forcing" me to do the repartitioning again

alexmbra said:
I had the same problem, but after repartition the system following this instructions ( http://forum.xda-developers.com/showthread.php?p=29505489 ), now I am able to install it.
Click to expand...
Click to collapse
I was just about to post this. :thumbup:
Sent from my U8800-51 using Tapatalk 2

Thanks
Somcom3X said:
I was just about to post this. :thumbup:
Sent from my U8800-51 using Tapatalk 2
Click to expand...
Click to collapse
:good: works

Test HALO PA build?

Hey guys, need this PA build tested. Built from source for m7ul using CM's source so thanks go to them. As always, flash at your own risk, im not responsible, etc. It should be perfectly fine though. Make sure things like data, camera, wifi, in call voice, etc work please. Also boot to recovery and make sure all seems well.
Grab some screenshots for me if it does boot. Thanks!
HALO BUILD
PA GAPPS

slick_rick said:
Hey guys, need this PA build tested. Built from source for m7ul using CM's source so thanks go to them. As always, flash at your own risk, im not responsible, etc. It should be perfectly fine though. Make sure things like data, camera, wifi, in call voice, etc work please. Also boot to recovery and make sure all seems well.
Grab some screenshots for me if it does boot. Thanks!
HALO BUILD
PA GAPPS
Click to expand...
Click to collapse
I'll flash this tomorrow when I get home. Sorry I can't do it right now. 1:41 in the morning and if something goes wrong, I don't want to pull an all nighter. I've been waiting for this ROM so I can't wait!
Sent from my HTC One 801e using Tapatalk 4 Beta

Downloading!! Will test it as soon as i am back home!
I urge other users who can to test this cool rom out soon!
Thank u dev!

Downloading i'll try it tonight

PA Halo on the HTC one, this great news I used this rom as my dailey on my Nexus 4, I will test it later.

Was just about to install it but it looks like it has protection so only the international HTC One will work on it. Using my AT&T HTC One and was given this error
Installing update...
assert failed: getprop("ro.product.device) == ro.build.product") == "m7ul"
E:Error in /sdcard/0/Download/pa_m7ul-3.56-04JU
(Status 7)
Installion aborted
If anyone knows how to bypass this, please help, I'm guessing changing the build.prop in the zip probably won't work

JewBagel254 said:
Was just about to install it but it looks like it has protection so only the international HTC One will work on it. Using my AT&T HTC One and was given this error
Installing update...
assert failed: getprop("ro.product.device) == ro.build.product") == "m7ul"
E:Error in /sdcard/0/Download/pa_m7ul-3.56-04JU
(Status 7)
Installion aborted
If anyone knows how to bypass this, please help, I'm guessing changing the build.prop in the zip probably won't work
Click to expand...
Click to collapse
I had the same problem using my TMO HTC One.

JewBagel254 said:
Was just about to install it but it looks like it has protection so only the international HTC One will work on it. Using my AT&T HTC One and was given this error
Installing update...
assert failed: getprop("ro.product.device) == ro.build.product") == "m7ul"
E:Error in /sdcard/0/Download/pa_m7ul-3.56-04JU
(Status 7)
Installion aborted
If anyone knows how to bypass this, please help, I'm guessing changing the build.prop in the zip probably won't work
Click to expand...
Click to collapse
Probably have to open up the update script and remove the asset get prop bit at the beginning.

Cryosx said:
Probably have to open up the update script and remove the asset get prop bit at the beginning.
Click to expand...
Click to collapse
Just tried that using my mac but unfortunately, it still aborted the installation.

JewBagel254 said:
Just tried that using my mac but unfortunately, it still aborted the installation.
Click to expand...
Click to collapse
Well, i got in but it keeps turning off 5 seconds in. Looks like a no go for me. Seemed really nice though, nicer than the other aosp roms we have. Probably just the wallpaper haha
AT&T HTC One

link is not opening, loading...........................
edit: done, downloading!!
---------- Post added at 03:59 PM ---------- Previous post was at 03:10 PM ----------
JewBagel254 said:
Was just about to install it but it looks like it has protection so only the international HTC One will work on it. Using my AT&T HTC One and was given this error
Installing update...
assert failed: getprop("ro.product.device) == ro.build.product") == "m7ul"
E:Error in /sdcard/0/Download/pa_m7ul-3.56-04JU
(Status 7)
Installion aborted
If anyone knows how to bypass this, please help, I'm guessing changing the build.prop in the zip probably won't work
Click to expand...
Click to collapse
Same error on my international One! but i am using android revolution hd 10.1 rom!

did you try with another recovery?
it solved mu problem once..that could be the case here

aamitabh28 said:
did you try with another recovery?
it solved mu problem once..that could be the case here
Click to expand...
Click to collapse
i guess there is some other prob.
---------- Post added at 04:37 PM ---------- Previous post was at 04:34 PM ----------
Cryosx said:
Probably have to open up the update script and remove the asset get prop bit at the beginning.
Click to expand...
Click to collapse
bro did your thing and it flashed fully!!
thanks!
Edit : same prob. reboot in 5 seconds!

can anyone give me the logcat??

I will test this when I get home tonight--64 gig M7 Developer Edition. And thank you very much for working on this, I have been waiting for someone to release a Paranoid Android ROM! I tried porting it myself, but it was always too buggy for a daily driver.

raziehEP said:
I will test this when I get home tonight--64 gig M7 Developer Edition. And thank you very much for working on this, I have been waiting for someone to release a Paranoid Android ROM! I tried porting it myself, but it was always too buggy for a daily driver.
Click to expand...
Click to collapse
Add me on Hangouts if you have experience building for m7. I'm devving blind for now so I wouldn't mind some help.
Sent from my SPH-L900 using Tapatalk 2

i'm getting error flashing zip

raziehEP said:
I will test this when I get home tonight--64 gig M7 Developer Edition. And thank you very much for working on this, I have been waiting for someone to release a Paranoid Android ROM! I tried porting it myself, but it was always too buggy for a daily driver.
Click to expand...
Click to collapse
Unfortunately I did not notice the rom was for the GSM version until I got home--I tried it anyways; I had obvious issues flashing it, given it was for the wrong device, but I got it to work. After flashing the rom it would crash after 10-30 seconds of use.
Now this part may or may not help: I took your build and the M7 version of CM10 and ported the rom over. I was able to get it to boot but continued to crash after the same amount of time.
slick_rick said:
Add me on Hangouts if you have experience building for m7. I'm devving blind for now so I wouldn't mind some help.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
I have very basic experience building for M7, so we might be in the same boat. I am more than happy to help you with anything I can though.

@m3dd0g and @melando
You guys could probably be of quite a bit of assistance to @slick_rick with this. Would you guys mind helping out? Understand if your too busy.
Sent from my HTC One using xda app-developers app

https://plus.google.com/10472832955...con&utm_medium=chrome_app&utm_campaign=chrome
http://d-h.st/zAE
New build out.should work on all gsm variants.

Android Wear 2.0 Beta APK won´t start

Hi,
I installed Android Wear 2.0 beta apk from apkmirror, because my Huawei Watch told me on latest 2.0 dev preview, that it setup has to be continoued on smartphone, but my Android Wear 1.5 app told me, it has to update, even on latest update already installed..
So I downloaded the 2.0 beta apk and now this one can´t start, because it tells me:
"This phone has been flashed with an unsupported configuration for companion.
You must re-flash it as either signed/user or unsigned/userdebug."
I´m on latest cm14 build for OnePlus 3, but also found users, that get this error on official Android.
So whats to do, to get it working? Is it, because I´m not in beta-program for Android Wear APK, just use Dev Preview on my Watch?
If so, how can I participate to APK´s beta program?
EDIT: Finally found way to participate beta program, but app doesn´t work even now.. reinstalled already 3 times

I'm having the same issue with CyanogenMod on my HTC one m8 (w/ LG watch urbane 2)... I did the app the 'right' way... Was about to try apkmirror version but now I see u have the same problem with that...

The answer is in this thread here
http://forum.xda-developers.com/showpost.php?p=68924594&postcount=285
Edit the build.prop
edit -this is the direct link to the post. Now that I can search and copy urls, I think the first link was wrong thread.

In case anyone else sees this as the answer... be careful when doing that edit.... I did on my HTC One m8 (running cm nightlies).... killed my phone and can't get into recovery to try and revert the change.
Edit: Finally fixed my m8... Moral of the story is: Don't blindly edit the build.prop file... That simple change can, at least in certain cases, cause the phone to not boot.

That solution does not work for me (I'm on cm13 klte snapshot).
Does anyone have another suggestion?

VollNoob said:
That solution does not work for me (I'm on cm13 klte snapshot).
Does anyone have another suggestion?
Click to expand...
Click to collapse
Make the change, then reboot. Didn't work for me before rebooting, but worked after.

Pkt_Lnt said:
The answer is in this thread here
http://forum.xda-developers.com/showpost.php?p=68924594&postcount=285
Edit the build.prop
edit -this is the direct link to the post. Now that I can search and copy urls, I think the first link was wrong thread.
Click to expand...
Click to collapse
where to find the build.prop?? thank you

Synthi said:
where to find the build.prop?? thank you
Click to expand...
Click to collapse
In your phone /system folder. Edit with a root enabled file manager.

How do i make Roms for sm-g530(H/F/W) Compatible with G530(T)??

Im seeing all these roms out there and none of them are for my phone. Like theres roms for (G530H/F/W) but for never (SM-G530T) do i need to do anything to make them "Compatible" for can i just flash it on my prime even though its for a different "type" of phone.
Lets say on my G530T. For example if I wanted a rom only for SM-G530H/W/H what do i have to do to make it for my G530T??

I too would like to know this information; Id be willing to build and post ROMS if some one would be willing to describe the process

tbirdguy said:
I too would like to know this information; Id be willing to build and post ROMS if some one would be willing to describe the process
Click to expand...
Click to collapse
Me too

@Bloodygamers @tbirdguy @Coeur Brisé
Post The Screenshot From About Phone.
Download the latest build of CM12.1 from here:
https://jenkins.sandpox.org/job/FORTUNAXX3G_CM12.1/
Nd flash it on your device. Before flashing open the zip file nd in Meta Inf folder find updater script. Remove the assert scripts on the top nd then you're good to flash.
Flash them with TWRP nd let me know the results, bugs nd issues.
Mention or reply to this post when you've to.

Duplicate.

Ive tried flashing cm12.1 for the fortunax already twrp wouldnt let me.

Coeur Brisé said:
Ive tried flashing cm12.1 for the fortunax already twrp wouldnt let me.
Click to expand...
Click to collapse
What error does it show? Take a screenshot in TWRP nd post here.
The error is probably because you haven't removed the assert lines.

I have been interested in porting / building roms for a bit now; but with no real compile expierence (unless u count PASCAL from High School, 1992) im dl and attempting flash now; i currently have a CM12.1 rom on the phone, and I read a post before about porting roms here but havent actually tried it because I dont have a build environment setup (I will again soon tho)
edit with results from flash minus asserts
it flashed without the asserts but and boots but im getting random reboots before i can finish setting up

@Bloodygamers, a custom ROM already exists for the SM-G530T. http://forum.xda-developers.com/gra...12-1-g530w-t3424761/post67877333#post67877333