yashsingh1/xdaforums huggingface dataset:
[ONE Q&A, Help & Troubleshooting] Heisenberg:
I'm fairly confident that the problem here isn't due to a naturally occurring bug caused by CM or OnePlus, it's most likely you just have the wrong firmware/modem for whatever ROM you're on. 99% of the time this "bug" is caused by user error. It isn't their fault that users flash away and end up with misaligned firmware, causing this to happen. And no, I'm not trying to defend either company, I really don't like either. You mention using TWRP to flash which is probably half your problem. I'm assuming you're on a Lollipop ROM, the best idea is to download the latest stock images from here:

https://www.androidfilehost.com/?fid=24052804347802352

Then flash only the firmware components with fastboot:

fastboot flash aboot emmc_appsboot.mbn
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot reboot
[ONE Q&A, Help & Troubleshooting] therealgiblet:
I had completley stock 11S with lots of xposed modules that weren't initially supported on 12.1.

Eventually about a couple of weeks ago after nearly going insane due to the bug with the keyboard I thought sod it - I'll 'upgrade' to 12.1

I upgrade to 12.1 and didn't notice the data issue (constant ! by signal bars and sporadic data connection) - just thought my network provider had problems.

A few days ago I got so annoyed with the data issue I looked online and saw various threads detailing 'issues' with the 12.1 modem.

The fix people were quoting was to install an older modem. I installed 241 and this fixed my mobile data issues. Unfortunately a side effect was that the proximity sensor was broken.

This is what I'm trying to fix.

I've just reflashed the 241 modem with TWRP 2.8.60 after downgrading from 2.8.7.0 and now my screen is not black in phone calls - so that's a great success.

Gestures are the only thing that aren't working (not the end of the world but I used the light shortcut 'V' on screen a lot).

If I could fix that I'd be very happy. I still think the proximity sensor isn't quite right as when I run a test on it the values remain static no matter how close I place my hand or how I touch the screen.

Thanks anyway
[ONE Q&A, Help & Troubleshooting] Heisenberg:
How did you upgrade from CM11S to COS 12.1? Via TWRP? Via fastboot?
[ONE Q&A, Help & Troubleshooting] therealgiblet:
Uninstalled Xposed and all modules then followed the OTA update process including all incremental updates and patches.

You're going to tell me to do a clean install aren't you? :) I still don't think that will fix the issue with the modem as both these threads

http://xdaforums.com/oneplus-one/development/radio-updated-modem-radio-files-oxygen-t3072516

http://xdaforums.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734

have multiple reports of the same problems irespective of installation method... and they still require you to downgrade or revert to previous modem to fix the data and signal problems with the modem.

This is turn messes up the proximity and gestures sensor.

But I might be wrong (probably am :) )...
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Ok, but did you flash the update with TWRP or with the stock recovery? There may not be a need for a clean flash, I need to diagnose the cause in order to determine that though.
[ONE Q&A, Help & Troubleshooting] therealgiblet:
TBH - I didn't pay much attention to the whole upgrade process whilst it was happening.

I had TWRP installed on 11S but I don't how the system automated the update or what recovery it used.

I did have to reinstall TWRP after the update to 12.1 as I noticed the TWRP recovery had been overwritten and had reverted to the stock one...

Sorry not much help.
[ONE Q&A, Help & Troubleshooting] Heisenberg:
TWRP would have installed the update, and because you were on 2.8.7.0 it was unable to flash the modem (that version can't flash modems). That's almost definitely what caused your initial problem, you were left with a KitKat modem while on a Lollipop ROM. The update did flash the stock recovery but that occurred during the boot afterwards. So the people who advised you to flash an older modem were incorrect, they were assuming you were on the latest modem and that that modem was causing the problem, when really it was the leftover KitKat modem causing the problem. At this stage you can go ahead and flash the files I mentioned earlier, and you can do so without having to wipe anything, this should ensure that everything is in line as it's meant to be.
[ONE Q&A, Help & Troubleshooting] therealgiblet:
Ok thanks a lot - I'll give it a go later when I'm not at work. Thanks again
[ONE Q&A, Help & Troubleshooting] Heisenberg:
No problems, let me know how you go.
[ONE Q&A, Help & Troubleshooting] therealgiblet:
C:\CM12>fastboot devices
9b612b68 fastboot

C:\CM12>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.018s]
writing 'aboot'...
OKAY [ 0.023s]
finished. total time: 0.044s

