Develop Bugs

Can't find my way through the many guides, could use a lil'bit of help

Hey lads!
I am trying to root my HTC One M8, so I can get a finer options for sounds (and other advantages, aswell). I found this post https://forum.xda-developers.com/htc-one-m8/help/how-to-root-htc-one-m8-android-6-0-t3420748 about rooting an M8 with android 6.0. I'm writing this post, because I don't want to screw it up, so it seemed better to ask for help, before I do something stupid and brick my phone. I tried searching the forum, but after opening like 10 tabs, I lost my way. (I am using Windows 10, legit)
So, this is what I did:
1) Downloaded the Android Studio.
2) Via the studio, I downloaded the 6.0 platform.
3) And here is my first block: tried to install ADB, via Universal Naked Driver: I downloaded the ZIP, unpacked it, and while my phone was connected, tried to update its driver via the Device Manager. I got a message that it's up to date, and even tho I picked the 'I have disk' option, it wouldn't do anything. Now, I downloaded MiniADB v_1031, and when I ran the cmd from here, I could see my device with adb devicelist. I also installed HTC Sync, and used the driver installer from adbdriver.com, and it showed that I have the needed driver.
4) From the folder where I have unpacked miniadb, was able to run adb devicelist, and adb bootloader reboot aswell. But from that point, even tho I enabled developer options in my phone, and USB debugging aswell, my PC can't see the phone, only if I reboot to normal mode. When I am in fastboot USB, adb devices just says 'list of devices' and a blank line under it.
5) Tried to unlock the bootloader, and I got my identifier token. I am good to go then, I have every driver what I need for continuing from here?
5)b) Edit: Seems like I managed to unlock the bootloader.
---------
So if I understand it well:
From now on:
---------
6) Download the EU version of TWRP 3.0 from here (I am from the EU)
7) Use the cmd 'fastboot flash recovery twrp.img'
8) The site mention a key-combo to prevent the phone to go back to basic recovery, do I need this?
9) Do a backup via TWRP (is it going to be a simple option in the recovery? How big SD card do I need? Atm, I have 12 Gb one, gonna buy a 128 one in like 1-2 month)
10) Copy the SU.zip to my SD card and use a flash option in the recovery?
Sorry for any dumb question, I'm kinda scared bricking my phone, but at the same time, I would like to get the advantages of rooting.
So anyway, did I miss out on any step, screwed up anywhere, or smth like this?
Any help is much appreciated!

My comments to your steps/questions:
4 and 5) adb and fastboot are two different, but related interfaces. Don't feel bad, it's a common mistake to mix up the two (adb and fastboot). You'll really only need fastboot for rooting the phone. The step to "adb reboot bootloader" in the TWRP install instructions can alternately be done without that command, using the button combo to get to bootloader. But I think you must have figured that out by now, if you managed to unlock the bootloader.
In summary,
adb: needs USB debugging on in phone settings, only works when phone is booted in OS or alternately when booted into TWRP (last part obviously doesn't help, if you haven't installed TWRP yet).
fastboot: only works in bootloader-fastboot mode (will not work in OS or TWRP), does not need USB debugging on in phone settings.
6) The options are for download mirror locations (US vs. Europe - literally just where the download's server location is located), and do not specifically refer to different TWRP versions. The same TWRP version works for both US and Euro M8 models. What you downloaded is fine, so my comment is just FYI.
8) No, you shouldn't need this. I believe this comment refers to newer devices, and not specifically to the M8. I literally think the TWRP team has copy/pasted this statement to instructions for every device on their website, whether it applies or not.
9) Yes, this is a clear option once booted into TWRP recovery. Literally, on the TWRP main screen, you will see a big button labeled BACKUP. Tap it, and select system (ROM or OS) and boot.img, and also backup data if you like. The backup of system and boot.img will take around 2 GB. The backup of your user data might be much more, depending on your apps, etc. Although, if you just unlocked the bootloader, the phone should have been wiped, so you may not have much (if any) user data to backup.
10) While SuperSU 2.76 (mentioned in the thread you linked) should work fine, I would suggest using the latest stable version 2.79 from here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Just put it on the phone, boot into TWRP, select INSTALL, select SuperSU 2.79.
---------- Post added at 12:42 PM ---------- Previous post was at 12:37 PM ----------
Rivyan said:
Sorry for any dumb question, I'm kinda scared bricking my phone, but at the same time, I would like to get the advantages of rooting.
Click to expand...
Click to collapse
Don't worry, you won't brick the phone (permanent damage) by unlocking the bootloader, custom recovery, root, etc.
Anything you do is recoverable/reversible, even if something goes wrong (especially if you make a TWRP backup of your current stock ROM before rooting).

