Unofficial TWRP 3.2.3-0 UA
F2FS Support
EFS & Persist backup support
Clean device tree
Based on Unlegacy-Android kernel
Regular updates
Known-issues
HTML:
- To be filled
Installation
HTML:
1. Go in fastboot mode (hold down Power + Vol down for few seconds.
# Or use flashers like Flasify/FlashFire and others
2. Open terminal window/command prompt to execute following commands:
fastboot erase recovery
fastboot flash recovery twrp_mako-3.2.3-0.img
3. With volume up and down select recovery mode and press power button
4. Enjoy your reboot in TWRP
Downloads:
Latest: AFH
Credits:
Special thanks to
- TWRP team
- Unlegacy-Android team
- Clamor
- And anyone I forgot to mention
Additional sources:
Kernel Sources: Github
TWRP Sources: Github
XDA:DevDB Information
Unofficial TWRP 3.2.3-0 UA, Tool/Utility for the Google Nexus 4
Contributors
sudokamikaze, clamor
Source Code: https://github.com/clamor95/android_device_unlegacy_recovery/tree/mako
Version Information
Status: Stable
Created 2018-08-16
Last Updated 2018-08-17
Thank you Sir for continuing support mako...
Have a stock Nexus 4.
Will be unlocking it and installing some ROM.
What is the difference between this and the official TWRP version?
Is this version of TWRP better than the official twrp-3.2.3-0-mako?
Thank you.
/root said:
Have a stock Nexus 4.
Will be unlocking it and installing some ROM.
What is the difference between this and the official TWRP version?
Is this version of TWRP better than the official twrp-3.2.3-0-mako?
Thank you.
Click to expand...
Click to collapse
Please, read OP post again. Our recovery has F2FS support for /data & /cache. EFS/Persist backup support, that means you can backup your IMEI/WIFI + BT Mac address stuff. And compare teamwin device tree and ours, I'm sure that you will be impressed
deleted
So should I format all partitions to f2fs and then install LOS? Is that advisable or should I just change filesystem for cache and data?
Edit 1 : btw Great recovery . I had to give it more than 2 tries though at first it got stuck in a bootloop of never entering the recovery page. then i flashed stock and tried again that time it couldn't format and twrp never got proceeded. did a stock flash again and the third time it worked fine.
Edit 2 : So checked the fstab of mako on LOS and it seems f2fs is only supported for /cache and /data. So only those two partitions need to be changed to f2fs format. Am I concluding it correctly?
Thank you @sudokamikaze
/root said:
So should I format all partitions to f2fs and then install LOS? Is that advisable or should I just change filesystem for cache and data?
Edit 1 : btw Great recovery . I had to give it more than 2 tries though at first it got stuck in a bootloop of never entering the recovery page. then i flashed stock and tried again that time it couldn't format and twrp never got proceeded. did a stock flash again and the third time it worked fine.
Edit 2 : So checked the fstab of mako on LOS and it seems f2fs is only supported for /cache and /data. So only those two partitions need to be changed to f2fs format. Am I concluding it correctly?
Thank you @sudokamikaze
Click to expand...
Click to collapse
About EDIT 1:
First of all I'm sorry about that, I will find why and which thing causing this.
I had something like that on friend's phone. But worked just fine after re-entering.
If rom which you decided to use supports f2fs - feel free to use that. Leave system as is
sudokamikaze said:
About EDIT 1:
First of all I'm sorry about that, I will find why and which thing causing this.
I had something like that on friend's phone. But worked just fine after re-entering.
If rom which you decided to use supports f2fs - feel free to use that. Leave system as is
Click to expand...
Click to collapse
Thank you, had no issues flashing and entering recovery and doing a full backup including EFS and Persist.
Otg compatible too?
is this support error digitiser/ nav bar ?
hakimarx said:
is this support error digitiser/ nav bar ?
Click to expand...
Click to collapse
You must check it yourself. Inactive surfaces can be of different widths.
You always have the option to return to the main menu by touching the TWRP logo.
ze7zez said:
You must check it yourself. Inactive surfaces can be of different widths.
You always have the option to return to the main menu by touching the TWRP logo.
Click to expand...
Click to collapse
Thanks..
Btw, please support TWRP multi OS for ubuntu touch
wizmart said:
Otg compatible too?
Click to expand...
Click to collapse
No, it's not compatible with OTG feature, and probably won't be either
Downloading stalled?
Hi. Newb here, been trying to search for an answer, but not sure what it is I'm needing to search for?
Issue is phone is unlocked and am in bootloader mode, and am trying to download above twrp but after entering the commands into my computer terminal, the computer terminal says " sending," and the phone says "downloading," but nothing is happening. Tried this a few times, and have actually left it for an hour, but no download?
Am I missing a step here? Followed the posted instructions.
Thanks for your patience.
toydriod said:
Hi. Newb here, been trying to search for an answer, but not sure what it is I'm needing to search for?
Issue is phone is unlocked and am in bootloader mode, and am trying to download above twrp but after entering the commands into my computer terminal, the computer terminal says " sending," and the phone says "downloading," but nothing is happening. Tried this a few times, and have actually left it for an hour, but no download?
Am I missing a step here? Followed the posted instructions.
Thanks for your patience.
Click to expand...
Click to collapse
Hmm, have you tried to switch USB cable or port or both? and what about official TWRP, same error?
You can try:
HTML:
fastboot erase recovery
fastboot flash recovery recovery.img # CHANGE HERE NAME OF FILE
sudokamikaze said:
Hmm, have you tried to switch USB cable or port or both? and what about official TWRP, same error?
You can try:
HTML:
fastboot erase recovery
fastboot flash recovery recovery.img # CHANGE HERE NAME OF FILE
Click to expand...
Click to collapse
Yes.
Tried
fastboot flash recovery openrecovery-twrp-2.3.2.3-mako.img Terminal says sending 'recovery' (8176 KB)... Phone says nothing
fastboot flash recovery openrecovery-twrp-2.8.5.2-mako.img Terminal says sending 'recovery' (9020 KB)... Phone says " downloading..."
toydriod said:
Yes.
Tried
fastboot flash recovery openrecovery-twrp-2.3.2.3-mako.img Terminal says sending 'recovery' (8176 KB)... Phone says nothing
fastboot flash recovery openrecovery-twrp-2.8.5.2-mako.img Terminal says sending 'recovery' (9020 KB)... Phone says " downloading..."
Click to expand...
Click to collapse
Then problem isn't in my recovery, reinstall drivers/switch pc/cable/port
sudokamikaze said:
Hmm, have you tried to switch USB cable or port or both? and what about official TWRP, same error?
You can try:
HTML:
fastboot erase recovery
fastboot flash recovery recovery.img # CHANGE HERE NAME OF FILE
Click to expand...
Click to collapse
sudokamikaze said:
Then problem isn't in my recovery, reinstall drivers/switch pc/cable/port
Click to expand...
Click to collapse
Thanks, I'm going to try it on another system.
toydriod said:
Thanks, I'm going to try it on another system.
Click to expand...
Click to collapse
FWIW Tried on another computer, and download worked fine. Thanks for you help and for making this.
I currently am on the official 3.1.xx TWRP version, can i just flash this as a zip from the current recovery? will that just replace the old one with this one, or do I need to first flash stock recovery?
Related
I made a mistake and did not turn on the debug mode. So when trying to unlock the bootloader using the tool here:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
it dint work. Now I keep getting "UTAG "flashfail" configured as fastboot" error. I have searched the forums and it seems I need to reflash the motorola boot img to get it to work.
Someone please help me out with it. I am on the latest 5.0.2 update for XT1068 - Indian version.
vicky_ag said:
I made a mistake and did not turn on the debug mode. So when trying to unlock the bootloader using the tool here:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
it dint work. Now I keep getting "UTAG "flashfail" configured as fastboot" error. I have searched the forums and it seems I need to reflash the motorola boot img to get it to work.
Someone please help me out with it. I am on the latest 5.0.2 update for XT1068 - Indian version.
Click to expand...
Click to collapse
ok download the boot.img and use mfastboot to flash
reefuge said:
ok download the boot.img and use mfastboot to flash
Click to expand...
Click to collapse
Links to the boot image please
vicky_ag said:
Links to the boot image please
Click to expand...
Click to collapse
heres a flashable zip if you have custom recovery, or just use the boot.img (5.0.2) from unzipped file
Code:
mfastboot.exe flash boot boot.img
That worked. But now having another issue
I have rooted a lot of phones but this is the first I am stumbling my way through it. I unlocked the bootloader by going to Motorola's site and then went ahead and tried to root the phone using the tool mentioned in original post.
So the tool pushes the boot.img and reboots the phone. Then even when the phones boots in TWRP, the computer keeps saying waiting for device.
Now when I try to do a normal boot, I get the warning from Motorola but then phone wont bootup. No matter how much I wait or even try to re-flash the above image.
vicky_ag said:
That worked. But now having another issue
I have rooted a lot of phones but this is the first I am stumbling my way through it. I unlocked the bootloader by going to Motorola's site and then went ahead and tried to root the phone using the tool mentioned in original post.
So the tool pushes the boot.img and reboots the phone. Then even when the phones boots in TWRP, the computer keeps saying waiting for device.
Now when I try to do a normal boot, I get the warning from Motorola but then phone wont bootup. No matter how much I wait or even try to re-flash the above image.
Click to expand...
Click to collapse
Please don't use mfastboot. It is known for having problems with latest Android versions. You can use Minimal adb and fastboot or the the latest Android SDK.
Next make sure you have flashed the latest TWRP 2.8.4.0.
Wipe everything in twrp. Cache, dalvik and data.
MTP is a bit messed up (not just on our devices). Go to mount, disable mtp, unmount everything, connect usb and enable MTP. Now your device should appear on your computers file manager.
One last thing. Unless you flash the latest SuperSU 2.4.5, stock Lollipop will automatically remove twrp and reinstall stock recovery on the next boot (Actually there is another way. But why would you want to install TWRP without rooting the phone).
doppelhelix said:
Please don't use mfastboot. It is known for having problems with latest Android versions. You can use Minimal adb and fastboot or the the latest Android SDK.
Next make sure you have flashed the latest TWRP 2.8.4.0.
Wipe everything in twrp. Cache, dalvik and data.
MTP is a bit messed up (not just on our devices). Go to mount, disable mtp, unmount everything, connect usb and enable MTP. Now your device should appear on your computers file manager.
One last thing. Unless you flash the latest SuperSU 2.4.5, stock Lollipop will automatically remove twrp and reinstall stock recovery on the next boot.
Click to expand...
Click to collapse
Oh. After many tries now I am stuck in a bootloop. The phones goes to the "warning" then reboots for 5-6 times before it actually starts up. So I am wondering what will be the correct way to go about rooting and clearing this mess. And I see only SuperSu 2.4.0 in play store. has there been a latest version?
vicky_ag said:
The phones goes to the "warning" then reboots for 5-6 times
Click to expand...
Click to collapse
That's because off the outdated SuperSU. Get the latest .zip here http://forum.xda-developers.com/showthread.php?p=23427715
doppelhelix said:
That's because off the outdated SuperSU. Get the latest .zip here http://forum.xda-developers.com/showthread.php?p=23427715
Click to expand...
Click to collapse
So I went this way. I installed the recovery using the tool mentioned in the op. Installed SuperSU latest. Still when I go to bootloader and try recovery, nothing happens. I booted up the phone to see if SuperSU is installed and it appears fine in the apps. But the recovery wont load no matter what.
Another strange thing even when I am connected on 3G, I am not getting the icon.
vicky_ag said:
So I went this way. I installed the recovery using the tool mentioned in the op. Installed SuperSU latest. Still when I go to bootloader and try recovery, nothing happens. I re-tried installing recovery, still no go.
Click to expand...
Click to collapse
Then how did you install SuperSU if you can't get into recovery?
doppelhelix said:
Then how did you install SuperSU if you can't get into recovery?
Click to expand...
Click to collapse
I got in the first time using the tool mentioned in the op. I checked and it uses the command:
fastboot.exe boot twrp.img
This causes the phone to boot into twrp and I can copy the SuperSU to install. But the recovery still doesn't work.
vicky_ag said:
I got in the first time using the tool mentioned in the op. I checked and it uses the command:
fastboot.exe boot twrp.img
This causes the phone to boot into twrp and I can copy the SuperSU to install. But the recovery still doesn't work.
Click to expand...
Click to collapse
What are you talking about. TWRP is the recovery.
---------- Post added at 10:08 ---------- Previous post was at 10:06 ----------
Oh sorry. Now I understand. Please use this commands:
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img
doppelhelix said:
What are you talking about. TWRP is the recovery.
Click to expand...
Click to collapse
Ok so this is what has happened:
1. I use the tool mentioned which uses the command:
fastboot.exe boot twrp.img
2. This causes the phone to boot into TWRP recovery. Then I installed SuperSU.
3. Rebooted the phone completely and checked the version of SuperSU.
4. Again went to the bootloader menu, selected TWRP. Nothing happens at this setup. phone doesn't boot at all. on clicking the power button it goes into normal boot
5. I tried going to the bootloader menu and running.
fastboot.exe flash recovery twrp.img
still no luck. Again trying to go from the bootloader menu to recoery yields no boot up.
vicky_ag said:
Ok so this is what has happened:
1. I use the tool mentioned which uses the command:
fastboot.exe boot twrp.img
2. This causes the phone to boot into TWRP recovery. Then I installed SuperSU.
3. Rebooted the phone completely and checked the version of SuperSU.
4. Again went to the bootloader menu, selected TWRP. Nothing happens at this setup. phone doesn't boot at all. on clicking the power button it goes into normal boot
5. I tried going to the bootloader menu and running.
fastboot.exe flash recovery twrp.img
still no luck. Again trying to go from the bootloader menu to recoery yields no boot up.
Click to expand...
Click to collapse
You are overriding the boot image with the recovery. The correct commands are
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img
doppelhelix said:
You are overriding the boot image with the recovery. The correct commands are
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Just tried that:
C:\fastboot>fastboot.exe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.496s]
writing 'boot'...
OKAY [ 0.438s]
finished. total time: 0.944s
C:\fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (9696 KB)...
OKAY [ 0.463s]
writing 'recovery'...
OKAY [ 0.433s]
finished. total time: 0.903s
Click to expand...
Click to collapse
Still when I go to the bootloader and select recovery, phone doesn't boot up at all.
vicky_ag said:
Just tried that:
Still when I go to the bootloader and select recovery, phone doesn't boot up at all.
Click to expand...
Click to collapse
Ok. Let's try this.
Can you boot normally into android? If so, please look if SuperSU is installed. If so, go to play store and install Android Terminal Emulator.
Open it and type
Code:
su
Supersu should pop up. Allow root.
Next type
Code:
reboot recovery
The device should boot into recovery. ( some people have this problem)
doppelhelix said:
Ok. Let's try this.
Can you boot normally into android? If so, please look if SuperSU is installed. If so, go to play store and install Android Terminal Emulator.
Open it and type
Code:
su
Supersu should pop up. Allow root.
Next type
Code:
reboot recovery
The device should boot into recovery. ( some people have this problem)
Click to expand...
Click to collapse
Thanks that works
vicky_ag said:
Thanks that works
Click to expand...
Click to collapse
Nice. Until you can go directly to the recovery, be very carefull not to leave the recovery without having flashed a rom and SuperSU. Also make sure that you grant adb access by accepting the RSA key when connecting the device with your computer. Just in case.
doppelhelix said:
Nice. Until you can go directly to the recovery, be very carefull not to leave the recovery without having flashed a rom and SuperSU. Also make sure that you grant adb access by accepting the RSA key when connecting the device with your computer. Just in case.
Click to expand...
Click to collapse
I am actually fine with a stock ROM on Motorola for now. They have lesser fluff than samsung et al. The major reason for trying to root the phone was to get TitanBackup working, I have been preserving some apps at a particular version in my last phone. The only way I found to restore the app and data was to use TitanBackup. The whole unlock the bootloader was because of Motorola adding a step to do this.
Adding recovery was an addition just in case Motorola forgets about us 1 year down the line. Then might flash to CM or something
Ok guys, this is a sureshot guide for
PROBLEM
* anyone wanting to decrypt their op3 but stuck at 1+ boot screen(Or not able to boot any custom ROMs.) and only able to restore twrp backups
* After using fastboot format userdata twrp and about phone shows only 32gb phone memory(where the hell is my rest of 32gb )
* Fastboot format userdata resulting in Stuck at boot screen or simply an unbrick trick to return to Stock OOS in unencrypted stage
SOLUTION
1. Use method 2 of Mega unbrick guide to restore your phone to stock partitions found here
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
2. After the flashing is complete do not reboot the phone instead reboot directly into bootloader.
3. In fastboot mode flash modded twrp 3.0.2.22 using command ''fastboot flash recovery recovery.img'' found here
http://forum.xda-developers.com/devdb/project/?id=15934#downloads
4. Reboot directly into twrp and using mtp mode copy latest elemental x kernel or bluspark kernel zip for OOS and SYSTEM supersu.zip into the internal storage. System supersu.zip here OR directly proceed to step 8
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
5. Now flash system supersu.zip and directly after that kernel.zip
6. Now again reboot to recovery directly and from twrp boot into system.
7. After boot up you system should be decrypted. You can check in security settings.
8.Reboot recovery and flash required firmware + modem zip found here
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
9.wipe data +cache +dalvik +system
10. Flash any rom of your choice and go flashoholic, use multirom or whatever you want.
Pheww. Thanks.
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Ashtrix said:
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Click to expand...
Click to collapse
anything... even multirom works flawless.
I will give this a try, Or will try to Flash the EX then perform parts of this since they support Kexec, to see what works, I have data and lot of apps working them again is a real pita with my schedule...
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
ach3fck said:
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
Click to expand...
Click to collapse
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
nikhilsnigam said:
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
Click to expand...
Click to collapse
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
ach3fck said:
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
Click to expand...
Click to collapse
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
nikhilsnigam said:
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
Click to expand...
Click to collapse
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
ach3fck said:
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
Click to expand...
Click to collapse
your bootloader doesn't get locked
nikhilsnigam said:
your bootloader doesn't get locked
Click to expand...
Click to collapse
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
ach3fck said:
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
Click to expand...
Click to collapse
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
nikhilsnigam said:
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
Click to expand...
Click to collapse
Yeah, i know that, thanks a lot, will try later all of this since i have no time now, will report how it went.Thanks!
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Anova's Origin said:
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Click to expand...
Click to collapse
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
ddaharu said:
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
Click to expand...
Click to collapse
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Anova's Origin said:
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Click to expand...
Click to collapse
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
ddaharu said:
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
Click to expand...
Click to collapse
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Anova's Origin said:
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Click to expand...
Click to collapse
One last question. Is there any twrp version you'll recommend? Or anyone is good?
ddaharu said:
One last question. Is there any twrp version you'll recommend? Or anyone is good?
Click to expand...
Click to collapse
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Anova's Origin said:
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Click to expand...
Click to collapse
MY PHONE IS RUNNING AGAIN! thanks for your help man.
Btw! Seeing that the positions were somewhat corrupted, I actually had to use stock recovery to sideload the stock ROM then flash TWRP and finally on freedom is 2.6.1
Thanks again, mate. :highfive:
ddaharu said:
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Click to expand...
Click to collapse
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
9891ishu said:
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
Click to expand...
Click to collapse
Thanks. I got through.
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.
Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?
rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can
Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.
Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and
customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to
mash. The GUI is also fully XML driven and completely theme-able. You can change just about
every aspect of the look and
Click to expand...
Click to collapse
Prerequisites:
Code:
. Unlocked Bootloader
Installation instructions:
Recovery Install Method:
Simply download the TWRP-3.5.1_10-0 from twrp website and flash it using fastboot mode, steps are mentioned below
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Download only the platform-tools according to your device to get adb and fastboot binaries.
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the zip file attached to this thread and copy the recovery.img file into the same folder as your adb and fastboot binaries and type:
Code:
fastboot flash recovery recovery.img
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Device Changelog
Version:3.5.1-10-0:
Initial Official Release
Click to expand...
Click to collapse
Version: 3.5.1_10-0-2:
Upstreamed to 3.5.1_10.0
Fixed issue related to fs of ext_media
Fixed issue related to format data
Click to expand...
Click to collapse
Version: 3.5.0_10-0-1:
Fixed Android 11 loop errors
Click to expand...
Click to collapse
Version: 3.5.0_10-0:
Initial Stable version
Fastbootd Mode Working Fine
Adb sideload Working Fine
A11 decryption working Fine
Nandroid Backup and Restore Working(not tested on miui)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads
Official TWRP Website
My Telegram TWRP Support Group:
Poco X2 | Recoveries
Recovery Support For Poco X2 Rules: 1. Dont spam 2. Be polite and help others 3. No Purn spam 4. English is recommended
t.me
Credits:
Huge thanks to @Captain_Throwback for his guidences
Sources
TWRP: https://github.com/TeamWin/android_bootable_recovery
Device Tree: https://github.com/TeamWin/android_device_xiaomi_phoenix
Kernel Tree: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/phoenix-q-oss
Status: Stable
TWRP: 3.5.1_10
Nice. Hope it go official soon
Has anybody tried this? Time zone settings, display time out setting, none of the settings are saving. It goes back to default after reboot. I installed the zip via older version of TWRP. I tried installing via Fastboot but it stuck on splash screen.
after formatting data and rebooting to recovery, copying files to device does not work. Internal storage does not show up. i have to reboot to system again to get copy to device working and get internal storage to show up again. this is a bug with every other twrp out there except the LR team one. Hope you fix this bug.
LEGACY710 said:
after formatting data and rebooting to recovery, copying files to device does not work. Internal storage does not show up. i have to reboot to system again to get copy to device working and get internal storage to show up again. this is a bug with every other twrp out there except the LR team one. Hope you fix this bug.
Click to expand...
Click to collapse
I have shared a new test build for that
Join the support group to test it
Hey, glad to see someone working on X2 TWRP again.
Normal versioning would be like 3.5.0_10-1 (then 3.5.0_10-2, etc.) not 3.5.0_10.0.1, by the way, but otherwise looking good over here!
osm0sis said:
Hey, glad to see someone working on X2 TWRP again.
Normal versioning would be like 3.5.0_10-1 (then 3.5.0_10-2, etc.) not 3.5.0_10.0.1, by the way, but otherwise looking good over here!
Click to expand...
Click to collapse
10.0.1 is just the incremental version by my side
HimanshuRaj said:
10.0.1 is just the incremental version by my side
Click to expand...
Click to collapse
Yeah normally the device-side increment is just the -1 or -2, etc. No worries though.
osm0sis said:
Yeah normally the device-side increment is just the -1 or -2, etc. No worries though.
Click to expand...
Click to collapse
Thankyou sir for telling me that, i wasn't knowing it,
Himanshu,
Does this twrp support android 11 rom flashing? And will it allow us to flash any phoenix roms on phoenixin phone?
Please make it official
AIDROOS said:
Himanshu,
Does this twrp support android 11 rom flashing? And will it allow us to flash any phoenix roms on phoenixin phone?
Click to expand...
Click to collapse
It supports android 11, only miui based on a11 is not supported yet
Yeh u can flash phoenix and phoenixin both
404fac said:
Please make it official
Click to expand...
Click to collapse
I don't know till how long i can maintain it, so i am not going for official,
And did official or unofficial matter ?
HimanshuRaj said:
I don't know till how long i can maintain it, so i am not going for official,
And did official or unofficial matter ?
Click to expand...
Click to collapse
For me it doesn't matter . . .
Installed it on Android 11..Internel storage shows 0
Mukit222 said:
Installed it on Android 11..Internel storage shows 0
Click to expand...
Click to collapse
Cuz it didn't support miui a11 rn
Hi, I have a poco x2(miui 12.1.2) and I'm looking to flash a custom rom. Can I use this safely? I'm new to all of this and I'd like to avoid bricking my phone by accident, If not, would you mind suggesting an alternative?
Mukit222 said:
Installed it on Android 11..Internel storage shows 0
Click to expand...
Click to collapse
Cuz of keymaster 4.1, it isn't supported by twrp as of now, but the team is working....
HimanshuRaj said:
Cuz of keymaster 4.1, it isn't supported by twrp as of now, but the team is working....
Click to expand...
Click to collapse
Eagerly Waiting ))
E:Unable to decrypt FBe device
help pls
I bought this phone in China,I think it is someting different from yours