Database Develop

[Q] M7 Rooting issue (Not bricked/Recovery access only)

Hi all,
This is my first post here. Even though i follow some threads on this forum, I've never posted cause i never needed to. All my questions were generally answered in the threads.
However, I believe I've run into a unique problem.
Yesterday, I started rooting my phone using this tutorial: htconeroot.com/ htc-one-root/ how-to-root-htc-one-windowsmaclinux
And i got pretty far. In half an hour, I had successfully unlocked the bootloader, flashed the recovery program (TWRP) and copied the SuperSU zip file into the storage memory. Now as the tutorial suggested, I opened my phone and in the recovery mode, I flashed the SuperSU file. After i got the message saying 'Operation completed successfully". I wiped the Dalvik and the cache and then rebooted the system.
This where things go wrong. After rebooting, the HTC logo shows up along with the "powered by android" logo. Then the screen goes blank i.e. the screen is black but the backlit is on.
I've been trying to fix this by searching on threads, on YouTube, asking friends but I've gotten nowhere. So PLEASE any help would be appreciated.

hamza.ar said:
Hi all,
This is my first post here. Even though i follow some threads on this forum, I've never posted cause i never needed to. All my questions were generally answered in the threads.
However, I believe I've run into a unique problem.
Yesterday, I started rooting my phone using this tutorial: htconeroot.com/ htc-one-root/ how-to-root-htc-one-windowsmaclinux
And i got pretty far. In half an hour, I had successfully unlocked the bootloader, flashed the recovery program (TWRP) and copied the SuperSU zip file into the storage memory. Now as the tutorial suggested, I opened my phone and in the recovery mode, I flashed the SuperSU file. After i got the message saying 'Operation completed successfully". I wiped the Dalvik and the cache and then rebooted the system.
This where things go wrong. After rebooting, the HTC logo shows up along with the "powered by android" logo. Then the screen goes blank i.e. the screen is black but the backlit is on.
I've been trying to fix this by searching on threads, on YouTube, asking friends but I've gotten nowhere. So PLEASE any help would be appreciated.
Click to expand...
Click to collapse
post a link of the TWRP version you have used and the supersu.zip version.

alray said:
post a link of the TWRP version you have used and the supersu.zip version.
Click to expand...
Click to collapse
twrp: openrecovery-twrp-2.6.3.0-m7
Super SU: UPDATE-SuperSU-v2.46

hamza.ar said:
twrp: openrecovery-twrp-2.6.3.0-m7
Super SU: UPDATE-SuperSU-v2.46
Click to expand...
Click to collapse
TWRP 2.6.3.0 is really outdated. Flash 2.8.6.0 and try again using supersu 2.46

alray said:
TWRP 2.6.3.0 is really outdated. Flash 2.8.6.0 and try again using supersu 2.46
Click to expand...
Click to collapse
WOW i had almost given up and was gonna get a new phone. I just tried this AND IT WORKED!!!
Thanks a lot man. Sorry if this was kind of a noob question anyway

Keep booting into TWRP after Android 7.0

I had TWRP installed and enrolled in the beta program. I just downloaded the official 7.0 through the push notification and clicked, "Restart and Install." Now, my phone boots automatically into TWRP. I've turned it off, then back on and same thing. Any ideas how to get out of this?

Boot into bootloader from recovery and select start.

prestige777 said:
Boot into bootloader from recovery and select start.
Click to expand...
Click to collapse
Yeah but it still can't install the update,any way fix it?

Boot to bootloader and flash the stock recovery from factory image. Then boot into stock recovery and the update should start.

The same happened to me. Disappointing, since the previews all worked (for me) in TWRP.
I just downloaded the OTA and sideloaded it, flashed TWRP, rebooted into TWRP and installed SuperSU 2.78. Worked fine.
https://developers.google.com/android/nexus/ota#shamu

dahawthorne said:
The same happened to me. Disappointing, since the previews all worked (for me) in TWRP.
I just downloaded the OTA and sideloaded it, flashed TWRP, rebooted into TWRP and installed SuperSU 2.78. Worked fine.
https://developers.google.com/android/nexus/ota#shamu
Click to expand...
Click to collapse
May I ask which version of TWRP did you use?

twrp-3.0.2-0-shamu.img

you cant flash an official factory image in twrp..this is a known fact...

Is that comment aimed at me? Did you actually read my post? Can you point me at the relevant part where I get it wrong?
Feel free to apologise any time.

