First of all this is not my work I only tested theirs.
Credit to @themustached for finding that a patched .ops was the solution.
This guy doesn't even have the damn phone yet and did this for us so show some love. You can donate to him through paypal here - http://paypal.me/dustinwann
Also @Eliminater74 @jkyoho and others for their hard work and dedication to this conversion.
Disclaimer: I do not take responsibility for any damage done to your device by using this procedure. Everyone has problems sometimes so be civil and ask clear questions explaining where you failed if you expect help.
These instructions will convert your TMOBILE Oneplus 7 PRO to the International version of the phone.
This lets you unlock the bootloader, root, twrp etc.. Sim unlock is still being worked on.
Take a breath, drop the hype and read every single step before you even plug your phone into the PC.
These steps assume you understand you lose all data on the device, are sim unlocked, have the Download mode drivers installed, adb and fastboot and your device powered OFF.
1) Download both of these archives and extract them to a folder you can locate. - https://mega.nz/#!289BVITR https://mega.nz/#!St1DiShb Mirror - https://www.androidfilehost.com/?w=files&flid=294946
2) Open the MSM tool and uncheck the box next to SHA 256.
3) Hold both volume buttons for 5 seconds then plug in the USB cable. OR In ADB type "adb reboot edl".
4) Watch the MSM tool and the second it says *Connected* next to one of the COM ports, press START.
5) DO NOT unplug the device until after it says Success in green.
6) Once the phone boots into the system, go through all the setup options.
7) Enable Developer Options and enable OEM Unlocking.
8) Enter bootloader mode on your device and type "fastboot oem unlock".
You now have an unlocked international OP7.
If you want to root and install twrp dont take the OTA yet.
-Follow these two threads below then take the OTA, do that after you root and twrp. You can preserve root by going into Magisk Manager after the OTA installs, then press the top Install button on the right and use the after OTA option.
This will put you on the latest version with twrp, root and working sound/wifi.
1) Root - https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205 by @acervenky
2) Twrp - https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 by @mauronofrio
3) OTA zips - https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585 by @Titokhan
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*Future proofing Update*
Hot off the press. Here is a tool that will allow you to patch an ops file without having to download a new modified one every update.
You can use this with a stock MSM or the modified one linked above. Must be run on an unmodified ops..
Global
EU
China
1) Extract the Patcher into the same directory as your MSM tool and OPS firmware.
2) Launch the Patcher as admin. Now select the ops you want to patch and check all the boxes under Patch Options and click Start.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Once it finishes you will be able to flash the ops file from the stock MSM or the modded one above.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*TMobile Update*
The MSM tool/firmware for TMobile OP7Pro is now released.
You can find it on my other thread - HERE
Credit for this one also goes to @themustached.
Guacamole decryption key - 836tI3vZa3ixi9487IpxNEw-I5RGT3QjJXmm0dGYLcI
Additional decryption key - ezLIQmIL9j7OQV1qcvJtof8M0pCHYY_nC9W4pDaw3is
~FAQ~
~Not fast enough to start flash
If you press Start on the MSMTool it will "wait for device".
Doing this will make the flash start right when the phone enters EDL.
~MSM is getting stuck on Param Preload or something similar.
This can be caused by having old Oneplus L2 drivers from a different model installed.
-Follow the steps up until MSM gets stuck. Open Device Manager, right click on the Qualcomm device under the COM section.
Click Uninstall but do not check the box to delete the driver, then click Scan for Hardware changes. Now go to the folder you extracted the L2 driver to, right click the inf file and click Install.
You should be able to use the MSM tool right away but may need to exit and re-open. Also restart back into EDL if needed.
You guys are the best, I'm going to try it once I get home. Do I need to unlock the bootloader if I don't want to after the conversion?
Sent from my GM1915 using Tapatalk
Can u lock bootlaoder and stay like international version plus get update update the air without pushing it?
I converted mine manually or I'd do this, but that was quick boys! Awesome job. Going to be lots of happy people now that this is out.
Niceeeeeeee
So this is the patched tool to convert to intl
Yup I'll give it a shot once I get home!
Sent from my GM1915 using Tapatalk
Can't wait to try this when I get home. Thank you all for the work.
So I did accidentally unplugged the device after doing the 5 seconds thing and plugged it into a computer. I unplugged it by accident and now it won't turn on.
Strike99Fear said:
So I did accidentally unplugged the device after doing the 5 seconds thing and plugged it into a computer. I unplugged it by accident and now it won't turn on.
Click to expand...
Click to collapse
Just press the power button for 20 seconds or so
Primal instinct said:
Just press the power button for 20 seconds or so
Click to expand...
Click to collapse
Tried it and it won't work.
i connect the op and show Qualcomm QD loader on device manager but then it will disconnect and show usb mass storage device
Strike99Fear said:
So I did accidentally unplugged the device after doing the 5 seconds thing and plugged it into a computer. I unplugged it by accident and now it won't turn on.
Click to expand...
Click to collapse
Try hold power and both volume buttons
Bootloader unlock is optional, correct?
Adb reboot edl also works but fully converted here
Primal instinct said:
Try hold power and both volume buttons
Click to expand...
Click to collapse
That worked thanks brother!
Does deleting modem St files remove the Sim lock on the OP7 as well?
I'm gonna try it wish me luck
OEM unlocking is greyed out for me at Step 7, not sure if I did something wrong.
Related
Hello guys!
Today I'm bringing you a tutorial on how to achieve root permissions on the Xperia M2 with Android 5.1.1 Lollipop. As of right now, this is only available for UNLOCKED BOOTLOADERS, so those with LBL have to wait a little more until I find a suitable solution.
What do we need?
Upgrade your bootloader using this guide.
My ADB pack.
My modded TWRP for unlocked bootloaders.
Ric Disabler by my friend @AleksJ [MIRROR]
The procedure:
First, flash Lollipop if you didn't flash it before. Once done, upgrade your bootloader using Emma or the FTF I linked before.
WARNING: If you updated your bootloader BEFORE FLASHING LOLLIPOP, you MUST upgrade it again since Lollipop FTF overwrites it.
Now, turn on the phone, go to Settings, Info. about the device, and tap 7~8 times the Compilation Number. This will un-hide the developer options. Press back button once and go inside the Dev. Options. Now turn them on if they were off, and enable USB Debbuging. Now turn off your phone.
Now, unzip my ADB Pack 'Herramientas-de-flasheo.zip', which contains basic ADB and Fastboot executables to a folder in your desktop. Also, copy the TWRP Recovery .img you downloaded to that folder.
Put your phone in Fastboot mode, this means, while pressing and holding the Vol+ button, connect the USB cable. Once the Led goes blue, stop pressing it.
Now, execute the following keyboard shortcut (Win+R) and type inside the Run prompt CMD. Inside the Command Prompt, using CD (change directory), navigate to the folder you created in the desktop. It'll be something like...
Code:
cd C:\Users\linuxct\Desktop\adbpack\
Now, execute the following command:
Code:
fastboot flash recovery [COLOR="DarkOrchid"]RECOVERY-TWRP-2.8.7.0-D230X_D240X-UPDATED-THEME[/COLOR].img
Once it finishes, disconnect the USB cable. Now, to enter into the recovery, press and hold the volume down button, and while you're holding it, press and hold the Power button until it vibrates. When you see the BIG Sony logo, stop holding the Vol- Button.
This will load Erikcas TWRP. After few seconds, it'll ask you to allow /system modifications, so slide it to allow modifications. Now navigate to Reboot, and choose System. In a moment or so it'll ask you if you want to root your device. To do that, slide again.
The device will reboot in a few seconds. When it's succesfully booted up, go to the App Drawer and look for 'SuperSU Installer'. Open it and hit the 'Play' button. This will open SuperSU in Google Play. Now update SuperSU.
When it's done updating [Don't open SuperSU yet!], unzip the Ric Disabler from AleksJ in your PC, and open the Install.bat OR Use the following Bash Script if you're on Linux, thanks to @luichi. Once it's opened, connect again your device via USB. In the M2, the script will prompt a question about USB Debbuging key. Tick the 'Remember this PC' checkbox and hit Allow. After some secs, it'll ask you for root permissions, so hit Allow.
In a while, when in CMD it says 'Press any key to continue', disconnect your cable and open SuperSU in your device. Now it'll ask you about updating su binary. Hit Update, and then hit on 'Normal' method.
And that's it! Enjoy your Lollipoped device with Root!
Don't forget to hit the thanks button and thank all people mentioned in this post too!
Thanks for this tutorial! All working
Can you make bootloader in FTF file for D2305 plz? Thanks!
Thanks
Do you know if Xposed is fully working?
Laura158 said:
Can you make bootloader in FTF file for D2305 plz? Thanks!
Click to expand...
Click to collapse
It's generic, don't worry, you can use it in any D230X and any D240X you want.
KolikKitsune said:
Thanks
Do you know if Xposed is fully working?
Click to expand...
Click to collapse
I have no idea...
KolikKitsune said:
Thanks
Do you know if Xposed is fully working?
Click to expand...
Click to collapse
@KolikKitsune for me nope. i might do something wrong but its saying with the current version it doesnt work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It is only for M2 or for Aqua too?
Evedammo said:
It is only for M2 or work in Aqua too?
Click to expand...
Click to collapse
Aqua too! Any M2 in general can use it :good:
via emma ? can you show how upgrade bootloaders via emma ?
WoW, nice work. Have a fully working recovery AND root now.
If you want something "simpler", you can flash a boot.img with integrated recovery instead of using the first method.
BlazingBullets said:
WoW, nice work. Have a fully working recovery AND root now.
If you want something "simpler", you can flash a boot.img with integrated recovery instead of using the first method.
Click to expand...
Click to collapse
But then you'll need to go back to 5.1.1 kernel in order to boot the device, loosing the recovery. This recovery is permanent as it's isolated in it's own partition.
faizal21 said:
via emma ? can you show how upgrade bootloaders via emma ?
Click to expand...
Click to collapse
Follow this nice guide made by Sony
vampirian said:
@KolikKitsune for me nope. i might do something wrong but its saying with the current version it doesnt work
(img)
Click to expand...
Click to collapse
Guys, you need to install the experimental Xposed for Lollipop 5.1.1! The 4.x installer is not working anymore!
BUT, take this into account:
- Sony seems to have shipped some ROMs with corrupted services.odex (the embedded .dex is invalid). Those ROMs will bootloop with a "Fatal signal 6" or "No pending exception expected: java.lang.ArrayIndexOutOfBoundsException" error, which I unfortunately cannot fix.
Click to expand...
Click to collapse
@linuxct
I dunno if I flashed back or not, but if i didn't then I think FKernal works with 5.1.1
Don't really want to test it either
Guys dont even try xposed...Bootloop because of corrupted services.odex
Too late... -.-
after Flashtool by sony
after taht, what the next step ?
faizal21 said:
after taht, what the next step ?
Click to expand...
Click to collapse
After flashing the bootloader update, turn the phone on, enable USB Debugging and then turn it off; and go ahead to flash erikcas twrp. (2nd and 3rd points)...
after step 8 i reboot like normally but touch wont work, but the touch in RecoveryMode work well..
Well, I just purchased this device and came here after that to look at what we had and I'm disgusted.
And there are several reasons for that, being:
1 - Locked Bootloader...
2 - This forum seems somewhat abandoned, which leads it to be somewhat disorganized.
EdiT:
Thanks to our friend repey6 > http://forum.xda-developers.com/member.php?u=5704037
TWRP 2.8.7.0 is now included, and it works just ok, with all functionality.
I strongly recommend you to use it instead of any other recovery. Just make sure to backup your ROM again after installing it, as CWM or Carliv backups won't work in TWRP.
I replaced the old TWRP included in the attachments with the new one provided by repey6, but the installation process remains the same.
Plus, this was not created by me and it's mad old (2014). But still it works better than the Carliv Recovery we have available here...
So Let's go. The proccess is the same for both, just choose the recovery image you want in the end of the topic.
(almost forgot to say that if your phone bricks it's you responsibility, I tested it in mine and it is working fine)
STEPS:
STEP1- Root your phone (if it's not rooted yet).
To root your phone you'll need to:
a-Download the framaroot APK provided in the attachments
b-Install it then click in the Boromir option and the su binary will be installed.
c-Download SuperSU from google play store.
That's all, simple like that.
STEP2- Check your bootloader's S1 Version
a-Open your dialer and input *#*#7378423#*#* , then go to Service Info>Software Info> S1 Boot Version.
b- Check if yours is 2.14.J.2.6 or 2.14.J.2.13 or 2.14.J.2.16 . If yours is one of these go ahead, it should work just fine and you can proceed.
If yours is 2.14.J.0.68 do not proceed, as it will 100% brick your phone.
c- My phone has S1 Boot Version 2.14.J.1.15 and in spite of the developer having not mentioned anything about it, I risked it all and my phone flashed the recovery normally, so if your version is also 2.14.J.1.15, it should work just fine and you can proceed.
STEP3 - Install the recovery
NOW, BE EXTREMELY CAREFUL HERE, OTHERWISE YOU WILL HARD BRICK YOUR PHONE:
a-Download the mobileuncle.apk file provided in the attachments and install it.
b-Download the twrp_xperia_C.img file provided below and put it in your internal memory (not on the external). Rename it to recovery.img, otherwise mobile uncle won't see it.
Now, here's the part you have to mind, so you won't brick your phone.
Mobile uncle can install a recovery using one of two methods. One is by installing the image from your internal memory (which we'll be doing). Other is installing it from the internet.
Now, YOU DON'T WANT to install a recovery from the internet, as mobile uncle doesn't provide any image for your device. So if you flash any of these recoveries, you'll never be able to make your phone boot again.
See in the image below and you'll get what I mean:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
c - So, before proceeding TURN OFF YOUR WIFI AND DATA CONNECTIONS so that mobile uncle won't show any recovery from internet
d-Open mobile uncle.
e-Grant Super User
f-Press "Recovery Update"
g- With wifi turned off, you'll see only your recovery in the screen
h- Click it, the file size of the file I'm posting must be around 6MB ( 6210KB for CWM), if it's different cancel and download file again.
i- press ok and restart.
DONE
:good:
EDIT:
I just noticed that after flashing the recovery you might get your phone stuck in the SONY logo after it.
In fact it happened to me, but just once.
If that happens don't panick. Recove the cover of your phone and besides the SIM-2 slot you'll see a tiny role with the word "reset". Insert a needle in there and your phone will restart normally.
CREDITS FOR CWM
Prashanth Jraj
Credits for posting it on the net and for the original tutorial:
informationlord.com
credits for TWRP 2.8.7.0
Miha_xXx
Original Post (for TWRP - in Russian): Click Here
credits for this tutorial:
me
ATTACHMENTS BELOW
Thanks for the guide! Does this also work on the C2305 model, or is it strictly for C2304?
Syd_M said:
Thanks for the guide! Does this also work on the C2305 model, or is it strictly for C2304?
Click to expand...
Click to collapse
It should work in both, I'm using a recovery for C2305 in my C2304.
Just don't try flashing a C2305 ROM on your C2304. It will not hardbrick your phonw, but the SIM cards will not work and you will get a mad functioning phones.
Some custom ROM's based on stock firmware work in both though.
Hey anyone tried for xc 2305???
So my S1 bootloader version is: 2.14.J.0.68. Is it for sure there is nothing that can be done?
SMIT120 said:
Hey anyone tried for xc 2305???
Click to expand...
Click to collapse
sid4913 said:
So my S1 bootloader version is: 2.14.J.0.68. Is it for sure there is nothing that can be done?
Click to expand...
Click to collapse
Sorry for the late reply! Haven't been able to test this until recently due to an issue getting my PC to work properly with my phone. Anyway, I would like to confirm that I was able to flash this on my Xperia C2305 that had S1 Boot Version 2.14.J.0.68. The photo below is proof of CWM running on my Xperia C2305:
Things you will need:
WMShua SuperFlash: http://soft.flushrom.com/WMShuaSetup.exe (after installing, you can change the language to English by renaming Program Files/wmshua/language to Program Files/wmshua/language_x)
Xperia C 16.0.B.2.16 FTF: C2305_16.0.B.2.16_TacoNikky.ftf or C2305_16.0.B.2.16_Congngheviet.ftf (pick one; I used TacoNikky's version)
Procedure:
1. Open WMShua, then click on Flash (not Super Flash). Browse to the FTF file you downloaded. You can choose to backup system before flash (I unchecked it on mine). Follow the screenshot below for guidance:
2. Turn off your phone. Next, hold down the Vol- (volume down) button on your phone. While holding down, plug in the micro USB cable. The LED will flash red. When it changes to green, release the Vol- button. WMShua should automatically try to install the needed drivers. After installing drivers, it will begin the flashing process. If your phone turns on instead, simply unplug it from the USB, turn it off, then try again.
The flash process may take a long time (it took 30+ minutes for me), and sometimes it may look like it hanged, but it's actually working. Just be patient. Once it reaches 100%, your phone will automatically boot up. Check your S1 Boot Version—it should now be 2.14.J.2.16. You may find that you've lost root, so you will need to root it again (I use KingoRoot). After rooting, follow the instructions on the first post to install CWM or TWRP. Good luck!
Starmobile Up Prime
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SOME INFO:
MT6737/M (they seem to be the same thing)
Antutu Score: 30052 [source]
As of Jan 6 2018, latest official firmware is v13 06292017.
A. Root
Disclaimer: YOU ARE DOING THIS AT YOUR OWN RISK. I will not assume any responsibility for your own actions on your phone. Follow the instructions carefully, and ask questions if you're unsure.
Tested way: Magisk Manager patched boot method
Other option: SRS Root reports to root the v12 firmware, though I didn't use this method so I don't know if it works.
Magisk Manager Patched Boot Method
1. Unlock your bootloader (Note: this will factory reset your phone and you will lose all your personal data) To do this:
Enable bootloader unlock inside developer options, accessed by pressing build number 7 times in settings. Thanks @Nao Tomori !
Install adb and fastboot on a computer (Search it, it's available)
Reboot to fastboot mode (Switch off phone, press power and volume up simultaneously. Choose fastboot mode from the menu that appears)
Connect to computer by USB Cable provided
Open a command prompt or terminal and check if fastboot detects your device by typing
Code:
fastboot devices
A device number should appear. If nothing appears, it's a most likely driver problem. Click this button to know more.
Linux doesn't need drivers so try using fastboot in linux. If you really want to do it in windows, try PDANET drivers while connected in fastboot mode. No guarantees. I'm using a linux machine to specifically avoid this hassle
We're now gonna unlock your bootloader. Type
Code:
fastboot oem unlock
and confirm unlock by clicking volume up on your phone.
Reboot and go through all the necessary set-up.2. Download Magisk Manager from here and install the APK.
Make sure you download the latest apk version provided.
Note it says that Magisk itself is not yet installed.
We've only installed the helper app.
3. Flash Patched Boot Image
At this point you have two options: extract and patch your own boot image, or just use my patched boot image. I will assume you pick the second but this REQUIRES that you are on the same v13 06292017 official firmware. PM me if you want to do the first one. Download my patched boot image.
Download
Move the file to a known location that's easy to type (home directory or C Drive)
Reboot to fastboot mode, same as before
Flash with fastboot then reboot
Code:
fastboot flash boot /path/to/patched_boot.img
Code:
fastboot reboot
CONGRATS! Magisk should now be installed and along with it, Magisk's Superuser
Press thanks if it helped you! And/or leave feedback if it worked for you, and if your setup differed from mine. Thanks
MODS
B. Mods
1. Xposed Framework (systemless)
Install Xposed framework from within Magisk. Install API24.
Then reboot. This first boot takes really long. I pulled out my battery once, then the next time it successfully booted after a while.
Install topjohnwu's Xposed apk from his systemless Xposed thread.
It will tell you that Xposed is installed but not active yet.
Reboot one last time
2. Dolby Atmos (systemless)
Install from within Magisk. Confirmed working!
RECOVERY
Reserved
If you get fail operation
If you get
Code:
FAILED (remote:
Unlock operation is not allowed
)
Just go to Developer Settings > OEM Unlocking and enable it.
I used PDAnet for Windows and it worked
Nao Tomori said:
If you get
Code:
FAILED (remote:
Unlock operation is not allowed
)
Just go to Developer Settings > OEM Unlocking and enable it.
I used PDAnet for Windows and it worked
Click to expand...
Click to collapse
Oh yes, I forgot about that! Thanks. Will add and credit you
hi there bro. i just want to know, is there a custom rom that we can use for this phone? i have the same exact phone but i cannot find any articles about any other custom roms that has been used on this phone. hoping to hear from you. thanks.
And another thing, can we use TWRP for this phone?
Hello. Is there anyone here who has a clean stock rom for Starmobile UP Prime? The phone keeps popping up ads and redirecting to chrome/google play. Contact names sometimes disappear too. I ran the malwarebytes app and it said that "Settings" app is the malware. I downloaded and flashed another rom before (I forgot from what website), but same experience. Hoping for helpful response.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclamer
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
WARNING: The stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.
Prerequisites :
YOUR BOOTLOADER MUST BE UNLOCKED
How to unlock the bootloader :
1-enable oem unlock in the developer settings
2-reboot to fastboot [adb reboot bootloader] then issue this command [fastboot oem unlock]
note: this will wipe your data]
Click to expand...
Click to collapse
-If you have problems with the device drivers installed , you will need to install lg bridge, you can download it from here:
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=PWZO7A26B9UW
How to flash Twrp:
BOOT INTO FASTBOOT MODE:
With your phone off, connect your usb cable to your phone while holding VOLUME DOWN to boot into fastboot mode or just type [adb reboot bootloader] in the adb terminal
ONCE YOU ARE IN FASTBOOT MODE:
Open a command prompt and type "fastboot flash recovery <path_to_recovery.img>” without the quotation marks.
Example: fastboot flash recovery C:/Users/John/Desktop/recovery.img
[don't forget to extract the downloaded recovery zip to get the recovery.img]
WHEN THE FLASH COMPLETES: (Takes about 2 seconds)
On your phone, unplug the usb cable and power it off by taking out the battery and putting it back in.
BOOT INTO RECOVERY MODE FOR THE FIRST TIME
HOLD VOLUME DOWN + POWER until you see the LG logo and then temporarily release the POWER button, immediately pressing and holding it back down until you see the white prompt [factory reset] screen. You will NEVER release the volume down button in this process!
Use the hard keys to select "YES" and then "YES" again to boot into TWRP
How to Disable encryption and flash super su [Install Root]:
1. In TWRP, go to Wipe > Format Data. Enter the keyword ‘yes‘, in the provided space and enter. This will wipe the automatically encrypted filesystem, and decrypt it.
2. Once the wiping is done, reboot back into recovery. Go to Reboot > Recovery.
3. When the recovery boots again, connect your phone to the PC and Enable MTP under the Mount section.
4. Transfer the downloaded ‘no-verity-opt-encrypt-**.zip’ and ‘SR1-SuperSU-v2.78-SR1-20160915123031.zip to your internal storage or EXTSD
5. Disconnect the device now.
6. Tap on Install. Now, navigate your phone’s storage and select ‘no-verity-opt-encrypt-**.zip’. Finally swipe the ‘Swipe to confirm Flash’ button on the bottom of the screen.
7. The flashing process will merely take a few seconds. And when it’s done, follow the same method to flash the root package – SR1-SuperSU-v2.78-SR1-20160915123031.zip [/B]
Wait 1 or 2 minutes after the zip files are done flashing then reboot system and PROFIT! Your phone may take 3-5 minutes to boot the first time and it might boot-loop once or twice at the Metro PCS splash screen but don’t worry this is expected.
Click to expand...
Click to collapse
Downloads :
#1
https://www.mediafire.com/download/uxquk880q8pkurl
Additional Downloads :
SuperSU stable by Chainfire
dm-verity and force encryption disabler
Notice: After the TWRP splash screen you will see the option to type in the password to decrypt the filesystem just ignore it and press the cancel button.
Credits :
TeamWin, Me
Please hit the thanks button and conider to donate if you appreciate my work :highfive:
Paypal donation link: https://paypal.me/messi2050
What version of TWRP is this
brad2192 said:
What version of TWRP is this
Click to expand...
Click to collapse
Same as aristo 1
So, you made it from what source?
brad2192 said:
So, you made it from what source?
Click to expand...
Click to collapse
Are you investigating me :laugh: , ported it from my aristo 1 recovery.
messi2050 said:
Are you investigating me :laugh: , ported it from my aristo 1 recovery.
Click to expand...
Click to collapse
Just strange that a TWRP recovery just came out for the same device 2 hours previous to your post.
brad2192 said:
Just strange that a TWRP recovery just came out for the same device 2 hours previous to your post.
Click to expand...
Click to collapse
Ah actually is strange that the one you are talking about came directly after i posted on your topic saying I posted test twrp for aristo 2 on my blog (posted 4 days ago on my blog)
https://forum.xda-developers.com/showpost.php?p=75558782&postcount=16
https://messi2050.blogspot.com.eg
I was not aware of that friend, my apologies.
I'm having an issue, Instagram Twitter and Facebook refuse to update after using magisk, so I switched to SuperSU and I still have the same problem. The only way to get it to work is to remove root. I can't even connect to them through the browser it keeps saying failed to uodate
KyleBryant said:
I'm having an issue, Instagram Twitter and Facebook refuse to update after using magisk, so I switched to SuperSU and I still have the same problem. The only way to get it to work is to remove root. I can't even connect to them through the browser it keeps saying failed to uodate
Click to expand...
Click to collapse
That's probably because of adblock or similar sw
Tried it again no adblock and then google play services kept crashing I couldn't even add my account
Fixed it, forgot I had removed chrome and that was the issue for some reason
when i try to flash twrp i get the response "error can not load" plz. help
ive been having trouble flashing a rom to the aristo 2 because of the buildprop device values being incorrect. how can this be fixed?
messi2050 said:
Same as aristo 1
Click to expand...
Click to collapse
3.0.3.0
Trying this, I get an error "Failed to mount '/data' (No such device)"
tge101 said:
Trying this, I get an error "Failed to mount '/data' (No such device)"
Click to expand...
Click to collapse
Sounds like your partition table is hosed, brother.
Follow this post to restore your phone:
https://forum.xda-developers.com/showpost.php?p=76799751&postcount=91
tecknight said:
Sounds like your partition table is hosed, brother.
Follow this post to restore your phone:
https://forum.xda-developers.com/showpost.php?p=76799751&postcount=91
Click to expand...
Click to collapse
I got it restored eventually but im still having the same issur that made me try a factory reset in the first place. Half the time, i need to reboot for my phone to charge and some of those times the notifications that its charging and that debug is on stay in the status bar. Im at my wits end.
I just grabbed an Aristo 2 and though I don't know how long I'll have it, in my free time ( which is limited ) I'm going to be working on getting a full rom package with kernel compiled. What would you guys like to see? I primarily focus on flagships, and this is definitely a budget device but it's been working well for me despite the snapdragon 425 and only 2gb ram...I'd like to see some development for this thing and though I've only spent about 20 minutes looking around on xda it seems it's very limited (which is to be expected)...Can someone give me a brief rundown on where we are with the device and what yet needs accomplished to be ready for a compile? Are sources available (kernel source, etc)? I thought I read back in another post (messi2050?) that some sources had been obtained? I'm going to go back over it and see what else is needed....do we have defconfig and whatnot to build? Any info you guys can paraphrase will make this all a lot faster since I've got very limited time to research but access to a poweredge r330 blade with 32GB and a 3.4ghz octa to compile on....I've already set up the VM with linux and am waiting to see what else I find that I'm going to need and decide on a build (lineage, cm, stock rooted, etc) before I take the time to download android source....I've only got a 50mbps line coming into the server so a 40gb source download isn't exactly fast and I work construction so I'm in and out but never seem to have EXTENDED periods of time to sit down and burn the keyboard up....
Thanks guys....I'm about to install Tapatalk on the device and I'll be out-n-about checking on jobs in the field but if anyone wants to DM me and bring me up to speed I'll be sure to reply....In the meantime as time allows I can remote the server at the office if need be....
-Rx8driver
I've also noticed that driver issues are pretty noticeable using win10 in fastboot mode...i had to load the Google driver manually to get fastboot mode working... if you're having issues take a close look thru the device manager and make sure the lg driver is properly loaded when the device is in fastboot and download modes if you're running win10...
Sent from my LM-X210(G) using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to Root Samsung Galaxy M12 ( Without TWRP )
Warning :
This will certainly delete all your files. Make a backup of what you consider important and do at your own risk.
Ok Now lets start to root your Samsung Galaxy M12 :
-- Unlock Bootloader
Unlock Bootloader :
Requirements
- PC
- Backup All Important Data
1. Go to settings > about phone > software information > tap build number seven times to unlock developer options
2. Now go back to settings and open developer options and turn on oem unlocking and usb debugging
3. Now turn off Your phone
4. Connect Your usb cable to pc and press both volume buttons and insert Your usb cable to phone instantly
5. You will get blue colour screen
6. long press volume up to unlock bootloader and press volume up ( yes )
Now your phone will be formatted, After that phone will turn on and do Setup. Make sure you connected to Wifi or you have mobile data.
Now :
1. Unlock/Enable Developer Options Again
2. Check is there's Grayed OEM Unlock Options
3. If No OEM Unlock Options in Developer Settings, Close settings app from Recent Apps, and wait 1-5 minutes,
4. Check Developer Settings again
5. If there's a "Grayed" OEM Unlock Options in Developer Settings.. Your bootloader is unlocked
-- Flashing Root Files
Flashing Patched Boot Image :
Requirements
- PC
- Odin Software
- Unlocked Bootloader
- Drivers of Samsung Phone
- Patched Boot Image ( TAR Format )
1. Download RootM12.tar
2. Now turn off Your phone, Connect Your usb cable to pc and press both volume buttons and insert Your usb cable to phone instantly
3. Now Press Volume Up ( Download Mode )
4. Go to Options in ODIN Software and Make Sure Options turned on only "Auto Reboot" and "F Reset Time"
5. Open Odin Software in Your PC and Add M12Root.tar in AP Block and Your Phone will automatically Reboot
6. Open Magisk App and Do Additional Setup
7. Reboot and Now your phone is Rooted
If you need help or this method not working for you, let me know with replying this thread
Ah also No Hardbrick chance of doing this
And Thanks!
Some Link
RootM12.tar
drive.google.com
Click to expand...
Click to collapse
ErukunBAKA said:
1. Download RootM12.tar file attached below
Click to expand...
Click to collapse
What file??
Badger50 said:
What file??
Click to expand...
Click to collapse
Ah Wait sir.. I Remember i've upload the files.. Maybe because My Internet Rip .. I'll try Attach Files again or add link
Edit : Added GDrive Link sir
Should be feasible?
This method is not working and is not transparent at all. Please guide us on how to patch the boot and vbmeta ourselves. As you cannot possibly create the patched boot and vbmeta for all the firmware builds nor you have mentioned which build this patched boot belongs to.
I have been trying to root M12 with the official magisk way but it is ending up in boot loops. Any ideas on how we can genuinely root this phone?
ankush1492 said:
This method is not working and is not transparent at all. Please guide us on how to patch the boot and vbmeta ourselves. As you cannot possibly create the patched boot and vbmeta for all the firmware builds nor you have mentioned which build this patched boot belongs to.
I have been trying to root M12 with the official magisk way but it is ending up in boot loops. Any ideas on how we can genuinely root this phone?
Click to expand...
Click to collapse
No Same problem with me too, I think we have to wait for some custom recovery and custom rom to be build for the M12, until than we can not do any thing, please do not try to force the root as it will be result in bricked device.
Hello
I am not a programmer and my knowledge of android is little , but from what I understand in this topic below , what is there also works on the galaxy M12
[ROOT] Modified Magisk for Galaxy A21S (R)
It seems that the A21S hasn't had any root since it was released (other than pre-rooted GSI ROMS) When flashing Magisk, the phone went into bootloop, and the only way to fix it was to flash stock rom via Odin. After some analysis, it seems that...
forum.xda-developers.com
Please read the replicas
ps: I think I should create a new topic on the matter put by me ...
M12 F bricked successfully!
Weverton Dev said:
M12 F bricked successfully!
Click to expand...
Click to collapse
Hi
You should have read this topic carefully, especially the replicas.
The method of this topic does not work!!!
On the other hand, what problem is your phone in? So someone here can help you
Sorry for the big letters but it's like warning to other people
ErukunBAKA said:
View attachment 5293105
How to Root Samsung Galaxy M12 ( Without TWRP )
Warning :
This will certainly delete all your files. Make a backup of what you consider important and do at your own risk.
Ok Now lets start to root your Samsung Galaxy M12 :
-- Unlock Bootloader
Unlock Bootloader :
Requirements
- PC
- Backup All Important Data
1. Go to settings > about phone > software information > tap build number seven times to unlock developer options
2. Now go back to settings and open developer options and turn on oem unlocking and usb debugging
3. Now turn off Your phone
4. Connect Your usb cable to pc and press both volume buttons and insert Your usb cable to phone instantly
5. You will get blue colour screen
6. long press volume up to unlock bootloader and press volume up ( yes )
Now your phone will be formatted, After that phone will turn on and do Setup. Make sure you connected to Wifi or you have mobile data.
Now :
1. Unlock/Enable Developer Options Again
2. Check is there's Grayed OEM Unlock Options
3. If No OEM Unlock Options in Developer Settings, Close settings app from Recent Apps, and wait 1-5 minutes,
4. Check Developer Settings again
5. If there's a "Grayed" OEM Unlock Options in Developer Settings.. Your bootloader is unlocked
-- Flashing Root Files
Flashing Patched Boot Image :
Requirements
- PC
- Odin Software
- Unlocked Bootloader
- Drivers of Samsung Phone
- Patched Boot Image ( TAR Format )
1. Download RootM12.tar
2. Now turn off Your phone, Connect Your usb cable to pc and press both volume buttons and insert Your usb cable to phone instantly
3. Now Press Volume Up ( Download Mode )
4. Go to Options in ODIN Software and Make Sure Options turned on only "Auto Reboot" and "F Reset Time"
5. Open Odin Software in Your PC and Add M12Root.tar in AP Block and Your Phone will automatically Reboot
6. Open Magisk App and Do Additional Setup
7. Reboot and Now your phone is Rooted
If you need help or this method not working for you, let me know with replying this thread
Ah also No Hardbrick chance of doing this
And Thanks!
Click to expand...
Click to collapse
How to backup data
Star_xda said:
How to backup data
Click to expand...
Click to collapse
Use cloud storage or your personal computer