Related
THIS IS FOR QUALCOMM SM-G935P
I saw that the original root thread was missing a few information on the first and second post, so I decided to still offer the same information, while making the entire root process easy to follow along. All work goes to those at the Samsung G935P Root Forum and @colormedroid .
The Files Needed Are:
Odin by Princecosmy: ODIN
G935A: Galaxy S7 Edge
SuperSU: SuperSU Root
Minimal ADB and Fastboot: XDA Forums
You will also need Package Disabler Pro for Samsung: Package Disabler Pro (Samsung) $0.99
I know it costs money, but it is worth it, especially on future devices that support Samsung Admin while waiting for root.
Make sure all files above are downloaded and ready to be accessed.
These steps are best done on a factory reset (can be found in FAQ #3) on PF2 update.
Step By Step Instructions
1. After downloading Package Disabler Pro and getting it set up, you'll need to disable three packages: samsung dm phone interface, samsung dm service, and securityLogAgent.
2. Turn off your phone and boot into Download/Bootloader mode by pressing and holding the Vol Down+Home+Power after your phone is off.
3. Plug Phone into Flash the G935A.TAR in ODIN under AP and your device should restart by itself.
4. Your phone should boot straight into Android. Most likely you will have no LTE. Do not worry, that is normal. Continue onto step 5.
5. Copy the files from SuperSU to the location of your Minimal ADB and Fastboot folder on the computer (Default is "C:\Program Files (x86)\Minimal ADB and Fastboot")then after you enable USB debugging in the Developer Options menu on your phone (If you don't have Developer Options in Settings, go to About Phone, and tap on Build Number 7 Times), Run the Root.Bat file from your Minimal ADB and Fastboot Folder.
6. Open Build.Prop with BuildProp Editor and change the following settings
ro.cdma.default_numeric=310000
Change the value to 310120
ro.cdma.default_alpha=Chameleon
Change "Chameleon" to Sprint
Edit*ro.build.characteristics=Chameleon
Change "Chameleon" to Sprint
After a reboot, you should be good to go and have LTE.
Any other questions, feel free to post to the thread and myself and other helpful members of the community can help!
FAQ
1. Download and install BusyBox on Rails and get it set up. After that's set up, open up SuperSU, go to settings, and under Security check Enable SU during boot. Next, download Kernel Toolkit and under CPU set the Big Cores Maximum Frequency to 2150 Mhz. Don't forget to apply to boot from the side menu.
2. I'm stuck on the LTE splash screen. What do I do?
A: Press and hold the Volume Down + Power button down until your phone restarts. You may have to Factory Reset your device if it stays stuck on the splash screen. Get the files from FAQ #3 to successfully reset. If you wish to Re-Root, activate device beforehand by doing the Device Setup or by going into Settings - Activate Device. After Activated, follow the step by step guide.
3. I'd like to unroot and return to factory stock. How would I go about this?
A: Download the factory firmware from HERE and extract the file. Once Extracted, open ODIN and load each file in their appropriate space (BL file to BL, AP file to AP, CP file to CP, and CSC file to CSC). Make sure your phone is in download/bootloader mode by holding the Vol Down+Home+Power after the phone is off. Click Start once in download/bootloader mode and you should be back to stock once your phone reboots.
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Once the edit is saved correctly, restart your phone.
Credit goes out to: @guaneet for this fix
More answers to FAQ's to come.
Thanks, this guide is a bit clearer for beginners like me
EDIT: I can't seem to find the Minimal ADB and Fastboot Folder, where is it? (solved)
EDIT2: Where do I find the root.bat file in my phone? (solved, I had to run it from the computer not the phone)
This doesn't trip Knox right? So if I root and decide to go back stock, Samsung pay should work right?
JG96EVO said:
This doesn't trip Knox right? So if I root and decide to go back stock, Samsung pay should work right?
Click to expand...
Click to collapse
Correct. It requires to be on unchanged software. When going on complete factory reset using ODIN, it reverts any and all software changes made.
That changing the thing to sprint an the numbers to 310120 does not work for me when i do that i get no data wel 3g an it comes in an out then goes to roaming..an i cant change apns an there r no sprint apns as well...not sure if anyone els is having that
donbudafuko said:
That changing the thing to sprint an the numbers to 310120 does not work for me when i do that i get no data wel 3g an it comes in an out then goes to roaming..an i cant change apns an there r no sprint apns as well...not sure if anyone els is having that
Click to expand...
Click to collapse
Did you let the phone set up once before rooting? Did you also go into mobile networks and change roaming settings to home only?
Edit: The setup to bring your phone to Sprint did work because Sprint does not allow (unless with MSL) editing of APNs. I also made an edit that changes ro.build.characteristics=Chameleon in Build.Prop to ro.build.characteristics=Sprint. Hopefully that helps as well.
So let me throw out some errors that happened with me with the solvencies so no one has to feel like an idiot like me...
1. If Odin throws an error on your pit it will look like its good to go. It is not. Let your phone setup and then reodin
2. After initializing the 3 you disabled, go to settings, activate device. Let it activate but do NOT press done or ok or restart or a winky face emoticon or anything... But the home button and disable that same three again. Reboot. If your device keeps trying to be crazy, pick yourself up and try again.
3. For the bad file... Enable USB debugging, install the and drivers and the such then... Plug your phone into your computer and agree to the popup on your phone. After you agree (You have to be down with MTP, you know me) run the bad file on your computer. It'll say stuff and take a couple of minutes. Let it run. After reboot, reboot again. Root achieved.
Thanks so much for your clarification OP, I would've loved to use this post when I did mine lol
NOTE: Your mileage may vary... I did the buildprop change from Chameleon and the 31000 change and it negated my service. I went and changed it back, restarted, re-enabled the 3, activated the device, homed out, re-disabled the 3 and restarted. My LTE is back up and running
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Even after making these changes and verifying, my WiFi credentials and still being erased.
Hardcorp said:
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Even after making these changes and verifying, my WiFi credentials and still being erased.
Click to expand...
Click to collapse
Verify your edit stuck. Make sure there is not any extra "space" in line or end of that line. Reboot.
xyameax said:
Did you let the phone set up once before rooting? Did you also go into mobile networks and change roaming settings to home only?
Edit: The setup to bring your phone to Sprint did work because Sprint does not allow (unless with MSL) editing of APNs. I also made an edit that changes ro.build.characteristics=Chameleon in Build.Prop to ro.build.characteristics=Sprint. Hopefully that helps as well.
Click to expand...
Click to collapse
Tryed that still the samething..really doesnt mayter thimo i have data an call service as is so um goid just wanting to let everyine els know it might not work
LeftyGR said:
Verify your edit stuck. Make sure there is not any extra "space" in line or end of that line. Reboot.
Click to expand...
Click to collapse
After the next reboot they started to stick.
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Are there still issues with lag and battery drain after root?
wojo797 said:
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Click to expand...
Click to collapse
Updating supersu has had mixed results. Some have no problem, but it has been suggested by chainfire himself to not update it.
ch0de said:
Are there still issues with lag and battery drain after root?
Click to expand...
Click to collapse
If you follow the Kernal Auditor step, it helps with the lag and battery drain. It is because the phone is in performance mode first upon root, and so the phone throttles on heat. Setting it to Interactive brings down heat and ultimately lag and brings back battery life.
wojo797 said:
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Click to expand...
Click to collapse
Are you on the Qualcomm or Exynos device? Are you sure you're G935P? I ask to try again one more time and make sure SU is installed on your phone. It may take a while for the prompt to open as well, but give it time.
xyameax said:
If you follow the Kernal Auditor step, it helps with the lag and battery drain. It is because the phone is in performance mode first upon root, and so the phone throttles on heat. Setting it to Interactive brings down heat and ultimately lag and brings back battery life.
Click to expand...
Click to collapse
Just to clarify, and I apologize for my ignorance..
When you say "helps" with battery drain and lag, does that mean it fixes the issue and it preforms at "stock", or does that mean its better then doing nothing but still more lag and battery/heat the unrooted stock ?
As per XDA forum rules, duplicating threads is not allowed. There is nothing wrong with making your contribution to the existing thread. Please continue there:
SM-G935P Root
THREAD CLOSED
Alright. So here it is. OnionRoot. ver 1.0.0
How does it work?
Same as default root with modifications of fixing the lag after you root.
This is early and it takes about a minute after you boot for OnionRoot (app) to fix the lag. DON'T WORRY, I am still trying to find a way to run the onion_root.sh script when the device is booting. It will be updated to fix this but it does what it is so far intended to do, remove lag.
Steps?
RECOMMENDED! Restore to stock firmware AP,CP,CSC,BL! Android 6.0.1
1. Put device into download mode
2. Flash Samsung_G935x_QC_Rooted_BOOT with Odin PrinceComsy.exe in AP
3. You device will lag like aids, I know. This is due to the fact that you flashed a version of the boot for samsung engineers. Go to settings and enable developers options and enable USB debuggging. You should know this by now.
4. Open your device. It should be at the homescreen. Now run part1_rooting.bat
5. Your device should be rebooting. After its done, open it and go to the homescreen again and run part2_after_rooted.bat
6. After running part2_after_rooted.bat your device will reboot again. It will install busy box for you and onionroot. Open busybox first and grant SU access. wait for all packages to download and install to /system/xbin
7. Open OnionRoot and tap manually lag out. This will ask you for root access, grant SU access. Tap it again just to be sure it ran the CPU governor script and give it about 30 seconds. Manually lag out doesnt lag your device, I know how it sounds, it actually switches your CPU governor to ondemand in order to make it run better without lagging like crap.
Now you should be good to go! Every time you reboot your device, OnionRoot will take a minute to execute the script to remove lag without having you to do anything! I am working on a MUCH better way of executing the script. I need to find out a way to execute the onion_root.sh script before the device boots up completely. If you have any ideas, let me know! Any suggestions on what to add, I am reading and listening. I am always looking for better ways to improve this root tool and make it fix performance without downloading so many apps and running them to make sure your device runs smoothly and not kill your battery.
P.S. I am open to ANY suggestions to make this better, we can make this open source too if you'd like
(edit) Should I also add a little fix to remove the notification pop up that says : "Security notice" Unauthorized actions have been detected blah blah ?
Thank you.
-SentoDev_ aka silentwind827
Download OnionRoot.rar
I'm all for development, but why make another thread when you have one other one about this tool?
Thanks, I performed all of your steps and it works well for me. I needed to perform a clean wipe, so I'm glad you posted this at the right time. The only issue now is to make OnionRoot autmatically start after boot up.
StrumerJohn said:
I'm all for development, but why make another thread when you have one other one about this tool?
Click to expand...
Click to collapse
I'm kinda new to xda and how posting works
Can you do this from APK1?
S7 SM-G930T Root Deleting Apps on Restart
Hi SilentJoe,
I had a rooted Samsung S7 that worked perfectly until I restart or power cycle. When I restart it will come back showing several user installed apps as "not installed" but with the icons still there. Then the power cycle started deleting the Google app and Play Store app. I ended up having to reload stock rom and reset and am trying to determine if there is a stable root available for the SM-G930T? Let me know if you are having any luck with your method listed in this post?
Here's My Config:
Phone - Samsung T-Mobile S7 SM-G930T
Baseband - G930TUVU3APG1
Android - 6.0.1
Root Used - Samsung_G930x_QC_Rooted_BOOT.TAR
Root Patches - S7_or_S7Edge_Fixes_V15.zip (MD5 hash F15CD9BDC35382A8F48FFBEDBB1BCDF0)
SperSu - V.2.79
Any feedback would be greatly appreciated. Thanks in advance for all of your efforts!
-Todd
Thanks,
-Todd
cogancorp said:
Hi SilentJoe,
I had a rooted Samsung S7 that worked perfectly until I restart or power cycle. When I restart it will come back showing several user installed apps as "not installed" but with the icons still there. Then the power cycle started deleting the Google app and Play Store app. I ended up having to reload stock rom and reset and am trying to determine if there is a stable root available for the SM-G930T? Let me know if you are having any luck with your method listed in this post?
Here's My Config:
Phone - Samsung T-Mobile S7 SM-G930T
Baseband - G930TUVU3APG1
Android - 6.0.1
Root Used - Samsung_G930x_QC_Rooted_BOOT.TAR
Root Patches - S7_or_S7Edge_Fixes_V15.zip (MD5 hash F15CD9BDC35382A8F48FFBEDBB1BCDF0)
SperSu - V.2.79
Any feedback would be greatly appreciated. Thanks in advance for all of your efforts!
-Todd
Thanks,
-Todd
Click to expand...
Click to collapse
This was developed for S7 Edge, not the regular S7. Also are you saying that you did this when you rooted with my tool?
uniphase said:
Thanks, I performed all of your steps and it works well for me. I needed to perform a clean wipe, so I'm glad you posted this at the right time. The only issue now is to make OnionRoot autmatically start after boot up.
Click to expand...
Click to collapse
OnionRoot does start to run its script at start up, but it doesn't do it while booting. It activates the script after your device has completed booted. Try it, boot you device (if you rooted with OnionRoot) and youll see a toast message popup saying "Lagged Out". This means it removed the lag and should make your device run smoothly. I am working on ideas how to make the script run while the device is in booting stages and completely remove lag due to the flash with odin of eng_boot.tar. Thanks.
S7 SM-G930T Root Deleting Apps on Restart
No, I did not use your tools or method. The previous method I used listed as S7 or S7 edge. Do you recommend trying your method? Has it been stable? Thanks for your reply. -Todd
silentwind827 said:
This was developed for S7 Edge, not the regular S7. Also are you saying that you did this when you rooted with my tool?
Click to expand...
Click to collapse
Gotta go get my laptop from home. Gonna do this at work.... Can't wait. Thanks
Sent from my SM-G935T using XDA-Developers Legacy app
cogancorp said:
No, I did not use your tools or method. The previous method I used listed as S7 or S7 edge. Do you recommend trying your method? Has it been stable? Thanks for your reply. -Todd
Click to expand...
Click to collapse
Follow these intructions and let me know if it worked. NOTE: you should restore EVERYTHING before rooting in order to make sure you didnt leave any data behind and have a fresh stock rom before rooting. Dont forget to wipe partitions and factory reset in recovery!
cogancorp said:
No, I did not use your tools or method. The previous method I used listed as S7 or S7 edge. Do you recommend trying your method? Has it been stable? Thanks for your reply. -Todd
Click to expand...
Click to collapse
Follow these instructions and let me know if it worked. NOTE: you should restore EVERYTHING before rooting in order to make sure you didnt leave any data behind and have a fresh stock rom before rooting. Dont forget to wipe partitions and factory reset in recovery!
Got it. I will let you know how it goes. Thank you again! -Todd
silentwind827 said:
Alright. So here it is. OnionRoot. ver 1.0.0
How does it work?
Same as default root with modifications of fixing the lag after you root.
This is early and it takes about a minute after you boot for OnionRoot (app) to fix the lag. DON'T WORRY, I am still trying to find a way to run the onion_root.sh script when the device is booting. It will be updated to fix this but it does what it is so far intended to do, remove lag.
Steps?
RECOMMENDED! Restore to stock firmware AP,CP,CSC,BL! Android 6.0.1
1. Put device into download mode
2. Flash Samsung_G935x_QC_Rooted_BOOT with Odin PrinceComsy.exe in AP
3. You device will lag like aids, I know. This is due to the fact that you flashed a version of the boot for samsung engineers. Go to settings and enable developers options and enable USB debuggging. You should know this by now.
4. Open your device. It should be at the homescreen. Now run part1_rooting.bat
5. Your device should be rebooting. After its done, open it and go to the homescreen again and run part2_after_rooted.bat
6. After running part2_after_rooted.bat your device will reboot again. It will install busy box for you and onionroot. Open busybox first and grant SU access. wait for all packages to download and install to /system/xbin
7. Open OnionRoot and tap manually lag out. This will ask you for root access, grant SU access. Tap it again just to be sure it ran the CPU governor script and give it about 30 seconds. Manually lag out doesnt lag your device, I know how it sounds, it actually switches your CPU governor to ondemand in order to make it run better without lagging like crap.
Now you should be good to go! Every time you reboot your device, OnionRoot will take a minute to execute the script to remove lag without having you to do anything! I am working on a MUCH better way of executing the script. I need to find out a way to execute the onion_root.sh script before the device boots up completely. If you have any ideas, let me know! Any suggestions on what to add, I am reading and listening. I am always looking for better ways to improve this root tool and make it fix performance without downloading so many apps and running them to make sure your device runs smoothly and not kill your battery.
P.S. I am open to ANY suggestions to make this better, we can make this open source too if you'd like
(edit) Should I also add a little fix to remove the notification pop up that says : "Security notice" Unauthorized actions have been detected blah blah ?
Thank you.
-SentoDev_ aka silentwind827
Download OnionRoot.rar
Click to expand...
Click to collapse
I think I will try to fix the ENGBOOT.tar kernel files so the device doesn't lag that much and drain the battery or might just move on to trying to figure out a possibility of unlocking bootloader which is highly unlikely.
Iomo said:
Can you do this from APK1?
Click to expand...
Click to collapse
What do you mean? Its possible but useless you'd still need to flash ENGBOOT.tar with pc on odin
Easy install. Snappy so far.
Is it okay to update SuperSU via playstore?
Can't Continue, Phone Not "Properly Rooted"
Hi i followed the steps but after getting to the busy-box app it says root isn't properly installed i re-did this about 2 times and still the same message.
silentwind827 said:
OnionRoot does start to run its script at start up, but it doesn't do it while booting. It activates the script after your device has completed booted. Try it, boot you device (if you rooted with OnionRoot) and youll see a toast message popup saying "Lagged Out". This means it removed the lag and should make your device run smoothly. I am working on ideas how to make the script run while the device is in booting stages and completely remove lag due to the flash with odin of eng_boot.tar. Thanks.
Click to expand...
Click to collapse
Something that may work is creating a /system/su.d folder and placing the script in with 7xx permissions.
I have Engineering Root for latest 7.0
I have oneplus one came from chineese retailer already rooted and with adware. always meant to reflash with straight CM or with a version of AOSP, but ended up use adb (which I have for development, though I am NOT experienced in using adb, flashing rom or what ever only programming) to disable a number of apps and it seemed to be stable.
More recently I had a phone crash following the crash of an app that I think is the CM app launcher, something begining with t, trebuchet?, i dont recall. Since then the phone keeps rebooting and I cannot seems to use adb, the device is either not present or offline.
I can boot to cyanogen recovery which offers:
- reboot system now
- apply update
- apply from adb
- choose from internal storage
- wipe data/factory reset
- wipe cache partition
- wipe media
If I select apply from adb then the device is nolonger offline but in sideline mode, but I don't think this is what I want.
I never liked CM and I had always thought that I might try to flash with a version of AOSP if possible and I wondered if now was the time. I thought TWRP might be useful for this and the first step to installing this was:
C:\...\Downloads>adb reboot bootloader
but I get
error: closed
I briefly see the debugging notification before the phone reboots but in adb it is always not present or offline.
How do I get to the point of either solving my repeating reboot at least or preferably installing a version of AOSP that would be compatible with OnePlus One, preferably without destrying data. I think the data is in a different partition or something but I have forgotten the little I learnt about this a few years ago.
I would be so grateful of some help and learning, right now to all intents and purposes I have a nice looking brick.
hardya said:
I have oneplus one came from chineese retailer already rooted and with adware. always meant to reflash with straight CM or with a version of AOSP, but ended up use adb (which I have for development, though I am NOT experienced in using adb, flashing rom or what ever only programming) to disable a number of apps and it seemed to be stable.
More recently I had a phone crash following the crash of an app that I think is the CM app launcher, something begining with t, trebuchet?, i dont recall. Since then the phone keeps rebooting and I cannot seems to use adb, the device is either not present or offline.
I can boot to cyanogen recovery which offers:
- reboot system now
- apply update
- apply from adb
- choose from internal storage
- wipe data/factory reset
- wipe cache partition
- wipe media
If I select apply from adb then the device is nolonger offline but in sideline mode, but I don't think this is what I want.
I never liked CM and I had always thought that I might try to flash with a version of AOSP if possible and I wondered if now was the time. I thought TWRP might be useful for this and the first step to installing this was:
C:\...\Downloads>adb reboot bootloader
but I get
error: closed
I briefly see the debugging notification before the phone reboots but in adb it is always not present or offline.
How do I get to the point of either solving my repeating reboot at least or preferably installing a version of AOSP that would be compatible with OnePlus One, preferably without destrying data. I think the data is in a different partition or something but I have forgotten the little I learnt about this a few years ago.
I would be so grateful of some help and learning, right now to all intents and purposes I have a nice looking brick.
Click to expand...
Click to collapse
Did you try factory reset?
Thank you so much for your the suggestion, I appreciate it.
Not yet I haven't. I'm not familiar with the CM Recovery Software and the option is entitled "wipe data/factory reset". Do you happen to know if this means bother or either and if selecting this explains more and gives options before proceeding. Key is I want to avoid wiping data if possible because while most is sync'd offline some is recent and not or not for particular reasons.
If there's a choice then will "factory reset" leave personal data alone? Do you know, will the factory reset likely be to version/adaptation of CM put on by rooting retailer PLUS anoying/mal/ad/ware apps put on by rooting retailer.
If this is my only option then I will go ahead and do it and take the hit.
If following this, it is possible to install a stable Android 7.n.n AOSP only that will support the hardware and leave data intact (ONLY LEAVE DATA IF POSSIBLE) I would be very grateful for a clear and complete script to achieve this. I was a professional developer for 20 years, now semi-retired, so I know what I know and what I don't know in terms of foundational knowledge, taking care etc etc, but I am very inexperienced in flashing phones and using ADB except the fact the eclipse/android studio uses it.
I used a windows script to install fastboot if that is any help (though the script did show some errors it still said "All Done!" at the end. Tried to C&P the errors but failed). I can also try to install TWRP (or what ever) if that's any help.
Many thanks would really appreciate your help in my getting my OnePlus One working and stable again.
Andrew.
hardya said:
Thank you so much for your the suggestion, I appreciate it.
Not yet I haven't. I'm not familiar with the CM Recovery Software and the option is entitled "wipe data/factory reset". Do you happen to know if this means bother or either and if selecting this explains more and gives options before proceeding. Key is I want to avoid wiping data if possible because while most is sync'd offline some is recent and not or not for particular reasons.
If there's a choice then will "factory reset" leave personal data alone? Do you know, will the factory reset likely be to version/adaptation of CM put on by rooting retailer PLUS anoying/mal/ad/ware apps put on by rooting retailer.
If this is my only option then I will go ahead and do it and take the hit.
If following this, it is possible to install a stable Android 7.n.n AOSP only that will support the hardware and leave data intact (ONLY LEAVE DATA IF POSSIBLE) I would be very grateful for a clear and complete script to achieve this. I was a professional developer for 20 years, now semi-retired, so I know what I know and what I don't know in terms of foundational knowledge, taking care etc etc, but I am very inexperienced in flashing phones and using ADB except the fact the eclipse/android studio uses it.
I used a windows script to install fastboot if that is any help (though the script did show some errors it still said "All Done!" at the end. Tried to C&P the errors but failed). I can also try to install TWRP (or what ever) if that's any help.
Many thanks would really appreciate your help in my getting my OnePlus One working and stable again.
Andrew.
Click to expand...
Click to collapse
Okay,since you want to flash Aosp N,leave that factory reset thing.
https://forum.xda-developers.com/showthread.php?t=2788632
This thread should be enough atm.Everything has been explained,and it's just simple copy paste,so,even if you're unfamiliar with adb,you should be able to do just fine.
Just follow,install adb/fastboot drivers,unlock bootloader,and flash twrp.
Now,unlocking bootloader will format internal storage,which means everything....but,a simple adb command should be able to back everything up into your pc.
Ensure your adb/fastboot drivers are already installed,and using adb devices in cmd shows your connected device id,before below process!
adb backup -apk -shared -all -f C:\Users\NAME\backup.ab
Where "NAME" is the name of your Windows user name.
On the device, a new screen should appear. If you want to encrypt the backup, enter a password -- otherwise, tap Back up my data. The backup will begin, and you'll find the backup file in the folder declared in the backup command.
Depending on how much data your device holds, this process can take quite some time.
The restoration process is simple. Connect the device to be restored and (from the same location you issued the backup command) enter the command:
adb restore C:\Users\NAME\backup.ab
Where NAME is the name of the same Windows user from the backup process.
Again, depending on how much data is on the backup, the restore process can take some time.
Click to expand...
Click to collapse
When you're done doing all of this,just follow any rom's thread instructions to flash that rom.
Btw,you're on Cos13.1.x,yes?
So sorry for not replying to say thank you sooner, I have been busy with family issues.
Thank you so much for your response, I really appreciate it. I shall take a look at this soon and try to get regular android N on the phone soon. Thank you.
I'm just starting to read and work through this. Just to clarify, re my original post, is the fact that my phone is continually rebooting and that adb shows the device as offline a problem? Will I still be able to use adb to backup the phone contents? Do I need any special understanding to do that?
I finally came back to this and flashed a new rom carbon rom. I only noticed afterwards that there is very little support for this rom and I've had some issues.
If you think the issues are in some way generic and you have come accross them before you may have some ideas:
- there is no built in task manager and third party ones do not seem to cover the apps I am interested in. Any ideas why there is no built in task manager anymore like there used to be and how one might be able to turn it back on?
- the camera does not work and the open camera I installed instead has some image faults (or misunderstood feature). Big line down the middle of the image.
Any ideas.
** USE THIS AT YOUR OWN RISK.
** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS.
** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE.
** BACKUP YOUR WORKING MODEMST1/2 AND PERSIST PARTITION IMAGES WITH BEFORE CONTINUING. THESE PARTITIONS ARE DEVICE UNIQUE, SO IF SOMETHING HAPPENS TO THESE PARTITIONS DURING THE CONVERSION, AND YOU DON'T HAVE A BACKUP, NOT EVEN MSM DOWNLOAD TOOL CAN SAVE YOU. YOU'LL HAVE TO SEND YOUR DEVICE BACK TO ONEPLUS FOR REPAIR. If YOUR PHONE IS ALREADY ROOTED, I RECOMMEND USING PARTITIONS BACKUP AND RESTORE TO DO THIS. JUST REMEMBER TO COPY YOUR BACKUPS OFF YOUR PHONE BEFORE YOU GET STARTED.
** BE SURE TO HAVE MSM DOWNLOAD TOOL AT THE READY FOR IF SOMETHING DOES HAPPEN. FOR THE T-MOBILE ONEPLUS 9, YOU CAN GET IT HERE: https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/
THIS METHOD REQUIRES AN UNLOCKED SIM AND BOOTLOADER
If you don't wish to unlock either, craznazn has released a MSM conversion package you can use to acomplish the same thing without requiring ether to be unlocked. Just download the package from their post, and follow the steps on their 8T MSM Conversion guide, as the steps should mostly be identical.
* I've successfully done this ONCE on my own personal T-Mobile OnePlus 9
* The script used here is just the same one made by craznazn to convert the T-Mobile OnePlus 9 Pro to EU firmware. I just swapped EU OnePlus 9 Pro images for the Global OnePlus 9 images and wrote a bash script for non-Windows users to use. You can just download my conversion package and follow their steps if you want. Just for convenience I'll also be writing the steps on how to use it here as well.
* You can drag and drop my bash script into craznazn's conversion package to use their package on non-Windows systems. You can download the bash script by itself here: https://gist.github.com/Lomeli12/73825a287d3cf60414e244aece9b6bdf
* This package will install Global Firmware 11.2.2.2. You'll need to use Oxygen Updater to update it to the current version (or at least until System Update can do it for you).
* Use the latest platform tools, either from https://developer.android.com/studio/releases/platform-tools or through your package manager of choice (apt, brew, scoop, etc). DO NOT USE MINIMAL ADB, it has not been updated for years.
* If you're having issues with either adb or fastboot detecting your device, consider installing the Universal ADB Driver.
* Have any issues? Describe the steps you take, copy the script's output log, and take screenshots. Include the output of fastboot --version in your post.
Now with all that out of the way...
Steps to convert your T-Mobile OnePlus 9 to the Global (or other) firmware
Unlock your bootloader and SIM. See https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/
Download and unzip the conversion package:
Global 11.2.2.2
MD5: 14e0c5e41df26bacbc11fe7e69a63c0e
SHA256: 10801f12c50e2d9a7e8085d113ac4a90ab312018beb84a10fa4c1a0f84fc95eb
Google Drive: https://drive.google.com/file/d/1h7Hpbde40wLYynUIo83TTIoERhA_04nS/view
AndroidFileHost: https://www.androidfilehost.com/?fid=2188818919693806454
Spoiler: If you want to use a newer or different region firmware, delete all the *.img files from my conversion package and do the following:
Download and unzip the firmware you want from the OxygenOS Repo thread. You'll specifically want to extract the payload.bin file.
Install Python 3 and Python Protobuf. Figure out how to do this on your own system.
Download cyxx's extract android ota payload script from GitHub: https://github.com/cyxx/extract_android_ota_payload/
Place the payload.bin you extracted earlier into the same directory as the extract_android_ota_payload.py script.
Run the extraction script and wait. This step usually takes a while to complete
Bash:
python3 extract_android_ota_payload.py payload.bin tmp/
Open up the tmp folder the script created and copy all the image files from there over to where flash_all scripts are located.
Boot to bootloader
From adb:
Bash:
adb reboot bootloader
From fastboot/bootloader:
Bash:
fastboot reboot bootloader
Execute either flash_all.bat or flash_all.sh from the unzipped conversion package.
Reboot into recovery and wipe everything
Once fully booted and setup, use Oxygen Updaterto update your phone to the latest version the app provides. Oxygen Updater will provide steps on how to use the full OTA zip.
After you've updated using Oxygen Updater, go into Settings -> System -> System Updates and check for new updates, as Oxygen Updater usually takes a few days to have the absolute latest OTA available. If there is another update available, go ahead and let the System Updater do its thing.
Do a regular system reboot, NOT into recovery, bootloader, or fastbootd.
NOTE: The following steps (8-10) may or may not be optional, we haven't 100% figured it out yet
Repeat step 3 to get back into the bootloader.
Flash the T-Mobile modem included in the conversion package
Bash:
fastboot flash modem NON-HLOS.bin
After each full OTA you take in the future, repeat steps 8 and 9 again.
Fixing SafetyNet by installing Magisk
When I first did this on my own phone, my phone would fail SafetyNet, specifically with a CTS Profile Mismatch. Once I installed Magisk and enabled MagiskHide, however, SafetyNet was passed once more. No MagiskHidePropConfig or UniversalSafetyNetFix required. Here are the steps I did.
Make sure you've updated your phone to the absolute latest version of OxygenOS you can. See step 6 of the conversion steps on how to do so.
Copy the boot.img from the conversion package onto your phone.
Install Magisk Manager onto your phone.
Open Magisk Manager and patch boot.img
Tap Install
Select Select and Patch a file and tap Let's Go
Choose the boot.img file we copied over and hit okay
Once the patch is finished, copy the patched boot.img back onto your PC. Magisk Manager usually puts it in your phone's downloads folder as magisk_patched-<current magisk version>_<random string of characters>.img. The logs in Magisk Manager will tell you exactly what it named the patch image as.
Boot to your bootloader. See step 3 of the conversion steps for this.
Boot your phone using the patched boot.img
Bash:
fastboot boot magisk_patched-<current magisk version>_<random string of characters>.img
Once your phone has booted up, open Magisk Manager once more
Go into Magisk Manager settings and enable MagiskHide.
Back out of the settings and install Magisk via Direct Install
Reboot your phone normally. You should now have Magisk and pass SafetyNet.
Issues so far:
Using EdXposed Hide on the Google Play Store or Google Play Services can cause a soft brick requiring resetting your device via recovery. No issues with LSPosed so far.
Google Phone dialer doesn't display option for Visual Voice Mail. The T-Mobile Visual Voicemail app can be used though.
What appears to work:
Everything else
Edit 1 (5/17/2021):
Fixed some wording that I felt was awkward after the fact.
Made a note that flashing the T-Mobile modem may be optional, still up in the air on that.
Included download mirror for AndroidFileHost.
Listed EdXposed softbrick reported by @Josh McGrath.
Edit 2 (5/19/2021):
Added note about VVM missing from Google Dialer, but T-Mobile VVM app being a good alternative.
Adjusted phrasing in modem flashing steps
Edit 3 (6/7/2021):
Added link to craznazn's MSM conversion tool, which is a good alternative for those who don't want to unlock their bootloader.
Excellent. I've been waiting for this. For partition backup, using the MSM readback functionality (password is usually oneplus) is also an option.
If the OP9 is anything like the OP8T, a direct Euro conversion would be better for quicker updates.
Getting to Euro from Global in a GUI-based approach is also possible. Just set the device ID to OnePlus 9 (EU) in Oxygen Updater and follow the rest of the main guide. You might need to enable advanced settings and ignore device mismatch warnings though. Assuming you are already rooted at this point, you can keep root after the local upgrade, but before rebooting, by flashing Magisk to the inactive slot. Modem still needs to be reflashed.
Modem in general is going to be a pain. Somebody will need to extract it from each T-Mobile OTA if you want fixes and new carrier aggregation combos.
Note: I have not tested this and this is not advice. Follow at your own risk.
He said the TMobile modem files were in the download. Are those 2 files not the correct ones or something?
Or are you just talking about updating the modem every time Tmo sends out an update. (which is usually every 3 months )
Talking about modems in OTAs.
That will be a pain to get any updated modem images, but 1) we just need one person who's willing to stay on the T-Mobile firmware and dump it. Just need to find this willing person and 2) like @Josh McGrath said, expecting T-Mobile OTAs to come frequently, especially those with substantially changes to the modem.img, might be giving T-Mobile too much credit.
Just wanted to say thank you to @Lomeli12 for this tutorial! Also..
After following this guide, and updated through oxygen updater to 11.2.4.4 then 11.2.5.5 from factory OTA . I have full 5g internet and phone signal, without ever flashing modem non-HLOS.bin.... has anyone else had this luck? or am I the only one???
Jg1234 said:
Just wanted to say thank you to @Lomeli12 for this tutorial! Also..
After following this guide, and updated through oxygen updater to 11.2.4.4 then 11.2.5.5 from factory OTA . I have full 5g internet and phone signal, without ever flashing modem non-HLOS.bin.... has anyone else had this luck? or am I the only one???
Click to expand...
Click to collapse
I also noticed this on my phone. I still flashed the T-Mobile modem.img just for network compatibility, but it is possible we don't even need the T-Mobile modem.img to begin with.
Lomeli12 said:
I also noticed this on my phone. I still flashed the T-Mobile modem.img just for network compatibility, but it is possible we don't even need the T-Mobile modem.img to begin with.
Click to expand...
Click to collapse
I know they have trouble with the pro version, so far I haven't had any issues. I will report back after the weekend and test it more while I travel, but don't think that will make a difference. Maybe others can test too!
I was about to do this but I've been using Minimal ADB of course but I downloaded platform tools from the link, unzipped it and ADB.exe won't work. It immediately closed.
Anyone had this issue?
And I didn't read that sentence correctly. Any specifics on what adb error ya got
No prob on the misreading my post bro.
There are no errors, it just simply will not stay open. It opens and immediately closed down. I've downloaded it twice already. Any idea? Win 10
Again, sorry. Completely misread the sentence. Without getting logs or anything more specific than "adb.exe isn't working", we can't really help you.
Not a problem. And yes I totally understand that. I was hoping it was a known easy fix that someone knew but I guess not. But thanks for your help anyhow and will ask again if I can't get it working and get the logs.
Just to test things out and see if adb is working, verify that you don't have minimal adb installed anymore and run
Bash:
adb devices > log.txt
and copy whatever got piped into log.txt.
Minimal ADB is too old. Follow directions.
You may need to set PATH for ADB or put everything in the same folder.
LLStarks, I said I was not using min adb. However, I was able to fix my issue by doing the exact rookie error you stated. :Facepalm.
But I got it all converted over now as of last night and everything is working great so thank you for this guide, Lomeli12.
The new edxposed has an Xposed hide option and I will say to NOT try to hide the play store or play services with this cause it soft bricked me and had to do a master reset via recovery. Just a fyi for anyone trying to hide for safety net. (I did use it for Snapchat and it works)
Josh McGrath said:
LLStarks, I said I was not using min adb. However, I was able to fix my issue by doing the exact rookie error you stated. :Facepalm.
But I got it all converted over now as of last night and everything is working great so thank you for this guide, Lomeli12.
The new edxposed has an Xposed hide option and I will say to NOT try to hide the play store or play services with this cause it soft bricked me and had to do a master reset via recovery. Just a fyi for anyone trying to hide for safety net. (I did use it for Snapchat and it works)
Click to expand...
Click to collapse
Good that you've resolved your issue. I've only tried with LSPosed without issue or triggering SafetyNet, but I'll make a note of it for EdXposed.
After replacing the flash, does the VVM voicemail in the dialer work?
After replacing the flash, does the VVM voicemail in the dialer work?
iSkyJIE said:
After replacing the flash, does the VVM voicemail in the dialer work?
Click to expand...
Click to collapse
Can confirm Visual Voicemail does work, so does the Dialer.. Although, i don't recognize the dialer as the oneplus stock one... someone else may be of better use for an answer for that, as I have never used the stock dialer. Although, one slight issue with the conversion.. And it doesn't seem as if anyone else is having this problem.. After I updated to 11.2.4.4 via oxygen updater, I can't get OTA to work.. It starts for two seconds and says Update Failed.. I'm not sure what I could have done wrong, I followed the steps 100% and the only thing I could think of that could have caused it is that when I rooted before this process (while still on the T-Mobile ROM), I accidentally flashed the boot.img from the EU version instead of boot it. I tried to flash the boot img that was in the ZIP package from the download above, and still didn't fix it. Hoping I or someone could figure this one out.
Hi Community, Recently I uninstalled some packages from my IQ007 using Adb shell.
Now I am facing some weird issues, so I want to reinstall all the deleted package files, but problem is I don't remember which packages I deleted.
Is their any Adb command or any way to reinstall all default packages of IQ007 with hard reset.
naseebpanghal said:
Hi Community, Recently I uninstalled some packages from my IQ007 using Adb shell.
Now I am facing some weird issues, so I want to reinstall all the deleted package files, but problem is I don't remember which packages I deleted.
Is their any Adb command or any way to reinstall all default packages of IQ007 with hard reset.
Click to expand...
Click to collapse
"cmd package install-existing" use that command it'll reinstall
I aware about that command but I am not aware which package I have deleted. So, What can be done to get all the packages installed?
naseebpanghal said:
I aware about that command but I am not aware which package I have deleted. So, What can be done to get all the packages installed?
Click to expand...
Click to collapse
What's the problem with ur phone?
Neeraj.sharma said:
What's the problem with ur phone?
Click to expand...
Click to collapse
Not a Big concern but after applying some packages deletion, I am facing wierd issue. Sometimes few apps are getting crash.
naseebpanghal said:
Not a Big concern but after applying some packages deletion, I am facing wierd issue. Sometimes few apps are getting crash.
Click to expand...
Click to collapse
I think you've uninstalled wisdom engine? Check it if that's not the case go through the below link it has iqoo 7's all package names
IQOO 7 Pre Installed Packages | PDF | Verizon Wireless | Arm Architecture
Scribd is the world's largest social reading and publishing site.
www.scribd.com
Well, thanks niraj I will surely look into it.
Last Resort : Factory Reset your phone and it'd bring back everything.
If you can give a list of apps that are crashing, may be I can help since I have maintained a list of almost apps removable along with their uses.
*deleted*
nikhilkaushik said:
Last Resort : Factory Reset your phone and it'd bring back everything.
If you can give a list of apps that are crashing, may be I can help since I have maintained a list of almost apps removable along with their uses.
Click to expand...
Click to collapse
**SOLVED FOR ME - I restarted my phone and all works well now. As always, try turning it off and back on again to se if that fixes it first**
Bit of a necro but I am having difficulty recieving text messages. I can send them, but I cannot recieve them. Are you able to take a look at the below list of removed packages and tell me which one might have sonething to do with text messaging?
package:com.oneplus.calculatorpackage:com.android.cts.priv.ctsshimpackage:com.oneplus.gamespacepackage:com.sprint.ecidpackage:com.google.android.cellbroadcastservicepackage:com.sprint.w.installerpackage:cn.oneplus.photospackage:com.tmobile.m1package:com.qualcomm.uimremoteclientpackage:com.oneplus.brickmodepackage:com.netflix.partner.activationpackage:com.tmobile.pr.mytmobilepackage:com.oneplus.factorymode.specialtestpackage:com.google.ar.corepackage:com.oneplus.android.cellbroadcast.overlaypackage:com.google.android.marvin.talkbackpackage:com.oneplus.factorymodepackage:com.android.eggpackage:com.google.android.apps.tachyonpackage:com.sprint.ms.cdmpackage:net.oneplus.pushpackage:com.android.dreams.basicpackage:com.google.android.apps.wellbeingpackage:com.tmobile.pr.adaptpackage:com.android.bipspackage:com.android.cellbroadcastreceiverpackage:cn.oneplus.oemtcmapackage:com.oneplus.filemanagerpackage:com.google.android.ttspackage:com.sprint.ce.updaterpackage:com.google.android.videospackage:com.oneplus.faceunlockpackage:com.google.android.feedbackpackage:com.oneplus.opbugreportlitepackage:com.tmobile.rsuadapter.qualcommpackage:com.oneplus.screenrecordpackage:com.android.providers.partnerbookmarkspackage:com.android.wallpaper.livepickerpackage:com.oneplus.bttestmodepackage:net.oneplus.commonlogtoolpackage:com.android.bookmarkproviderpackage:com.android.cts.ctsshimpackage:com.android.wallpaperbackuppackage:com.sprint.ms.smf.servicespackage:com.google.android.apps.youtube.musicpackage:com.android.traceurpackage:com.google.android.cellbroadcastreceiverpackage:com.tmobile.rsuapppackage:com.tmobile.rsusrvpackage:com.android.cellbroadcastreceiver.overlay.common
RonnieDoitch said:
**SOLVED FOR ME - I restarted my phone and all works well now. As always, try turning it off and back on again to se if that fixes it first**
Bit of a necro but I am having difficulty recieving text messages. I can send them, but I cannot recieve them. Are you able to take a look at the below list of removed packages and tell me which one might have sonething to do with text messaging?
package:com.oneplus.calculatorpackage:com.android.cts.priv.ctsshimpackage:com.oneplus.gamespacepackage:com.sprint.ecidpackage:com.google.android.cellbroadcastservicepackage:com.sprint.w.installerpackage:cn.oneplus.photospackage:com.tmobile.m1package:com.qualcomm.uimremoteclientpackage:com.oneplus.brickmodepackage:com.netflix.partner.activationpackage:com.tmobile.pr.mytmobilepackage:com.oneplus.factorymode.specialtestpackage:com.google.ar.corepackage:com.oneplus.android.cellbroadcast.overlaypackage:com.google.android.marvin.talkbackpackage:com.oneplus.factorymodepackage:com.android.eggpackage:com.google.android.apps.tachyonpackage:com.sprint.ms.cdmpackage:net.oneplus.pushpackage:com.android.dreams.basicpackage:com.google.android.apps.wellbeingpackage:com.tmobile.pr.adaptpackage:com.android.bipspackage:com.android.cellbroadcastreceiverpackage:cn.oneplus.oemtcmapackage:com.oneplus.filemanagerpackage:com.google.android.ttspackage:com.sprint.ce.updaterpackage:com.google.android.videospackage:com.oneplus.faceunlockpackage:com.google.android.feedbackpackage:com.oneplus.opbugreportlitepackage:com.tmobile.rsuadapter.qualcommpackage:com.oneplus.screenrecordpackage:com.android.providers.partnerbookmarkspackage:com.android.wallpaper.livepickerpackage:com.oneplus.bttestmodepackage:net.oneplus.commonlogtoolpackage:com.android.bookmarkproviderpackage:com.android.cts.ctsshimpackage:com.android.wallpaperbackuppackage:com.sprint.ms.smf.servicespackage:com.google.android.apps.youtube.musicpackage:com.android.traceurpackage:com.google.android.cellbroadcastreceiverpackage:com.tmobile.rsuapppackage:com.tmobile.rsusrvpackage:com.android.cellbroadcastreceiver.overlay.common
Click to expand...
Click to collapse
Try enabling
Com.sprint.ms.cdm
And
com.sprint.ms.smf.services
Looks like these 2 packages could be causing that.
It's only a hunch but you may give it a try.