yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] ilmich:
Looking into this commit https://github.com/omnirom/android_bootable_recovery/commit/71c6c50d0da1f32dd18a749797e88de2358c5ba1 I've supposed that also for oneplus one the flag

TW_CRYPTO_USE_SYSTEM_VOLD := qseecomd

should be used as fallback for oreo encryption. (for now seems that is not enabled in all the recovery builted for this device)

I'm trying to build twrp myself, but without success for now (I need some times to setup build environment :) )

Cheers

Michele
[ONE Original Android Development] tompol74:
Maybe it's not a big deal but openrecoveryscript FAQ states as follows :

In fact, backup name is fixed string equal "(Current Date)".

I'm using Lineage Downloader which allows for creating backup automatically before upgrading system but every backup has the same name so I have to manually remove the old one before upgrading.
[ONE Original Android Development] troypulk:
I think I bricked my bacon trying to install TWRP 3.2.1

This all started because I tried to upgrade to LOS 15.1 but got the error 7 message and I read that upgrading to TWRP 3.2.1 would fix it. so I tried upgrading to TWRP 3.2.1 following this web site: https://twrp.me/devices/oneplusone.html

The first time I flashed into recovery then I rebooted the system and then rebooted into recovery but it never worked it just stayed at the first boot screen with a 1 in a box.

So I held down the power button and it turned off then pressing it again it booted into the latest LOS 14.1 nightly.

So I tried the same thing with TWRP 3.1.1.0 same thing it did not work, I delete the .twrp file in the TWRP folder and tried to boot into recovery but it didn't work either.

I first did this with me.twrp.twrpapp-26.apk which was version 1.13 after this didn't work I downloaded the TWRP app from the google store which was version 1.19 and tried again but this time after I tried to boot to recovery it will not reboot into the OS it's just stuck on the screen with a 1 in a box and holding down the power button and the down volume does not work.

What else can I try to bring the phone back to life?

Thanks

fastboot works but When I type adb devices the List of devices attached is blank.

adb is the same devices is List of devices attached is blank.

fastboot devices

