yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Anders Williams:
I have a newbie friend to OPO so trying to help him out here.

We recently flashed 2.8.7.0 on the OPO, and things appears to flash perfectly, except for one thing, and I cannot for the life of me figure out why. The updated modem/baseband drivers will not update from v.2.0.1 which as far as I know is the stock baseband driver form 11s which the device came with.

Tried several of the latest CM12 nightlies, the stand a long OPO firmware as of 15/5 and the Oxygen OS modem driver found here on XDA, all of which has worked with updating the baseband on my own device but for some reason not on the other, anyone know of any issue with TWRP versions and modem flashing?

Ps. also posting in a OPO modem driver thread just to see if anyone got anything on it there as well, but thought it could be TWRP related
[ONE Original Android Development] OmegaBlaze:
2.8.1.0! [MENTION=5192487]deepaklunked[/MENTION]
[ONE Original Android Development] deepaklunked:
Oh! Fine. I just assumed it to be a typo, thought u meant a recent release. [emoji12] Sorry. And thanks for throwing light on old versions.

Sent from my ONE
[ONE Original Android Development] geowolf1000:
Try this
[ONE Original Android Development] yannn007:
You need TWRP version 2.8.6.0 or older. The new ones dont flash modems, idk why they just dont.
[ONE Original Android Development] Anders Williams:
Thanks, we managed to flash one directly from fastboot, he's is now on 3.xxx.241 which appears to have improved proximity sensor operations.
[ONE Original Android Development] geowolf1000:
I am on cos12

I ve been upgrade with 2.8.7.0 hudrogen modem

After i install later s full firmware from 5.1.1 i can not either flash modem s

Maybe changes relate to cm and not to twrp

I am not sure
[ONE Original Android Development] Ok_Kaleidoscope5109:
I noticed something really weird yesterday... I did a full wipe on TWRP 2.8.6.1--factory reset essentially so it wiped my internal storage and everything....

I then proceeded to install CM12.1 0702 nightly and the latest Gapps from OpenGapps (0701).

I copied a few folders to my computer beforehand and copied them back in TWRP. Those folders were my TWRP Nandroid backup, my TitaniumBackup Files, my WhatsApp files, my SMS backup, etc. However after copying them back I noticed the years were all 1970. That's fine and all--I suppose the timestamp is just messed up, but I cannot WRITE to any of those folders anymore, nor can I even change the permission in CM. Is TWRP doing something weird if I copy files through TWRP?

The issue i first noticed was WhatsApp--I can't download new pictures from messages because it apparently can't write to the WhatsApp folder. I tried a chmod 777 in TWRP but the folder is Wonky. Same with my other folders. In Titanium Backup, the app says it's not a writeable folder, so when I tried to make newer backups I had to create a whole new folder. I'm not sure what's going on here
[ONE Original Android Development] aosp:
Try flashing it next time with [MENTION=4021423]ketut.kumajaya[/MENTION] custom built twrps for the opo https://www.androidfilehost.com/?w=files&flid=30332

bacon: f2fs

https://github.com/dcd/android_device_oneplus_bacon/commit/1970e33987a5e7e7503ae8f6e36b35f70bad2201

msm8974: f2fs: bring up to date with Jaegeuk's branch

https://github.com/dcd/android_kern...mmit/9fc3aa9f59b482fe2bf61b68352626866f9fd630

update f2fs

https://github.com/dcd/android_kern...mmit/55fde14d40d0e5d8c15d4f1c86a786526562bfba

bacon: support f2fs /data and /cache

https://github.com/kumajaya/android...mmit/7237af43cc01061853694ac9f265dbf76679c99e

TWRP-ify

https://github.com/kumajaya/android...mmit/010a16154a75267a5cdc9327d860332a04f0e89c

bacon: Switch to TWRP 1080x1920hq resolution

https://github.com/kumajaya/android...mmit/10480d87733f39619e5b0dbfe8127b2d46f2a129

oppo_msm8974-common: support f2fs volumes

https://github.com/kumajaya/android...mmit/7950485c7109053131a1eff4491f33719db9eecf

1080x1920hq: OnePlus branding

https://github.com/kumajaya/Team-Wi...mmit/f60850ae89ed081bf2369816019b015c0985f5de
[ONE Original Android Development] ABHISHEKSR:
You have to manually flash modem via fastboot. Starting 2.8.6.0 TWRP has encrypted modem partition to prevent touching it by flashable zips. It's normal behaviour :D

---------- Post added at 08:14 PM ---------- Previous post was at 08:13 PM ----------