[STOCK ROM][PERRY][MetroPCS.XT1765]A8M'S XT1765 STOCK ROM April 14th, 2018

The original thread was closed...sorry guys I've been busy. Link to the rom has been updated!!!!
Eureka! After two days of trials, tribulations, and extreme reading, I have been successfully able to create a flashable, working Stock Rom for the MetroPCS XT1765. And yes, I figured out how to get root working on it too (albeit experimental)!!!! This has been something visibly lacking in our E4 community, and since its the phone I have, I felt it was a necessity since once you unlock the bootloader or ever took an update its impossible to get the original .xml back on the phone.
Disclaimers Before You Begin:
This tutorial is for people like me that wanted a flashable stock rom for the Moto E4 XT1765 Metro PCS Qualcomm/Perry Variant running on stock Nougat 7.1.1 Please follow the guide carefully. Cutting corners and skipping steps could have MAJOR CONSEQUENCES.
For everybody with other Perry variants, I don't know if this rom will work or not, so if you're feeling frisky try at your own risk as this has only been tested on the XT1765.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
Introduction
The A8M'S METROPCS XT1765-PERRY STOCKROM PROJECT was created from the Motorola PERRY_METROPCS_C_7.1.1_NCQ26.69-46_cid22_subsidy-MPCS_regulatory-DEFAULT_CFC.xml firmware, straight from their official site. This was not made from a backup, but from extracting the firmware files itself, and compiling via Assayyad kitchen. Nothing was removed from the firmware on this build, but you will have to flash Open Gapps and add it during installation, as well as No-Verity. Outside of that, it's a virgin rom slightly removed.
Preparation
1. READ EVERYTHING IN THIS GUIDE BEFORE STARTING! This variant can tear you a new one, so get a handle of what you're working with on this.
2. This is only for people that have bootloader unlocked their phones, and can successfully use TWRP on their device. I highly recommend @squid2's TWRP (which is in my download files list on this guide). I can also only give support for those using his TWRP, as that is the one I used flashing this rom.
3. Backup all your data if you want - the phone has to be wiped clean for this to work right as a dirty flash won't cut the mustard. It's not hard exporting your contact list, or using SMS Backup Restore for your call log and text msgs to your SD card. This helps putting back your phone exactly how you had it before this. Takes a second (but be sure to uninstall SMSBackupRestore when you've successfully restored your stuff unless you like it).
4. Download all the files from the list below,and put all of them but the boot.img on your SD card. That is the Stock Rom, the noverity.zip, the magisk.zip, superuser.zip, rootchecker, and opengapps.zip. Make sure the file sizes are correctly matching and that there are no errors in your transferring.
***NOTES SO YOU DON'T FREAK OUT***
Once you flash the rom its going to take 3-5 minutes to boot the first time. It's normal. If you see the "Hello Moto" constantly repeat, that's a bootloop, and you need to wipe and reflash again (even though this did not happen to me). Also, if you see a Bad Key black screen and it doesn't boot, you've made a mistake by not flashing no-verity after flashing the rom. It isn't a brick, you just need to go to recovery and flash it again.
Files Needed:
Download and add these to your SD card. These are the exact files I used on my phone. ***NOTE*** My file share service says they will delete these June 14th, so if you know of a fast share site that's free and can handle big files, please let me know.
Mod Edit: If / When you update these links, PM @Az Biker to reopen this thread.
1. My Flashable Stock Rom: https://drive.google.com/open?id=1ScvA3zO6qHY4mhMtaM4aDajx9ZH6CpYj
2. OpenGapps Nano: https://drive.google.com/open?id=1x3Uz_sia1N3OYPGrdEwJ7TBeSmyiDlEZ
3. No Verity Opt Encrypt.zip: https://drive.google.com/open?id=1FqcpWgYJ16HYjIzZgIlHEZOlKJPjaorM
4.Superuser-r259.zip: https://drive.google.com/open?id=1iFswMvZ2vycIrQ4tK7nTWZAG7zktrPH2
5. Magisk v14.0.zip: https://drive.google.com/open?id=1wyV5EJe2wtSIadFNZsbJQOfGrsNQzG4p
6. Root Checker (Playstore)
7. Boot.Img file in case you make it to the bonus round: https://www45.zippyshare.com/v/Uhru1YeL/file.html
Additional Software: you may need Minimal ADB and Fastboot in case you don't have TWRP installed already for the rooting part or if you run into problems trying to gain root; you'll have to search XDA for that one .
Part I - Installation:
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. As soon as you flash the stock you'll see the phone trying to push an update, as it auto turns on your data if you choose not to set up wifi (which you shouldn't do just yet).
3. Boot into Recovery TWRP. (If TWRP isn't installed, see 3A and skip this part.) If TWRP is installed you can power the device off and then hold the Volume Down plus the Power key to get into fastboot, and with the volume rocker select recovery and then hit the power button to boot. If you have unlocked the bootloader you will see N/A black screen in this process.
3A. If you do not have TWRP installed, With the phone on, run the command in Minimal ADB and Fastboot "adb devices" without the quotations. You should see your phone ID and device. Next, turn the phone completely OFF. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY). Connect device to PC via USB cable. Then open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your recovery image file is in the Minimal ADB directory or it won't work; the type "fastboot boot thenameofyourrecoveryfile.img". This should boot you to the TWRP.
4. Once booted into TWRP, tap Wipe, then Advanced Wipe; check Dalvik/ART Cache, System, Data, Cache ONLY, then swipe to wipe. Just to be on the paranoid safe side, click back (triangle pointing left) to the main menu, go back to Wipe, Tap Format Data, Type yes and wipe. Click back to main menu after - do NOT reboot.
5. Click Install; install A8M'S-METROPCS-XT1765-PERRY-STOCKROM-PROJECT-04142018.zip. Afterwards, go back to main menu.
6. Click Mount; make sure System, Data, Cache, and Micro SD Card are checked. Disable MTP. Click back to main menu after.
7. Click Install; install open_gapps-arm-7.1-nano-20180331.zip. Note: This takes 3-5 minutes. You will see a warning that StockRom Gapps is installed. That's okay - ignore it, its necessary. Click back to main menu after.
8. Click Install; install no-verity-opt-encrypt.zip. Click back to main menu after.
If you don't want root, hit Reboot, then System. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed. Congratulations, welcome to your brand spanky new stock rom flashed phone.
If you do want root don't reboot, keep reading the next section.
Part II - Rooting:
Okay, this section might be challenging, but hopefully this will ease your nerves as you walk through the ever so daunting task of rooting. It has some of the same challenges that rooting the .xml had (refer to my "The Complete Noob Guide to Rooting MetroPCS XT1765 Qualcomm Variant" guide for such challenges). This might feel totally redundant, and to a lesser degree it is, but it will pay off in the end. And remember, if at first you don't succeed, wipe clean and flash again!
9. In TWRP, click Install; install Magisk-v14.0.zip FIRST - very important. Do not install supersuser first. Afterwards, click back to the main menu.
10. Click Install; install superuser-r259.zip. Afterwards, click Reboot. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed.
4. Install Root Checker (free on Google Play). You can access your file without a file manager by hitting Downloads, selecting the three lines on the top left, and selecting SD Card from the pulldown menu. You should have root. Also check the Magisk Manager, it should confirm its installation with a green checkmark.
5. Disable Updates. This thing will race you to that. On initial launch, you should not have the wifi connected. As soon as you put your Sim card back in, IMMEDIATELY cut off your data until you disable updates.
Bonus Round - In Case Of Error -1 Issues:
Hopefully, the first two parts got you straight, and you're playing on your stock rom now. However, this variant is challenging, and getting root could be a pain in the android ass. If you installed either superuser.zip or magisk.zip and got an Error -1 for either or both, this section is for you.
Unfortunately, the boot.img getting corrupted probably is the main culprit. Don't freak, it was a problem with the original root method on this variant straight out the box. Also, if you have been flashing/re-flashing a lot, sometimes it just makes it funky. But its a fix with a little patience.
1. Turn your phone on, and let it boot.
2. Go into your phone settings, and activate developer options (you know, hitting the build number 7x).
3. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below). Very Important. Also uncheck "Verify Apps Over USB", but only if you having probs with fastboot in ADB. You can recheck it later.
4. Make sure you've enabled Allow installation of apps from Unknown Sources (its in the Security section of Settings).
5. Turn your phone completely off.
6. Plug your phone via USB cable into the computer.
7. Press Volume Down and Power to boot into fastboot mode.
8. Open up Minimal ADB and Fastboot command prompt on the PC (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your boot image file is in the Minimal ADB directory (same place you see recovery.img that boots/installs TWRP) or it won't work. Download it from the files list above.
9. In Minimal ADB command prompt type "fastboot erase boot. " It might say permission denied, and that's okay. Keep going.
10. In Minimal ADB command prompt type "fastboot flash boot boot.img" That should restore your original boot image to stock and correct any error 1 problems. And no, you don't have to reflash the stock rom after this either.
11. Reboot into recovery - make sure you select READ ONLY when it launches.
12. 6. Click Mount; make sure System, Data, Cache, and Micro SD Card are checked. Disable MTP. Click back to main menu after.
13. Click Install; install Magisk-v14.0.zip FIRST - very important. Afterwards, click back to the main menu. It should be successful.
14. Click Install; install superuser-r259.zip. Afterwards, click Reboot. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed.
15. Install Root Checker (free on Google Play). You can access your file without a file manager by hitting Downloads, selecting the three lines on the top left, and selecting SD Card from the pulldown menu. You should have root. Also check the Magisk Manager, it should confirm its installation with a green checkmark.
If you're still having problems after flashing the boot.img, start all the way over from the beginning wiping everything clean. That should correct the problem and let you install without trouble or needing to flash the boot.img again.
Bonus Round - In Case Of No Root After Root Issues:
As soon as the little bugger tried to force the update via my data when I stuck my Sim Card in, it messed with my root, even catching and cutting it off as quick as I could and not doing a full update. When I rebooted, I lost root. This has happened off and on every other flash - so your root may stick or it may not. If it doesn't, either you can 1. wait for a better method, 2. reflash, 3. live without it for now. This is still kind of experimental for me, as I had to wipe and reset to get root back. Still trying to figure out a more perm way for this like on the .xml.
Enjoy Everyone - I'm learning, taking it one android day at a time but I'll help when I can. It's an awesome day to be a nerd!
Sincere Thanks:
The devs that created a method of root for various variant E4's that sent me on this journey, I love you guys!
The devs behind Magisk, Superuser, and No-Verity!
@squid2 for the TWRP recovery that helped A BUNCH!
@ASSAYYED for the beautiful kitchen that forced me to keep learning.
@Al936 for the beautiful tutorial that helped me figure out how to extract the files needed in the journey.
@MotoJunkie01 for giving me the inspiration to try it on my own.
@madbat99 for the small, but powerful words of encouragement.
And to the community at large that let me ask questions to the point of getting on their nerves. Thank you!!!

[REPOST][ROM][PERRY][MetroPCS.XT1765][STOCK] A8M'S XT1765 STOCK ROM April 14th, 2018
Reserved.

Good work. When you say nothing was removed, does that mean the six Metro apps are still included? I've been looking for the stock Motorola ROM for the unlocked variant of this phone. Thanks.

ilanor said:
Good work. When you say nothing was removed, does that mean the six Metro apps are still included? I've been looking for the stock Motorola ROM for the unlocked variant of this phone. Thanks.
Click to expand...
Click to collapse
Everything is stock. Just as it was on a complete fresh out the box setup. You will find all the metropcs apps there.

How do I put the boot image into the same directory as adb and fastboot ? I don't really understand stand what that means.

Moto_E4_xt1765_metroPcs said:
How do I put the boot image into the same directory as adb and fastboot ? I don't really understand stand what that means.
Click to expand...
Click to collapse
you install ADB and fastboot on your computer then open the folder that contains those. Put the boot image in that folder
Pretty sure this guy that is extremely outdated though

this flashed fine and magisk and superuser flashed fine booted actually a little faster than normal. I don ' know how but it say no service though and it throws an error "error occured could not search" or something similar . how can i get my radios back

My phone has no recovery mode and TWRP.

First I apologize for my English, I do not speak English, and I used google translate to translate my text.
I need your help. Please, anyone who understands TWRP and Recovery on Xiaomi phones, help me.
I'll leave it to you to make it easier for you to understand, because the text is long.
TL; DR my cell phone is neither with TWRP nor with Recovery of xiaomi (I think it is not, because I can not get into any of the 2 at all). Everything I did I left step by step in the text.
I wanted to install the ROM pixel, do root and install GCam on my Xiaomi Redmi Note 5 Pro.
The first step was to unlock the bootloader, and yes, I was able to unlock everything quietly, (I waited 180 hours and then I was saying that I did not have my cell phone long enough to unlock, so I downloaded another version of miunlock and managed to unlock).
The second step was to install TWRP, which started to complicate.
Through a video on youtube of a channel that always posts videos to this phone, I followed the instructions for installing TWRP, I did everything according to the video (in this video he did not ask to install anything in Windows, just use cmd) and the commands he typed were as follows:
fastboot flash antirbpass dummy.img,
fastboot flash recovery twrp-3.2.3-1-whyred.img
From there he had to close the cmd and turn off the cell phone (remembering that the cell phone was already in fastboot mode) and then turn on the cell holding power + volume UP to enter the TWRP, however, did not enter the TWRP, entered the recovery mode standard of xiaomi.
So I left for another video. This time, the video was gringo, in this video, the guy asked to install an Adb on the PC, installed correctly and entered the CMD as the video. The commands that the guy from the video passed were this:
fastboot devices
fastboot boot twrp (twrp from another version)
This time the device entered TWRP, but to my surprise, TWRP was asking for a password (which I had no idea what it was) so I went after another version of twrp.
The alternative version for not asking for a password in TWRP that I used is 3.2.3.0, I used it according to the tips of the second video (the same one that I got to TWRP for the first time), and finally I joined the TWRP and did not asked for no password, end of the second part.
The third step was to install the ROM pixel and the magisk, and that's where it started to disgrace everything, I followed the steps according to another video for ROM installation.
In the video, the guy had to enter WIPE, advanced and check some options that did not include internal memory, I did everything right as in the video. Then he had to go to install and select the ROM, when the installation of my ROM started, it already presented an error, the despair hit and I did not know what to do (since I had no more operating system because I had reset the cell phone ) and by impulse, I decided to download the last version of MIUI 10 Stable (I was using the Beta version of MIUI 10), but I did not look right because I was VERY DESPERATE and I ended up downloading ROM Recovery, not ROM fastboot (I think influence on something, I am layman in that, I do not know), I was able to install the MIUI 10 Stable ROM, and soon after I installed Magisk to do the root, in that he had to restart the device.
After rebooting, I made the initial settings, and according to the video, I would need to turn off the phone to enter the TWRP mode to install the GCAM, but my cell phone HAS NO MORE TWRP, and worse, it does not come in the standard Recovery mode of the xiaomi, it's just written MI (that normal boot screen when you connect the Xiaomi device) and I have to restart it by holding down the power button.
I'm using it normally, it's root. But I can not get into the TWRP nor the normal Recovery of the ceular, that is, I can not even install GCam.
That's where my doubt comes in. Can I install TWRP yet? Remembering that the steps I did for the installation is on the topic so I do not know if I can do it again.
And since I'm without TWRP and without Recovery, I will not be able to update my phone anymore? I'm getting into fastboot and system mode at least.

spoktasy said:
First I apologize for my English, I do not speak English, and I used google translate to translate my text.
I need your help. Please, anyone who understands TWRP and Recovery on Xiaomi phones, help me.
I'll leave it to you to make it easier for you to understand, because the text is long.
TL; DR my cell phone is neither with TWRP nor with Recovery of xiaomi (I think it is not, because I can not get into any of the 2 at all). Everything I did I left step by step in the text.
I wanted to install the ROM pixel, do root and install GCam on my Xiaomi Redmi Note 5 Pro.
The first step was to unlock the bootloader, and yes, I was able to unlock everything quietly, (I waited 180 hours and then I was saying that I did not have my cell phone long enough to unlock, so I downloaded another version of miunlock and managed to unlock).
The second step was to install TWRP, which started to complicate.
Through a video on youtube of a channel that always posts videos to this phone, I followed the instructions for installing TWRP, I did everything according to the video (in this video he did not ask to install anything in Windows, just use cmd) and the commands he typed were as follows:
fastboot flash antirbpass dummy.img,
fastboot flash recovery twrp-3.2.3-1-whyred.img
From there he had to close the cmd and turn off the cell phone (remembering that the cell phone was already in fastboot mode) and then turn on the cell holding power + volume UP to enter the TWRP, however, did not enter the TWRP, entered the recovery mode standard of xiaomi.
So I left for another video. This time, the video was gringo, in this video, the guy asked to install an Adb on the PC, installed correctly and entered the CMD as the video. The commands that the guy from the video passed were this:
fastboot devices
fastboot boot twrp (twrp from another version)
This time the device entered TWRP, but to my surprise, TWRP was asking for a password (which I had no idea what it was) so I went after another version of twrp.
The alternative version for not asking for a password in TWRP that I used is 3.2.3.0, I used it according to the tips of the second video (the same one that I got to TWRP for the first time), and finally I joined the TWRP and did not asked for no password, end of the second part.
The third step was to install the ROM pixel and the magisk, and that's where it started to disgrace everything, I followed the steps according to another video for ROM installation.
In the video, the guy had to enter WIPE, advanced and check some options that did not include internal memory, I did everything right as in the video. Then he had to go to install and select the ROM, when the installation of my ROM started, it already presented an error, the despair hit and I did not know what to do (since I had no more operating system because I had reset the cell phone ) and by impulse, I decided to download the last version of MIUI 10 Stable (I was using the Beta version of MIUI 10), but I did not look right because I was VERY DESPERATE and I ended up downloading ROM Recovery, not ROM fastboot (I think influence on something, I am layman in that, I do not know), I was able to install the MIUI 10 Stable ROM, and soon after I installed Magisk to do the root, in that he had to restart the device.
After rebooting, I made the initial settings, and according to the video, I would need to turn off the phone to enter the TWRP mode to install the GCAM, but my cell phone HAS NO MORE TWRP, and worse, it does not come in the standard Recovery mode of the xiaomi, it's just written MI (that normal boot screen when you connect the Xiaomi device) and I have to restart it by holding down the power button.
I'm using it normally, it's root. But I can not get into the TWRP nor the normal Recovery of the ceular, that is, I can not even install GCam.
That's where my doubt comes in. Can I install TWRP yet? Remembering that the steps I did for the installation is on the topic so I do not know if I can do it again.
And since I'm without TWRP and without Recovery, I will not be able to update my phone anymore? I'm getting into fastboot and system mode at least.
Click to expand...
Click to collapse
id say start from scratch.. upto you to reset to official miui with fastboot rom and mi flash (note if you do check clean all only or ill relock bootloader if clean and lock is selected.. no need to wait again but you must unlock it again)
follow this guide.
https://forum.xda-developers.com/re...ne-xiaomi-redmi-note-5-whyred-unlock-t3778049
just skip steps you already did like adb if already installed.... also install drivers.
for twrp use this 1 click also has miflash
https://drive.google.com/open?id=1XLncxs4UDcSxiefQomwT4yZpWthwfAES
i recommend to use orangefox recovery. when you boot into twrp flash orangefox zip thats it.

thanks for answering. I was able to solve the TWRP part using another version of it. Now I'd like to know if it's possible for me to access TWRP directly from my cell phone, without the need for the computer.

spoktasy said:
thanks for answering. I was able to solve the TWRP part using another version of it. Now I'd like to know if it's possible for me to access TWRP directly from my cell phone, without the need for the computer.
Click to expand...
Click to collapse
use quick reboot app from playstore. it boots into recovery or fastboot .

spoktasy said:
thanks for answering. I was able to solve the TWRP part using another version of it. Now I'd like to know if it's possible for me to access TWRP directly from my cell phone, without the need for the computer.
Click to expand...
Click to collapse
settings > developer options > enable extended power menu
this should work

Lenovo P2 (P2a42) stuck mostly on blue logo screen

Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.

NickSergeant said:
Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.
Click to expand...
Click to collapse
YOU CAN CHECK IN MY SIGNATURE FOR ALL BASIC TERMS USED IN FLASHING.
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
If you have TWRP installed , you can update TWRP and then flash a custom rom. You can hold both volume up and down and power key to boot into TWRP when phone is switched off.
Remember new custom roms need newer version of TWRP.
What you'll need to do is download a custom rom like say Havoc OS Android 10 (just search it in the forum), you will need to upgrade your TWRP.
Once this is done, you will download Havoc OS Rom and put it in your phone or sd card
You just do a factory reset and then format only system . Don't format other partitions in TWRP.
Install that room and then you will also need to install gapps. (Google open gapps , chose Android 10 version and architect as 64bit and choose nano or pico gapps)
So in your sd card, you must have rom and gapps.
Once you install rom first and then gapps, restart. If it comes with an error, it means your TWRP needs update.
To update you will choose to download TWRP (zip format will install directly while IMG format can be flashed as well by choosing install IMG while you select install in your TWRP.
Restore is only available if you already made a backup with your TWRP .
I will suggest to make a full backup (except system and data ) in TWRP before you do the above.
I will also suggest you to Google if you are not sure. Make sure to follow instructions only from XDA as they are most reliable than other sources.
Watching YouTube videos may help you as well
In short:
Update TWRP
Download Havoc Rom and Gapps pico
Put them in your sd card
Install them in this order rom and then gapps.
Restart.
If you still feel you need help, please quote me for an answer
All the best .

Hnk1 said:
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
Click to expand...
Click to collapse
Thank you for this advice -- it worked! Finally the phone gets past the logon and is operating.
Now I have a further problem and please let me know if you think this should be a new thread for this.
I cannot sign in to Google because of anti-theft feature -- instead I get this.
“This device was reset. To continue, sign in with a Google Account that was previously synced on this device”
I see a few solutions online but not exactly for Lenovo. What would you recommend?

I'm on the same boat as Nick. Do we have to wait 15 days to unlock the bootloader? Just coz it'll be hard to be 15 days without a phone and everything wiped out. I wanna try Syberia 2.9 as the last LineageOS is not ready yet. Thank you very much.

LineageOS 17.1 device shuts down after some time from booting on SM-T295

note: everything that I've flashed was from my SD card; I had the files on /sdcard1/Download
note 2: since my device's bootloader is unlocked, I have to press the power button after turning on the device, so that the "bootloader unlocked" warning goes away
I've managed to install TWRP (I followed this guide, "How to Install twrp Recovery on Samsung SM-T295" part, I modified a bit the steps, i had to go into download mode again after flashing TWRP_3.4.0.1+vbmeta_T295.tar and flash aboot_vk_T295XXS3ATB4.tar) and then LineageOS 17.1 (from a GSI I found on this post, to flash I followed this guide) on a Samsung Galaxy Tab A 8.0 (2019) (SM-T295). Then I rooted it after installing LOS (from this guide, "How to Root Samsung SM-T295" part, I didn't make a backup due to errors, and multidisabler-samsung-2.6.zip failed to flash). Magisk had to update after, so I did that. Until then, no errors, until I downloaded BitGApps (I followed this guide, I downloaded the ARM64 version for Android 10 directly from my device). My TWRP had some problems flashing, because I couldn't access the Internal Storage from there (for some reason, /sdcard directory shows only folders on Install (and files, in the file manager) with random numbers and letters names like MAKVjaaw24Ajg35waD (not an actual folder or file, just an example), and I couldn't find the files to flash, which is why i had to flash everything from my SD card), so I rebooted to system from TWRP, and tried to copy the BitGApps file to my SD card so I could flash. I think I was about to copy the file (or I had just selected the copy option but hadn't found the directory to copy the file to, which was /sdcard1/Download), and suddenly, my device just powered off. I thought "oh it's just a bug, I'll power it on again and it'll be fine", but something strange happened when I powered it on; Now, every time I turn it on with the power button, I have to hold it less time for it to boot for some reason. That's weird. When android started and I could use the device, I tried to copy BitGApps to my SD card again, but my tablet powered off again and the same happens every time now. When i boot into safe mode, this doesn't happen, so I suspect it happens because of an app I installed, and now that I think about it while writing, I think it's probably Magisk Manager (I made it so that Magisk allows any superuser request, which is why I think Magisk has to do). I have the apps Phone Guardian (I always install it because I love it), Magisk Manager and the Official TWRP app.
Also something weird I noticed; Ever since the first time it bugged for me, whenever I boot into TWRP and then power off from the reboot menu, next boot is TWRP even if I don't do the button combo to boot into recovery (for my SM-T295 it's hold power + hold volume up at the same time when the device is off, then when it powers on, release all the keys and press power when promted to make the "bootloader unlocked" warning go away if necessary).
Does anyone have any ideas on why this is happening? Am I right on my guess that Magisk is faulty? Do I need to uninstall it and unroot if that's the case? Thank you all in advance.

