Hi all guys Thanks for having help on this forum.
In short, my problem is.
I wanted to do the usual root procedures with on board Android 8.0 latest firmware no brand update, then put supersu on sd card go to download mode, odin, twrp flash, wipe total, flash twrp supersu and reboot.
After starting everything in place but as soon as I restarted, a red text appeared, from there it is no longer in recovery nor on the system I can only go to download mode but I have tried everything not flasha nothing is blocked by rmm state of samsung.
Ok after explaining the problem what can I do? Do you have a solution?
P.Š. I asked around and they told me that it takes the samsung box I have to pass by force there?
Dantes991 said:
Hi all guys Thanks for having help on this forum.
In short, my problem is.
I wanted to do the usual root procedures with on board Android 8.0 latest firmware no brand update, then put supersu on sd card go to download mode, odin, twrp flash, wipe total, flash twrp supersu and reboot.
After starting everything in place but as soon as I restarted, a red text appeared, from there it is no longer in recovery nor on the system I can only go to download mode but I have tried everything not flasha nothing is blocked by rmm state of samsung.
Ok after explaining the problem what can I do? Do you have a solution?
P.Š. I asked around and they told me that it takes the samsung box I have to pass by force there?
Click to expand...
Click to collapse
You should have deleted "security log agent" in system/app before rebooting.
stonedpsycho said:
You should have deleted "security log agent" in system/app before rebooting.
Click to expand...
Click to collapse
Yes i detected log security agent
Dantes991 said:
Yes i detected log security agent
Click to expand...
Click to collapse
Once I deleted that it has been fine for me. The post below may help you though.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
stonedpsycho said:
Once I deleted that it has been fine for me. The post below may help you though.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
but I can not flash the twrp
Dantes991 said:
but I can not flash the twrp
Click to expand...
Click to collapse
I think you need to flash the stock rom with Odin and basically start again.
You could just flash the dev-base rom which is basically just the stock rom but with all the above disabled already.
Related
I was trying to fix my google play "no connection error" but it didn't work so i just reset my phone as a last resort to try and fix this problem. It restarted in recovery mode i thought this was just a procedure and i just hit reboot -> system. it rebooted again into recovery mode i checked if there were any wtuck volume rockers but there aren't any help?
(FYI: one plus 3T: Rooted)
(FYI: link to what i used to try and fix my google play store:https: //forum.xda-developers.com/showthread.php?t=2273994)
What recovery are you running? Stock or TWRP?
bealer said:
What recovery are you running? Stock or TWRP?
Click to expand...
Click to collapse
TWRP
And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.
bealer said:
And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.
Click to expand...
Click to collapse
already did that but still brings me back into TWRP
TrappleV3 said:
already did that but still brings me back into TWRP
Click to expand...
Click to collapse
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.
Droid-2 said:
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.
Click to expand...
Click to collapse
you have a link to the file because i can't seem to find it. But thank you anyway for your help.
TrappleV3 said:
you have a link to the file because i can't seem to find it. But thank you anyway for your help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
mximer said:
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
Click to expand...
Click to collapse
Thank You.
Issue has been resolved. OP is my little cousin who's been messing around a bit too frantically [emoji14]
I restored his device with the unbrick tool by Haris K., all's peachy again. There are still some issues with TWRP for 3T, doesn't run nearly as smooth as on the OPO. It completely failed to restore any working system (both from backup or from reflashing). Sideloading seemingly worked, but rebooted to recovery again, adb push only resulted in errors. Are there any tweaked TWRP releases that can do better?
Cooked with Resurrected bacon!
Hi, I am new to this forum but old on android. My oneplus 3t brick yesterday and i don't know why. I never rooted phone and always update phone via OTA. I contacted Oneplus support yesterday and they arrange a remote session where they are unable to install anything via msmdownload tool. I download msmdownload tool yesterday from this forum and my phone works but there is no modem in it. I am unable to connect to wifi and SIM internet. Oxygen OS version install at the moment is 3.5.1 and android version is 6.0.1. Need help from some seniors.
Update by using on the of the official "full zips"? These include the modem, so I would think that would fix the problem, unless there is a more serious issue (hardware failure, etc.):
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
redpoint73 said:
Update by using on the of the official "full zips"? These include the modem, so I would think that would fix the problem, unless there is a more serious issue (hardware failure, etc.):
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
I tried multiple time but device stuck in boot loop. Downloaded ROM from Oneplus official site.
xusmanmalik said:
I tried multiple time but device stuck in boot loop. Downloaded ROM from Oneplus official site.
Click to expand...
Click to collapse
The full zip or the OTA?
Is your phone rooted/TWRP installed, or is it stock?
redpoint73 said:
The full zip or the OTA?
Is your phone rooted/TWRP installed, or is it stock?
Click to expand...
Click to collapse
Phone is stock not rooted. When i upgrade locally or through adb process phone stuck in bootloop.
xusmanmalik said:
Phone is stock not rooted. When i upgrade locally or through adb process phone stuck in bootloop.
Click to expand...
Click to collapse
Now i updated from 3.5.1 to 3.5.4 but issue still exist
xusmanmalik said:
Now i updated from 3.5.1 to 3.5.4 but issue still exist
Click to expand...
Click to collapse
Upgrading from 3.5.4 to 4.0.2 phone again stuck at boot screen. I don't know what to do know. Should i go for warranty claim or try something else. Need HELP!!!!
Thanks in Advance.
Are you able to go to fastboot mode? If yes, go for it:
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Install TWRP too. Now you're able to wipe everything and upload a full ROM to your device (Thanks to MTP-mode via TWRP, so handy!). Flash the full ROM and have a try .
MickyFoley said:
Are you able to go to fastboot mode? If yes, go for it:
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Install TWRP too. Now you're able to wipe everything and upload a full ROM to your device (Thanks to MTP-mode via TWRP, so handy!). Flash the full ROM and have a try .
Click to expand...
Click to collapse
Micky Thanks for the help. I will give a try and will inform further.
I ****ed up somewhere. Encryption unsuccessful Error.
xusmanmalik said:
I ****ed up somewhere. Encryption unsuccessful Error.
Click to expand...
Click to collapse
Do you have TWRP installed? Just wipe your phone, get an otg cable and a flash drive, you can flash everything from the flash drive
I revert back trying again now.
xusmanmalik said:
Micky Thanks for the help. I will give a try and will inform further.
Click to expand...
Click to collapse
Hi Micky Foley, I successfully followed all steps and now i am on twrp and su installed.
But still i am unable to install other ROM than 3.5.*
Your last option is the warranty then mate
Why does it always say 'only official binaries are allowed to be flashed' after rebooting my rooted note 8(n950f/ds)
After installing twrp recovery and flashing magisk, rebooting the phone would always result in a bootloop with the error message (only official binaries are allowed to be flashed)
any solutions for this?
creastwell95 said:
Why does it always say 'only official binaries are allowed to be flashed' after rebooting my rooted note 8(n950f/ds)
After installing twrp recovery and flashing magisk, rebooting the phone would always result in a bootloop with the error message (only official binaries are allowed to be flashed)
any solutions for this?
Click to expand...
Click to collapse
You HAVE to delete "securitylogagent" in system/app on the first boot after flashing TWRP.
stonedpsycho said:
You HAVE to delete "securitylogagent" in system/app on the first boot after flashing TWRP.
Click to expand...
Click to collapse
I had the same problem, even after flashing the rmm fix. after wanting to install a module finish on reboot and flashing stock ROM. I believe that the rmm fix should always be used after installing something.
I do not think that deleting the security log agent makes a difference, that's why the Samsung root removal fix is anyway
cogelindo said:
I had the same problem, even after flashing the rmm fix. after wanting to install a module finish on reboot and flashing stock ROM. I believe that the rmm fix should always be used after installing something.
I do not think that deleting the security log agent makes a difference, that's why the Samsung root removal fix is anyway
Click to expand...
Click to collapse
Use this zip instead. You can get it link on dr.ketan' rooting guides
anwar amu said:
Use this zip instead. You can get it link on dr.ketan' rooting guides
Click to expand...
Click to collapse
Yes thank you, I have had it for a while and I already used it, but I still distrust having to restart for some reason. If I have to do it I turn it off and go to the recovery to flash that zip before restarting. The problem of official binaries has already happened to me before, and it is very uncomfortable ...
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
jmalmberg said:
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
Click to expand...
Click to collapse
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
kc6wke said:
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
Click to expand...
Click to collapse
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
jmalmberg said:
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
Click to expand...
Click to collapse
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
kc6wke said:
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
Click to expand...
Click to collapse
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
jmalmberg said:
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
Click to expand...
Click to collapse
You need to format data (type yes) In twrp
kc6wke said:
You need to format data (type yes) In twrp
Click to expand...
Click to collapse
That worked! Thank you very much!!! I really appreciate it!!!!
jmalmberg said:
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
.
Click to expand...
Click to collapse
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Tigger31337 said:
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Click to expand...
Click to collapse
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
jmalmberg said:
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
Click to expand...
Click to collapse
Yup, I solved it. Thanks. I ended up using 3.2.3.official.
Rooting; ending in bootloop help
Sorry if I am hijacking this thread; thought to discuss here as the title "Trouble rooting my g6" still applies.
I have:
XT1925-13 (Moto G6 ALI) running stock Android Pie with build ppss29.55-34.
I have issues when I tried to root. I followed these steps:
I downloaded the factory image “ALI_RETAIL_9.0_PPS29.55-34_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip” and flashed it first. The mobile restarted and went to the first screen to select a language.
I rebooted it into bootloader, ran the TWRP as a temp by command “fastboot boot twrp-3.3.0-0-Ali.img,” which asked for the password.
I pressed cancel, and then I wiped cache and data.
Via ADB I transferred “adb push Magisk-v20.0.zip /sdcard” and “adb push no-verity-opt-encrypt-6.1.zip /sdcard”.
Then from TWRP, I installed Magisk. Then when installing no-verity, it gave an error “updater process ended with an error: 1 error installing zip file ‘no-verity-opt-encrypt-6.1.zip’.
Rebooted the device with hope and ended in a boot loop.
I also tried to use Magisk-v19.4.zip in the above steps and also tried to skip no-verity-opt-encrypt-6.1.zip. All ended in boot loop.
Any idea why? Are there any guides for the combination XT1925-13 (Moto G6 ALI) running ppss29.55-34?
Many thanks for your time.
Here is a solution
Flash original boot in fastboot followed by TWRP and reboot in recovery.
Install Magisk 19.4 in TWRP (3.3.x Android 9 OK) and reboot
You can update to 20 in Magisk Manager later
Hi guys. I rooted my phone before last update with "magisk patch ap file" method. But this method isn't working with the new firmware. And i tried to root with twrp too and it boots but in a black screen its written verification failed. So the both not working anymore. How u guys able to root your m20?
And how about havoc os gsi? Is there a guide for it?
alfadyn said:
Hi guys. I rooted my phone before last update with "magisk patch ap file" method. But this method isn't working with the new firmware. And i tried to root with twrp too and it boots but in a black screen its written verification failed. So the both not working anymore. How u guys able to root your m20?
And how about havoc os gsi? Is there a guide for it?
Click to expand...
Click to collapse
Hey all you need to do is wipe data partition by changing it's file format.
For that do the usual routing stuff.
Boot into Twrp
Formata Data -- Yes---
Flash RMM
Wipe--- Advanced -- data -- change/repair--- choose the one left of f2fs --- wipe --- f2fs now --- wipe --- back
Install magisk
Boom
Let me know if video is needed.
Rooted.ndroid said:
Hey all you need to do is wipe data partition by changing it's file format.
For that do the usual routing stuff.
Boot into Twrp
Formata Data -- Yes---
Flash RMM
Wipe--- Advanced -- data -- change/repair--- choose the one left of f2fs --- wipe --- f2fs now --- wipe --- back
Install magisk
Boom
Let me know if video is needed.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-m20/development/recovery-twrp-3-2-3-galaxy-m20-t3906705
first i did everything correctly in this post above.
after that i followed your procedure and i did everything correctly.
and it boot up without showing verification error. i was really happy and wanted to thank you. but after i rebooted my device. an then it said only official binaries allowed. then i flashed the firmware again because it cant be booted otherwise now it stucked at the samsung screen. i dont know why samsung makes things like this complicated.
edit: it booted after i format data. but still no root
alfadyn1 said:
https://forum.xda-developers.com/galaxy-m20/development/recovery-twrp-3-2-3-galaxy-m20-t3906705
first i did everything correctly in this post above.
after that i followed your procedure and i did everything correctly.
and it boot up without showing verification error. i was really happy and wanted to thank you. but after i rebooted my device. an then it said only official binaries allowed. then i flashed the firmware again because it cant be booted otherwise now it stucked at the samsung screen. i dont know why samsung makes things like this complicated.
edit: it booted after i format data. but still no root
Click to expand...
Click to collapse
Do you have twrp installed right now?
And did you flash RMM bypass?
Rooted.ndroid said:
Do you have twrp installed right now?
And did you flash RMM bypass?
Click to expand...
Click to collapse
yes i flashed rmm bypass v2 and i realized that there is version 3 i will try with it. and tell how it goes
---------- Post added at 12:02 PM ---------- Previous post was at 11:32 AM ----------
Rooted.ndroid said:
Do you have twrp installed right now?
And did you flash RMM bypass?
Click to expand...
Click to collapse
i didnt get the. only official relases error and it booted up. but i got a sweet bootloop right now . im done with it i ll never try to root again can u tell me how do i get rid of this bootloop
edit: got out of bootloop flashed official firmware. thank you for the help never gonna try to root again