yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy Note5] mysticjp:
my poor note 5

the note 5 has a vulnerability with older revisions if you flash anything sometimes the cell signal will get disabled, samsung sent me one that i had no problem with then i sat on that one and asurion sent me and older revision of the note 5 so im having the no signal problem again so im sending this one back to samsung the n5 is perfect cept for this vulnerability =(

this is like the 5th time ive had to take my n5 to samsung and only once did they send me one that i never had this issue no matter what i did

weird any ideas anyone?

dou thinx i being haxed or its just a vulnerability?
[Sprint Samsung Galaxy Note5] TheMadScientist:
i have 3 note 5s used to build one and i had issues with a tmobile mb and the sprint one both had no sig my verizon one worked great

well i sold it guy spilled beer on it shorted out the verizon board. so i got the sprint board in it now and out of nowhere its got great signal the tmobile one has antenna issues i soldered a safty pin to the board for the hell of it and out of nowhere it gets full sig like im standing on top of the tower.

ive read a lot about the note 5 having horrible sig issues an i believe its in the antennas
[HTC One A9] MGfusion:
So I have heard a few people saying that after installing Android N on the HTC One A9 it in not downgradeable. Does this mean even after trying to flash the 6.0.1 RUU it won't downgrade
[HTC One A9] salvy':
Yes is possible downgrade but you need to flash first firmware 1.57 and then run the Ruu 1.57. 7.0 change the signature key so is a problem pass 1.57 to 2.18 and 2.18 to 1.57
[HTC One A9] MGfusion:
Ah I see. Thanks for the help
[HTC One A9] The_scam:
How would I flash the firmware? Can you tell me?
[HTC One A9] salvy':
Download the 1.57 ota extract the firmware and use fastboot here you find a guide http://android-revolution-hd.blogspot.it/2015/02/how-to-flash-firmware-package-on-htc.html
[HTC One A9] The_scam:
Yeah I did that already, but thanks. Running cm14 again
[HTC One A9] vljfreak:
error

hice todo como dice en la guia y ma tira este error

mini-sdk>fastboot flash zip firmware.zip

sending 'zip'... (1796952 KB) [isLargeZip: 0 fileCount: 1 / 1]

FAILdata too large, 1840079206 > 938115072

FAILED (data size is too large(1796952 KB) for device to download ZIP file 'firmware.zip'
[HTC One A9] vljfreak:
What is the procedure for downgrading from nougat to marshmallow locked bootloader and s-on
[HTC One A9] Wonders_Never_Cease:
Pretty sure this is not doable.. Maybe the ota firmware can be flashed,but not a chance I personally would take.
[ZTE Axon 7 Questions & Answers] gpz1100:
Solved - see post #9

---------------------------

Stock/rooted/Bootloader unlocked B29

After doing a factory reset either in android itself, or TWRP, the phone does not boot properly. Zte logo comes on, then stuck at the axon 7 logo after a few minutes, force a reboot, then it boots up in under a minute.

What am I missing here?
[ZTE Axon 7 Questions & Answers] stevecaboose:
What roms did you try flashing?
[ZTE Axon 7 Questions & Answers] gpz1100:
Who's flashing any roms? Factory reset != flashing roms :)

The os is fully stock except as specified.
[ZTE Axon 7 Questions & Answers] stevecaboose:
Well what about restoring a back up. If that happened to me the first thing I would do is restore my backup and try reseting it and if the problem continues then flash a rom to maybe overwrite data that is causing issues
[ZTE Axon 7 Questions & Answers] gpz1100:
Restoring from a backup works depending if full or partial restore.

Full restore (system/boot/data) = success

partial restore - wipe data then select system/boot only for restore = same issue as in the OP

I've left for as long as 5 min or even longer. What's strange is after forcing a reboot, it boots up within 30-45 seconds. Someone said in a thread about it possibly taking 10 min to boot up on first boot. Seems excessive, esp given the above. I've repeated this several times and it seems to be consistent. Forced reboot during this boot loop results in a very quick subsequent boot.
[ZTE Axon 7 Questions & Answers] stevecaboose:
I would try to unlock your bootloader and flash a rom just to see how it goes.
[ZTE Axon 7 Questions & Answers] gpz1100:
My bad, bootloader is already unlocked.

It's almost as though something on /data is corrupt the first time around.
[ZTE Axon 7 Questions & Answers] stevecaboose:
Yeah that seems to be whats wrong.
[ZTE Axon 7 Questions & Answers] gpz1100:
I was hoping to avoid doing a full firmware restore.

I grabbed the b29 update from zte's site a while back.

Using 7zip, extracted the update script to remove the lines for recovery and fastboot partitions. Left everything else alone. Repackaged and crossed my fingers.

Tried sideloading it into twrp but no go. Had to be copied to the sdcard.

Afterward, it was at the zte logo for a good minute or so, then the axon 7 logo came on. Within ~45 seconds I was at the language screen. Immediately went to the factory reset option after the setup wizard completed. This time again it rebooted in about 30-45 seconds. Tried a few more times for good measure -- identical results. Rerooted the phone with supersu 2.79 and repeated the above. Again, no issues.

So, this is really odd. The phone came with B27. Took the OTA to B29 then unlocked the bootloader, rooted, xposed. No other changes. In trying to figure this out, I even reverted back to the stock unpatched kernel (due to supersu patching), just in case that had something to do with it. I suppose something might of glitched in the ota process but there no was indications of any failures.
[ZTE Axon 7 Questions & Answers] amphi66:
So if one wanted to "dirty flash" the original ROM, exactly what modifications (& what rename) to the OEM B29 ROM? Thanks.
[ZTE Axon 7 Questions & Answers] gpz1100:
Other than the recovery and fastboot lines, there's a line towards the bottom about wiping user data. I'd remove that too.

There's nothing to rename, just removal of those lines, adding the update script back into the archive (in the same folder as original).

http://i.imgur.com/lZa4irW.png

Note: Unlike the ota updates, this script does no device validation at all (which is why it's twrp compatible).

Here's what the script looks like. Blank lines indicate lines I removed.

ui_print("Target: ZTE/P996A01/ailsa_ii:6.0.1/MMB29M/20161014.114339:user/release-keys");
show_progress(0.850000, 180);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
package_extract_file("ddr.img", "/dev/block/bootdevice/by-name/ddr");
package_extract_file("xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("lksecapp.mbn", "/dev/block/bootdevice/by-name/lksecapp");
package_extract_file("rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("echarge.img", "/dev/block/bootdevice/by-name/echarge");
package_extract_file("mdtp.img", "/dev/block/bootdevice/by-name/mdtp");
package_extract_file("xbl.elf", "/dev/block/bootdevice/by-name/xbl");

package_extract_file("adspso.bin", "/dev/block/bootdevice/by-name/dsp");

package_extract_file("sec.dat", "/dev/block/bootdevice/by-name/sec");
package_extract_file("NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
package_extract_file("splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
package_extract_file("cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
show_progress(0.100000, 10);
format("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "0", "/data");
set_progress(1.000000);
[ZTE Axon 7 Questions & Answers] StickMonster:
I have the US version of the Axon 7. TWRP 3.0.2, with locked bootloader, stock rom, no root.

Ultimately I want to follow this guide by [MENTION=319057]Oki[/MENTION], to root with safetynet:

https://xdaforums.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906

That guide says I have to have TWRP 3.0.3, so that's what I am trying to install.

I've already installed TWRP 3.0.2, following this guide, up through step A:

https://xdaforums.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379

Once that was installed I tried to flash the official TWRP 3.0.3, using both TWRP and axon7tool, and it seems to flash, but recovery boots to a black screen. I'm pretty sure it is in edl mode. Shouldn't I be able to upgrade TWRP this way?

So I gave in and downloaded the gigantic unlock kit, and tried to follow the instructions from [MENTION=5672995]jcadduono[/MENTION], except from TWRP 3.0.2. It fails trying to flash step 1 with an assert that product name isn't P996A0.

Help! What should I do next?
[ZTE Axon 7 Questions & Answers] jcadduono:
since you're in twrp you can open that step 1 full OTA zip in 7-zip and browse to META-INF/com/google/android and open updater-script file.

you will see a line starting with assert() somewhere, just remove that line and save, then flash it

alternatively you can find a stock P996A01 recovery, flash that, then flash the zips (unmodified) from there
[ZTE Axon 7 Questions & Answers] stevecaboose:
First unlock your bootloader

What I did was this... Already have the old twrp as you do. I got the official twrp for the axon 7 global version (even though my phone is U). I then flashed it through fastboot. I never flash recovery images through twrp. It's never worked for me on many phones. Can't go wrong with fastboot though. Good luck. I recently got my bootloader unlocked and rooted and it was a nightmare digging through these many slightly different tutorials so I know this process is a pain
[ZTE Axon 7 Questions & Answers] Oki:
You need to install again the unofficial TWRP 3.0.2-2.

1. Download it to your computer from http://d-h.st/dgWW (it is signed so it is recognized as a ZTE recovery and bootloader won't reject it) and extract recovery.img from it.

2. Connect your phone to your computer and boot into bootloader. In your computer type the command

fastboot flash recovery recovery.img

At this point you will have unofficial bootable TWRP again. However you have to unlock your bootloader by following the DrakenFX's guide here https://xdaforums.com/axon-7/how-to/bootloader-unlock-t3437778. You can flash the file in the guide from TWRP too.

Only after the bootloader had been unlocked you will be able to use the official TWRP. The guide to have root+safetynet requires unlocked bootloader. You should have pay attention to the requirements before initiating the steps. However do not worry, your state is easily fixable following the steps.
[ZTE Axon 7 Questions & Answers] StickMonster:
Thank you everyone. I really appreciate the responses. I had already figured out how to re-install the unofficial twrp, so I just followed [MENTION=5672995]jcadduono[/MENTION]'s modified instructions and got my bootloader unlocked and the official twrp. I didn't realize the official twrp required the bootloader to be unlocked. I was going to get there eventually anyway, though :).
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] xmatharux:
Hi All,

not sure if this is normal (dont think so) but i have annoying battery drain and dont know what i can do to fix it.

My screen on time is around the 2hr 30 mins mark before i will need to recharge - ive seen people getting 6 hours some how??

ive uninstalled all useless apps, wiped cache and all the normal things but still not worked (even location services off)

I just had a look today on WakeLockDectector and it appears it has something to do with the google app?

Does anyone know a solution to this battery drain? - cell mobile radio seems to keep my phone awake??

[IMG="Battery summary"]https://s25.postimg.org/nrtwh4233/Screenshot_20170112_124135.png[/IMG]

[IMG="Awake time"]https://s25.postimg.org/nt3uaj3wv/Screenshot_20170112_124148.png[/IMG]
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] Minerael:
You're not the only one. I'm struggling with it since I bought this bloody phone. Had even exchanged battery.

Facing the same problems as you do. Perhaps our models are broken somehow?

It's hard to say...

Anyway, no clue what's going on.
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] sushi-gee:
Same problem just started. Was doing great after factory reset but along the way it's slipped
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] rahulje9:
mine does vary alot.lowest was 1.5hr and max was 5hr.

i guess the problem is with marshmallow.hopefully it will be fixed with next update
[Oppo F1] MiniBlu:
CyanogenMod 13 is a free, community built distribution of Android 6.0.1 (Marshmallow) which greatly extends the capabilities of your phone.

These are unofficial Beta builds of CM13 for the Oppo f1f.

To hear about the latest updates and changes to CyanogenMod as a whole, you can follow +CyanogenMod on Google+!

My change log is in post #2.

#include <stddisclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

What doesn't work yet

- You tell me

Installation Instructions

You must be on 010 ColorOs firmware to use this rom. If you are on a newer version of ColorOs and hvae problems with things like wifi you can flash the firmware from that version with the zip file in the optional extas post (post#3)

1. You must unlock your bootloader using magictricks.zip supplied by [MENTION=5314976]uberlaggydarwin[/MENTION].

2. You must have a custom recovery installed that allows SELinux. Get TWRP build for Oppo f1f from here.

3. Download the current Oppo f1f build from here.

4. Get Gapps from here.

5. Download the latest kernel update from here.

6. Fully wipe your device from TWRP Recovery. eg WIPE > SWIPE to Factory Reset.

7. Install Rom , Gapps and kernel update from TWRP Recovery then Wipe dalvic and cache then Reboot.

Credits

- [MENTION=5314976]uberlaggydarwin[/MENTION] Without all his work this would never be possible. So please thank him. The bootloader unlock and original kernel for this is all his work.

- CyanogenMod Team.

If I have missed anyone please let me know and I will happily add to the credits.

XDA:DevDB Information

CM13 for Oppo f1f, ROM for the Oppo F1

Contributors

MiniBlu, uberlaggydarwin

Source Code: https://github.com/MiniBlu

ROM OS Version: 6.0.x Marshmallow

ROM Kernel: Linux 3.10.x

ROM Firmware Required: magictricks bootloader, twrp recovery, ColorOS V2.1.0i - F1fEX_11_160507 firmware

Based On: CyanogenMod

Version Information

Status: Beta

Current Beta Version: Beta1

Beta Release Date: 2017-01-16

Created 2017-01-22

Last Updated 2017-02-21
[Oppo F1] MiniBlu:
Change Log

- 21 Feb 2017 - Updated kernel Release (Based on latest CM re-based kernel source)

- Battery battery life and performance

- Improved audio
[Oppo F1] MiniBlu:
Optional Extras

- Updated Kernel for the 16 Jam 2017 release. Here is and updated kernel that you can flash on top of the 16 Jam 2017 release. Just flash it from TWRP then wipe dalvic and cache and reboot (make sure your phone is fully charged first as re-optimizing all you apps will take a lot of battery).

- ColorOs 010 firmware can be flashed with this zip.
[Oppo F1] AnantNigam:
Does on screen and off screen gestures work? Screenshots plz
[Oppo F1] MiniBlu:
Screen off yes screen on no. I might do some screenshots at some stage but its just stock cm13, they all look the same. Its only a beta testing version, still a lot of real work to do on it before I worry about things like that.
[Oppo F1] Caferatte89:
Thank you! So this is the problem that I've had when I use the rom:

- Sometimes I cannot unlock the lock screen settings to reset the new screen lock.

- The Camera app sometimes will crash when I try to record.

- The battern drain is quite fast. (as you mentioned)

Other than these, I think the rom is really great.. :o :good:
[Oppo F1] AnantNigam:
Do we have to install old firmware to make wifi work?
[Oppo F1] MiniBlu:
If you have the latest update, then yes. Just flash the color is ROM mentioned in the requirements section of the op first. I'll add a smaller firmware only zip to the op tomorrow.
[Oppo F1] chetan_p:
Hey

Nice to see development taking place for our oppo f1. Thnx fr ur hard work

I just wanted to know if VOLTE working?

Thank you
[Oppo F1] Hexyth:
Nice ROM , Thanks!

I found some problems :

-Camera

Crash when I switch from front camera to back camera and vice versa , crash too when I switch from photo mode to video mode and vice versa.

-Battery

Battery drains fast , and the charging time is becoming fast too :eek:

sorry for my bad english
[Oppo F1] Jamie_oppo:
Thanks so much you two for giving this's phone hope.

I was having the same problem with battery life. Maybe 2 hours from 100-0 then miniblu suggested. Turn off all the settings in display and lights that would drain power. Yesterday I got 12 hours out of it with lite usage . The battery expected life in setting isn't correct so don't trust the expected time (it drains to 80% in like 30 min then the rest can last another 12 hr on lite usage).

-little bugs I've noticed- camera app was a bit buggy first time I opened it up. (Reboot fixes it)

-when u leave to camera app what was left on the screen is your wallpaper for 2 seconds.

I can use this phone no problems everyday. I would recommend to anyone. Just make turn of any unessasary settings in screen off and it's prefect. I found nothing else wrong with this rom.

Thanks so much for this Minblu and uberlaggydarwin
[Oppo F1] revesxxa:
This seems like the best place to ask:

Optus in Australia released a network locked version of the Oppo f1f with some startup/shutdown branding for a reduced cost. They also disabled the second SIM slot that this phone has in other countries.

My question is, could the ability to use the second SIM slot be activated by using a custom ROM such as this one, or is it more likely that Optus have crippled or possibly even removed the actual components from the handset?

Thanks, and thank you for the development effort you're putting in to this. I look forward to trying it out over the weekend.
[Oppo F1] tianly_199:
Audio crackling sound

Thank you very much for the effort and time that you put in making this rom possible.

I have a question.. is anybody else experiencing audio problems when using headphones or earphones? There's like a crackling sound while I'm listening to music.
[Oppo F1] Jamie_oppo:
Yeah. Go into audiofx and turn down the bass or vitualizer until it doesn't make that noise anymore?
[Oppo F1] tianly_199:
I've already tried it but it didn't work. There's still this annoying sound like static. I thought it was the phone so I reverted back to coloros but when I tried, the sound is back to normal so I'm guessing it must be a bug in the cm13 rom.
[Oppo F1] mikeysteele:
IIRC Oppo claimed that the Optus F1f had the second SIM hardware physically removed.
[Oppo F1] AnantNigam:
One last question please does VoLTE works with this rom?
[Oppo F1] nj25668:
Problems

-Camera crash and maybe not connected

-CPU always run full load (very bad problem)

-battery drain (because cpu full load always)

-more heat (because of cpu too )

-screen backlight always on when i turn off charging

-often Battery not +℅ when i turn on charging

-in choose manual network menu not show 4g signal for select

-cpu hotplug not support in cpu tuner apps

And everything is fine :good::good::good:

This rom better than project spectrum because can boot in to twrp recovery

I hope you will fix all problems

And port rom to cm14-14.1 soon

-----------------

Sorry for my bad English
[Oppo F1] bamz1117:
It so awesome!!!

I've been waiting for this on my f1 , a cyanogenmod 13..thank you so much MiniBlu and of couse [MENTION=5314976]uberlaggydarwin[/MENTION] the great developer...i will install it in this weekend..thanks a lot again!!!!:good:
[Oppo F1] durrellb:
It's to do with the digital mixers distorting the sound as it boosts it. In system/etc/ there is a file called mixer_paths_mtp.xml, where you can edit volumes through the speakers and headphones. A quick fiddle around with RX values makes it slightly better, but it's still there.
[Oppo F1] Jamie_oppo:
Here's a screenshot if that helps. Yeah the battery weird. I think its something we can't see that's draining it. I get 1hr screen on time from 100% to 40% then 2hr for 40%-10% its so weird.
[Oppo F1] Jamie_oppo:
http://techbeasts.com/cm-fixed-camera/

I'm looking for a camera solution

I flashed that zip in the url. It optimises apps and it booted up. The camera says its seams a bit better. I'll report back soon
[Oppo F1] Jamie_oppo:
New twrp image 3.1.0 available. I'm going to test it out. It flashed and booted successfully.
[Oppo F1] Y@SH:
Thank you so much mate , yes please report back wedr it makes any improvement :)
[Oppo F1] Jamie_oppo:
It installs another app which works for like 1 minute then doesn't work again. But with the main camera app. I never get the error. Can't connect to camera. But it does crash still. So what its fixed is that cannot connect to camera
[Oppo F1] Jamie_oppo:
Anyone got a good setup in kernel auditor for battery life?
[Oppo F1] Jamie_oppo:
The zip file I flashed from the link above. After a day of use. I found that the camera will not crash after taking pictures but the only time it crashes is when u flip camera too many times.
[Oppo F1] Jamie_oppo:
What's everyone else's screen on time. I'm not sure if this apps I have on here is draining the battery. Or if it is normal.
[Oppo F1] ajparag:
my battery life has improved after a couple of days. not as good as i would want it to be but still its manageable now. however, i am facing a weird issue with GPS. my gps is not working well. i am assuming it can also be a reason for battery drain for the users. battery drain due to gps sync is one of the issues in CM13.
[Oppo F1] Jamie_oppo:
Have a read of this from page 10 onwards

https://xdaforums.com/oppo-f1/development/dev-cyanogenmod-14-1-oppo-f1-f1f-t3519981/page9
[Oppo F1] ajparag:
I have turned off everything in Settings >> Display and Light. Give it a try and post here if it saves you battery.
[Oppo F1] Jamie_oppo:
Yeah that's what we recommended everyone do when u flash this rom. It helps with battery alot
[Oppo F1] ajparag:
then we should include it in the first post
[Oppo F1] TechExhibeo:
Even after flashing linked firmware from thread

phone is not able to complete the bootup after bootanimation.

phone goes to never ending bootloop.

-TechExhibeo
[Oppo F1] hzzyebny:
Same goes here, the issue with GPS & AGPS is unanswered. There's no solution to it so far. You'll definitely gonna have a problem using any Apps that air mainly depending on your GPS & AGPS such as Grab, Uber, Tinder, Swarm, etc. It seems geolocation/geofencing is a problem here.
[Oppo F1] Jamie_oppo:
The cm14.1 rom is alot better on agps. the lineage os oppo f1 thread and read from page 9 until the end. The rom Is alot better than cm13. https://xdaforums.com/oppo-f1/development/dev-cyanogenmod-14-1-oppo-f1-f1f-t3519981/page9

It fixes the agps
[Oppo F1] Jamie_oppo:
Read from page 9 until the end because there are some bug fixes during them
[Oppo F1] Shadow Gamer98:
GPS didn't work plz help