no permissions (verify udev rules); see [http://developer.android.com/tools/device.html]	fastboot

adb reconnect

error: no devices/emulators found

I'm not sure what to do now the device list is blank

It also says

fastboot flash recovery twrp-3.2.1.img

< waiting for any device >

UPDATE

I need to put sudo before fastboot devices

twrp-3.2.1.img is the wrong format I'm looking for the right one now.

I get this:

sudo fastboot flash recovery twrp-3.1.1-0.img

error: cannot load 'twrp-3.1.1-0.img'

twrp-3.1.1-0.img is already on the phone at /sdcard

UPDATE:

I needed to put the twrp-3.2.1-0 image in the PC directory I was running the fastboot commands from

This worked and the new version twrp-3.2.1-0 is installed and working

I installed LOS 15.1 and everything is working.
[ONE Original Android Development] Maverick John:
Flashed [MENTION=2040569]jgcaap[/MENTION]'s final MM ROM no problem but, when I entered recovery again to flash another ROM... Cyanogen Mod Recovery??? What happened to my TWRP? Any way to get it back?
[ONE Original Android Development] zertyuiop:
You need to uncheck "Update recovery" setting in developer options and then reflash TWRP via fastboot without reboot, power off and then power on via Volume Down + Power to enter TWRP.
[ONE Original Android Development] Maverick John:
Without reboot? Can you kindly explain the steps?
[ONE Original Android Development] zertyuiop:
You need to boot into fastboot, flash TWRP via "fastboot flash recovery twrp-*.img" and then power off smartphone using power button. Then you must boot into recovery by pressing Volume Down and Power for some seconds. (You must replace twrp-*.img with TWRP image file name)
[ONE Original Android Development] Maverick John:
OK. I'll try.
[ONE Original Android Development] kuzip:
I have installed TWRP 3.2.3-0 and LineageOS 15.1 on my One and there is one problem.

I've encrypted the Data-Partition using lineageOS.

TWRP fails to decrypt the /data partition. If I enter the recovery mode TWRP asks for my pattern but it always says:

"Pattern failed, please try again!". If I boot normally: LineageOS also asks for the pattern and it works. Updates are working fine without the but I also want to backup my phone. :(

Did you have similar experiences?

Any solutions?

Thank you in advance.
[ONE Original Android Development] stewa2jm:
Same. Others too. Doesn't appear to be a solution.

EDIT: Oh dear... I just realized I was on a different thread than I thought. I have this issue on a Galaxy S9+. Ignore me.
[ONE Original Android Development] thedamager:
You could try this:

https://xdaforums.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692

Works fine for me.
[ONE Original Android Development] kuzip:
Same with twrp-3.2.1-K2

Now I installed "twrp-3.2.1-K2" but problem is still the same.
[ONE Original Android Development] :
I'm using TWRP 3.2.3-T3 beta (from same dev) and it's working / decrypting fine.

https://kutep0v.gitlab.io/TWRP/?version=testing
[ONE Original Android Development] ketut.kumajaya:
Official lineage-15.1 fix available but need patched TWRP https://github.com/kumajaya/android_bootable_recovery/commits/lineage-15.1

TWRP binary: https://goo.gl/iVRPW8
[ONE Original Android Development] iwishuweredad:
Guys, i got a problem, i am/was using latest TWRP Version, with LOS 16 on Oneplus One, suddenly today, while charging, i looked on my phone, and the bootloader with the message"no os installed" starred at me. I tried to reinstall, but the Memory showed 0 MB, and: Not active. So my question is: Is the harddrive dead? Do i need a new phone? I tried whiping, changing formats over TWRP, but no success, "no mounting of storage" possible.
[ONE Original Android Development] bluemoel:
I had that happen to me a while back and I sorta panicked hard and started flashing and formatting and fixing like Ive never done before. including changing twrp versions, multirom, normal. I don't remember what actually got it working again. bit I think it was I installing one of the newer k2 twrp versions. and luckily I had made a backup of emmc firmware partitions. which I flashed and then restored another backup I made years ago using an older tarp version I think back to lollipop. and then everything has been working fine since. sorry I don't have a straight answer. but I did recover from the mess. just play around with it. if not trade it in for a oneplus 7 pro with the limited offer. good luck
[ONE Original Android Development] automatisms:
Is it possible to move (or copy) a folder & its contents from internal storage to a usb drive while retaining file & folder modified dates & times on TWRP 3.2.3-0 without root? If so, how could this be done?
[ONE Original Android Development] ze7zez:
Try tar or gzip.
[ONE Original Android Development] bluemoel:
Try using command line in twrp and use "cp -R /sdcard/TWRP/ /storage/usbmount/location"
[ONE Original Android Development] navinthomas:
ADB and MTP are not working in TWRP

ADB and MTP are not working for me when I am in TWRP. They both work fine when I boot into any ROM, just not while I am in TWRP. Does anyone have any experience with similar issues?

EDIT: Got it fixed. Check my next reply.
[ONE Original Android Development] ze7zez:
Show recovery.log after connecting usb cable to PC.
[ONE Original Android Development] navinthomas:
Someone else was able to help me with this issue and it got fixed. :)

When my phone is in TWRP, it appeared as Google Nexus ADB Interface in Device Manager of Windows. I clicked Update Driver and force changed it to USB Composite Device. It worked fine after that. Both MTP and ADB started working while in TWRP.
[ONE Original Android Development] lap87:
I just dug up my OPO, wanted to try out e-foundation rom, and foolishly tried to flash the latest twrp for bacon/OPO.. And i can't boot into recovery at all, and no matter what recovery i try to flash, it won't work.

It's currently not even rooted, on LineageOS 15.1.

What do i do?
[ONE Original Android Development] lap87:
i think i bricked it now.. fml

Black screen, no vibration on power-on etc.

Doesn't list as fastboot/adb
[ONE Original Android Development] steve8x8:
You should still be able to enter fastboot mode... And there's the option to open the device and disconnect the battery...
[ONE Original Android Development] lap87:
Yeah, gonna try the battery route when i get back home tonight, it wasn't showing up in device manager on win10 etc, fastboot wasn't working.
[ONE Original Android Development] steve8x8:
Any news? Perhaps another cable / USB port would help?
[ONE Original Android Development] drezz2:
I have done a backup of android 9 and another one of android 10, when I try to restore the one of android 9, many times it starts in fastboot mode, but if I repeat the restoration a couple of times, it ends up starting android 9, but with android 10 , the restore always takes me to fastboot mode when I start, is there something I am doing wrong?
[ONE Original Android Development] oriped:
basically, I've done the same. the latest official oxygen os is installed and fastboot is still working.

flashed the latest twrp - can't reach recovery anymore. tried different verions, no success

Any suggestions?
[ONE Original Android Development] TheBlackHoleFR:
Have you tried the unbrick guide ? https://xdaforums.com/t/guide-unbrick-unbrick-oneplus-one.3013732/
[ONE Original Android Development] oriped:
thanks, I actually found an easier way from this site, as fastboot is still working:

return opo to stock (without reset tamper flag)

then i flashed the LineageOS recovery (twrp didn't work the last time, that's how the trouble started...) and then directly rebooted to recovery (as stock OS apparently removes custom recovery). so, next steps from fastboot mode: pull out usb cable, press power button to turn off, and then vol down+power to get into recovery.

Followed instructions to manually upgrade LineageOS to latest version, installed opengapps for Android 11, arm, pico (nano version was to big, surprisingly).

Systems runs pretty smooth, i am surprised :)