You have to manually flash modem via fastboot. Starting 2.8.6.0 TWRP has encrypted modem partition to prevent touching it by flashable zips. It's normal behaviour :D
[ONE Original Android Development] geowolf1000:
Some of us can flash modems with latest

Is no the point if but who?
[ONE Original Android Development] ABHISHEKSR:
You can flash but it won't update your modem.
[ONE Original Android Development] geowolf1000:
I am on latest firmaware

And i have cos12 i use mine maintance and upgrade wiith all the avaible methods

With firmware also update charge and partition behavior.

Can also be again compitible to write all your files in next version

Is new commit did not read

but i am also encrypt and i did change ful latest firmware wich fix various problems with cos

As i know the same method that cngn support encrypted did and [MENTION=912474]Dees_Troy[/MENTION] .

Thanks
[ONE Original Android Development] Grigster:
The latest version still has the Modem flashing problem.

I tried to flash latest CM Nightly in order to get the latest modem version (241) but it just didn't flash anything.

Went back to 2.8.6.0 and I'm the happiest flash-o-holic person right now.
[ONE Original Android Development] djha53k:
Yes damr here, everytime Inflashed FW in latest version it worked only for same install only. Once I flashed new update, the FW dissapeared :(

Also back to 2.8.6.0...
[ONE Original Android Development] pwnyu:
As mentioned in my post i flashed the twrp img file via fastboot which got the phone up and running again.. the TWRP manager doing the same thing corrupted the EFS and i had no recovery.. only OS without network/wifi and fastboot
[ONE Original Android Development] playya:
I asked as there was another user with the same issue. Did you nandroid or you had a backup of your efs

edit: Link me to your thread

1+1 Homie......
[ONE Original Android Development] pwnyu:
I didn't have any EFS back up at all.

the symptoms i had was corrupt EFS. no IMEI/MAC/Serial/network etc what normally happens with corrupt EFS after using TWRP Manager to flash the same file after selecting bacon as the device. It gives you a warning saying "make sure the destination path is correct" then flashes once you reboot into recovery nothing happens you have no recovery.

For the 3rd time..ALL I DID was flash the twrp 2.7.1.1 .img via fast boot and then i had IMEI/MAC/Serial/Wifi/Network again and a recovery.
[ONE Original Android Development] playya:
Hahahaha 3rd time huh OK man completely different success story than most I've read. Thanks for repeating yourself to me... Take it easy

1+1 Homie......
[ONE Original Android Development] dictionary:
His first post clearly states that twrp manager screwed up is efs. Then said by fastboot flashing the recovery, it worked.

I didn't go that route, I did everything else, then finally flashing coloros worked. I wonder if I had just fastboot flashed recovery it would have worked. Not sure, but definitely the easiest first option.
[ONE Original Android Development] playya:
I agree but since I have never heard of this form of success and this is xda where people screw things up all the time. I was merely trying to make sure we were all on the same page. Not a big deal and I was actually asking to help you out... If you can now repair your efs by flashing recovery then that is great to know for all..

Thx again
[ONE Original Android Development] Vonnegut:
Does anyone know what these lines mean?

I:Unable to open '/data/media/0/TWRP/BACKUPS/c606c06'

I:Boot status: OKAY

I:Got arguments from boot message

Startup Commands: '--oemunlock'

They come from a log of OnePlus One with a locked bootloader.

Taking a log with my unlocked phone, i don't see'em.

In both cases, i took the log from a

booted

TWRP recovery ('cause i'm testing something for a guy).

I'm especially curious to know what Startup Commands: '--oemunlock' means.

Does that mean that it unlock (temporarely) the booloader?
[ONE Original Android Development] jznomoney:
Can someone rebuild twrp with the latest patches by cyanogen in the kernel (http://review.cyanogenmod.org/#/c/70390/) to fix the touchscreen issues some of us oneplus users have experienced? I have experienced the unresponsive touchscreen in twrp as well and these kernel patches should fix it.
[ONE Original Android Development] o0ze:
Missing changelog

Is it safe to install 2.7.1.1 ? Does it contain any important bugfixes ? I see no change log about it in the original post.

2.7.1.1 available on http://techerrata.com/browse/twrp2/bacon
[ONE Original Android Development] zephiK:
No changelog. But from what I observe since I've installed it way back, TWRP boots a lot faster.
[ONE Original Android Development] spacemanvt:
does anyone have touchscreen issues in TWRP?

mine seems to freeze sometime, even after the latest CM11 build with the new touchscreen driver.

edit: ah saw the above post.... i guess TWRP needs to be updated with that driver...

Also, I tried to update my TWRP via TWRP Manager to the newest version and nothing happened. Luckily didnt screw up anything... ran Flashify and it updated properly.......

TWRP guys need to add that new touchscreen driver and fix whatever is wrong with TWRP manager. thanks!
[ONE Original Android Development] Poesini:
Can TWRP support F2FS formatting (at least mkfs.f2fs) in the future?
[ONE Original Android Development] bud77:
It's on the way ...
[ONE Original Android Development] DerRomtester:
How do you know that?
[ONE Original Android Development] bud77:
Search for F2FS in AK kernel thread ;)
[ONE Original Android Development] bagadj:
I tried to only boot v. 2.7.1.1 via fastboot but nothing happens... Then tried again 2.7.1.0 andò it works fine..

Inviato dal mio TF300T utilizzando Tapatalk
[ONE Original Android Development] nneves:
Hi

Using 2.7.1.1 but the touchscreen bug don't let me use twrp.

Any way to fix this?

Thanks
[ONE Original Android Development] DerRomtester:
Seems to be an hardware issue for me.

You should rma.

Any news about an twrp update for f2fs ?
[ONE Original Android Development] nneves:
I don't have problems with the rom, only with twrp.

I'll test this for some time.
[ONE Original Android Development] real_sl4cker:
Restore not working?!

Trying to restore any backup I made (using Online Nandroid Backup) resets everything and I'm greeted with the android setup wizzard, all apps, settings etc. not restored. Restore process looks normal concerning restore time, MD5s match.

I'm on TWRP 2.7.1.1 and current CM11S (rooted).

Anybody else having issues with backup restore? Looks like I'll have to completely setup my phone from scratch :eek: :mad:

EDIT:

Ok, I went back in history and was able to restore a backup of August 15th. All newer backups won't restore. I have no idea why because I created those backups all the same way using Online Nandroid Backup.
[ONE Original Android Development] bombadier:
You can always use fastboot as its no hardship when near a computer which I tend to be when flashing firmware
[ONE Original Android Development] Lanchon:
can somebody explain why are modems failing to flash? does this happen silently?
[ONE Original Android Development] CBpbxEcmecmBeH:
just read a few posts earlier.. You'll find your answer
[ONE Original Android Development] ABHISHEKSR:
You have to manually flash modem via fastboot. Starting 2.8.6.0 TWRP has encrypted modem partition to prevent touching it by flashable zips. It's normal behaviour*:)
[ONE Original Android Development] bombadier:
Someone said it was to do with encrypted firmware partitions but not heard an official explanation or there was no link posted for further reading, 100% sure fire way is to use fastboot, you do not get an error it just does not flash correctly in TWRP 2.8.6.1+

---------- Post added at 04:54 PM ---------- Previous post was at 04:48 PM ----------

When I first got this problem I thought it was the comparison checks that the fw zip makes as the message I was getting was x partiton is already up to date, got the same message with cm12.1 nightly, I removed all the checks in my firmware zip and those that have tested said it worked.

Have you a link to some more reading about these encrypted partitions ? I know that katinatez's unofficial version had to remove the fw backup part as it was causing problems
[ONE Original Android Development] ABHISHEKSR:
This was the last update from katinatez on the issue. He linked the twrp commits which was the cause.

http://xdaforums.com/showpost.php?p=61547609&postcount=614
[ONE Original Android Development] djha53k:
I installed couple newer TWRP versions, but always revert back to 2.8.6.0...

Any idea when all those issues will ne fixed?

Thanks.
[ONE Original Android Development] Lanchon:
nope. i had already read all the posts, i think, and no explanation. somebody did mention something regarding encryption, but that was not an explanation because it didnt explain anything and didnt make any sense at all. }

