My phone has no recovery mode and TWRP. - Xiaomi Redmi Note 5 Pro Questions & Answers

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

Related

[Q] Wifi Model, Stuck on Google Boot Up Screen, No OS Installed says TWRP, help?

Hey all,
So, my smart self was attempting to flash Marshmallow 6.0 from 4.3 (rooted)...I did the same thing that was here on this THREAD and now my tab can only go into TWRP, but there's no OS installed because I wiped (and didn't make a darn backup....), but there are a few differences from the thread I referred to:
- I can get into my Bootloader
- I can get into TWRP
- I have the current TWRP 2.8.7
- I've tried the Nexus Toolkit from HERE, my device serial is recognized, but it states that I'm offline
- Because I'm offline, I can't push any files to my device through the tool
- When I'm in TWRP, my computer will recognize my tablet and I can actually get into folders and what not, but I can't copy/paste any files to flash within TWRP and I get an error
- Anytime I power down or reboot within TWRP, it tells me that I have No OS installed
- I can't use ADB (as far as I know) because my device shows that it's offline
Is there any hope that I can recover even back to 4.3?
Any guidance would really be appreciated. I have to step away because I'm frustrated and am angry at myself that I didn't make a nandroid.
Thanks in advance.
kevs888 said:
Hey all,
So, my smart self was attempting to flash Marshmallow 6.0 from 4.3 (rooted)...I did the same thing that was here on this THREAD and now my tab can only go into TWRP, but there's no OS installed because I wiped (and didn't make a darn backup....), but there are a few differences from the thread I referred to:
- I can get into my Bootloader
- I can get into TWRP
- I have the current TWRP 2.8.7
- I've tried the Nexus Toolkit from HERE, my device serial is recognized, but it states that I'm offline
- Because I'm offline, I can't push any files to my device through the tool
- When I'm in TWRP, my computer will recognize my tablet and I can actually get into folders and what not, but I can't copy/paste any files to flash within TWRP and I get an error
- Anytime I power down or reboot within TWRP, it tells me that I have No OS installed
- I can't use ADB (as far as I know) because my device shows that it's offline
Is there any hope that I can recover even back to 4.3?
Any guidance would really be appreciated. I have to step away because I'm frustrated and am angry at myself that I didn't make a nandroid.
Thanks in advance.
Click to expand...
Click to collapse
Are you using stock rom? Because if you are, I wouldn't even try. What with the widespread knowledge that stock might brick, some people insist on it. Otherwise, if you can get to the bootloader:
(1) Make sure it's unlocked (if you're not familiar, connect tab to PC, make sure fastboot works, then enter "fastboot oem unlocked" without the quotes then follow instructions on your tab);
(2) Flash bootloader 4.05 if you haven't already;
(3) Get a USB OTG thumb drive (you might need an OTG adapter for this); and download a Marshmallow-based custom rom in the Android Development section;
(4) Get into TWRP and mount USB OTG. You should see all the files on your thumb drive;
(5) Copy all data you care about to your PC;
(6) Wipe everything except USB OTG twice. Then go to Format and do it twice too. If yours is 32GB, it will take a while (30 Mins average depending on how much data);
(7) Flash rom, then Gapps.
You should be able to boot after that. Good luck.
(4)
graphdarnell said:
Are you using stock rom? Because if you are, I wouldn't even try. What with the widespread knowledge that stock might brick, some people insist on it. Otherwise, if you can get to the bootloader:
(1) Make sure it's unlocked (if you're not familiar, connect tab to PC, make sure fastboot works, then enter "fastboot oem unlocked" without the quotes then follow instructions on your tab);
(2) Flash bootloader 4.05 if you haven't already;
(3) Get a USB OTG thumb drive (you might need an OTG adapter for this); and download a Marshmallow-based custom rom in the Android Development section;
(4) Get into TWRP and mount USB OTG. You should see all the files on your thumb drive;
(5) Copy all data you care about to your PC;
(6) Wipe everything except USB OTG twice. Then go to Format and do it twice too. If yours is 32GB, it will take a while (30 Mins average depending on how much data);
(7) Flash rom, then Gapps.
You should be able to boot after that. Good luck.
(4)
Click to expand...
Click to collapse
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
kevs888 said:
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
Click to expand...
Click to collapse
It shouldn't make a difference what rom you flash now so long as you wipe and format everything inside TWRP. But you must make sure you have bootloader 4.05. 4.02 will not allow you to flash LL or MM successfully, and the system does not upgrade on its own no matter what rom you're flashing now.
Since you said you couldn't get TWRP to copy anything, I suggested that you use a thumb drive. Basically, if you turn the tab totally off, hold power + volume down for a few seconds, it should take you to the fastboot page (pic). Look to see what bootloader version you have there.
From here, you can basically flash anything. I recommended that you wipe and format first with TWRP because it happened to me a few times when for some reason, wiping alone still left some residual data that interfered with flashing newer roms.
Stay away from anything stock for the moment. God knows it has bricked more than a few devices. Download SkipsoftToolKit and flash from the fastboot page if you want an automated process. It has worked wonderfully in my experience. Ask if you have more questions. Have fun.
kevs888 said:
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
Click to expand...
Click to collapse
Fastboot page
graphdarnell said:
It shouldn't make a difference what rom you flash now so long as you wipe and format everything inside TWRP. But you must make sure you have bootloader 4.05. 4.02 will not allow you to flash LL or MM successfully, and the system does not upgrade on its own no matter what rom you're flashing now.
Since you said you couldn't get TWRP to copy anything, I suggested that you use a thumb drive. Basically, if you turn the tab totally off, hold power + volume down for a few seconds, it should take you to the fastboot page (pic). Look to see what bootloader version you have there.
From here, you can basically flash anything. I recommended that you wipe and format first with TWRP because it happened to me a few times when for some reason, wiping alone still left some residual data that interfered with flashing newer roms.
Stay away from anything stock for the moment. God knows it has bricked more than a few devices. Download SkipsoftToolKit and flash from the fastboot page if you want an automated process. It has worked wonderfully in my experience. Ask if you have more questions. Have fun.
Click to expand...
Click to collapse
This is really helpful...I think I'm almost there.
I'm on a super old Bootloader (see attachment) so I'll need to update. I downloaded the update from this XDA Thread
More questions:
- Would I be able to push the 4.05 bootloader update and custom whatever Marshmallow ROM via the toolkit instead of from a USB OTG?
- If I was rooted on 4.3, am I still rooted so that I would be able to flash the custom ROM? I don't want to risk doing further damage, lol.
- I'm not home at the moment, so I can't test this out -- I'm thinking I couldn't put anything into my tablet last night because it was running TWRP and I didn't have it on the Fastboot screen. Would being in the Fastboot screen possibly allow me to copy/paste the zip files into my tablet?
- If there's nothing I need to copy from the tablet, would I still need the USB OTG? Or could I just use the Toolkit to push everything into my tablet and flash via TWRP?
Based on your answers to the above would this be the correct order:
1. Push 4.05 bootloader update and custom ROM via toolkit to my tablet
2. Flash 4.05 bootloader update within TWRP
3. *Per your earlier advice* Wipe everything except USB OTG twice. Is this cache, dalvik, system, and data? Or literally there's an option for "wipe everything" (I don't remember what I saw)?
4. Then go to Format and do it twice, too. I have a 32GB, so I'm expecting it to take awhile for the format
5. Flash ROM, then Gapps. I don't have any apps I need to put back so much as I need an OS to load, so I can add later.
Thanks again for everything!
EDIT:
Okay, so I came home and was able to use the Toolkit to recognize the device in fastboot mode. However, I wasn't able to push anything into the phone because the Toolkit said that I needed to be booted into Android.
The last thing I saw when I was in TWRP poking around was that I saw that I could install .zip files from USB OTG. Are either of these alright for me to connect my flash drive to and be recognized inside TWRP?
Example 1
Example 2
kevs888 said:
This is really helpful...I think I'm almost there.
I'm on a super old Bootloader (see attachment) so I'll need to update. I downloaded the update from this XDA Thread
More questions:
- Would I be able to push the 4.05 bootloader update and custom whatever Marshmallow ROM via the toolkit instead of from a USB OTG?
- If I was rooted on 4.3, am I still rooted so that I would be able to flash the custom ROM? I don't want to risk doing further damage, lol.
- I'm not home at the moment, so I can't test this out -- I'm thinking I couldn't put anything into my tablet last night because it was running TWRP and I didn't have it on the Fastboot screen. Would being in the Fastboot screen possibly allow me to copy/paste the zip files into my tablet?
- If there's nothing I need to copy from the tablet, would I still need the USB OTG? Or could I just use the Toolkit to push everything into my tablet and flash via TWRP?
Based on your answers to the above would this be the correct order:
1. Push 4.05 bootloader update and custom ROM via toolkit to my tablet
2. Flash 4.05 bootloader update within TWRP
3. *Per your earlier advice* Wipe everything except USB OTG twice. Is this cache, dalvik, system, and data? Or literally there's an option for "wipe everything" (I don't remember what I saw)?
4. Then go to Format and do it twice, too. I have a 32GB, so I'm expecting it to take awhile for the format
5. Flash ROM, then Gapps. I don't have any apps I need to put back so much as I need an OS to load, so I can add later.
Thanks again for everything!
EDIT:
Okay, so I came home and was able to use the Toolkit to recognize the device in fastboot mode. However, I wasn't able to push anything into the phone because the Toolkit said that I needed to be booted into Android.
The last thing I saw when I was in TWRP poking around was that I saw that I could install .zip files from USB OTG. Are either of these alright for me to connect my flash drive to and be recognized inside TWRP?
Example 1
Example 2
Click to expand...
Click to collapse
If you're comfortable using the ToolKit, you don't need an OTG cable. Connect your tab to PC, fire up ToolKit, complete all the prelim BS, then flash the bootloader from TK. Do not use TWRP for this. To do this, open the ToolKit folder in drive C:, locate the folder therein for zips, place the zip files (4.05 bootloader; TWRP; or custom roms) in there, and start to install. I am talking off the top of my head. But give me a few minutes to check the Kit again, and I'll give specific instructions. Bear with me, as I'm on Linux at the moment and therefore cannot start ToolKit (which is in Windows).
Things to do in order:
1. Download bootloader 4.05 (flashable zip HERE); and custom rom of your choice (zip format)
2. Locate the Unified Android ToolKit on drive C: on your PC and open it;
3. Locate the folder “put zip file to sideload here” → “Nexus 7 2013” then paste
bootloader zip and Rom zip in there;
4. Fire up Toolkit with tab connected; complete all the prelim questions;
5. Follow all the steps to install TWR 2870 (pic 8, choice 6);
6. Go to TWRP, wipe and format.
7. Go back to TWRP main page → “Advanced” → “ADB sideload”;
8 Go to ToolKit (pic 8) enter choice 16 (Look at the pics that follow for the correct choices) to
sideload Bootloader;
9. Flash Bootloader.
10. Go back to TWRP main page → Reboot → Bootloader. Once there check bootloader version 4.05;
11. Get into TWRP to sideload Rom; flash it.
graphdarnell said:
Things to do in order:
1. Download bootloader 4.05 (flashable zip HERE); and custom rom of your choice (zip format)
2. Locate the Unified Android ToolKit on drive C: on your PC and open it;
3. Locate the folder “put zip file to sideload here” → “Nexus 7 2013” then paste
bootloader zip and Rom zip in there;
4. Fire up Toolkit with tab connected; complete all the prelim questions;
5. Follow all the steps to install TWR 2870 (pic 8, choice 6);
6. Go to TWRP, wipe and format.
7. Go back to TWRP main page → “Advanced” → “ADB sideload”;
8 Go to ToolKit (pic 8) enter choice 16 (Look at the pics that follow for the correct choices) to
sideload Bootloader;
9. Flash Bootloader.
10. Go back to TWRP main page → Reboot → Bootloader. Once there check bootloader version 4.05;
11. Get into TWRP to sideload Rom; flash it.
Click to expand...
Click to collapse
Wow, this is awesome. Thank you so much.
I had already flashed TWRP 2870 before I wiped the OS, but I figured I'd try again using the Toolkit, but I got an error. I stopped here just in case.
Earlier, I tried flashing the zip for the bootloader the same way you just instructed, but my serial number turned into question marks?
Please see attachments. My pics are on the right side of the comparisons and I blacked out some of my serial number just in case for the TWRP pic.
Thanks again for the continued support!
kevs888 said:
Wow, this is awesome. Thank you so much.
I had already flashed TWRP 2870 before I wiped the OS, but I figured I'd try again using the Toolkit, but I got an error. I stopped here just in case.
Earlier, I tried flashing the zip for the bootloader the same way you just instructed, but my serial number turned into question marks?
Please see attachments. My pics are on the right side of the comparisons and I blacked out some of my serial number just in case for the TWRP pic.
Thanks again for the continued support!
Click to expand...
Click to collapse
Ok. One step at a time. Since you don't have an OS installed, ToolKit cannot complete the process of sideloading because it normally would have to use ADB from within the OS (which is absent) to restart the tab into recovery mode (TWRP). But if you're already in sideload mode within TWRP, it would detect it and transfer the file over to your tab. Let's go back.
(1) Fire up ToolKit (TK), go to sideload step, type the file name and stop. Get to fastboot page on your tab. Go back to TK and hit enter. TK should detect fastboot mode, download TWRP 2.7.1.1, take the tab into TWRP, tell you to go to sideload mode. Thereafter, it should detect this mode and transfer the file over. Then TWRP would flash the bootloader 4.05 automatically. If successful, sideload the rom the same way to flash it. Then upgrade TWRP back to 2870 with TK.
(2) Failing the above (because TWRP somehow doesn't function correctly), put the tab in fastboot mode, go to TK and follow the steps to flash TWRP anew. TK should detect fastboot and begin to flash the recovery. That done, go back and restart (1) above.
(3) If that still doesn't work, we have to resort to fastboot.exe and do it by command lines. But that's far ahead. Try the above first. We'll cross that bridge if we get to it.
I can send you an automated package that would upgrade the bootloader to 4.04 that I downloaded a year ago from Scott's Roms (thanks to him). It's good enough for Lollipop 5.1. The file is about 4MB and I'm not sure how we can do this through XDA. But if we ever get there, I'm certain we'll find a way. And smile, it's only a lousy tab.
graphdarnell said:
Ok. One step at a time. Since you don't have an OS installed, ToolKit cannot complete the process of sideloading because it normally would have to use ADB from within the OS (which is absent) to restart the tab into recovery mode (TWRP). But if you're already in sideload mode within TWRP, it would detect it and transfer the file over to your tab. Let's go back.
(1) Fire up ToolKit (TK), go to sideload step, type the file name and stop. Get to fastboot page on your tab. Go back to TK and hit enter. TK should detect fastboot mode, download TWRP 2.7.1.1, take the tab into TWRP, tell you to go to sideload mode. Thereafter, it should detect this mode and transfer the file over. Then TWRP would flash the bootloader 4.05 automatically. If successful, sideload the rom the same way to flash it. Then upgrade TWRP back to 2870 with TK.
(2) Failing the above (because TWRP somehow doesn't function correctly), put the tab in fastboot mode, go to TK and follow the steps to flash TWRP anew. TK should detect fastboot and begin to flash the recovery. That done, go back and restart (1) above.
(3) If that still doesn't work, we have to resort to fastboot.exe and do it by command lines. But that's far ahead. Try the above first. We'll cross that bridge if we get to it.
I can send you an automated package that would upgrade the bootloader to 4.04 that I downloaded a year ago from Scott's Roms (thanks to him). It's good enough for Lollipop 5.1. The file is about 4MB and I'm not sure how we can do this through XDA. But if we ever get there, I'm certain we'll find a way. And smile, it's only a lousy tab.
Click to expand...
Click to collapse
Let me just say, I'm so thankful for your help in all of this. Seriously. Thank you.
I kept on tinkering with the ToolKit and Fastboot kept on stopping everytime I switched to TWRP. I got to the point where TWRP showed 2.7.1 but the ADB Sideload kept getting stuck at the "Starting Sideload" prompt.
I went out and bought a $3 OTB USG cable and figured I'd give it a go since this sounded easier (theoretically). At first, I couldn't understand why the OTG wasn't recognized within TWRP. Then, I realized I needed to mount it within TWRP.
Once it mounted, I wiped and flashed the 4.05 bootloader zip. Success.
I went back into the Fastboot screen to verify 4.05. Success.
Went back into TWRP 2.8.7 and flashed a 6.0 ROM from these boards. Success.
Flashed Gapps. Success.
Rebooted. I'm now running a custom Marshmallow ROM and it runs so smoothly now.
Seriously. Thank you.
kevs888 said:
Let me just say, I'm so thankful for your help in all of this. Seriously. Thank you.
I kept on tinkering with the ToolKit and Fastboot kept on stopping everytime I switched to TWRP. I got to the point where TWRP showed 2.7.1 but the ADB Sideload kept getting stuck at the "Starting Sideload" prompt.
I went out and bought a $3 OTB USG cable and figured I'd give it a go since this sounded easier (theoretically). At first, I couldn't understand why the OTG wasn't recognized within TWRP. Then, I realized I needed to mount it within TWRP.
Once it mounted, I wiped and flashed the 4.05 bootloader zip. Success.
I went back into the Fastboot screen to verify 4.05. Success.
Went back into TWRP 2.8.7 and flashed a 6.0 ROM from these boards. Success.
Flashed Gapps. Success.
Rebooted. I'm now running a custom Marshmallow ROM and it runs so smoothly now.
Seriously. Thank you.
Click to expand...
Click to collapse
I'm glad you got it working again. Sorry you had to make a trip to the store. You should've waited for KT to switch the tab to TWRP 2711 for you. But it was not a waste of time anyway.

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).

I think I bricked my ZE551ML_Z00A

Hi everyone, I think I bricked my ZE551ML by being very very dumb, how did I come in such troubles? Well I'll explain you the whole story.
Usually I'm quite good with IT but I'm new to Android and I wanted to install Lineageos because I don't like Asus's ROM, so I searched tutorials and I found the lineage website tutorial at first it didn't seem like a hard task for me, so I started following the tutorial and I got stopped first with trying to get twrp-3.1.1-0-Z00A on the device but didn't seem to work so I tried an older version witch didn't worked too, so I came to xda to get the twrp_z00a_v24_repack and it worked (so well that I erased the system without saving anything just in case but I saved myself by getting the Asus ROM and pushing it to /sdcard/ ) so I attempted to install Lineage (that time with a save) but it gave me the "error executing updater binary in zip" so I searched on the Internet and it seemed that I had to root the phone so I downloaded addonsu-14.1-x86-signed from the Lineageos website and ran it on twrp and it told me that it worked so I wiped the system (I still got the backup) and tried to install Lineage but the same error showed up so I was thinking "Hmm maybe due to TWRP being an old version it might not work if it's not updated" so I rebooted to fastboot and then did fastboot flash recovery twrp-3.1.1-0-Z00A and tried to go in recovery, the phone rebooted, the splashscreen showed and it got to a screen similar to the splashscreen and did nothing (just heard the plug-in device sound in Windows), when I try to shut down and push the power + "+" Button it just starts as normal and the fastboot mode doesn't show.
So that's where I am, if someone could do a dumbproof step by step tutorial on how to unbrick that thing and then install Lineageos that would be so great.
Thank so much to the person (or people) that will help me
PS: I tried to search how to get out of this mess but I didn't understood all of it so I didn't wanted to get in more troubles.
Yuno17 said:
Hi everyone, I think I bricked my ZE551ML by being very very dumb, how did I come in such troubles? Well I'll explain you the whole story.
Usually I'm quite good with IT but I'm new to Android and I wanted to install Lineageos because I don't like Asus's ROM, so I searched tutorials and I found the lineage website tutorial at first it didn't seem like a hard task for me, so I started following the tutorial and I got stopped first with trying to get twrp-3.1.1-0-Z00A on the device but didn't seem to work so I tried an older version witch didn't worked too, so I came to xda to get the twrp_z00a_v24_repack and it worked (so well that I erased the system without saving anything just in case but I saved myself by getting the Asus ROM and pushing it to /sdcard/ ) so I attempted to install Lineage (that time with a save) but it gave me the "error executing updater binary in zip" so I searched on the Internet and it seemed that I had to root the phone so I downloaded addonsu-14.1-x86-signed from the Lineageos website and ran it on twrp and it told me that it worked so I wiped the system (I still got the backup) and tried to install Lineage but the same error showed up so I was thinking "Hmm maybe due to TWRP being an old version it might not work if it's not updated" so I rebooted to fastboot and then did fastboot flash recovery twrp-3.1.1-0-Z00A and tried to go in recovery, the phone rebooted, the splashscreen showed and it got to a screen similar to the splashscreen and did nothing (just heard the plug-in device sound in Windows), when I try to shut down and push the power + "+" Button it just starts as normal and the fastboot mode doesn't show.
So that's where I am, if someone could do a dumbproof step by step tutorial on how to unbrick that thing and then install Lineageos that would be so great.
Thank so much to the person (or people) that will help me
PS: I tried to search how to get out of this mess but I didn't understood all of it so I didn't wanted to get in more troubles.
Click to expand...
Click to collapse
if you are able to access recovery then dd fastboot there. if no recovery, no fastboot, no system there isonly option left. go to below thread and do step by step as suggested.. after you get fastboot mode back, do not use asus flash tool use commands to flash raw firmware see section flash firmware without AFT
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
if you are able to access recovery then dd fastboot there. if no recovery, no fastboot, no system there isonly option left. go to below thread and do step by step as suggested.. after you get fastboot mode back, do not use asus flash tool use commands to flash raw firmware see section flash firmware without AFT
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi, thanks for the reply, I don't know if I have to post it here or on the guide but xFSTK-downloader just won't run (Windows 10 1151) and it doesn't show up in task manager (even when the antivirus is disabled).
Have you got an idea on why it doesn't work?
Yuno17 said:
Hi, thanks for the reply, I don't know if I have to post it here or on the guide but xFSTK-downloader just won't run (Windows 10 1151) and it doesn't show up in task manager (even when the antivirus is disabled).
Have you got an idea on why it doesn't work?
Click to expand...
Click to collapse
very first of all uninstall everything especially i soc drivers and xFSTK. then disable driver signature enforcement. and go to thread above posted and do step by step.
how to disable signature enforcement and install driver on win 10 see in thread above

My Honor 7x BND-L21 is quite broken, need help

Hello, sorry for the generic title, but i'm quite the noob about android modding and stuff.
Anyway I wanted to root my phone, just to stream some music to my stereo system. How naive I was...
So I unlocked the bootloader, installed twrp with adb and SuperSU with twrp. Everything was fine and phone was rooted but my past naive me thought "well let's try a custom rom, why not". So I went forth and downloaded some stuff from getdroidtips and what I understood is that all I needed to do was to do a wipe, then install the zip file via twrp. I did that and didn't work. After that I realized I made a crucial mistake: I didn't backup my phone from twrp, so I was there with no OS, quite panicked and frustrated. So I tried some other roms, finally I got one that worked, this: https://forum.xda-developers.com/honor-7x/development/openkirin-aosp-8-0-honor-7x-t3746257
It works but it's barebones and on boot it shows a message: "There's an internal problem with your device. Contact your manifacturer for details.". So, I tried recovering from HiSuite, recovery mode etc but nothing worked, I reinstalled SuperSU in the new OS via twrp to see if that would help somehow, but no. in the end I had the even more naive thought that maybe unrooting would allow me to repair via hi suite or something, so I mindlessly selected "complete unroot" on the SuperSU app, and this was the second big mistake, the process somehow ****ed up the twrp install and it no longer works. Instead, if I try to enter twrp with power button + volume up button, it shows the regular "your phone has been unlocked" screen and then comes up for a split second a black screen with, on the bottom half of the screen the "no command" logo, under it some lines of code that I can't read. It suddenly disappears and sometimes enters in a bootloop showing this screen and powering off every time.
If I keep power button pressed bootloop ends and the phone boots "regularly" in the openkirin OS.
I tried reinstalling twrp the same way I did the first time. No error on adb but same no command behaviour
So what I got now is:
kind of bootlooping no command window
openkirin OS with internal problem message
fastboot and rescue mode
it seems to work on adb (everything is fine if I type adb devices)
not working HiSuite recovery
not working Huawei eRecovery
not working download mode (I guess? the power+volume up+volume down combination)
Maybe I should mention I also did a data wipe (?? the option on the right next to "advanced wipe" in the Wipe screen, if I remember correctly) in twrp before installing openkirin, it was suggested on a yt video about how to install openkirin. And that, at a stage I tried using MultiTool but it gives me an error: "exception during a web client request. Error#9", while at the bottom left it says "downloading AdbWinUsbApi.dll..."
Sorry for the general noobishness and the bad english that might be there.
So, any tips for bringing back the phone to normal? Or at least repair twrp??
Please help, I hate needing to throw this phone away just because I wanted to stream some music and because of a couple of stupid errors
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
sdivk said:
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
Click to expand...
Click to collapse
No worries, I managed to fix it anyway. Some things might be obvious but I'll share what I did nevertheless, in case some other newbie finds himself in a similar situation.
So there was seemingly no way of reinstalling twrp nor the stock recovery. But luck came my way and by almost random clicking I found out that, even if multitool closed as soon as I clicked the ok button in the error message, if I simply ignored the error, the program worked just fine (as I write this I installed another version and it gave no error message). So I played with it a bit and found out that it can flash twrp and it does not need a file from you, it already has a twrp version ready to install. I did that and it worked. It looks like the first twrp file I used didn't work anymore or was someway corrupted by the countless things I tried. So, with twrp working again I was able to backup the sloppy openkiring OS and try the unbrick tool. So I browsed the internet for a guide. Guides always mention as the first step for unbricking using the VENDOR.img file located inside a full stock rom. Problem is, 99% of the times they provide a rom without the needed file. So after some tries I found a good complete stock rom with the VENDOR.img here: drive.google.com/file/d/1tjHefytEWbpuV1f4YjX8AaSMzT6jr8TQ/view but I can't remember which forum/site I found it in.
I followed the guide which involves:
-extracting the UPDATE.APP file contained in the provided zip with huawei extractor tool into an X folder on your pc
-copying the VENDOR.img file contained in the X folder, on the root folder of the sd card
-backing up OS (if there's any) via twrp (I had something like 50 partitions, I guess that was messing things up a bit, but for safety I backed them all up)
-doing an advanced wipe from twrp selecting ALL checkboxes BESIDES the SDcard of course
-flashing the vendor.img file via twrp selecting the "Vendor" partition when prompted
-downloading the update_full_[your model]_hw_[your region].zip file, in my case update_full_BND-L21C_hw_eu.zip
-extracting the UPDATE.APP file contained in update_full_BND-L21C_hw_eu.zip with Huawei extractor tool in some other folder Y
-looking for a file named cust.img/CUST.img/version.img/other_name.img (I don't know which other names it can have, I was lucky and had a VERSION.img file in it)
-rename the cust.img/CUST.img/version.img/other_name.img to CUST.img and copy it from the Y folder to the X folder
-boot your phone into fastboot mode
-connect phone to multitool via usb and select the "unbrick" tab
-there, Multitool asks for a folder, give it the X folder. There are some checkmarks on the Multitool "unbrick" page. 4/5 of them should become checked after the folder input. In my case the first 4
-then, simply press the unbrick button
-wait and pray (it can look like it freezes while it's copying the system.img file but wait, it'll be fine)
So I did that and it worked flawlessly, the phone booted slowly but surely into EMUI 5.1 with Android 7.0 I think and everything was fine.
At that point I had a working OS and a working twrp but wanted to go back to the OS I was used to, Android 8.something so, I tried connecting the thing to HiSuite and it automatically asked if I wanted to update, not to 8.something but to 9.1. I thought "SURE I DO!" and updated flawlessly (I thought 9.1 hadn't even been released here in Italy).
When it booted I found out the new OS was working like an antivirusless xp pc: it didn't recognise the SIM, it would crash every 20 seconds, app downloads got stuck at 99%, if it felt like it, it rebooted, pc connection was not stable. Besides, the update being "official" and installed from "trusted" sources (HiSuite), it completely wiped twrp.
And that was the "OH ****, here we go again" moment: no twrp and worse-than-ever-working OS.
So because of the new EMUI version, I guess, Multitool kept recognizing the phone but stopped offering its own recovery, eRecovery, twrp files available for flashing. I was completely frustrated with all of this and decided to give up, but I made the last effort: I tried the relock function in multitool. So I provided the key, pressed relock, waited, prayed, and finally cheered. It worked like a charm. Phone runs now on EMUI 9.1 with locked bootloader without problems. Finally
So I guess in the end I payed 4 euros for a nice update, a painful and frustrating trip into android modding and a lesson : never do android modding!
no, just kidding, don't do it just if you are a newbie AND you don't want to risk to throw the phone in the grabage.
In all other cases consider it carefully
Oh, and also, God bless the MT Team and Russia altogether!! thanks
Quite an experience. All the best. ?
Lol sounds fun. I've bricked my Huawei Mate SE/Honor 7x more times than I can count. I'm just awaiting my 9.1. I want my GPU Turbo! Is it as good as it's supposed to be?

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.

Categories

Resources