Hi, I have a problem where I can not do root in my mi-4c after this miui 8.2 update came out, there was a day when my cell phone updated and restored everything, I flash everything in TWRP, I executed the script To disable DM verification and when I gave flash in supersu it gave infinite loop, does anyone know how to solve this? Is it necessary to downgrade to re-rotate the device again? Can someone tell me what the source of the problem is? If it is the new binary su or if the script does not work anymore?
Must flash the newest version of SuperSU
http://download.chainfire.eu/supersu-beta
isaque-v-soares said:
Hi, I have a problem where I can not do root in my mi-4c after this miui 8.2 update came out, there was a day when my cell phone updated and restored everything, I flash everything in TWRP, I executed the script To disable DM verification and when I gave flash in supersu it gave infinite loop, does anyone know how to solve this? Is it necessary to downgrade to re-rotate the device again? Can someone tell me what the source of the problem is? If it is the new binary su or if the script does not work anymore?
Click to expand...
Click to collapse
Had this problem too.
In version 8.2.x.x the system partition has no free space to accommodate supersu although twrp doesn't complain when installing supersu- this corrupts the system partition.
You should reflash the system partition and start over.
Before installing supersu you should delete some useless system apps like AnaliticsCore, BaiduLocation (or smth), SystemAdSolution using twrp's file manager to make some space on the system partition.
If you are not comfortable with that you should try Magisk.
thanks bro i try
Can you tell me what this AnaliticsCore app is for? It n exists only in the miui already used other devices like moto G2 and moto maxx and I already saw this app there
Related
i would like to install the latest OTA update for 4.4.2 but it keeps failing.
i flashed stock recovery and i have stock kernel.
when i apply the update it just states that the update was unsuccessful.
any idea on how to solve this? i have tesco moto g on which i flashed stock UK firmware. it is only rooted. i do not think that i have deleted system apps and i tryed disabling xposed modules.
could someone make a flashable zip if it is possile?
i would really appreciate it :victory:
I use the latest TWRP as my recovery and it updates the OTA files fine, so I would suggest trying that.
Atomix86 said:
I use the latest TWRP as my recovery and it updates the OTA files fine, so I would suggest trying that.
Click to expand...
Click to collapse
i installed TWRP and disabled all xposed modules. the update went fine. the only thing is when it booted i got: an unexpected error has occured. please try again later.
should i worry about it? system version is now 176.44.1.
ManBearrrPig said:
i installed TWRP and disabled all xposed modules. the update went fine. the only thing is when it booted i got: an unexpected error has occured. please try again later.
should i worry about it? system version is now 176.44.1.
Click to expand...
Click to collapse
I didn't get that error so I can't answer that I'm afraid, sorry.
Sent from my Google Nexus G -
hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........
Just flash this super user zip file
http://forum.xda-developers.com/attachment.php?attachmentid=3655401&d=1456122222
is supersu installing systemless?
make sure to do this first in twrp terminal: "echo SYSTEMLESS=true>>/data/.supersu"
Sushilsingh said:
hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........
Click to expand...
Click to collapse
You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.
The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572
acejavelin said:
You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.
The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572
Click to expand...
Click to collapse
buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?
Sushilsingh said:
buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?
Click to expand...
Click to collapse
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
acejavelin said:
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
Click to expand...
Click to collapse
well, all the things get installed successfully but even the installation of supersu.zip file also
but it always reboot without any root access or supersu app
i try to install supersu from playstore but it wont help much
after that i tried BETA-SuperSU-v2.62-3-20151211162651.zip this version
and this version does the job
thanks buddy, i really appreciate your help.
acejavelin said:
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
Click to expand...
Click to collapse
Thanks, thats works for me..! i tried 3 time until work
PD: (when you root, install recovery or unlock bootloader without enough time happens this kind of things)..
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.
As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data
https://forum.xda-developers.com/on...-to-uninstall-magisk-module-t3940369#poststop
Just had the same issue an hour ago. Do this then re-root your phone again. Easy. Then re-install magisk modules.
spart0n said:
As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data
Click to expand...
Click to collapse
Had the same issue.
Same here. I just reflashed TWRP (flash boot command), flashed the TWRP installer zip, rebooted recovery and then flashed Magisk. That solved it.
By the way, theres a new TWRP out for the 7 Pro.
I got the same problem but my internal storage is encrypted (it shows 0kb). TWRP is not asking for PIN to unencrypt the partition. What can I do now?
Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)
dude9946 said:
Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)
Click to expand...
Click to collapse
Your best bet is to use the oxygen updater app, download 9.5.9 and then copy it to a PC then use boot.img extract thingy and then use magisk to patch it and then use fastboot to to root it
Hello!
I am on an older version of Android 11 and I would like to install the latest Android 11 OTA without losing root and TWRP.
I know that I could just manually flash the lasted Android 11 firmware, then re-install TWRP and Magisk, but this would mean losing all data and having to reinstall apps, restore backups, etc...
So I was wondering if there were a quicker way to install OTA updates without losing data and root.
I know that there are many articles on the subject but they all refer to a previous version of TWRP and Magisk. Because TWRP 3.6.0 sports a completely revamped codebase I would like to know what is the latest recommended method if any.
This is my system info:
Android 11 sargo-rq1a.201105.002-factory-2433e0c0
Magisk v23
TWRP 3.6.0-11_0
Japan region
PS I do not intend to update to Android 12 yet
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
reyqn said:
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
Click to expand...
Click to collapse
The flashall script will still remove TWRP and root though, right?
blksith0 said:
The flashall script will still remove TWRP and root though, right?
Click to expand...
Click to collapse
Yeah it does, you have to reflash them after
It's annoying that we can't choose the OTA android installs, it has to be the latest one. On some phones you can choose a local file, but I didn't find a way to do so with a pixel 3a.
If you were able to do this, in theory you could just flash the magisk module for twrp retention and preflash magisk on the unactive partition after installing the ota but before rebooting. Then just reboot and you keep everything.
I'm not ready to update to android 12 either (gravitybox, twrp), but I'll try then...
LastStarDust said:
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
Click to expand...
Click to collapse
I don't understand. Just flash the Full Factory OTA zip in TWRP. That won't remove any data. And you can just check the box to "Automatically flash TWRP after zip" so that you'll keep whatever TWRP you're using. Then you just have to reboot recovery (so that you're on the updated slot) and flash the Magisk APK in TWRP. Reboot and profit.
P.S. This post belongs in Q&A.
Captain_Throwback said:
I don't understand. Just flash the Full Factory OTA zip in TWRP
Click to expand...
Click to collapse
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
reyqn said:
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
Click to expand...
Click to collapse
That 'recommendation' is specific to incremental OTAs. Also, it not generally being supported isn't the same as it not being recommended.
TWRP will install the zip to the inactive slot, and then when you reboot, the device will automatically boot into the updated slot.
Thanks for the precisions, I'll know for the next time. TWRP really is awesome
hi everyone, i flashed pixel 3a to android 12 and now my imei is 004400.... and no service ..... what should i do?