Not content with having only a few ROMs available for our devices, I decided to see if I could make a Jellybean ROM Porting package that you could flash on top of an i717 ROM.
I have made a flashable zip that successfully loads Jellybean ROMs just fine but with two bugs I was able to notice:
The phone does not recognize that it has any vibration hardware, so capacitive buttons and silent mode with vibration dont work.
WiFi does not turn on
What I did was take existing kernels from our current Jellybean Roms, injected our phones RIL files, and wrapped it into a flashable zip.
So far I only have those two bugs, so I am curious if anyone has any ideas what other files need to be changed to make this porting package work?
Update: I tried a bunch of different Roms and system file combinations, still having the two bugs above in every ROM.
Here's the porting package in case anyone wants to try upgrading or fixing it or testing other ROMs.
http://db.tt/iWn2gt5q
Simply wipe your phone, flash an i717 ROM, then the porting package, then wipe dalvik cache and cache.
Credits to Jamie for his awesome paranoid android ROM, from which I had used some of the files from in this package
speedysilwady said:
Not content with having only a few ROMs available for our devices, I decided to see if I could make a Jellybean ROM Porting package that you could flash on top of an i717 ROM.
I have made a flashable zip that successfully loads Jellybean ROMs just fine but with two bugs I was able to notice:
The phone does not recognize that it has any vibration hardware, so capacitive buttons and silent mode with vibration dont work.
WiFi does not turn on
What I did was take existing kernels from our current Jellybean Roms, injected our phones RIL files, and wrapped it into a flashable zip.
So far I only have those two bugs, so I am curious if anyone has any ideas what other files need to be changed to make this porting package work?
Update: I tried a bunch of different Roms and system file combinations, still having the two bugs above in every ROM.
Here's the porting package in case anyone wants to try upgrading or fixing it or testing other ROMs.
http://db.tt/iWn2gt5q
Simply wipe your phone, flash an i717 ROM, then the porting package, then wipe dalvik cache and cache.
Credits to Jamie for his awesome paranoid android ROM, from which I had used some of the files from in this package
Click to expand...
Click to collapse
ok so I am having a problem. I downloaded PA 2.23 and went to install and i got a fail message. I use twrp so i installed a i1717 twrp and then it let me install PA 2.23. I installed the porting package and then wiped cache and delvik and rebooted phone. After the restart the bottom lights up but just stays lit up. Nothing else happened for 20 minutes. I wiped everything, used darkside to wipe phone. What am i doing wrong? Thanks
randyv2003 said:
ok so I am having a problem. I downloaded PA 2.23 and went to install and i got a fail message. I use twrp so i installed a i1717 twrp and then it let me install PA 2.23. I installed the porting package and then wiped cache and delvik and rebooted phone. After the restart the bottom lights up but just stays lit up. Nothing else happened for 20 minutes. I wiped everything, used darkside to wipe phone. What am i doing wrong? Thanks
Click to expand...
Click to collapse
I never tried testing with the i717 twrp, I used our phones recovery.
I had the same issue. The solution is simple, but takes a little bit of effort
The problem is that the ROM has a device check in the updater-script within the ROM zip file in the META-INF folder. You have to extract the zip, open the updater-script in a text editor and remove the first few lines that specify the prop checks for quincyatt and i717. Then compress it and reflash using the steps I mentioned.
speedysilwady said:
I never tried testing with the i717 twrp, I used our phones recovery.
I had the same issue. The solution is simple, but takes a little bit of effort
The problem is that the ROM has a device check in the updater-script within the ROM zip file in the META-INF folder. You have to extract the zip, open the updater-script in a text editor and remove the first few lines that specify the prop checks for quincyatt and i717. Then compress it and reflash using the steps I mentioned.
Click to expand...
Click to collapse
yeah that seems easy enough. lol, i dont know how i got to this point so maybe i will wait for when Jamie releases the next version for us on Tmobile. Thanks for your help, i am going to try it on other JB roms later.
The vibration problem and wifi problem are from not I corporating the kernel modules into the ROM. What you are looking for is dhd.ko and vibtator.ko.
Sent from my SGH-T989 using xda app-developers app
speedysilwady said:
I never tried testing with the i717 twrp, I used our phones recovery.
I had the same issue. The solution is simple, but takes a little bit of effort
The problem is that the ROM has a device check in the updater-script within the ROM zip file in the META-INF folder. You have to extract the zip, open the updater-script in a text editor and remove the first few lines that specify the prop checks for quincyatt and i717. Then compress it and reflash using the steps I mentioned.
Click to expand...
Click to collapse
Trying this now thanks! (first attempt failed)
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
ptmr3 said:
The vibration problem and wifi problem are from not I corporating the kernel modules into the ROM. What you are looking for is dhd.ko and vibtator.ko.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks! Going to try my hand at modifying now.... :cyclops:
---------- Post added at 11:05 PM ---------- Previous post was at 10:49 PM ----------
speedysilwady said:
I never tried testing with the i717 twrp, I used our phones recovery.
I had the same issue. The solution is simple, but takes a little bit of effort
The problem is that the ROM has a device check in the updater-script within the ROM zip file in the META-INF folder. You have to extract the zip, open the updater-script in a text editor and remove the first few lines that specify the prop checks for quincyatt and i717. Then compress it and reflash using the steps I mentioned.
Click to expand...
Click to collapse
Removed as much of the updater-script that seemed logical but still getting error, Failed. Going to try to modify the updater-script again. Am I possibly removing too much? What about just overwriting the i7i7 with T879?
---------- Post added at 11:16 PM ---------- Previous post was at 11:05 PM ----------
ptmr3 said:
The vibration problem and wifi problem are from not I corporating the kernel modules into the ROM. What you are looking for is dhd.ko and vibtator.ko.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Where does one incorporate the kernel modules into the ROM? the dhd.ko and the vibrator.ko. From where do we get them? Are they oncorporated into the port.zip he made?
Trying my hardest NOT to brick ANOTHER phone :cyclops:
---------- Post added at 11:18 PM ---------- Previous post was at 11:16 PM ----------
speedysilwady said:
I never tried testing with the i717 twrp, I used our phones recovery.
I had the same issue. The solution is simple, but takes a little bit of effort
The problem is that the ROM has a device check in the updater-script within the ROM zip file in the META-INF folder. You have to extract the zip, open the updater-script in a text editor and remove the first few lines that specify the prop checks for quincyatt and i717. Then compress it and reflash using the steps I mentioned.
Click to expand...
Click to collapse
Tried deleting lines, tried overwriting the i717 with T879, nothing.....
---------- Post added at 11:27 PM ---------- Previous post was at 11:18 PM ----------
speedysilwady said:
Not content with having only a few ROMs available for our devices, I decided to see if I could make a Jellybean ROM Porting package that you could flash on top of an i717 ROM.
I have made a flashable zip that successfully loads Jellybean ROMs just fine but with two bugs I was able to notice:
The phone does not recognize that it has any vibration hardware, so capacitive buttons and silent mode with vibration dont work.
WiFi does not turn on
What I did was take existing kernels from our current Jellybean Roms, injected our phones RIL files, and wrapped it into a flashable zip.
So far I only have those two bugs, so I am curious if anyone has any ideas what other files need to be changed to make this porting package work?
Update: I tried a bunch of different Roms and system file combinations, still having the two bugs above in every ROM.
Here's the porting package in case anyone wants to try upgrading or fixing it or testing other ROMs.
http://db.tt/iWn2gt5q
Simply wipe your phone, flash an i717 ROM, then the porting package, then wipe dalvik cache and cache.
Credits to Jamie for his awesome paranoid android ROM, from which I had used some of the files from in this package
Click to expand...
Click to collapse
We are talking about flashing an i717 ROM to a T879 correct?
---------- Post added 1st March 2013 at 12:03 AM ---------- Previous post was 28th February 2013 at 11:27 PM ----------
rekamyenom said:
Trying this now thanks! (first attempt failed)
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
Thanks! Going to try my hand at modifying now.... :cyclops:
---------- Post added at 11:05 PM ---------- Previous post was at 10:49 PM ----------
Removed as much of the updater-script that seemed logical but still getting error, Failed. Going to try to modify the updater-script again. Am I possibly removing too much? What about just overwriting the i7i7 with T879?
---------- Post added at 11:16 PM ---------- Previous post was at 11:05 PM ----------
Where does one incorporate the kernel modules into the ROM? the dhd.ko and the vibrator.ko. From where do we get them? Are they oncorporated into the port.zip he made?
Trying my hardest NOT to brick ANOTHER phone :cyclops:
---------- Post added at 11:18 PM ---------- Previous post was at 11:16 PM ----------
Tried deleting lines, tried overwriting the i717 with T879, nothing.....
---------- Post added at 11:27 PM ---------- Previous post was at 11:18 PM ----------
We are talking about flashing an i717 ROM to a T879 correct?
Click to expand...
Click to collapse
I got the ROM to write. Flashed the Port zip. Flashed ICS Blaze Modem. Wiped cache and Dalvik, Fixed permissions. Then Nothing. Gets to Samsung Screen with progression bar that goes all the way then nothing.
---------- Post added at 12:05 AM ---------- Previous post was at 12:03 AM ----------
Gonna Try it again. FYI trying to write AoCP 4.2.2
---------- Post added at 12:12 AM ---------- Previous post was at 12:05 AM ----------
No luck for me...........
---------- Post added at 12:30 AM ---------- Previous post was at 12:12 AM ----------
speedysilwady said:
Not content with having only a few ROMs available for our devices, I decided to see if I could make a Jellybean ROM Porting package that you could flash on top of an i717 ROM.
I have made a flashable zip that successfully loads Jellybean ROMs just fine but with two bugs I was able to notice:
The phone does not recognize that it has any vibration hardware, so capacitive buttons and silent mode with vibration dont work.
WiFi does not turn on
What I did was take existing kernels from our current Jellybean Roms, injected our phones RIL files, and wrapped it into a flashable zip.
So far I only have those two bugs, so I am curious if anyone has any ideas what other files need to be changed to make this porting package work?
Update: I tried a bunch of different Roms and system file combinations, still having the two bugs above in every ROM.
Here's the porting package in case anyone wants to try upgrading or fixing it or testing other ROMs.
http://db.tt/iWn2gt5q
Simply wipe your phone, flash an i717 ROM, then the porting package, then wipe dalvik cache and cache.
Credits to Jamie for his awesome paranoid android ROM, from which I had used some of the files from in this package
Click to expand...
Click to collapse
Frustrating.... I think I give up. I must be trying to flash the ROMS that Absolutelt can not be flashed to the T879. Gonna give it a break before I brick this phone....
Sad Day
speedysilwady said:
Not content with having only a few ROMs available for our devices, I decided to see if I could make a Jellybean ROM Porting package that you could flash on top of an i717 ROM.
I have made a flashable zip that successfully loads Jellybean ROMs just fine but with two bugs I was able to notice:
The phone does not recognize that it has any vibration hardware, so capacitive buttons and silent mode with vibration dont work.
WiFi does not turn on
What I did was take existing kernels from our current Jellybean Roms, injected our phones RIL files, and wrapped it into a flashable zip.
So far I only have those two bugs, so I am curious if anyone has any ideas what other files need to be changed to make this porting package work?
Update: I tried a bunch of different Roms and system file combinations, still having the two bugs above in every ROM.
Here's the porting package in case anyone wants to try upgrading or fixing it or testing other ROMs.
http://db.tt/iWn2gt5q
Simply wipe your phone, flash an i717 ROM, then the porting package, then wipe dalvik cache and cache.
Credits to Jamie for his awesome paranoid android ROM, from which I had used some of the files from in this package
Click to expand...
Click to collapse
You gotta tell me what I am doing wrong... This does not work for me at all.
+1 too.
Every roms for T-717, tried to flashing on t-879.
Everything working but Wifi.
I tried so many roms. .still problem with wifi.
Anybody had been flashing the rom sucessfully?
Thanks
Sent from my SGH-T879 using xda premium
Hi FIH-FBO Community
On the Eve of chrismas I am adding one more star for our device.
This is Shendu OS rom basically fine tuned for our device
It has
ICS Camera
File explorer with system access
3 shendu themes
Tweaked to make it stable
ADW launcher
Beats Audio libs
INIT.D tweaks
Bravia
and many more
Bugs
After selecting Shendu Launcher, settings window will not work ( Default bug). you need to select ADW Launcher to select setting.
and many which I don't know
Please note
Do full wipe (Data and dalvik cache)
Download link
http://d-h.st/g5X
Thanks
VIvek and Whyzee to help me get rid of Headset Issue
If some one is getting FCs and process acore extract this libs and copy into system/libs of your rom and then flash
Is this GB or ICS?
innocuous76 said:
Is this GB or ICS?
Click to expand...
Click to collapse
The title says Shendu OS V1 GingerBread
downloading
---------- Post added at 01:05 PM ---------- Previous post was at 12:52 PM ----------
home kbutton not working
---------- Post added at 01:12 PM ---------- Previous post was at 01:05 PM ----------
mount system -format system
mountdata-format data
and now by clean installation home key working fine
Initially the title was "Shendu OS", thats why the question.
demonskill said:
The title says Shendu OS V1 GingerBread
Click to expand...
Click to collapse
Nice and puzzeling
Sent from my A99 using xda app-developers app
Hi everyone
I have added libs for those who got FCs and process acore (other variants of MI - 410.
Copy them into system/libs of rom and flash
Newbie Question:
I want to install the KNOXRAID 2.6, do I the wipe System and Data on the STOCK ROM or perform a wipe on a newly created ROM slot 1?
Thanks
Read the OP. It clearly says exactly what to do.
Sent from my Nexus 7 2013 using XDA Premium 4 mobile app
Dont wipe stock rom slot
Butch and his Big ol Note3
---------- Post added at 08:01 AM ---------- Previous post was at 08:00 AM ----------
Create a new slot..slot 1, do a backup of you stock slot while in safestrap
Butch and his Big ol Note3
Dont wipe stock rom slot
Butch and his Big ol Note3
---------- Post added at 08:01 AM ---------- Previous post was at 08:00 AM ----------
Create a new slot..slot 1, do a backup of you stock slot while in safestrap
Butch and his Big ol Note3
+1
OnePlus cm12.1 - yesterday update to S1K2.
after intalltion everything works great UNTIL...
"su binary needs to update".
regular update passed ok.
and then:
1. tasker fail to perform a few actions that demand root (such as "sceencap -p \sdcard\folder\pic.png").
2. Titanume backup fail to backup . "rom storgage full" or somthing like this.
reintall old su zip 2.46 from recovery fixed the problems , reupdate su binary return the problems.
use one of these: http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 (same install process as 2.46)
Xmaster24 said:
use one of these: http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 (same install process as 2.46)
Click to expand...
Click to collapse
same problems.
flashed back to 2.46..
this is your device correct?: https://download.cyanogenmod.org/?device=bacon What build number are you on?
Xmaster24 said:
this is your device correct?:-- What build number are you on?
Click to expand...
Click to collapse
this is the device with last stable cm12.1 version:
Build number : LMY48Y
Cyanogen OS : 12.1.1-YOG7DAS2K1
bouhady said:
this is the device with last stable cm12.1 version:
Build number : LMY48Y
Cyanogen OS : 12.1.1-YOG7DAS2K1
Click to expand...
Click to collapse
Ah you are using Cyanogen OS cm's most despised OS. Seems to be they just updated to android 5.1.1. The Quality of this ROM is nowhere near the same as Cyanogenmod, could just be some broken port of 5.1.1
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
You are not running cm 12.1 you are running COS 12.1
Xmaster24 said:
Ah you are using Cyanogen OS cm's most despised OS. Seems to be they just updated to android 5.1.1. The Quality of this ROM is nowhere near the same as Cyanogenmod, could just be some broken port of 5.1.1
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
You are not running cm 12.1 you are running COS 12.1
Click to expand...
Click to collapse
But this is the official last version for OPO. isn't it suppoed to be supported?
Well technically OPO has no "official ROM" See they provide COS by default but they themselves also support other ROMs like Cyanogenmod. I highly recommend you get cm 13 it's well worth it
---------- Post added at 03:08 PM ---------- Previous post was at 03:02 PM ----------
cyanogen OS is managed by a different sector in Cyanongen Inc than Cyanogenmod which is mainly managed by independent developers and they are well known for making awful ROM's (that sector is)
After changing my touchscreen, when i flash any Adrian's builds or Helium kernel 6.1 my phone can't access recovery and touchscreen doesn't work. But when i use any Adrian's builds with Helium Kernel lower than 6.0 - everything works fine.
P.s. stock CM 12.1 Nightlies with CM kernel also work without issues
Using Adrian's AICP and Helium 5.0 - everything works good.
Any ideas?
The safest answer would be the kernel apparently doesn't support the newer touchscreen you installed. I suspect driver issues but I may be wrong
wuarx said:
After changing my touchscreen, when i flash any Adrian's builds or Helium kernel 6.1 my phone can't access recovery and touchscreen doesn't work. But when i use any Adrian's builds with Helium Kernel lower than 6.0 - everything works fine.
P.s. stock CM 12.1 Nightlies with CM kernel also work without issues
Using Adrian's AICP and Helium 5.0 - everything works good.
Any ideas?
Click to expand...
Click to collapse
Starting from Helium 6 I cleaned up the config file of the kernel to match Adrian's. This removed a lot of unnecessary drivers but it might have removed some options that made your touchscreen work properly. Previously I used a very old config file. I'll compare the two configs and try to build another kernel that supports your touchscreen.
Same issue here, in TWRP i cannot use my touchscreen. (I changed 2 digitizer, last one give this problem)
F*** ! Digitizer not working on cm12.1 :'(
2.attempt : CM14.0 - Digitizer not working
---------- Post added at 12:13 PM ---------- Previous post was at 11:46 AM ----------
Have you solved this problem ?
---------- Post added at 01:01 PM ---------- Previous post was at 12:13 PM ----------
Tomoms said:
Starting from Helium 6 I cleaned up the config file of the kernel to match Adrian's. This removed a lot of unnecessary drivers but it might have removed some options that made your touchscreen work properly. Previously I used a very old config file. I'll compare the two configs and try to build another kernel that supports your touchscreen.
Click to expand...
Click to collapse
Is there any solution for this ?
Iekuta said:
Is there any solution for this ?
Click to expand...
Click to collapse
This issue has been fixed by Adrian ages ago.
Tomoms said:
This issue has been fixed by Adrian ages ago.
Click to expand...
Click to collapse
i wonder what the heck is going on with my screen.
I was on 4.1.2 , waiting STRYFLEX 2.0.
I changed my digitizer 3 days ago. No problems in 3 days.
But this morning, the screen go a little crazy (touched 3-4 times itself randomly ), but i did not care so much.
After that, i reboot to recovery /to install and try Sailfish OS.
But after Fastboot flash TWRP 3.0.2 /// BAMM BOOM %#$!!
The screen is not working anymore. I will try to reflash the stock with Flashtool.
and thanks for the reply
---------- Post added at 03:19 PM ---------- Previous post was at 02:41 PM ----------
I tried 4.3 but again, no response from digitizer.
Will flash 4.1.2 and make sure that the screen is completely gone