I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Features:
-touchwiz ui with near stock functionality
-based on Tab A and Tab S frameworks
-Tab S2 apps
-Tab S3 UI Sounds
-SPen features
-theme support
-pre-rooted (magisk)
-deodexed
-debloated
-knox removed
-all apps support multiwindow
-some minor changes like removing safe volume warning, overlay fix etc
-ported IronKernel from @Tkkg1994 (read more about kernel features here: https://forum.xda-developers.com/galaxy-tab-s/orig-development/kernel-ironstock-kernel-v3-2-t3531295 )
Notes:
full wipe required!
First boot takes 10 minutes
For some features root required
Device encryption doesn't support here
If you don't want to install root, remove magisk folder from install zip
If you don't have working spen, flash stock rom before this one.
If you want to make custom rom based on my rom, you're welcome.
Thanks to @Miron24 for testing rom
Download:
02feb
gdrive: https://drive.google.com/open?id=1sAiyxBEkEDEWtOiuMvOM53DKWmAVWHQx
Thanks to @Tkkg1994 for the kernel
Kernel sources:
https://github.com/bonuzzz/IronKernel
I'll download and give this a shot. I really need all apps in multi windows.
How works SPEN?
write me please your feedback, what working or not working in hardware part
won't work on p600,
@maxximboy black screen after bootloader without any reboots?
@bonuzzz
Do your roms (P900, P600, T900) work on 3G devices(P901, etc.)? I want to test your rom on my P601. Do you plan to port Tab A 10.1 with S Pen apps to your roms?
Miron24 said:
@bonuzzz
Do your roms (P900, P600, T900) work on 3G devices(P901, etc.)? I want to test your rom on my P601. Do you plan to port Tab A 10.1 with S Pen apps to your roms?
Click to expand...
Click to collapse
if you dont need 3g support, so it should working. but current version doesn't boot on p600. trying to find, where is problem in kernel. wait for fix.
do you want exact app from tab A ?
Hi there, good to see this kind of development. I tried flashing, but install was unsuccessful.
Previous ROM is Resurrection Remix for P600
Went to recovery, did factory reset on TWRP, then wiped System partition
Flashed your zip, and out comes on the terminal:
This package is for "v1awifi, v2awifi, n1awifi, n2awifi, klimtwifi, chagallwifi" devices, this is a "lt03wifiue"
Updater process ended with ERROR: 7
So I assume the problem lies somewhere with the device name/code, but I'm not sure how to change this. From what I've searched it's in build.prop, but that doesn't exist one /system is wiped. After wiping everything I tried flashing AICP Rom, but still the same error code comes out when I tried flashing your .zip. Have any other tips? I assume you also have a P600 no? How did you get it to boot?
EDIT: Thanks for correcting noob mistake @mosimchah
Pact said:
Previous ROM is Resurrection Remix for P600 ie AOSP based
Click to expand...
Click to collapse
Resurrection Remix is lineage based, and lineage is caf based (not AOSP)
Sent from my LEX727 using XDA Labs
---------- Post added at 06:07 PM ---------- Previous post was at 06:00 PM ----------
bonuzzz said:
if you dont need 3g support, so it should working. but current version doesn't boot on p600. trying to find, where is problem in kernel. wait for fix.
do you want exact app from tab A ?
Click to expand...
Click to collapse
Check out the unofficial Lineage 13.0 kernel, it's based on the tab s mm source and works on the p600
https://github.com/exynos5420/andro...configs/cyanogenmod_deathly_n1awifi_defconfig
https://github.com/exynos5420/andro...tree/091b5954799bbfbb38bced4ac6342c5939900348
Sent from my LEX727 using XDA Labs
ok, lt03wifiue is also p600. I didn't know that. you could remove assert in updater-script to disable check device.
@Pact I have P900
OK, I removed the assert lines as per this guide:
https://forum.xda-developers.com/showpost.php?p=31519426&postcount=186
Used 7zip, edited the file mentioned above, deleted the lines, 7zip recompiles that, moved it to SD card and started flashing. Of course I did a factory reset beforehand, and wiped /system too. The usual stuff appears:
Checking config . . .
Formatting system . . .
Extracting system . . .
The flash was successful, then the Magisk installation lines appear and that was good too.
Once that's done, I flashed the kernel provided above, and that complete, I rebooted the tablet, no other warnings or anything like that appearing during installation. The Galaxy Note screen appeared, then the screen went black (lights on, nothing else displayed). I thought this was normal for a new flash, then I waited till 20 minutes and it's still like that. So I forced a reboot (long press power button) and the Galaxy Note screen appeared again, this time I've waited 5 minutes and nothing else happens - still lighted screen with nothing else. The backside is hot during both reboots, so something is definitely happening using CPU cycles, but I'm not sure what. Should I dirty reflash next?
bonuzzz said:
ok, lt03wifiue is also p600. I didn't know that. you could remove assert in updater-script to disable check device.
Test please this kernel
https://yadi.sk/d/WGxcpVrn3K6G7R
@Pact I have P900
Click to expand...
Click to collapse
Make sure you're using the proper vendor blobs
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/n1awifi
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/nx-common
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/exynos5420-common
Using the tab s blobs could cause it to not boot
Pact said:
OK, I removed the assert lines as per this guide:
https://forum.xda-developers.com/showpost.php?p=31519426&postcount=186
Used 7zip, edited the file mentioned above, deleted the lines, 7zip recompiles that, moved it to SD card and started flashing. Of course I did a factory reset beforehand, and wiped /system too. The usual stuff appears:
Checking config . . .
Formatting system . . .
Extracting system . . .
The flash was successful, then the Magisk installation lines appear and that was good too.
Once that's done, I flashed the kernel provided above, and that complete, I rebooted the tablet, no other warnings or anything like that appearing during installation. The Galaxy Note screen appeared, then the screen went black (lights on, nothing else displayed). I thought this was normal for a new flash, then I waited till 20 minutes and it's still like that. So I forced a reboot (long press power button) and the Galaxy Note screen appeared again, this time I've waited 5 minutes and nothing else happens - still lighted screen with nothing else. The backside is hot during both reboots, so something is definitely happening using CPU cycles, but I'm not sure what. Should I dirty reflash next?
Click to expand...
Click to collapse
Sent from my LEX727 using XDA Labs
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
bonuzzz said:
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
Click to expand...
Click to collapse
I'm not using this ROM, just happened to see the thread
Sent from my LEX727 using XDA Labs
bonuzzz said:
@maxximboy black screen after bootloader without any reboots?
Click to expand...
Click to collapse
no no black or blank screen, it wont flash the rom, message was something like, my p600 is not compatible.
View attachment tombstones.zip
View attachment last_kmsg.txt
bonuzzz said:
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
Click to expand...
Click to collapse
Hre's those files. After the second black blank screen that I mentioned in my previous post, I rebooted to recovery and grabbed these from the file manager. There's 10 tombstone files in the folder so I zipped it up. Hope it helps.
I am really excited about this rom, and cant wait to flash it on my p600..... i am not techies as you guys, so my question is, what do i need to do to make it work?
thanks all
maxximboy said:
I am really excited about this rom, and cant wait to flash it on my p600..... i am not techies as you guys, so my question is, what do i need to do to make it work?
thanks all
Click to expand...
Click to collapse
It need proper kernel ...patience
I need a tester, who will spend some time to flash couple of builds. write in pm
thanks in advance
Related
DISCLAIMER:
Your device, your responsibility. I am not liable for anything you flash, including this.
As a result you'll probably want to read the rest of the thread and at least be aware of what you're flashing.
You've been warned.
CM: CWM Based Recovery for SPH-L720 (jfltespr)​
Features:
This is comes from CM as it is provided in the source repos. I will be keeping it as such at this time.
Only deviations are to allow it to build properly and are generally from CM repos.
If modifications deviate from CM source we will set up a new repo.
Screenshots: None
Latest Build: v1.0
Tar/ZIP Mirror: [CWM][RECOVERY]Team SXTP CWM for Galaxy S4 (Team SXTP Site)
Flash Instructions:
Boot to Odin Mode and flash via Odin.
Summary Changelog:
Code:
v1.0 - Final Prealpha, successful operations and display
Prealpha Builds - Initial Buildup.
Source:
CyanogenMod Official Repositories
Device Dependencies:
android_device_samsung_jf-common
android_device_samsung_msm8960-common
android_device_samsung_qcom-common
Sprint GS4 Device Repository
NOTE: Due to potential copyright issues I do not include a vendor repo.
You can extract the files from the phone or ROM as needed - should you decide to build on your own.
Credits:
Early Bringup Advice: Entropy512, Shabbypenguin, Cordell12
Current Advisors/Collaborators: Noobnl (CM CDMA Maintainer)
Testers: Mohogalore, robbyamor, crawj and others
Steve Kondik (Cyanogen) for CM development and jf common work
The CM maintainters who continue to improve CM along with Mr. Kondik
The crew that is Paranoid Android - Pure Hybrid!
...and of course! You, the community, for your support as well! Thank you!
Heard this has bad graphics so will revisit asap
Sent from my SPH-L900 using Tapatalk 2
garwynn said:
Heard this has bad graphics so will revisit asap
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Sorry for not reporting that here. Ever since I screwed up my phone I've been killing time by flashing every recovery firmware I got my hands on. I'll probably keep testing before the stock image comes out.
Running this now... as stated graphics do not redraw every other click but it does function normally otherwise. Just made a backup which completed normally.
edit... navigation is also a little touchy vol down will sometimes register as enter.
did a full wipe booted fine now to restore.
Thanks - working on a possible graphics fix at the moment.
Will post Alpha 4 when it's ready.
harrybozack said:
Sorry for not reporting that here. Ever since I screwed up my phone I've been killing time by flashing every recovery firmware I got my hands on. I'll probably keep testing before the stock image comes out.
Click to expand...
Click to collapse
Define screwing up the phone... just curious if can get it back running.
I have a stock ROM that is uploaded but will have to rename to pull from web.
restore completed and looks good
lafester said:
restore completed and looks good
Click to expand...
Click to collapse
Very nice! So you're functioning normally?
I will test this CWM to see how it works, i did test shabby penguins version and got a bug where it would only let me select every other selection and didnt recognize the selection.
Alpha 4 posted.
MoHoGalore said:
Very nice! So you're functioning normally?
Click to expand...
Click to collapse
yes everything restored that I can tell. navigating cwm is difficult though at the moment with the graphics error
same result on Alpha 3 for me. Will test Alpha 4
---------- Post added at 12:04 PM ---------- Previous post was at 12:00 PM ----------
just tested Alpha 4 and same results. Only lets me select every other selection and when i do make a selection the menu goes away and im left with the CWM logo and label on the bottom. Have to hold power to reboot.
when you have a blank screen hit vol down to enable the graphics
Sounds like need to play with recovery keys a little more. Glad it is functionally working though!
Sent from my SPH-L900 using Tapatalk 2
garwynn said:
Define screwing up the phone... just curious if can get it back running.
I have a stock ROM that is uploaded but will have to rename to pull from web.
Click to expand...
Click to collapse
Well it's stuck in a boot loop. I flashed recovery firmware for the i9505 instead of my model phone and one of them screwed up big time. My own fault for being careless.
lafester said:
when you have a blank screen hit vol down to enable the graphics
Click to expand...
Click to collapse
well i did that but then it goes to a loose root access type screen. i always check no but then it reboots.
garwynn said:
Define screwing up the phone... just curious if can get it back running.
I have a stock ROM that is uploaded but will have to rename to pull from web.
Click to expand...
Click to collapse
Wait so you have the stock rom for the SPH-L720? I'd love to try flashing that to fix my problems.
Alpha 4 works, except you need to count key presses. Every other press changes highlighted selection but every press registers for choice (if that makes sense.) When pressing enter to make selection, press volume down to "wake up" the screen.
Backup successful. Restore successful.
I can make a video if that would be easier to explain what I'm seeing, if needed.
:edit: Location for backup is normal - /data/media/clockworkmod/backups - Must have been something I did. Disregard previous statement.
MoHoGalore said:
Alpha 4 works, except you need to count key presses. Every other press changes highlighted selection but every press registers for choice (if that makes sense.) When pressing enter to make selection, press volume down to "wake up" the screen.
Backup successful. Restore successful.
I can make a video if that would be easier to explain what I'm seeing, if needed.
:edit: Location for backup is normal - /data/media/clockworkmod/backups - Must have been something I did. Disregard previous statement.
Click to expand...
Click to collapse
You had the same experience as I did. Worked fine just hard to navigate.
In other news I just activated my phone and it did a factory reset and installed on the sprint crap. It did not wipe sd so my backup is still there. attempting to restore now.
update: restore successful
Update with Alpha 4 and testing of Garwynn's test builds: Actions taken in this order;
(Started with Alpha 4 already flashed)
1. Backup - Successful
2. Restore - Successful
3. Flashed Stock Dump Recovery - Successful
4. Flashed Stock Dump Kernel - Successful
5. Flashed Stock Dump Rom - Successful
6. Flashed Alpha 4
7. Performed Wipe Data/Factory reset- successful
8. Rebooted system
9. Restored previous backup - Successful
(Used Odin 1.85 for Stock build flashes)
Hi all! I just finished porting Paranoid Android Beta 5 (Oct 22, 2014) to our beloved Vibrant. My only problem is my Vibrant is my daily driver. Can any kind soul whose Vibrant is not your daily driver (or if you just like to live on the bleeding edge) please test this out for me?
ROM *EDIT: Wi-Fi not working yet. Wi-Fi working now, but took down link to wait for original dev's permission. I have permission now, but I keep getting "No SD card" error
PA Gapps
Official PA5 xda link of the Rom I ported (i9000/galaxysmtd)
Permission from the official Rom maintainer is still pending, hopefully I'll get it soon.
Thank you so much!
Edit: I suppose I should include these steps (copied from xda thread above):
Installation Instructions
Coming other ROM
1. You must be rooted!
2. You must have a custom recovery installed.
3. Wipe your device if you are not coming from PA 4.+ already.
4. Flash the ROM zip, it could appear a warning (all data will be wiped due different partition table)
5. Reflash the ROM zip, it will continue now.
6. Flash the GAPPS.
7. Reboot. (It can take up to 5 min.)
8. Enjoy
Coming from AOSPA 4.0+
NOTE: I'm not responsible of crashes due kernel changes.
1. Flash the ROM zip.
2. Reboot.
3. Wait the upgrading android dialog.
4. Enjoy!
Click to expand...
Click to collapse
I don't know why I was hesitating - I could just take a Nandroid backup before flashing. I just did this, and I'm happy to report that everything went just fine! The only snag I had was a Wi-Fi problem - it says "Turning Wi-Fi on", but just stays like that. I remember seeing this problem somewhere before, maybe the kernel. Will investigate and report back
------
Edit (4.41pm cst):
SIGH... Been researching and trying out solutions all this time, and nothing's working Tried NeatKernel, Semaphore kernel, neither worked. Will keep at it and report back.
raddatt said:
I don't know why I was hesitating - I could just take a Nandroid backup before flashing. I just did this, and I'm happy to report that everything went just fine! The only snag I had was a Wi-Fi problem - it says "Turning Wi-Fi on", but just stays like that. I remember seeing this problem somewhere before, maybe the kernel. Will investigate and report back
------
Edit (4.41pm cst):
SIGH... Been researching and trying out solutions all this time, and nothing's working Tried NeatKernel, Semaphore kernel, neither worked. Will keep at it and report back.
Click to expand...
Click to collapse
you need to copy over system/lib/modules from base to port or from custom kernel if that what you're using, in order to get wifi working. I could of sworn PA was patched a certain way and would only run with its provided kernel or maybe something has changed since i last tried to port it for personal use. Also not a great idea posting ones work with out getting full permission yet may cause you trouble later on down the road...
dzee206 said:
you need to copy over system/lib/modules from base to port or from custom kernel if that what you're using, in order to get wifi working. I could of sworn PA was patched a certain way and would only run with its provided kernel or maybe something has changed since i last tried to port it for personal use. Also not a great idea posting ones work with out getting full permission yet may cause you trouble later on down the road...
Click to expand...
Click to collapse
Omg, that worked beautifully! Thank you so much, kind sir! I've also taken down the Rom download link and will put it back up again once I have full permission. Thanks for prompting me to do it. This is my first time at porting a Rom, so I'm not fully caught up on the etiquette yet. I've asked him for permission, and thought I could put it up only for testing purposes in the meantime, and then post it fully in our development forum once I have his full permission. He has been pretty great so far with granting a few people permission on that thread, so hopefully I can become one of them soon Thanks again so much!
Okay, it seems like I'm having another problem/bug. My phone's not detecting its SD card. When I tried to download a file it said, "No SD card". When I went to Settings/Storage, there are 2 areas of storage as usual, but it only lasts for about 3 seconds, then all the rows collapse and all I'm left with is "Internal Storage" and a couple of rows - no sight of an SD card. Is this something you've come across?
raddatt said:
Okay, it seems like I'm having another problem/bug. My phone's not detecting its SD card. When I tried to download a file it said, "No SD card. When I went to Settings/Storage, there are 2 areas of storage as usual, but it only lasts for about 3 seconds, then all the rows collapse and all I'm left with is "Internal Storage" and a couple of rows - no sight of an SD card. Is this something you've come across?
Click to expand...
Click to collapse
Try flashing one of the custom kernels we have and see if that works, if it doesn't help solve the issues it may just be kernel related. If all else fails give this a shot http://forum.xda-developers.com/showpost.php?p=51293597&postcount=151<br /> and if that doesn't help try porting a previous version of PA and see if the SD will mount properly.
For some reason whenever I flash a kernel, everything goes well until the "Android is upgrading" point. All apps are updated, then it says "starting apps" or something and it doesn't go anywhere after that, just stuck on that stage Then when I tried to reboot into recovery, it would be really difficult for some reason (like holding the buttons down would cause boot looping, very finicky). When I finally did get into recovery, it turned out to be Twrp, and not the Cwm I was used to. I have no idea where it came from, esp since I believe both port and base were cwm! I got really scared for a few minutes because twrp didn't have my backups. Finally, after a few more reboots, I got back the familiar cwm. I've never been so relieved in my life lol. I'm back to my old state, and will try again tomorrow morning. That's what I get for trying to play hero haha
Sent from my Vibrant using ugly ass xda app.
raddatt said:
For some reason whenever I flash a kernel, everything goes well until the "Android is upgrading" point. All apps are updated, then it says "starting apps" or something and it doesn't go anywhere after that, just stuck on that stage Then when I tried to reboot into recovery, it would be really difficult for some reason (like holding the buttons down would cause boot looping, very finicky). When I finally did get into recovery, it turned out to be Twrp, and not the Cwm I was used to. I have no idea where it came from, esp since I believe both port and base were cwm! I got really scared for a few minutes because twrp didn't have my backups. Finally, after a few more reboots, I got back the familiar cwm. I've never been so relieved in my life lol. I'm back to my old state, and will try again tomorrow morning. That's what I get for trying to play hero haha
Sent from my Vibrant using ugly ass xda app.
Click to expand...
Click to collapse
Its fine you ended up with twrp that happens when you flash a kernel that comes with twrp, see our device recovery image is within the kernel. I actually prefer twrp over cwm due to it being touch screen and putting less stress/abuse on the volume and power button/s. I checked the i9000 thread of PA and didn't see any users with the SD not mounting so I'm guessing it could be kernel related. If i can get my hands on my wife's vibrant I'll do a personal port and let you know of the results.
dzee206 said:
Its fine you ended up with twrp that happens when you flash a kernel that comes with twrp, see our device recovery image is within the kernel. I actually prefer twrp over cwm due to it being touch screen and putting less stress/abuse on the volume and power button/s. I checked the i9000 thread of PA and didn't see any users with the SD not mounting so I'm guessing it could be kernel related. If i can get my hands on my wife's vibrant I'll do a personal port and let you know of the results.
Click to expand...
Click to collapse
Ah, yes, from the kernel, that makes sense. Yeah, I'm glad more people are switching to Twrp because I like the touchscreen too instead of hurting the physical buttons. There's also a kernel (Semaphore?) that uses touchscreen scrolling in Cwm, which is cool too. Thank you, I'd really appreciate that!
Also, can you please show me how to properly bring an outside kernel into a Rom? I have been following this guide. It says to replace:
bml_over_mtd
bml_over_mtd.sh
erase_image
file_contexts
flash_image
make_ext4fs
boot.img
Plus system/lib/modules per your suggestion. However, I was about to try Iyahman's kernel, but it doesn't have:
file_contexts
flash_image
make_ext4fs
system/lib/modules
How would that work?
Btw, I just tried pulling the kernel resources of the kernel used by SlimKat into PA5 rom, but I still get the No SD card error
Our SlimKat rom uses the "samsung kernel aries", which is also used by the i9000 PA rom, so I thought it would work this time, but nope.
@dzee206 - Sorry for the spamming, man, but I just wanted to clarify the SD card problem I'm having, because I'm a bit confused as to what exactly it is. So when I try to download an .apk off of an xda thread using Browser, I get the error:
"No SD Card
An SD card is required to download ...apk"
But I am able to successfully download an app from the Play Store and use it well.
When I open Gallery, I get this error:
"No Storage
No external storage available"
Sorry I'm a big noob, but is the phone saying I don't have an external card or an internal card? I've never had these problems on this phone before, and I've never used an external SD on it. Thanks.
raddatt said:
Also, can you please show me how to properly bring an outside kernel into a Rom? I have been following this guide. It says to replace:
bml_over_mtd
bml_over_mtd.sh
erase_image
file_contexts
flash_image
make_ext4fs
boot.img
Plus system/lib/modules per your suggestion. However, I was about to try Iyahman's kernel, but it doesn't have:
file_contexts
flash_image
make_ext4fs
system/lib/modules
How would that work?
Click to expand...
Click to collapse
You only need the files in the root of the kernel (zip) not the folders though, don't worry about the modules with semaphore that's just how it is. Just leave file_contexts, flash_image, make_ext4fs that came with PA while porting they should suffice. Sorry man I ported PA yesterday while at my in-laws but didn't get a chance to transfer it over. I'd do it while at home but my PC exhaust fan crapped out on me and I won't have time to replace it till the beginning of next week. For now the best I can do is give advice base on my experience porting. May wanna give a different ROM a shot at porting such as DU or Mackay.
Sent from my SGH-I717 using XDA Premium 4 mobile app
dzee206 said:
You only need the files in the root of the kernel (zip) not the folders though, don't worry about the modules with semaphore that's just how it is. Just leave file_contexts, flash_image, make_ext4fs that came with PA while porting they should suffice. Sorry man I ported PA yesterday while at my in-laws but didn't get a chance to transfer it over. I'd do it while at home but my PC exhaust fan crapped out on me and I won't have time to replace it till the beginning of next week. For now the best I can do is give advice base on my experience porting. May wanna give a different ROM a shot at porting such as DU or Mackay.
Sent from my SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man, I really appreciate your advice and efforts. Will try a couple more things and report back.
I tried putting Iyahman's Semaphore kernel stuff into PA5 and using SlimKat as base, but it didn't work I got the error 7, that the ROM was for i9000 and not for T959. I don't get why it happened... I deleted the i9000 lines from updater-script and everything, just like previous attempts (the rom had actually loaded properly in previous attempts, so the difference here must lie in the using of the kernel or SlimKat as base).
raddatt said:
I tried putting Iyahman's Semaphore kernel stuff into PA5 and using SlimKat as base, but it didn't work I got the error 7, that the ROM was for i9000 and not for T959. I don't get why it happened... I deleted the i9000 lines from updater-script and everything, just like previous attempts (the rom had actually loaded properly in previous attempts, so the difference here must lie in the using of the kernel or SlimKat as base).
Click to expand...
Click to collapse
Never use a ported ROM as base it be best to use the unofficial cm11 or spirit ROM, since those are the only ROMs we have that's built from source. Honestly if it was me I'd give up on PA and look for something else to run there's plenty of i9000 ROMs that have yet to be ported over or hasn't been updated I a while.
Sent from my SGH-I717 using XDA Premium 4 mobile app
dzee206 said:
Never use a ported ROM as base it be best to use the unofficial cm11 or spirit ROM, since those are the only ROMs we have that's built from source. Honestly if it was me I'd give up on PA and look for something else to run there's plenty of i9000 ROMs that have yet to be ported over or hasn't been updated I a while.
Sent from my SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ahh, thanks! I read somewhere that both base and port should both be either CM-based or AOSP-based, so I guess I started looking for AOSP-based roms and decided to try SlimKat. But I'll make sure not to use ported roms anymore. I tried the cm11 one, I might try Spirit as a last ditch effort, then see what else is on i9000. When Paranoid updated their website this week, I had checked it out, and when I saw galaxymtd as one of the legacy devices, I had gotten excited at the prospect of a new-ish rom. But lemme see what else is on i9000 after I try a couple more things here. Thanks again!
raddatt said:
Ahh, thanks! I read somewhere that both base and port should both be either CM-based or AOSP-based, so I guess I started looking for AOSP-based roms and decided to try SlimKat. But I'll make sure not to use ported roms anymore. I tried the cm11 one, I might try Spirit as a last ditch effort, then see what else is on i9000. When Paranoid updated their website this week, I had checked it out, and when I saw galaxymtd as one of the legacy devices, I had gotten excited at the prospect of a new-ish rom. But lemme see what else is on i9000 after I try a couple more things here. Thanks again!
Click to expand...
Click to collapse
It's some what true about using the same type of based ROMs when it comes to porting but pickings are slim. Myself and a bunch of other porters have been using cm as base and haven't had any issues porting different type ROMs.
Sent from my SGH-I717 using XDA Premium 4 mobile app
Dual boot Patcher now works with our v20 I can confirm it works with the h918 but I cannot confirm it works with any of the others but as they are the same Hardware I cannot see why not.
I take no credit for this mod as all I did was send the original developer the necessary files to get it working on our phones, so go give @chenxiaolong a thanks and go here http://forum.xda-developers.com/showthread.php?t=2447534&page=1083
To download the latest snapshot and DualBoot utilities to easily managed between the two or three or however many you get.
This will really come in handy once we get Aosp up and running for our devices! Set alarm just putting this here in case anyone is interested.
jthrasher47 said:
Dual boot Patcher now works with our v20 I can confirm it works with the h918 but I cannot confirm it works with any of the others but as they are the same Hardware I cannot see why not.
I take no credit for this mod as all I did was send the original developer the necessary files to get it working on our phones, so go give @chenxiaolong a thanks and go here http://forum.xda-developers.com/showthread.php?t=2447534&page=1083
To download the latest snapshot and DualBoot utilities to easily managed between the two or three or however many you get.
This will really come in handy once we get Aosp up and running for our devices! Set alarm just putting this here in case anyone is interested.
Click to expand...
Click to collapse
Thank you so much for the heads up on this! I used this on my Note 4 and loved it!
Sent from my LG-H918 using Tapatalk
Thanks for sharing! Works great! Just flashed CM as secondary
Be warned, I used this with NATFs ROM as a primary and CM as secondary and I got locked out of my phone when going back to NATFs ROM. Pattern lock said it was wrong pattern. So be careful and disable lockscreen and fingerprints before doing this. There are still some bugs floating around.
But nice job and great progress for our phones!!!
jthrasher47 said:
Dual boot Patcher now works with our v20 I can confirm it works with the h918 but I cannot confirm it works with any of the others but as they are the same Hardware I cannot see why not.
I take no credit for this mod as all I did was send the original developer the necessary files to get it working on our phones, so go give @chenxiaolong a thanks and go here http://forum.xda-developers.com/showthread.php?t=2447534&page=1083
To download the latest snapshot and DualBoot utilities to easily managed between the two or three or however many you get.
This will really come in handy once we get Aosp up and running for our devices! Set alarm just putting this here in case anyone is interested.
Click to expand...
Click to collapse
For some reason I'm losing root on my secondary rom. I checked the dual boot thread and did not figure it out. Any ideas on what I can try? Thanks
Edit: I figured it out. If I flash it in twrp root sticks.
Sent from my LG-H918 using Tapatalk
For future reference for anyone with root sticking problems.. Just patche the SuperSU. Zip for dual or multi whatever you are going to use then flash it either in app or recovery and when you are booted into your secondary Rom make sure to set kernel accordingly
dfogelstrom said:
Be warned, I used this with NATFs ROM as a primary and CM as secondary and I got locked out of my phone when going back to NATFs ROM. Pattern lock said it was wrong pattern. So be careful and disable lockscreen and fingerprints before doing this. There are still some bugs floating around.
But nice job and great progress for our phones!!!
Click to expand...
Click to collapse
If you do run into this, delete all `lockscreen.db*` files in `/data/system/`.
Yes, it is good etiquette to remove lock screen patterns and fingerprints before installing a new ROM in any of your slots as it will not let you in when you go back to the other
I was having issues with this on my ls997. I was running teamdev ROM with werewolf kernel set as primary. I patched resurrection remix for secondary and tried to flash through app and got an error. So I tried to flash from TWRP and it failed to flash. I saw an error about the us996 at some point. Anyone have this working on ls997? What am I doing wrong?
almony8 said:
I was having issues with this on my ls997. I was running teamdev ROM with werewolf kernel set as primary. I patched resurrection remix for secondary and tried to flash through app and got an error. So I tried to flash from TWRP and it failed to flash. I saw an error about the us996 at some point. Anyone have this working on ls997? What am I doing wrong?
Click to expand...
Click to collapse
Did you patch the Rom and gapps zips before flashing?
Yes I patched them. I even tried downloading the ROM again. Still no luck. Any other thoughts?
almony8 said:
Yes I patched them. I even tried downloading the ROM again. Still no luck. Any other thoughts?
Click to expand...
Click to collapse
What's the error?
Zacharee1 said:
What's the error?
Click to expand...
Click to collapse
I didn't get a screenshot or anything but it said something about it not being a h918. It said like file type unrecognized
almony8 said:
I was having issues with this on my ls997. I was running teamdev ROM with werewolf kernel set as primary. I patched resurrection remix for secondary and tried to flash through app and got an error. So I tried to flash from TWRP and it failed to flash. I saw an error about the us996 at some point. Anyone have this working on ls997? What am I doing wrong?
Click to expand...
Click to collapse
Unfortunately this dual boot Patcher is setup for the h918.
So what you were going to have to do to get it working is extract the entire Resurrection ROM folder and open the updater script and remove the get prop lines and then save the file and rezip then patch and Flash after that all should be well
jthrasher47 said:
Unfortunately this dual boot Patcher is setup for the h918.
So what you were going to have to do to get it working is extract the entire Resurrection ROM folder and open the updater script and remove the get prop lines and then save the file and rezip then patch and Flash after that all should be well
Click to expand...
Click to collapse
I'll hold off I guess until RR gets a little further along instead of messing with it now
almony8 said:
I was having issues with this on my ls997. I was running teamdev ROM with werewolf kernel set as primary. I patched resurrection remix for secondary and tried to flash through app and got an error. So I tried to flash from TWRP and it failed to flash. I saw an error about the us996 at some point. Anyone have this working on ls997? What am I doing wrong?
Click to expand...
Click to collapse
works fine
almony8 said:
I'll hold off I guess until RR gets a little further along instead of messing with it now
Click to expand...
Click to collapse
It works
I admit its a bit confusing but once you figure it out it will be so easy to use
ricohz said:
works fine
Click to expand...
Click to collapse
Did you do what he said to do with removing the prop stuff or just install and use regular?
---------- Post added at 10:56 PM ---------- Previous post was at 10:54 PM ----------
ricohz said:
It works
I admit its a bit confusing but once you figure it out it will be so easy to use
Click to expand...
Click to collapse
I used this dual boot before on old phones without issues, just not working for me on this phone. I'll give it another shot when I have the time
just a regular install
I was having trouble with patching the zip files
so with file explorer I went to file's location and saw that the patch files were way smaller(for example gapps patch zip was like 20mg) so i deleted all the files and started over
jthrasher47 said:
Unfortunately this dual boot Patcher is setup for the h918.
So what you were going to have to do to get it working is extract the entire Resurrection ROM folder and open the updater script and remove the get prop lines and then save the file and rezip then patch and Flash after that all should be well
Click to expand...
Click to collapse
Device.json? Or am I in the wrong file?
ATTENTION EVERYONE (For everyone who attempted to install this ROM):
This ROM breaks the Tab splash screen and does harm to the Tablet.
I recommend calling 1-800-SAMSUNG, and ask for a factory re-flash. Do not say anything that you are / were rooted. This should be 100% free, they even pay for shipping. They did mine for free. I recommend doing this ASAP, before more damage might come to the Tablet.
Downloading and testing, do you need anything else? Like the twrp?
edit 1:
Impossible to install, the updater is badly configured, I can not locate the problem, even with normal recovery will not let me install, I will continue to try
edit 2:
Well I found the error, the rom is not well developed, did you do with some automated program? I remember that the tablet 10.1 has another processor and that the compatibility of a direct port without changing the drivers is impossible
jimmy999x said:
Downloading and testing, do you need anything else? Like the twrp?
edit 1:
Impossible to install, the updater is badly configured, I can not locate the problem, even with normal recovery will not let me install, I will continue to try
edit 2:
Well I found the error, the rom is not well developed, did you do with some automated program? I remember that the tablet 10.1 has another processor and that the compatibility of a direct port without changing the drivers is impossible
Click to expand...
Click to collapse
I made it on ES File Explorer, on my Nook, it took me an hour... I had ported it from Acclaim RC5 and Docker 6 Degaswifi, and I changed the updater script to say, "degaswifi", for the device. and I changed the build prop, to be the same cpu, exc... as the tab 4. I used Degaswifi Docker 6 boot.img and recovery folder, and some other important stuff in the system folder. What is the error are you getting?
secretwolf98 said:
I made it on ES File Explorer, on my Nook, it took me an hour... I had ported it from Acclaim RC5 and Docker 6 Degaswifi, and I changed the updater script to say, "degaswifi", for the device. and I changed the build prop, to be the same cpu, exc... as the tab 4. I used Degaswifi Docker 6 boot.img and recovery folder, and some other important stuff in the system folder. What is the error are you getting?
Click to expand...
Click to collapse
Even using other twrp I still can not install, use the recovery and the boot image I found 2 weeks ago, I even deleted the first line and it looked like it would install, but these errors appeared
jimmy999x said:
Even using other twrp I still can not install, use the recovery and the boot image I found 2 weeks ago, I even deleted the first line and it looked like it would install, but these errors appeared
Click to expand...
Click to collapse
Can I see what you had edited?
Only the first line of the updater inside google folder
jimmy999x said:
Only the first line of the updater inside google folder
Click to expand...
Click to collapse
What is in the first line? The new updated one, that you had did?
secretwolf98 said:
What is in the first line? The new updated one, that you had did?
Click to expand...
Click to collapse
this
jimmy999x said:
this
Click to expand...
Click to collapse
strange
I'll look into it later
jimmy999x said:
this
Click to expand...
Click to collapse
Question, after you flashed this rom, did the Splash Screen disappeared on the Samsung?
Because the both versions that I had made, broke my Samsung Splash Screen.
secretwolf98 said:
Question, after you flashed this rom, did the Splash Screen disappeared on the Samsung?
Because the both versions that I had made, broke my Samsung Splash Screen.
Click to expand...
Click to collapse
If, in fact, they stop seeing the logos of samsung when turning on and when entering the download mode, the only way to correct that is to install the official firmware
jimmy999x said:
If, in fact, they stop seeing the logos of samsung when turning on and when entering the download mode, the only way to correct that is to install the official firmware
Click to expand...
Click to collapse
so it did for you, when you flashed official PA1 firmware threw odin? did the screen that broke say, "Samsung Galaxy Tab 4 7.0 SM-T230NU Powered By Android"?
Interested to get this rom running smooth on our tabs
Hello!
Please forgive me as it's been a long time since I made/posted a stock based ROM as I have been mainly doing security research and dealing more with source code last few years.
Most seasoned Samsung users on here probably already know me and work that I have done so I won't waste time posting any "about me" stuff.
DISCLAIMER:
This ROM is still WIP (although fully functional) and based on Android R Beta 1ZTJA for G986U/U1/W. An unlocked BL is required to flash this ROM!
Features:
- Based on Stock R Beta 3 Build aka 1ZTJA.
- This is a full ODIN flashable tar (got tired of messing with update zips.)
- Disabled vbmeta
- Pretty heavily debloated
- Deknoxed
- Removed pesky recovery-from-boot.p which could cause boot loops.
- Currently only has SPR csc mods (will mod others in next build)
*Native call recording
*App Lock (forgot to push the app though so will fix in next build)
*Few others.. will post more specifics and give creds since I used the csc mod for exynos as a basis..
- Probably forgetting something but thhis is an initial build so will add more as time goes..
Instructions:
Note: The zip contains an instructions.txt that is more detailed.
Note 2: Zip contains the full firmware tar file which includes everything to be fully updated/on ztja. This means all bl files, modem, boot, recovery, super etc. so you can start from and build. Zip also contains files and instructions on how to obtain root.
- Backup your data if you must since this will wipe device!
- Put phone in dl mode and extract zip to pc somewhere.
- Open ODIN (INCLUDED IN ZIP) and in AP slot navigate to SamPWND.R3.v1-G986U1.tar and flash it.
- Device will reboot into stock ZTJA recovery where you will wipe data and reboot.
- Set up device and win?
Root Steps (optional):
Note: Since theres no sources for R yet theres no custom recovery. Also, Q based recovery will not work on R bootloaders as well as R there is no more /sbin so root needs to be flashed at this time.
- After you have flashed rom and everything is set up reboot back into DL mode.
- Open included ODIN and in AP slot navigate to the 1BTIF_BL_Files_and_LOS_Recovery.tar. Make sure auto reboot is NOT selected. Flash it.
- Once thats flashed hold vol down and power until screen turns off then immediately hold vol up and power until LOS recovery loads.
- However you want to flash magisk (I included Magisk.v21.0.zip) flash it.
* I do adb push magisk.zip /... Then select Install Update then install from root and select magisk zip...
- Reboot back into DL mode.
- In ODIn, select AP slot then navigate to 1ZTJA_BL_Files_and_1ZTJA_Stock_Recovery.tar and flash it.
- Device will boot back into ROM and you will now be rooted!
***TWRP RECOVERY***
- Download listed below
- I suggest you follow all the steps above and make sure it's up and running before installing TWRP.
- Basically extract the .tar from the .gz archive and flash in ODIN!
- adb works
- file manager and other tools work
- If follow above steps first as recommended, data will be decrypted.
- mounts work
- flashing works
- backup/restore works
- no issues found so far?
Steps are really quite simple if you have ever used ODIN.
It took a bit to put this together since all we have are update zips so I had to do a bit of trickery as well as had to build some binaries/tools to manually patch from 1BTIF to 1ZTJ3 to 1ZTJA to be able to have all the firmware images.
I will create a Telegram ROM support group soon where you can ask all the questions you want there (I am not at liberty to discuss unlocking bootloader on XDA so questions about this on here will either be ignored or will say I cant discuss. More info as to why will be posted in the support group or you can read the imcluded instructions.txt wink.wink).
ENJOY!
Shout Outs:
@topjohnwu for Magisk of course
@jesec for LOS Recovery
@afaneh92 base TWRP
@Mentalmuso for direction on how to get TWRP to work on R!
More shout outs coming soon!
SamPWND ROM Support and Other Support Telegram Group CLICK HERE
Downloads will be in post 2.
SamPWND.R3.v1-G986U1.tar
G986U/U1 1ZTJA TWRP Recovery
SamPWND ROM Support and Other Support Telegram Group CLICK HERE
CHANGELOG and Other Updates:
10/31/2020 - Added Telegram ROM Support group link to OP and second post as well as cleaned posts up a bit
10/19/2020 - Initial Upload/Post Creation
elliwigy said:
SamPWND.R3.v1-G986U1.tar
https://drive.google.com/file/d/1cm5H-GEEENQAhK0DnKGMjjZWnyONVXCm/view?usp=drivesdk
Click to expand...
Click to collapse
Nice, I'm going to give this a try in a little while.
Misterxtc said:
Nice, I'm going to give this a try in a little while.
Click to expand...
Click to collapse
feel free to use it as a base to work ur rom magic lol! u kno how my roms are.. bare bones lol
elliwigy said:
feel free to use it as a base to work ur rom magic lol! u kno how my roms are.. bare bones lol
Click to expand...
Click to collapse
Thanks, that will be a big help getting me back into building roms again. I haven't had the time at all lately except for some minor phone stuff plus I'm waiting for computer parts to come in and put together a 10th gen Intel system. Then I can get started again.
I can flash this on g9860 device?Great work!
Verstuurd vanaf mijn SM-G9860 met Tapatalk
[email protected] said:
I can flash this on g9860 device?Great work!
Verstuurd vanaf mijn SM-G9860 met Tapatalk
Click to expand...
Click to collapse
dunno.. i wouldnt try it tho.. not sure how g986u bl files will work on a g9860.. might hard brick
Great work. Good to have more choices
so this will work on G988U too?
Smartphones13 said:
so this will work on G988U too?
Click to expand...
Click to collapse
no
it clearly states its for G986U/U1/W if anyone tries it or flashes it to any other device then dont complain if it doesnt work or bricks phone
That being said, how do we get this going for the 988U1? I have root working for R on the 988U1. Although attempting to boot into stock recovery on ZTJA sends it into a boot loop still working on that.
Zavon said:
That being said, how do we get this going for the 988U1? I have root working for R on the 988U1. Although attempting to boot into stock recovery on ZTJA sends it into a boot loop still working on that.
Click to expand...
Click to collapse
i have toake rom for g988u/u1..
and thats bcuz it needs to pull recovery from boot which it xan only do on stock boot.img
Just flashed this last night, seems to be running beautifully, no issues so far, battery is looking good. Removed a dozen more useless apps, root is working great.
Running on a G986W with a Canadian Sim, everything seems to be working fine with my carrier (WiFi calling, LTE+...)
Thanks brother! Keep up the good work
elliwigy said:
no
it clearly states its for G986U/U1/W if anyone tries it or flashes it to any other device then dont complain if it doesnt work or bricks phone
Click to expand...
Click to collapse
I have sm-G986U1 American version will it work or na?
Franzferdinan51 said:
I have sm-G986U1 American version will it work or na?
Click to expand...
Click to collapse
is ur bl unlocked? if not then no.. if it is then yes
Now that the FE has TWRP, any idea if these will work on that?
elliwigy said:
is ur bl unlocked? if not then no.. if it is then yes
Click to expand...
Click to collapse
How do you unlock the BL for the US Variant SM-G981x (S20 5G), is it possible
Superguy said:
Now that the FE has TWRP, any idea if these will work on that?
Click to expand...
Click to collapse
as i stated already a few times the answer is no.. this is for g986u/u1. the rom has g986u/u1 bootloaders and everything.. its not a twrp flashable zip.. if u try and hard brick thats on you.
illiterateBuffoon said:
How do you unlock the BL for the US Variant SM-G981x (S20 5G), is it possible
Click to expand...
Click to collapse
its not allowed to b posted on xda since its a paid service.. if u look around ull be able to find ur way