Now I can continue using the OPO (as secondary phone, btw)
[ONE Original Android Development] TheBlackHoleFR:
Glad to hear you revived your OPO, mine (also as a secondary phone) is literally falling to pieces : if I remove my bump case, all buttons will fall 😁
[ONE Original Android Development] Vortex1969:
Sounds good so no lag with this rebooting into recovery? Like the unofficial.
[ONE Original Android Development] dictionary:
I haven't flashed this newest one yet, as I'm using Philz, but 2.7.1.1 boots much faster than this unofficial 2.7.1.0
[ONE Original Android Development] SmokinJohnny:
Encryption is fixed! Thank you!
[ONE Original Android Development] DirtyDroidX:
Running 2.8 with no problems. Tested all options, everything seems lovely jublly.

Sent from my A0001
[ONE Original Android Development] wickedninjalo:
Can you please send me a copy of the v2.8 you have please? The official download link isn't working for me.
[ONE Original Android Development] störte:
Can somebody check if the OTG is working ?

Mine is not working and i need it as i have all backups on my otg stick
[ONE Original Android Development] Guido83:
I was about to post the same. OTG is not working anymore. reverting back to 2.7 now....
[ONE Original Android Development] störte:
Hast PM
[ONE Original Android Development] Ok_Kaleidoscope5109:
I get the error "Can't install this package on top of incompatible data" when flashing the latest CM nightly. I did an MD5 check too.

However on TWRP 2.7.0.0 it works perfectly. Seems like 2.8 is somewhat different? Any thoughts?
[ONE Original Android Development] :
For me the same error :(
[ONE Original Android Development] RBwai:
Where is recovery.img located. I try to install v2.8 with TWRP Manager and Manager continously crashes. Is thereany possibility to install it manualy with Root Explorer? On my old phon that way was possible.
[ONE Original Android Development] mhulsegge:
Hi all, thanks for this update. Just flashed it, worked like a charm.

However, I cannot see the OPO in my pc's explorer when in Recovery. How can I mount it properly ?

In Device manager, while in recovery, it's listed as "Google Nexus ADB Interface".

MTP is enabled in recovery.

Thanks
[ONE Original Android Development] RBwai:
I have trouble when instaling recovery with TWRP Manager, so I prepare a zip for instalation through recovery. It works for me!

View attachment TWRP_2.8.0.0-Bacon.zip
[ONE Original Android Development] jrior001:
Were you guys encrypted or no?
[ONE Original Android Development] danyvw:
Thanks. Works like a charm.
[ONE Original Android Development] :
I want to report a bug with aroma installer. With 2.7.1.1 my Aroma Installer Zip File works, but with 2.8.0.0 it doent.
[ONE Original Android Development] ak:
I have the same error, no encrypted partitions.
[ONE Original Android Development] :
+1 no encrypted partitions, flashed via fastboot

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] DirtyDroidX:
Another mirror if OP is still down.

