Has anyone ran into the chance of seeing any custom recovery for this phone yet?
Unfortunately, I have no such experience
However, I successfully rooted the phone with Magisk
mingkee said:
Unfortunately, I have no such experience
However, I successfully rooted the phone with Magisk
Click to expand...
Click to collapse
How did you do that since the current way is to rename the apk and flash in a custom recovery?
1 Unlock bootloader
2 get stock firmware from program, forgot the name is the recovery stuff for moto
3 extract boot l.img
4 install magisk app and click install in the app, choosing patch boot.img
5 open adb adb reboot fastboot fastboot flashing boot boot.img
Viola rooted. I don't see any twrp, roms or anything. Could try a different variant I know moto g stylus twrp is really moto g 8 pro, or something like that. I'd back up with the recovery program tho, it has saved me when messing with flashing roms. GL
I also got root albeit tricky since trying root on the MetroPCS version will make the screen lose all touch functionality.
What good is root on this phone with you can't do anything with Android 10 being Read Only. I've been reading up on that and even in custom recovery it still is Read Only. That's the problem. So yay we got root but can't modify anything in it.
Articul8Madness said:
I also got root albeit tricky since trying root on the MetroPCS version will make the screen lose all touch functionality.
What good is root on this phone with you can't do anything with Android 10 being Read Only. I've been reading up on that and even in custom recovery it still is Read Only. That's the problem. So yay we got root but can't modify anything in it.
Click to expand...
Click to collapse
Main reason for me to root would be to bypass Hotspot limit via MagiskHide Props Config, and Screen2Auto AA mod/hack to send all apps to Car Stereo.
Does this touchscreen bug affect the T-Mobile version of the Ace 5G? I haven't ordered one yet.
Related
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
buyslake said:
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
Click to expand...
Click to collapse
First of all, no need to use 10D tot file anymore. Download and install 20A kdz front autoprime located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20a-rom-flashable-zips-imgs-t3511294
Once that's installed, set up your system and then follow the following guide to get TWRP an root:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
After you have TWRP and root download the flashable 20F zip and install from TWRP (make sure to delete recovery from boot.p file after installing and also flash root). Here's the link to 20F:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20f-rom-flashable-zips-imgs-t3592855
If you follow all of that, you will be on stock 20F, rooted and with TWRP. After that, I recommend checking out the following custom kernel and installing that and using magisk instead of SuperSU. Kernel located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Hopefully that helps, if you need more help just ask.
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
buyslake said:
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
Click to expand...
Click to collapse
After flashing the 20F version from TWRP, it creates a recovery from boot.p file in the system directory. If you don't delete this file before rebooting, you will lose TWRP. So, after doing the recowvery method to get root and TWRP and then after you flash the 20F from TWRP, after it's done flashing go to main menu of TWRP, click on mount, check system, go back to main menu, click advanced, click file manager and go-to system directory and click on the recovery from boot.p file and then delete. Now you can reboot without losing TWRP. Then you can flash SuperSU or magisk for root
Your Device software cannot be checked for corruption. Lock the bootloader
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
buyslake said:
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
Click to expand...
Click to collapse
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Where is Magisk?
jeffsga88 said:
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Click to expand...
Click to collapse
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
buyslake said:
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
Click to expand...
Click to collapse
No. I said currently there is no way to get rid of that message unless you lock the bootloader and you can't do that after modifying the system (i.e. installing TWRP and root). I said magisk will allow you to pass safety net. All that does is allow you to use apps that won't work with root / unlocked bootloader. If you don't use apps like Android pay or other apps that don't work when rooted, it really isn't necessary to switch from SuperSU to magisk. Anyways, if you're interested in magisk use Google (or XDA search) and search magisk XDA.
Could anyone please point out a way to root my phone(in title), as of this day. There are many methods. So I am confused. I recently read about magisk manager, used to root. Does it work? I just wanted to know the latest method, easier one of any. Also can TWRP manager be used to flash recovery in phone or should it be done flashing TWRP. Img, file.
Please forgive me if i posted in wrong section.
Thanks in advance.
enusri said:
Could anyone please point out a way to root my phone(in title), as of this day. There are many methods. So I am confused. I recently read about magisk manager, used to root. Does it work? I just wanted to know the latest method, easier one of any. Also can TWRP manager be used to flash recovery in phone or should it be done flashing TWRP. Img, file.
Please forgive me if i posted in wrong section.
Thanks in advance.
Click to expand...
Click to collapse
Use PC via ADB (fastboot)to flash TWRP. Flash Magisk in recovery, then dl Magisk manager from play store.
Magisk works very well.
This all is assuming your boot loader is unlocked.
Good luck.
melp57 said:
Use PC via ADB (fastboot)to flash TWRP. Flash Magisk in recovery, then dl Magisk manager from play store.
Magisk works very well.
This all is assuming your boot loader is unlocked.
Good luck.
Click to expand...
Click to collapse
So instead of supersu, we use magisk?
And I read somewhere also that using magisk we can still get updates to our phones. Is that right?
Also there is a TWRP manager in play Store can we use it to flash TWRP instead of ADB?
Thanks for the steps though.
enusri said:
So instead of supersu, we use magisk?
And I read somewhere also that using magisk we can still get updates to our phones. Is that right?
Also there is a TWRP manager in play Store can we use it to flash TWRP instead of ADB?
Thanks for the steps though.
Click to expand...
Click to collapse
My experience with TWRP manager has been it breaks my recovery. No idea why so I flashed via PC. Not sure you can still receive updates when your boot loader has been unlocked. Depends on a lot of factors. Someoneelse will have to answer that question.
melp57 said:
My experience with TWRP manager has been it breaks my recovery. No idea why so I flashed via PC. Not sure you can still receive updates when your boot loader has been unlocked. Depends on a lot of factors. Someoneelse will have to answer that question.
Click to expand...
Click to collapse
OK thanks.
An unlocked bootloader doesn't prevent you from receiving updates from Motorola. But I think rooting the ROM will prevent installation of further updates.
I don't think Motorola is going to push any further updates. So just do anything you want with your phone (personal opinion).
bin.sayantan said:
An unlocked bootloader doesn't prevent you from receiving updates from Motorola. But I think rooting the ROM will prevent installation of further updates.
I don't think Motorola is going to push any further updates. So just do anything you want with your phone (personal opinion).
Click to expand...
Click to collapse
I've never received a update notice.
I would have to agree... There is little chance of getting another update, and if we did it would just be a simple security update and not important.
And no, even with Magisk you cannot apply an OTA update, it will fail.
Unlock your bootloader, flash the twrp recovery using adb fastboot...then wipe the stock rom, flash custom rom along with SuperSU....enjoy! (Processes are same but you should use the latest versions of all these...)
https://forum.xda-developers.com/2015-moto-g/general/guide-osprey-moto-g3-begin-how-to-t3599251
This is the first phone where I don't plan to install a custom ROM, and I don't know how OTA updates work while rooted.
Can they still be downloaded/installed normally while rooted? If so do I need to re-apply root each update? Does updating while rooted, or reapplying root afterwords wipe apps/settings?
I'm not sure if these are questions that can even be answered now, before anything has shipped, but worth a shot.
I might be wrong but I believe once you root you have to side load any OTA updates that come along and you may have to reroot and no this won't wipe ur phone
Flash Fire will be the way to go....
On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.
me_droid said:
On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.
Click to expand...
Click to collapse
I started with full image and removing the w.
Then Google started releasing OTA So I used flashfire and it worked fine.
I tried sideloading and it worked also.
During the whole period, I never lost root or hotspot accept for the last update I lost hotspot because of an update changing Carrier entitlement. So I had to go about modding system file but. My hats off to developers. I suggest everyone donates to the people who make things available.
Thanks,
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Nice tutorial. Is there a way to install magisk any easier if I don't care about OTA's? Can't I just flash magisk and carry on or do I still have to worry about the A/B partitions?
I did this and now I'm stuck in a bootloop!
FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
I followed this procedure and everything seemed to be fine until reboot. At first it would attempt to boot, get to the screen with the G logo, and then after a few seconds reboot again, showing the unlocked bootloader warning screen. i interrupted the loop with the power button, and now I get to the G logo with the small grey animated progress bar going back and forth, but it hangs there and never completes booting..
Checked out realme's website and they state that unlocking and flashing roms does not void warranty but rooting the phone does.So what are the possibilities/things one can do with the phone while unlocking it but not rooting it.
Also is there a safe rooting method which doesnt leave traces after unrooting again? So that the device can be used in warranty.
Thanks in advance for any advice.
If you have Realme 5 Pro (not q) then you can still flash custom rom, recovery or basically anything with adb. It's just you won't be able to do root stuff on your phone but you'll need pc. Still you could flash custom kernel, rom, or ota update. Magisk is called systemless root for it does root your system without touching the system files so after uninstalling it and flashing stock rom realme service shouldn't ever be able to tell that your phone was ever rooted. I live in Hungary and my previous Xiaomi phone was installed with custom rom, kernel and Magisk root. Before taking it to Xiaomi service I did a clean flash, reverted everything to stock and warranty was still good to go. That'd be just an example. Don't know Realme how is with these stuff.
greenys' said:
If you have Realme 5 Pro (not q) then you can still flash custom rom, recovery or basically anything with adb. It's just you won't be able to do root stuff on your phone but you'll need pc. Still you could flash custom kernel, rom, or ota update. Magisk is called systemless root for it does root your system without touching the system files so after uninstalling it and flashing stock rom realme service shouldn't ever be able to tell that your phone was ever rooted. I live in Hungary and my previous Xiaomi phone was installed with custom rom, kernel and Magisk root. Before taking it to Xiaomi service I did a clean flash, reverted everything to stock and warranty was still good to go. That'd be just an example. Don't know Realme how is with these stuff.
Click to expand...
Click to collapse
Thank you so much for the prompt and clear reply.Really did clear a lot of stuff for me. Yes I do have realme 5 pro and the problems was with the audio jack output .Its terrible so wanted to flash dolby and / viper . I'll give adb a go then. Thank you again.
Firebolt1994 said:
Thank you so much for the prompt and clear reply.Really did clear a lot of stuff for me. Yes I do have realme 5 pro and the problems was with the audio jack output .Its terrible so wanted to flash dolby and / viper . I'll give adb a go then. Thank you again.
Click to expand...
Click to collapse
You're welcome. If indeed only root void warranty then you're free to flash to your linking almost everything via usb adb. Except for root ofc.
thank you again for the same.
Firebolt1994 said:
thank you again for the same.
Click to expand...
Click to collapse
After installing twrp via adb you can flash stuff from your sd card. Don't forget to always have a backup zip file of your stock rom in case something goes wrong. And don't forget to use backup in twrp for data partition sometimes when you feel you're about to do something risky that might flip your system's stability. I do that all the time ?*
Yep I will.Its a new phone so more of a reason to take precautions .
Firebolt1994 said:
Yep I will.Its a new phone so more of a reason to take precautions .
Click to expand...
Click to collapse
Exactly. Have fun but take care.
bootloader unlock 7 ROOT
Does bootloader unlock will prevent running of Bank Applications?Can this Realme5Pro be rooted and installed Twrp using Kingoroot/
Waiting with thanks.
Please any one give an advice
TWRP
If TWRP is installed via ADB in my unrooted Rm5P will it become rooted and prevent bank applications?
pnsdhrn said:
If TWRP is installed via ADB in my unrooted Rm5P will it become rooted and prevent bank applications?
Click to expand...
Click to collapse
Magisk has an option to hide from those apps, I used it all the time with secure banking apps
If I unlock bootloader and flash TWRP, can this TWRP can be used as my stock recovery further for flashing zips(not custom ROMs)? Also will Bank apps work in this set up without any problems?
Yes, you can use TWRP to flash anything. Yes, bank apps will work as long as you have magisk installed.
I just bought a new Redmi 9a with hopes to root this device. But after much time and effort in attempting to root it. I was just stuck with a boot loop. I did all the necessary requirement in order to root. Unlocked Bootloader (waited 7 days) Downloaded and Installed Updated Drivers..etc
I was successful in almost all steps of the rooting process until the one where im supposed to enter the twrp recovery mode. Is there a solution to this? or is because the twrp file is unofficial? Is there no chance to root this model of phone just yet?
magicayk said:
I just bought a new Redmi 9a with hopes to root this device. But after much time and effort in attempting to root it. I was just stuck with a boot loop. I did all the necessary requirement in order to root. Unlocked Bootloader (waited 7 days) Downloaded and Installed Updated Drivers..etc
I was successful in almost all steps of the rooting process until the one where im supposed to enter the twrp recovery mode. Is there a solution to this? or is because the twrp file is unofficial? Is there no chance to root this model of phone just yet?
Click to expand...
Click to collapse
There is actually no reason to install TWRP because nothing seems to be working after a flash, like Magisk.
I rooted mine by flashing boot.img from Tigrouzen, you can find his work in dev section. The only thing you have to do is to play with ADB commands, it should take 5 minutes at most.
Important point : I'm on MIUI 12. I really dont know if it work on the newest update.
To finish, like everytime, sorry for my scoolish English.