what is encrypted? the modem partition certainly isnt! and why would any encryption not let me flash a raw image of a partition, which is independent of filesystem and encryption? and why would it fail silently?

so my question stands. can anybody answer? -->>

---------- Post added at 11:19 AM ---------- Previous post was at 11:15 AM ----------

i read this already. as worded it doesnt make sense. twrp is a recovery, it is not a phone or an emmc or storage device, it does not have modem partitions within it. and an encrypted partition would do nothing to prevent it being overwritten raw. what is the source of this information?
[ONE Original Android Development] bombadier:
http://xdaforums.com/showpost.php?p=61547609&postcount=614

And missed the link on the last page where the developer of the unofficial twrp explains its due to encryption commits and links to those commits ?

That is why the zip file fails to flash thats the reason,it seems like they are protected and twrp will not allow zips to flash anything over them, so the "fault" lies with TWRP
[ONE Original Android Development] Lanchon:
ok thanks i will look into this.

---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------

i was reading and replying in order.

---------- Post added at 11:37 AM ---------- Previous post was at 11:31 AM ----------

ok there is no explanation whatsoever. it's a known regression introduced with qcom encryption support but no explanation given. just a regression bug that hasnt been researched yet, ok.
[ONE Original Android Development] Lookitfast:
Do you recommend I use "fix permissions" in lollipop or repair file system data.system & cache for just regular maintenance purposes?
[ONE Original Android Development] Lanchon:
dude, if it aint broken dont fix it!
[ONE Original Android Development] maxed4901:
Hi.. Important