https://docs.google.com/file/d/0BzgUrWZ7XZ0rbDFiWWZUU19vcEE/edit?usp=docslist_api

Sent from my A0001
[ONE Original Android Development] jrior001:
Are us guys on f2fs?
[Moto X General] super65man:
If you haven't heard, there is an $18,000 located here http://xdaforums.com/showthread.php?t=2728051. This may be for the Samsung Galaxy S5. If there is an exploit that will cover 4.4.2, it could possibly support multiple: devices running it and possibly bootloaders running 4.4.2, but I'm no expert on how tight the relation of security is on both Moto and Samsung platforms. What do you guys think? :laugh:
[Moto X General] thelogman:
I thought 18,000 was a typo at first then I read the thread and about lost my mind
[Moto X General] super65man:
If you think about it, a bootloader unlock and a root exploit are 2 different things. Zergrush is an example of a mutli-supported root exploit.
[Moto X General] SymbioticGenius:
LMAO. Thanks for posting this, I was having trouble sleeping (4am now) but this bit of comedy should help me right along.

I can't believe that people who care about unlocking and rooting are still on Verizon, still buying Samsung devices, not waiting for devices to be unlocked first, and complaining about all of the above. I wouldn't be shocked if that bounty hits 6 figures. Good luck to them.
[Moto X General] super65man:
The thing is though, there is no exploit widely available for kitkat. If someone can find an exploit for the samsung phone it might actually work on all platforms of phones.
[Moto X General] KidJoe:
But root is only part of the equation on the X.

Don't forget about write protection.

Remember, when on 4.4 rooted with write protection disabled, when you upgrade to 4.4.2, you keep root but write protection becomes re-enabled... at that point anything you save/modify in /system or the like are lost at power off/on. That appeared to be in the bootloader, not the OS.

So a "common" 4.4.2 root would also need to disable write protection to be effective on the X.
[Moto X General] spc_hicks09:
People are still on Verizon because of unlimited data (like myself). Samsung devices aren't bad either, just because their build quality doesn't allow you to drop the phone from higher than 5 feet. I'll tell you now, I once dropped a Note 2 from head level (i'm 5'10") and it just had some scuffs on the battery cover and a ding on the fake chrome framing on the bottom left hand corner. No screen damage or anything else. By the way, the Verizon versions aren't the only ones locked up.

Root bounties are going to continue to get higher and higher, as locked devices become more and more the "norm." Not everyone can afford $600-$700 for dev edition phones, so until the price of dev editions come down, more and more people will still be wanting root exploits to be found.
[Moto X General] SymbioticGenius:
I had unlimited on Verizon for years. Now I have unlimited on T-Mobile for half the price.

I don't have much of an issue with Samsung's build quality. Their radios suck and their phones are locked tighter than fort "Knox"

With the money I've saved I could have bought a new Nexus5 or MotoX every three months. At first I had both in fact.

It's just interesting to see so many people band together to spend money to circumvent a company when they could easily save money and drop the company altogether.

You'd be shocked how quick Verizon would allow unlocked phones if everyone left them for that reason. Although I'm sure they'd try to claim the bounty LOL
[Moto X General] Darth:
I have to say....I would never buy a phone that didn't suit my needs just to save on my bill. Money isn't everything.

I want a phone i can do what I want to with it.....never a locked down one. This is my hobby....I'll pay what I need to for the phone that's right for me.

So I'll never be involved in bounties and waiting games.

