Develop Bugs

[Q] which TWRP?

Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.

redheadplantguy said:
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
Click to expand...
Click to collapse
most stable version would be 2.6.3.3

buhohitr said:
most stable version would be 2.6.3.3
Click to expand...
Click to collapse
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.

redheadplantguy said:
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
Click to expand...
Click to collapse
the version I stated is most stable, other twrp version may cause cache corruption and other issues.

buhohitr said:
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
Click to expand...
Click to collapse
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.

redheadplantguy said:
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
Click to expand...
Click to collapse
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.

buhohitr said:
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
Click to expand...
Click to collapse
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?

redheadplantguy said:
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
Click to expand...
Click to collapse
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/

Hi,
This post saved me, I installed TWRP 2.8 and my system froze, I couldn't get past the Samsung 10.1 screen.
But found this post and flashed 2.6.3.3 via Odin and it all went smoothly.
PS Goo.img.com dosen't have the files anymore

buhohitr said:
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Click to expand...
Click to collapse
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?

redheadplantguy said:
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
Click to expand...
Click to collapse
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.

Is 2.6.3.3 more reliable / stable in terms of making / restoring nandroids? I just got my new Note last week (p607t) and flashed xKat with TWRP at one point, restoring apps from (some with data to avoid re-entering account info or redoing complex settings...) I have had one problem however, when I was almost done restoring, I noticed that I was getting fc's, particularly with games that required an internet connection. I wiped dalvik and cache in TWRP, then hit fix permissions, which I think screwed everything up (maybe due to the bootloader / firmware base mismatch). Anyway, my most recent nandroid was with the fresh xKat install, but fixing permissions caused this weird "hot"-bootloop where it skipped the boot animation but start loading immediately after rebooting, but then freezing before all boot tasks had completed (ex. some optimizations on boot with Android Tuner Pro, FolderMount mounting folders, loading xposed modules...)
Not wanting to re-restore, I first just tried dirty-flashing the ROM again (only wiped dalvik and cache, but did something I hadn't tried before: in the wipe menu I hit "repair partition" for system and data, pre-flash). Luckily it worked and set everything straight... but just want to make sure, 2.6.3.3 is still recommended as the most stable version (in my experience, fixing permissions in recovery can be very hit or miss on any version)?
2 questions before I roll back my recovery, I think these "killer features" (totally serious, #2 has been huge since I got a couple of the newish flash drives with micro usb on one side and regular usb on the other) of TWRP were implemented in 2.6.3.3, but just want to make sure: can you 1) compress nandroids and 2) mount a USB OTG drive and flash from or backup to it? Thanks all, really loving my new Note (massive upgrade from my Note 8!)

buhohitr said:
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Click to expand...
Click to collapse
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.

redheadplantguy said:
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
Click to expand...
Click to collapse
How about wipe cache/davikcache/data with your stock recovery (just reflash your stock recovery). After that let it boot up, then power down and flash twrp. Once done, don't boot up, boot back to twrp . Let me know how it goes.

Cool. I can try that when I get home. Do you have a link handy for the stock recovery?

redheadplantguy said:
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
Click to expand...
Click to collapse
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.

buhohitr said:
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
Click to expand...
Click to collapse
THANK YOU SO MUCH! TWRP booted right up, and nandroid in progress. now I'll be able to try some custom ROM's and play in system.
:laugh:

SOLVED

Hello,
It sure has been a while since I've posted in this forums. I am having some trouble on my phone. Here's the story: I was on MIUI 7, but didn't like the way it was handling memory. It kept closing apps even when there were only 3 running, so I decided to restore a previous CM backup. So, I did that and rebooted the phone. It gave an error saying that "Encryption was interrupted", yet I have never encrypted my phone. Anyway, I decided to flash CM12 with a zip I had. Rebooted, and same problem occurred. Now, I'm trying to reboot phone into recovery, but whenever I do, the screen goes black and re-displays the teamwin logo, and just does that over and over. I tried flashing recovery through fastboot, but same problem. Is my phone savable? It should be, as it isn't hard-bricked. Any help is appreciated!

How do you solve this problem? When I flash CM12, the phone repeat reboot and can't enter recovery. At last I flash the Omini ROM.

Just flash stock rom
flash stock recovery.. go to wipe data and cache.. it will work.. if not try restoring partition with the stock recovery..
you can find stock recovery in oppo community
JackYao said:
How do you solve this problem? When I flash CM12, the phone repeat reboot and can't enter recovery. At last I flash the Omini ROM.
Click to expand...
Click to collapse

sydtek said:
flash stock rom.. go to wipe data and cache.. it will work.. if not try restoring partition with the stock recovery..
you can find stock recovery in oppo community
Click to expand...
Click to collapse
Thanks, I solved the stock recovery. And wipe data and cache, but still can't flash CM rom. At last, I flash the Omini rom. Problem is it often prompt me "Storage space running out".

Try flashing oppo's stock recovery
You can only instal oppo's rom (I.e. ColorOS) in that recovery.. First you have to flash TWRP recovery and then instal the CM rom.. This will work perfectly fine, but in some case like the above the rom would not boot into CM or whatever custom ROM.. In that case you have to instal OPPO's stock recovery to make it work..
And also the insufficient storage problem can be solved by OPPO's stock recovery by using partition - restore partition..
JackYao said:
Thanks, I solved the stock recovery. And wipe data and cache, but still can't flash CM rom. At last, I flash the Omini rom. Problem is it often prompt me "Storage space running out".
Click to expand...
Click to collapse

Wiped Internal Storage; now phone reboots on loading ROMs

Hey guys,
So last night I accidentally wiped internal storage in TWRP. I guess that messed up my partitions or something, I don't know. Anyway, I can still access recovery, and I've tried to do a restore (one that I made back when I was on stock 4.4.2 I think) but after that it tries to boot, gets to "Android is upgrading... Optimizing app Y of X." and once that operation completes it shows the lockscreen for about a tenth of a second, and the phone reboots.
I'm stumped. Anyone know what can I do?
Sorry if this has been asked a hundred times. For some reason the search function in the forums isn't working for me. And I've been looking for a solution all morning.
EDIT: FYI when I tried the restore I did only System and Data and not Boot, because I was afraid that'd cause more problems.

Did you try restoring and performing a factory wipe before booting the newly-restored ROM?

It seems that Marshmallow based roms aren't working, but Lollipop ones will boot. Not sure why as I didn't have any problem with the same MM roms in the past.
More info:
MM roms wont flash in TWRP; after the failed attempt, TWRP says system cannot be mounted until I either wipe or install a 12.1 rom.
Tried to install a stock rom (4.4.2) and it failed in TWRP. Just says "Error Flashing"

Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?

audit13 said:
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
Click to expand...
Click to collapse
Yes to full wipe. TWRP is 2.8.7.0, so yeah I think it's the newest? Not 100% sure.

Wiping internal storage should not affect the partitions. I'm not sure that TWRP even has the ability to change partitions.
Yes, 2.8.7.0 is the latester version of TWRP.
If you are on the nj2 bootloader, try flashing this in TWRP: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006

Welp, seems to be all good now. Not sure if I really did anything to fix it or not. I tried to install a stock ROM but it wouldn't boot (stuck on Samsung logo) but after that my CM13 ROM installed properly again. The one CM13 ROM I have still wont install at all - maybe that file became corrupt or something? Not sure if that's even possible.
Either way I'm all fixed up. Thanks for all your help.
Cheers

Glad you got it sorted out. If you do figure out what you did to get it working, post your answer as it may help others that are in a similar situation.

Issues flashing ROM

I'm having some issues flashing any ROM. TWRP will not wipe data, or internal SD
For some reason, when I go to wipe data and factory reset, TWRP will say it was successful, but nothing ever gets wiped. It will only wipe system if I choose to. I've gotten a ROM to flash but when it boots up, all of the old apps and user data are still there and it makes everything crash. I've gotten into settings to do a reset, it reboots into recovery, runs the script, and still nothing wipes.
What I have tried:
Old TWRP, newest TWRP
CWM (seems to wipe but it won't get past the note 2 screen after flashing anything)
Wiping with CWM, flashing TWRP, then flashing a ROM (still loops after the note 2 screen)
Is there a terminal command I can use in TWRP to manually wipe things?
Thanks for any help I can get, I've flashed so many phones I can't remember but I've never had this issue

Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?

audit13 said:
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
Click to expand...
Click to collapse
Well when it bootloops t the Note 2 screen, I have to flash a ROM with Odin to get it working again. I've flashed a stock ROM with Odin, flashed TWRP with Odin, tried the wipes and it never wipes anything... I'm lost...
Isn't there a format function in TWRP that is seperate from the factory reset or advanced wipes? I was also trying to find a terminal command to type in the terminal in TWRP... I'm a little stumped...

I'm sorry, I read that too fast... That may actually work, wipe it in the stock recovery, and just don't let it boot into the system before flashing other stuff... I'm gonna try that out... Thanks man, I'll post back about it...

Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?

audit13 said:
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
Click to expand...
Click to collapse
The stock ROM I used is I317-ODIN-UCUCNJ1-Stock without the booloader packaged in, I'm still on the old bootloader. It's 4.4.2
The ROMS I've tried to flash was
Cyanide (Error 7, says incompatible data, please wipe the phone)
Resurrection Remix (Error 7, says incompatible data, please wipe the phone)
Latest CM10 Nightly
I got CM10 and Resurrection Remix to flash a couple times, but the phone boots and all the old apps and data, including the AT&T ones are still there, and the system keeps crashing. Then I change the recovery to CWM because it seems to wipe, change back to TWRP, flash the ROM and gapps again, but it bootloops at the Note 2 screen.
Should I try the 4.1.1 ROM and CWM? Whenever I'm going from a stock TW to non-TW I like to format everything, data, cache, system, and internal SD, but of course TWRP won't wipe the data or the internal SD.

It's probably because the bootloader and modem are too old for the roms. Recent roms will need updated bootloaders.

Ok, I had some more time to mess around with this today and figured it out. I feel kind of dumb but oh well, I got it.
TWRP was already loaded on, so I went to messing with it again. The 'Swipe to factory reset' was not wiping the data, and there was the 'Format Data' button right there in front of me. I did the factory reset, format data, rebooted recovery, wiped dalvik, cache, and system, then flashed the ROM and everything booted up just fine.
Thanks for all of the help!

Soft brick, stuck on logo screen

I just got my new OP3, I rooted it and flash Cm 14.1. Everything was working fine until I added a 6x6 pattern password which I forgot. Search around a bit and looked like the only option was to factory reset. I went to twrp and wipe into factory reset. Afterwards I reboot system only to find that I'm stuck at the Oneplus logo screen, it wouldn't load into lock screen. I have tried flashing lastest stock rom as well as OS 3.2.7 which was the one I used in conjunction with Cm 14.1.
No idea how to fix this. I can use recovery mode and fastboot, but I just can't get pass that logo during reboot.
Any help would be great. Thanks in advance.

try wiping the dalvik cache and data and everything else and clean install the ROM

Tried wipe
anup807 said:
try wiping the dalvik cache and data and everything else and clean install the ROM
Click to expand...
Click to collapse
I wiped everything but the internal storage. I am quite new, what is clean install?

Check this thread out: http://forum.xda-developers.com/oneplus-3/how-to/guide-downgrade-to-mm-flashing-ob8-t3511161
If all else fails, and you're fine with losing your data, pictures, etc. Reformat your phone. I had a similar problem when trying to go back to Android M from N. I ended up booting in fastboot and running the commands:
fastboot format:ext4 cache
fastboot format:ext4 data
fastboot format:ext4 system
Then from here you could either side load a ROM or boot into twrp and transfer your ROMs to flash. That's how I fixed my softbrick lol. There might be another way but that worked for me.
---------- Post added at 04:26 AM ---------- Previous post was at 04:25 AM ----------
Darrentay said:
I wiped everything but the internal storage. I am quite new, what is clean install?
Click to expand...
Click to collapse
Wiping all partitions except for internal storage then flashing a ROM is considered a clean flash.

Thanks
jon52491 said:
Check this thread out: http://forum.xda-developers.com/oneplus-3/how-to/guide-downgrade-to-mm-flashing-ob8-t3511161
If all else fails, and you're fine with losing your data, pictures, etc. Reformat your phone. I had a similar problem when trying to go back to Android M from N. I ended up booting in fastboot and running the commands:
fastboot format:ext4 cache
fastboot format:ext4 data
fastboot format:ext4 system
Then from here you could either side load a ROM or boot into twrp and transfer your ROMs to flash. That's how I fixed my softbrick lol. There might be another way but that worked for me.
---------- Post added at 04:26 AM ---------- Previous post was at 04:25 AM ----------
Wiping all partitions except for internal storage then flashing a ROM is considered a clean flash.
Click to expand...
Click to collapse
Well in that case, I have clean flash multiple times with different ROM, but I'm still stuck at the logo once I try to reboot. I also tried to flash Os 3.2.7 and Cm 14.1 again but i got no results. Attempting to reformat I guess? I have no data since its a new phone, so I don't mind losing stuff.

Okay sounds good! Before you reformat through fastboot, try booting into twrp and reformatting the partitions through there. TWRP>wipe>advance wipe>cache>change file system>ext4
Repeat the steps for the data and system partitions as well. Then from there transfer a 6.0 ROM and flash it over with the correct Gapps.
Sent from my ONEPLUS A3000 using Tapatalk

Darrentay said:
I just got my new OP3, I rooted it and flash Cm 14.1. Everything was working fine until I added a 6x6 pattern password which I forgot. Search around a bit and looked like the only option was to factory reset. I went to twrp and wipe into factory reset. Afterwards I reboot system only to find that I'm stuck at the Oneplus logo screen, it wouldn't load into lock screen. I have tried flashing lastest stock rom as well as OS 3.2.7 which was the one I used in conjunction with Cm 14.1.
No idea how to fix this. I can use recovery mode and fastboot, but I just can't get pass that logo during reboot.
Any help would be great. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/one...ashing-ob8-t3511161/post69994625#post69994625
Try this method. It worked flawlessly for me.
Download the official ROM from oneplus Website. Support-->Downloads.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
official recovery:
http://oneplusroms.s3.amazonaws.com...694615&Signature=1Momnxm8gHWw03D401Oof5YxnE4=

anup807 said:
http://forum.xda-developers.com/one...ashing-ob8-t3511161/post69994625#post69994625
Try this method. It worked flawlessly for me.
Download the official ROM from oneplus Website. Support-->Downloads.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
official recovery:
http://oneplusroms.s3.amazonaws.com...694615&Signature=1Momnxm8gHWw03D401Oof5YxnE4=
Click to expand...
Click to collapse
I notice something interesting after flashing 3.2.8, when I try to reboot system, it says no OS installed.

Darrentay said:
I notice something interesting after flashing 3.2.8, when I try to reboot system, it says no OS installed.
Click to expand...
Click to collapse
Really Strange. I think its the problem with the system partition format and encryption.
Anyway best solution now is to contact Oneplus tech support.
They'll hard reset your phone and restore it with stock firmware.

Partitions are probably corrupt or on f2fs. Check each partition and make sure it's set to ext4. If it won't allow you to do that in twrp, use the command "fastboot format:ext4 nameofpartition". After that you should be able to flash over a marshmallow ROM.
Sent from my ONEPLUS A3000 using Tapatalk

Have you tried changing / updating the twrp recovery. Newer roms require the unofficial one.

v.konvict said:
Have you tried changing / updating the twrp recovery. Newer roms require the unofficial one.
Click to expand...
Click to collapse
I can't solve the problem so I contacted Oneplus. They use remote access to help wipe everything and reinstall drivers. Thanks for the help though.