Related
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
This is the latest KitKat 4.4.2 Rom from T-mobile. I ported it to ATT and tried to apply just enough modification to keep all the functionality and remove all the limitations. Nothing has been removed from the rom. The disabled apps are kept to a very minimum so this is NOT a de-bloated ROM. This is as close to stock as it gets. If you need a debloated version go here: http://forum.xda-developers.com/att-galaxy-s5/development/rom-debloated-bnh5-ported-tmobile-t2901620
1- Pre-rooted and deodexed.
2- Knox, security apps, and updater disabled (your phone will no longer update itself without your knowledge)
3- Call recording enabled.
4- SDcard write restrictions removed.
5- Tethering restrictions removed.
6- Download Bosoter functional on AT&T network.
7- Lookout security and T-mobile apps that don't work on ATT are disabled.
If a certain features like WiFi calling doesn't work it's because AT&T doesn't support the feature.
Requirements:
1- Safestrap or custom recovery.
2- To begin with, you should be on ATT NCE4 rom or a variant of that. It has been reported that this is incompatible with NG3
Download link:
Download the latest version since I post an update immediately after discovering a bug.
Mega https://mega.co.nz/#!gpUAxBqI!ukloBoz5KRzixo8a2cEXxsmJ_K0z-8LAYDfKerkWG4U (version 5)
Instructions:
This is a flashable zip. Boot to recovery to flash it. I strongly recommend a clean wipe before flashing a new Rom.
After reboot, go through the initial setup and then leave the phone alone for 10 minutes before you use it. After the first reboot the data connection takes a while to be recognized. If it does not connect after 10 min, enable and disable airplane mode and it should be fine after that.
Credits:
JustArchi for creating ArchiKitchen
Screenshots
Download booster, home screen, call recording.
Change log:
V1: Disabled knox and updaters and security apps except for Lookout.
V2: Same as V1 with Lookout and T-mobile apps disabled.
V3: Essentially the same as V2. A small type was corrected.
V4: Disabled IQ lib and corrected a potentially fatal typo in the update script.
V5: Disabled two more annoying Samsung auto-update apps that somehow slipped through.
Amazing thanks
Enviado desde mi SM-G900F mediante Tapatalk
Any benefits of features to this to make it worth while over say, Goldeneye (MI2) or an International based ROM?
joe3681 said:
Any benefits of features to this to make it worth while over say, Goldeneye (MI2) or an International based ROM?
Click to expand...
Click to collapse
This is closer to pure stock, which may offer benefits in stability. As an example, when I flash this on my system the status remains official (no padlock on boot up).
Tried it. Still full of TMobile bloat and couldn't even do anything with it because "Context Service has stopped". Couldn't type anything anywhere like web browser, couldn't edit the notification toggles, anything. Generally has WAY too many TMobile remnants left in it. Once that's all fixed it might be stable. Not entirely sure this was even tested out.
Also, idk what "Security Apps" were removed but Lookout is most annoyingly still there.
Before it's asked yes, It was a CLEAN freshly wiped install.
joe3681 said:
Tried it. Still full of TMobile bloat and couldn't even do anything with it because "Context Service has stopped". Couldn't type anything anywhere like web browser, couldn't edit the notification toggles, anything. Generally has WAY too many TMobile remnants left in it. Once that's all fixed it might be stable. Not entirely sure this was even tested out.
Also, idk what "Security Apps" were removed but Lookout is most annoyingly still there.
Before it's asked yes, It was a CLEAN freshly wiped install.
Click to expand...
Click to collapse
I flashed this using safestrap on a phone that had G900AUCU1ANCE installed. Since safestrap does not allow boot.img to be written, the result was that after the flash AP and CSC changed to BNH5 but the kernel remained at ANCE1. With this configuration I didn't see any problems. Also, this rom doesn't come with a modem, so it relies that the phone comes with unaltered ATT modem, in my case ANCE1. So, do you have a different kernel or modem?
BTW, disabled security apps are Carrier IQ, and security manager service/provider.
PS: I agree with you on Lookout being a nuisance. I will disable it and re-upload.
I flashed from stock NG3
joe3681 said:
I flashed from stock NG3
Click to expand...
Click to collapse
I see. Perhaps T-mobile NH5 rom is not compatible with ATT NG3 boot.img or modem. I will put a note in the OP. Thanks for checking this out.
OP, can you do something similar with a stock G900F firmware that will be able to be flashed on a G900A?
I have a smg900az - on tmobile
I have a smg900az on Tmo- I want this rom for this purpose. Does this include tmobile AND att modems, or just att? I am downgrading from lollipop..
Because I am sure there are others with ATT based phones who may be on TMO- would you mind if I kang your rom, debloat it, or include a debloat option, add features, etc? All credit would be given to your base.. and it would be a minute before I can get it done anyways..
P.S. PLEASE PLEASE post the md5 checksum for each version! Many of us dont want to spend the time wiping, flashing, finding out it is corrupt, then having to restore, etc!
Attached is the md5 file for version 5 that es-file explore pushed out
md5: a40d7d1ee9903bbec056cd29d52c0277 <--- flashed without a hitch
also- downgraded from a lollipop rom(Liquidsmooth 5.0 revision 2 from the unified dev section) without anything special.. so now sure what is meant by-"To begin with, you should be on ATT NCE4 rom or a variant of that. It has been reported that this is incompatible with NG3" - but perhaps you should link to anything that explains why you believe this..
I am inviting you to a document here where I hope to get developers/contributors for all galaxy variants sharing their knowledge openly- http://forum.xda-developers.com/gal...mplified-to-connect-developers-share-t2997834
KnowledgeBroker said:
I have a smg900az on Tmo- I want this rom for this purpose. Does this include tmobile AND att modems, or just att? I am downgrading from lollipop..
Because I am sure there are others with ATT based phones who may be on TMO- would you mind if I kang your rom, debloat it, or include a debloat option, add features, etc? All credit would be given to your base.. and it would be a minute before I can get it done anyways..
P.S. PLEASE PLEASE post the md5 checksum for each version! Many of us dont want to spend the time wiping, flashing, finding out it is corrupt, then having to restore, etc!
Attached is the md5 file for version 5 that es-file explore pushed out
md5: a40d7d1ee9903bbec056cd29d52c0277 <--- flashed without a hitch
also- downgraded from a lollipop rom(Liquidsmooth 5.0 revision 2 from the unified dev section) without anything special.. so now sure what is meant by-"To begin with, you should be on ATT NCE4 rom or a variant of that. It has been reported that this is incompatible with NG3" - but perhaps you should link to anything that explains why you believe this..
I am inviting you to a document here where I hope to get developers/contributors for all galaxy variants sharing their knowledge openly- http://forum.xda-developers.com/gal...mplified-to-connect-developers-share-t2997834
Click to expand...
Click to collapse
1- This doesn't have any modem in it. Please only use version 5. The older ones are buggy.
2- You can use this ROM for your purpose. Thanks for giving credits.
3- I think I am getting the same MD5: a40d7d1ee9903bbec056cd29d52c0277.
najoor said:
1- This doesn't have any modem in it. Please only use version 5. The older ones are buggy.
2- You can use this ROM for your purpose. Thanks for giving credits.
3- I think I am getting the same MD5: a40d7d1ee9903bbec056cd29d52c0277.
Click to expand...
Click to collapse
Maybe you can clarify- the big modem thread on the tmo S5 section said not to flash their modems on another device.
My phone is back on tmo, so I imagine that running a tmo modem could increase reception..
And if you're willing to add flashable scripts that debloat and some others that make some good changes to the build prop- you have a good base, I wouldn't change it.. then people can just add/remove specific features in your own thread.
Join that Google doc in the last post, and create a section about what you've learned porting over the tmo rom.. more devs need to take it seriously.
Sent from my SM-G900T using XDA Free mobile app
Ignore this... I'm using the debloat version.
Sent from my SM-G900T using XDA Free mobile app
Did you happen to disable any of the Samsung account apps? I'm trying to sign in on gear manager to work with my gear s, but when I go to sign in to my Samsung account it crashes the gear app
LukeLeBron said:
Did you happen to disable any of the Samsung account apps? I'm trying to sign in on gear manager to work with my gear s, but when I go to sign in to my Samsung account it crashes the gear app
Click to expand...
Click to collapse
Yes. Samsung account apps are disabled. You can go to /system/app or /system/priv-app, find the app that you want to enable, and renaming it from wuteverthenameiz.apk.bac to wuteverthenameiz.apk and reboot.
Since I'm on ANG3 rooted, no recovery, I'm happy with my current setup, I just need the stock T-Mobile apps. Can you help?
**You can begin the following process from any Build/ROM but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app.
**Notice** - I light of the new OF2 update these ROM's are no longer safe. Stand by for a new KeepRoot thread!
Downloads:
- G900A_OC4_Stock_Rooted_ROM_wOA1_BL
- G900A_OC4_Stock_DeOdexed_ROM_wOA1_BL
Set your screen timeout setting to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and use default "Reboot" setting.
6. Last, press the lightning bolt then "Ok" to begin the flash .
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the AT&T splash screen for about 1 - 2 minutes ( 10 - 15 mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
Optional - Enable Native Tethering:
- G900A_OC4_TetherAddOn (Flash using FlashFire's "Flash zip or ota" option).
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery to OC4. Your Bootloader will only be updated OA1 allowing for downgrading your firmware at anytime.
3. As of 5/7/2015 no need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. The TetherAddOn has been moved Here.
5. If you do not already have root access or to unbrick you must flash the G900A_Downgrade_to_NCE.tar(Caution! Do not use if you have taken the OC4 ota update) and root with TowelRoot, before continuing with the above process.
6. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
For whenever you get a chance to think about it, will there ever be a Safestrap for 5? need to look into Nandroid backups then? i loved SS. thanks again for all your hard work. AND FAST TOO.
I suggest that since safestrap no longer works, to do the data backup in KIES before this method and restore after doing this method.
muniz_ri said:
**You can begin the following process from any previous Build/ROM but you must already have root and Safestrap installed. Make certain Reactivation lock is unchecked!**
Instructions:
1. Extract the G900A_OC4_Stock_Rooted_Backup from the .rar archive and place it into the following folder: ext-sdcard/TWRP/BACKUPS/xxxxxx, fyi...the name of this folder will vary. If the folder does not already exist you must first use Safestrap to create a nandroid backup and Safestrap will create the folder for you.
2. From Safestrap recovery press "Wipe" then "Advanced Wipe" and wipe everything but your ext-sdcard.
3. From the main menu press "Restore," then select and restore the G900A_OC4_Stock_Rooted_Backup.
4. Once complete from the main menu press "Reboot," then reboot into "Download" mode.
5. Last, flash the G900A_OC4_Stock_Partitions_wOA1_BL using Odin's PDA slot (AP in Odin v3.09+) and reboot. Done!
After completing the above process your device will pause on the AT&T splash screen for 5 - 10 minutes before completely rebooting.
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. This process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery to OC4 and your Bootloader to OA1 (BusyBox is also pre-installed).
3. Safestrap will no longer function after updating to 5.0.
4. The most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure!
Click to expand...
Click to collapse
I did everything as you said, but when I am trying to restore I says RESTORE FAIL??? What should I do
I was on 4.4.4???
Now I downgrade to 4.4.2 with G900A_Downgrade_to_NCE.tar but again I cant make OTA update
Please help
CAG-man said:
I suggest that since safestrap no longer works, to do the data backup in KIES before this method and restore after doing this method.
Click to expand...
Click to collapse
Good idea.... I did not do this lol, but I have some titanium backups on my sd card.
I was on the pre-rooted 4.4.4 that muniz_ri put together a couple of months ago. Worked well and quickly without any problems.
I actually don't mind starting fresh.... anything else I'll use titanium ... I miss safestrap though (security blanket wise lol).
Nice work again muniz_ri.
muniz_ri said:
OP
Click to expand...
Click to collapse
Been following this since yesterday, just made an account to say fantastic work muniz, this really helps out the community.
One thing though, once we move to Lollipop, are we able to do the same as Verizon and flash the old kernel to access Safestrap?
I am on 4.4.2 rooted with Unity ROM installed. Do I need to upgrade to 4.4.4 first or am I all set?
muniz_ri said:
**You can begin the following process from any previous Build/ROM but you must already have root and Safestrap installed. Make certain Reactivation lock is unchecked!**
Instructions:
1. Extract the G900A_OC4_Stock_Rooted_Backup from the .rar archive and place it into the following folder: ext-sdcard/TWRP/BACKUPS/xxxxxx, fyi...the name of this folder will vary. If the folder does not already exist you must first use Safestrap to create a nandroid backup and Safestrap will create the folder for you.
2. From Safestrap recovery press "Wipe" then "Advanced Wipe" and wipe everything but your ext-sdcard.
3. From the main menu press "Restore," then select and restore the G900A_OC4_Stock_Rooted_Backup.
4. Once complete from the main menu press "Reboot," then reboot into "Download" mode.
5. Last, flash the G900A_OC4_Stock_Partitions_wOA1_BL using Odin's PDA slot (AP in Odin v3.09+) and reboot. Done!
After completing the above process your device will pause on the AT&T splash screen for 5 - 10 minutes before completely rebooting.
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. This process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery to OC4 and your Bootloader to OA1 (BusyBox is also pre-installed).
3. Safestrap will no longer function after updating to 5.0.
4. The most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure!
Click to expand...
Click to collapse
I successfully did a backup via Kies and via Safestrap onto my external SD, but when I installed 5.0 and the updated kernel... I restored my backup from Kies and it did successfully restore, but it apparently didn't restore my apps, is there a way I can restore my apps with the backup from Safestrap? Thanks for any replies in advance.
Sorry to be a pain but for those of us that just rooted before and never used Safestrap,can you break it down Barney style so everybody can understand it correctly plz? I've never used SS and would like to keep my root but am leary of using SS and doing backups,etc. I'm on 4.4.4. OA1 stock,rooted.
PS4AndroidHacker said:
Sorry to be a pain but for those of us that just rooted before and never used Safestrap,can you break it down Barney style so everybody can understand it correctly plz? I've never used SS and would like to keep my root but am leary of using SS and doing backups,etc. I'm on 4.4.4. OA1 stock,rooted.
Click to expand...
Click to collapse
check out here: http://forum.xda-developers.com/showpost.php?p=56707749&postcount=294
then install busybox then safestrap (not to worry, works great, been around quite a while), create/install recovery in SS, make a current backup and then follow the great instructions in post #1
but if you dont like L, then its back to the beginning with NCE, root, SS, go back to OA1 and then restore your OA1 bu from SS
http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120
at least this is my understanding and i have gone from 442/NG3 to OA1 and back this way and it works fine, dont take too long either. just need all the files.
Thank you for the guide, I will run it soon. Xposed Framework is working just fine with Lollipop as well right? Besides Titanium Backup that is my other need for root.
.......... thk you for your amazingly quick work :highfive: ............
kipptc said:
Been following this since yesterday, just made an account to say fantastic work muniz, this really helps out the community.
One thing though, once we move to Lollipop, are we able to do the same as Verizon and flash the old kernel to access Safestrap?
Click to expand...
Click to collapse
Have not seen it confirmed yet but it should work. Added the kernels to the OP.
samccfl99 said:
For whenever you get a chance to think about it, will there ever be a Safestrap for 5? need to look into Nandroid backups then? i loved SS. thanks again for all your hard work. AND FAST TOO.
Click to expand...
Click to collapse
There is a safestrap replacement coming out of the vz note 3 forum soon. Should work on the S5.
pennywisdom said:
Xposed Framework is working just fine with Lollipop as well right?
Click to expand...
Click to collapse
Unless something has changed very recently, it is only working for AOSP, it is causing bootloops on any Touchwiz based Lollipop.
muniz_ri said:
There is a safestrap replacement coming out of the vz note 3 forum soon. Should work on the S5.
Click to expand...
Click to collapse
thats great news! please let us know when you know...
just one thing when u have a chance to respond. obviously i dont trust google's great development team. so IF L is not so good yet (do we know if this is 5.0 or 5.0.1 or .2?) is there an easier way to get back to 442/NG3. i have read in the post how to bring SS back temporarily, so my real question is Can i Odin the G900A_NG3_Stock_Kernel.tar.md5 and then just restore my XDK install or do i need to go back to NCE and go forward? (i think the answer is no, but hey, its worth it to ask). this is the part i do not understand about SELinux and the partitions and what they do.
i thank you for all your hard work and a small donation will be coming soon. YOU ARE THE CHAMP!!!
hlb3 said:
Unless something has changed very recently, it is only working for AOSP, it is causing bootloops on any Touchwiz based Lollipop.
Click to expand...
Click to collapse
Ooh that's poopy. Well maybe I can get by without some of those tweaks in Lollipop.
hlb3 said:
Unless something has changed very recently, it is only working for AOSP, it is causing bootloops on any Touchwiz based Lollipop.
Click to expand...
Click to collapse
so you are saying Xposed dont work right now if we go to L? what good is that? i wonder what else dont work??? we have the touchwiz because of stupid att and their locked bootloader, right? wish i had a 900-F....really want to play with this, but what is the point??? plus if this is just plain 5.0, well then hell, another should not be too far behind it. do u think ATT fixed any bugs from 5.0 (can they even?)
muniz_ri said:
**You can begin the following process from any previous Build/ROM but you must already have root and Safestrap installed. Make certain Reactivation lock is unchecked!**
Pls someone help , I updated to Lolipop and downgraded my phone to 4.4.2 and got my phone soft bricked . I tried flashing OC4 stock partitons wl 0AL bootlader but it is not flashing and is showing failed . Pls can you upload the previous orignal OC4 stock partition files ? This new OC4 stock partition file is different . Pls I am screwed
Thanks
Click to expand...
Click to collapse
yash.mann97 said:
muniz_ri said:
**You can begin the following process from any previous Build/ROM but you must already have root and Safestrap installed. Make certain Reactivation lock is unchecked!**
Pls someone help , I updated to Lolipop and downgraded my phone to 4.4.2 and got my phone soft bricked . I tried flashing OC4 stock partitons wl 0AL bootlader but it is not flashing and is showing failed . Pls can you upload the previous orignal OC4 stock partition files ? This new OC4 stock partition file is different . Pls I am screwed
Thanks
Click to expand...
Click to collapse
Just flash the OC4 kernel from the OP.
Click to expand...
Click to collapse
This is an early release, but just like the other it's fully functional as a daily driver.
Note:
Still no root method for our device on Nougat
Features:
Pixel 2 emoji
Pixel 2 fonts
Pixel 2 wallpapers (live and still)
Pixel 2 sounds and notifications
Google Assistant
Google Lens
Unlimited Google photo storage (Pixel feature)
Round icons (uses apps native icons, not masks)
Daydreams enabled on battery power (screensaver can be used like always on display, until 15% battery)
360° rotation, everywhere
Power menu from sleep
All quick settings enabled (including mobile data toggle)
Hotspot activation bypass
System menu translated into every language
To do:
Lower the 15% screensaver limit
Add Pixel 2 logo and startup animation
Lockscreen background
Lockscreen default widgets (phone & camera)
What else do you want?
Bugs:
Selfie video doesn't record (prolly not fixable until we get an updated app)
Anything else?
Installation:
From 6.0.1:
Flash with Flashfire and do full wipe
From 7.1.1:
*Must use PC*
Method A
1. Unzip ROM.
2. Flash the included eng_root kernel with Odin.
3. Double click the included "Install.bat"
The script will wipe your data for you (and not touch the internal sd)
Method B
Use Odin to downgrade to 6.0.1 then flash zip with flashfire.
Download
I'll add more screenshots tomorrow
As of right now, even with the custom ROM, there is no root, correct?
I installed it, and every time I boot, I get a System UI has stopped error.
@NateDogg1232
Did you wipe?
... Correct no root yet, until we get a permissive kernel
DamienMc said:
@NateDogg1232
Did you wipe?
... Correct no root yet, until we get a permissive kernel
Click to expand...
Click to collapse
Yes, I did wipe.
I even did it again using the default recovery just to make sure.
More screenshots
Please, upload more screenshots, I would like to install this rom but I do not know if I really have any problems when using it, as it is in terms of speed, can it really be used now?
@RaghebAlama
Sorry I am having problems uploading more screenshots (used all my data this month)
I'll be sure to do it this evening when I'm on wifi.
I've been running this for a week now and haven't had any issues yet
But after the above comment you might want to grab full Odin updates as well, just in case you need to recover
@NateDogg1232
What method did you use to install?
What device do you have?
I would recommend going back to stock and giving it another try.
I apologise tho, I tried to get a few testers this time but never find any. It's hard to test every scenario with just one device
I used FlashFire from actually your first GPE ROM.
I have the J320A
I will reset from stock and try again as soon as I can and try again.
Whether it works or not, though. Thank you for your work on this phone
I bet that's it, I'm not sure I tried to install from v1.
Can't think of why it would fail except maybe if goodlock has files on your sd and this systemui is trying to use them... If you want to test that just pull your sd, because wipe already did your internal sd
I'll test it later this evening
[EDIT]
Nah wasn't that, it was a mistake by me. Two actually.
Testing a quick fix now. And I'll upload a full fixed Rom while I sleep
[/EDIT]
DamienMc said:
@RaghebAlama
Sorry I am having problems uploading more screenshots (used all my data this month)
I'll be sure to do it this evening when I'm on wifi.
try to explain in detail the installation process since 7.1.1 the eng_root does not detect it ODIN if it is not in .tar format, after installing the Eng_root, you have to start the normal cell phone and then the second.pass with the Install.bat ?
Click to expand...
Click to collapse
I fixed the systemui error and another popped up, sigh... ill let you know when it's fixed.
The only way to install this currently is from 7.1.1
@RaghebAlama
Eng_root is a tar. Flash it with Odin.
Your phone will stay on the logo the entire time.
Then just run the bat...The script waits for your phone, copies the required files, then it flashes the original kernel back and reboots.
easy peasy
... and it really does work installing this way
Sorry for the delay. Uploaded fixed version, OP updated
Alright, this looks AWESOME. Will try it when I get time. But about the root problem: I don't know if nobody's thought of this, or if I don't know something you do, but to get root for this, couldn't you add Magisk-14.zip (or another root method) to the queue in Flashfire, or include it in the install.bat? Flash the ROM then root, then reboot to system? I've tried to install Magisk before on stock Nougat with its new way of installing, which is flashing a boot.img that Magisk Manager patched, but Odin always failed on Operation: Write. I was going to go back to Marshmallow to try flashing a ROM and Magisk with Flashfire.
Hello. Can I get permission to make a version for j320fn/f/g
DJJosephJumper said:
Alright, this looks AWESOME. Will try it when I get time. But about the root problem: I don't know if nobody's thought of this, or if I don't know something you do, but to get root for this, couldn't you add Magisk-14.zip (or another root method) to the queue in Flashfire, or include it in the install.bat? Flash the ROM then root, then reboot to system? I've tried to install Magisk before on stock Nougat with its new way of installing, which is flashing a boot.img that Magisk Manager patched, but Odin always failed on Operation: Write. I was going to go back to Marshmallow to try flashing a ROM and Magisk with Flashfire.
Click to expand...
Click to collapse
Odin will not install a custom boot image on our device.
There are other ways to install the custom kernel, but our bootloader will not allow it to boot.
I can install SuperSU, but our selinux policy will not let the system load. The way I know it's rooted tho is that I can get a root shell thru adb, but that's useless since the system will not fully load... We need a new permissive boot image (engboot)
borksek said:
Hello. Can I get permission to make a version for j320fn/f/g
Click to expand...
Click to collapse
All yours bud
DamienMc said:
Odin will not install a custom boot image on our device.
There are other ways to install the custom kernel, but our bootloader will not allow it to boot.
I can install SuperSU, but our selinux policy will not let the system load. The way I know it's rooted tho is that I can get a root shell thru adb, but that's useless since the system will not fully load... We need a new permissive boot image (engboot)
Click to expand...
Click to collapse
Got it. Again, I was without the experience. Thanks for clearing it up.
Can i use this rom on my j320f
Does it work on the SM-J320m?
@aR_aNiK & @lithoy
Sorry guys, no.
I created a new ROM with WifiCalling: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]
ROM last updated: 9/24/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This thread here is just my take and customization on what they already did. Ultimately, I wanted Oreo rooted & modded, but I couldn't find a single guide. And the ROMs that existed weren't exactly what I was looking for. I wanted something exclusive to Tmobile. So I did a ton of reading and compiled it all together into a HOPEFULLY easy guide to follow. PS If you like Samsung bloatware, this is NOT for you!
Description:
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc.
Everything possible I replace Samsung with Google
Solid ROM, very fast
There are very few options in Aroma to limit issues & repeatability. There are many options once booted up after initial setup
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
Aroma installer layout is a little wonky, apologies (If anyone knows how to fix this please chime in )
This will delete all of your data! This is the only way so don't ask. Backup your data!
Features:
Optional Tmobile Apps
Optional Google Apps
Root Features: See Downloads->Recommended Root Zip & thank him for his work!!
Debloated
Deodexed
De-Knoxed
Zipalign
Instant Face Unlock mod
Disable signature verification
S9 Dolby Atmos
Memory Saver
OperMax
More Toggles
Mulit User
Private Mode
Unlock Stock NetWork Speed
Build Prop Tweaks
Device Status Official
White Page
CallRecord
Capture and Record Screen
Remove Volume Safe Warning
Remove brightness Warning
Added Bike Mode
Allow fingerprint unlock after a reboot
Google MarkUp
Force always visible Free Form Menu item in notifications
Substratum Theme
Dual speaker
Samsung Weather
Samsung Video Editor and Trimmer
LancControl Mods:
Ui Mods
3Mint Clock
Gradient statusbar
Virtual Lock Home Recent Button
Phone Mods
Clock Face Setting Aod
AdAway
Dpi Changer
Disable/Enable Apps
Kernel Adiutor
TW Mods:
Adaptive Fast Charging
Wireless Fast Charging
Usb Plug in/out Wakeup
OutDoor Mode
HardKey Lights
TouchLight
Recents Menu Mods:
Tasks Changer
Blur recent and Notification Menu
Download Links:
Base.7z & Oreo_Kevin71246Modded_v1.zip
VoLTE Fix
Steps:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
OPTIONAL: (Testing, WIP...) Backup with Titanium Backup (or whatever) at this time the following apps so they work in the end: Visual Voicemail, Wifi...
OPTIONAL: (Testing, doesnt work. Please provide a fix if you know!) VoLTE Icon Fix: via FlashFire app: Flash OREO_VOLTE_ICON_HOTSPOT_FIX.zip (Flashes fine but doesnt fix it!!)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM
Download & copy Oreo_Kevin71246Modded_v#.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash ZIP or OTA-> Select Oreo_Kevin71246Modded_v#.zip-> Default options-> Check mark-> Lighting bolt at bottom-> OK
Phone will reboot to Aroma
Aroma Setup
Choose options as desired (Use vol up/down+power buttons to select! Touch is offset so if you use this touch BELOW your option to select)
Use very Bottom Right "Next" button if you see multiple
*Wait 3-5min on loading screen. If it doesn't boot after 10min: Hold Vol Down+Pwr buttons (~10sec) until phone restarts. After restarts, IMMEDIATELY hold VolUp + Home buttons. Should say Recovery. Wipe Data/Factory & Wipe cache. Restart Phone. Should load to Setup.
OPTIONAL: Root: Follow "Root Instructions" above, again.
Followup-Steps:
Fix Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Known Issues:
Wifi Calling not working despite flashing Tmobile Wifi & Tmobile Wifi Settings app
Visual Voicemail not working (disabled until we can figure this out)
VoLTE Icon wont go away despite flashing known working fixes
Changelog:
Version 1: First build
Immediate References:
[Rom][ALL_CARRIERS_G930_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]
Root For S7/S7Edge Oreo And Nougat
Project L s7 Google/Samsung Oreo Rom CRF1 Base
Credits:
(Im copying/pasting credits from other links since so many people participated I dont want to miss anyone!)
- @jrkruse & @klabit87 for root
- @Lanc-City for ROM base
- @gustco for eng boot.img
- @Raymonf for modified odin
- @afaneh92 for safestrap
- @me2151 for finding this method
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for xposed on non rooted
- @partcyborg for finding the root method!
- @elliwigy for being great help and original S8 root
- @rayan-refoua for boot animation
- @FatalONEM8 - For posting Oreo OTA
- @stang5litre
- @jds3118
- @Krog18
- @klabit87 for S7 Safestrap
- @amarullz Aroma Installer
- @mrRobinson for adaway
- @Chainfire for Flashfire
- @JaeKar99 for Reactor_BootAnimation
- echoe rom and noname rom
- stang5litre Test Group
- Please PM me if you were forgotten!
Reserved1
Reserved2
Reserved3
Ayy mentioned. Good work on the rom ?
Okay I don't know what's going on here but I have never talked to you or never given you permission to reuse my Rom/work this is stealing my rom is still being worked on this thread must come down this is not cool
IF YOU WANT TO share something Make your own Rom My Rom/Work is not to be reused in any type of way I put a lot of time and work into it
Lanc-City said:
Okay I don't know what's going on here but I have never talked to you or never given you permission to reuse my Rom/work this is stealing my rom is still being worked on this thread must come down this is not cool
IF YOU WANT TO share something Make your own Rom My Rom/Work is not to be reused in any type of way I put a lot of time and work into it
Click to expand...
Click to collapse
Meant no offensive at all, I assure you. Did I completely misunderstand the point of the xda community? I clearly gave you credit and didn't say I created this from scratch, rather pieced it together, literally what every Dev here does. I am not doing this for money. I mentioned & thanked you, which is probably how you found this thread. All I am trying to do is give back to the community. I spent a TON of time going through guides, updating what I found, creating a guide, and testing this - I didn't just rebrand it.
That said, I did use part of your work so I'll give you the choice: can I use part of your work and allow the xda community to benefit, or do you want me to remove your segment & Lanc app this comes with?
Btw see the post above yours. And shouldn't this chat be on PM? For reference, what I used from you was your apks so I didn't have to redownload & retest them and aroma script for a starting point, but the script is 90% different at this point.
Again, I did not mean to offend, but please let me know if I have your permission. Thank you
Good news! We got @Lanc-City 's blessing to continue to use his base ROM & LancControl app. This XDA community is AWESOME! Don't forget to go and check out his original Mod'd ROM: Project L s7 Google/Samsung Oreo Rom CRF1
VoLTE icon fix
Not sure if this will work for everyone. Download System UI Tuner by Zach Wander from Play Store. Once in menu, go to TouchWiz, scroll down to IMS VoLTE Icon and toggle on then off. I did not apply the fix that you have the link for above, and I was able to uninstall the app and the icon does not come back.
Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.
infamouz421 said:
Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.
Click to expand...
Click to collapse
deleted, wrong thread
infamouz421 said:
Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.
Click to expand...
Click to collapse
Copying/Pasting PM I sent you for others, and added some things:
Did you let the "rainbow" sit there for at least 10 min? (It should be 3-5 but who knows.) Are you soft-bricked in your current situation? If you start again, at "Install Stock Oreo:" does this at least restore your phone back to stock Oreo? If so, then try again and proceed with ALL the remaining steps again, CAREFULLY reading the instructions again & again.
Also, what phone model do you have? And I admit I haven't tested the CPU governors in the root script ; I ALWAYS chose none - I'll remove those options in the next version since I have tested them and there are plenty of CPU overclocking options once booted inside the ROM.
If you are able to restart this process and get stock Oreo back, AND chose NO CPU governors in the root script, maybe you want to either try "NO" to Google & Tmobile options just to make sure you can get Android booted- If it boots fine, then try the ROM again and pick Google and/or Tmobile to isolate any issues (things that are breaking)
Have you used ONLY what I provided, such as ODIN (version is important), etc?
Re Flashfire: Default options should be fine. The ROM script will set all the partitions, mounts, permissions, etc.
Good luck!
*Above response I guess is for overall troubleshooting the ROM, if any issues present themselves.
On another note: I'm actively working on this ROM as time allows. Trying to ease the install process, correct some issues, further customize, & improve...
kevin71246 said:
Copying/Pasting PM I sent you for others, and added some things:
Did you let the "rainbow" sit there for at least 10 min? (It should be 3-5 but who knows.) Are you soft-bricked in your current situation? If you start again, at "Install Stock Oreo:" does this at least restore your phone back to stock Oreo? If so, then try again and proceed with ALL the remaining steps again, CAREFULLY reading the instructions again & again.
Also, what phone model do you have? And I admit I haven't tested the CPU governors in the root script ; I ALWAYS chose none - I'll remove those options in the next version since I have tested them and there are plenty of CPU overclocking options once booted inside the ROM.
If you are able to restart this process and get stock Oreo back, AND chose NO CPU governors in the root script, maybe you want to either try "NO" to Google & Tmobile options just to make sure you can get Android booted- If it boots fine, then try the ROM again and pick Google and/or Tmobile to isolate any issues (things that are breaking)
Have you used ONLY what I provided, such as ODIN (version is important), etc?
Re Flashfire: Default options should be fine. The ROM script will set all the partitions, mounts, permissions, etc.
Good luck!
*Above response I guess is for overall troubleshooting the ROM, if any issues present themselves.
On another note: I'm actively working on this ROM as time allows. Trying to ease the install process, correct some issues, further customize, & improve...
Click to expand...
Click to collapse
So I did let it sit for a long time, maybe like 30 mins, but nothing happened. So I tried again from installing from stock and repeating each step. I'm using the odin files you supplied. Same thing. I was using install Google Apps and No T-mobile apps, and interactive governor for both situations. Stuck on boot animation screen. I did not try the options you suggested above since I eventually got it to work. So while stuck on the boot animation screen, I just ended up holding the Vol down, power and home until it rebooted and said entering recovery mode and let go before it went into download mode. From there I just wiped data, and cache, which may not be necessary, and then rebooted, and everything works. Thanks.
infamouz421 said:
So I did let it sit for a long time, maybe like 30 mins, but nothing happened. So I tried again from installing from stock and repeating each step. I'm using the odin files you supplied. Same thing. I was using install Google Apps and No T-mobile apps, and interactive governor for both situations. Stuck on boot animation screen. I did not try the options you suggested above since I eventually got it to work. So while stuck on the boot animation screen, I just ended up holding the Vol down, power and home until it rebooted and said entering recovery mode and let go before it went into download mode. From there I just wiped data, and cache, which may not be necessary, and then rebooted, and everything works. Thanks.
Click to expand...
Click to collapse
That's odd since the installer does exactly that. But I added this to the guide. Thanks for the feedback!
Thanks for the tutorial. Deeply appreciate the effort you put in foraging the resources and putting all the pieces together. The rom works great and all but I can't seem to get the lockscreen to display the wallpaper. It's just black lol. The adaptive clock works however. Would be grateful if you could drop a fix for this.
Alkan3 said:
Thanks for the tutorial. Deeply appreciate the effort you put in foraging the resources and putting all the pieces together. The rom works great and all but I can't seem to get the lockscreen to display the wallpaper. It's just black lol. The adaptive clock works however. Would be grateful if you could drop a fix for this.
Click to expand...
Click to collapse
(Not sure why I didn't get an email from XDA for this post.) Mind walking me through the exact place this setting is? Here? PhoneSettings->Lock screen and security->Clock and Facewidgets->Clock Style->Select a style for "Lock screen" tab at top->Done? (Im able to get these to work)
BTW, Im glad you found this thread resourceful! & Im working on another one, which will be better & more original. Takes a TON of time!
Hey i have two questions, if i'm on oreo already do i need to flash base? And, does this need an unlocked bootloader?
nam2amna said:
Hey i have two questions, if i'm on oreo already do i need to flash base? And, does this need an unlocked bootloader?
Click to expand...
Click to collapse
Your stock oreo should work without issues but I always flash his stock firmware just in case(it's smoother too I think). And no, it doesnt require an unlocked bootloader.
Oh and happy modding
Alkan3 said:
Your stock oreo should work without issues but I always flash his stock firmware just in case(it's smoother too I think). And no, it doesnt require an unlocked bootloader.
Oh and happy modding
Click to expand...
Click to collapse
There are a couple ways an installer can work for custom rom mods like this: start with base then remove everything we don't want. OR: delete everything then add in what we want. This rom happens to work with the latter method. You can see why the base would be so important with the first method. (Because if we don't start with a given base then we can't predict the results because we don't know what u froze or deleted). Regardless, for expected & reliable results, I would always start with an Odin flash of stock for a rom like this. Roms like this are different than vanilla AOSPs because we strip what Samsung & tmobile brewed up, and we often then refer to it as a hybrid- as opposed to vanilla aosp which would be google only & only Samsung for drivers, etc. Hope that helps.
Btw I'm working on another rom with tmobile wifi calling working. I had to start from scratch, literally to get it working. Btw I'm curious if anyone else got it to work after the fact with a custom rom. If so, PLEASE chime in & let me know. Thanks!
Deleted by MarvinMod
Do I needed to format data for this?
Can you install viper4android from xda labs on stock android 10 with magisk.
Install viper4android, reboot and recheck magisk to see if it still works.
Cuz for Android 9, the moment I install any magisk modules and reboot, the magisk breaks and I have only partial root access ( root access given to apps before still works but access to newer apps doesn't)
Also what do you mean by open stock recovery folder? You mean stock rom we download from samfirm
JakunTech1010 said:
Do I needed to format data for this?
Click to expand...
Click to collapse
yes, follow instructions exactly as written
fizzingbees said:
Can you install viper4android from xda labs on stock android 10 with magisk.
Install viper4android, reboot and recheck magisk to see if it still works.
Cuz for Android 9, the moment I install any magisk modules and reboot, the magisk breaks and I have only partial root access ( root access given to apps before still works but access to newer apps doesn't)
Also what do you mean by open stock recovery folder? You mean stock rom we download from samfirm
Click to expand...
Click to collapse
yes, when you download the stock rom from samfirm, it becomes a folder with your stock .tar.md5 files inside, that's your stock rom folder I speak of. I do not know if it works for 9. give it a try and let us know. I have 10 and once you update, you cant downgrade due to samsungs fuse set.
FYI, you can remove the .md5 from the stock rom files for faster loading but odin wont check the integrity of the file.
also, did you know that viper is Los based? other custom roms base off of Los so just replace Los in the guide with the rom of your choice. should work but I don't know, I only stick with Los or Stock.
A705MN
good morning friend I did all the steps you told me and it remains in the lineage logo I believe that the Roms you sent me is from an A705FN and my model is an A705MN that is why it does not configure because it stays in the logo and then it restarts me in twrp
jalexis30 said:
good morning friend I did all the steps you told me and it remains in the lineage logo I believe that the Roms you sent me is from an A705FN and my model is an A705MN that is why it does not configure because it stays in the logo and then it restarts me in twrp
Click to expand...
Click to collapse
my model is a705mn as it says in my signature below, your missing a step somewhere, did you format data properly? I flashed my device while writing the steps then again following the steps. also, I didn't post any stock roms and the los rom works with all a70 devices.
in twrp click wipe, then click format data and type yes and hit enter or the check on the keyboard.
when installing los, step 7 requires format data and step 9 requires format data so in the Los guide there will me format data done twice. these steps are for android 10 users, I have a guide for android 9 users that im transferring here but it will be some time. if your on android 9, pm me and ill link that guide to you, otherwise, try that format data or start from scratch by flashing the entire stock rom.
A705MN
sorry excuse my friend so much but in the step of formatting what should I do or could you give me the steps to follow and sorry for so much inconvenience
---------- Post added at 06:44 PM ---------- Previous post was at 06:36 PM ----------
friend and i'm in stock roms android 9 it will be that is why you don't configure the lineage it will be that you send me the android 9 guide
jalexis30 said:
sorry excuse my friend so much but in the step of formatting what should I do or could you give me the steps to follow and sorry for so much inconvenience
---------- Post added at 06:44 PM ---------- Previous post was at 06:36 PM ----------
friend and i'm in stock roms android 9 it will be that is why you don't configure the lineage it will be that you send me the android 9 guide
Click to expand...
Click to collapse
as long as you haven't done anything else trying to get it running(if you have, start from scratch by flahing the entire stock rom using odin) otherwise, boot to twrp, click wipe, click format data, type yes and hit the check box in lower right corner, reboot.
if your on 9, use this guide, its a bit outdated but as I said im working on it.
https://forum.xda-developers.com/showpost.php?p=81649149&postcount=151
also, what are you wanting, lineage os or stock os?
A705MN
friend thank you very much and I was able to install everything thank you very much for your contribution and time really that this xda group is the best there are many thanks
MarvinMod said:
yes, when you download the stock rom from samfirm, it becomes a folder with your stock .tar.md5 files inside, that's your stock rom folder I speak of. I do not know if it works for 9. give it a try and let us know. I have 10 and once you update, you cant downgrade due to samsungs fuse set.
FYI, you can remove the .md5 from the stock rom files for faster loading but odin wont check the integrity of the file.
also, did you know that viper is Los based? other custom roms base off of Los so just replace Los in the guide with the rom of your choice. should work but I don't know, I only stick with Los or Stock.
Click to expand...
Click to collapse
Viper4android is not a rom
It's a sound driver
It's magisk module.
What I meant is can you install this magisk model or download viper4android v2.7.6.1 from xda labs, install, reboot and check if magisk is still functional on stock Samsung Android 10 rom.
Also isn't android 10 and android 9 bootloader of Samsung rom same... V5 bootloader? Why would it mess with downgrading.?
fizzingbees said:
Viper4android is not a rom
It's a sound driver
It's magisk module.
What I meant is can you install this magisk model or download viper4android v2.7.6.1 from xda labs, install, reboot and check if magisk is still functional on stock Samsung Android 10 rom.
Also isn't android 10 and android 9 bootloader of Samsung rom same... V5 bootloader? Why would it mess with downgrading.?
Click to expand...
Click to collapse
Just assumed it was a rom, my apologies. I will check that for you when i have time but ive tested many modules with magisk and they work as well as magisk. Android 10 was an overhaul, not the same rom as 9 but still V5, however, thats not really the issue other then for twrp. Samsung devices has a fuse set, when a samsung devices bootloader is upgraded, the device trips or as we say "burns" out a fuse. The device can not be downgraded. After an update from 9 to 10, if you power off, hold both vol keys and plug into pc, in download mode at the top will tell you if a fuse has been triggered and provisioned. This means you cant go from 10 back to 9.
MarvinMod said:
Just assumed it was a rom, my apologies. I will check that for you when i have time but ive tested many modules with magisk and they work as well as magisk. Android 10 was an overhaul, not the same rom as 9 but still V5, however, thats not really the issue other then for twrp. Samsung devices has a fuse set, when a samsung devices bootloader is upgraded, the device trips or as we say "burns" out a fuse. The device can not be downgraded. After an update from 9 to 10, if you power off, hold both vol keys and plug into pc, in download mode at the top will tell you if a fuse has been triggered and provisioned. This means you cant go from 10 back to 9.
Click to expand...
Click to collapse
Thank you. Please do report back with viper4android. It's proper working with magisk is critical for me.
I understand your explanation about e-fuse.
But then that last android 10 upgrade that had this charging pcb issue, people did downgraded back successfully to Android 9 then.
How did they do that if e-fuse got triggered?
Lets leave this argument here.
I don't want to sidetrack you from your twrp and root work for Android 10.
Please tell me how to delete img files from the AP file
Or do I just need to replace img files with lz.4 files
fizzingbees said:
Thank you. Please do report back with viper4android. It's proper working with magisk is critical for me.
I understand your explanation about e-fuse.
But then that last android 10 upgrade that had this charging pcb issue, people did downgraded back successfully to Android 9 then.
How did they do that if e-fuse got triggered?
Lets leave this argument here.
I don't want to sidetrack you from your twrp and root work for Android 10.
Click to expand...
Click to collapse
No one with a galaxy A70 has updated to Android 10 stock and then went back to Android 9 stock. Viper worked fine and i kept root.
kissa67zwi said:
Please tell me how to delete img files from the AP file
Or do I just need to replace img files with lz.4 files
Click to expand...
Click to collapse
Extract the contents of AP file using peazip into a new folder on your desktop. Name the folder AP. Inside the new folder will be the files you need to delete or move out depending on what guide you following. When youve made the necessary changes, repack that new folder with peazip into a .TAR and now its flashable. Do not worry about the .lz4 extension. To delete, as long as its not zipped, right click the file, choose delete. To move the file, right click and hold, drag and drop to wherever and choose move here.
Fyi everyone, ill be making some youtube videos of the instructions for newbies by end of the week. It will have start to finish including bootloader unlock.
MarvinMod said:
Fyi everyone, ill be making some youtube videos of the instructions for newbies by end of the week. It will have start to finish including bootloader unlock.
Click to expand...
Click to collapse
That would be helpful for lot.
Kindly do link your videos here for us when they get uploaded
---------- Post added at 03:31 PM ---------- Previous post was at 03:31 PM ----------
MarvinMod said:
No one with a galaxy A70 has updated to Android 10 stock and then went back to Android 9 stock. Viper worked fine and i kept root.
Click to expand...
Click to collapse
Good to hear.
Thanks for trying and reporting back
According to your instructions, I will be able to use tvrp on the Android 10 stock?Rооt is a worker?
naruba said:
According to your instructions, I will be able to use tvrp on the Android 10 stock?Rооt is a worker?
Click to expand...
Click to collapse
no,youll be using twrp to root stock 10 this method allows you to keep root and use modules. twrp does not work with android 10 stock due to some changes in 10. it does however work with custom roms. you can either have twrp, custom rom and magisk root or have stock rom and magisk root.