C:\CM12>fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.022s]
finished. total time: 0.039s

C:\CM12>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.827s]
writing 'modem'...
OKAY [ 0.717s]
finished. total time: 2.548s

C:\CM12>fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.023s]
finished. total time: 0.039s

C:\CM12>fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
OKAY [ 0.015s]
finished. total time: 0.024s

C:\CM12>fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.011s]
writing 'rpm'...
OKAY [ 0.021s]
finished. total time: 0.035s

C:\CM12>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.330s]
writing 'oppostanvbk'...
OKAY [ 0.149s]
finished. total time: 0.484s

C:\CM12>fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.017s]
writing 'tz'...
OKAY [ 0.022s]
finished. total time: 0.041s

C:\CM12>fastboot reboot
rebooting...

finished. total time: 0.008s

Right - done the above with the 'cm-12.1-YOG4PAS1N0-bacon-signed' firmware.

Nothing has changed - in fact the phone has reverted to having a black screen again in a phone call and gestures still do not work.

I checked 'About Device' in the settings and they seem no different from the ones previous to the fastboot flashing. I have screenshots but I just thought I'd clear Dalvic and phone is currently optimizing apps.

Sensor test - showed all sensors working except the Proximity/Gesture sensor - values remained static.

---------- Post added at 02:52 PM ---------- Previous post was at 02:29 PM ----------

Sensors
[ONE Q&A, Help & Troubleshooting] therealgiblet:
Gave up with a fix and installed 12.1 from scratch after wiping all partitions.

Everything is fine now... data, signal and gestures!

Thanks anyway
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Out of interest, which build were you on at this point?
[ONE Q&A, Help & Troubleshooting] therealgiblet:
LMY48B -- same as current build I'm on now. I've no idea why I had those issues but fresh install has worked like a charm!
[ONE Q&A, Help & Troubleshooting] therealgiblet:
Ok - 2 weeks later noticed (no changes to phone since rebuild) that the ! is back often on data connection and a reboot will solve the issue (toggling LTE, Airplane and anything doesn't resolve problem).

Still, reading the modem thread there is no proper fix for this problem and judging by the threads on the OnePlus forums and here there isn't one planned either.

So annoyed. My mate has exactly same problem - we're both planning on changing to Nexus5X but still have to live with this for a while longer. Really annoying.

'Never settle' - yeah that's because you will constantly be rebooting your phone to get data back.... 'Never oneplus, again' - that's my new tagline.
[Android Q&A, Help & Troubleshooting] Jaling Orion:
Since Lenovo has no intention of updating the A8-50 5500-F ideatab to Android 5.0, I've been looking to root the tablet and throw a new ROM on there. I've seen a couple forum posts on here and done some research and the steps to begin this are pretty much agreed upon with everyone.

1) Enable debugging mode

2) Install drivers

3) Use (Enter root program here)

4) etc.

The problem is happening at the first couple steps. If debugging isn't enabled on the tablet, my computer can see it. It accesses the device's data without issue and Device Manager shows a good driver installed. When I switch it to debugging mode, it loses access to the tablet's data and device manager says the device doesn't have any drivers installed. Also, software like Lenovo Smart Assistant and Kingo ROOT think that the device isn't in debugging mode when it is and keep saying to make sure debugging is enabled. Here's what I've tried so far to mitigate it and where it fell through:

XDA Forum: All about - Lenovo A5500 - When I try to use the drivers provided, Windows states that there are no drivers available in the folder I tell it to look from.

XDA Forum: [TOOL][WINDOWS]ADB, Fastboot and Drivers - The install completes, but when I try to copy the steps provided here, there is no ADB selection.

XDA Forum: [ROOT] Framaroot... - I get error #9 which means it won't work for my device with it's current version when I try to use Borimir.

Youtube: Install driver for Android Tablet - The AdbDriverInstaller software doesn't actually see the device when I plug it in. This is either in or out of debugging mode. Pretty much the same issue I mentioned above with Kingo ROOT and Lenovo Smart Assistant.

Additional steps:

Downloaded SuperSU from the Play store - I get the error "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

Downloaded Superuser from the Play store - There's just no apps in the list

I'll keep looking, but I seem to have run out of ideas myself and what I can find in my research is just starting to repeat itself. Has anyone seen this before? I'd really appreciate any help.

Edit: Might help if I include the current device info...

