Related
First off, i'm sorry if the title is misleading and/or belong in the wrong part of this forum.
So, I'm late to the party, just got myself a Z5 E6653 and when I look for guides on how to obtain root they kind of out-of-date. So i'm here to make sure the path I choose to follow will be the correct one as I dont want to lose my TA partition. As far as I know, according to this guide to back up my TA partition I have to downgrade to Lollipop, but I found something interesting about backing up TA partition on Marshmallow using dirtycow method (sorry Nougat users).
So, the steps I'm proposed is, if my device is already on stock MM unrooted, locked bootloader.
1. Go here Sony cross-devices development and download file called backupTA_v2.zip this shouldnt makes us need to downgrade
2. Run the BackupTA.cmd file if you're on windows
3. There will be errors about dirtycow failed but the script automatically retry, me myself got screen-full of retries before the script actually backed up my TA partition and you'll be presented with .imgfile called TA_devicemodel_somenumbers_timestamp.img about 2MB in size (am i correct so far? this is why i want to make sure this will work)
4. Save your file in a very secure place.
That concludes the Backup TA part of rooting process am I on the right path so far?
To get unlocked bootloader according to this :
Given that you have downloaded flashtool and installed the drivers in the \drivers folder in flashtool installation
!!THIS WILL WIPE ALL DATA!!
1. Click the BLU button at top then open Sony developer website
2. Select device and follow instruction until you get a key
3. Paste the key to flashtool
4. THAT'S IT?
Now after this we can use fastboot command to flash kernel and the kernel includes recovery.
Are these steps correct so far?
I might as well add these here.
To get kernel and recovery up and running, I'll be taking androplus kernel for example, I'm assuming it works with stock ROM.
1. Get the kernel .zip here at Androplus homepage
2. And download latest TWRP recovery from androplus download page, at this time of writing it should be TWRP-3.0.2.2-e6653.img
3. Notice that it's in .zip format which we cannot use yet since we don't have custom recovery.
4. Open the zip file you just downloaded and you should see boot.img That's your brand new shining kernel, extract it outside put it in a folder along with your favorite fastboot.exe file
5. Go to fastboot, as far as I know you go to fastboot by turning off the device -> hold volume down then plug USB cable. (see note)
6. First, according to Androplus page, flash the kernel first using the command
Code:
fastboot flash boot boot.img
7. Then the recovery
Code:
fastboot flash recovery TWRP-3.0.2.2-E6653.img
8. Reboot by unplugging the USB cable
Note: some interesting thing I found while trying to enter fastboot or flashmode that it might not work if your USB port is powered How to tell if your port is powered? I'm not sure. You will have to change port and hope for the best ^_^
Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!
sceryavuz said:
Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!
Click to expand...
Click to collapse
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?
webslasher said:
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?
Click to expand...
Click to collapse
LineageOS, CarbonROM, eXistenZ, SunKernel..
Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min
sceryavuz said:
LineageOS, CarbonROM, eXistenZ, SunKernel..
Click to expand...
Click to collapse
I will try Existenz as I want to keep it stock looking, thanks!
bosquarid said:
Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min
Click to expand...
Click to collapse
I'm glad to find someone that is going to go through these procedures too! I will also proceed to unlock my bootloader what rom and kernel do you plan to flash?
Hi, thanks for this. I just got the Z5 today so my first port of call was coming here and finding out how to root it. I previously had the Z2 and Z2 tablet which I rooted last year with the help of the members here, I hope the process for this isn't too different for this one. I think I forget more than I remember so the guide is helpful.
About time that means that the Stylo 3 Plus is knocking on our door step @ our local retail MetroPCS Stores and i will be going to purchase soon as its released.
QUOTE=xxbabiboi228xx;72292409]Ok these are the steps on how i kept Root from Marshmallow 2 Nougat
1.I used LGUP and flashed the Stock MS55010R.kdz to get back to bare bones stock.
2.Then i went to Settings, Date and Time Unchecked Auto Date & Time Changed the Time to 11:30 P.M then About Phone, System Updates if it doesnt show the Update right off hand you have to keep messing with it atleast 5 times or more times then it will finally show the 7.0 Update File size is like 1 thousand something something mb.
3.I kept the Fastboot OEM Unlocked Enabled the whole time I did not change it back to Fastboot OEM Lock after i flashed back to bare bones stock with the LGUP MS55010R.kdz
4.Then i used what i used with the Marshmallow Roms to Flash the Custom Recovery TWRP
5.Make sure Usb Debugging is Enabled and also in the settings Fingerprint & Security make sure Unknown Sources is check and the one underneath it is unchecked B4 you click on All-In-One-Tool v4 (mini).exe all you have to do is hit enter it will make your phone reboot into the bootloader after you allow and pair the debugging mode on your phone it will flash the custom recovery for you.
6.After it finishes pull your battery hold down the power and volume down release power to go into the custom recovery wipe data reboot to recovery.
7.Flash SuperSU then Flash No Verity Opt Encrypt 5.1 Now your rooted.[/QUOTE]
Hope this Helps The XDA Community in anyway
How i learned was just READ thats all you have to do (READ!!!)
All-In-One-Tool v4 (mini).exe Modded by me I Added MetroPCS MS550 Lg Stylo 2 Plus 3.0.1.0 TWRP Recovery and Themed it with AIK and a Terminal emulator.Materialised Light Play.
Deleted the boot/recovery.img/Update.zip which was the SuperSu but an older version that was used when this Mod was made.
ONE CLICK CUSTOM RECOVERY FLASHING PROGRAM (TWRP)
All-In-One-Tool v4 (mini)
https://drive.google.com/file/d/0B7nOJ0l6RQfmNEtremNvTkdVTGM/view?usp=drivesdk
T-Mobile today roll out nougat for LG K550 and K550BN download and enjoy new software <3
Step 4 should be split into Steps 5, 6, 7 etc.
xxbabiboi228xx said:
Ok these are the steps on how i kept Root from Marshmallow 2 Nougat
1.I used LGUP and flashed the Stock MS55010R.kdz to get back to bare bones stock.
2.Then i went to Settings, Date and Time Unchecked Auto Date & Time Changed the Time to 11:30 P.M then About Phone, System Updates if it doesnt show the Update right off hand you have to keep messing with it atleast 5 times or more times then it will finally show the 7.0 Update File size is like 1 thousand something something mb.
3.I kept the Fastboot OEM Unlocked Enabled the whole time I did not change it back to Fastboot OEM Lock after i flashed back to bare bones stock with the LGUP MS55010R.kdz
4.Then i used what i used with the Marshmallow Roms to Flash the Custom Recovery TWRP
5.Make sure Usb Debugging is Enabled and also in the settings Fingerprint & Security make sure Unknown Sources is check and the one underneath it is unchecked B4 you click on All-In-One-Tool v4 (mini).exe all you have to do is hit enter it will make your phone reboot into the bootloader after you allow and pair the debugging mode on your phone it will flash the custom recovery for you.
6.After it finishes pull your battery hold down the power and volume down release power to go into the custom recovery wipe data reboot to recovery.
7.Flash SuperSU then Flash No Verity Opt Encrypt 5.1 Now your rooted.
Click to expand...
Click to collapse
Hope this Helps The XDA Community in anyway
How i learned was just READ thats all you have to do (READ!!!)
All-In-One-Tool v4 (mini).exe Modded by me I Added MetroPCS MS550 Lg Stylo 2 Plus 3.0.1.0 TWRP Recovery and Themed it with AIK and a Terminal emulator.Materialised Light Play.
Deleted the boot/recovery.img/Update.zip which was the SuperSu but an older version that was used when this Mod was made.
ONE CLICK CUSTOM RECOVERY FLASHING PROGRAM (TWRP)
All-In-One-Tool v4 (mini)
https://drive.google.com/file/d/0B7nOJ0l6RQfmNEtremNvTkdVTGM/view?usp=drivesdk
Where did you find the stock MS55010R.kdz ? i can't seem to find that anywhere. also where do you find the .dll for the lgup tool?
There's no need to do it the way op did. Download LG Bridge from LG's official site, power up phone into bootloader, flash stock.
greentag said:
There's no need to do it the way op did. Download LG Bridge from LG's official site, power up phone into bootloader, flash stock.
Click to expand...
Click to collapse
Of coarse but at the time i wrote this they didnt have 7.0 on LG Bridge tried and tried through bridge it was a no go at that point in time.
xxbabiboi228xx said:
Of coarse but at the time i wrote this they didnt have 7.0 on LG Bridge tried and tried through bridge it was a no go at that point in time.
Click to expand...
Click to collapse
They didn't when I reflashed mine. I just did a fresh flash of 6.0, and waited for the update to kick in.
Can you post a link to the DLL and KDZ for LGUP please. I'm sure all of us would be greatly appreciative if you did
sephiroth878 said:
Can you post a link to the DLL and KDZ for LGUP please. I'm sure all of us would be greatly appreciative if you did
Click to expand...
Click to collapse
Ok Time to break out the Laptop for you guys
After you install LGUP on your PC look in your C: Programs Folder if you have a 64 bit PC you will look in your C: Programs x86 Folder for LG Electronics Folder open it there you will see the LGUP Folder open it until you find the Model Folder there you will place the Common Folder i provided you with in this setup. Now your PC should recognize your phone but first b4 you start the LGUP Program you need to Power off your phone and hold volume up and plug your phone in thus will put your phone into Download Mode. Now you can Start the LGUP Program.
I supplied the .zip with these Installation instructions also
Where you will find the 10r firmware
http://android.gl/download-lg-stylo-2-plus-t-mobile-k55010r-metropcs-ms55010r-android-6-0-1-kdz.html
Please save the update before applying
xxbabiboi228xx said:
After you install LGUP on your PC look in your C: Programs Folder if you have a 64 bit PC you will look in your C: Programs x86 Folder for LG Electronics Folder open it there you will see the LGUP Folder open it until you find the Model Folder there you will place the Common Folder i provided you with in this setup. Now your PC should recognize your phone but first b4 you start the LGUP Program you need to Power off your phone and hold volume up and plug your phone in thus will put your phone into Download Mode. Now you can Start the LGUP Program.
I supplied the .zip with these Installation instructions also
Where you will find the 10r firmware
http://android.gl/download-lg-stylo-2-plus-t-mobile-k55010r-metropcs-ms55010r-android-6-0-1-kdz.html
Click to expand...
Click to collapse
If anyone can please save the nougat update and put it on your desktop or something before actually applying it so that we can all have nougat instead of waiting for metro to push it? I have tried these steps for the past few days with no avail, and I think it has to do with with the staggering of updates so their server doesn't overload pushing it out to everyone. That would be greatly appreciated
Does this work on 7.0?
As of right now, I just installed Supersu and got root again and am currently setting my phone back up and the 7.0 update appeared. Can I just install the 7.0 update and still have Root or no? If not please let me know what I have to do to keep root. Thank you
you have to be unrooted to take the update
Reudabae said:
As of right now, I just installed Supersu and got root again and am currently setting my phone back up and the 7.0 update appeared. Can I just install the 7.0 update and still have Root or no? If not please let me know what I have to do to keep root. Thank you
Click to expand...
Click to collapse
You have to be completely stock and take the 7.0 update, then afterwards you can re-root with ease.
thành viên
Hello brother . I am a Vietnamese using lg stylo 2 plus home network metro pcs. But I can not use metro pcs in Vietnam. I hope you help unlock the machine to use as international version. thanks so much. : O: O: O: O: O: O: O: O
Look on your phone under a set of Metro PCS apps. There should be one with a key on it called unlock or something like that. Open it up and go through the steps and see if it's allowed to be unlocked by Metro. If that doesn't work then I would try calling Metro and ask them to unlock it. Tell them you're going to Vietnam for a month and need to use your phone. Good luck brother
Thành viên
tech15 said:
Look on your phone under a set of Metro PCS apps. There should be one with a key on it called unlock or something like that. Open it up and go through the steps and see if it's allowed to be unlocked by Metro. If that doesn't work then I would try calling Metro and ask them to unlock it. Tell them you're going to Vietnam for a month and need to use your phone. Good luck brother
Click to expand...
Click to collapse
thank you. But I contacted and the network operator did not unlock me. Is there no way to crack it?
---------- Post added at 12:42 AM ---------- Previous post was at 12:32 AM ----------
Everybody. Help with.
I'm not sure
Updates are pushed down under the method there is a new update as of 8-17-2018 so if you like please read, thanks
if anyone needs hep with their V20 and ran into an issue with my video/Post feel free to message me here or my facebook page at www.facebook.com/laser452
------------------------------Alpha ROM------------------------------
https://youtu.be/1U4XB8KGGZA
So I found a cool ROM you all should try, i made a small review and all for fun the video is not a tutorial, for those who don't know how to install the ROM i did show at the end how to do it
so as always thank the dev, the creators who made this ROM possable
https://forum.xda-developers.com/v20/development/rom-vs995-alpha-rom-v1-1-t3709727
---------------------------DeBloat VS995---------------------------
thermal MOD (phone less laggy)
https://forum.xda-developers.com/v20/themes/mod-fix-cpu-throttling-charging-gaming-t3650705
link2SD
https://play.google.com/store/apps/details?id=com.buak.Link2SD&hl=en
Es File Explorer
https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
---------------------------(Downgrade 15A to 13A)---------------------------
16A and 17A will work for this method 18A is unknown
Upper CUt plus LGUP tool
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
13A KDZ
https://www.mylgphones.com/veirzon-...tock-kdz-firmware-available-for-download.html
driver
https://drive.google.com/file/d/0BwHeBLVyhdWoUlg0d01ueWZfTzQ/view
i had a common file from my v10, i do not know if this is important if so i upload the file
---------------------------(root method)---------------------------
I am back with a new Phone the LG V20, so lets get her rooted and ready to go with some awesome videos
this post will have other methods added to it so i dont have more then one post everywhere
(please note i am running on VS99512A downgraded from 13A. i do not know if this will work on 13A or 14B and have no plans to test this. please ask others, if i see it is possible to root 13A and 14B or later i would not mind to make videos. i make a downgrade from 13A to 12A for those who needs help, just install LGUP and uppercut and it should work fine from there
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
enjoy)
method 1 (root method dirty Santa)
remember i DO NOT TAKE CREDIT for these methods, i make videos to help others understand these methods, please thank the devs
sites used in this video/post
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
http://highonandroid.com/android-root/how-to-root-lg-v20-attsprintverizonkorean/
so as always i always make long ass videos so i will post the steps here if you are one of those who loves to read then watch a video
Tip of the post XD
having issues with power button not locking your screen, i have found a way to get it unstuck, hold vol. up and power a few times it should work then. your welcome
(video)
Subscrib to my channel for more
https://www.youtube.com/user/lasertechcomputers
1. you need the files
- v20-root.zip
https://www.androidfilehost.com/?fid=457095661767122821
- TWRP
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-us996.img
- Terminal Emulator
use phone ------> https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
if you are lazy to sign into google -----> https://drive.google.com/open?id=0BwHeBLVyhdWoTHZ0N1BKTFdHc00
(note unknown sources must be checked)
- Newest SuperSU(SuperSU v2.78 SR5 or greater is needed)
-latest SU -----> https://forum.xda-developers.com/apps/supersu
-SU 2.78 ----> https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
-fastboot
http://download.highonandroid.com/file/Tools/fastboot.zip
-usb driver fastboot
http://download.highonandroid.com/file/Drivers/usb_driver.zip
-LG V20 VS995 drivers (verizon)
https://drive.google.com/open?id=0BwHeBLVyhdWoUlg0d01ueWZfTzQ
-the guy who helped -please thank the guy who sent me the link to make it easy -
https://forum.xda-developers.com/v20/help/vs995-rooted-2-issues-t3617982/post72574087#post72574087
-kernel MAIN POST (thank the dev for making it)
https://forum.xda-developers.com/v20/development/kernel-restock-stock-based-kernel-v20-t3556263
(UPDATE ON ROOT FILES) 3-25-2019
I have updated the root folder to root files (AIO).zip. this will have everything to root your phone, nothing dose not have to be move other then moving the folder to where you like it to be at. enjoy
IN CASE SOMETHING IS BROKEN HERE IS A BACKUP OF ALL FILES
I do not take credit of these files and have uploaded them to my g-Drive incase a link is broken,
https://drive.google.com/open?id=0BwHeBLVyhdWoMk5SOEtYd1YtY2s
2. since you have all files lets get to it
A. first extract the fastboot zip,
B. extract files in the v20-root zip to fastboot folder
C. extract TWRP to fast boot folder
D. install the v20 drivers
E. copy SU and Kernel to root of SD card (DO NOT USE INTERNAL)
F. install Terminal Emulator
G. G for good luck if you hit that thanks button to the devs and who all helped
3. once you have got everything set now go to settings/about phone/software/ hit build number
till you see a message saying you are now a dev.
4. back out to the main settings menu and you will see developer options
5. check USB De Bugging
6. plug in phone
A. in the fastboot folder hold shift and right click anywhere that is blank
B. click open command window here (you will need this)
7. Run RUNME.BAT (DO NOT CLOSE THIS WINDOW) then click step 1.bat
8. open Terminal Emulator. type in the info
id (press enter)
you get a message, look for untrusted_app (dirtysanta has an imamge on the post)
type
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
9. once done look at the RUNME CMD window, once you see run step 2.bat double click it
10. your phone will boot into fast boot
A. SKIP to 11. if you did not see the message waiting for device
B. go to control panal/device maneger
C. look for the yellow triangle (should say android or ADB i dont remember)
D. right click on it and click Update driver software
E. browse my computer for driver software
F. Let me pick from a list of device drivers on my computer
G. Have disk
H. browse ad go to where you have the usb driver
I. click android_winusb then click open
J. hit ok then click android ADB interface then hit next
11. run step 3.bat. once phone reboot you need to hold the vol down till you are in fastboot again
12. once back on fast boot enter each of these codes (do not try to copy all codes and paste them.
please do one at a time
fastboot flash boot bootbackup.img
fastboot flash recovery twrp-3.0.2-1-us996.img
fastboot flash boot bootbackup.img
fastboot reboot
13. after you type in fastboot reboot hold the vol down and power button down. once you see the LG logo, let go of the power button then hold it down again
14. you are now in TWRP, press cancel then swipe to modify
A. go to wipe
B. tap format data
C. type yes and hit enter
D. hit the home key then go to install
E. change storage to micro SD card and install SU
F. go back to install and install the kernel (verizon restock)
G. go to wipe. tap advanced wipe. check dlvik cache and then check cache. the swipe to wipe
H. reboot system
15. DO NOT TOUCH PHONE let it sit there till it loads into the welcome screen (takes about 5 or 10 min)
there you now have root, enjoy
---------------------------(UPDATE SECTION)---------------------------
---------------------------(Update 8-17-2018)---------------------------
Sup everyone, sorry i was not on for months, i am back, there is a video in my YouTube channel explaining where i been. im sure you all missed me so here i am, i am back
my channel is not going to be for only Cellphones, i am doing alot more then that but i will be here to help you out when you need it. thank you all for the support
---------------------------(update 8-14-2017)---------------------------
if anyone is wondering where is the debloat video, incase if you are not looking on my YT channel i have to pospone that video cause of major issues with this phone, i rather work on it and make sure it works for you guys then to get loads of HATE MAIL!!!! lol so i am sorry it is taking forever for a video to come out, i got someone helping me with some advice and working on it as we speak, plus this phone is kinda picky to what has been removed/frozen.
once all the BS is done and overwith you all will see an update here and on my YT channel and facebook page
i want to thank @bond32 for giving me advice and helping me with questions i have for this phone
lets give a big thanks to @me2151 for the root method and all the help he gave us, if it was not for him, this phone would just be a POS and no fun to us all. me2151 has posted a post that he is moving on and i shoot the link, make sure you all thank him for the awesome hard work that was done and to others that was into the root
https://forum.xda-developers.com/v20/how-to/fun-goodbye-v20-t3656059
Nice! I'm sure newcommers will appreciate this post a ton. Just a note, the exploit WILL work on 13a, but it WILL NOT work on 14b. If someone has the 14b firmware, they aren't screwed - simply use the KDZ restore to downgrade to either 13a or 12a. Note: when doing this, data WILL NOT be wiped - your phone will have a ton of force closes. I recommend in this case to try to get to the backup in settings and do a factory reset because the FC's will not let you get to terminal emulator to do the exploit. Factory reset to start fresh, then enable debugging, etc.
bond32 said:
Nice! I'm sure newcommers will appreciate this post a ton. Just a note, the exploit WILL work on 13a, but it WILL NOT work on 14b. If someone has the 14b firmware, they aren't screwed - simply use the KDZ restore to downgrade to either 13a or 12a. Note: when doing this, data WILL NOT be wiped - your phone will have a ton of force closes. I recommend in this case to try to get to the backup in settings and do a factory reset because the FC's will not let you get to terminal emulator to do the exploit. Factory reset to start fresh, then enable debugging, etc.
Click to expand...
Click to collapse
Ive been looking all day to see if I can just kdz to 13a. I now have plans after work. Thank you!
Ruttedbeez said:
Ive been looking all day to see if I can just kdz to 13a. I now have plans after work. Thank you!
Click to expand...
Click to collapse
Nice, glad to help. Don't forget, your phone will likely go cray with all the force closes so you may want to just factory reset after the KDZ completes. Also, if/when you do that, after it is back to the point where you set the phone up, just get past the initial setup as quickly as possible then put the phone in airplane mode - this will keep it from trying to load the 300 apps as well as prevent Verizon's bloat crap from downloading Candcrush, garbage, [insert unwanted app here], etc. Then just enable usb debugging, install terminal emulator, and you're good to proceed with the exploit.
Personally (and I DO NOT recommend this), I've gone back and forth so many times I've lost count between stock/unroot and root. I am actually able to restore a backup from right after installing TWRP and rebooting by jumping straight into TWRP after installing TWRP image and formatting data. It has worked a number of times now.
I really only need root access for adblocking and ViperAudio.
Thanks again OP!
bond32 said:
Nice, glad to help. Don't forget, your phone will likely go cray with all the force closes so you may want to just factory reset after the KDZ completes. Also, if/when you do that, after it is back to the point where you set the phone up, just get past the initial setup as quickly as possible then put the phone in airplane mode - this will keep it from trying to load the 300 apps as well as prevent Verizon's bloat crap from downloading Candcrush, garbage, [insert unwanted app here], etc. Then just enable usb debugging, install terminal emulator, and you're good to proceed with the exploit.
Personally (and I DO NOT recommend this), I've gone back and forth so many times I've lost count between stock/unroot and root. I am actually able to restore a backup from right after installing TWRP and rebooting by jumping straight into TWRP after installing TWRP image and formatting data. It has worked a number of times now.
I really only need root access for adblocking and ViperAudio.
Thanks again OP!
Click to expand...
Click to collapse
I just got the phone 3 days ago so a factory reset isnt gonna bother me much. And good idea on the airplane mode wouldny have thought of that.
bond32 said:
Nice! I'm sure newcommers will appreciate this post a ton. Just a note, the exploit WILL work on 13a, but it WILL NOT work on 14b. If someone has the 14b firmware, they aren't screwed - simply use the KDZ restore to downgrade to either 13a or 12a. Note: when doing this, data WILL NOT be wiped - your phone will have a ton of force closes. I recommend in this case to try to get to the backup in settings and do a factory reset because the FC's will not let you get to terminal emulator to do the exploit. Factory reset to start fresh, then enable debugging, etc.
Click to expand...
Click to collapse
thank you for that info i was not sure of 13A but i ake sure to add it to my video. glad this helped people i love to make videos and help others out in need, i deal with the hard work trying to understand how a method works and once i get it going i show all steps that are missing (i know they wont add it cause as you see my video is long hehehe) but i dont mind doing it, gives me somthing to do and its somthing i love doing
thank you for that info that is a big help there, i be making more videos and will be updating this post as a new video is uploaded, i will try to get one this week for debloating apps off the phone, i am still messing around with freeing apps cause here and there i seen a few screw ups and trying to study it before all is final on a video
Ruttedbeez said:
Ive been looking all day to see if I can just kdz to 13a. I now have plans after work. Thank you!
Click to expand...
Click to collapse
hope you get it all working, if you want more videos adn want to keep up to date on this phone, feel free to subscribe to my chanel
I subscribed, good stuff! Thanks for putting all that together, I'm sure it will be helpful.
You should make a video or guide about debloating apps, there are plenty out there but sometimes people are really wanting to know about their specific phone model.
Subscribed. Thanks for this.
Sent from my VS995 using Tapatalk
bond32 said:
I subscribed, good stuff! Thanks for putting all that together, I'm sure it will be helpful.
You should make a video or guide about debloating apps, there are plenty out there but sometimes people are really wanting to know about their specific phone model.
Click to expand...
Click to collapse
i do have plans to make a debloat video but i have a trip coming up. good news is when i debloated my phone i had no issues like i did before so that is one thing why i have not made a video. a debloat video will be up at the end of this month or next month. thanks for subscribing to my channel
moejoe88 said:
Subscribed. Thanks for this.
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
thanks and you are welcome more videos be up later end of this month or next month
I think I could use some help. I got all the files flashed and rebooted the phone and now my screen is flickering and freaking out and the phone is constantly vibrating. everything went well through all the steps until I typed it fastboot reboot.
EDIT: Got back into fastboot and retyped typed the last few lines and I think I got that fixed. I think I'm still having a slight problem. Phone vibration wont turn off now while phone is running. ideas?
EDIT: Vibration turns off when I turn the screen off so I guess I got that semi fixed. Is that normal?
DELETED...
Is this phone unlocked by default for international use?
Sent from my Redmi Note 4 using Tapatalk
jmcnabb2 said:
I think I could use some help. I got all the files flashed and rebooted the phone and now my screen is flickering and freaking out and the phone is constantly vibrating. everything went well through all the steps until I typed it fastboot reboot.
EDIT: Got back into fastboot and retyped typed the last few lines and I think I got that fixed. I think I'm still having a slight problem. Phone vibration wont turn off now while phone is running. ideas?
EDIT: Vibration turns off when I turn the screen off so I guess I got that semi fixed. Is that normal?
Click to expand...
Click to collapse
sorry i didnt reply in forever, i dont get a email or anything when people post on here unless i been quated, i hope your v20 is rooted, if not feel free to message my facebook page
www.facebook.com/laser452
just make sure your phone is a vs995 cause thats what phone i use and all i know as i dont own other v20s, if i did i be more of help
ankurcshah said:
Is this phone unlocked by default for international use?
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
i went to the Netherlands with my vs995 and had no issues, i was using Verizon tho with there travel pass
@LASERWOLF452 Hi. I am using an HTC 10 on Verizon. I'm thinking about buying a refurbished LG V20, and would like to know if I can just swap my HTC 10 SIM card into a V20 and be good to go on Verizon? After that I would want to root the V20 following your guide here.
Zoandroid said:
@LASERWOLF452 Hi. I am using an HTC 10 on Verizon. I'm thinking about buying a refurbished LG V20, and would like to know if I can just swap my HTC 10 SIM card into a V20 and be good to go on Verizon? After that I would want to root the V20 following your guide here.
Click to expand...
Click to collapse
Yes you can just put your Verizon Sim card from your HTC 10 in a Verizon or Unlocked V20 and all will work.
Zoandroid said:
@LASERWOLF452 Hi. I am using an HTC 10 on Verizon. I'm thinking about buying a refurbished LG V20, and would like to know if I can just swap my HTC 10 SIM card into a V20 and be good to go on Verizon? After that I would want to root the V20 following your guide here.
Click to expand...
Click to collapse
Yes it will work
After unlocking the bootloader using the dirty santa tutorial, if I reinstall KDZ stock for my cell phone, I still have the bootloader unlocked so I can later install Custom and root?
***WARNING***
This is ONLY for the H910. If you flash H915 firmware on an H918 -- you WILL brick it.
If you are currently on Oreo, you can root your phone, but you CAN NOT keep Oreo - for now. This will downgrade you back to Nougat, which is rootable.
I know this is a long post, but this is also a complicated root procedure. Please read the ENTIRE post before starting.
Also, if you run into a problem, please use the search thread box to see if your problem has already been addressed. It will save having to ask the same questions over and over.
If you want to restore to stock v10q after rooting, you can use this: link.
Standard disclaimer: There are no guarantees in life. No part of this should brick your phone, but if it does somehow, that is on you.
This should work on any H910 version, up to v20g, that is no longer rootable by DirtySanta (IE: dirtycow has been patched). It has been tested on 10m to 20g
Make sure that you have an SD card that has at least 8 gigs of free space. It CAN NOT be formatted FAT, or FAT32. It needs to be exFat or ext4, otherwise the zip won't fit (2 gig file limit on FAT and FAT32).
Make sure you have a working adb environment. I use Linux so hopefully this is a good resource. If not, you will have to Google this yourself: link.
Make sure that you have a working WiFi connection. Part of this process involves installing a terminal emulator. Since the phone will have no signal at that time, you use WiFi, or you can side load.
Download the H915 v10e KDZ: H91510e_00_VTR_CA_OP_1205.kdz.
- WARNING: Do not use any newer H915 firmware, as they all have dirtycow patched (v10p, v10q), and I do not know if they increment ARB.
- If they do increment ARB, then you will be stuck with a phone that can't be rooted, and you can't fix the modem! You have been warned.
Download the patched LG UP from this thread: link.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Put your phone into download mode (power off / hold vol. up / plug in USB cable)
Use LG UP to dump your phone. When you run it, there will be additional radio buttons.
- Pick the one that says DUMP and click Start. You will be asked what partitions to dump, click the "select all" checkbox, and then you can uncheck userdata.
- This is an OPTIONAL but HIGHLY recommended step. It is a good idea to have a full backup of your phone, but with this new procedure, this is no longer needed.
When it is finished, click the PARTITION DL radio button, pick the H915 v10e KDZ that you downloaded above, and click start. Make sure all partitions are checked.
Once it is complete, your phone should reboot into a nice new (old) Freedom Mobile ROM (complete the setup), and you may not have signal.
- If you are on AT&T I understand that you will, but T-Mobile does not. Either way, this is normal.
Before continuing, make sure that you enable developer mode, and enable USB debugging. Also, make sure that your PC is authorized (plug the phone in and touch always allow, and then OK).
Also go ahead and download a terminal emulator -- NOT Termux. I recommend good old "Terminal Emulator for Andorid" -- the first thing that pops up if you search for "terminal"
Download this modified (by modified, I mean it contains all the extras needed to make this work) DirtySanta root package: link.
- Extract this somewhere that you can run adb and fastboot from.
- Check the SHA hash: 88a3a0f90c66a486807da3e69e9fb0a08c779efe
Download the v10r firmware + boot + system here: link (sorry - no time to dump and package 10v)
- Check the SHA hash: 5451146030393e490dcfba3558b620badefe75cd
- This includes v1.0 of the mk2000 kernel
Copy the zip, to your SD card, and insert it in the phone.
- Alternatively, you can use adb to push the zip to your phone while in TWRP. This is NOT supported.
- I switched to having people flash from SD card because too many people were having problems with adb.
- If you want, try it, if it doesn't work, don't ask for help -- use the SD card method!
Open two command windows. In each one change to the directory that you extracted the root package.
In the first one execute:
Code:
adb logcat -s dirtysanta
Then in the second one execute:
Code:
STEP1.BAT
Wait till you get a prompt back then type (or copy / paste):
Code:
run-as con
chmod 0777 /storage/emulated/0/*
Now open up your terminal emulator on your phone and type:
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
Watch the window that has logcat running. When it says to run step 2, execute:
Code:
STEP2.BAT
Once fastboot comes up -- it will be a really small red font that says, FASTBOOT MODE. Once that is up, execute:
Code:
STEP3.BAT
This is flashing TWRP and the WW 2.0 kernel onto your phone. The phone will reboot once they are flashed.
When it reboots, you will get a very nasty looking warning about the fact that your phone has been compromised and will not boot.
This is due to running the engineering aboot and is normal -- don't panic your phone will boot. You will see this every time the phone reboots.
At this point, you have H915v10e and TWRP. You can now boot into TWRP so that we can flash the H910 firmware back onto the phone:
If you have re-enabled developer mode, and enabled USB debugging, and have your phone connected, you can execute the following in a command window:
Code:
adb reboot recovery
Otherwise just pull the battery, put the battery back in, hold vol down + power till the LG logo appears. Release power, and then immediately press and hold it again until you get to a screen that asks if you want to factory reset your phone. Say yes twice and it will take you into TWRP. If the phone had the stock recovery, it would do a factory reset -- however, since you now have TWRP, that is what you are taken to instead. This is a key combination that is embedded into the bootloader that tells it to execute recovery - in this case TWRP. Hope that clears up some confusion as to why you get a screen asking you to factory reset your phone...
Now that you are in TWRP you need to do a couple of things:
Format data. Wipe -> Format data. It will ask you to type "yes". If you don't do this, you will be prompted to enter a passcode, and will have 30 tries. If that happens, just boot back to TWRP and do this step again.
Wipe cache / dalvik cache
Flash the zip. Choose "Install" and browse to your SD card, and select the h910-10r.zip file. When complete hit the home button.
Now, format data again for good measure....
Once the second format completes you can reboot your phone, and it will be just like you got it fresh off the factory floor, except it will have TWRP.
No part of the H915 firmware is left on the phone. The only things that are not 100% stock v10r firmware are ABOOT (it is the US996 engineering aboot that is unlocked. It also gives the nasty warning on boot), BOOT (it is the 10q kernel with a few patches added by @askermk2000 - KCAL, Adreno idler, etc), and of course RECOVERY (TWRP).
It takes a little while for the first boot -- be patient. It should NOT take longer than 10 minutes. If it does, something went wrong. Boot back to TWRP and try flashing the 10r zip again.
Now that you have a phone with TWRP, feel free to download whatever root method you would like (SuperSU or Magisk).
Old, unsupported ROMs will NOT work with the 10p, 10q or 10r firmware.
If you want to run NATF or WETA (or any old, unsupported ROM that you find floating around these forums) you will need to flash the older 10m firmware: here.
SHA: 1007dedb6e935b0bea1e25f28e39ccb8e69f9694
This is JUST the firmware! It has no kernel, or system. You MUST flash a 10m or earlier ROM or your phone will not boot. If you forget, you can always boot back to TWRP and try again.
The newer kernel should work, but I have not tested it with the older firmware. If it doesn't grab the WW2.0 kernel, it works fine with 10m.
For the latest kernel, please visit @askermk2000's thread: here
Do NOT flash firmware for the H918 -- it will brick your phone. Firmware for the other models won't work, but they won't brick your phone.
Feel free to ask away if any of this doesn't make sense. I really hope that isn't the case now
Most of all -- have fun. That is what this is supposed to be about!
Again, If you want to restore to stock v10q, you can use this: link.
Serious credits go out to:
@me2151 for DirtySanta. Please visit his original thread and hit the thanks button.
@smitel for Reversing LG UP and figuring out how unlock lab mode. No partition dl, no root on the new firmware. Again, hit the thanks button.
@Prowler_gr for patching LG UP for the V20 not to mention finding that thread. I never go into the G5 forums, so I would have never seen it. AGAIN -- hit that thanks button.
@USA-RedDragon for his Werewolf kernel. I know I sure like not having static on boot. Most people get the ability to hit thanks 6 or 7 times a day -- be sure to use up one more.
@askermk2000 For the new 10q kernel. Dude doesn't even have a V20 and jumped in to help out.
Seriously, these guys are the real devs, and the ones that have left the V20 scene are missed...
-- Brian
FAQ:
Q1: If I revert to stock will AT&T know that I rooted my phone?
A1: Nope. Unlike Samsung phones (at least older ones, I don't know about current ones), there is no KNOX style indicator that shows how many times a phone has been flashed.
Q2: Do we have to flash ALL of the H915 firmware, that seems like a waste?
A2: You would be correct -- it is a waste, but I am going to need more time to test and make sure that only the XBL and ABOOT need to be flashed AND that doesn't break trusted boot. As I have stated, the H910 and H915 have the same PBL. I ran my phone with the H915 XBL, with the rest of the firmware being H910 and I don't have a brick -- but I did it manually and not though LG UP. When I feel like wiping my phone again, I will test this.
Q3: Can any other variants be rooted with this method?
A3: Maybe. I was able to get the patched LG UP to recognize a KDZ that I modified, and it let me flash. My next step is to completely roll my own KDZ. If that works, then ANY LG phone will be rootable simply by flashing a KDZ.
A3: YES! It turns out that the LS997 is able to use the VS995 KDZ. I have written up a post on the procedure.
Q4: If that works, and you can roll your own KDZ, can you get around ARB?
A4: I believe so. Now that we have the ability to take a dump of an unmodified / stock / out of the box phone, we could dump the XBL (this is what updates ARB), and package that up with an older ABOOT. I am mainly talking about H918s here, since all other V20s work with the engineering ABOOT. But it will also apply if AT&T ever increments ARB on the H910.
Nope, there is no getting around ARB. Once a particular ARB version is blown into your QFPROM, you *MUST* use a boot stack that has that ARB version, and that is basically the entire firmware except for boot, recovery, laf and system.
Q5: Will the AM&FM Radio still work
A5: Yes.
Q6: Why are my boot times longer after rooting?
A6: In order to unlock the bootloader, an engineering aboot had to be used, and a lot of additional data is generated on boot.
Q7: Can I return my phone to stock?
A7: This was addressed in the post above, but I will address it again. Yes. For the link, see the post above.
I am Definitely missing something here, I cant for the life of me get the h915 firmware to flash using lgup
It just states kdz file is invalid.
H910 -> h915
Confirmed im attempting to use the patched lgup as well
It is definitely not reading the modified model file. You must have had another version installed. You need to uninstall / delete any other model dll files you have installed.
It would appear that i dont have lgup installed correctly (not at all in this case) to begin with
Let me do a little digging to figure out lgup.
Not entirely sure how i did a full dump with it not even installed but alright
---------- Post added at 09:10 PM ---------- Previous post was at 08:51 PM ----------
Just to confirm for 100% sure that we are supposed to be ticking the upgrade option and not the option for partition dl that is mentioned in the patched lgup thread correct?
I simply cannot get passed invalid kdz and have confirmed numerous times now that there is only one dll in the lgup folder
Path to the lgup exe that i have replaced with the above patched executable from the other thread
C:\Program Files (x86)\LG Electronics\LGUP\LGUP.exe
Path to the dll folder that i placed there as well along with a LOG folder directly above it
C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_common.dll
The log folder consists of a folder by this name here LG-H910 (my current device)
There is nothing else in the model folder at all except for the two mentions above
If lgup is somehow reading from another directory outside of where i launched the exe, I have zero clue as i have searched lgup to no availability.
And that is why I wanted to write this up as I did it
You are correct. Choose partition dl, and make sure all partitions are selected.
After that, the rest of the instructions should be correct.
runningnak3d said:
And that is why I wanted to write this up as I did it
You are correct. Choose partition dl, and make sure all partitions are selected.
After that, the rest of the instructions should be correct.
Click to expand...
Click to collapse
I have ran out of time tonight to muck around with it but have definitely rendered it bootlooping currently (stuck at second lg logo is more accurate)
Not entirely sure what i did wrong, was able to get into twrp a couple times as well trying to continue the steps
Since you have TWRP installed, you can fix whatever is wrong.
Unfortunately, whatever you did wrong was within the DirtySanta root procedure, and that would have gone wrong even with H910 firmware with the Dec. 2016 sec patch.
You are going to have to provide some more details.
It booted successfully after the h915 flash and I made it all the way up to step three before it was bricked under the dirty Santa method and have been attempting to recover it since.. I can't get lg up to recognize it any longer as of now
---------- Post added at 01:37 PM ---------- Previous post was at 01:27 PM ----------
Scratch that somehow i got it booted, I was stuffing around it twrp and flashed the natf with a factory reset and it is now static booting which I'll have to fix once I grab that kernel
runningnak3d said:
WARNING: This is ONLY for H910. If you flash H915 firmware on an H918 -- you WILL brick it. I am not sure about other variants, but cross flashing firmware is HIGHLY risky. I only found out this was safe because I got myself in a situation where I had nothing to lose, so I tried it.
Since I have had quite a few people ask me via PM for the procedure, I figured it was time to make a post. I really wanted to wait till I got my H910 back from LG so I could type this up as I do it again (yes this has been tested) to make sure that I don't miss a step. I am 99% sure that I didn't, but even if I did, the worst that is going to happen is that you get an error or have to start again.
Standard disclaimer -- there are no guarantees in life. No part of this should brick your phone, but if it does somehow, that is on you.
This should work on any version that is no longer rootable by DirtySanta (IE: dirtycow has been patched), but it has only been tested on v10m (Sec. patch April 2017).
The H910 and H915 have the same PBL (Primary Boot Loader), so it is safe to flash H915 firmware on H910 hardware.
Make sure you have a working adb environment. I use Linux so hopefully this is a good resource. If not, you will have to Google this yourself: link.
Download the H915 v10e KDZ: H91510e_00_VTR_CA_OP_1205.kdz. WARNING: Do not use any newer H915 firmware, as they all have dirtycow patched (v10p, v10q), and I do not know if they increment ARB. If they do increment ARB, then you will be stuck with a phone that can't be rooted, and you can't fix the modem! You have been warned.
Download the patched LG UP from this thread: link.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Put your phone into download mode (power off / hold vol. up / plug in USB cable)
Use LG UP to dump your phone. When you run it, there will be additional radio buttons. Pick the one that says DUMP and click Start.
When it is finished, click the PARTITION DL radio button, pick the H915 v10e KDZ that you downloaded above, and click start. Make sure all partitions are selected.
Once it is complete, your phone should reboot into a nice new (old) Freedom Mobile ROM, and you will have no signal. This is normal.
You are now safe to root your phone following the standard DirtySanta procedure: link. You can ignore the part where it says that you can't go back to stock. As soon as my phone comes back from LG, I will be posting a zip that you can flash that will completely return you to stock v10m.
OK, so now you are rooted, and have TWRP. Now I am guessing you would like to actually be able to use your phone to make calls / send texts / surf porn read XDA, so you need a working modem...
The following you will do from a command prompt:
adb reboot recovery
adb push X:\path\modem_COMYY /sdcard/
Where X:\path is the path that you saved the dump from your phone, and YY is the COM port number. For example, if Windows detected your phone as COM11, then the file will be named: modem_COM11
adb shell
cd /sdcard
dd if=modem_COMYY of=/dev/block/bootdevice/by-name/modem
exit
adb reboot
When your phone reboots you should have a rooted H910 with Freedom Mobile v10e ROM and phone / data functional.
At this point, you are free to flash any ROM that is for the H910. I use NATF, but some prefer WETA. I am not including links since you should really go find a ROM you like yourself.
As I stated at the beginning of this post, my phone is in the shop and I don't have a full dump of v10m. When it gets back, I will make a zip that will flash all the pertinent partitions with our v10m firmware so that we have nice, updated phones. I will also post a zip that will flash ALL the v10m partitions and take you back to exactly where you are now in case you want to return to stock for some reason.
Feel free to ask away if any of this doesn't make sense
-- Brian
Click to expand...
Click to collapse
GOD BLESS YOU! I needed this today! Will try later!
Passing along an update of progress, currently still having trouble with this.
Current status is it is static screen booting currently.
I also have no signal and your steps for flashing the modem work just fine to what it appears to from the commands lines (everything goes through correctly) but upon booting shortly after i am greeted with a blue screen saying subsystem crash : modem
Yes i did use the dumps from the very first step and they appeared to have flashed back correctly.
Lgup will not recognize the phone from everything i have tried to recover it at this time either
Edit: when it comes to the step where you have to type this here below
dd if=modem_COM5 of=/dev/block/bootdevice/by-name/modem
Is the portion from this line where it states "by-name" correct?
Com5 is correct as that is the name of my file when i pulled it from the device
Stuck on step 5 of Dirty Santa on an H910. Went back and redid steps 3-5 and it's still just sitting on LG logo. Any ideas???? I know I followed the instructions verbatim!!
jreed3786 said:
Stuck on step 5 of Dirty Santa on an H910. Went back and redid steps 3-5 and it's still just sitting on LG logo. Any ideas???? I know I followed the instructions verbatim!!
Click to expand...
Click to collapse
Have you tried this
me2151 said:
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot bootbackup.img
fastboot reboot
Click to expand...
Click to collapse
Sent from my LG-H910 using Tapatalk
Is there a method to getting back to full stock 10m on the h910 for now until i can get this sorted out.
Ive tried flashing the backed up modem i have multiple times at this point and cannot get signal back after following this method here to the letter.
I do have access to twrp but cannot get access to lgup at all no matter whether it is in fastboot mode/recovery/usb debugging/etc etc etc
daw41 said:
Have you tried this
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
SURE have. This is for the Verizon variant. I have AT&T. No such path found. I too, just need the modem to work. I tried a few workarounds...
SO, either a fix for the bootloop on the LG logo, or a flashable H910 modem so I can use my phone.
runningnak3d said:
Reserved for FAQ
Click to expand...
Click to collapse
Sir, i accdientally KDZ my H910 to F800K. I managed to make the call, mess function again by flashing US996 modem file but now my phone can't connect to any mobile network when data switch on. I mean i can call and receive call from other people, send and receive mess too. Could you kindly teach me how to fix this???? I can KDZ to US996 rom but it end up in bootloop (i can get into the rom, but after a few second it will reboot itself). In US996 rom, my phone functioning normal, no problem at all, but the bootloop happen so, sir. Help me, please
jreed3786 said:
SURE have. This is for the Verizon variant. I have AT&T. No such path found. I too, just need the modem to work. I tried a few workarounds...
SO, either a fix for the bootloop on the LG logo, or a flashable H910 modem so I can use my phone.
Click to expand...
Click to collapse
So if you're at step 5 you should have TWRP manually reboot into TWRP and Flash a ROM like natf or weta should fix your issue
Sent from my LG-H910 using Tapatalk
daw41 said:
So if you're at step 5 you should have TWRP manually reboot into TWRP and Flash a ROM like natf or weta should fix your issue
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
Yes sir...it should, but I still get error about modem, even when flashing WETA and rebooting. Any easier way to flash the H910 modem?
jreed3786 said:
Yes sir...it should, but I still get error about modem, even when flashing WETA and rebooting. Any easier way to flash the H910 modem?
Click to expand...
Click to collapse
Sir, i can make the phone call and mess work again but the mobile data i nowhere to be found. At least you can make phone call and send text. You can try by flashing US996 modem file, the signal will come back but without 4g,3g or whatsoever.
Jerry SQ said:
Sir, i can make the phone call and mess work again but the mobile data i nowhere to be found. At least you can make phone call and send text. You can try by flashing US996 modem file, the signal will come back but without 4g,3g or whatsoever.
Click to expand...
Click to collapse
There's no way to flash or find an H910 modem file? Why is this? Just wondering.
Due to the disrespect of certain members I will no longer share the tutorials.
Wait does this mean you finally got my script to work?
lebigmac said:
Wait does this mean you finally got my script to work?
How about a little feedback in my project thread? Is that too much to ask for?
Did the latest fix work for you or not? Hello?
Click to expand...
Click to collapse
I said you were working on it. LOL. If it worked I'd be writing a Guide for that!
Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root
mingkee said:
Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root
Click to expand...
Click to collapse
Exactly. Definitely made a note of that in the guide since that is why the frozen touchscreen issue happens.
Articul8Madness said:
.This tutorial is for people like me than ran into problems rooting the Moto One 5G Ace XT2113 (MetroPCS Qualcomm Variant) running on stock Android 10. I got this phone literally last week brand new in the box. This is a hand holding guide for the Noobs that really are intimidated by rooting their device.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
I want to thank @mingkee and @sd_shadow for pointing me in the right direction. And for the rest of the contributors that I took bits and pieces from that helped me figure out rooting this; I did achieve root out the starting gate but initially lost touchscreen functionality. The issue was that you have to use the boot.img of your firmware to patch into Magisk; if you do this with your phone out the box you really don't know which firmware was used and that is where the bungle happens. This will clear up all those potential freakout moments.
Thanks to Android 10 being System As Root with all these new super partitions running amuck, you cannot get Write access in the actual system files. So even when you achieve root, you can't do much. @lebigmac is working on that as we speak. Drop by his thread on R/W access and beta test his script so he can get more knowledge about how our phone works.
Introduction/Preparation
First, go and prepare by READING EVERYTHING. Very important. This is the Qualcomm variant and NOT the Mediatek variant. Flashing does make a difference between the two. Last thing you want to do is brick the device because you flashed the wrong firmware to the wrong processor, or you flashed other software for the other similiar Moto One 5G and it bricked.
Second, unlock the bootloader. All T-Mobile and their subsidiary variants can be unlocked by Motorola as well as International and Motorola factory variants; go to their bootloader official unlock site and follow their instructions, it's easy peasy. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). It is HIGHLY ADVISABLE to do this in Waterfox or Chrome (I used Waterfox). And yes, you may have to request the code 3x to get it to send to your email depending on their server traffic. When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
Verizon and ATT Variants CANNOT BE BOOTLOADER UNLOADER UNLOCKED.
***NOTES SO YOU DON'T FREAK OUT***
1. I did NOT see the motorola post screen telling me it was unlocked. I had to find this in fastboot's menu.
2. The only way to restore the phone if something goes wrong is by flashing it via fastboot. The way to get to fastboot is turn the phone off and press Volume Down and Power. The Motorola tool will NOT work. That's normal.
3. You will see a cute message that you've unlocked the bootloader and that the phone software integrity is compromised when you boot the phone up every single time after the bootloader unlock. It will also say press the power button to pause. This is normal. Give it a minute, you havent broke it.
4. OEM Unlocking should already be activated and greyed out in the Developer Options once the bootloader is unlocked; you can't access it anymore.
Files
You will need an SD card for root. You will also need other apks to successfully help you pull off root ready to install. Pull ALL the necessary files you will need.
1. Get Minimal ADB and Fastboot (it's easier).
2. Download the Motorola Drivers from their site if yo don't already have them (if you run into problems you will have to uninstall and reinstall them through their utility which is found on PC here: C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
3. Cpu-Z.apk (Very important, its hard to know your hardware without this).
4. Magisk v22.0.apk (They no longer have a separate Magisk Manager)
5. Root Explorer.apk (This software helps navigation better but you can use any Explorer of your choice).
6. Root Checker.apk
7. Stock Firmware XT2113-3_KIEV_RETEU_10_QZK30.Q4-40-62_subsidy-DEFAULT_regulatory-XT2113-3-EU-SAR_CFC.xml (This is important if you mess up the boot image trying to root). You can get the firmware of your choice at Motorola Official Firmware For Kiev.
8. Patience (and a good movie keeping you going).
As of now this device as no TWRP, so you have to do this the old fashioned way to root. And just so you know, I used Windows 7 for all of this.
Pre-Rooting
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. Everytime you wipe the phone or do anything messing with the boot image the phone resets itself to factory settings, and tries to push an update. Just take the silver key thing and pop it out. You will have to push it back in and out in a second, but start with it out.
3. Make sure your wifi is OFF.
4. Make sure your SD is in and mountable and all files you need are on the card.
5. Make sure you Save boot.img to your SD Card from your firmware files. This is very important for root.
6. Make sure your developer options are activated.
7. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below).
8. Make sure to check CPU-Z for your hardware specs so you download the right files for the phone and avoid potential problems.
9. Make sure you manually set USB to Transfer files (no other option will work and by default its set to Charge this Device).
10. Make sure you have the STOCK CABLE that comes with the phone. Like most Motorolas this model is funky about using other cables.
11. Make sure you back up all your calls, texts, pics, etc. Flashing the firmware is the ultimate factory reset and you will lose all your files on the phone. SMS Restore is a good software to backup Calls and Text logs and it supports keeping MMS.
12. Make sure you have the internet. It is necessary for some steps.
Rooting
1. Make sure all the firmware files are extracted into your Minimal ADB and Fastboot folder (or whatever ADB folder you're using for this).
2. Open FlashFile.xml in Notepad. This is located among the firmware files you put in the Minimal ADB and Fastboot folder.
3. Cut, copy, and paste everything from the FlashFile that is shown and then paste it in an online Flash file Converter. I used Online Flash File Converter here.
4. Convert the text by pressing the bar below where you pasted the text. It may be in Spanish or Portuguese but is should say something like Cerar Commandos.
5. Copy the text by hitting the two pieces of paper icon in the corner after it's converted. Or just cut copy and paste manually.
6. Turn the phone completely OFF.
7. Plug your phone via USB cable into the computer.
8. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY).
9. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your firmware files are in the Minimal ADB directory or it won't work.
10. Paste the contents of the flashfile converter into Minimal ADB and Fastboot. This should start the process of the flashing.
11. When the entire flash is complete, boot the phone and disconnect phone from the computer. Ignore the bootloader unlock error.
12. Wait. Sometimes this takes up to 3-5 minutes on a new flash. You should see the boot animation of Motorola.
13. Push your Sim Card back into the phone.
14. Start setting up your device on the screen. Sim Card must be in or it will give you a message your phone is Network Locked.
15. Once you make it to the Wifi Setup screen take the Sim back OUT the phone. Do not connect to Wifi.
16. Once you are done with setup, go to Settings>About phone.
17. Go all the way down to Build Number and press it until you unlock Developer Options.
18. Go to Settings>System>Advanced>Developer Options. Advanced is a pull down tab that will reveal Developer Options.
19. Disable Automatic System Updates. I know this is hard for some people, but a forced OTA update may cause problems and prohibit root.
20. Enable USB Debugging. Disable Verify bytecode of debuggable apps. Disable Verify apps over USB if it is highlighted. Exit.
21. Put your SD/Sim card back into the phone.
22. Go to the Files folder and install Magisk first, then Root Explorer and Root Checker.
23. Open Magisk. You will see Magisk and App. Hit Install by Magisk (a fingerprint looking icon is to its left).
24. Allow Magisk to access photos, media, and files if it asks.
25. Select option "Select and Patch A File."
26. It will take you to a screen where you can select your explorer to navigate to your SD card where you saved the boot.img. Go there and select it.
27. Magisk will save it as magisk_patched.img. Once you get it patched, find where it saved, make sure it's on your SD card and then turn off the phone.
28. Plug your phone via USB cable into the computer.
29. Press Volume Down and Power to boot into fastboot mode.
30. Open up a fresh Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure you transfer the magisk_patched.img that Magisk patched off your SD card into this folder.
31. Rename your original boot.img to "boot.img original" or whatever distinct name you want to give it in your Minimal ADB and Fastboot folder.
32. Rename your magisk_patched.img to boot.img.
33. In Minimal ADB and Fastboot type "fastboot flash boot boot.img" and hit enter.
34. If all goes well it should flash to the partition before it says done and in how many seconds.
35. When it is done, reboot phone by selecting START (keep pressing volume rockers until you see it, then press the power button).
36. Wait for the bootloader cannot be trusted screen to pass (may take a minute) and wait for the Hello Moto opening.
37. Open Root Checker and confirm root. You can uninstall it after confirmation if you like.
38. Open Root Explorer. A prompt asking you to grant permission should pop up.
Congrats. You should be rooted now.
***NOTES SO YOU DON'T FREAK OUT***
1. Do NOT flash someone else's patched boot image. It WILL NOT WORK. Do the work, find your firmware, and patch the boot image yourself. You're asking for bootloop hell if you do as your boot.img that Magisk patches needs to match that particular firmware you used.
2. While it hasn't happened to me, You may have followed everything perfect and it still bootlooped. Save yourself the frustration and just flash it over. See the next section on the proper way to flash so you don't lose your baseband, IMEI, or any other important stuff.
3. While you won't lose anything just flashing boot.img, you will lose everything having to flash ALL the firmware over. Keep backups of all your important stuff.
****Notes on Flashing The Stock Firmware if you have to****
In the event you bootloop and have to start from scratch, follow my guide on restoring the firmware on the phone. And don't worry - it won't relock the bootloader. You can find my guide here: The Complete Noob Guide to Flashing via Fastboot MetroPCS Moto One 5G Ace XT2113 [Qualcomm Version]
Hope this helps my fellow TMobile and subdiary acolytes and othoers. I have flashed and reflashed my phone with different variant roms trying to force Write status and beta testing scripts for @lebigmac on our device so it's pretty straightforward now.
I will try and answer questions if I can or point you in the right direction.
Click to expand...
Click to collapse
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset
bobbyp1086 said:
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset
Click to expand...
Click to collapse
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.
Articul8Madness said:
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.
Click to expand...
Click to collapse
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.
bobbyp1086 said:
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.
Click to expand...
Click to collapse
If your bootloader is unlocked the only way you should have gotten the corruption is if you flashed an incompatible firmware. Mine came with MetroPCS but I've flashed RETUS and RETEU well. I'd stray from any VZW or ATT software just because you can't trust their firmware won't lock down the bootloader.
Or maybe the software just didn't download well. Try re-downloading it . I've had a bad download mess up a flash before.
I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch
bobbyp1086 said:
I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch
Click to expand...
Click to collapse
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.
Articul8Madness said:
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.
Click to expand...
Click to collapse
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /
{
"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"
}
and fix file permissions, it's in settings
bobbyp1086 said:
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /View attachment 5279427View attachment 5279429View attachment 5279431View attachment 5279433 and fix file permissions, it's in settings
Click to expand...
Click to collapse
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.
I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?
I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked
bobbyp1086 said:
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.
Click to expand...
Click to collapse
Android 10 is very challenging. It is easy to root but it is a trickable root with a false sense of root since Google locked all Android 10 and newer as Read Only on the System with this super partition crap trying to be Apple.
Skel40 said:
I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?
Click to expand...
Click to collapse
Check my guide. I posted link to where the repository is.
Skel40 said:
I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked
Click to expand...
Click to collapse
You will not pass safety net because you've rooted it and Android 10 will block it. It isn't necessary, especially if you delete all Google stuff and their tracking Covid crap.
Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
Hi @Articul8Madness. Thanks for mentioning me
There's a Motorola user who recently got my script to work using the troubleshooting repair script that I posted here
It turns out the lpmake arguments that are auto-generated by the original script were flawless and were not the root cause of the unidentified lpmake error that some Motorola users were experiencing at the end of the original script. According to @Xiaoleng the error was most likely caused by some kind of new Motorola security feature that prevents the terminal command from executing if the arguments are too long. Go figure.
And he was even able to fastboot flash the super_fixed.bin in one piece without having to first split it up into chunks. That's a huge surprise to me. I always thought Motorola users can only fastboot flash super sparsechunks?!
Please feel free to give it a try and report back your results. Thanks. Good luck!