Develop Bugs

Several Qs: 0 folder under sdcard\download\, soft bricked, counter...etc

My I747 is currently running Carbon Rom nightly 20131102 (4.3.1), it's quite old and I want to upgrade to 4.4.
So last night I nandroid backup , format system, data, flashed Carbon KK on it, then gapps, data, cache, delvik, reboot. But it stayed at the CM alien. I reflashed several times but still stuck at there. But I can nandroid back so I'm kind of fine now. But anyone know why?
Second, I notice my \0\ folder is under sdcard\download\0\ than usual sdcard\0\, I must have done something wrong when I first flash the carbon but I don't know what it is. I usually put my .zip in download, could that be why? Could that cause the bricking I have with KK?
Last, I know there's a flash counter and when I first root/flash last year, I went thru many things to avoid that&IMEI, instead of directly flashing a recovery. I think that could be the source of the problems above??? Now 1 year is up and my warranty is already over so I don't have to worry about the counter anymore. If I want to redo everything, and have to noobiest/simpliest method to flash to KK, what should I do?
Sorry if I lack any essential information. I'd be happy to find it to help.

Did you update to the latest CWM before flashing the ROM? Is your current bootloader supported by the ROM?

Not the latest but 6.0.4.3
I'll update it to 6.0.4.7 and try again.
Unfortunately I don't know if my bootloader is supported. I don't really know how to find mine.

I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.

audit13 said:
I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.
Click to expand...
Click to collapse
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.

afyaff said:
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.
Click to expand...
Click to collapse
To be sure, look at the bootloaders mentioned in the ROM's updater script.

After updating from cm13 to cm14 cant access TWRP recovery mode

Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help

If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.

luigymarani said:
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
Click to expand...
Click to collapse
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.

nitros12 said:
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
Click to expand...
Click to collapse
Thanks a lot! it worked
Hw4ng3r said:
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
Click to expand...
Click to collapse
Oh I didnt know that, thank you

Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.

DamianSewo said:
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
Click to expand...
Click to collapse
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"

This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
Click to expand...
Click to collapse
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:

DamianSewo said:
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
Click to expand...
Click to collapse
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/

luigymarani said:
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
Click to expand...
Click to collapse
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?

DamianSewo said:
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
Click to expand...
Click to collapse
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk

luigymarani said:
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
Click to expand...
Click to collapse
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?

DamianSewo said:
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
Click to expand...
Click to collapse
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.

luigymarani said:
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
Click to expand...
Click to collapse
I'm also using 3.0.2.1-v23. Trying to find any information that could help me have my CM13 TWRP image working again, but no luck so far

HELP: Issues updating rooted device to OOS 3.2.8

hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.

backup all your data and install 3.2.8 with the official procedure

Sacob said:
backup all your data and install 3.2.8 with the official procedure
Click to expand...
Click to collapse
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3

tropicanapure said:
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
Click to expand...
Click to collapse
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great

Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Sacob said:
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Click to expand...
Click to collapse

tropicanapure said:
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Click to expand...
Click to collapse
i got the impression that your phone wasn't booting xD
well, every time i flash those betas (9 and 10) TWRP asks me for a PIN that doesn't exists and to solve that i need wipe everything... so i wouldn't count on that

tropicanapure said:
hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
Click to expand...
Click to collapse
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.

No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
ptblad said:
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
Click to expand...
Click to collapse

tropicanapure said:
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
Click to expand...
Click to collapse
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?

I wish I had, man. You went a number of steps ahead when your phone went past the boot animation
As a afterthought - try looking through your logs.
ptblad said:
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
Click to expand...
Click to collapse

Nightly 14.1 lineageOS Rom For Crackling

https://download.lineageos.org/crackling
The First One!

Do we need su for arm or su for arm64?

Obscurax said:
Do we need su for arm or su for arm64?
Click to expand...
Click to collapse
Arm64

What's the build name of the Swift 2X?
Sent from my Moto G4 using XDA Labs

kartotar said:
What's the build name of the Swift 2X?
Click to expand...
Click to collapse
marmite

M.A.K said:
marmite
Click to expand...
Click to collapse
Thanks. Do you have any idea if LineageOS will be supported on Marmite?
Sent from my Moto G4 using XDA Labs

AFAIK, Swift 2 ks not officially supported by Lineage OS, so no. You may be able to find an unofficial version though.

Cannot dirty flash
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?

Got no problems installing it via TWRP. Works great, stable so far.
crdroid was fine too, lots of special settings (little too much for me), but I prefer a ROM with regular OTA updates. Thank you beroid anyway.
P.S. My grammar help changes "beroid" to "heroic"

Can this be installed over the top of cm13.0 nightly?