Update: it was Magisk, but not the option I said, maybe a module?

Update: I got it now.
Jaqueek said:
Update: it was Magisk, but not the option I said, maybe a module?
Click to expand...
Click to collapse
No, I was wrong. I figured it out. It bugs after I update to Magisk 21.3 from 20.4. The manager is not a problem. Also,...
Jaqueek said:
Now, every time I turn it on with the power button, I have to hold it less time for it to boot for some reason. That's weird.
Click to expand...
Click to collapse
... It is weird indeed, but not important, it's not annoying and useful if I'm in a hurry or smth so I can't complain. Also, after I uninstalled Magisk that didn't dissapear. Anyways, I just don't care about that anymore.
Also, I managed to flash GApps pico, it was a little hard.
One last thing, when I said that my TWRP saw gibberish when trying to access /sdcard1,
it appeared to not be only TWRP. Stock File Manager saw those weird names too, after I wiped the Internal Storage partition. I just fixed content in TWRP and wiped Int. Storage again, it's fine now. I still haven't checked TWRP though. (just checked, yeah it looks the same still but any file manager is fine)
So, what is causing my device to turn off when I update to Magisk 21.3?
Edit: It also happens when I uninstall the original and install the new one.

How did you get the Treble GSI working on this device?
Mine just bootloops on the bootloader, even after doing your steps...