dahawthorne said:
Is that comment aimed at me? Did you actually read my post? Can you point me at the relevant part where I get it wrong?
Feel free to apologise any time.
Click to expand...
Click to collapse
You are side loaded ota then flash twrp . But in op he was flashed ota via twrp and now os corrupted and he is not able to boot into system. All ota can flashed via stock recovery , i think. He have to flash firmware now via fast boot. Am i correct . If anything wrong ,you can correct.
Everybody should be friends in XDA.

It seems that people don't read posts before writing. The OP clearly said that he had applied the OTA. I clearly said that this was exactly what I did with the same result. I also clearly explained what I did to fix it. The next comment should be from the OP saying what he's doing to recover. If he does what I did he'll be fine.

drmuruga said:
You are side loaded ota then flash twrp . But in op he was flashed ota via twrp and now os corrupted and he is not able to boot into system. All ota can flashed via stock recovery , i think. He have to flash firmware now via fast boot. Am i correct . If anything wrong ,you can correct.
Everybody should be friends in XDA.
Click to expand...
Click to collapse
He can reinstall stock recovery and side load from there
Either flash the stock recovery.img through twrp or
Flash stock recovery through fastboot or
Install factory image through fastboot
Edit: oops didn't read the entire thread

itsagood said:
I had TWRP installed and enrolled in the beta program. I just downloaded the official 7.0 through the push notification and clicked, "Restart and Install." Now, my phone boots automatically into TWRP. I've turned it off, then back on and same thing. Any ideas how to get out of this?
Click to expand...
Click to collapse
To avoid issues, I'd say make sure you're 100% stock, recovery and all before installing an official update. Like I said, just to be sure it won't fail.

I got the the OTA notification before work yesterday. All day at work I was itching to install it but with no PC I couldn't risk it. I was on the DP5 with TWRP, no root, and unlocked. I couldn't wait. I flashed the OTA with TWRP after I restored a backup of when I first installed DP5. TWRP throw a couple of errors but after about 10 minutes of hanging on the boot animation it finally booted. My phone was encrypted but other then that it was fine. I was gonna root it afterwards but I was on stock recovery after flashing the OTA so I couldn't do anything until I got home. Made a noforc-nonverify boot IMG throw on TWRP reformatted. Running great now.
Edit: My DP5 boot.img was also noforc-nonverify.
Sent from my Nexus 6

[Mate 10 Pro] Stuck in bootloop, need help with stock firmware

After unlocking the bootloader, I installed the latest versions of TWRP and Magisk. It worked after a few reboots, but after installing the Xposed Magisk module the phone got stuck in a boot loop.
I tried to use the Magisk uninstaller, didn't work, tried to use eRecovery and HiSuite recovery, and then I get an error how my phone is unsupported or how there was an issue getting package information for my device.
I tried to flash the SYSTEM.IMG of the same version thinking how it will let me factory reset my phone... and it didn't work. Tried using HWOTA (Which in the end fixed my problems)*, but then I realised it only works for Mate 10 Lite (or maybe I'm just dumb)
I got my phone softbricked and cought in a bootloop, and I don't know how to unbrick it. So I'm asking You guys for help because I really f***ed up, and Your help would be very much appreciated.
Model BLA-L29 (C432) - Europe
*Edit: Fixed by following this guide https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814

Boot to twrp and flash install the same exposed module (you can find it in MagiskManager folder) it should uninstall and get you out of bootloop. Hope it works!

Read You dingus
Nevermind it turns out it was error on My part (which I think You guys all expected), because it looks like I suck at reading REAL easy instructions.
So the problem was I didn't pay attention to one of the prompts of this tool/guide: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
After downloading all 3 stock firmware/update files, dropping them, and then renaming them in the HWOTA8_Mate10\repack folder so I could run the repack.bat that would patch them. I did that part just easy, but then I managed to screw up a even easier thing, which was running the ota.bat and following the instructions.
What went wrong was I didn't press ENTER after opening the recovery, so My device never got to do the updating/installing part that all these previous steps were leading up to.
Lesson learned: Read, and follow the steps, it really isn't that hard
SOLVED

Please help -- got same bootloop issue.
I already had Magisc root installed, then decided to try "System-less Xposed Framework":
https://magiskroot.net/install-system-less-xposed-framework-oreo-8/
-- after I flashed (using TWRP) xposed-sdk26-topjohnwu.zip -- phone went into bootloop.

_hunter said:
Please help -- got same bootloop issue.
I already had Magisc root installed, then decided to try "System-less Xposed Framework":
https://magiskroot.net/install-system-less-xposed-framework-oreo-8/
-- after I flashed (using TWRP) xposed-sdk26-topjohnwu.zip -- phone went into bootloop.
Click to expand...
Click to collapse
Xposed oreo beta 4? Or an another version?
Sent from my HUAWEI BKL-L09 using XDA Labs