Mithodin said:
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Click to expand...
Click to collapse
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
I dirty flashed from stock -> cm13 -> crDroid -> thomson.aa's LOS14 without issue. I tried with the official release and got the same as you. So after editing the installer script to force it to install, it did. But once it booted, everything kept force closing. It just wasn't happening.
So I wiped data and chose to restore my backup from google. I just installs most of your apps but it saves a bit of time. Still need to set things up properly though.

M.A.K said:
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
Click to expand...
Click to collapse
I figured this might be due to either
- Something being wrong with the currently installed build
- Something being wrong with the one I'm trying to install
That's why I posted in both places. Sorry if that is not the thing to do.
Thanks for your reply. I guess I'll have to do another reinstall then.

Wifi
Installed tonite smoothly however no wifi - anyone else with this?

Same here, just reported a bug to the bugtracker.

Make a clean install three days ago, all works fine

pahesis said:
Same here, just reported a bug to the bugtracker.
Click to expand...
Click to collapse
I have no wifi, too (after trying a dirty install over an old CM13 that resulted in an error). Here's the issue in their bugtracker, I think, in case anyone else experiences this.
Got the same issue when trying to go back to CM13 now -___-

Seems strange that I've had no wifi issues. I've tried turning it on and off with no problems.
A few (maybe patronising) thoughts:
Did you guys check the md5 hash?
Which recovery did you use? I used TWRP 3.0.2.5
Were you previously on COS13.1.2? I was.
I downloaded fresh open-gapps for the install - ARM64, 7.1, nano.
I wiped system, dalvik, cache. Installed LOS14.1, su, gapps in that order.
The dirty boot left me with lots of force closures so I wiped data, dalvik and cache, completed the wizard after booting and all was fine.

M.A.K said:
Did you guys check the md5 hash?
Click to expand...
Click to collapse
Yes
M.A.K said:
Which recovery did you use?
Click to expand...
Click to collapse
TWRP-3.0.3-0
M.A.K said:
Were you previously on COS13.1.2?
Click to expand...
Click to collapse
I was on the latest CyanogenMod snapshot.
I wiped data, dalik and cache, then installed lineage, gapps and su. Restoring a nandroid backup of CM13 did bring the wifi back again.
I then wanted to restore my backup of lineage, because I already transferred most apps and settings and don’t care to much for the wifi (hoping it will be solved in not too far future), but TWRP failed to recover, getting stuck while restoring data, only restoring the system partition. Strangely, after this, the wifi worked, however I experienced many FCs. After wiping data again, the wifi was broken again, the MAC adress showing as 02:00:00:00:00:00.
Wiping system, I tried to reinstall lineage without any extras, but TWRP just got stuck again with no progress being made after detection of the partitions. Strangely, restoration of the lineage backup worked now, including data The original problem persists, of course.

I mentioned COS13.1.2 specifically because it flashes partitions other than system that may affect your situation. CM doesn't. If you've had COS13.1.2 installed previously then these other partitions should be up to date.
If you're having inconsistent results using TWRP3.0.3 it may be worth trying 3.0.2.5.

ES File Explorer
Hello guys! I have a small problem. I installed the LOS 14.1 and now I have error in ES File Explorer, "Sorry test failed. This feature cannot run on your phone".
The su binary I already threw, and all files bin already threw. Help solve the problem!
p.s. sorry for my English

Endless Bootloop when using LineageOS and AOKP ROMs

Hello,
Since I got my XT1635-02 in April I have tried to use LineageOS and/ or AOKP. The problem is, when I flash either, I get an endless bootloop.
When I got the phone I:
Unlocked the bootloader
Flashed TWRP - the latest 3.1.1-0
Flashed Lineage ROM
I don't use Gapps - or I'd rather not - but at this stage I have flashed the Pico package
Then flash su-addon.
I've tried different combinations; only flashing LineageOS/AOKP but got the same result.
Stock images work fine for me. I even got to the point where I had to write a little bash script to flash all of the components in the correct order for the RETUS Nougat image.
Last month, by some fluke I got LineageOS to boot. However, I have no idea what I did differently, it just seemed to work that one time. However, I have been living off of that install for about 3 weeks and the OTAs even worked perfectly.
Today I got bored and decided to flash AOKP.
Booted in to TWRP
Wiped Dalvik, Sys, Data, Cache
Flash AOKP
Reboot
Bootloop.
Is there something wrong with my phone or is there something wrong with my process?
Any suggestions welcome. Thank you.

I remember​ that problem with Razr. Some custom roms were booting fine, some bootlooping.
The first workaround was to flash working one then without reboot flash desired one.
Later we figured out that wiping/formating partitions was the problem. Bootlooping rom couldn't read the file system. Solution was to not wipe or to wipe to the correct file system.
Sent from my XT1635-02 using Tapatalk

I think you may be on to something because I had flashed LineageOS after flashing the stock Nougat image. Still, would like a surefire way to just run a ROM. I've never had this issue on any other device.

I had it on Razr and just started to happen after one CM nightly build. Turned out that devs changed FS.