Been running twrp 3.2.1-r1 for a while now with resurrection remix on my Perry. Today it fraged itself, so I decided to try the new 3.2.3 twrp. After booting it, it seemed to flash without issue. Upon reboot, it wouldn't load. I flashed the 3.2.1 twrp I tried flashing the ROM, but the data partition wouldn't take it. I discovered that the partition size was 0. I fixed the partition size, and flashed the ROM. Everything seems to be fine, except booting. The phone defaults to twrp instead of booting the ROM. I have to reboot to boot loader, the click start to get the ROM to load. Not critical, but VERY annoying. Any help resolving this is appreciated. Thanks
Tried the fastboot OEM fb_mode_clear command, which flashes, but no change. Tried the adb wipe /misc partition, which returns invalid file.
HigherStateD said:
Been running twrp 3.2.1-r1 for a while now with resurrection remix on my Perry. Today it fraged itself, so I decided to try the new 3.2.3 twrp. After booting it, it seemed to flash without issue. Upon reboot, it wouldn't load. I flashed the 3.2.1 twrp I tried flashing the ROM, but the data partition wouldn't take it. I discovered that the partition size was 0. I fixed the partition size, and flashed the ROM. Everything seems to be fine, except booting. The phone defaults to twrp instead of booting the ROM. I have to reboot to boot loader, the click start to get the ROM to load. Not critical, but VERY annoying. Any help resolving this is appreciated. Thanks
Tried the fastboot OEM fb_mode_clear command, which flashes, but no change. Tried the adb wipe /misc partition, which returns invalid file.
Click to expand...
Click to collapse
TW RP is not clearing the BCB correctly. The boot loader control block. I'll post the commands you need to fix it in a minute when I pull over. Driving right now
---------- Post added at 01:40 AM ---------- Previous post was at 01:37 AM ----------
This version of TWRP is not reading and clearing the bootloader control block (BCB). So, if you do a factory reset via Settings->Backup & Reset->Factory Data Reset, you'll be stuck in a TWRP bootloop.
The quick workaround is to reboot to bootloader, then proceed from there to Start. However, you'll need to do this *every* time until the BCB is cleared.
To clear the BCB manually, issue this command in TWRP terminal:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M
The quick workaround is to reboot to bootloader said:
Thanks for the reply. I tried the command to zero out misc, it returns misc not found, which is of, as I can clearly see the file in an ls file list.
Click to expand...
Click to collapse
Got it by CD to the dir misc is located then executing the following: dd if=/dev/zero of=misc
Could use some help flashing the latest twerp, but since no ROMs need the added 64 bit support, I don't see it as necessary yet.
HigherStateD said:
Got it by CD to the dir misc is located then executing the following: dd if=/dev/zero of=misc
Could use some help flashing the latest twerp, but since no ROMs need the added 64 bit support, I don't see it as necessary yet.
Click to expand...
Click to collapse
The old twrp has the same issue. Just go ahead and Flash the new one. It's just a problem that May come up when you format or if you do a factory reset
madbat99 said:
The old twrp has the same issue. Just go ahead and Flash the new one. It's just a problem that May come up when you format or if you do a factory reset
Click to expand...
Click to collapse
Tried flashing the new twrp from within the old one. I get a kernel error when trying to load after successful flash.
HigherStateD said:
Tried flashing the new twrp from within the old one. I get a kernel error when trying to load after successful flash.
Click to expand...
Click to collapse
Are you flashing it to the recovery partition? Try flashing it with Flashify. but it should work if you choose select install image in TWRP and select the recovery partition.
madbat99 said:
Are you flashing it to the recovery partition? Try flashing it with Flashify. but it should work if you choose select install image in TWRP and select the recovery partition.
Click to expand...
Click to collapse
Yes.. Phone boots fine. Only issue is with recovery. New twrp flashed either in twrp or fastboot generates kernel error. After flashing old twrp, recovery works fine
HigherStateD said:
Yes.. Phone boots fine. Only issue is with recovery. New twrp flashed either in twrp or fastboot generates kernel error. After flashing old twrp, recovery works fine
Click to expand...
Click to collapse
Which version of the E4 do you have?
madbat99 said:
Which version of the E4 do you have?
Click to expand...
Click to collapse
XT1765 by metro
HigherStateD said:
XT1765 by metro
Click to expand...
Click to collapse
I've seen other people with the Metro version and the T-Mobile one which have the same model number and it works fine for them. Don't know exactly why it's not working for you I sse you resized some partitions and had trouble clearing the BCB. So you may have done some other things that I don't know about. All I can say is that if the previous version was working you should stick with that one.
madbat99 said:
I've seen other people with the Metro version and the T-Mobile one which have the same model number and it works fine for them. Don't know exactly why it's not working for you I sse you resized some partitions and had trouble clearing the BCB. So you may have done some other things that I don't know about. All I can say is that if the previous version was working you should stick with that one.
Click to expand...
Click to collapse
I tried to flash the 3.2.3 after my system went into a boot loop for an unknown reason. I was able to eventually clear the BCB with a modified command in the twrp terminal. Is there a way of checking the size of the recovery partition? I'm thinking the added 4~MB of the 3.2.3 twrp might be causing an issue. Perhaps overrunning the size of the partition. Can't think of any other reason it wouldn't work.
HigherStateD said:
I tried to flash the 3.2.3 after my system went into a boot loop for an unknown reason. I was able to eventually clear the BCB with a modified command in the twrp terminal. Is there a way of checking the size of the recovery partition? I'm thinking the added 4~MB of the 3.2.3 twrp might be causing an issue. Perhaps overrunning the size of the partition. Can't think of any other reason it wouldn't work.
Click to expand...
Click to collapse
I flashed it on mine no problem. the recovery partition is bigger than it needs to be. Don't go messing around changing partition sizes or you're asking for trouble.
Related
I've changed my password on the 6P (running Cyanogenmod), and ever since then, I can't enter my TWRP recovery, because it can't decrypt anymore. I've tried both the old and the new password in TWRP, but it can't decrypt it. Booting normally into the OS with the new password works fine, just not for TWRP.
TL;DR: Changed password in Cyanogenmod on encrypted 6P, now can't enter TWRP recovery anymore, but can still enter the phone OS.
Any ideas? Perhaps I could somehow reflash TWRP without losing data? Or will this mess up the encryption even more, so that I possibly also couldn't enter the OS anymore?
jb91 said:
I've changed my password on the 6P (running Cyanogenmod), and ever since then, I can't enter my TWRP recovery, because it can't decrypt anymore. I've tried both the old and the new password in TWRP, but it can't decrypt it. Booting normally into the OS with the new password works fine, just not for TWRP.
TL;DR: Changed password in Cyanogenmod on encrypted 6P, now can't enter TWRP recovery anymore, but can still enter the phone OS.
Any ideas? Perhaps I could somehow reflash TWRP without losing data? Or will this mess up the encryption even more, so that I possibly also couldn't enter the OS anymore?
Click to expand...
Click to collapse
Flashing the recovery even 'n' number of times won't do any bad to the ROM. It seems like an issue with decryption itself. If you don't bother backing up and restoring your data, I would advise you to decrypt the complete partition manually.
DJBhardwaj said:
Flashing the recovery even 'n' number of times won't do any bad to the ROM. It seems like an issue with decryption itself. If you don't bother backing up and restoring your data, I would advise you to decrypt the complete partition manually.
Click to expand...
Click to collapse
How can I decrypt it? And normally I backup a nandroid, but I can't do that now because I can't enter the recovery, or is there another way?
jb91 said:
How can I decrypt it? And normally I backup a nandroid, but I can't do that now because I can't enter the recovery, or is there another way?
Click to expand...
Click to collapse
The process will not wipe the ROM, but all the apps and data. Since your data is encrypted, I am not sure if Nandroid will work, backing up the /data partition. You can give a try to Flashfire app, to backup your parition data though.
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
About decryption, you can reboot into bootloader, and enter the following commands consecutively.
Code:
fastboot format userdata
fastboot reboot
jb91 said:
I've changed my password on the 6P (running Cyanogenmod), and ever since then, I can't enter my TWRP recovery, because it can't decrypt anymore. I've tried both the old and the new password in TWRP, but it can't decrypt it. Booting normally into the OS with the new password works fine, just not for TWRP.
TL;DR: Changed password in Cyanogenmod on encrypted 6P, now can't enter TWRP recovery anymore, but can still enter the phone OS.
Any ideas? Perhaps I could somehow reflash TWRP without losing data? Or will this mess up the encryption even more, so that I possibly also couldn't enter the OS anymore?
Click to expand...
Click to collapse
What version of TWRP are you using? There is an issue with decryption on version 3.0.1-0. See here: http://forum.xda-developers.com/nex...y-twrp-2-8-7-0-touch-recovery-t3234976/page83
Solution seems to be use the previous version 3.0.0-1.
garrettsessions said:
What version of TWRP are you using? There is an issue with decryption on version 3.0.1-0. See here: http://forum.xda-developers.com/nex...y-twrp-2-8-7-0-touch-recovery-t3234976/page83
Solution seems to be use the previous version 3.0.0-1.
Click to expand...
Click to collapse
Holy ****, I actually did update to the latest TWRP the other day. If this will be this simple to fix, that would be really great. I'm not sure how to flash the older TWRP now though. I used to always just download the TWRP img file on my phone directly, then install it directly within TWRP itself, to update TWRP. Now that I can't enter TWRP because it's unable to decrypt, I have no idea how to flash the old TWRP version. Is there an adb command so I can flash this from my PC?
EDIT: It worked! Thank you so much! I downgraded to the TWRP 3.0.0.1 with ADB and it decrypted again without any problems. You possibly spared me hours of setting up everything from scratch again.
jb91 said:
Holy ****, I actually did update to the latest TWRP the other day. If this will be this simple to fix, that would be really great. I'm not sure how to flash the older TWRP now though. I used to always just download the TWRP img file on my phone directly, then install it directly within TWRP itself, to update TWRP. Now that I can't enter TWRP because it's unable to decrypt, I have no idea how to flash the old TWRP version. Is there an adb command so I can flash this from my PC?
Click to expand...
Click to collapse
Fastboot is used to flash/modify partitions on Android devices.
Have a look at this thread: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
jb91 said:
Holy ****, I actually did update to the latest TWRP the other day. If this will be this simple to fix, that would be really great. I'm not sure how to flash the older TWRP now though. I used to always just download the TWRP img file on my phone directly, then install it directly within TWRP itself, to update TWRP. Now that I can't enter TWRP because it's unable to decrypt, I have no idea how to flash the old TWRP version. Is there an adb command so I can flash this from my PC?
Click to expand...
Click to collapse
If you are rooted, download the 3.0.0-1 version and flash with Flashfire or Flashify. I'm sure there's an adb command, but I always install through fastboot.
Hello everyone,
i just flashed the newest Pure Nexus Rom and everything went fine.
I forgot to flash the SuperSU Zip so i tried to got back into TWRP, but now it stuck.
The System boots normally, only TWRP wont boot.
Anyone had that problem too?
if anyone else has the same issue, here is the answer:
I forgot to erase the userdata or cache.
If you have the same problem use fastboot!
fastboot format cache
fastboot format userdata
Then it should work again.
(Everything on your own risk)
If you dont flah SuperSU asap, TWRP will not stick on reboot (w nougat). That was the issue.
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
Exactly. It happened before you flashed SuperSU zip. Not flashing SuperSU caused your problem. It needs to be flashed the first time you go into TWRP or you won't be able to boot back into TWRP. The previous poster is correct.
Maybe we talk about different problems
Ive formatted cache and userdata yesterday,
now i can go back into twrp.
(SuperSU is not flashed now).
Just tried it, works perfectly!
kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
I never, ever flash userdata, and never had an issue.
We can agree to disagree. Either the other poster and I arent understanding your question, or you arent understanding our reply. It's cool, it happens.
But TWRP not sticking is due to not running SuperSU at the end of the install process. It wont stick.
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
kaufikauf said:
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
Click to expand...
Click to collapse
You should take a look at this post in the official TWRP thread for a clearer reason why.
SlimSnoopOS said:
You should take a look at this post in the official TWRP thread for a clearer reason why.
Click to expand...
Click to collapse
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
USFguy said:
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
Click to expand...
Click to collapse
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
USFguy said:
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
Click to expand...
Click to collapse
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Tried that, ended up going down an update in TWRP and it worked, weird....
I had a similar issue and I had to go back in and reflash Recovery image to recovery partition and all was well
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.
android_101_ said:
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.
Click to expand...
Click to collapse
I only have the Twrp recovery.
Canukboy said:
I only have the Twrp recovery.
Click to expand...
Click to collapse
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?
wang1chung said:
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?
Click to expand...
Click to collapse
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.
Canukboy said:
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.
Click to expand...
Click to collapse
Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.
Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.
Click to expand...
Click to collapse
Hy Wang.. I followed your guide - modified updater-script, but I can't install the stock rom .zip from TWRP.
It says "can't extract updater-binary", I tried few times thinking that the file is corrupt, but the result still same.
FYI, I use stock ROM "UL-ASUS_Z012D-WW-14.2020.1709.68-user.zip", and TWRP 3.1.1.
Please help me if you have experienced it before. Thanks
@rzahunn
I've never had that error before and you're on the latest version of TWRP so I'm going to guess it has to do with your modification of the updater script.
You edited updater-script not updater-binary, correct? There are two files with similar names
There's a detailed guide by @kyle_l88 on how to return to stock.
Here's the link: https://forum.xda-developers.com/zenfone-3/development/how-to-to-stock-rom-recovery-zenfone-3-t3666223
Do note that the original recovery link is dead. The updated link is: https://mega.nz/#F!LIhwiCia!b_pyuHXS9E7f2VbyXcLyXA
TWRP Bootloop
Sorry if my reply is irrelevant, but I need some helps.
I am also using Zenfone 3, but stuck in TWRP bootloop.
I cannot flash using fastboot (not detected on PC), reflashing ROM doesn't help either.
I've tried all the possible methods I found on Google, such as dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota method but still has no luck.
Restoring backup would end me in TWRP too.
@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.
wang1chung said:
@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.
Click to expand...
Click to collapse
I've managed to fix the bootloop after following the guide. I missed that somehow, thanks for pointing that to me.
I've thanked you (pressed the Thanks button).
dm verity
Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
does it hangs on logo then start again? then reflashing the rom then flashing the dm verity zip again hope it works
Very stupid question. ive never had a A/B device before so how would i go about flashing twrp and a custom rom with the 2 partitions
TWRP installer, installs to both A and B [emoji6]
---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------
If you read the log as it is flashing you should see it being flashed to both.
Sobreally it's just the same as before
What version of TWRP are you using? The latest?
RevTheory said:
Very stupid question. ive never had a A/B device before so how would i go about flashing twrp and a custom rom with the 2 partitions
Click to expand...
Click to collapse
It's not stupid at all actually. I've been having the same question and concerns myself regarding the A/B partition slot setup and would love a descriptive tutorial on the differences between this and prior OP devices when it comes to flashing/installing custom ROMs, mods and other zip files.
RevTheory said:
Very stupid question. ive never had a A/B device before so how would i go about flashing twrp and a custom rom with the 2 partitions
Click to expand...
Click to collapse
Daskalman said:
It's not stupid at all actually. I've been having the same question and concerns myself regarding the A/B partition slot setup and would love a descriptive tutorial on the differences between this and prior OP devices when it comes to flashing/installing custom ROMs, mods and other zip files.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
When I reboot recovery after flashing a new rom and also flashing TWRP again (newest version), why are all my files "missing" and replaced with a bunch of weird looking files? Mind you, when I boot system and then go back to recovery, all the proper files are showing again.
Right now I flashed a new rom and TWRP and rebooted recovery and then tried to boot into system, but it keeps booting back to recovery and isn't showing my proper files, so I can't fix by flashing something else or using one of my backups.
Lochman79 said:
When I reboot recovery after flashing a new rom and also flashing TWRP again (newest version), why are all my files "missing" and replaced with a bunch of weird looking files? Mind you, when I boot system and then go back to recovery, all the proper files are showing again.
Right now I flashed a new rom and TWRP and rebooted recovery and then tried to boot into system, but it keeps booting back to recovery and isn't showing my proper files, so I can't fix by flashing something else or using one of my backups.
Click to expand...
Click to collapse
The same is happening to me trying to flash the latest OOS I'm on slot a, I flash the Magisk uninstaller, then OOS, then TWRP installer.. when I boot back to TWRP everything is just a garbled mix of file names.. I go to the reboot menu and select boot from "a" slot, and it's back to normal... Haven't tried anything else, still getting used to the whole a/b partition thing..
That is nice though, if the flash doesn't work, just go into recovery and boot from the other slot and it's the device as it was before flashing...
I also want to say if you wipe data it should boot.. if that doesn't work, you can format data in twrp.. clears your internal storage but it should boot...
This thread is not pirated, mirrored or copy of official twrp
I'm just sharing the official TWRP 3.6.0_9-0 patched boot img for Stock Android 10, 11 & Custom ROMs
Whats Working?
Everything
Whats Not Working?
Encryption/Decryption of Data
Download
Unofficial TWRP 3.6.0_9-0 IMG for Stock Android 10, 11 & Custom ROMs
https://androidfilehost.com/?fid=17825722713688272934
Official TWRP 3.6.0_9-0 IMG for Stock Android 9 only
https://dl.twrp.me/laurel_sprout/twrp-3.6.0_9-0-laurel_sprout.img.html
Official TWRP Installer 3.6.0_9-0 ZIP for Stock Android 9, 10 & Custom ROMs
https://dl.twrp.me/laurel_sprout/twrp-installer-3.6.0_9-0-laurel_sprout.zip.html
Note: enable "use rm -rf instead of formatting" in TWRP settings, before you wipe data, else userdata partition will be ****ed
Hit thanks button if you liked my work
Reserved
Deleted
Will this be able to format data on Android 10 encryption like SHRP?
Flashed it from fastboot but doesn't come ,only comes fastboot mode ?
Only Sharp works in 10 properly.
Sami Devo said:
Flashed it from fastboot but doesn't come ,only comes fastboot mode ?
Only Sharp works in 10 properly.
Click to expand...
Click to collapse
Your not doing it right because everyone else is able to install all recoveries it's only you who is having these issues. Without a proper bug report nobody can help you though
Rajendran Rasa said:
This thread is not pirated, mirrored and copy the official twrp
I'm just sharing the official TWRP 3.4.0-0 patched img of Android 10
Unofficial TWRP 3.4.0-0 for Android 10
https://androidfilehost.com/?fid=8889791610682878366
Official twrp-3.4.0-0 for Android 9
https://dl.twrp.me/laurel_sprout/twrp-3.4.0-0-laurel_sprout.img.html
Official twrp-installer-3.4.0-0 for Android 9&10
https://dl.twrp.me/laurel_sprout/twrp-installer-3.4.0-0-laurel_sprout.zip.html
Note: enable "use rm -rf instead of formatting" in TWRP settings, before you wipe data, else userdata partition will be damaged
Hit thanks button if you liked my work?
Click to expand...
Click to collapse
Which one should I download? unofficial?
hello, i have this noob question:
i have 4 year flashing twrp and roms... but i'm new with this device and its slotA slotB issue (fastboot boot loop)...
please OP, can you tell us the tutorial of how install correctly the official twrp? i saw videos on youtube but none has this 3.4.0 version.
thank you very much for your hard work, i really apreciatte it.
and thanks in advance for your comments.
garylawwd said:
Your not doing it right because everyone else is able to install all recoveries it's only you who is having these issues. Without a proper bug report nobody can help you though
Click to expand...
Click to collapse
Oops sorry it was orange fox.!! It has problem!
"........else userdata partition will be damaged"
what does it mean??....I will lost my data???...or phone can be bricked??.....what can happen exctly??
ovi2901 said:
"........else userdata partition will be damaged"
what does it mean??....I will lost my data???...or phone can be bricked??.....what can happen exctly??
Click to expand...
Click to collapse
It just won't boot. You can still recover from this by enabling the setting in twrp and reformatting data.
You will lose data regardless of this being enabled because this is only used for formatting data. That's what formatting data does
garylawwd said:
It just won't boot. You can still recover from this by enabling the setting in twrp and reformatting data.
You will lose data regardless of this being enabled because this is only used for formatting data. That's what formatting data does
Click to expand...
Click to collapse
can I install shrp recovery zip and then miui12...
what I will do is -->
1. install this recovery in b slot through minimal adb
2. boot in twrp
3. install shrp recovery zip file (phone is still in b-slot)
4. change slot to a
5. reboot recovery
6. format data
7. install miui12
8. reboot
will this steps safely boot my device???
hello. first thank you very much for your hard work. i really apreciate.
so, i was on stock rom, freshly unlock the bootloader and flash twrp unofficial for android 10.
then in twrp i flash the zip installer and reboot to recovery.
once again in twrp i, like i'm use to, wipe successfully dalvik/system/data to erased all of stock rom.
then i format data (the one typing "yes" for confirmation) but it broke internal storage.
twrp does not show any file or folders. i rebooti in recovery but it won't show anything
i reflash twrp and the same... nothing.
so i went to fastboot mode and flash shrp, boot up in recovery but it was still not showing files or folders of internal storage. i wipe dalvik/system/data and reboot to recovey.
and this time it show folder but with codes like "QRGHQ9R4HGVUQE4RNG98TH9324HTG923" OR "66EFQ3KFK4TK34KT3K4K34K2KK2" and so...
what do i 'm doing wrong?
can i format data with out breaking internal storage?
the only thing i can do to get internal storage was flash stock rom again, i have not encrypted anything, i don't use microsd card, even i don't use password to unlock screen.
thanks in advance for your comments.
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
ovi2901 said:
can I install shrp recovery zip and then miui12...
Click to expand...
Click to collapse
this it twrp thread bro
d_g_m_2000 said:
hello. first thank you very much for your hard work. i really apreciate.
so, i was on stock rom, freshly unlock the bootloader and flash twrp unofficial for android 10.
then in twrp i flash the zip installer and reboot to recovery.
once again in twrp i, like i'm use to, wipe successfully dalvik/system/data to erased all of stock rom.
then i format data (the one typing "yes" for confirmation) but it broke internal storage.
twrp does not show any file or folders. i rebooti in recovery but it won't show anything
i reflash twrp and the same... nothing.
so i went to fastboot mode and flash shrp, boot up in recovery but it was still not showing files or folders of internal storage. i wipe dalvik/system/data and reboot to recovey.
and this time it show folder but with codes like "QRGHQ9R4HGVUQE4RNG98TH9324HTG923" OR "66EFQ3KFK4TK34KT3K4K34K2KK2" and so...
what do i 'm doing wrong?
can i format data with out breaking internal storage?
the only thing i can do to get internal storage was flash stock rom again, i have not encrypted anything, i don't use microsd card, even i don't use password to unlock screen.
thanks in advance for your comments.
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
this it twrp thread bro
Click to expand...
Click to collapse
Ok you performed Format > And type "Yes" , actually this will Format your internal storage as well, RIP for your Data now else you took a backup earlier.
Now connect your phone to your PC with data cable , in mount section check if MTP is enabled if not then enable it , now your phone's internal storage shows in PC transfer Rom flash Zip files to internal storage, disconnect from PC and flash that rom.
Recovery choice is yours SHRP or TWRP
Note - Do not perform format > yes before flashing that zip.
Sent from my Mi A3 using Tapatalk
Not able to flash recovery
I am on the latest stock android patch, probably that's why not able to flash recovery.
First I tried TWRP 3.3.1-2 Unofficial by Nikesh Kataria from the other post. As it said it supported android 10 with decryption and everything. But it didn't work.
Now with version 3.4.0-0, I am able to boot into recovery using platform-tools. But the files in /sdcard seems to be encrypted (judging by the codes shown instead of readable folder names).
Could someone please help me suggest any recovery which supports latest stock android 10 with decryption?
Is there a way around this?
https://drive.google.com/file/d/1TcRxuBUde9chk3MWbvFWhUuojS-iZ8x2/view?usp=sharing
Thanks in advance!
Themane said:
I am on the latest stock android patch, probably that's why not able to flash recovery.
First I tried TWRP 3.3.1-2 Unofficial by Nikesh Kataria from the other post. As it said it supported android 10 with decryption and everything. But it didn't work.
Now with version 3.4.0-0, I am able to boot into recovery using platform-tools. But the files in /sdcard seems to be encrypted (judging by the codes shown instead of readable folder names).
Could someone please help me suggest any recovery which supports latest stock android 10 with decryption?
Is there a way around this?
https://drive.google.com/file/d/1TcRxuBUde9chk3MWbvFWhUuojS-iZ8x2/view?usp=sharing
Thanks in advance!
Click to expand...
Click to collapse
Decryption will only work if you format data first. This is with every recovery. Has to be a factory reset of stock ROM or fresh install of custom ROM and from then twrp will be able to decrypt if it is installed, you're not installing it either by the way just temporarily installing it to inactive slot which will get wiped on reboot. For twrp to decrypt you must install it using the installer.zip by flashing it in you're temporarily installed twrp.img
garylawwd said:
Decryption will only work if you format data first. This is with every recovery. Has to be a factory reset of stock ROM or fresh install of custom ROM and from then twrp will be able to decrypt if it is installed, you're not installing it either by the way just temporarily installing it to inactive slot which will get wiped on reboot. For twrp to decrypt you must install it using the installer.zip by flashing it in you're temporarily installed twrp.img
Click to expand...
Click to collapse
Thanks for the help.
But after booting into twrp, how do I install twrp.zip. I even tried sideload that also errors out "Unable to find partition for path /cache".
May be I am missing some step. But here is what I have done.
Unlocked bootloader.
Booted into TWRP on inactive_slot(i.e. slot_b , in my case) with command fastboot flash boot twrp.img
Trying to install twrp.zip (failing at this step itself).
Themane said:
Thanks for the help.
But after booting into twrp, how do I install twrp.zip. I even tried sideload that also errors out "Unable to find partition for path /cache".
May be I am missing some step. But here is what I have done.
Unlocked bootloader.
Booted into TWRP on inactive_slot(i.e. slot_b , in my case) with command fastboot flash boot twrp.img
Trying to install twrp.zip (failing at this step itself).
Click to expand...
Click to collapse
Put the zip on an SD card
Some ROM has some recovery integrated within the OS. If i install that and then the ROM, will the ROM's recovery overwrite this?
mihovkris said:
Some ROM has some recovery integrated within the OS. If i install that and then the ROM, will the ROM's recovery overwrite this?
Click to expand...
Click to collapse
Yes
Flash twrp installer zip after flashing rom zip