Hi. I installed twrp manager and it asked me to install a script to make memory readable. M using the one plus one.

After install it rebooted. M on custom ROM exodus 12.1. I would like to know of this will have any impact on ROM or it's function.. I intend to keep the twrp manager so should I keep the memory readable? Safe?
[ONE Original Android Development] Ok_Kaleidoscope5109:
So basically modem flashing is broken. Use fastboot.

Is there ever going to be a resolution?
[ONE Original Android Development] renaltosonylevi:
Or use twrp 2.8.6.0 .
[ONE Original Android Development] Ok_Kaleidoscope5109:
That's a band aid solution though. ?
[ONE Original Android Development] renaltosonylevi:
Unfortunately that is the way it is most of the time.

Better than no Band-Aids:)
[ONE Original Android Development] lchiocca:
Hi guys,

I've tried to search through the thread for my question but didn't find any. If it was already answered, please be gentile ;). My question is simple: Why can I not backup the "internal storage" (sdcard)? It doesn't make sense if the backup location is on the internal storage itself, but I'm putting the backups on a USB drive using a OTG dongle.

The reason why I'm asking is because I've enabled encryption on my cm12.0s bacon and I want to revert it. Since the data and internal storage are encrypted I would need to make a backup, wipe everything and restore from the backup. I know I can simply copy everything over, but permissions won't get across correctly (and I don't have a md5 etc...). Please also forgive me, but I'm not on the latest trwp but rather on twrp 2.8.6.1. I've looked at the change log, but nothing there seems to indicate that it has changed.

Thanks for any feedback

Loris
[ONE Original Android Development] Formhault:
Why? I mean what improvements does the newer version bring over 2.8.6.0?
[ONE Original Android Development] tanveerkhan9:
Thanks TWRP Team. Best Recovery
[ONE Original Android Development] Ok_Kaleidoscope5109:
[MENTION=912474]Dees_Troy[/MENTION] are you looking into the modem flashing issue with TWRP at all? Is a fix on the horizon?
[ONE Original Android Development] andip71:
Openrecoveryscript restore broken since version 2.8.7.0 / Bacon

Oh, and when we are on the "bugs" topic already, I have another one for which I also created an issue already on github:

https://github.com/omnirom/android_bootable_recovery/issues/38

I always used to create a script by an own app that just fires a single "restore xxxx" command in the script to restore a previous backup.

While this was running fine before TWRP 2.8.7.0, it now fails with the message:

E: Cannot restore system -- mounted read only

I understand this is due to the latest changes on mounting the system volume ro for the OTA stuff.

However, it now completely breaks the restore command when placed into /cache/recovery/openrecoveryscript.

Is there any way I can workaround this issue? (I tried almost everything I can do in the script, but no dice)

Or can it be fixed in the next TWRP version again?

BTW... in an adb session when calling "twrp restore xxxx" it works fine too, just not when in the script itself.

Thanks

Andi
[ONE Original Android Development] djha53k:
I have installed the TWRP 2.8.7.0 Materialist, but when I connect One in recovery to PC... ADB stated: device unauthorized :confused:

So, I had to downgrade back to the TWRP 2.8.6.0... ADB works OK again....

Question is what about the TWRP backup which I made in the TWRP 2.8.7.0? Can I restore from it under the TWRP 2.8.6.0?
[ONE Original Android Development] andip71:
Yes you can, the backups are fully compatible.

Andi
[ONE Original Android Development] Flak:
Does v2.8.6.1 work or do I have to go back to v2.8.6.0?

To answer my own question, yes, apparently you do have to specifically go back to at least v2.8.6.0.
[ONE Original Android Development] knuspertante:
Which OS runs on your pc?

Does it have enough rights?