Device Information:

Model Number:

Lenovo A5500-F

Android version:

4.4.2

Kernel version

3.4.67

Build number

A5500F_A442_000_029_150408_ROW
[Android Q&A, Help & Troubleshooting] dantheman9703:
http://www.kingoapp.com

Kongo root works somehow. Not sure about a ROM though?
[One (M7) Q&A, Help & Troubleshooting] Julian1738:
Hey , im new to rooting and the forums so sorry if somethings are not properly explained.

I recently managed to root my uk variant m7 unlocked to any service with the latest twrp recovery.

I have recently found the venom rom which i would like to install to futher customize my rooted device, but i need to upgrade my android to 5.0.2 and i am currently on 4.2.2.

in the toolbar it says 'system update avaliable' and after installing it says 'system update ready' and im guessing this will bring me to 5.0.2 firmware. after clicking on it it reboots my phone and for some reason enters the recovery. from this point i do not know what to do.

so to summarise, i need to upgrade my m7 from 4.2.2 to 5.0.2 nut when i do it enters my twrp recovery and i do not know what to do

system details:

HTC One M7 UK variant unlocked to any service

rooted with SuperSU

Stock rom (4.2.2)

Stock kernel

Thanks ;)
[One (M7) Q&A, Help & Troubleshooting] alray:
no, there are a lot of updates between 4.2.2 and 5.0.2

Because the ota update is supposed to be flashed from stock recovery.

You can't update your phone in its current status. You need stock recovery installed, unmodified /system files and /data/preload which is deleted during the htcdev bootloader unlock process. You'll probably need to use a RUU or something else.

Unfortunately, this is not really relevant info, post the output of "fastboot getvar all" command, remove your IMEI # before posting.
[One (M7) Q&A, Help & Troubleshooting] Julian1738:
so i have to unroot my phone

great this is going to take a while :/

if i factory reset my phone will it remove the bootloader and root?
[One (M7) Q&A, Help & Troubleshooting] alray:
What? You might want to read about what a bootloader is ;)

A device without a booloader is called a paperweight

A factory reset only wipes user data. Root files are stored in /system partition which is not affected by a factory reset so short answer no, like I said you'll probably need a RUU or something else (stock odex rom/nandroid backup/guru reset rom) to reset your phone back to stock. Post the output of "fastboot getvar all"
[One (M7) Q&A, Help & Troubleshooting] tkdfilipe:
Its possible to download the update elsewhere and install it through twrp recovery?

If yes, where i can find these updates in zip form?

If not, what's the simple option to install the update?

thanks
[One (M7) Q&A, Help & Troubleshooting] alray:
If your phone is S-off, you can download the Ota zip files and install them incrementally (can't skip a version) using stock recovery. That doesn't change the fact that all files in /system and /data/preload must be unmodified.

Imo, the simplest way to update if your phone isn't stock is with a RUU. If your phone is stock, reflash stock recovery and update with Ota, if it's stock and soff you can update with Ota zip files if you can find all the ones you need.
[Verizon Samsung Galaxy S6] deliberate.dev:
I downloaded the Flashfire apk in hopes I'd be able to flash from my phone without recovery and every time I try going into the app, it instantly force closes. Has this happened to anyone else?
[Verizon Samsung Galaxy S6] twiz0r:
It's probably because your bootloader is unlocked. :)

Honestly though I haven't heard of this.

I'm assuming you have the latest version and that you are rooted correct?

Has it worked at all on your setup?

Have you tried factory resetting, installing, and trying?

Maybe this might help someone who is more capable of helping than I am.
[Verizon Samsung Galaxy S6] deliberate.dev:
Have the latest version and I'm rooted. I've tried multiple times. Ah, I guess I'll just continue trying.
[Verizon Samsung Galaxy S6] krelvinaz:
No issue with stock rooted.
[Verizon Samsung Galaxy S6] twiz0r:
No good. I knew one of the last 3 updates had a force close issue on 64 bit fixed. Was hoping it was that easy. Hopefully someone else will pop in for ya
[Verizon Samsung Galaxy S6] deliberate.dev:
Thanks
[Verizon Samsung Galaxy S6] deliberate.dev:
My supposed "unlocked bootloader." Ha! You got me laughing.
[Verizon Samsung Galaxy S6] twiz0r:
I had to throw that in there on ya. Sorry :)

