Related
im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated
bjf189 said:
im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated
Click to expand...
Click to collapse
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5
Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)
ShapesBlue said:
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5
Click to expand...
Click to collapse
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5
ShapesBlue said:
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Its cool. Good to see safestrap works on the prepaid version also
Sent from my Nexus 5
I'm not sure what a bash terminal is unless it's the same thing as the terminal emulator. I tried using that rom that's called paulpizz or something like that. I used some other rom to. The paulpizz one always failed to install even after downloading it a third time. The other one i can't remember the name but it installed but wouldn't start at all. It would just go black and bootloop and goes into stock recovery for some reason. I came across the nf5 module when i found that paulpizz rom on the goo server they hosted it on. So i got the module and i figured if i were to flash the module over the i535 rom that it would fix the wifi an data problem but never got an answer because it always failed to start up properly and would just bootloop into stock recovery. Ugh Verizon is making things so difficult with modding lol. As of now I'm just using xposed to get at least some theming in and tweaks. I couldn't get any deodex program to work. Whenever i used the deodex files and pushed them to the system of apps and framework, it would restart and just stick on the Verizon logo. So i had to flash the firmware to fix the problem.
When i was on 4.3 with this phone safestrap worked and i got the wifi and data sim error. Now that i got it replaced I'm running the kernel of July 22 2014. Everyone was saying I'm out of luck but i came across kingroot and got the most recent version and it worked. I have root. Installed safestrap for 4.4 and it runs fine but can't get any custom roms to boot. I only managed to find one 4.4 touchwiz rom unfortunately
OpenSourcererSweg said:
Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)
Click to expand...
Click to collapse
OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something
bjf189 said:
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.
OpenSourcererSweg said:
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.
Click to expand...
Click to collapse
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader
bjf189 said:
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader
Click to expand...
Click to collapse
Safestrap 3.75 had support for AOSP roms (wifi/data didn't work for them either) and 4.0 dropped support for that (there is currently no point). Read the thread for more info http://forum.xda-developers.com/showthread.php?t=2797314
Ok i wasn't using safestrap 4.0. I had 3.75 B05 which i thought was the latest version they had. I'm updated to 4.0 now and about to test the modules on the superlite rom
Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't
bjf189 said:
Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't
Click to expand...
Click to collapse
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that
OpenSourcererSweg said:
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that
Click to expand...
Click to collapse
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?
bjf189 said:
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?
Click to expand...
Click to collapse
I'm running the stock prepaid rom, not superlightrom, sorry if there's any confusion there.
When I tried out superlightrom (quite some time ago) it appeared to work fine (excluding wifi/data and nagging about no SIM card being inserted, nothing like what you're describing) and I went back to stock.
Oh ok. Well it seems that the prepaid version or the s3 in general is dead. That's unfortunate
Hi folks,
just posting this writeup thinking maybe it might be of help to some people.
Started with a clean S6 Edge straight from Samsung repair for broken screen. Factory wipe, KNOX reset. It had the PD2 update. Tried using Skipsoft's Toolkit and ponied up a donation to get the Pro version with the S6 Edge 6.0.1 update, but it didn't work: it got stuck at the "SEANDROID NOT ENFORCING" screen after flashing TWRP 3.0.2. I know there are issues with 3.0.2, but it's what's optioned in Toolkit now.
Flashing TWRP 2.8.7.0 results in normal boot, but I could not enter recovery mode for some reason. 3.0.0-0 didn't work, either.
What I ended up doing is forcing phone into download mode (Power+Volume Down+Home), ODINing TWRP 3.0.2-1. This resulted in a bootloop (somewhat expected). But I could get into recovery easily. From recovery, I flashed Renegade's PD2-Aroma V3.0 Full ROM via ADB sideload. After a very long first boot, everything works 100%! Root, SuperSU, etc., all taken care of. Hotspot works.
Notes and tips:
- While I didn't use Skipsoft's Toolkit in the end, it's still worth supporting. Might work smoothly using 3.0.2-1 instead of 3.0.2.0, but I'm comfortable with adb/fastboot/etc. so just ended up using that. If you don't already have Android SDK and tools/platform-tools, Skipsoft conveniently includes those commands in its directory under C:\Unified_Android_Toolkit (they're named adb-toolkit and fastboot-toolkit. You can copy and rename them as "adb" and "fastboot" for convenience).
- Make sure you get the right TWRP 3.0.2-1 device version. You want to use twrp-3.0.2-1-zeroltespr.tar.md5 for Sprint S6 Edge. Remove the .md5 part and set it to use the .tar extension (stupid Windows asks you to confirm file extension type change).
- In TWRP you can either push your custom ROM or sideload it. To push a file, move the custom ROM into the same directory you've got adb/fastboot for convenience. Open a terminal window in that directory, and either "adb push customromfilenamehere.zip /sdcard/" or in TWRP, click Advanced/ADB Sideload, and enter "adb sideload customromfilenamehere.zip".
- If you're sideloading it, it's gonna take a while, and will start flashing even while the transfer percentage is creeping up. Example: at around 9%, it started AROMA, around 14%, it went through some of the installation options. It was done flashing everything and ready for reboot even though the terminal window said only 76% was transferred. That's ok. Click "finish" in AROMA on phone, reboot. Unplug phone. Wait a long time for first boot (this took around 20 minutes for me). ENJOY.
Remember: all is not lost as long as you can get into download mode! Power-Volume Down-Home until you get to screen prompting to get to download mode. Volume up to select that mode. You can ODIN from here.
Additionally: if you find yourself for whatever reason stuck at the initial S6 Edge boot screen with "SEANDROID NOT ENFORCING," you might be in some kinda of boot limbo. I was able to issue some adb commands here, even with recovery was borked and the phone didn't boot all the way. Doing an "adb reboot-bootloader" would let me do a complete boot to ROM while I was trying to get the different TWRP versions working (until 3.0.2-1).
Hope this helps someone.
tl;dr: For PD2/6.0.1 Sprint S6 Edge, manual flash TWRP 3.0.2-1. Push custom ROM through Recovery. Reboot, wait a long time. Success!
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN latest TWRP 3.0.2.1 - HERE.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Alpine- said:
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN Ram's TWRP 3.0.2 - HERE I'm assuming the other guy's 3.0.2 works fine too, I am not sure why you hung and had to revert to a 2.x TWRP build.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Click to expand...
Click to collapse
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
baknblack said:
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
Click to expand...
Click to collapse
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Alpine- said:
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Click to expand...
Click to collapse
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
baknblack said:
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
Click to expand...
Click to collapse
Edge is better imo, certainly looks better. All you need is Renegade rom anyway. May be a few more roms in active dev for s6 but nothing better per se. Renegade rom dev is alive and well.
Would these root methods trip knox?
chen69chuck said:
Would these root methods trip knox?
Click to expand...
Click to collapse
Yes
Thanks.
Working for g920v 6.0.1?
freaking thank you been struggling with twrp on and off for two days trying to bring this phone back from the dead! YOU the man
Hey guys, first time on this forum because I've run out of options otherwise. So last night i decided to finally root my phone after reading about it a lot. The root it self went just fine and it was working great. I then tried to download xposed using TWRP. However, that put my phone into a bootloop. It keeps restarted after it comes to the Samsung logo. I did some research and people said to simple put it back to the stock firmware so i downloaded some ( had trouble downloading because sammobile wouldn't work for me) However, now every time I try to flash it back to the stock firmware using odin it says failed and comes up with an error on the phone saying SW REV CHECK FAIL DEVICE 3, BINARY 1. The phone is a SM-G920W8. Any suggestions cause right now I have a $700 paper weight and no back up phone. I'm kinda freaking out haha.
Thanks for the help. I can send screen shots if you guys need them.
same problem.is there a way to install xposed framework without these annoying problems?
how to install the custom recovery and xposed properly?
Yeah, use the correct Xposed for S6.
There's an uninstall tool for the Xposed you've already installed (look in OP for Xposed you installed), that should have been your first step after bootloop. Try now, see if it will uninstall.
There's a Windows tool called SamFirm, or an Android app + website called Updato, use those to download stock ROMs if you still need to.
Then search for Wanam Xposed s6, and use that version.
Sent from my SM-G920W8 using Tapatalk
The reason I am posting here and not in the Rom section is because I am not a developer. I am an Android enthusiast who, with the help of a few awesome tools, some reading and some help from a couple of great devs, I was able to build a custom rom from a stock first release. I have been running it now for a couple of weeks and battery life is awesome. Just enough Samsung apks left in too call it a stock rom but not so many to cause it to lag. I thought that since it was running so nice, I would share it with you. So, without further ado, this is what I came up with.
"Ghost Project v1.0 6.0.1 t350" This is only for the t350.
With the help of a few awesome people, that provided me with the direction and resources links, I was able to take a stock firmware.tar (T350XXU1BPE3) and make a TWRP flashable zip. This is what I came up with:
I am not a developer..... Let me make this clear.. Lol.. I am not a developer. But I did use an awesome tool that allowed me to make this rom " superr kitchen" .... http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296/page26
So first and foremost a big thanks goes out to this developer for this awesome tool.
I would also like to give props to Samsung and Sammobile.com for the firmware.
The kernel is from http://forum.xda-developers.com/galaxy-tab-a/development/kernel-galaxy-tab-sm-t555-5-8-2016-t3433560 and is a stock, permissive kernel. By "[ashyx, http://forum.xda-developers.com/member.php?u=4899305 Recognized Contributor]" another awesome dev. This is a stock kernel in every respect with SElinux set to permissive.
I would also like to thank and give props to"{FankieT} of {R3Ds themes and Development}" https://plus.google.com/communities/102477541363210451018 for all of his help and guidance. He was who got me started into Linux through Ubuntu and spent many hours teaching this old dog the ways of Android coding. Just a pinch of coding on my part..lol
Glockman4519
Owner
Hayes Tech Rom Reviews
Dec 09, 2016
Use at your own risk. ********You have been warned..*********
Features:
1. Rooted with chainfires SuperSu in system, not systemless (I hate systemless root)
2. Busybox installed
3. Debloated. I didn't go too far (for reliability) but will work on getting more Samsung system apps removed.
4. Zip aligned
5. Deodexed (I may make one that is odexed later on)
6. Removed Kies
7. Custom kernel
Stock but SElinux permissive (see note on developer in Intro)
8. Some script changes but nothing to change system behavior
9. Added ES File explorer v3.2.5.
This app will try to update unless Play Store settings are changed to not auto update. But if you like the latest than update it.
10. Added Nova Launcher v3.3
I don't like the newer Material Designed updated builds. This will also try to update unless settings in Play Store are set to not auto update.
11. Latest Google Keyboard.
I just don't care for Samsung's and like the theming features of Google's latest keyboard. Samsung keyboard is still in though if you prefer to use it instead.
12. According to the toolkit, Knox was removed. Although I still see it in the settings tab under Settings/about phone. I don't think this can be removed safely however all updates (annoying notifications stating that there is an update available) have been removed so there shouldn't be any chance of accidentally updating to the latest firmware, if any is released. If you want an update than you will have to download any updates ( if the are any) from Samsung and use Odin to install it.
Kernel:
Here is a link to the kernel developer's thread, who is another awesome dev, who's kernel is the heart of this rom.
http://forum.xda-developers.com/gal...el-galaxy-tab-sm-t555-5-8-2016-t3433560/page8
By "[ashyx, Recognized Contributor]" This is a stock kernel in every reguard with SElinux set to permissive.
A few other small things here and there but mostly stock.
-This is a flashable zip using TWRP recovery and I highly recommend the 2.8.7.0 build as apposed to the 3.0.2.0 build that is also on XDA in this forum.
Link to recovery built by "ashyx" an awesome dev...
http://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560/page13
-Since this is a stock rom build, gapps are included
#####Flashing instructions#######
###MUST BE ON MARSHMALLOW BUILD ****T350XXU1BPE3******####### so, if you are on a lollipop build (5.0.1) you need to update to 6.0.1 and have TWRP installed........
1. Make a backup onto your external SD card or on a PC using TWRP recovery. This is a very important step as things do go wrong. You have been warned.
2. Wipe. I recommend a clean install with all 4 major wipes done (system, Cache, Dalvik Cache and Data)
3. Flash "Ghost Project v1.0 6.0.1 t350" rom zip.
4. Wipe both Cache and Dalvik Cache
5. Reboot to system and profit.
*****The first boot will take a long time to boot. Put the device down and walk away until it boots (could take up to 15 minutes ) but most likely around 12 to 15 minutes. That is because all files are deodexed.
After it boots up Go ahead and set up the device the way you like it and enjoy.
I also have a Google Plus Communitee Called "Hayes Tech Rom Reviews" where you can go to watch reviews/overviews of custom roms for many devices that I own. I have about 20 to 25 devices now and try to do reviews on all the diferent roms out for them. I also have awesome links like the 3Minit battery mod by{made by "gharrington"} for the Nexus 6 and many more things. Please feel free to stop by.
https://plus.google.com/communities/109262972011341635244
**LAST BUT NOT LEAST****USE AT YOUR OWN RISK**
Warning, I am not a developer. All I am doing is sharing my personal build. I am not nor will I be responsible for anyone ruining your device. Thermonuclear war or Loss of job from device not working is your responsibility. And above all this zip will void your warranty.
I can't think of anything else..lol.. This is the first time for me so I'm not too sure about proper post etiquette for Custom Roms. I am not posting in the roms section because I am not a developer. I do not have the skills those great people have. We just do not have any stock based roms yet and mine is running great so I am sharing with you all. I am going to try to add more custom features and may even add a pure stock rom for total stock experience, let me know... Enjoy.
A video review of my rom... Go here if you would like to see it
https://youtu.be/dVnx709LO7Y
I built another rom for those that want the stock experience but still want it rooted and Knox removed. It is also Zip Aligned and is running the same permissive kernel for Xposed Mods to work better with it.
Download Rom (AFH)
Stock/Rooted/Deodexed/Debloated/Knox Removed/Zip Aligned/Permissive Kernel/ES File Explorer 3.2.5, Nova Launcher 3.3, Latest Google Keyboard
https://www.androidfilehost.com/?fid=673368273298916139
Stock/Rooted/Deodexed/Knox Removed/Zip Aligned/Permissive Kernel/No Extra Apps Added (Pure Samsung)
https://www.androidfilehost.com/?fid=385035244224406713
Xposed Installer Zips (For Samsung) By wanam, Recognized Contributor. You can find his thread here http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Screens:
If you want to run the wallpapers that I am, I am working on getting them into the default wallpaper but until then you can get it here
Just in case again. Lol
Sent from my Nexus 6 using XDA Premium HD app
Merry Christmas Everyone.
the link to the rom doesnt work
ratchetrizzo said:
the link to the rom doesnt work
Click to expand...
Click to collapse
I am checking now to see whats up. Here is my original Google drive link.
https://drive.google.com/file/d/0ByTpk6hgHRa5VU4wSkVrcy1jakU/view?usp=drivesdk
ratchetrizzo said:
the link to the rom doesnt work
Click to expand...
Click to collapse
AFH link is now fixed
https://www.androidfilehost.com/?fid=673368273298916139
glockman4519 said:
AFH link is now fixed
https://www.androidfilehost.com/?fid=673368273298916139
Click to expand...
Click to collapse
Does xposed work on this rom? If so, which version?
thanks!
ratchetrizzo said:
Does xposed work on this rom? If so, which version?
thanks!
Click to expand...
Click to collapse
Yes it does. I used the kernel that is in this forum to build it with and it is a permissive kernel. The version is v87.1-sdk23-arm made by Wanam specifically for Samsung. I am running it now asking with gravitybox and a few other mods.
Just remember that since it is deodexed it will take a long, long time to boot. I timed it on my last 2 flashes at around 13 minutes both times. My battery life is outstanding.
glockman4519 said:
Yes it does. I used the kernel that is in this forum to build it with and it is a permissive kernel. The version is v87.1-sdk23-arm made by Wanam specifically for Samsung. I am running it now asking with gravitybox and a few other mods.
Just remember that since it is deodexed it will take a long, long time to boot. I timed it on my last 2 flashes at around 13 minutes both times. My battery life is outstanding.
Click to expand...
Click to collapse
do you have a link for that?
ratchetrizzo said:
do you have a link for that?
Click to expand...
Click to collapse
Yes I do but only to my Google Drive. I will try to link them to the OP later but to then here you go.
https://drive.google.com/folderview?id=0ByTpk6hgHRa5X3g5VnBVam9OaDQ
glockman4519 said:
Yes I do but only to my Google Drive. I will try to link them to the OP later but to then here you go.
https://drive.google.com/folderview?id=0ByTpk6hgHRa5X3g5VnBVam9OaDQ
Click to expand...
Click to collapse
Just installed this, flashed it and xposed at the same time, took 7 minutes to boot the first time.
Updating, reinstalling and debloating things I don't need now.
Seems faster than the debloated 5.02 rom I was on.
Will keep you posted after everything is done
glockman4519 said:
Yes I do but only to my Google Drive. I will try to link them to the OP later but to then here you go.
https://drive.google.com/folderview?id=0ByTpk6hgHRa5X3g5VnBVam9OaDQ
Click to expand...
Click to collapse
everything works great.
Quick question, what did you use to change your clock and signal icon colors?
Wanam isn't changing the clock color or left hand icons for me.
ratchetrizzo said:
everything works great.
Quick question, what did you use to change your clock and signal icon colors?
Wanam isn't changing the clock color or left hand icons for me.
Click to expand...
Click to collapse
Sorry, I am on night shift and was getting some sleep..lol.. I used Gravitybox MM. It has almost everything in it that I need to make a stock rom custom..lol..
ratchetrizzo said:
Just installed this, flashed it and xposed at the same time, took 7 minutes to boot the first time.
Updating, reinstalling and debloating things I don't need now.
Seems faster than the debloated 5.02 rom I was on.
Will keep you posted after everything is done
Click to expand...
Click to collapse
Thats great... It takesk me 13 minutes on both ( plus or minus)... Every device will respond differently though so the boot times will vary. Thats Awesome.
glockman4519 said:
Thats great... It takesk me 13 minutes on both ( plus or minus)... Every device will respond differently though so the boot times will vary. Thats Awesome.
Click to expand...
Click to collapse
I screwed something up with a xposed module (I guess, everything was fine until I installed a power menu module and told it to reboot into recovery). No matter what I did, It would only boot into twrp. Even if I powered off and plugged the charger in, instantly twrp. Reflashing the rom did absolutely nothing, I had to odin stock then reflash this rom.
Ah well, live and learn with xposed.. I know not to install that power module lol
ratchetrizzo said:
I screwed something up with a xposed module (I guess, everything was fine until I installed a power menu module and told it to reboot into recovery). No matter what I did, It would only boot into twrp. Even if I powered off and plugged the charger in, instantly twrp. Reflashing the rom did absolutely nothing, I had to odin stock then reflash this rom.
Ah well, live and learn with xposed.. I know not to install that power module lol
Click to expand...
Click to collapse
I hear ya. Xposed is something I use only if I know the module. I never use test version (anymore .. lol) I did the same thing you did a whike back with some other mod.
The only mods I use are Gravitybox, Notify Clean, Xuimod, and sometimes either HK theme engine out Xtheme engine. Gravitybox has most all mods that I need built right in it including an advanced powed menus settings.
Also, when you were in that issue, did you try using the Xposed uninstall zip? That may have got you fixed up too.
glockman4519 said:
I hear ya. Xposed is something I use only if I know the module. I never use test version (anymore .. lol) I did the same thing you did a whike back with some other mod.
The only mods I use are Gravitybox, Notify Clean, Xuimod, and sometimes either HK theme engine out Xtheme engine. Gravitybox has most all mods that I need built right in it including an advanced powed menus settings.
Also, when you were in that issue, did you try using the Xposed uninstall zip? That may have got you fixed up too.
Click to expand...
Click to collapse
Well, even with gravitybox's reboot menu, if i have it boot me into recovery it sets the recoverybit and makes me reflash stock firmware.
so DON'T pick recovery from your reboot menu
ratchetrizzo said:
Well, even with gravitybox's reboot menu, if i have it boot me into recovery it sets the recoverybit and makes me reflash stock firmware.
so DON'T pick recovery from your reboot menu
Click to expand...
Click to collapse
I use it all the time. I just rebooted into recovery just before I responded here. Anyways there are also app on the p
Play Store that will reboot you to recovery too, like "Quickboot". I don't understand why this is giving you issues. What version of recovery are you on? There are problems with the 3.0.2.0. I used the other one on this forum 2.7.8.0.
glockman4519 said:
I use it all the time. I just rebooted into recovery just before I responded here. Anyways there are also app on the p
Play Store that will reboot you to recovery too, like "Quickboot". I don't understand why this is giving you issues. What version of recovery are you on? There are problems with the 3.0.2.0. I used the other one on this forum 2.7.8.0.
Click to expand...
Click to collapse
I'll go down to 2.7.8.0 and see how that works for me
I modified some files for @LeeDroid rom for sprint support prior to sprints nougat ota and posted the download link in his thread but I'm not sure how often other sprint users check his thread being that sprint support wasn't available. If interested in testing to verify before the edits get fully implemented into the rom build please let me know if there are any issues.
***Thread has been updated for Sprint Oreo Support. This thread is for sprint users to report bugs with the sprint specific components of the ROM for me to troubleshoot to lessen the work on Lee since he isn't on the Sprint network. Also with new Sprint updates I will post test zips here because devices act differently and I want to be sure that the fixes/tests I build work for everyone.***
DISCLAIMER
I, nor any of the developers involved, are not liable for any damages that may occur to your device as a result of flashing. Flash at your own risk. I have this version running currently and have had no issues.
Big thanks to @LeeDroid for putting up with my pestering for sprint support and for challenging me to get it done
Thanks to @Captain_Throwback for file location guidance and for the use of his apktool when mine was being fussy, and for the use of his Sprint APNs.
Download Test 1 - Failed attempt, thanks to all who tested and let me know that it was broken. Don't use this one
https://www.androidfilehost.com/?fid=529152257862696764
MD5 6495ccb05ec3886306aad7dbc7088f28
Test 2 was never publicly released. I had multiple test 2's
Download Test 3 - Fresh out the oven. Clean flashed (format data in twrp) and booted, restored most of my settings over mobile data without having to edit any apns, didn't have statusbar clock for a little bit which was weird but it showed up, maybe it was taking a nap . Give it a try and let me know.
https://www.androidfilehost.com/?fid=673368273298925530
MD5 0a61e3fbdad51e4fa3d0ada511606f72
Install procedure
1. Clean start in twrp (full wipe)
2. Flash sprint test zip
3. In aroma select Sprint
This is where I edited the necessary files for sprint data to connect
4. Make selections in aroma for options as you normally would
5. Let install finish
6. Reboot
6.5 Don't worry about the boot animation, personally I prefer the stock Android so that's what it is
7. Wait
8. Wait
9. Profit? Hopefully
gstanke said:
I modified some files for @LeeDroid rom for sprint support prior to sprints nougat ota and posted the download link in his thread but I'm not sure how often other sprint users check his thread being that sprint support wasn't available. If interested in testing to verify before the edits get fully implemented into the rom build please let me know if there are any issues.
<c> <b> DISCLAIMER </b> </c>
I, not any of the developers involved, are not liable for any damages that may occur to your device as a result of flashing. Flash at your own risk. I have this version running currently and have had no issues.
Big thanks to @LeeDroid for putting up with my pestering for sprint support and for challenging me to get it done
Thanks to @Captain_Throwback for file location guidance and for the use of his apktool when mine was being fussy
Click to expand...
Click to collapse
Sprint user here. Will test soon as I get a chance.. what TWRP version is necessary? Does it matter what firmware I'm currently on? Thanks!
Lurien said:
Sprint user here. Will test soon as I get a chance.. what TWRP version is necessary? Does it matter what firmware I'm currently on? Thanks!
Click to expand...
Click to collapse
I haven't updated firmware to most recent yet since it was a security update I didn't feel the need and currently my twrp version is 3.0.2-6 I believe
gstanke said:
I haven't updated firmware to most recent yet since it was a security update I didn't feel the need and currently my twrp version is 3.0.2-6 I believe
Click to expand...
Click to collapse
Great! Thanks again..
gstanke said:
I haven't updated firmware to most recent yet since it was a security update I didn't feel the need and currently my twrp version is 3.0.2-6 I believe
Click to expand...
Click to collapse
Sprint here as well, I will test too, thanks!
GROOVYJOSHCLARK said:
Sprint here as well, I will test too, thanks!
Click to expand...
Click to collapse
Should flash fine and provide a working data connection
gstanke said:
Install procedure
1. Clean start in twrp (full wipe)
2. Flash sprint test zip
3. In aroma select <b> US UNLOCKED </b>
This is where I edited the necessary files for sprint data to connect
4. Make selections in aroma for options as you normally would
5. Let install finish
6. Reboot
6.5 Don't worry about the boot animation, personally I prefer the stock Android so that's what it is
7. Wait
8. Wait
9. Profit? Hopefully
Click to expand...
Click to collapse
dude!!! awesome!! ive been waiting and wishing ice or leedroid would support sprint with their N builds! trying this now
deakelem said:
dude!!! awesome!! ive been waiting and wishing ice or leedroid would support sprint with their N builds! trying this now
Click to expand...
Click to collapse
Any update? Hopefully everything is good to go
Sprint User Too
I'm a sprint user as well and have been waiting for something like this (impatient waiting for sprint upgrade) will test and post results.
JhoonB51 said:
I'm a sprint user as well and have been waiting for something like this (impatient waiting for sprint upgrade) will test and post results.
Click to expand...
Click to collapse
I finished the edits last night and so far have had no issues but since Lee doesn't have a sprint device for testing I figured this was the best way, if everything is good the edits will be merged into the main rom
I'll try it later but the download speed is poop. Says I have 5 days left. I'll try to download later.
gstanke said:
Any update? Hopefully everything is good to go
Click to expand...
Click to collapse
I flashed like the directions said but the phone sat at the "android" boot logo for at least 30 minutes before i restored a backup. I tried flashing a second time too with certain options not selected (such as using the stock kernel this time) and the same thing happened. should i wait longer?
deakelem said:
I flashed like the directions said but the phone sat at the "android" boot logo for at least 30 minutes before i restored a backup. I tried flashing a second time too with certain options not selected (such as using the stock kernel this time) and the same thing happened. should i wait longer?
Click to expand...
Click to collapse
I did not have that issue.
Try flashing, letting sit at Android screen again if it doesn't boot try dirty flashing over top
I had formatted data through twrp and run unencrypted
Also what selections did you choose? Mmfirmware? Root method?
gstanke said:
I did not have that issue.
Try flashing, letting sit at Android screen again if it doesn't boot try dirty flashing over top
I had formatted data through twrp and run unencrypted
Also what selections did you choose? Mmfirmware? Root method?
Click to expand...
Click to collapse
hmmm.. so i selected the MM firmware options but the only thing i did different from you was I selected encryption each time. I will try again while setting encryption to disabled.
deakelem said:
hmmm.. so i selected the MM firmware options but the only thing i did different from you was I selected encryption each time. I will try again while setting encryption to disabled.
Click to expand...
Click to collapse
Format data in twrp beforehand to be able to run unencrypted, which version of twrp are you using
gstanke said:
Format data in twrp beforehand to be able to run unencrypted, which version of twrp are you using
Click to expand...
Click to collapse
yup yup, did that already. just flashed and now its booting.
Update: just an update, it is still booting and is at the android logo, 15 mins so far. I will continue to wait another 30 mins or so
deakelem said:
yup yup, did that already. just flashed and now its booting.
Update: just an update, it is still booting and is at the android logo, 15 mins so far. I will continue to wait another 30 mins or so
Click to expand...
Click to collapse
same results after 30 mins. I even tried not selecting any options other than us unlocked and the stock kernel, and disabled encryption, still had the same result. It sits at the android logo during boot up for a while and will reboot once and sit there again. Anyone else seeing any problems like this?
deakelem said:
yup yup, did that already. just flashed and now its booting.
Update: just an update, it is still booting and is at the android logo, 15 mins so far. I will continue to wait another 30 mins or so
Click to expand...
Click to collapse
I am having the same results, stayed at android logo for well over an hour and would go no further. I chose mm firmware, run unencrypted (been unencrypted long time) twrp 3.0.3....went back to 2.71