* I'm 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 the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Click to expand...
Click to collapse
This is my first time posting here on xda if i miss some rules please let me know
Installing drivers & Preparing PC (Thanks to balazs312)
- Download this file and extract it
- Open and install "adb-setup-1.4.3.exe"
- When it is done, go to "Drivers" folder and start "miflash_unlock.exe"
- Click on the gear icon top right corner and click on "Check" next to "Click the button to install the drive"
- Do as the installer says
- Hopefully the drivers has been installed so we're done with it
NOW Unlock Bootloader (It will wipe ur data! so backup before doing it)
-Open the Settings app on ur phone
-Go to System.
-Tap on About phone.
-Scroll down and tap on Build number 7 times until it says you’re now a developer.
-Go back one page you should see “Developer options.” click it
-then you should see an “OEM unlocking” option. Enable it.
-Scroll down a bit until you see “USB debugging.” Enable it.
-Disable automatic updates
-now turn off your phone
-now turn on ur phone in fastboot mode by pressing volume down + power key in will boot in fastboot mode
- Download zip and extract it on your PC
- Open it and type "cmd" (without the quotations) in the file manager header where you see (This computer>somethingsomething>Mi A2 fastboot), don't be afraid just type it in, and hit enter and you'll enter into command prompt
- Now we are ready for action
- Type these commands one by one:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
done now pop up will show on your phone select unlock bootloader with volume key n power
it will reboot set up ur phone again
2. Installing Magisk
To Install Magisk you need patched boot image you can have one from here
{always use img that matches exactly to ur build no}
OR
{OPTIONAL}
you can make own boot img
download fastboot rom and get boot.img from there
or download untouched img from here
so now ur phone is unlocked download magisk manager and install it from HERE
copy that untouched boot image from ur pc to phone
open magisk manager >install >patch boot image select ur boot img u just transferred
magisk manager will create a patch image in same directory or download folder
Fastboot patch img
Now if u have created ur own patch img transfer it to pc from ur phone n put it in adb folder
or if u have simply downloaded the patch image copy it to adb folder
Open a fastboot command prompt on your pc.
Type "fastboot boot {patched boot image name}.img"
Your phone will reboot
Install the magisk apk.
Now open Magisk Manager app
Click Install, direct install. Wait for the process
And click reboot.
HOW TO APPLY OTA UPDATES
IMPORTANT: it will only work if you do not alter system yourself like build.prop (try altering system just using magisk modules)
{if u created ur own patch img}
When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images"
{if u have not created ur own img put untouched downloaded build.img in magisk folder then}
When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images"
Close Magisk Manager and go to "Settings" > "About Phone" > "System update" and install the OTA update. Dont Reboot
Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot" and after that you can tap on "Reboot".
alternatively
Magisk could alert you that it cannot restore the original boot.img when you trying to uninstall
To fix this, you can flash directly the untouched boot.img through fastboot
Code:
fastboot getvar current-slot
then you will get ur active slot it might be a or b
if its a then use
Code:
fastboot flash boot_a boot.img
If its b then use
Code:
fastboot flash boot_b boot.img
Now We Have Mi A2 Telegram Group get in if u want to help or need some help
OffTopic Group HERE
Development Group HERE
-reserved-
i have just created this account to reply here it
i used to read here alot but i dont reply here
as i found this thread has no reply but the best method i was searching for on internet for my mi a2
i just got my mi a2 was highly confused how to root because of a/b partition and no official twrp
i found this method among the best no confusion straight on point
and seriously a noob guide
thank you for the this !
geekh said:
i have just created this account to reply here it
i used to read here alot but i dont reply here
as i found this thread has no reply but the best method i was searching for on internet for my mi a2
i just got my mi a2 was highly confused how to root because of a/b partition and no official twrp
i found this method among the best no confusion straight on point
and seriously a noob guide
thank you for the this !
Click to expand...
Click to collapse
I personally think that there are at times some confusion. but it remains a more reliable method. (in terms of ease this method (https://forum.xda-developers.com/mi-a2/how-to/guide-2-minutes-magisk-installation-t3856980/amp/) is by far the fatest, try it after your next ota)
Atlas/ML said:
I personally think that there are at times some confusion. but it remains a reliable method. in terms of ease this method (https://forum.xda-developers.com/mi-a2/how-to/guide-2-minutes-magisk-installation-t3856980/amp/) is by far the easiest, try it after your next ota
Click to expand...
Click to collapse
I have just checked your linked thread first of all its wrong to promote your own thread like this
u are fishing people to come to your thread thats completely wrong and unprofessional you are on xda maintain some professionalism !
if someone wants to use your thread he/she will use it by themselves ,its visible to all !
and about your method i didnt wanted to use ur method i have looked into it you are using temp twrp method using unoffical twrp which i dont want to use thats personal preference i will wait for official twrp before flashing !
this method is best for me(noob here might be not as good as you but i know basic stuff) i can easily flash twrp permanenlty as soon as it is released without any further steps
Not everyone wants to use that temp twrp method
It is not fair to @Adinid who has taken so much time writing this great noob friendly thread
coming to his thread and telling people that ur thread is best or easiest is isnt good my friend !
in OTA part，"put untouched downloaded build.img in magisk folder"，This is invalid，I test it on V9.6.13，It always prompts that the backup image was not found.
geekh said:
I have just checked your linked thread first of all its wrong to promote your own thread like this
u are fishing people to come to your thread thats completely wrong and unprofessional you are on xda maintain some professionalism !
if someone wants to use your thread he/she will use it by themselves ,its visible to all !
and about your method i didnt wanted to use ur method i have looked into it you are using temp twrp method using unoffical twrp which i dont want to use thats personal preference i will wait for official twrp before flashing !
this method is best for me(noob here might be not as good as you but i know basic stuff) i can easily flash twrp permanenlty as soon as it is released without any further steps
Not everyone wants to use that temp twrp method
It is not fair to @Adinid who has taken so much time writing this great noob friendly thread
coming to his thread and telling people that ur thread is best or easiest is isnt good my friend !
Click to expand...
Click to collapse
I personally think that official twrp will never support boot, because At first glance the beta does'nt support it. So my method will be the simplest for a while.
As for the sharing of MY guide, it is a simpler and faster method. And it will allow more people to root their phone without following 50,000 steps and without fear of brick their phone ...
If @@Adinidhas a problem with sharing my guide, he can tell me privately on Telgram, and I'll delete it.
Have nice day,
Matteo
I don't really care which method people use to do one thing or another. It's up to them, whatever they feel most comfortable doing.
But, I do care when someone misuses the 'code' functionality box. It's not used for 'further description'... it's used for CODE... ie, actual code:
like: fastboot boot bootloader
like: adb shell setprop persist (etc)
It's meant to be something someone can copy and paste it to the command line, to avoid typing errors, not for 'further descriptions...'
Atlas/ML said:
I personally think that official twrp will never support boot, because At first glance the beta does'nt support it. So my method will be the simplest for a while.
As for the sharing of MY guide, it is a simpler and faster method. And it will allow more people to root their phone without following 50,000 steps and without fear of brick their phone ...
If @@Adinidhas a problem with sharing my guide, he can tell me privately on Telgram, and I'll delete it.
Have nice day,
Matteo
Click to expand...
Click to collapse
Your Reply shows your arrogance and unprofessionalism nothing else
you think the method you have is best u dont want to even think that someone can have other method n others might prefer it
you are just boasting about your method as best n what not lol !
instead of accepting that you did wrong by sharing your thread here , you are trying pull down op thread by shamelessly telling people that op method might brick phone n needs 50k steps(that is completely NOT true ) when ur method CAN also brick it !
you both have given options to users its their pick which one they want to use !
I dont want to waste my time here to educate you about how to behave in public forum !
Just want to say calm down put ur arrogance on side,show some maturity and even please try to change ur attitude
you might be good but try to learn as it doesnt matter how good you are there is always someone who is better than you n others might prefer it more !
different people have diff use cases preferences always remember that
peace !
AsItLies said:
I don't really care which method people use to do one thing or another. It's up to them, whatever they feel most comfortable doing.
But, I do care when someone misuses the 'code' functionality box. It's not used for 'further description'... it's used for CODE... ie, actual code:
like: fastboot boot bootloader
like: adb shell setprop persist (etc)
It's meant to be something someone can copy and paste it to the command line, to avoid typing errors, not for 'further descriptions...'
Click to expand...
Click to collapse
Thank you for your feedback sir, i have just started posting here as i wrote it in my initial post
my apologies will try to format it properly
tianma163 said:
in OTA part，"put untouched downloaded build.img in magisk folder"，This is invalid，I test it on V9.6.13，It always prompts that the backup image was not found.
Click to expand...
Click to collapse
looking into it
till then i just added alternate method use that !
geekh said:
Your Reply shows your arrogance and unprofessionalism nothing else
you think the method you have is best u dont want to even think that someone can have other method n others might prefer it
you are just boasting about your method as best n what not lol !
instead of accepting that you did wrong by sharing your thread here , you are trying pull down op thread by shamelessly telling people that op method might brick phone n needs 50k steps(that is completely NOT true ) when ur method CAN also brick it !
you both have given options to users its their pick which one they want to use !
I dont want to waste my time here to educate you about how to behave in public forum !
Just want to say calm down put ur arrogance on side,show some maturity and even please try to change ur attitude
you might be good but try to learn as it doesnt matter how good you are there is always someone who is better than you n others might prefer it more !
different people have diff use cases preferences always remember that
peace !
Click to expand...
Click to collapse
That's why i add a warranty part lmao, and for brick not possible, because magisk support A/B, and Twrp is BOOT only. So after reboot it's gone.
I just say that my method is the simplest, not the better. As for the arrogance I only share my link for you to win time if needs after any ota, if you do not want to use it. You say that I lower his method, etc. I have already done one with these same methods, and I will soon hold a repo. You're totally wrong. No luck You judge me without knowing me and give me orders and I'm arrogant. OwO
As for the answers, personally I do not have anything to do with it, it makes go up this thread in the list, hoping that it has more visibility.
Matteo
If i enable camera2api does it count as altering system for ota?
Ajakazema said:
If i enable camera2api does it count as altering system for ota?
Click to expand...
Click to collapse
it depends on how you activated it. if you activate it using a magisk module it will be fine, if you activate it using an adb command it's a system modification. so it should alter the ota.
Ajakazema said:
If i enable camera2api does it count as altering system for ota?
Click to expand...
Click to collapse
if u do that by build.prop edit it will count for altering system
but if u use magisk module to do that it will not
let me know if u have any more confusion
happy to help !
I'm currently in august security patch, with an unlocked device + root (magisk) and i've altered the build.prop to enable cameraapi2. How can I update safely to the new october patch?
Thanks in advance
hugopg said:
I'm currently in august security patch, with an unlocked device + root (magisk) and i've altered the build.prop to enable cameraapi2. How can I update safely to the new october patch?
Thanks in advance
Click to expand...
Click to collapse
if u want everything clean u can flash fastboot rom
after uninstalling magisk through magisk manager
or just uninstall magisk then fastboot flash boot img
u can check it in my how to get ota part in my initial post (alternative method)
then apply ota
root again if u want
adinid
Adinid said:
if u want everything clean u can flash fastboot rom
after uninstalling magisk through magisk manager
or just uninstall magisk then fastboot flash boot img
u can check it in my how to get ota part in my initial post (alternative method)
then apply ota
root again if u want
adinid
Click to expand...
Click to collapse
Hey, thanks for your fast reply!
In your post you said that the OTA can be done if I didn't altered the system.prop, but I did! So I would need to restore boot.img (through magisk, to remove root) and also flash system.img (to restore the prop)? Is that it?
Thanks
Atlas/ML said:
it depends on how you activated it. if you activate it using a magisk module it will be fine, if you activate it using an adb command it's a system modification. so it should alter the ota.
Click to expand...
Click to collapse
This is COMPLETELY inaccurate information! YOU are setting a very bad precedent.
Magisk is a SYSTEMLESS root, which means what it does with system is HIDDEN (very hard to detect), but that does NOT mean it doesn't modify system!!
The ADB command to set the cam2api is a setprop persist command WHICH DOES NOT MODIFY SYSTEM! EVER!
PLEASE DO NOT SPREAD COMPLETELY INACCURATE INFORMATION!! YOU WILL BE MISLEADING POTENTIAL FUTURE OWNERS OF THIS DEVICE!!
AsItLies said:
This is COMPLETELY inaccurate information! YOU are setting a very bad precedent.
Magisk is a SYSTEMLESS root, which means what it does with system is HIDDEN (very hard to detect), but that does NOT mean it doesn't modify system!!
The ADB command to set the cam2api is a setprop persist command WHICH DOES NOT MODIFY SYSTEM! EVER!
PLEASE DO NOT SPREAD COMPLETELY INACCURATE INFORMATION!! YOU WILL BE MISLEADING POTENTIAL FUTURE OWNERS OF THIS DEVICE!!
Click to expand...
Click to collapse
So, first shut a up.
Next i never say that magisk doesn't modify system, i just say that if use magisk for enable it it's fine.
For the second information, my bad , i try but with the adb command ota failed so i'm not totally false.
Have a bad day,
Matteo
Related
i have read LOTS of forums on this, but have found no diffinative, working methods. has anyone actually ever done this, and if so what method did you use? links/guides would be much appreciated! thanks
I also have searched everywhere and apart from "get a pc" or "get parallels and windows 7 for your mac" I've heard nothing concrete.
Any advice on this would be hugely appreciated!
ishamm said:
i have read LOTS of forums on this, but have found no diffinative, working methods. has anyone actually ever done this, and if so what method did you use? links/guides would be much appreciated! thanks
Click to expand...
Click to collapse
No guys, all the methods posted are just theoretical blabber posted for the LULZ!...
.... NOT!!!
... all the methods mentioned on this forum work, unless stated otherwise...
only a handful require a Windows PC
yes, preinstall method works, CWM root package works, gingerbreak works,
1-click easy root also works
follow the link, go to post 3... and you have directions for Mac OS
sorry, i didnt mention, im not on gingerbread (thanks to tmobiles slow updating), and most of these rooting methods seem to require it. would going straight to unlocking the bootloader be easier on mac? (i realise the methods arent written for fun, but many require a lot of presumed knowledge of terminal commands, which unfortunately i lack XD )
thanks
Bootcamp or parallels with windows 7. That's how I did it.
xploited said:
No guys, all the methods posted are just theoretical blabber posted for the LULZ!...
.... NOT!!!
... all the methods mentioned on this forum work, unless stated otherwise...
only a handful require a Windows PC
yes, preinstall method works, CWM root package works, gingerbreak works,
1-click easy root also works
follow the link, go to post 3... and you have directions for Mac OS
Click to expand...
Click to collapse
Many thanks, I'll try one of the ones you mentioned.
I'd love to try the one click method for mac but I clocked on the link, went to third post and it's not as you suggested it might be.
If there is a simple oneclick method for mac dullards like me it would be great to tell me where to go for it. Thanks again!
i have tried using dorootv3.sh and doroot2, on terminal, but both always fail, is there any other .sh that has been shown to work?
---------- Post added at 06:19 PM ---------- Previous post was at 05:32 PM ----------
basically, after a load of different attempts, my main problem seems to be this: to root on mac, i need 2.3.4 (i have 2.2.2); to get 2.3.4 i need to unlock the bootloader; and to unlock the bootloader it must be rooted.
it seems im stuck in this cycle, and dont really know what i should do. any help would be great.
can i flash with the at&t 2.3.4 from this thread http://forum.xda-developers.com/showthread.php?t=1125944 ?
you dont need root to unlock bootloader....you unlock bootloader through an sbf flash
we seriously need a popup box on every freaking forum that will explain what ROOT actually is.
root is SYSTEM access within the OS. outside of the OS, root doesnt mean squat
you will wipe all your system when you unlock your bootloader which means:
contacts stored on phone (unless you export them to vcf on sdcard)
settings
text messages
user installed apps
it does NOT wipe internal or external sdcard (i always keep a backup of this stuff on my computer anyway when i start messing with my phone)
oh sorry, in that case i totally got the wrong end of the stick reading the noob intro howtos so to unlock the bootloader what sbf do i need to flash? that i can do now through terminal, which is very handy, but i havnt come across any howto on bootloader unlocking that just says flash an sbf
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
i typed in google.com
'unlock motorola atrix bootloader'
a link lead me directly to that.....its the exact same tut listed here on xda....
sorry, im having a serious slow day, just gone on holiday so brain is totally out of gear XD thanks so much for clearing up the root/bootloader confusion, i have now unlocked successfuly, and will be installing my first rom!
ishamm said:
sorry, im having a serious slow day, just gone on holiday so brain is totally out of gear XD thanks so much for clearing up the root/bootloader confusion, i have now unlocked successfuly, and will be installing my first rom!
Click to expand...
Click to collapse
its not just you confused with root. its xda-wide.
for some reason sooooo many people have this notion that root=unlocking bl/s-off/rom-flashing
its frustrating to see people suggesting to others on some forums around here that they need to 're-root' their device when they are already on a rooted rom....its baffling that so much misinformation can be spread like wildfire.
my last confusion, for now XD, is this: the alien rom contains an image, which i can flash ok, but also a Meta Inf folder and System folder. if i follow this method
"
1. Extract all the files to the same directory and CD there in the terminal.
2. Put your phone in fastboot mode (turn it on holding volume down button then press volume up)
3. Type these commands in the terminal:
chmod +x moto-fastboot-osx64
./moto-fastboot-osx64 flash boot XXXXXX.boot.img (work out what Tegra part you need to flash and change the XXXXXX to that!)
./moto-fastboot-osx64 flash system ORFR234-system.img
./moto-fastboot-osx64 flash webtop webtop.img
./moto-fastboot-osx64 reboot
"
what should i do with the 2 folders, since as far as i know, i cant just flash folders right?
thanks
ishamm said:
my last confusion, for now XD, is this: the alien rom contains an image, which i can flash ok, but also a Meta Inf folder and System folder. if i follow this method
"
1. Extract all the files to the same directory and CD there in the terminal.
2. Put your phone in fastboot mode (turn it on holding volume down button then press volume up)
3. Type these commands in the terminal:
chmod +x moto-fastboot-osx64
./moto-fastboot-osx64 flash boot XXXXXX.boot.img (work out what Tegra part you need to flash and change the XXXXXX to that!)
./moto-fastboot-osx64 flash system ORFR234-system.img
./moto-fastboot-osx64 flash webtop webtop.img
./moto-fastboot-osx64 reboot
"
what should i do with the 2 folders, since as far as i know, i cant just flash folders right?
thanks
Click to expand...
Click to collapse
alien rom, as with any other custom rom, comes packaged for CLOCKWORK MOD RECOVERY
you dont extract rom zips
you need CWM installed on your unlocked atrix, then you boot to recovery, and flash the rom zip
oh man, just when i thought i'd started to understand everything! XD
if its not too much trouble, can you explain the method to go about installing alien on a mac, or if it exists, link a relevent thread? i can only find ones which confuse me even more
many thanks
ishamm said:
oh man, just when i thought i'd started to understand everything! XD
if its not too much trouble, can you explain the method to go about installing alien on a mac, or if it exists, link a relevent thread? i can only find ones which confuse me even more
many thanks
Click to expand...
Click to collapse
you dont install roms from your computer
you need to make sure you have CWM installed. you can do this with fastboot
fastboot this recovery on
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.img
instructions can be found
http://forum.xda-developers.com/showthread.php?t=1204500
you download a rom to your phone and flash it through recovery. no computer needed at all after you have unlocked and flashed recovery on.
and is this do-able without an SD card installed? before i get halfway down the road and find im screwed XD also it seems i need to be rooted for CWM, though i still cant find a way to do it...
ishamm said:
and is this do-able without an SD card installed? before i get halfway down the road and find im screwed XD also it seems i need to be rooted for CWM, though i still cant find a way to do it...
Click to expand...
Click to collapse
did you actually read the post above????
you can fastboot the recovery image.
you DO NOT need root in order to do so.....
yes i did read it... while it might be obvious to you, some of us have no idea what were doing. loads of howtos include having to install the rom from a SD card. also CWM says "The SD Card needs to be mounted to use ROM Manager" so i dont think its too much of a stretch to think i need one
ishamm said:
yes i did read it... while it might be obvious to you, some of us have no idea what were doing. loads of howtos include having to install the rom from a SD card. also CWM says "The SD Card needs to be mounted to use ROM Manager" so i dont think its too much of a stretch to think i need one
Click to expand...
Click to collapse
you dont need rom manager....
you boot into recovery and install from there.......
A. download rom
B. transfer to phone's storage (if you download directly from phone, obviously skip this step)
C. boot into recovery
D. wipe data/factory reset (option in CWM recovery)
E. select option: install from sdcard
F. confirm
G. after flash is complete reboot your phone, you are now on a new rom.
Hello All! As you know rooting is an important and first step for a person to step into developer world. Our Android devices have many methods to root them, so as our Xperia SP too.Today I am gonna tell you step by step how to root your Xperia SP in the easiest way possible.!
This is for JB 4.3 firmware 12.1.A.205. Root your phone in one click!
Steps for rooting
Pre Rooting Instructions
Backup each and everything on your Android phone as follows :
Backup all your important contacts
Backup all your important sms messages.
Backup all your important call logs,
Backup all your important media content manually. (Copy to your PC.)
Make sure that you read the instructions carefully and applied all precautionary measures. Let’s go ahead.
***WARNING***
I WILL NOT BE RESPONSIBLE FOR ANY DEAD OR BRICKED DEVICES, ROOTING IS FOR YOUR OWN NEED DO IT AT YOUR OWN RISK, IF YOU BLAME ME I'LL LAUGH AT YOU! ALSO YOU WILL VOID YOUR WARRANTY
Click to expand...
Click to collapse
1) Download DoomLord Advance stock kernel file (.elf file) (thanks to him) ----> http://doomlord.xperia-files.com/download.php?dlid=U1BfRG9vTUxvUkRfQWR2U3RrS2VybmVsX0ZXLTIwMV92MDM= (links are in blue mostly)
2) Download Stock kernel for your device C5302 : - [SIZE="5"https://docs.google.com/file/d/0B6OcGH8yjAPOaFRJRFBHUVk4QXM/edit][/SIZE][/COLOR][/U][/B][/U][/B][/COLOR][/SIZE][/B]
[B][U]C5303 : - [B][U][COLOR="Blue"]https://docs.google.com/file/d/0B6OcGH8yjAPONzdxR0k0T0k5MGs/edit
4) Download latest version of root exploiter from here (click on the lambda icon to start download) ----> www.towelroot.com
Install the apk to your phone. Make sure your unknown sources option and the development options is enabled and you have ticked usb debugging option. If not then go to settings then about phone , scroll down and click 5-6 times on the build version of the device and you will have development option available.
Make sure you are connected to internet, open the root exploiter you downloaded and click on the tab which says
make it ra1n
Click to expand...
Click to collapse
and that's it you're done rooting
Now time to install SuperSU on your phone
Go to play store and search for SuperSU and download it. Open it. After opening it will ask to update binary script Select continue and now it will ask for installation of the file. One you will have as normal mode other one would be TWRP/CWM. We don't have CMW/TWRP installed for now so select Normal mode and application will update itself!
In case if you have rooted and installed any recovery manually install the updater script from recovery. Place it in SD card reboot into recovery and install it. Download here
Installing the Recovery (CWM for those who haven't installed recovery) (With Unlocked Bootloaders)
1) Download Flashtool to your PC -- http://www.flashtool.net/download.php
2) Install it and open it.
3) Go to where you have downloaded flash tool zip file and locate "driver" there. Open it and install the C5302/03/06 driver for your phone. After installation of drivers open Flashtool.
4) Connect your Xperia SP to your PC now. Make sure that the connection is up to the mark.
5) Hit the smart lightening button on the right upper left side and select “Fastboot Mode.”. Make sure that usb debugging is on when you connect to PC
6)On the right side, click on “Reboot Device into Fastboot Mode.”
(If this doesn’t work for you, manually put your device into Fastboot Mode and connect it to your PC. To do so, turn off your Xperia device and now connect to your PC while keeping the Volume Up key pressed. As soon your PC detects your device,the blue LED will turn on showing fastboot mode.)
7) Now click on “Select Kernel to flash”.
8)In the format selection, by default it will be “*.sin”. Change it to *.elf.
Now select the DoomLord Advanced Stock Kernel.elf file that you downloaded first of all and flash it.
9)This kernel will flash CWM recovery in your device. Disconnect your device now.
Turn it on, as soon as you see the Sony Logo, press Volume – Key 5 to 6 times and you should see the CWM recovery interface now.
Install Recovery on Locked Bootloaders
http://forum.xda-developers.com/showthread.php?t=2352920
Go to this link and follow the instructions (Thanks to Dimtrov)
That's IT! Congrats! You rooted your Xperia SP!
Stock Kernel you downloaded keep it as if anything goes wrong during flashing the DoomLord's Kernel you can flash your original Kernel back to your device!
If anyone wants Unlocking Bootloader Tutorial just reply below
Hit thanks! ;D I definitely helped
***My Works***
Most Beautiful and Mesmerizing bootanimation for Xperia SP! ---> [http://forum.xda-developers.com/xpe...zing-boot-animation-xperia-sp-t2831628/COLOR]
]Official Android L boot animation for Xperia SP in two variants PURE WHITE AND ORIGINAL BLACK ---> [http://forum.xda-developers.com/xpe...id-l-boot-animation-xperia-sp-t2833128/COLOR]
UP movie boot animation for Xperia SP! ---> http://forum.xda-developers.com/xperia-sp/themes-apps/bootanimation-disney-studios-movie-boot-t2832873
Request your bootanimations here! ---> http://forum.xda-developers.com/xperia-sp/themes-apps/boot-animation-request-desired-t2833559
EDIT : Animation compelete check this threadhttp://forum.xda-developers.com/xperia-sp/themes-apps/bootanimation-playstion-2-boot-t2834872
It requires lots of time and fund in order to create these files. Me being alone as a developer is really impossible to manage alone.! Please consider a small amount of donation and help me as it can help me get my resources Thank you!
1. There's no need to change kernel to root
2. U can't install custom kernel with locked bootloader,u're ure giving instructions to brick phones
3. There's no need for towelroot to have internet acces to work
4. And talking about Towelroot, there's a thread with towelroot in this forum (about three actually)
5. There are recoveries for locked booleaders, also there's an index with it in general
5. What with all ad f.ly and ad links? are u trying to make money? put a link to the original thread or the links of creators if is not your work
6. Red is a really bad color to be the main in the thread
just sayin'
QBerto said:
1. There's no need to change kernel to root
2. U can't install custom kernel with locked bootloader,u're ure giving instructions to brick phones
3. There's no need for towelroot to have internet acces to work
4. And talking about Towelroot, there's a thread with towelroot in this forum (about three actually)
5. There are recoveries for locked booleaders, also there's an index with it in general
5. What with all ad f.ly and ad links? are u trying to make money? put a link to the original thread or the links of creators if is not your work
6. Red is a really bad color to be the main in the thread
just sayin'
Click to expand...
Click to collapse
Apologies on first part for letting adfly links on the tutorial wasn't aware of this rule.
Secondly towelroot gave error on my Xperia SP that "Please make sure you are connected to internet" that's why I advised to stay connected likewise SuperSU would take Internet connetion to download then why not to be on safe side
As considered with that custom kernel flashing thing thank you for correcting me! You saved a blunder mishap and prevented it from happening thanks a LOT!:highfive::angel:
I always give credits to the one who created the original stuff! I NEVER TAKE CREDITS FOR OTHER'S WORK
And RED is a color that is easily hilighted and people actually pay more attention to words written in red rather than any other color
Just Saying
:good:
Wut? Towelroot now needs internet conection? D: maybe sounds paranoic, but don't like xD
and one more thing, you can install SU from the zip w/o recovery, just open the zip with a file manager and look into 'common' folder, there's a Superuser.apk in there, install as normal APK, and you can update binaries with the zip w/o internet too (just open SU app and click normal, the same as you said)
QBerto said:
:good:
Wut? Towelroot now needs internet conection? D: maybe sounds paranoic, but don't like xD
and one more thing, you can install SU from the zip w/o recovery, just open the zip with a file manager and look into 'common' folder, there's a Superuser.apk in there, install as normal APK, and you can update binaries with the zip w/o internet too (just open SU app and click normal, the same as you said)
Click to expand...
Click to collapse
As for being paranoic check this out http://www.shadowandy.net/2014/06/geohots-towelroot-features-one-click-root-many-kitkat-devices.htm and read cooment of guy named Alin guess I am not the only one facing this issue
As far as SU is considered I told both the method stop daydreaming and check the post clearly
There is an existing thread for this.
[LB/UBL] Root Your device with just an app!
Please use this existing thread for further posting.
@Tech N You Please search for existing threads before creating new threads.
In case you have not read the XDA Rules yet here is a link.....
The XDA Rules
Thread closed
ive been seeing enough and more posts asking about flashing OxygenOS. I'll try and explain in simple terms. read carefully and only then try it.
I TAKE NO RESPONSIBILITY IF YOU SPOIL YOUR DEVICES. YOU ARE DOING THIS AT YOUR OWN RISK!
if you have a custom recovery skip to step 7
1. Your devices needs a custom recovery. to install one you need to be rooted. to root u need an unlocked bootloader. OnePlus claims that you wont loose warranty on rooting and unlocking so your safe there unless u do something wrong. so be cautious.
2.for unlocking rooting and flashing i recommend using Bacon Root Toolkit. even though i know to do it the Oldschool way. this is much more simple and u really cant go wrong with the toolkit its NoobFriendly. download the toolkit from the following link and install it along with the drivers. http://www.wugfresh.com/brt/
3. once installed choose the version of CM you are running. the toolkit will automatically download all required files. once in u will have to set up the drivers. the instructions for that are well explained in the toolkit please follow it there.
4. after the drivers are set up first u need to unlock. REMEMBER UNLOCKING WILL CLEAR ALL DATA!. so backup all required data.for the internal SD card u can connect the phone to the computer as an MTP device and copydata, for the apps you can backup using Helium and copy the helium folder to the computer. please do not post comments telling that you lost all data there is NO WAY to recover that data once you unlock.
5.press UNLOCK in the toolkit, it will guide you through the process. after unlock when you switch on the phone itll be as good as new you will have to go through the procedure of logging into google etc. once done head over to settings enable developer options and tick ADB. DONT FORGET TO DO THIS
6. Now you need to root your device. by default the toolkit uses SUPERSU to root and TWRP as custom recovery its perfectly fine unless you intend on changing it later on stick to these two. remember to tick CUSTOM RECOVERY under the root option. press root and follow the steps. it pretty much does everything u jut have to keep confirming.
7. Hoping that right now your rooted and have a custom recovery, if not please go through the previous steps.
now we need to download the oxygenOS head over to the forum and download or use this link https://oneplus.net/oxygenos, once downloaded check the size it should be 705MB incase its not the download again may be the download got corrupted.
8. IMPORTANT STEP FOR NEWBIES
once u download u have ONE .zip file named "oxygenos_1.0.0.zip" extract that file and u will get a folder named "oxygenos_1.0.0" leave it there DONT EXTRACT ANY FURTHER!. the folder will contain two files "oxygen_1.0.0_flashable.zip" "oxygen_1.0.0_flashable.md5" leave them as they are. preferably copy this folder containing the two files to the root of the phone. in simple terms put it in your phone memory without putting it into any other folder.
9. Now you have your files ready you need to head over to the recovery. two ways of doing it. you can go to settings developer options and tick advance reboot. now when u press reboot u get an option to reboot recovery and bootloader. choose recovery.
another way of getting to recovery is shut down the phone hold the buttons POWER+VOLUME DOWN once the phone comes on leave the power button and hold VOLUME DOWN till the recovery shows up.
10. Once your in TWRP u have an option to backup your rom. You could do this as a precaution if anything goes wrong u can restore from this backup file. fro backing up press backup and choose the partitions you want to backup and swipe to backup. the backup should be around 2-3gb i think. once backed up copy the file from the TWRP folder on your phone to the computer.
11. since you are changing the ROM completely you need to factory reset once before flashing. in TWRP press WIPE and swipe to factory reset. and go back to home dont reboot device.
12. FLASHING THE ROM: in TWRP press install in the list find the folder oxygenos_1.0.0. in that folder click on the file "oxygen_1.0.0_flashable.zip" and then swipe to flash. the flashing can take a while dont do anything while its in progress.
13.once flashed reboot system. the first reboot will take time let it happen do not get worried and try restarting just let it take its time it has to set up everything for u.
14. Now you should be having OXYGEN OS... use it appreciate it rather than criticizing it. incase u feel like customizing it try out XPOSED. though it is still in testing for L it shouldnt be too buggy. gravityBox is compatible with lollipop.
15. incase you feel like going back to CM.. head over to the toolkit connect the phone (remember to enable ADB) doesnt matter which build u set. press FLASH STOCK+UNROOT choose the CM build you want and let it do its work. follow the instructions.
some may point out that the toolkit has an option to flash the rom as well. yes it does but i wont dive into that now. this method is simple enough. but if u know how to do it that way u sure can
PS: KEEP YOU BATTERY FULLY CHARGED WHILE DOING ALL THIS. INCASE THE PHONE DIES WHILE FLASHING ITLL BE BRICKED.
please correct me if i went wrong anywhere.
hope this helps.
shoaib30 said:
ive been seeing enough and more .....
Click to expand...
Click to collapse
There is absolutely no need for this thread - it's all been covered before. Flashing OOS is no different to any other custom ROM.
You text/formatting is abysmal. You recommend using the toolkit, WTF? This device is the easiest ever created for unlocking/rooting and using a toolkit is a BAD idea as if it goes wrong you will end up confused and not knowing what to do next. Anyone who can't unlock / root / flash TWRP on this device should not be attempting to install a custom ROM anyway.
What you have posted is actually more confusing for a 'noobie' than what is already out there, I'd suggest this thread should probably be deleted and people with questions can simply search and find the useful instructions which already exist.
SimonTS said:
There is absolutely no need for this thread - it's all been covered before. Flashing OOS is no different to any other custom ROM.
You text/formatting is abysmal. You recommend using the toolkit, WTF? This device is the easiest ever created for unlocking/rooting and using a toolkit is a BAD idea as if it goes wrong you will end up confused and not knowing what to do next. Anyone who can't unlock / root / flash TWRP on this device should not be attempting to install a custom ROM anyway.
What you have posted is actually more confusing for a 'noobie' than what is already out there, I'd suggest this thread should probably be deleted and people with questions can simply search and find the useful instructions which already exist.
Click to expand...
Click to collapse
im sorry ill take it off. i had ppl asking me in person so i thought i can explain here and send the link to them. my bad
Please don't create duplicate threads. There are already threads open that cover this topic.
Thread closed.
I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
fir1996 said:
I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
Click to expand...
Click to collapse
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
JudgeDread11 said:
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
Click to expand...
Click to collapse
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Dylan2232 said:
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
JudgeDread11 said:
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
Click to expand...
Click to collapse
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Dylan2232 said:
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Click to expand...
Click to collapse
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying anything is learning how to backup and restore.
JudgeDread11 said:
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying any freething is learning how to backup and restore.
Click to expand...
Click to collapse
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Dylan2232 said:
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Click to expand...
Click to collapse
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
hi , good news for Huawei y5 2017(MYA-L22) users.
Download latest lineage14.
visit to my blog.
cheers
https://p55novo.blogspot.com/2018/07...e-141-for.html
JudgeDread11 said:
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
Click to expand...
Click to collapse
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Dylan2232 said:
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Click to expand...
Click to collapse
For rooting you need unlocked bootloader ( if you don't do ir then below won't work).
1)download the 4pda app from google play store and register an account .
2) download the TWRP.img file from 4pda website here is the link
https://4pda.ru/forum/index.php?showtopic=823938&view=findpost&p=74424572
3) enable developer mode in your phone by going to setting about phone , tap 6 times on the build number.
4)go to developer mode and enable usb debugging and oem factory unlock .
5) go to your pc install adb here link https://forum.xda-developers.com/showthread.php?t=2588979
6) now conect the phone to the pc and run cmd , type adb reboot bootloader . (Your device ahould restart and enter bootloader mode (white screen)).
7) now take the TWRP.img (must be copyied to desktop ) and type in cmd cd desktop.
8) type fastboot flash recovery TWRP.img (change the file name to TWRP ).
9) type fastboot reboot.
Now you have successfully install TWRP on your device.
Continue... If replied
Hi All,
In the best interest to provide clarity I'm creating this quick and easy tutorial on how to root your Razer Phone 2 after the Pie Upgrade. Please send me any feedback to improve this post, we need to build up a strong community.
*As usual, I'm not responsible of any damage or brick to your phone, do it at your own risk.
Pre-Requirements:
-Be sure to have at least 70% of charges... or plug your phone to power
-Backup anything you consider important
-Already installed Pie Upgrade via OTA or Side Loaded
-Enable Developer Options
• Open Phone "Settings" and scroll down.
• You will see an option "Build Number".
• Simply tap on it 7 times to enable it on your Android Oreo based device.
• Your device immediately display a message on screen that will say "You are now a developer".
• The Developer Option is now available in the Settings>System>Developer Options. Enjoy!
- Install Android Drivers (https://developer.android.com/studio/run/win-usb) and ADB, I personally recommend -[TOOL]Minimal ADB and Fastboot [2-9-18] - https://forum.xda-developers.com/showthread.php?t=2317790
-Unlock Bootloader
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
• Using ADB commands reboot on bootloader
adb reboot bootloader
• After reboot completes follow phone menus and select "UNLOCK BOOTLOADER"; accept all warnings, after restart you have completed the unlock.
Root and Installing Magisk
Since our phone doesn't have a proven customer recovery fully working (Ex TWRP) Magisk needs to be installed by manually patching the device boot image.
Making leverage of Warrior1988 post [Root Magisk Pie Update For Unlocked Devices] all credits to him. Download the image from his post
• Boot in fastboot mode To boot into fastboot, press and hold the Power button + Volume Down Keys for few seconds; Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Install Magisk Download the apk and install it as usual on your RP2, that should be all.
DONE!!!! You now have a unleashed the beast! Please send me any recommendations to improved this guide.
chpimentelpr said:
Install Android Drivers and ADB
Click to expand...
Click to collapse
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
chpimentelpr said:
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
Click to expand...
Click to collapse
I assume this is where we plug our phone into our computer?
chpimentelpr said:
• Using ADB commands reboot on bootloader
Click to expand...
Click to collapse
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
chpimentelpr said:
• Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash*boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
AbsoluteContingency said:
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
I assume this is where we plug our phone into our computer?
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
Click to expand...
Click to collapse
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Warrior1988 said:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
No asterisk. Cool. Got it. Thank you, dude.
The drivers are the regular ones for android nothing specific, they can be downloaded from their SDK https://developer.android.com/studio/run/win-usb
App root detection?
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Bounty33 said:
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Click to expand...
Click to collapse
You can use magisk to hide the root from those apps. In general banking app are not affected by root. Google pay could be affected, but I don't use it so can't be sure. And you can always unroot.
AbsoluteContingency said:
No asterisk. Cool. Got it. Thank you, dude.
Click to expand...
Click to collapse
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
chpimentelpr said:
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
Click to expand...
Click to collapse
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
AbsoluteContingency said:
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
Click to expand...
Click to collapse
Yes, install them as any other driver.
After rooting can you relock the boot loader or will that brick the phone?
ndragon798 said:
After rooting can you relock the boot loader or will that brick the phone?
Click to expand...
Click to collapse
Not sure, but why you want to relock the boot.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Mostly to get rid of the startup message
Very nice. I've rooted a ton of phones over the years, but they had more established communities and had well-explained (and tested) methods of rooting. The previous guide posted (that you referenced) was fine enough, but it was very much lacking a couple prerequisites that I was wondering/concerned about. This guide has cleared all of that up for me, and I now feel confident about rooting this phone.
Just as soon as I charge up the phone and install the OTA I've been avoiding until now... lol. Hoping somebody will make a Magisk module to move the clock back to where it belongs (if they haven't already).
EDIT: Just wanted to add my success story to this. Only thing I had to do that wasn't listed in the instructions (but makes sense) is that fastboot didn't work until I enabled USB Debugging (again, after the wipe and reboot), and I had to very manually tell the computer which driver to use (ADB) after that. Didn't have that issue for the bootloader instructions beforehand (that time, the driver worked automatically), so I figured I'd mention it.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
ndragon798 said:
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
Click to expand...
Click to collapse
I don't believe encryption is supported at the moment, and I don't encourage you to try it until TWRP is fully supported since you may end up in a boot loop. I'm eagerly waiting for the full encryption capability, so I will let you know as soon as something come up.
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
ChronosTrigger said:
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
Click to expand...
Click to collapse
i'm glad it helps.
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
xttweaponttx said:
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
Click to expand...
Click to collapse
I doubt the issue with the wifi is related with the image, since it doesn't have anything to do with it. If your phone doesn't detect the update you will need to sideload it. Then try the root guide again. Let us know how it goes, it the first time I hear something wrong with WIFI after rooting.