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?
Related
Sprint Moto X [XT1056] Stock ROMS
By using any of these you agree that I am not responsible for ANYTHING that can or may happen to your phone
Click to expand...
Click to collapse
Like this guy said:
iKrYpToNiTe said:
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please!
Click to expand...
Click to collapse
-----------------------------------------------------------------
KIT KAT 4.4.4
System Version: 212.44.28
Software update 08/2014
Code:
[B]DETAILED ENHANCEMENTS:[/B]
Android™ 4.4.4, KitKat® - Android 4.4.4, KitKat, is the latest release of the Android platform. This release includes several stability, framework and security fixes in addition to accuracy improvements to the power profile.
Camera - Improved image quality - Improved camera image quality including better consistency of exposure, more realistic flash coloring, improved photos in low light conditions using front camera.
Camera - Pause video recording - Added the ability to pause video recording with a convenient pause/resume button on the viewfinder.
Updated Phone dialer - Updated Phone dialer with a new graphical layout and colors to improve consistency and usability.
Motorola Alert application - New Motorola Alert application sends periodic alerts with your location to your selected contacts. Now available for download from the Google Play Store.
ROM LINK
212.44.28
md5: d1fb4c2259855abf74dfadbad5ccdbc2
FIRMWARE LINK
LINK
-----------------------------------------------------------------
BIG thanks to:
iKrYpToNiTe
chad.goodman
NineInchNails
Rizal Lovins
ibanez7
motofirmware.center
JustCMH
HOT-SPOT UNLOCK:
iKrYpToNiTe said:
All you have to do is add net.tethering.noprovisioning=true to your build.prop file and then you can remove or freeze the entitlement check app if you want to. Sprint model requires ro.mot.tether_dun_required to change from 1 to 0.
For people who don't want to mess with modifying their build.prop file or use xposed. I made an app which requires Root, that will run a setprop command to bypass the check until you reboot. If you want it to last after a reboot you can select apply of boot to run the command after every reboot. This was tested and confirmed by cvhovey thanks to him for testing it for me, since I have free tethering. This is my first app so I hope you Enjoy it! I want to say thanks to jcase's slapmymoto and the developer of adaway, I used their github sources as references when I couldn't get something working. Also androidicons for the icon template, and Poliva for setpropex, and jduck for getting setpropex working on KitKat.
Download Links
v1.2 http://www.androidfilehost.com/?fid=23501681358557764(v1.2 is signed with a different key than v1.0/v1.1 so it will display a msg box telling you this just click okay)
Click to expand...
Click to collapse
RECOVERY LINKS
CWM Advanced Edition- PhilZ Touch
TWRP
SUPERUSER LINKS
SuperSU
CWM Superuser (Koush)
DID YOU MAKE AN EXPENSIVE BRICK?
[HOW-TO] Resurrecting A Bricked Moto X
FEW WAYS TO GET BACK TO STOCK
Easy Guide to Restore Stock Firmware on Moto X using RSD Lite
Moto X Toolkit v1.4.3 [Backup/Restore,Drivers,Return to stock,Root,Bootani]
Script FlashFirmware (simple and safe method to flash firmware)
Getting a moto x back to stock on mac os x
BAD BATTERY DRAIN LATELY? TRY THIS
hardware reset of the processor and terminates all running commands
LEAVING THIS HERE IN CASE I FORGET HOW TO TAKE A DUMP
Code:
[B]dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/System.img.ext4
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/Boot.img[/B]
Thanks for this! Thanks soo much for the hard work!
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
They are both up. md5's should be posted right, they were manually entered. I'm carving pumpkins with the boys, so........hopefully all is good. If not, let me know and I'll attack it when able to.
AbstractXart said:
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
Click to expand...
Click to collapse
pfft, and mine was what?
looks good gokart
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
gokart2 said:
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
Click to expand...
Click to collapse
nah, the last big script i did for people was teh first nexus toolkit, nowadays i hop around trying to help out unloved devices (hence teh name of the team i made Official Unloved Devices Hit Squad ). people needed this anyways, my stock rom was based on the pre-ota camera fix apparently. i had considered getting this phone on republic wireless so i wanted to scope out how development was coming, saw nothing was going on and figured id help out .
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Wha?! I never saw it Shabby. My bad, let me rephrase,
FINALLY! The second rom for the Sprint variant :').... I Love you! haha.
Hey guys, I just wanted to update and say it won't boot on the Verizon dev edition like the T-mobile rom will. It freezes for me on the Moto Earth boot animation. Noo! Well darn, I was wanting to try the sprint rom to see if I could get google wallet tap to pay working on my vzw dev phone since no one has figured out how to make tap to pay work on the non-sprint variants.
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
gokart2 said:
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
Click to expand...
Click to collapse
what command are you using to pack the boot.img?
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
shabbypenguin said:
what command are you using to pack the boot.img?
Click to expand...
Click to collapse
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
jimmypop13 said:
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
Click to expand...
Click to collapse
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
Click to expand...
Click to collapse
i take it then you arent packing the Device tree file to the boot.img.
http://pastebin.com/tSGxTmYq save this script, run it against stock boot.img. youll get a DTB.img, extract your boot.img, edit what you want in ramdisk or swap zimages. then use a modified mkbootimg to include the dtb file as part of it all
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
Click to expand...
Click to collapse
I got the sprint deodex rom booting on my vzw dev edition doing like you said. But sadly I found google wallet would not work. It just sat saying "finishing up a few things." So I guess unfortunately there is a hardware issue preventing wallet from working on the non-sprint variants. That sucks!!!
I don't understand why but I noticed between the t-mobile, verizon, and sprint roms that the signal bars are slightly different on every one. Sprint's seems to be stretched out a little more and have an extra bar or two. I hate all of them though because the grey has some funky white lines through it where the separations are instead of being solid grey. I don't know what was wrong with the stock android signal bars that none of the carriers wanted them
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
d4mi3n said:
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
Click to expand...
Click to collapse
Honestly have no clue about SS. I would have to say no. No sure what needs to be done for it to be SS flashable.
Added 4.4 links. Thank abiezer for letting me link to his deodex 4.4 build HERE!
I plan on adding the SPRINT specific firmwares, and more in due time.
after a long wait for the firmware to be released of the S4 running OH7 , it still has not been released. However i decided to make it myself and now we finally have it. I have tested it on my S4 that came with OH7 build originally. So here you go guys, Firmware containing OH7 running lollipop 5.0.1 with stock kernel 3.4 of mon Sep. 7 2015.
little guide to help you install the firmware if you need it.
you will find the firmware link below that i have uploaded and as for odin you can just google it. now im sure you can use other versions of odin but always safest to be up-to-date.
you will need: OH7 firmware file (Download link at the bottom), odin 3.10.7, WinRar and USB data cable
steps:
1. put phone into download mode by holding the home+vol up+power keys at the same time.
2. plug your phone into your PC (be sure drivers for the phone are installed correctly)
3. open up your handy tool of Odin
4. open up the firmware file you have downloaded in Winrar and extract it, you will then be given an MD5 File containing the firmware
5. click on "AP" in odin and browse for the file (odin might not respond after that but be patient, it will)
6. after the program responds, double check that F. Reset time and Auto Reboot are the ONLY ones ticked/checked
7.Go ahead and hit start and sit back for a few minutes and let odin do its thing
8. after all goes well and in the top box says "PASS!" then your phone will reboot and be good as new.
Just a heads up that this firmware is meant and made for the prepaid variant of the Verizon S4. I wouldnt recommend trying it on the postpaid S4 for the postpaid firmware has negative effects on the prepaid variant so id assume it have the same outcome on postpaid variant. Also im not responsible like anyone else out there if you brick your phone by not following the steps correctly or flashing it incorrectly in some way. Just a disclaimer that everyone puts out on here. hope this helps everyone. enjoy!
If the link becomes a broken link, let me know and i will update. i just need to move the file from time to time due to high data traffic
Link Update
https://mega.nz/#!Uk412ZwR!IT_c5Lq6hxbs_CbDVJZKIEv9pAMony8vdUgvvVq0zuE
now that i have released the stock firmware of OH7, i am trying to Deodex this also but keep getting failed start ups. i used LBD 2.5 to try an deodex and followed the guide but i hear start up sound not even a second and it stops and it dont show the verizon logo. i used flashfire to flash the deodexed files. so that being said, could some actual dev, deodex this firmware for i cannot? id really appreciate it and id share the deodexed firmware on the thread as well with of course giving proper credit to whomever can deodex it. thanks!
bjf189 said:
now that i have released the stock firmware of OH7, i am trying to Deodex this also but keep getting failed start ups. i used LBD 2.5 to try an deodex and followed the guide but i hear start up sound not even a second and it stops and it dont show the verizon logo. i used flashfire to flash the deodexed files. so that being said, could some actual dev, deodex this firmware for i cannot? id really appreciate it and id share the deodexed firmware on the thread as well with of course giving proper credit to whomever can deodex it. thanks!
Click to expand...
Click to collapse
This needs to be maken into a rom first as well before deodexed but i can do both actually if you don't know how to build a rom.
Sent from my SM-G935V using Tapatalk
Well if you could do both, I'd really appreciate it. I can't even begin to understand how to extract an md5. So confusing. Plus gotta get it to work with flash fire. I tried other roms with flashfire and kept getting system not responding. So I always had to Odin back to stock and on the custom rom I never get even a boot animation. So I'm not sure what's up with it
stang5litre said:
This needs to be maken into a rom first as well before deodexed but i can do both actually if you don't know how to build a rom.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
What you think?
bjf189 said:
Well if you could do both, I'd really appreciate it. I can't even begin to understand how to extract an md5. So confusing. Plus gotta get it to work with flash fire. I tried other roms with flashfire and kept getting system not responding. So I always had to Odin back to stock and on the custom rom I never get even a boot animation. So I'm not sure what's up with it
Click to expand...
Click to collapse
Flash fire is horrible. Use v24 seems to be the best atm. I can do both. In the middle of mod'ing the s5 rom I made. But after I build it I would have you test it 1st before deodexing as you want to make sure it boots 1st before moving on.
Sent from my SM-G935V using Tapatalk
stang5litre said:
Flash fire is horrible. Use v24 seems to be the best atm. I can do both. In the middle of mod'ing the s5 rom I made. But after I build it I would have you test it 1st before deodexing as you want to make sure it boots 1st before moving on.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I think I tried your rom before. Your username was on a rom that I tried. It was non mdk which was said to use. I used flashfire beings I can't have safestrap on lollipop. It's all I could use to flash things thanks to a locked bootloader. But I'll try your suggestion and I can surely test what you put out for the s4. Just need an idea of what to use to flash things. And you talking version 24 of flashfire? Cause I already use that an got those outcomes. Also if it makes it any easier on you, could you just rebuild your ultranote5 rom for the prepaid variant? Whichever is easier for you. I loved the feature list that you had for it though I couldn't get it to get past the boot screen cause it would like freeze at the animation but at the same time there wasn't even an animation. Just a quick Samsung sound that doesn't even finish. Wish I knew more about rom development but it can get get complex I think.
bjf189 said:
now that i have released the stock firmware of OH7, i am trying to Deodex this also but keep getting failed start ups. i used LBD 2.5 to try an deodex and followed the guide but i hear start up sound not even a second and it stops and it dont show the verizon logo. i used flashfire to flash the deodexed files. so that being said, could some actual dev, deodex this firmware for i cannot? id really appreciate it and id share the deodexed firmware on the thread as well with of course giving proper credit to whomever can deodex it. thanks!
Click to expand...
Click to collapse
Not sure if it's still an issue or not, but I had similar problems before. Flashfire didn't seem to be finishing backups or flashes. I think I was using v18 or 19. Setting the screen timeout to 10 minutes fixed it, no problems after that and I just set it back when I'm done.
F1a5hP01ntX said:
Not sure if it's still an issue or not, but I had similar problems before. Flashfire didn't seem to be finishing backups or flashes. I think I was using v18 or 19. Setting the screen timeout to 10 minutes fixed it, no problems after that and I just set it back when I'm done.
Click to expand...
Click to collapse
My screen never shut off when I used flashfire. So I'm not sure. Could be something in flashfire being it was made for the s4. Not the prepaid variant. So maybe some code in it is different in the postpaid. Who knows
bjf189 said:
My screen never shut off when I used flashfire. So I'm not sure. Could be something in flashfire being it was made for the s4. Not the prepaid variant. So maybe some code in it is different in the postpaid. Who knows
Click to expand...
Click to collapse
Ah, not sure about that. I'm pretty sure my screen would shut off and then reboot shortly afterward as if it finished properly. I also just remembered that flashfire used to rearrange the order that the operations were added and would move the wipe toward the bottom of the list, usually after the flash. I would double check that the order is correct before starting if you haven't already. Those two were the only problems I had. Hope those tips help in some way.
F1a5hP01ntX said:
Ah, not sure about that. I'm pretty sure my screen would shut off and then reboot shortly afterward as if it finished properly. I also just remembered that flashfire used to rearrange the order that the operations were added and would move the wipe toward the bottom of the list, usually after the flash. I would double check that the order is correct before starting if you haven't already. Those two were the only problems I had. Hope those tips help in some way.
Click to expand...
Click to collapse
Well far as I know I'm using the up to date version which is .24. I haven't had the screen off issue or the rearranging problem. Flashfire showed what it was doing and what order it did it in. Everytime I used it, if the screen went black, it would say rebooting...after all was finished. So maybe the version you had was just buggy which the dev did say its a work in progress. Stuff like that, I'd be surprised if they got it to work perfectly with no bugs
stang5litre said:
Flash fire is horrible. Use v24 seems to be the best atm. I can do both. In the middle of mod'ing the s5 rom I made. But after I build it I would have you test it 1st before deodexing as you want to make sure it boots 1st before moving on.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I am more then willing to test any roms out as well. My new Galaxy S4 prepaid is only for tethering on my unlimited data, so I need a rom that I can install Xposed Framework on. Any rom that comes out and needs testing for OH7 based phones, I am onboard with.
TheXev said:
I am more then willing to test any roms out as well. My new Galaxy S4 prepaid is only for tethering on my unlimited data, so I need a rom that I can install Xposed Framework on. Any rom that comes out and needs testing for OH7 based phones, I am onboard with.
Click to expand...
Click to collapse
Well I am looking to install xposed as well but we gotta wait for the dev to have free time to rebuild a rom to the oh7. Well at least he has two people willing to test now for him. How did you get unlimited data with Verizon? They so stingy with data
Sorry been busy. Will build it tonight. Already deodexed. Just got to build it. If all you doing is using it for a hot spot why waste time building a rom for it. Dl a app and use your hot spot. I use foxfi on my s7 edge. Works np.
Let me know. Thought this was for people to actually use.
Sent from my SM-G935V using Tapatalk
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
bjf189 said:
Well far as I know I'm using the up to date version which is .24. I haven't had the screen off issue or the rearranging problem. Flashfire showed what it was doing and what order it did it in. Everytime I used it, if the screen went black, it would say rebooting...after all was finished. So maybe the version you had was just buggy which the dev did say its a work in progress. Stuff like that, I'd be surprised if they got it to work perfectly with no bugs
Click to expand...
Click to collapse
Black screen means the order was incorrect and wipe was moved to the end.
Sent from my SM-G935V using Tapatalk
stang5litre said:
Sorry been busy. Will build it tonight. Already deodexed. Just got to build it. If all you doing is using it for a hot spot why waste time building a rom for it. Dl a app and use your hot spot. I use foxfi on my s7 edge. Works np.
Let me know. Thought this was for people to actually use.
Sent from my SM-G935V using Tapatalk
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
Black screen means the order was incorrect and wipe was moved to the end.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I'm not looking to use it for the hotspot. I already can use it without any problems. I'm just wanting a custom rom/modded stock rom, I hate full stock and I love being deodexed. I'm sure more people will use your rom once they discover it.
If you believe that flashfire moved the order around, what can I do to stop that? The log in it says what it's doing and it says it's going in correct order so im not sure. Ive been using v24 which is latest I think
bjf189 said:
I'm not looking to use it for the hotspot. I already can use it without any problems. I'm just wanting a custom rom/modded stock rom, I hate full stock and I love being deodexed. I'm sure more people will use your rom once they discover it.
If you believe that flashfire moved the order around, what can I do to stop that? The log in it says what it's doing and it says it's going in correct order so im not sure. Ive been using v24 which is latest I think
Click to expand...
Click to collapse
Flash Fire moves it on its own right before you flash. You have to press and hold wipe and drag it to the top. It does this a lot. Pain in the arse. Ok I'll build it then just wasn't sure
Sent from my SM-G935V using Tapatalk
stang5litre said:
Flash Fire moves it on its own right before you flash. You have to press and hold wipe and drag it to the top. It does this a lot. Pain in the arse. Ok I'll build it then just wasn't sure
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I did that cause it put it at the bottom at default. I moved it to the top but still got same outcome. Maybe it's something to do with the kernel an bootloader bring different? That's my guess
bjf189 said:
I did that cause it put it at the bottom at default. I moved it to the top but still got same outcome. Maybe it's something to do with the kernel an bootloader bring different? That's my guess
Click to expand...
Click to collapse
What were you flashing?
Sent from my SM-G935V using Tapatalk
stang5litre said:
What were you flashing?
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Well I tried out your ultra note5 and non mdk one. I believe the ultra note wouldn't show the boot animation and cut off booting sound after a second then did nothing. The other one which was the non mdk one, didn't show boot animation but made the Samsung sound correctly but after booting into the system like ten minutes later of waiting, I get a pop up of system is not responding. If I ignore it an let it load another ten minutes or so, the setup wizard opens but if I hit wait or close on the system not responding box, it all closes and goes to black screen again and just repeats
bjf189 said:
Well I tried out your ultra note5 and non mdk one. I believe the ultra note wouldn't show the boot animation and cut off booting sound after a second then did nothing. The other one which was the non mdk one, didn't show boot animation but made the Samsung sound correctly but after booting into the system like ten minutes later of waiting, I get a pop up of system is not responding. If I ignore it an let it load another ten minutes or so, the setup wizard opens but if I hit wait or close on the system not responding box, it all closes and goes to black screen again and just repeats
Click to expand...
Click to collapse
Uploading stock rom for you to try....androidfilehost keeps losing connection.. You already built the rom from what i read a page back. So do you want me to just Upload the deodexd stuff for you to insert?
Sent from my SM-G935V using Tapatalk
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
## I TAKE NO RESPONSIBILITY IF YOU BRICK YOUR DEVICE##
THIS IS A MATERIAL TWRP IMG THAT I MADE FOR THE PAYTON
I HAVE TESTED THIS WHIT MY OWN DEVICE
ITS IS FULLY STABLE NOW YOU ALL TO ENJOY!!!
BUT IM STILL TWEAKING THING
INSTALL THE SAME WAS AS EVERY OTHER TWRP IMG
RECOMMEND CLEAN INSTALL DO NOT INSTALL OVER OTHER TWRP
reboot to bootloader
run this command
Fastboot boot TWRP-payton-material.img
wait for it to boot
then flash the installer zip
IF YOU KEEP REBOOTING BACK INTO TWRP REFLASH MAGISK
TO GET THE ADD ON TO BE ABLE TO CHANGE COLOR LAYOUT AND ALL THAT
AFTER FLASH COMPLETELY REBOOT BACK TO OS
THEN REBOOT BACK TO TWRP CLICK THE ICON NEXT TO SETTING IN THE TOP RIGHT
IT WILL ASK YOU FOR UI.ZIP CLICK CHANGE THEME SWIPE TO FLASH AND THERE YOU GO
DOWNLOAD
I HOPE EVERYONE ENJOYS!!!
FEATURES SO FAR
EVERYTHING IS WORKING!!!
MTP(YES)
OTG(YES)
ADB SIDELOAD(YES)
DECRYPTION(YES)
BONUS TWEAKS BUILT IN (YES)
GROUP AND BUG REPORTS
will this stay in place with a rom OTA (like havoc?)
themedicduck said:
will this stay in place with a rom OTA (like havoc?)
Click to expand...
Click to collapse
At this time i cant give a 100% yes
I only have a couple of beta tester as of right now
But they have reported it work like normal
so I do be leave that it will
if you do a OTA and it fails please tell me asap
Im still working on it but is stable enough to be beta tested :good:
FizzyAps said:
At this time i cant give a 100% yes
I only have a couple of beta tester as of right now
But they have reported it work like normal
so I do be leave that it will
if you do a OTA and it fails please tell me asap
Im still working on it but is stable enough to be beta tested :good:
Click to expand...
Click to collapse
Good deal.
I'm guessing dirty flashing this over my current TWRP is a bad idea? Clean install?
Recommend clean install do not install over other twrp
FizzyAps said:
Recommend clean install do not install over other twrp
Click to expand...
Click to collapse
Ok.
Did you do anything special to get this to build?
What sources are you using? Omni trees or los?
gee one said:
Did you do anything special to get this to build?
What sources are you using? Omni trees or los?
Click to expand...
Click to collapse
I de-compiled the official 3.2.3-1 and syberhexen 3.2.3-0
and re-compiled
them together with the themed ui the us see to get stable result
so mix of both
gee one said:
Did you do anything special to get this to build?
What sources are you using? Omni trees or los?
Click to expand...
Click to collapse
you can follow the build and updates on all are twrps here
https://t.me/motox4twrp
themedicduck said:
will this stay in place with a rom OTA (like havoc?)
Click to expand...
Click to collapse
There is no longer a recovery partition, instead recovery is built into the boot.img on X4 (and all other slot A/B devices)
So when you flash a rom, that file gets updated and you loose twrp.
The only way around that would be a custom installer that manually installs twrp during flash.
SchmilK said:
There is no longer a recovery partition, instead recovery is built into the boot.img on X4 (and all other slot A/B devices)
So when you flash a rom, that file gets updated and you loose twrp.
The only way around that would be a custom installer that manually installs twrp during flash.
Click to expand...
Click to collapse
Gotcha ok. I think I get it now. So if I don't want TWRP to be overwritten, I'll just have to manually flash updates every time like I do now.
themedicduck said:
Gotcha ok. I think I get it now. So if I don't want TWRP to be overwritten, I'll just have to manually flash updates every time like I do now.
Click to expand...
Click to collapse
You have to flash TWRP after every rom flash whether its OTA or manual.
Thank you for providing the decrypt function.
But I use a 6x6 pattern, and it is literally impossible to succeed with my pattern since the dots are so close together. Possible to spread them out?
I need to know: What are the bonus tweaks built in? Thanks
flieswithhawks said:
I need to know: What are the bonus tweaks built in? Thanks
Click to expand...
Click to collapse
Everything listed in the post
Which installer, TWRP-payton-Material-stb1 or TWRP-payton-material-installer? What's the difference?
flieswithhawks said:
I need to know: What are the bonus tweaks built in? Thanks
Click to expand...
Click to collapse
BONUS TWEAKS BUILT IN (YES)
It says right there. (YES)
I'd also like a list of what exactly the bonus tweaks are, as they are apparently mixed in with regular non-tweaked content.
So, in the context of recovery images... how exactly is there such a thing as a "dirty" flash? A flash is a flash for the recovery image. It is contained. What am I missing?
Please tell me!
TWRP-payton-Material-stb1.img or TWRP-payton-material.img - what's the difference, which one to use? Will the project be further developed - 3.3.1-0?
Thank you for a good job!
@FizzyAps Nicely done. Although I wish I could get the theme used when booting from the IMG file (TWRP-payton-material.img). -- That was impressive! Unfortunately, I see that the installer (and the ui.zip) do not include that. Still, it is both a visual and tech improvement over the current stock TWRP.
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