[TOOL/UTILITY][TWRP][3.2][RECOVERY] TWRP 3.2.1-0 TeamWin Recovery Project

[ildar_prophet]

FYI... V3.0.0 is out. There are a couple of fixes that are in this. MTP and ADB should now work in recovery. Shout out to @bigbiff for fixing these things and to TWRP for all their hard work!

I can confirm MTP, but not ADB. Anyone?
For the ref: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1066

 

[FlyingHorseGA]

Any release notes for the latest 3.2.1-0 version?

 

[bigbiff]

Any release notes for the latest 3.2.1-0 version?

Please see https://twrp.me for release notes.

 

[ubigred]

I can't get TWRP to stick P900.

Please help!

---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------

I'm trying to use the latest TWRP. it's not sticking!

 

[thompatry]

I can't get TWRP to stick P900.

Please help!

---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------

I'm trying to use the latest TWRP. it's not sticking!

Are you following the exact instructions in the OP?

 

[h_93]

I can't seem to find version 3.2.1-0 for P905.
The latest version that is listed on the TWRP homepage is 3.0.2.
Where can I find the latest version?

 

[wilmaed]

The latest version that is listed on the TWRP homepage is 3.0.2.

The latest working version.
Newer avaiable versions got me into trouble

 

[Valholy]

Got a smp 900 what would be the steps to install this on my tab, already rooted.

 

[BenPreston]

Hi guys, wondering if anyone could help me. My note pro seems to only be able to go into download mode, but can't flash anything onto it with either Kies or Odin. Any suggestions?

 

[chooks06]

Hi guys, wondering if anyone could help me. My note pro seems to only be able to go into download mode, but can't flash anything onto it with either Kies or Odin. Any suggestions?

If the device is not detected by Odin when in download mode, could be a cable problem or the connecting port is dirty/faulty. Try another cable?

 

[BenPreston]

If the device is not detected by Odin when in download mode, could be a cable problem or the connecting port is dirty/faulty. Try another cable?

I did think that, however Odin or Kies can sometimes detect it. However, whenever I try to flash anything onto it, it fails. Thanks for the suggestion :good:

 

[chooks06]

I did think that, however Odin or Kies can sometimes detect it. However, whenever I try to flash anything onto it, it fails. Thanks for the suggestion :good:

If detection is intermittent, I'm more inclined to zero in on hardware. You can try using a micro USB cable to connect and see if connection is persistent. I do that when I can't find the USB 3 cable for the device.

Assuming relevant drivers have been installed and connection is good, maybe try flashing a stock ROM via Odin which will restore stock recovery image and the rest of everything else. I have encountered instances on other devices where the flashing failed cuz the flashed version was lower than what was previously in the device before it "died". It would show a prompt in the download screen in red when it failed but I can't remember what it was - something about SW binary..



Not accepting responsibility if this totally kills your device..

Good luck..

Edit - the cable problem could also lie at PC end.

 

[BenPreston]

If detection is intermittent, I'm more inclined to zero in on hardware. You can try using a micro USB cable to connect and see if connection is persistent. I do that when I can't find the USB 3 cable for the device.

Assuming relevant drivers have been installed and connection is good, maybe try flashing a stock ROM via Odin which will restore stock recovery image and the rest of everything else. I have encountered instances on other devices where the flashing failed cuz the flashed version was lower than what was previously in the device before it "died". It would show a prompt in the download screen in red when it failed but I can't remember what it was - something about SW binary..



Not accepting responsibility if this totally kills your device..

Good luck..

Edit - the cable problem could also lie at PC end.

Thanks for that. I have been trying to reflash stock with Odin, trying many different files I've found on the web. Always fails when flashing system, I was previously on a Lineage 14.1 ROM, would that cause any problems here? Just seems suspicious it always fails when flashing system. Thanks again

 

[chooks06]

Thanks for that. I have been trying to reflash stock with Odin, trying many different files I've found on the web. Always fails when flashing system, I was previously on a Lineage 14.1 ROM, would that cause any problems here? Just seems suspicious it always fails when flashing system. Thanks again

Take note what it says on the device screen when it fails.. If there's a red line entry at the notion mentioning something about binary mismatch then that's where the problem lies. The stock binary is lower than lineage 14.1. It will fail flashing, even stock ROM since there's no 7.1 for the device.

 

[BenPreston]

Take note what it says on the device screen when it fails.. If there's a red line entry at the notion mentioning something about binary mismatch then that's where the problem lies. The stock binary is lower than lineage 14.1. It will fail flashing, even stock ROM since there's no 7.1 for the device.

So would flashing TWRP and just re installing the rom I had before help, if I'm somehow able to do so using Odin?

 

[chooks06]

So would flashing TWRP and just re installing the rom I had before help, if I'm somehow able to do so using Odin?

I'm no expert but logic dictates that once you can install TWRP, any custom ROM can be flashed via recovery.

However, to get back to stock using Odin, I think may fail. I think it was on a galaxy S3 i had this problem. Accidentally solved it by using CF auto root. Using the corresponding Odin flashable file for the device, it flashed super SU and then restored the stock recovery. From there, I was able to flash the corresponding stock ROM version via Odin. But I'm not sure if this works for the Note pro.

From there, I could flash custom recovery again and the rest.

Not fully sure what's your situation and if this can work.

No promises, just sharing my experiences.

Hope somebody out there has a better solution if this doesn't work.

 

[BenPreston]

I'm no expert but logic dictates that once you can install TWRP, any custom ROM can be flashed via recovery.

However, to get back to stock using Odin, I think may fail. I think it was on a galaxy S3 i had this problem. Accidentally solved it by using CF auto root. Using the corresponding Odin flashable file for the device, it flashed super SU and then restored the stock recovery. From there, I was able to flash the corresponding stock ROM version via Odin. But I'm not sure if this works for the Note pro.

From there, I could flash custom recovery again and the rest.

Not fully sure what's your situation and if this can work.

No promises, just sharing my experiences.

Hope somebody out there has a better solution if this doesn't work.

Thank you. I have managed to get TWRP running again, so I can work it out myself from here!

 

[chooks06]

Thank you. I have managed to get TWRP running again, so I can work it out myself from here!

That's great! Best of luck mate!

 

[diehengardt]

Hi folks

Just to let you know I have succesfully flashed latest (asof 2018 November 1st) TWRP 3.2.3 on my Galaxy Note Pro 12.2 (a1wifi).

But in order to do so you need a pretty old odin, I used v3.0.9.
Do not use latest Odin v3.13.1 as the flash simply does not work even if it says 'scussefully flashed'.

nandroid backup in progress

 

[ildar_prophet]

Just to let you know I have succesfully flashed latest (asof 2018 November 1st) TWRP 3.2.3
...
But in order to do so you need a pretty old odin, I used v3.0.9.

Nice!
Does Heimdall work, did you try?