Trouble rooting my g6

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

Moto Z3 Play stuck at TWRP logo screen

Hello everyone,
I tried to flash TWRP on my Z3 play today and got stuck on the TWRP logo screen. Since I am a noob, i will try to give a detailed describtion of what i have done so far.
I started by going into debuggingn mode and unlocking to bootloader following the guide unlock-bootloader-moto-z3-play from getdroidtips
This worked as far as i can tell. Today I wanted to get TWRP running as this seemed like the next step to take. Again i followed the getdroidtips guide twrp-recovery-moto-z3-play/ which linkes to flash-twrp-recovery-android. Here I didnt install Odin and Android Kies, because these seem to be Samsung-specific? I followed all other steps and arrived at the command line "fastboot flash recovery recovery.img" which didnt work, but gave the error message "invalid partition name recovery". After googling a bit I found that "fastboot boot recovery.img" should boot TWRP and that I could procced from there. At first it looked as if TWRP would actually boot, but then it got stuck in the logo screen and is sitting at that for an hour now.
Did I brick my phone? And can I fix this somehow?
Any help would be greatly appreciated.
Thank you.

Dunsinan said:
Hello everyone,
I tried to flash TWRP on my Z3 play today and got stuck on the TWRP logo screen. Since I am a noob, i will try to give a detailed describtion of what i have done so far.
I started by going into debuggingn mode and unlocking to bootloader following the guide unlock-bootloader-moto-z3-play from getdroidtips
This worked as far as i can tell. Today I wanted to get TWRP running as this seemed like the next step to take. Again i followed the getdroidtips guide twrp-recovery-moto-z3-play/ which linkes to flash-twrp-recovery-android. Here I didnt install Odin and Android Kies, because these seem to be Samsung-specific? I followed all other steps and arrived at the command line "fastboot flash recovery recovery.img" which didnt work, but gave the error message "invalid partition name recovery". After googling a bit I found that "fastboot boot recovery.img" should boot TWRP and that I could procced from there. At first it looked as if TWRP would actually boot, but then it got stuck in the logo screen and is sitting at that for an hour now.
Did I brick my phone? And can I fix this somehow?
Any help would be greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Just like the Google search you used, there's a search here on XDA. Your problem has been addressed many times.
Instead of creating a new Topic/thread, ideally you could've and should've first searched the TWRP Z3 thread. Then asked questions about TWRP in The TWRP thread.

kewlzter said:
Just like the Google search you used, there's a search here on XDA. Your problem has been addressed many times.
Instead of creating a new Topic/thread, ideally you could've and should've first searched the TWRP Z3 thread. Then asked questions about TWRP in The TWRP thread.
Click to expand...
Click to collapse
Oh, I am sorry if this is a duplicate. I searched the forum before and didnt find my problem. I will look again.
Thanks for the quick response

Dunsinan said:
Oh, I am sorry if this is a duplicate. I searched the forum before and didnt find my problem. I will look again.
Thanks for the quick response
Click to expand...
Click to collapse
Did you find the solution?
hint: 3.3.1.0

Okay, I am an idiot.
Thanks to your hint I figured out that I had to use TWRP 3.3.1.0 to not get stuck. This worked, but I accidentaly flashed TWRP to boot instead of recovery.
When i tried to flash to recovery i got: "Invalid partition name recovery"
What can I do now?

Dunsinan said:
Okay, I am an idiot.
Thanks to your hint I figured out that I had to use TWRP 3.3.1.0 to not get stuck. This worked, but I accidentaly flashed TWRP to boot instead of recovery.
When i tried to flash to recovery i got: "Invalid partition name recovery"
What can I do now?
Click to expand...
Click to collapse
That's not an accident, that's a mistake!
I'm sure there are a number of things you can do. But messing with Boot partition is the best way to brick your phone.
have you tried to use LMSA to start over.
or
Boot TWRP, use one of the backups you made. Restoring boot?
or
ADB flash boot, from firmware sideload folder.

I used LMSA to go back to stock android. Now it boots normal again.
Okay, so how do I get TWRP to work? I am hestitant to try on my own again.
Last time i tried to flash twrp to recovery i got a "invalid partition name recovery" error message.

Dunsinan said:
I used LMSA to go back to stock android. Now it boots normal again.
Okay, so how do I get TWRP to work? I am hestitant to try on my own again.
Last time i tried to flash twrp to recovery i got a "invalid partition name recovery" error message.
Click to expand...
Click to collapse
Do you just try things without any research? have you not considered reading the very short thread associated with TWRP and this device?
That's the correct place to both look for your answers, and ask for clarification.