This method creates the ability to debloat the Verizon GS7 (non-Edge Snapdragon) by modifying @jrkruse's method for the S7 edge posted here. Huge thanks to jrkruse for making the GS7 what it should be without massive bloat.
After my OP, he and @CVertigo1 evolved the method to fix the safetynet fail issues, so it now should work perfectly. I personally have not yet tried the updated method but will do so tomorrow. I'm copying instructions from the CVertigo1 thread here, but also keeping the old instructions below in post 1.
Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay.
New CVertigo1 method:
CVertigo1 said:
Yet again, all thanks go to @jrkruse for this one. I have modified his zip to work on the Verizon S7 flat. The ROM is silky smooth since it uses the factory kernel. I'm going to tweak his instructions to work for the flat. I can confirm that SafetyNet passes using this method.
Download
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
S7_SU_2_79_Root_Unroot_WO_Tweaks.zip
VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip
Install Instructions From Any Build
Warning: This will wipe your device. Some of these instructions are redundant, but they will ensure that everything goes as planned. If you don't follow them to the T, don't complain.
1) Unzip Odin and the firmware bundle zips. Boot the phone into download mode and flash the G930T BL, AP, and CP files in Odin.
2) Don't bother logging into any accounts, as the phone will get wiped again. Copy the FlashFire.apk and VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip to your SD card.
3) Shut off the phone and boot into download mode (volume down, home, and power). Flash the S7 Nougat root kernel in the AP slot in Odin. This file was in the firmware bundle.
4) When the phone reboots, unlock developer options and enable USB debugging. Unzip the S7_SU_2_79_Root_Unroot_WO_Tweaks.zip and run root.bat from your PC.
5) Now install FlashFire. Go into FlashFire settings and click option to allow flashing Bootloaders.
6) Now click flash firmware and chose AP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT_meta.tar.md5 SELECT ALL OF THE PARTIONS!!!
7) Now click install zip and choose VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip Make sure to click mount system when FlashFire asks. View attachment 4073928
VERY IMPORTANT NOTE: MAKE SURE TO UNCHECK INJECT ROOT AFTER ADDING THE ZIP!!!!!!!- Thanks @dclutter1
8) The phone will restart and FlashFire will flash the firmware first(it will take a couple minutes to find and flash everything), then the Aroma installer will start.
9) In Aroma, select wipe data(DO NOT KEEP SU)
10) The phone will say custom status on first boot, but it goes away after setup and reboot.
Click to expand...
Click to collapse
older method just for the record
Here is an OLDER METHOD with ADB install
Download stuff:
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
ROM: There are two basic options to choose from:
PlayStore Rom - so called because it has almost NO apps and you download what you want from the PlayStore. Has an experience very similar to the Pixel.
Hybrid ROM - close to Samsung Stock experience by massively debloated
Method:
Reboot phone to recovery wipe data
Reboot to bootloader
In odin flash:
In BL slot: BL_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT.tar.md5
In AP slot: AP_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT_meta.tar.md5
In CP slot: CP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT.tar.md5
Leave CSC slot Blank
Go through setup don't add any accounts your going to wipe again when finished reboot back to bootloader
In odin Flash Engineering Boot.img from above (in AP slot)
When phone reboots and computer reconnects to phone Open HYBRID_PLAYSTORE_ROM.zip folder
Click Verizon_TMO_PlayStore_Install.bat
When done click press to continue the phone will reboot back to download mode
In odin flash:
In CSC slot: CSC_VZW_G930VVZW4BQA2_CL10280325_QB12417265_REV02_user_low_ship_MULTI_CERT.tar.md5
In AP slot: G930TUVU4BQB1_Boot_Recovery_Image.tar.md5.tar
Phone will reboot to recovery and fail
In Recovery click Mount System
Wipe data
Reboot phone
During Boot Phone will Say Custom Status this will change after phone is setup and a reboot is performed
Once through setup open Rom Control App
Navigate to Phone and Settings
Click on IMS Settings
Choose Ims service switch
Click on MMTEL switch
Click on RCS switch
Under MMTEL section I enabled all the options
Click Back Button until your back to Phone and Settings Menu in Rom Control
Choose Activate Advanced Calling
Make sure under Advanced Calling that HD and Video calls are enabled
Activate WifiCalling
Known issues:
Safety net check fails (so Venmo does not work)
Some sites are blocked. Turning on "data saver" in Chrome settings worked for me but not everyone
I found that I had to go into settings > applications > phone and explicitly choose the phone as my default application for calls before it would correctly create a notification when the phone rang.
Some slightly more varsity moves:
Keeping apps from your stock:
You can modify the .bat file to not remove any apps you want to keep.
For example, I wanted to keep the "always on" display, so I deleted these lines from the .bat file:
Code:
adb shell rm -r /system/priv-app/AODService_v20
You can also further delete apps. Essentially during steps 5 - 7 above, the phone is rooted. During that time you can remove other packages. (My advice would be to pull them to your computer so you can push them back if needed)
For instance, I wanted to remove Hangouts, the AOSP browser (I use Chrome) and VisualVoiceMail. So I repeated step 5, then did:
Code:
adb root
adb remount
adb pull /system/app/VisualVoicemail
adb shell rm -r /system/app/VisualVoicemail
adb reboot bootloader
Then repeat steps 9 - 11
Wipe CACHE, (NOT data)
Reboot
Cool, cant wait to walk a friend thru this.
Just got up and running on PlayStore, everything seems good except I can't get the call recording to work. Thanks for putting this together
Sent from my SM-G935V using Tapatalk
JPSloan1 said:
...
7. Click Verizon_TMO_PlayStore_Install.bat.
...
Click to expand...
Click to collapse
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.
thrillerbee said:
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.
Click to expand...
Click to collapse
Yes It appears he updated his method to one that uses a different kind of temporary root as well as flashable files. I'll have to look at it and see if it's customizable the way the other one was, but it looks like you found the correct playstore ROM zip from before. Here is the other ROM. Sorry for the confusion.
Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,
if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.
t1231 said:
Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,
Click to expand...
Click to collapse
I tried but the .zip kept failing so maybe I didn't create it right.... So ultimately I did not bother and my service seems just fine at the moment.
Hobson318 said:
if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.
Click to expand...
Click to collapse
I think that would work (and wouldn't think you need to bother with the engineering bootloader steps either then) but to be honest it might be safer to ask jrkruse, because I don't deeply understand it - really just adapted his method for the S7 flat.
You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.
S3NTYN3L said:
You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.
Click to expand...
Click to collapse
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.
JPSloan1 said:
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.
Click to expand...
Click to collapse
Step 10.
Hmm, It seems that I wasn't holding the buttons down long enough.
If DL = Damn Long, then, yes, I agree.
OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.
S3NTYN3L said:
OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.
Click to expand...
Click to collapse
If ROM control didn't install manually it's because the .bat file didn't execute correctly. Did you modify it? Did it successfully acquire root and execute all the commands all the way through to the "click to continue" prompt? OR did it give error messages along the way? (There will be a few during the remove steps because it's removing packages that only exist on the S7 edge, not flat.
I would try it again if you have the patience.
I didn't modify anything.
I only recall a few minor errors regarding removal of non-existent directories.
Yes, the script went through to the end.
Yes, the phone had root and the TMobile rom wouldn't let me forget it, lol.
It kept complaining the whole way through.
JPSloan1 said:
Basically this method temporarily roots the phone to modify the packages installed, removes a ton of them, and then reverts. So with this method, Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay
Click to expand...
Click to collapse
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.
CVertigo1 said:
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.
Click to expand...
Click to collapse
Yeah attached. I think I also have this problem as do those in the other thread, and that's why I get an error on device check with Venmo.
I thought you posted that Samsung Pay worked for you in the OP.
CVertigo1 said:
I thought you posted that Samsung Pay worked for you in the OP.
Click to expand...
Click to collapse
I followed the method in the OP, installed Play Store version. Samsung Pay is working for me.
Sent from my SM-G935V using Tapatalk
Related
*I TAKE NO CREDIT FOR ANY OF THIS, IM JUST TELLING HOW I DID IT. I AM ALSO NOT GUARANTEING YOU WILL HAVE THE SAME OUTCOME*
*I recommend going to this new update guide by CVertigo1 in the ROM's section as this version of the PlayStore ROM is outdated.*
Credit for Root and PlayStore Rom goes to jrkruse (https://forum.xda-developers.com/member.php?u=1949695)
ROOTING
1)Flashed stock Nougat ROM
2)Flashed ENG-ROOT found here https://www.androidfilehost.com/?fid=457095661767141717
- Make sure to flash the correct kernel included in the zip file
3) Install SuperSU. Link: https://www.androidfilehost.com/?fid=529152257862710010
- I used the regular Root.bat not the one with tweaks
FIXING LAG
1)Install Flashfire from PlayStore
2)Download the PlayStore Rom from https://www.androidfilehost.com/?fid=457095661767144652
-Transfer the file to the S7
3)Open Flashfire and flash the zip choosing only Mount/ system read/write
4)Now AROMA Installer will pop up and go through all of the terms and conditions
-When asked what to wipe I choose to wipe everything
-Next when asked what bloat to remove I choose the PlayStore Rom which removes all bloat and replaces stock apps with google apps (To see full list of changes refer to the PlayStore thread)
5)Now when my S7 boot it showed no launcher, I simply held the home button down which opened the google search, in there I searched for the playstore app and installed Nova Launcher.
-Now reinstall SuperSU by double clicking the root.bat like before
6) Installed the following apps to help with lag; Lspeed, Greenify, Kernal Auditor, LeanDroid, Force Doze, and SSD Boost
-I used most of the settings found on Lag fix threads for the MM root
My S7 is smooth as butter after all of this, no lag spikes and random crashes like I was experiencing with just the ENG Root flashed.
EXTRA
1)I did have to to a reboot to get the camera to work properly
2) I had to download a Dialer/Contacts and Message app from the playstore because the stock ones were deleted in this process. But the store ones work just fine, I am recieving calls and messages like normal.
3) *Battery life is just a little worse than stock, might be worth waiting for Xposed to released for Nougat.*
Credit for Root and PlayStore Rom goes to jrkruse (https://forum.xda-developers.com/member.php?u=1949695) :good:
setup wizard keeps stopping...
I have followed your step with my phone (Galaxy S7 Verizon - Android 7), but when go to step no 5 my phone always alert (The process com.android.phone has stopped, Setup Wizard keep stopping...). I tried to hold HOME button but still nothing and message always alert even reboot phone.
Please help. thank in advance
Bunrin said:
I have followed your step with my phone (Galaxy S7 Verizon - Android 7), but when go to step no 5 my phone always alert (The process com.android.phone has stopped, Setup Wizard keep stopping...). I tried to hold HOME button but still nothing and message always alert even reboot phone.
Please help. thank in advance
Click to expand...
Click to collapse
Weird, did you wipe your S7 completely before doing the process? I would flash fresh nougat and try again.
UPDATE
Went through the entire process once more and found that wiping but keeping SU image works the best, I chose "no wipe" but it caused random reboots. I then wiped my phone and did as stated in my original post and it is working smooth once again.
ikoyhn said:
Weird, did you wipe your S7 completely before doing the process? I would flash fresh nougat and try again.
Click to expand...
Click to collapse
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Bunrin said:
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Click to expand...
Click to collapse
The rom is for Verizon and T mobile devices. Your good to go.
Blade22222 said:
The rom is for Verizon and T mobile devices. Your good to go.
Click to expand...
Click to collapse
Bunrin said:
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Click to expand...
Click to collapse
Yup it says G935 but it also works with the G930.
ikoyhn said:
Yup it says G935 but it also works with the G930.
Click to expand...
Click to collapse
When install finish after reboot my phone show "Setup Failed....". any ideas. thanks
Bunrin said:
When install finish after reboot my phone show "Setup Failed....". any ideas. thanks
Click to expand...
Click to collapse
Did you start on a factory fresh Nougat? It must be trying to run the setup that you first have to do when you get/wipe your phone. But you should have already done this prior IF you wiped your phone completely and started from there.
Here is another guide that you might find helpful: https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124
ikoyhn said:
Did you start on a factory fresh Nougat? It must be trying to run the setup that you first have to do when you get/wipe your phone. But you should have already done this prior IF you wiped your phone completely and started from there.
Here is another guide that you might find helpful: https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124
Click to expand...
Click to collapse
Thanks for your support.
Is this for the Qualcomm processor?
Gon Rouge said:
Is this for the Qualcomm processor?
Click to expand...
Click to collapse
Yes the *US*S7 does have the Qualcomm processor, and this ROM does work with it. If you are looking to see if it will work for another device with the processor then I recommend looking here: https://forum.xda-developers.com/member.php?u=1949695, for more information on the ROM and compatibility.
ikoyhn said:
Yes the S7 does have the Qualcomm processor, and this ROM does work with it. If you are looking to see if it will work for another device with the processor then I recommend looking here: https://forum.xda-developers.com/member.php?u=1949695, for more information on the ROM and compatibility.
Click to expand...
Click to collapse
Not all s7s are Qualcomm, we sometimes get international users in here.
Blade22222 said:
Not all s7s are Qualcomm, we sometimes get international users in here.
Click to expand...
Click to collapse
Whoops forgot about that, I fixed my reply. Thanks for pointing it out:good:
My phone is now stuck on the boot text (Samsung Galaxy S7) have yet to see past it.
IDCM said:
My phone is now stuck on the boot text (Samsung Galaxy S7) have yet to see past it.
Click to expand...
Click to collapse
-After what step did it get stuck on the boot text?
-Did you start factory fresh?
ikoyhn said:
-After what step did it get stuck on the boot text?
-Did you start factory fresh?
Click to expand...
Click to collapse
I've got it all in working order, but to address the issue.
It was just straight after using the first Odin file. (Flashed ENG-ROOT)
Although with hours of sitting here and determination, I came to a solution using this post and many others.
I now have my S7 (Verizon) rooted and functioning with no issues.
Thank you for sharing. :highfive: :good:
IDCM said:
I've got it all in working order, but to address the issue.
It was just straight after using the first Odin file. (Flashed ENG-ROOT)
Although with hours of sitting here and determination, I came to a solution using this post and many others.
I now have my S7 (Verizon) rooted and functioning with no issues.
Thank you for sharing. :highfive: :good:
Click to expand...
Click to collapse
Glad you got it all sorted out:good:
I haven't rooted a phone in a few years but I feel like I missed a fundamental step of the root process so I have a stupid question: I get to the rom flashing step and my phone can't reboot because "Custom binary locked by SECURE BOOT (boot.img)." Then I reflash the ENG-ROOT boot.img and that same secure boot blocks because of the custom modem binary. So I just reflashed stock to get it working again, but it still gives that message if I try to install something like magisk. Am I missing something?
fjgrf said:
I haven't rooted a phone in a few years but I feel like I missed a fundamental step of the root process so I have a stupid question: I get to the rom flashing step and my phone can't reboot because "Custom binary locked by SECURE BOOT (boot.img)." Then I reflash the ENG-ROOT boot.img and that same secure boot blocks because of the custom modem binary. So I just reflashed stock to get it working again, but it still gives that message if I try to install something like magisk. Am I missing something?
Click to expand...
Click to collapse
You cannot use any custom kernels on us snapdragon models. No magisk or anything. The only root option is engboot and root.bat plus the setups to smooth it out or no root at all
I'm really hoping someone can bail me out here before I...
I have made a mess of my new (to me) Note 4. I bought it as an Unlocked GSM. It arrived booting with a Sprint screen. I have Safelink BYOP service. When I switched from my Note2 to Note4, yesterday, an ATnT sim card was used to activate it with Tracfone. Everything seemed to work EXCEPT for MMS - I could not send nor receive pictures. I read -what I thought was- clear instructions here on the forum, I started downloading and attempting to root my phone, hoping that would solve the problem, since tech support had no answers.
I followed the instructions in this post - https://forum.xda-developers.com/note-4-sprint/help/rooting-sprint-note-4-pj1-t3495306 . Now the phone will only boot to download mode, or I can use the up volume button to get to the program to install, restore, etc. I have tried several times - with a couple of different .tar files. This last attempt - I tried to restore it - that also failed. My old eyes can not really see the tiny text but I did see in Odin3 that 1) No MDS found 2) Systemless mode Boot img support required 3) Boot Image Patcher Failed. When I attempt to install the SuperSU, from the thread, it gives me similar errors 1) NO MDS file found 2) (under Boot Image patcher it says FAILURE / Abort after extracting Ramdisk.
If anyone could help me out, I would be most grateful.
JadenEllis said:
I'm really hoping someone can bail me out here before I...
Click to expand...
Click to collapse
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Once you get phone back on stock. I'll show how to root!
Thank You
Thank you so much for the reply. I have downloaded the files you put in my post. I will attempt to do these things now, but I have a question. I stayed up fighting with the phone all night. I probably did some things I shouldn't have? I realized that I was getting stupid and quit, but I did (maybe) put some other stuff on the phone that night. Should I use the Clean or wipe function in TWRP before I do anything else???
Yes, I can boot to downloader or to TWRP. The phone (on its own) is now stuck trying to load with the Note 4 splash screen - but I can boot to either with the vol +/- buttons.
SamFirm did not work. It said Unable to fetch... please check data or enter manually.
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
First - THANK YOU all for the assistance.
Yesterday, none of the suggestions were working, but I kept at it. I was finally able to install the most current Stock tar that I could find. This phone had updated to the most current version available for the phone - it had Marshmallow 6.01. NOW, the red and yellow tamper errors appear to be gone from the Note4 splash screen - BUT, it boots to Sprint Activation so it won't fully load to OS. I read a post about removing the Sprint Hands Free Activation, but it gives two ways of doing so. 1 requires having a rooted phone (I am assuming it is not rooted now?) and the other uses ADN Connect, and I am not sure what that is.
I'm not really sure what to do from here? Any assistance appreciated. Can I start from step 1 of the original post to install SuperSU now?
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Well, the sun is about to come up - again - but I think I got it! This has been a learning experience to say the least. I wasn't really planning a crash course in Android, but thank you to all who responded. And to :Samep too!
I think I get it
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
JadenEllis said:
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
Click to expand...
Click to collapse
Sorry bud. I'm so busy. Haven't been online since i message you. Glad you got it.
Rookie messed up..
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
meBn360 said:
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
Click to expand...
Click to collapse
Sorry I don't get on here much lately. Just seen your post.
Without knowing exactly what you did. I'd say you lost your unlock. If you had an unlocked sprint phone. And tried nougat. I believe i remember that upgrading to nougat was messing up people's EFS partition. And that's where the unlock happens. Did you make a backup?
I always tell everyone, the most important thing you can do is have a full working backup of every partition.
Hope that sheds some light
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Have you tried flashing back to stock and seeing if that fixed these issues?
Pal Guite said:
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Click to expand...
Click to collapse
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
gman88667733 said:
Have you tried flashing back to stock and seeing if that fixed these issues?
Click to expand...
Click to collapse
Thanks. But i don't have the stock rom. I didn't intend to use a custom rom. I tried to root it to recover some deleted photos and the moron that i am, i didn't back up the stock firmwares and while tweaking around in the recovery i somehow deleted the stock rom. This is my 1st time...
DroneDoom said:
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Pal Guite said:
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Click to expand...
Click to collapse
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
DroneDoom said:
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
Click to expand...
Click to collapse
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Pal Guite said:
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Click to expand...
Click to collapse
If your on xda with your browser, it's the paperclip icon to attach files. If you are using a 3rd party app that wraps xda into it then I can't help you there. As for going back to stock, Motorola made things a little critical when they released Nougat. Depending on how far you were on keeping the device up to date through stock, flashing the available stock images (which aren't signed) could brick the device if you aren't careful. There use to be an account on androidfilehost that uploaded current stock packages but it seems they're all gone now. If you remember the build number of the device before you rooted, that will help in picking the right stock files. I've taken a break in keeping my device rooted so I haven't kept track of the resources used to help go back to stock but they're in the MZP guide threads.
EDIT: a word of caution when reverting to stock:
-Don't use flash tools that don't let you see/edit the fastboot commands
-Do not use commands that touch modem/radio or gpt partitions
Found an upload of the latest build release keep it around when you figure out what you need to flash. It's best to clear system, data, and cache before flashing. Also have a rom (and twrp) at hand to adb sideload in case stock doesn't boot.
https://androidfilehost.com/?a=show&w=files&flid=215703
This Android version 7.1.1
Security patch: Sept 2017
Build number: NPN26.118-22-2
Thanks alot... ?
This is NOT my work (Ianmacd) and guide is written by Mr Pickles all credits to him for his install method.
Also this is just a copy and paste but the guide is well written and TWRP should cause less issues.
I'm sure Gieti94 is just perhaps busy with other commitments, credit also to him for his fantastic efforts.
Just a new space for the currently working TWRP so all don't get in a pickle.
----------------------------
Download Maintained By Pickles (best all in one convenient place) will have everything necessary for twrp functionality. Credit to pickles.....:good:
http://bit.ly/2VlcqYd
Excellent installation Guide below
Install Guide
---------------------------
- NOT A SINGLE STEP IS UNNESSECARY
- DO THEM _ALL_ EXACTLY!
- ALL YOUR DATA WILL BE GONE - BACKUP!
---------------------------------------
DO NOT INSTALL MODPACK FROM SOLDIER - IT BREAKS TWRP!
---------------------------------------
If you have any problems - contact @PiCkLeS or on Telegram by PiCkLeS or @rp4k
---------------------------------------
All development is by @ianmacd (Ian Macdonald).
---------------------------------------
0 - No matter what you have today, no root or Magisk-only solution or TWRP with Magisk-solution, do ALL the steps..
1 - Make sure you copy the "Magisk_Manager_Ian_install.apk" file and "Multidisabler-g97x_by_Ian.zip" file to your sd-card before you start!
2 - Download latest firmware via Samfirm or Frija or in any way you can, and unpack.
3 - Boot your phone to Download mode (Power+Bixby+VolDown) and remember to have the USB connected to your computer, it won't boot to DL-mode otherwise
4 - Keep autoboot etc in Odin settings, put each file in its place (AP, BL, CSC etc) and _dont_ use HOME_CSC, use CSC-only-file.
5 - After Odin is done, your phone will reboot automatically - let it! It can feel like forever, but let it do its restarts and stuff until you are in system-setup
6 - Do the setup as per usual, CONNECT TO WIFI but you can safely just say Skip on sign in and other stuff
7 - When setup says its all finished and you get to the standard launcher - go into Settings and enable Developer settings
8 - This step IS necessary.. If you don't do this step, you might get in pre-normal rrm state and you will have wait 7 days to try again: Enter Developer settings and look for the "OEM Unlock" switch - if you are rooting for the first time, Enable it. If you already have root since before or unlocked your bootloiader before, just confirm that its Enabled and graded out.
9 - If you already have an unlocked bootloader, skip to step 12. If not, continue with step 10.
10 - IF you never have unlocked your bootloader before, Power off the phone and boot into download mode again. You will see the long press volUp option for unlock bl, do that.
11 - IF you never have unlocked OEM before, boot the phone again, do the setup without signing in etc but connect to wifi, enable dev settings, go into dev settings and check that OEM now is enabled and grayed out.
12 - Reboot the phone in recovery mode (Power+Bixby+VolUp and keep holding until you are in stock recovery. Choose and do a factory reset.
13 - Reboot to bootloader with option in Recovery.
14 - Flash the tar you got (S10x-TWRP+Magisk_fixed_by_Ian.tar I Odin in the AP-slot. DISABLE auto reboot in Odin first!
15 - When the tar has flashed - Do as instructed on the phone, hold Power+VolDown for a few seconds and AS SOON AS THE SCREEN GOES BLACK -> quickly press power+bixby+volUp for a _long_ time, and I mean it can feel as if its a full minute! After a while you will see TWRP starting with its start screen, you can now let go and enter TWRP.
16 - FORMAT data, then WIPE data AND Cache. DO NOT LET IT REBOOT
17 - Flash "Multidisabler-g97x_by_Ian.zip" from SD card
18 - Go back to start screen of TWRP, Choose Reboot, Choose Recovery - YOU MUST ALWAYS CHOOSE REBOOT TO RECOVERY and _NOT_ system!
19 - Let the phone reboot into system, it will do some reboots it self, and again it will feel like it takes FOREVER - Just let it do its thing and DO NOT PRESS ANY KEYS!
20 - When your phone is finally done booting, just do the normal setup/signing for real this time.
21 - When you are done and in system/launcher, install "Magisk_Manager_Ian_install.apk" from SD card and verify that you now have Magisk Manager installed.
22 - Start Magisk Manager and say YES to what it says, it will do some stuff and then say "Rebooting in 5 seconds" - LET IT BOOT AND DO NOT TOUCH ANY KEYS this time either..
23 - Now when booted to system, start Magisk Manager and see that you have all green and its installed.
24 - Now you have root.
** Every time you reboot manually, be prepared to hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and let it reboot, you will have root.
** Every time you power off the phone, when you power ON again, hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and it will boot with root.
** Every time you want to enter TWRP-recovery, do as above but KEEP HOLDING THE KEYS UNTIL TWRP-start screen shows then release. Remember to choose reboot to recovery afterwards and you will boot with root.
** IF you screw up and forget or miss the key combo, just let it boot to system, immediately when system is up - reboot again and do the key combo and all is fine again.
This is me just trying to get an emergency first aid space, nothing more, I'm NOT trying to take any credits or dismiss Gieti94.
Thanks All
Duncan1982 said:
This is NOT my work (Ianmacd) and guide is written by rp4k all credits to him for his install method.
Click to expand...
Click to collapse
This is my tutorial and not r4pk. And I'd prefer that you use the download I provide here and no where else to make sure the right files gets downloaded when updated.
http://bit.ly/2VlcqYd
/P
Yea I can keep the OP updated, this is just an emergency first aid thread, thanks to Pickles for his well written guide.
I'm really not wanting to offend anyone, just for all to make life a bit easier....
very nice to have a reliable twrp solution, pitty that we don't have too many things to flash in recovery
Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P
I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
And yes I never said I wrote the guide I just added myself for helping people
rp4k said:
I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
Click to expand...
Click to collapse
I understand. But that doesn't seem to be a big problem for any one else and the bigger problem is that you risk having a link that is being used by the people only see it here and don't read anywhere else, or this message, and end up with old information or even worse, outdated files.
I can help you get the files on PM but please remove these links outside of my drive, which I maintain every day and keep up to date. It's not for vanity, it's for safety.
For now please edit your text and remove the link. All must use v1.1 of the multidisabler zip by Ian.
/P
Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.
Duncan1982 said:
Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.
Click to expand...
Click to collapse
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P
PiCkLeS said:
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P
Click to expand...
Click to collapse
I fully appreciate and understand that, the reason I created as I have plenty of time to maintain, and will keep it up to date I have been around for quite some time, if you look at my posts (search) I have had almost every device you can think of, currently have the Vivo IQOO also, I have enough experience to understand the important and implications.
I don't want your PM's to be going crazy so I'll fully respect your decisions and will keep everything updated also. But it is better if everything is tody and not one thing here and there, OP has been updated with your direct link, is this cool?
Just thought by creating this thread that it might help, my sincere and good intentions are hopefully evident
PiCkLeS said:
Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P
Click to expand...
Click to collapse
Can I install multi Disabler 1.1 withouth lost data?
zubi182 said:
Can I install multi Disabler 1.1 withouth lost data?
Click to expand...
Click to collapse
Yes just flash it in twrp, nothing will be lost.
/P
I assume this is only for the Exynos version? Or does it work for Snapdragon as well?
mistermidas said:
I assume this is only for the Exynos version? Or does it work for Snapdragon as well?
Click to expand...
Click to collapse
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk
rp4k said:
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk
Click to expand...
Click to collapse
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.
mistermidas said:
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.
Click to expand...
Click to collapse
Sorry I responded when I was half asleep. My fault.
I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?
mercifool said:
I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?
Click to expand...
Click to collapse
Yes, just do exactly all the steps and use the new files in the link and you will be fine.
//P
deleted
Carotix said:
hi ,
do you have the OEM switched to on?
if not , you need it ..... if you can't get it because you are waiting the 7 days , you can make this trick
open settings and set the date 8 days before ... then reboot
so you can enable OEM in developer settings
Click to expand...
Click to collapse
Hi there, are these instructions for Exynos only or can I apply it to Snapdragon as well, please advise. Thank!
Hi there,
I've combined some custom-kernel-like tweaks into a single flashable .tar file and I wanted to share it with you.
This .tar file contains:
-patched vbmeta image
-working magisk root with full Android 11 support
-magisk manager helper preinstalled
-a cleaned up boot screen + no bullsh*t on boot screen
-a cleaned up unlocked bootloader screen + no bullsh*t on unlocked bootloader screen
Prerequisites
-an unlocked bootloader
-firmware version CTL1 (A11)/BTJ3 (A10) or newer
-Odin 3.XX.X
-all data backed up
-fully functional brain
-stock recovery and firmware (this will not work if you have a custom recovery or run a custom rom)
STOCK BASED ROMS LIKE BEYONDROM WILL ALSO NOT WORK!
PLEASE NOTE:
-I am not responsible for a bricked device, please make backups and make sure to
always have the official firmware if something goes wrong
-flashing this requires you to factory reset your phone or else the phone won't boot
Instructions:
-unlock your phone's bootloader
-boot into download mode
-in Odin uncheck auto-reboot
-put the .tar file into the AP slot (If it doesn't work try USERDATA)
-after flashing boot into recovery with the key combination
-select factory reset and confirm (This will wipe everything from your phone)
-after factory reset reboot into system
-setup the phone and restore your backup (if you made one)
-Install Magisk and you're good!
If you have any problems
Please don't just comment "Doesn't work" and instead tell me about
the errors you encountered, your software info and other information
you think would be helpful.
Happy flashing!
If you still have questions make sure to ask them below
DOWNLOAD CTL1+: https://1drv.ms/u/s!AtNTTTF5vqOe73aVGDPSRGr5aria?e=dICFlS
DOWNLOAD BTJ3+: https://drive.google.com/file/d/1KqOGRbAy4fY1ghro4HoP-eDDYh4G7b5Z/view?usp=sharing
Tried it on my friend's phone,works great.Thanks
Can i flash it as my firmware version starts with QP1A.??(build number)..
Thanks in advance and cheers..
@[email protected] said:
Can i flash it as my firmware version starts with QP1A.??(build number)..
Thanks in advance and cheers..
Click to expand...
Click to collapse
This doesn't say anything. Can you tell me what custom ROM you are running? If you are on rooted stock also tell me.
Hi,yes,phone is rootedAndroid 10,,one Ui,v 2.1,build number QP1A 190711.020.G988BXXU1ATCT..
@[email protected] said:
Hi,yes,phone is rootedAndroid 10,,one Ui,v 2.1,build number QP1A 190711.020.G988BXXU1ATCT..
Click to expand...
Click to collapse
Geeeeeez! Update your phone! You have to have OneUI 2.5 BTJ3 or OneUI 3.0 CTL1 at least. What are you doing on 2.1? If you don't update, this will break your phone.
Okay buddy,ty..will do that.
Hi again m8,can i update Android 11,,One GUi 3.0,RP1A200720.012 G988B...
And ,or which file i have to use??
@[email protected] said:
And ,or which file i have to use??
Click to expand...
Click to collapse
Depends on the version. I don't want to be rude but how did you even manage to root your phone with this lack of knowledge?
If you update to Android 11/One UI 3.0 you chose the One UI 3.0 one. If you only update to 2.5 you chose 2.5. Remember to check the end of your firmware number:
There are supported firmware endings:
One UI 2.5:
-BTJ3
-BTJ4
One UI 3.0:
-CTL1
-CTL6
-Any One UI 3.0 firmware above that.
Download SM-G988B / Galaxy S20 Ultra 5G SM-G988B in Samfw - Samsung firmware download
Pick your CSC there, chose the newest one preferably (A11), press "Download on website", unzip it and flash it with Odin while in download mode. You should know how to do that.
After it's finished, complete setup (do not restore any backups yet!) and go into download mode again. Flash the file as AP or USERDATA (whatever works) and perform another factory reset. Done.
So i just reflashed stock because Beyond rom is givving me issues, says you removed all the BS from the boot screens but i still have that unlocked bootloader msg. i flashed in AP with no issues, that msg mean it didnt work?
BCityModz said:
So i just reflashed stock because Beyond rom is givving me issues, says you removed all the BS from the boot screens but i still have that unlocked bootloader msg. i flashed in AP with no issues, that msg mean it didnt work?
Click to expand...
Click to collapse
The unlackiert bootlaoder Massage Stars Tiere just wichtig Themen Bulletin
Edit: German Autocorrection sorry wait haha
JanBoyGamer23 said:
The unlackiert bootlaoder Massage Stars Tiere just wichtig Themen Bulletin
Edit: German Autocorrection sorry wait haha
Click to expand...
Click to collapse
Ok disabled the autocorrection. What I was trying to say is: The unlocked bootloader message is still there just without the bull**** about your phone being vulnerable to hackers and this other ****. It now just says that it is unlocked.
JanBoyGamer23 said:
Ok disabled the autocorrection. What I was trying to say is: The unlocked bootloader message is still there just without the bull**** about your phone being vulnerable to hackers and this other ****. It now just says that it is unlocked.
Click to expand...
Click to collapse
Ok sweet, so Im no pro at any of this but i know the basics to flash. and wasnt able to unlock my last phone because the unlock option never popped up in settings. but now my camera isnt working, i open it up and its just black, no errors or anything.
BCityModz said:
Ok sweet, so Im no pro at any of this but i know the basics to flash. and wasnt able to unlock my last phone because the unlock option never popped up in settings. but now my camera isnt working, i open it up and its just black, no errors or anything.
Click to expand...
Click to collapse
That can't be an issue with the script as it doesn't modify anything related to the camera
JanBoyGamer23 said:
That can't be an issue with the script as it doesn't modify anything related to the camera
Click to expand...
Click to collapse
Ok I may have to make a copy of my girls phone and flash original back to the phone and go again.
JanBoyGamer23 said:
That can't be an issue with the script as it doesn't modify anything related to the camera
Click to expand...
Click to collapse
yea IDK, did it all over again, even booting up to make sure the cam was working. same thing black screen when i open the camera app.
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
frostmore said:
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
Click to expand...
Click to collapse
Short answer: Yes
Long answer: You are unlocking your bootloader and flashing a custom image so you lose your warranty and trip knox
frostmore said:
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
Click to expand...
Click to collapse
If you want to use s health: Download build.prop editor, grant it root access and and change the value of 'ro.config.tima' from 1 to 0