I'm not always an @$$hole I swear :)
[Verizon Samsung Galaxy S6] deliberate.dev:
Good to know. :)
[Verizon Samsung Galaxy S6] Tulsadiver:
There is one thing you might try. Delete the app. Go to your root folder data/data and delete the eu.chainfire.flash folder. Download and install the app again and see if it works.
[Verizon Samsung Galaxy S6] deliberate.dev:
Tried your suggestion, still doesn't work. Oh well, I'll just have to wait til something else comes along that'll let me flash.
[Verizon Samsung Galaxy S6] riker147:
Where did you download the apk from?

What version is it?

When you say it "force closes", are you getting an error message?
[Verizon Samsung Galaxy S6] deliberate.dev:
Finally got it working... then I go and upgrade my phone last night. Can't even use it til a new root method comes out.
[Verizon Samsung Galaxy S6] jonthn41:
how did you get it working?
[Verizon Samsung Galaxy S6] AlphaDroidzer:
setting your time to the year 2013

cant be connected to the internet
[Verizon Samsung Galaxy S6] jonthn41:
why 2013 ? because thats when the device had its last software update?.. im trying to figure out how to get flashfire working on my tablet
[Verizon Samsung Galaxy S6] AlphaDroidzer:
from what I gathered on google....

Devs stop supporting free version

if you dont want it to crash then buy pro
[Alcatel Pop C3 ROMs, Kernels, Recoveries, & Other ] kirito9:
* * * * * * * * * * * * * * * * * * * * * * * * *

PhilZ Touch 6 Recovery

CWM Advanced Edition 6.x

* * * * * * * * * * * * * * * * * * * * * * * * *

​

DISCLAIMER:

Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.

Basic computer skills are required and minimal knowledge about the phone and phone utilities also.

Make sure that whatever you do, you are doing it at your own responsibility.

Installation see here

Main PhilZ thread here and more info here

If you set a recovery password and forgot it read here

Aroma File Manager

Download aromafm.zip from the attached files and place in clockworkmod/aromafm/aromafm.zip of external storage.

How to get multi-flash to work:

Download the multi-flash zip from below and extract it to clockworkmod/ so then the folder looks like this

clockworkmod/multi-flash/flash/ Place zips here....

It won't work if it isn't in that format.
[Alcatel Pop C3 ROMs, Kernels, Recoveries, & Other ] kirito9:
................
[Nexus 7 (2013) Android Development] oadam11:
Ground Zero Roms presents -Tesla- for flo

--> Ground Zero ROMs G+ <--

Visit The G+ Community for screenshots, news, downloads, bugreports, wallpapers, bootanimations, ....

Google Plus Post

Android File Host Download

SlimPie
RRO Layers
Custimizable QS Tiles
SlimRecents
Slim's Power Menu
Slim's Nav bar and Hardware keys configuration
Animation Control
App Circle Sidebar
Lockscreen Weather
Screenrecorder settings
Kernel Aduitor built in
Plus more

​

kernel source
[Nexus 7 (2013) Android Development] IcipherPT:
Going to try gzroms on shamu and flo :)
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks...Flashed & everything is running fine...?

Thanks for your hard work..
[Nexus 7 (2013) Android Development] Lawlrus:
Anyone able to always show menu key and have it operate? Doesn't seem to do anything for me
[Nexus 7 (2013) Android Development] quickdraw86:
Works fine for me, works great in third party apps too. Not sure why the behavior of yours would be any different unless you use xposed or other mods...
[Nexus 7 (2013) Android Development] Lawlrus:
Nah I'm not using anything of the sort, and yeah I dunno what the deal is. I tried both apex and nova prime. The only app I seem to have it work with it the XDA app.

I'll try reflashing.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Much appreciated...
[Nexus 7 (2013) Android Development] cujo6801:
Ran this on my N6

Solid ROM..

Thanks

Sent from the "DOG" pound
[Nexus 7 (2013) Android Development] quickdraw86:
Gave Tesla 1.8 and tipsy a try the other day, I prefer Tesla due to a few small differences, but GZ ROMs make and has made great ROMs for flo. Thanks.
[Nexus 7 (2013) Android Development] quickdraw86:
Bump for excellence. Tipsy 1.4 just came out, giving that a run right now, but hope we see an update nonetheless. Tesla is sick.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Think tesla is not going to be on a regular update cycle...

