Related
I just want to verify before I actually try this because I have already bricked one phone and i don't want to brick another.
How do I go about flashing CWM for my recovery instead of TWRP?
Can I just download CWM, rename it to recovery.img and run
Code:
fastboot flash recovery recovery.img
Or is there some other method??
Thanks.
BigRed35m said:
I just want to verify before I actually try this because I have already bricked one phone and i don't want to brick another.
How do I go about flashing CWM for my recovery instead of TWRP?
Can I just download CWM, rename it to recovery.img and run
Code:
fastboot flash recovery recovery.img
Or is there some other method??
Thanks.
Click to expand...
Click to collapse
you;ve got it exactly right! allthough remember that you've renamed it to recovey.img because if in the future you do the same again for twrp or a different version you may forget which you have renamed. In addition if you already ahve either recovery and root you can download rommanager/goo.manager and within the app flash cwm/twrp respectively without ever having to use fastboot. Allthough the CWM in the forums has larger text but its the same thing.
jonesin said:
you;ve got it exactly right! allthough remember that you've renamed it to recovey.img because if in the future you do the same again for twrp or a different version you may forget which you have renamed. In addition if you already ahve either recovery and root you can download rommanager/goo.manager and within the app flash cwm/twrp respectively without ever having to use fastboot. Allthough the CWM in the forums has larger text but its the same thing.
Click to expand...
Click to collapse
Thanks! I saw a couple forums that related to goo manager, but wasn't sure if I'd be able to use it without S-OFF or not. Running the command through CMD Prompt seems easiest for me right now so I'll give that a try. Thanks again.
BigRed35m said:
Thanks! I saw a couple forums that related to goo manager, but wasn't sure if I'd be able to use it without S-OFF or not. Running the command through CMD Prompt seems easiest for me right now so I'll give that a try. Thanks again.
Click to expand...
Click to collapse
One more thing TWRP has been exhibiting problems for many users and at this time and until further notice i would recomend against it. It can be made to work but is buggy
jonesin said:
One more thing TWRP has been exhibiting problems for many users and at this time and until further notice i would recomend against it. It can be made to work but is buggy
Click to expand...
Click to collapse
TWRP Has shown problems when trying to switch to CWM? Or just in general?
BigRed35m said:
TWRP Has shown problems when trying to switch to CWM? Or just in general?
Click to expand...
Click to collapse
not it has nothing to do with switching between the two
TWRP has exhibitied problems when attempting to create a backup or when attempting to restore a backup. Just avoid it for now CWM is more stable
jonesin said:
not it has nothing to do with switching between the two
TWRP has exhibitied problems when attempting to create a backup or when attempting to restore a backup. Just avoid it for now CWM is more stable
Click to expand...
Click to collapse
were the problems with the md5 sum part ? i had problems with CWM it wouldent backup so I had to to switch to twrp
syler2012 said:
were the problems with the md5 sum part ? i had problems with CWM it wouldent backup so I had to to switch to twrp
Click to expand...
Click to collapse
I have had problems backing up with both. Try switching backup type to .tar in CWM. TWRP has had problems backing up as well. Right now we dont have a rock solid stable recovery just have to work around it. CWM has had more fixes applied though I know this for a fact.
BigRed35m said:
I just want to verify before I actually try this because I have already bricked one phone and i don't want to brick another.
How do I go about flashing CWM for my recovery instead of TWRP?
Can I just download CWM, rename it to recovery.img and run
Code:
fastboot flash recovery recovery.img
Or is there some other method??
Thanks.
Click to expand...
Click to collapse
If you don't do a lot of backups/restores I actually recommend TWRP. The built in file manager makes file management without S-OFF a lot more hassle free. Another upside I've found with TWRP is "adb remount" actually works. It's just the little things. The downsides of TWRP that I've found are, add I've stated backup/restore and the size (which actually bugs me so much that I'm using CWM). Overall, as of now for this device, I recommend TWRP for the everyday rooted user.
Sent from my HTC6435LVW using xda app-developers app
I'm trying to get into the bootloader to flash an older version of TWRP. I'm holding various combinations of buttons down when rebooting but the phone either goes to Recovery, Odin, or normal boot. The "bootloader" boot option in TWRP doesn't work either, it just goes to normal boot. What am I missing? I know for many phones the bootloader is accessed by holding VOL Down + Power when rebooting but that's not working on the Note 2.
Thanks.
slicknick27 said:
I'm trying to get into the bootloader to flash an older version of TWRP. I'm holding various combinations of buttons down when rebooting but the phone either goes to Recovery, Odin, or normal boot. The "bootloader" boot option in TWRP doesn't work either, it just goes to normal boot. What am I missing? I know for many phones the bootloader is accessed by holding VOL Down + Power when rebooting but that's not working on the Note 2.
Thanks.
Click to expand...
Click to collapse
I believe the reason why you can't boot into bootloader is because it has something to do with the Unlock Bootloader method/exploit. I'm going to take a shot in the dark and say the exploit is not the standard unlock method so therefore you can't boot into the bootloader.
Also, you can flash a recovery a different way. Download the Goo.im Manager app in the Google Play Store and when you go in the app, you can search the recoveries and it will flash them from the app for you.
DroidOnRoids said:
I believe the reason why you can't boot into bootloader is because it has something to do with the Unlock Bootloader method/exploit. I'm going to take a shot in the dark and say the exploit is not the standard unlock method so therefore you can't boot into the bootloader.
Also, you can flash a recovery a different way. Download the Goo.im Manager app in the Google Play Store and when you go in the app, you can search the recoveries and it will flash them from the app for you.
Click to expand...
Click to collapse
Hey, thanks for shedding some light on this. And I'm going to try flashing from the Goo.im manager, that sounds easier at this point, too.
slicknick27 said:
Hey, thanks for shedding some light on this. And I'm going to try flashing from the Goo.im manager, that sounds easier at this point, too.
Click to expand...
Click to collapse
No problem, man. Just make sure you flash the right recovery file because if you are broad on your search, it will give you a list of different recoveries for different devices. Search the version of TWRP you want with 'i605'.
DroidOnRoids said:
No problem, man. Just make sure you flash the right recovery file because if you are broad on your search, it will give you a list of different recoveries for different devices. Search the version of TWRP you want with 'i605'.
Click to expand...
Click to collapse
Unfortunately there are no older versions of TWRP in the Goo.im manager app. This is off-topic from my original question but it's the reason I was trying to get into the bootloader in the first place. Do you know of any way to downgrade TWRP to a previous version on this phone other than the flashing from bootloader method?
slicknick27 said:
Unfortunately there are no older versions of TWRP in the Goo.im manager app. This is off-topic from my original question but it's the reason I was trying to get into the bootloader in the first place. Do you know of any way to downgrade TWRP to a previous version on this phone other than the flashing from bootloader method?
Click to expand...
Click to collapse
Hm, you searched with i605, right? Well, I searched and found that on Goo.im, it is actually t0ltevzw.
Here are all the TWRP builds for the VZW Note 2 from Goo.im: http://goo.im/devs/OpenRecovery/t0ltevzw/
EDIT: Here's our device page on the TWRP website: http://teamw.in/project/twrp2/133
EDIT 2: If I were you, try not to flash a recovery using Odin. I wouldn't risk screwing up the unlocked bootloader exploit. Lastly, if you didn't know, do NOT in any way flash a custom rom using Odin. It's bad news for your phone.
Edited again because I forgot fastboot requires bootloader access lol
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
DroidOnRoids said:
Hm, you searched with i605, right? Well, I searched and found that on Goo.im, it is actually t0ltevzw.
Here are all the TWRP builds for the VZW Note 2 from Goo.im: http://goo.im/devs/OpenRecovery/t0ltevzw/
EDIT: Here's our device page on the TWRP website: http://teamw.in/project/twrp2/133
EDIT 2: If I were you, try not to flash a recovery using Odin. I wouldn't risk screwing up the unlocked bootloader exploit. Lastly, if you didn't know, do NOT in any way flash a custom rom using Odin. It's bad news for your phone.
Edited again because I forgot fastboot requires bootloader access lol
Click to expand...
Click to collapse
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
slicknick27 said:
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
Click to expand...
Click to collapse
So the 2.4.0.0 is the version you want, correct? And which file of this recovery version did you download? If you tried downloading and installing using the Goo.im app, try downloading the zip file from your computer and transferring it over to your SD Card. From there you can reboot to the existing recovery, install it, and reboot the recovery.
If that doesn't work either, tell me and I can figure out a different option.
DroidOnRoids said:
So the 2.4.0.0 is the version you want, correct? And which file of this recovery version did you download? If you tried downloading and installing using the Goo.im app, try downloading the zip file from your computer and transferring it over to your SD Card. From there you can reboot to the existing recovery, install it, and reboot the recovery.
If that doesn't work either, tell me and I can figure out a different option.
Click to expand...
Click to collapse
Actually, if I can I'd like to downgrade to TWRP 2.3.3.1, which was the version I installed back when I got the phone in December.
On Goo.im web site it is:
openrecovery-twrp-2.3.3.1-t0ltevzw.zip
It is my understanding though that you can't flash TWRP from within TWRP?
slicknick27 said:
Actually, if I can I'd like to downgrade to TWRP 2.3.3.1, which was the version I installed back when I got the phone in December.
On Goo.im web site it is:
openrecovery-twrp-2.3.3.1-t0ltevzw.zip
It is my understanding though that you can't flash TWRP from within TWRP?
Click to expand...
Click to collapse
You can flash CWM in TWRP, TWRP in CWM, TWRP in TWRP, or CWM in CWM. All you need to do is flash it and then go to the recovery options and hit Reboot Recovery.
Where did you hear that you can't flash TWRP in TWRP?
DroidOnRoids said:
You can flash CWM in TWRP, TWRP in CWM, TWRP in TWRP, or CWM in CWM. All you need to do is flash it and then go to the recovery options and hit Reboot Recovery.
Where did you hear that you can't flash TWRP in TWRP?
Click to expand...
Click to collapse
OK, yeah, I was told in another thread that I couldn't flash TWRP with TWRP.
So, I just want to clarify, I can flash an older version of TWRP over an newer version of TWRP already installed -- as if I was flashing any regular .zip?
slicknick27 said:
OK, yeah, I was told in another thread that I couldn't flash TWRP with TWRP.
So, I just want to clarify, I can flash an older version of TWRP over an newer version of TWRP already installed -- as if I would flash any regular .zip?
Click to expand...
Click to collapse
Yes, you can do that because it's going to completely overwrite the other version of TWRP. It doesn't matter what version you flash because it's going to be all on its own. The previous recovery doesn't benefit from a newer version of a recovery. You're safe to do it
EDIT: When I had my Galaxy Nexus, TWRP was brand spanking new so I had to downgrade a lot because of all the bugs presented in the later releases.
DroidOnRoids said:
Yes, you can do that because it's going to completely overwrite the other version of TWRP. It doesn't matter what version you flash because it's going to be all on it's own. The previous recovery doesn't benefit from a newer version of a recovery. You're safe to do it
EDIT: When I had my Galaxy Nexus, TWRP was brand spanking new so I had to downgrade a lot because of all the bugs presented in the later releases.
Click to expand...
Click to collapse
Phew. OK. Well again I thank you for sticking with me and clearing this up. I suspected I could do that in the first place but was confused by information I was given otherwise. Off I go to recovery!
slicknick27 said:
Phew. OK. Well again I thank you for sticking with me and clearing this up. I suspected I could do that in the first place but was confused by information I was given otherwise. Off I go to recovery!
Click to expand...
Click to collapse
Good luck! Let me know when it's a success.
DroidOnRoids said:
Good luck! Let me know when it's a success.
Click to expand...
Click to collapse
Well, TWRP verified the checksum and the modem installed successfully. But apparently it turns out the problem was not as it originally seemed.
When I downloaded the older version of TWRP, I opened its .MD5 file again just to check, and I noticed that the .MD5 files for the zips on Goo.im (or at least OpenRecovery's ZIPS) omitted the asterisk that precedes the filename:
Code:
d4624c4f8c9427b6137b2b97902e76b3 openrecovery-twrp-2.4.1.0-t0ltevzw.zip
Whereas with other .MD5 files that I've created (including the .MD5 file for the modem zip that was failing verification in TWRP), I've used an asterisk before the filename:
Code:
d4624c4f8c9427b6137b2b97902e76b3 [B][COLOR="Red"]*[/COLOR][/B]openrecovery-twrp-2.4.1.0-t0ltevzw.zip
So after the modem flashed successfully on TWRP 2.3, I decided to try flashing it again (with the asterisk omitted from the MD5 file) on the latest TWRP 2.4.1.0. It flashed just fine. So the issue seems to be TWRP getting hung up on the asterisk that precedes the filename in MD5 files -- though this doesn't happen all the time because I've flashed many MD5 files with the asterisk successfully.
A bug in TWRP? Or maybe I shouldn't be using the asterisk at all. In any case, I'm back on TWRP 2.4.1.0 with the modem flashed.
EDIT: And I learned that you can flash TWRP in TWRP
slicknick27 said:
Well, TWRP verified the checksum and the modem installed successfully. But apparently it turns out the problem was not as it originally seemed.
When I downloaded the older version of TWRP, I opened its .MD5 file again just to check, and I noticed that the .MD5 files for the zips on Goo.im (or at least OpenRecovery's ZIPS) omitted the asterisk that precedes the filename:
d4624c4f8c9427b6137b2b97902e76b3 openrecovery-twrp-2.4.1.0-t0ltevzw.zip
Whereas with other .MD5 files that I've created (including the .MD5 file for the modem zip that was failing verification in TWRP), I've used an asterisk before the filename:
d4624c4f8c9427b6137b2b97902e76b3 *openrecovery-twrp-2.4.1.0-t0ltevzw.zip
So after the modem flashed successfully on TWRP 2.3, I decided to try flashing it again (with the asterisk omitted from the MD5 file) on the latest TWRP 2.4.1.0. It flashed just fine. So the issue seems to be TWRP getting hung up on the asterisk that precedes the filename in MD5 files -- though this doesn't happen all the time because I've flashed many MD5 files with the asterisk successfully.
A bug in TWRP? Or maybe I shouldn't be using the asterisk at all. In any case, I'm back on TWRP 2.4.1.0 with the modem flashed.
EDIT: And I learned that you can flash TWRP in TWRP
Click to expand...
Click to collapse
I would bring that to their attention and see why that's the case on their recovery. Anyway, glad that everything is figured out and running perfectly. :good:
DroidOnRoids said:
I would bring that to their attention and see why that's the case on their recovery. Anyway, glad that everything is figured out and running perfectly. :good:
Click to expand...
Click to collapse
Yes I'm going to report it.
Take it easy.
hi Guys!
I just wanted to share my work with you.
I created a working TWRP recovery for the Pixel on Android O developer preview 4, that can boot and decrypt the /data partition. I don't own a Pixel XL, so I can't test, but @Chainfire did a few quick tests and it seems to be working on his Pixel XL too. So I would say you can try and see if it works for you. Please keep in mind, that I didn't test it, and neither Chainfire, or myself or anyone else can be blamed if it doesn't work, or damages your phone (shouldn't actually, but who knows..).
If you are still not scared enough, please follow this link to the Pixel forums and check out my work:
https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
Good luck!
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
sahilarora2003 said:
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
Click to expand...
Click to collapse
Its in the instructions but here is the command and you shouldn't flash it but instead fastboot it.
fastboot boot trwp.img
flash the latest supersu 2.82 sr1
NVM. Mission accomplished. Thank you for help.
feimummy said:
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
Click to expand...
Click to collapse
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
SR2 flash fine
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
You can try SR2 flash fine.
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
feimummy said:
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Click to expand...
Click to collapse
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
gubacsek said:
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
Click to expand...
Click to collapse
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
——————————The final outcome——————————
I have solved the problem with this SuperSU version:
https://forum.xda-developers.com/showpost.php?p=72686197&postcount=10481
Thanks a lot.
feimummy said:
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
Click to expand...
Click to collapse
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
gubacsek said:
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
Click to expand...
Click to collapse
Sr2 flash fine!
caballon said:
Sr2 flash fine!
Click to expand...
Click to collapse
Great! Nice to see that everything is working I had this itching, you know, when something is not as it should be, because I wanted to have Android O, but there was no recovery to do what I want... Now this feeling is gone, and I'm relaxed again
The only thing missing is a flashable zip. Is my current "itch"
Very nice. I booted into TWRP with no issue. I had already used boot-to-root so I did not have to flash SR2 in TWRP but nice knowing we have it working for the XL.
Thank you for making this sir.
Work like a charm in Final Android O!!! Thanks man.
caballon said:
Work like a charm in Final Android O!!! Thanks man.
Click to expand...
Click to collapse
Same here!
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
liam_davenport said:
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
Click to expand...
Click to collapse
Had this already sometimes on 7.1.2 with twrp rc 1 and 2. Must be an encryption error. Only way for me to use the phone again was to start all over with flashing factory image with flash-all.bat.
liam_davenport said:
People have successfully rooted O Final?
Click to expand...
Click to collapse
Reboot until you get prompted for your PIN in recovery, then flash SuperSU v2.82 SR3 from here.
The TWRP for the HD1910 works perfectly on the HD1925. Decryption works too. Install TWRP by using the installer.
Exact the img from the installer zip.
Boot to fastboot
Open a CMD within the extracted TWRP installer folder and type in
"fastboot boot recovery.img"
Once TWRP boots, then install the TWRP installer zip file.
I flashed magisk and it flashed with no issues. I used the latest version here.
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
NOTE: I did it on the latest version, 11.0.1.18 So I'm not sure if it works on any older versions but I would assume so.
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
starcms said:
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
Click to expand...
Click to collapse
I already know about all that. I've had this phone over a year, so I'm familiar with the hidden "secrets".
starcms said:
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
Click to expand...
Click to collapse
BTW, with unlocked bootloader OTA's are not available no matter what type of recovery you have installed. Unless you have reinstalled the reserve.img after unlocking the bootloader
AntiSocialSingh said:
@BobbyLynn I followed your tutorial to install the CrDroid recovery. Can you tell me how to flash TWRP? Bit of a noob for this phone.
Click to expand...
Click to collapse
Exact (Unzip) the zip folder. Within the extracted folder you'll see some other files. One of them is a recovery.img file. Open a command or PowerShell in the extracted folder. Reboot to fastboot.
Boot to fastboot and run this command
"fastboot boot recovery.img"
Once it boots into TWRP, then click on "install" and locate the TWRP installer zip and select it. It'll most likely be in the download folder. Just make sure you know where the TWRP installer zip is located before you even boot into TWRP
BobbyLynn said:
Exact (Unzip) the zip folder. Within the extracted folder you'll see some other files. One of them is an .img file (recovery). Open a command or PowerShell in the extracted folder. Reboot to fastboot.
Boot to fastboot and run this command
"fastboot boot recovery.img"
Once it boots into TWRP, then click on "install" and locate the TWRP installer zip and select it. It'll most likely be in the download folder. Just make sure you know where the TWRP installer zip is located before you even boot into TWRP
Click to expand...
Click to collapse
BTW download this TWRP from the link in my thread "twrp-installer-3.6.1_11-0-hotdog.zip"
AntiSocialSingh said:
@BobbyLynn Do i need to flash both a & b like i did in the case of crDroid?
Click to expand...
Click to collapse
Not at all. The installer will take care of all that once you boot into TWRP
AntiSocialSingh said:
@BobbyLynn Should I take a backup? Would it wipe my storage? or it would be as it is?
Click to expand...
Click to collapse
No it won't wipe data or anything else. But it's always good to have a backup just in case anything goes sour.
AntiSocialSingh said:
@BobbyLynn I am on the screen which says Install, Wipe, Backup, restore...... what should i do to install the zip file now?
Click to expand...
Click to collapse
Just click on "install" then located the installer zip file then select it and install it
AntiSocialSingh said:
I copied the .zip file on my phone but cannot navigate to it since all it shows is (Up A level), does not show the directories inside the storage
Click to expand...
Click to collapse
Select up a level then scroll down until you see a file called "storage" that'll take you to your storage. If it doesn't, the go back and click on "sdcard" But I'm almost certain it's in the storage folder
AntiSocialSingh said:
I think i need to flash it once via TWRP, i'll try it later, but thank you, it means that this TWRP works!
Click to expand...
Click to collapse
I just checked..... The "sdcard" folder is the one that takes you to the internal storage where the download folder is located. But as soon as you hit 'install" it should've taken you straight to the internal storage. If it didn't, then it sounds like it's still encrypted. If that's the case, then remove any screen locks on your phone before flashing TWRP
AntiSocialSingh said:
@BobbyLynn Let me try once again with the screen lock removed.
Click to expand...
Click to collapse
When I installed TWRP I didn't have a screen lock. But after installing TWRP I set a screen lock and TWRP decrypted just fine. So I'm guessing if you install TWRP while you have a screen lock it doesn't install properly so it can't decrypt. It appears that any screen locks must be removed before installing and after installing reapply a screen lock
AntiSocialSingh said:
@BobbyLynn It worked! So basically, I had to remove both fingerprint and pattern locks to get it to work. Thanks a ton!!
Click to expand...
Click to collapse
No problem
BobbyLynn said:
No problem
Click to expand...
Click to collapse
I'm kinda curious, why did you install TWRP? Are you fixing to "test drive" some custom ROM's or flash some mods? Or did you install TWRP just for the hell of it?
AntiSocialSingh said:
@BobbyLynn The latter yes, test driving some mods, and I am used to the interface of TWRP, not crDroid much, personal preference hahahaha....Thank you so much once again. you're a legend.
Click to expand...
Click to collapse
I'm more use to TWRP myself. I started using TWRP about 10 years ago, it was and still is the best recovery out there. I just happened to install crDroid the other day just to test something. And that test turned out to be a great discovery of a simple way to root the stock firmware. Since I have a extra McLaren, I do quite a bit of testing and modding and experimental stuff. I'm currently working on installing the global firmware (unbranding) it. No luck yet, but I might be getting close.
AntiSocialSingh said:
@BobbyLynn I will be the first one to follow your tutorial if you manage to flash the Global ROM on it sir. I promise haha!
Click to expand...
Click to collapse
You can bet your ass that if I pull off that trick it'll get LOT'S of comments from people thanking me lol. We've been wanting to install the global firmware on this phone, but nobody can figure out how to mod the ROM to make it flash on this phone. There's some very smart developers that own this phone, so I'm surprised that none of them have figured it out yet. So I've been tinkering around with trying to install it. It's looking like I'm going to have to make some modifications to the global ROM and/or the phone too to make the MSM tool see the phone as a comparable device
BobbyLynn said:
BTW, with unlocked bootloader OTA's are not available no matter what type of recovery you have installed. Unless you have reinstalled the reserve.img after unlocking the bootloader
Click to expand...
Click to collapse
Well, yeah, restoring reserve.img is a prerequisite to get OTAs with the bootloader unlocked, but it only has to be done once. After that, for each ota, just restore the boot image to stock (uninstall magisk) and you're good to go
starcms said:
Well, yeah, restoring reserve.img is a prerequisite to get OTAs with the bootloader unlocked, but it only has to be done once. After that, for each ota, just restore the boot image to stock (uninstall magisk) and you're good to go
Click to expand...
Click to collapse
I wanted to do OTA how should I restore my reserve.img?
Hello XDA developers, I'm in urgent and I have a really big problem. It sounds funny but, I deleted my realme ui recovery ,_,
I was trying to install PPUI 4.1 on my Realme 7 but I saw a tutorial that you have to erase the recovery to install TWRP. Please, I need a solution of how can I get it back. I also tried flashing a lot of recoveries and their vbmeta but nothing works. Sadly.
Edit: I'm on RMX2151_11_C.17 | Realme UI 2.0 Latest version
Here is the stock recovery
Chenes said:
Here is the stock recovery
Click to expand...
Click to collapse
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Sorry for a lot of questions, haha
iOussamato_ said:
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Click to expand...
Click to collapse
From what I read before, fastboot boot will only boot to that recovery file temporarily but I haven't tried it myself. It should be
Code:
fastboot flash recovery recovery.img
I'm not 100% sure it will work without problems, but if it did, your data will not be wiped.
I suggest you wait for someone else to answer coz I'm not expert. I only learned from guides in the telegram group.
Chenes said:
From what I read before, fastboot boot will only boot to that recovery file temporarily but I haven't tried it myself. It should be
Code:
fastboot flash recovery recovery.img
I'm not 100% sure it will work without problems, but if it did, you're data will not be wiped.
I suggest you wait for someone else to answer coz I'm not expert. I only learned from guides in the telegram group.
Click to expand...
Click to collapse
Can I have that Telegram group invite?
iOussamato_ said:
Can I have that Telegram group invite?
Click to expand...
Click to collapse
Realme 7 • Narzo 20 Pro • Global
Welcome To Realme 7 | Narzo 20 Pro Group • RM6785_updates(official-A12/A13)- @RM6785 / https://t.me/realme7updater • RM6785_Gaming- @RM6785Gaming • Realme 7 Cloud: @realme_7_cloud
t.me
iOussamato_ said:
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Sorry for a lot of questions, haha
Click to expand...
Click to collapse
You can try, first, if fastboot works in your device, type adb reboot fastboot, once the script ends, quickly disconnect device from your PC and again reconnect it, you will be redirected to fastboot, if the bootloader is unlocked, you could flash it using fastboot commands.
If you can´t get it to work then you can flash it using SPFT https://spflashtool.com/, put the recovery, in the same folder, with the attached files. All the sources to can use the tool, here https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
SubwayChamp said:
You can try, first, if fastboot works in your device, type adb reboot fastboot, once the script ends, quickly disconnect device from your PC and again reconnect it, you will be redirected to fastboot, if the bootloader is unlocked, you could flash it using fastboot commands.
If you can´t get it to work then you can flash it using SPFT https://spflashtool.com/, put the recovery, in the same folder, with the attached files. All the sources to can use the tool, here https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
Click to expand...
Click to collapse
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
iOussamato_ said:
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
Click to expand...
Click to collapse
Most of the custom roms I've seen requires formatting data. Just to be sure have you unlocked bootloader already? That requires wiping data iirc.
If not then nothing will really work with what you're doing.
iOussamato_ said:
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
Click to expand...
Click to collapse
What you are saying now is totally different from what you firstly posted.
Installing a custom ROM doesn't require a stock recovery (just in case you are confusing), and obviously, to can switch from a stock ROM to a custom ROM, that has a total different basement, it's mandatory to format data, anyway, you should back up your data previously to do so.
SubwayChamp said:
What you are saying now is totally different from what you firstly posted.
Installing a custom ROM doesn't require a stock recovery (just in case you are confusing), and obviously, to can switch from a stock ROM to a custom ROM, that has a total different basement, it's mandatory to format data, anyway, you should back up your data previously to do so.
Click to expand...
Click to collapse
I meant, I wish to install a custom ROM but I cannot install a working recovery and wanted the stock one. Sorry
Chenes said:
Most of the custom roms I've seen requires formatting data. Just to be sure have you unlocked bootloader already? That requires wiping data iirc.
If not then nothing will really work with what you're doing.
Click to expand...
Click to collapse
Yes my bootloader is already unlocked
iOussamato_ said:
Yes my bootloader is already unlocked
Click to expand...
Click to collapse
Then you can root your phone 1st then backup your files to a computer and use migrate backup to backup app data. Note that migrate backup is limited to 4gb. Then do the fastboot flash i mentioned before
iOussamato_ said:
I meant, I wish to install a custom ROM but I cannot install a working recovery and wanted the stock one. Sorry
Click to expand...
Click to collapse
Why you are saying that you cannot install a working recovery, I don't know of any attempt you did to achieve it.
A stock recovery is not needed to install a custom ROM, and even you can't install a custom ROM using a stock recovery.
If you want to join, flashing your device and stuff like this, better learn how to use SPFT, also you have this tool https://github.com/bkerler/mtkclient, this can save your device, if something in the process goes wrong.
SubwayChamp said:
Why you are saying that you cannot install a working recovery, I don't know of any attempt you did to achieve it.
A stock recovery is not needed to install a custom ROM, and even you can't install a custom ROM using a stock recovery.
If you want to join, flashing your device and stuff like this, better learn how to use SPFT, also you have this tool https://github.com/bkerler/mtkclient, this can save your device, if something in the process goes wrong.
Click to expand...
Click to collapse
I wanted to flash stock rom to downgrade into Realme UI 1.0 then flash the custom recovery so I can flash a custom rom
iOussamato_ said:
I wanted to flash stock rom to downgrade into Realme UI 1.0 then flash the custom recovery so I can flash a custom rom
Click to expand...
Click to collapse
OK, then what you are trying to install is an "old" Android 10 based ROM, if this is the case, then just download a stock Android 10 ROM, flash it through SPFT, then use SPFT to flash the custom recovery, transfer the custom ROM to your external SD Card (preferably) or sideload it, through recovery, and flash it. In the process you need to unlock bootloader, and immediately to flash the custom recovery, boot to it, using hardware buttons.
SubwayChamp said:
OK, then what you are trying to install is an "old" Android 10 based ROM, if this is the case, then just download a stock Android 10 ROM, flash it through SPFT, then use SPFT to flash the custom recovery, transfer the custom ROM to your external SD Card (preferably) or sideload it, through recovery, and flash it. In the process you need to unlock bootloader, and immediately to flash the custom recovery, boot to it, using hardware buttons.
Click to expand...
Click to collapse
Do you know a tutorial of how to use SPFlashTool?
iOussamato_ said:
Do you know a tutorial of how to use SPFlashTool?
Click to expand...
Click to collapse
How to use SP Flash Tool
This is a step-by-step tutorial on how to flash stock rom to a Mediatek device using Smart Phone Flash tool. SP Flash tool is one application you could find very useful in fixing extreme cases of a br
www.hovatek.com
Alright so, it might sound funny but I think I fixed it. I was playing with my downloaded recoveries until I downloaded the stock recovery, it is compatible but when I do fastboot reboot recovery I get stuck at Orange State for like 30min and it boots me into the recovery so does anyone know a solution for this? And thank you for everything and sorry for wasting y'all's time. Sincereley.
iOussamato_ said:
Alright so, it might sound funny but I think I fixed it. I was playing with my downloaded recoveries until I downloaded the stock recovery, it is compatible but when I do fastboot reboot recovery I get stuck at Orange State for like 30min and it boots me into the recovery so does anyone know a solution for this? And thank you for everything and sorry for wasting y'all's time. Sincereley.
Click to expand...
Click to collapse
You have to boot to recovery using hardware buttons (PWR + vol. down), in regard to orange state, this is absolutely normal when bootloader was unlocked, it's not an issue but a cosmetic thing.