But that's just me. ;)
[Moto X General] super65man:
That is true, but if an exploit is released that will root it we would be one step closer to having the entire package. I'm sure disabling write protection is easier than making an exploit for root. But that's just my opinion, I have no idea where you would start if you were finding vulnerabilities.
[Moto X General] Darth:
I think an $18000 bounty just shows how impossible it is. Devs would be trying everything to claim that kind of cash.
[Moto X General] thelogman:
Jcase released his exploit for the x write protection is still there though
[Moto X General] Darth:
Not too useful really. Root without write protection disabled let's you use certain apps OK...but any system changes revert on reboot.
[Moto X General] super65man:
Got a link to the exploit? Also then all we need to do is disable write protection now.
[Moto X General] thelogman:
I believe its in the moto x orig android development page.
[Moto X General] Darth:
And now 4.4.3 coming. See what happened there. ;)
[Moto X General] Arak-Nafein:
Some of us have no option. Verizon is the only carrier that gets an acceptable signal in my area. AT&T has about 75% of the coverage of Verizon, and all the other carriers get zilch. Plus, I would be throttled in the first day if I had T-Mobile, grandfathered unlimited data is amazing!
[Moto X General] thelogman:
Basically the exploit was outed by several people so it then became useless to jcase so he went ahead and released it now if someone figures out write protection my life will be completed.
[Moto X General] super65man:
Which is exactly why I'm not updating to 4.4.3
[Moto X General] KidJoe:
I hate to be a pessimist, but I don't think its going to happen. Here is why..

With the successor to the X being announced as coming later this year, the market saturation of the X has likely reached its peak.

Combine that with sales like today/tomorrow's $100 off 32gig, bringing the Dev Edition down to $349.99 (plus taxes), less if you use the JB rebate thing, so the cost to get an X with an unlockable bootloader is more reasonable. And unlocked bootloader doesn't need to worry about exploits.

Add in the number who got an unlock code for the ATT, VZW and Republic Wireless from the Chinese Site/Middleman, and the audience for a root/write protection disabled for locked bootloader again shrinks.

And to top it off... With 4.4.3 rolling out, any exploit left in 4.4.2 was likely patched too, like the root exploit was, so they'd have to start over... i.e. they are trying to hit a moving target with root and write protect disable on locked bootloaders.

So is it worth the time/effort, even with the bounty being offered?
[Moto X General] :
My opinion is...and this is a compliment to [MENTION=2376614]jcase[/MENTION], if he hasn't or can't or doesn't have time to disable write protection.......I doubt anyone else can. He seems to be the master at this.

Save up for those dev editions. ;)
[Moto X General] SymbioticGenius:
I believe jcase would have been able to get it done if a bunch of amateurs didn't release the exploit he was going to use. Every day I thank myself for getting a developer edition. I'm hoping that Motorola's next phone has one also.
[Moto X General] super65man:
How did they get ahold of the exploit if they were amateurs?
[Moto X General] SymbioticGenius:
The same way people hit the lottery, persistence and luck. If you flip a coin enough times... eventually it will land on its side.
[Moto X General] jcase:
They didn't get an exploit, they got patches from Google, as I tipped them to the vuln months ago. The only working exploit I've seen public is mine.
[Moto X General] marnold425:
Just out of curiosity what do you get out of finding exploits and then informing Google about them before end users can utilize them. I mean I know if no one updated they can use your exploit but what if they updated? Fortunately I have the dev edition so it doesn't hinder me in the least. I'm just thinking if Google isn't paying you handsomely then you're just finding exploits and tipping off Google because? To me it seems like control issues but I'm really just Curious like I said I have no need for your exploit. It's just funny how many people you left hanging and upset so you could keep the exploit for your "own" reasons and then you ended up releasing it anyway. Something smells a bit Petty like you wanted to release the exploit before someone else finished your work for US because it seems you're no longer on this team anymore. Id feel scared having you on XDA scared someone might find some amazing exploit or software mod and you'd run to Google And tell them all about it. you've shown us that u only care for yourself and don't say you released this exploit for us because you told us you wouldn't release it at all you only did so to beat the "amateurs" from completing and releasing your exploit.