I agree, Tesla just pips tipsy...Although I love the idea of visiting the bar as opposed to rom settings...
[Nexus 7 (2013) Android Development] quickdraw86:
That's the impression I got too. I saw that other devices are up to Tesla 1.9.1, and got a bit jealous lol. In all seriousness though, the last few gz rom releases for flo have few dls. Understandable why they don't build flo more regularly. Tipsy 1.4 is awesome, but I always preferred Tesla.
[Nexus 7 (2013) Android Development] quickdraw86:
View attachment 3436122

Tesla 2.0rc is up!

https://www.androidfilehost.com/?fid=24052804347792189
[Nexus 7 (2013) Android Development] SHABBYLEA:
It's running very well...only a couple of hours in but very impressed..

Quick edit: can't seem to get clear all button to work from bottom right location... Anyone else?
[Nexus 7 (2013) Android Development] quickdraw86:
I use slim style, but decided to check it out on stock, and, yeah, bottom right clear all position is unresponsive on stock.

Absolutely excellent ROM, many thanks to GZ ROMs.
[Nexus 7 (2013) Android Development] SHABBYLEA:
May also be a touch sound issue in certain configs...

Anyway...not bad for a blind build I think... In fact excellent...
[Nexus 7 (2013) Android Development] quickdraw86:
I don't ever use system sounds, can't confirm. Gesture input doesn't seem to work on the stock keyboard, may just be due to the gapps I use, may try a different package or take a look at the .libs in /system/app/latinIME. Overall, awesome though, like the light theming and reboot animation a lot. The kernel adiutor tile and breathing notifications alone are huge additions, not to mention the theming.
[Nexus 7 (2013) Android Development] SHABBYLEA:
As you say, overall, fantastic work...

As to maybe your gapps issue, I would recommend du gapps clear/tbo...since their last update I've flashed them on cm/aosp with no issues whatsoever...
[Nexus 7 (2013) Android Development] quickdraw86:
Yeah, I like those, but am such a minimalist that I prefer tk pico. I prefer updating the limited gapps I use through the playstore as opposed to alternative methods.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Just checking in...I would recommend any flo user to give this a try...there are a couple of niggles, but nothing major...excellent ROM...

Thanks to all involved...
[Nexus 7 (2013) Android Development] quickdraw86:
Indeed. I think Martin built the latest. One of my all-time favorite ROM projects.

As a follow up to what I posted before, it's not a latinIME .lib issue, but has to do with the modded AOSP keyboard app. Gesture type doesn't work with the included AOSP keyboard, but I've found everything else I use to be excellent and working perfectly. I agree, highly recommended to anyone on flo.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Yep..What impresses me is this is a blind build...exceptional...
[Nexus 7 (2013) Android Development] quickdraw86:
In other GZ ROMs news, Tipsy 1.5 is up.

https://www.androidfilehost.com/?w=files&flid=34891
[Nexus 7 (2013) Android Development] quickdraw86:
Tipsy 1.6 is up.

https://www.androidfilehost.com/?fid=24052804347799236
[Nexus 7 (2013) Android Development] oadam11:
New build is up in the op. Enjoy!
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks for the latest...One of my fave ROMs...
[Nexus 7 (2013) Android Development] oadam11:
Hey guys. New build in the op. Ota updates is now available. In subsequent builds, you will be able to download the update straight from the ROM. Enjoy!
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks... Just DL'd from g+ link...
[Nexus 7 (2013) Android Development] quickdraw86:
All hail Tesla, and [MENTION=5495092]oadam11[/MENTION] is the man. That is all.

Edit: if anyone's curious, dirty flash to 2.1 from 2.2 seems okay, just needed to reinstall gapps.
[Nexus 7 (2013) Android Development] oadam11:
New build is up in the op. If you are on v2.2.0. you can use the ota to download the update. Enjoy!
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks oadam, great work...

Thanks again...
[Nexus 7 (2013) Android Development] Nomad1600:
Past user of Slim, Screw'd and Broken ROMs trying out the latest Tesla. So far, very good. Battery seems especially good, even immediately after flashing. Relearning RRO Layers and patiently waiting on the next version of Sublime. But great job devs!!
[Nexus 7 (2013) Android Development] Nic2112:
This ROM is amazing, my favorite by far of everything I tried.
[Nexus 7 (2013) Android Development] Nic2112:
Layers itself seems to have problems at times but that's not ROM related at all. I'm very impressed with this. I reflashed clean and will stick to stock colors.