Related
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
I haven't had any issues with downloading the CM9 HP Touchpad nightlies from Cyanogenmod, and the last one I've downloaded was on March 10. However the one on March 18 will not download. It starts and stops and 0B. Has anyone else encountered this issue? I have tried this from the TP and my GS3, so I know it isn't just a TP issue.
It doesn't give me an error. It tells me it completed the download, but like I said, it says that the filesize is 0B, and the download stops instantly. Should I begin using CM10? Is it stable enough to use as my daily yet?
Many thanks -
Kevin
Download Link is broken. Guess we could check back later
---------- Post added at 09:30 PM ---------- Previous post was at 09:26 PM ----------
I also got the same 0 bytes file. There must be some issue on the uploaded file
yup I'M having the same problem...something about Md5 check failed.... so ur not the only one nor me for that matter
Here you go:
Code:
hXXp://goo.im/devs/jcsullins/cmtouchpad/testing/cm-9-20130318-UNOFFICIAL-tenderloin.zip
(replace XX with tt)
Thread moved to Q&A, please keep questions in the Q&A section, thank you!
Escuse me if this isn't the right place, but I didn't knew where to put it since I have no privileges to post in the development forums, still my problem is that since I installed the latest Tsunami build (5.5) I wasn't able to use bigmem (amongst a few other glitches). I tried Devil Kernel utility as well as Semaphore to no avail, it says that it can't write sys/kernel/bigmem folder, I tried to create it manually using some file managers but without luck.
I'm quite stuck at it, perhaps some has acknowledge this very same problem and already solved, it would be much apreciated since my Samsung really need all the RAM it can get its hands off!
Maybe bigmem libs
vertigoz said:
Escuse me if this isn't the right place, but I didn't knew where to put it since I have no privileges to post in the development forums, still my problem is that since I installed the latest Tsunami build (5.5) I wasn't able to use bigmem (amongst a few other glitches). I tried Devil Kernel utility as well as Semaphore to no avail, it says that it can't write sys/kernel/bigmem folder, I tried to create it manually using some file managers but without luck.
I'm quite stuck at it, perhaps some has acknowledge this very same problem and already solved, it would be much apreciated since my Samsung really need all the RAM it can get its hands off!
Click to expand...
Click to collapse
with semaphore s version you have to aply patch
http://forum.xda-developers.com/showthread.php?p=30725734
---------- Post added at 01:28 PM ---------- Previous post was at 01:23 PM ----------
JB_BigMem_26-aug-12.zip
http://forum.xda-developers.com/showpost.php?p=30725734&postcount=61
idroj said:
with semaphore s version you have to aply patch
http://forum.xda-developers.com/showthread.php?p=30725734
---------- Post added at 01:28 PM ---------- Previous post was at 01:23 PM ----------
JB_BigMem_26-aug-12.zip
http://forum.xda-developers.com/showpost.php?p=30725734&postcount=61
Click to expand...
Click to collapse
Thanks... It's that with Tsunami 5.2 it worked, so I find it strange this 'downgrade', well a bit of things changed as well. I'll try to see if this solve it.
BTW do you know how to install the patch?
idroj said:
with semaphore s version you have to aply patch
http://forum.xda-developers.com/showthread.php?p=30725734
---------- Post added at 01:28 PM ---------- Previous post was at 01:23 PM ----------
JB_BigMem_26-aug-12.zip
http://forum.xda-developers.com/showpost.php?p=30725734&postcount=61
Click to expand...
Click to collapse
It made it worse, got a black background and my status bar ceased to work
Send a private message to Tsunami developer
I will try a clean flash, and if you change the kernel, mount data and datadata anf fix permissions. If problem persists send a PM to developer.
When i have a question to developer I send PM if I don't find a solution.
vertigoz said:
Escuse me if this isn't the right place, but I didn't knew where to put it since I have no privileges to post in the development forums, still my problem is that since I installed the latest Tsunami build (5.5) I wasn't able to use bigmem (amongst a few other glitches). I tried Devil Kernel utility as well as Semaphore to no avail, it says that it can't write sys/kernel/bigmem folder, I tried to create it manually using some file managers but without luck.
I'm quite stuck at it, perhaps some has acknowledge this very same problem and already solved, it would be much apreciated since my Samsung really need all the RAM it can get its hands off!
Click to expand...
Click to collapse
Hi bro,
try to install SEMAPHORE 3.0.0s... or wait for new TSUNAMI 5.6 ...... I'll realese it today...
Lory
xlory said:
Hi bro,
try to install SEMAPHORE 3.0.0s... or wait for new TSUNAMI 5.6 ...... I'll realese it today...
Lory
Click to expand...
Click to collapse
\o/ )
idroj said:
I will try a clean flash, and if you change the kernel, mount data and datadata anf fix permissions. If problem persists send a PM to developer.
When i have a question to developer I send PM if I don't find a solution.
Click to expand...
Click to collapse
Well, I will probably do it in the future, thanks for the advice.
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
14.6 flat out doesn't work for me. 14.5 works but has a looping logcat issue that generates around 30gb of logs a day and drains battery in a hurry. Works ok for me, but won't work for my wife's phone (having her go in once every day or two to clear the logs is a non-starter). 14.37 is reported by some as working without the issue, but I can't find it anywhere. I attempted a build from source, however there is an issue with the sub module pull of SE linux for that tag, so I'm unable to build it myself. 14.0 isn't an option as it won't install on an Essential PH-1.
The segfault with v14.6 on Essential phones is known. No idea if it can be fixed though. Let's hope so...
Meanwhile, you can find old release on GitHub.
Didgeridoohan said:
Meanwhile, you can find old release on GitHub.
Click to expand...
Click to collapse
Since I'm not a dev and I'm on my phone and have the exact same problem (Magisk tell me to update to 14.6 and it cause bootloop, I have flah my phone with a backup to unbrick it), do you know where to find a useable version of Magisk 14.5, like you download and flash and it works?
And why do the dev erase old beta versions? It makes things complicated for no reasons... Magisk 14.5 was the only one to work on my phone. 14 don't works and 14.6 creates bootloop.
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
Ok, one nice guy put it here : http://www.rootandroidblog.com/download-magisk-v-14-5-zip-last-release/
Already in use said:
Since I'm not a dev and I'm on my phone and have the exact same problem (Magisk tell me to update to 14.6 and it cause bootloop, I have flah my phone with a backup to unbrick it), do you know where to find a useable version of Magisk 14.5, like you download and flash and it works?
And why do the dev erase old beta versions? It makes things complicated for no reasons... Magisk 14.5 was the only one to work on my phone. 14 don't works and 14.6 creates bootloop.
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
Ok, one nice guy put it here : http://www.rootandroidblog.com/download-magisk-v-14-5-zip-last-release/
Click to expand...
Click to collapse
For future reference, there's also the unofficial snapshots, where you can find builds by @DodoGTA and @kantjer.