On Ubuntu you must type in "sudo adb..."
[ONE Original Android Development] djha53k:
Hi, I havi Win7 and I ran "cmd" under Administrator.
[ONE Original Android Development] bombadier:
Go into developer options and revoke adb permissions then unplug/plug your device type adb devices and you should get a pop up asking you to authorize this computer

Actually after reading your post again that may not help if its only recovery that throws the error, do you still have a problem when your phone has booted into the rom ?
[ONE Original Android Development] djha53k:
Hi, nope I do not have this issue anymore once I downgrade TWRP back to 2.8.6.0 :good:
[ONE Original Android Development] tropicanapure:
Post upgrading to v2.8.7.0 in bacon, the nightly upgrade script stopped auto executing.

Selecting "reboot and upgrade" post the latest IMG downloading simply reboots the device with no chance of seeing if an error occurred.

Downgrading to v2.8.6.1 gets it working as expected again.

Anyone else experiencing this?

Tx.
[ONE Original Android Development] sam191919:
now i'm in twrp 2.8.5.0 how can i update to 2.8.7.0 please provid the download link and

before flashing wipe data is required please tell me how to update
[ONE Original Android Development] tropicanapure:
RTFM

"TWRP Install (Requires TWRP 2.8.4 or higher already installed):

Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash."

Source: https://twrp.me/devices/oneplusone.html
[ONE Original Android Development] TerrorApple:
Will there be support for 4x4, 5x5 and 6x6 patterns in future? Personally I'm using a 4x4 pattern and got my device encrypted. Accessing TWRP is only possible when I disable security before boot, because TWRP only allows entering 3x3 patterns. Annoying for ROM updates, but a huge problem if you're having issues with your ROM (bootloop, force closes etc). Then all your data is lost, because disabling security before boot is impossible without a proper running ROM and TWRP doesn't allow large pattern sizes.

Or is there maybe a workaround to unlock via PIN if you convert pattern to PIN?

I don't know if this was asked yet in this thread, the forum search is down atm. If yes, sorry for my question.
[ONE Original Android Development] sam191919:
Can I wipe caches or don't required
[ONE Original Android Development] Ejvyas:
Yyes
[ONE Original Android Development] tropicanapure:
Not required. Cache is used by Android system and not the recovery - I think.
[ONE Original Android Development] Sengeh:
Just one simple and stupid question what is BOOT in the nandroid backup?

Do we really need to restore boot? We have Boot, Cache, System, Data, .
[ONE Original Android Development] tropicanapure:
I generally only back up a combo of /system and /data. I use the image from CM download for starting point if I need a restore.
[ONE Original Android Development] The Dork Knight Rises:
The boot.img is the kernel. Backing up boot will backup your kernel image.

(It should be noted that this isn't the perfect way to restore an old kernel, as different kernels may need different modules for WiFi and other stuff, and hence just restoring the boot IMG while retaining modules from custom kernel MAY break WiFi and other stuff)
[ONE Original Android Development] hogze94:
What are the known bugs on 2870?
[ONE Original Android Development] djha53k:
Flashing FW doesnt work

I had convert back to 2860. Since that I did update it back.
[ONE Original Android Development] Ejvyas:
Flashing firmware, modem won't work
[ONE Original Android Development] provolinoo:
sticking with 2860 as well

firmware/modem fiashing along with the rom is something I don't want to lose
[ONE Original Android Development] 0ss0:
Hi I have a problem coming back from version 287 to version 286.

So, this is my situation: I started using TWRP 2.8.7 without problems. After a bit of time I used COS 11, I switched to Exodus via TWRP 2.8.7 without problems. When COS 12.1 came out, I'm interested only in the new baseband, so I downloaded the baseband flashable file zip from COS 12.1 (241 version) and I tried to flash it with TWRP. So I had to deal with the bug of that version of TWRP. Using the official application TWRP, I tried to downgrade to version 2.8.6 and seemed to be over, but when I tried to reboot into recovery, the phone has booted normally into the system. I tried in every way, even manually, but I always ended up the system. Ok, I re-install version 2.8.7 from the app. Now I could start the recovery and from there I flashed recovery 2.8.6. Yet everything seemed to be fine, but still I cannot get into recovery. So I installed Philz and finally via Philz I updated my baseband. The problem with Philz, however, is that it does not flash correctly exodus, so I reinstalled TWRP 2.8.7. but I know that at every Exodus update, basdeband will not, so I'd definitely solve the problem by installing TWRP 2.6.0. Can you give me some help?
[ONE Original Android Development] 0ss0:
Sorry. I missed it. Thank you

Inviato dal mio A0001 utilizzando Tapatalk