Develop Bugs

Updating twrp without a pc ?

My laptop blew up a capacitor, i have twrp 2.6 x x i we need 2. 7 x x for cm11. Is there a way to update without a pc ?

Download it on the kindle, flash the zip from inside of twrp, reboot into twrp again and you will notice the version is newer. If you have issues downloading the zip on your kindle just tell me I could temporarily host it somewhere for ya.
Sent from my Amazon Kindle Fire HD using Tapatalk

aakashba1001 said:
My laptop blew up a capacitor, i have twrp 2.6 x x i we need 2. 7 x x for cm11. Is there a way to update without a pc ?
Click to expand...
Click to collapse
you can download HashCode's TWRP Here:
http://forum.xda-developers.com/showthread.php?t=2218802
and install from your current TWRP, just as you flash a ROM.

Thanks guys
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?

aakashba1001 said:
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?
Click to expand...
Click to collapse
CM nightly build works good for me, you don't need to wiping new buld everyday, just choise one.
CM team will release a new month build every month, that build will be better than nightly build.
It takes time for the CM team to build a ROM with no bugs, so, just be patient.

I installed the 4/14 unofficial CM11 build that Hashcode posted over in development and am stunned at how well it works! I'll be sticking with this one for the interim. The TWRP upgrade is necessary, but Hashcode made it easy (see link in gatalon's post). In my case, I think it may have even fixed a long standing issue I had.
I've had my kindle HD 8.9" for over a year now, and have always been disappointed with it's performance. Even after I rooted it and put the CM10.1 build on it, it still exhibited weird sluggish, unresponsive behavior. This upgrade to TWRP 2.7 and CM11 has made all the difference in the world. All the weird sluggishness is magically gone.
It was noticeable as soon as I used TWRP 2.7 to wipe everything out. I'm half suspecting I had something wonky going on with the file system that wasn't getting addressed with the older version of recovery. I noticed 2.7 explicitly states that it's calling mkfs during the wipe process where the older version didn't. My uneducated theory is that the older version, 2.6.0.0, just deleted everything where the newer version is actually re-formatting the partitions. I could be way off base though. Just happy it's finally working like I thought a piece of hardware like this should! :victory:

aakashba1001 said:
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?
Click to expand...
Click to collapse
No wipe is needed (normally) when updating from one CM official nightly to a subsequent one. It will even detect if the engine has changed and recompile the davlik cache as needed. Personally, I'm a big fan of wiping cache (and only cache) with each new build and I also install any update PA GApps when available ( http://forum.xda-developers.com/showthread.php?t=2397942 ).
Caveat emptor: The CM team makes ever effort to make builds backwards compatible, but always take a backup and be prepared to do a factory reset / data wipe. It very rarely is needed, but you don't want to need a backup and not have one!

If the problem hasn't already been solved, here is an alternative: fireflash. Look it up.
Sent from my Amazon Jem using Tapatalk

[Q&A] [ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies

Q&A for [ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Hi, please see my post in old thread

I am having a problem with this rom. It runs great and is surprisingly fast and smooth. But I just saw in F-Droid that the rom reports that it does not provide android.hardware.telephony. This wonders me because I am able to call.

Is there any possible to have 5.0 running on our device?
Is there any possible to have 5.0 running on our device? From a old user holding a G2

error 7 trying to install kitakt 4.4
Can someone please help me?
I'm getting the status 7 error message when trying to install kitkat 4.4 on my desire z. Does anyone know how I can fix this error? I have clockwork mod 5.0.2.7 installed.
It says
(status 7)
Installation aborted
I have tried various other roms, and the only one that works is cyanogen mod 7.2
groan.

sonmamnibus said:
Can someone please help me?
I'm getting the status 7 error message when trying to install kitkat 4.4 on my desire z. Does anyone know how I can fix this error? I have clockwork mod 5.0.2.7 installed.
It says
(status 7)
Installation aborted
I have tried various other roms, and the only one that works is cyanogen mod 7.2
groan.
Click to expand...
Click to collapse
update your recovery
here is link
http://forum.xda-developers.com/showthread.php?t=1377754

hamxa266 said:
update your recovery
here is link
http://forum.xda-developers.com/showthread.php?t=1377754
Click to expand...
Click to collapse
A useless app that does nothing.
Is there a newer version of clockworkmod in .zip format available?

sonmamnibus said:
A useless app that does nothing.
Is there a newer version of clockworkmod in .zip format available?
Click to expand...
Click to collapse
The easiest way to install recovery is by using that app , any way if your not able to install via application then you must try fastboot or use secondary app like flashify to install recovery . And i really don't know about flash able zip file files for recovery !!

hamxa266 said:
The easiest way to install recovery is by using that app , any way if your not able to install via application then you must try fastboot or use secondary app like flashify to install recovery . And i really don't know about flash able zip file files for recovery !!
Click to expand...
Click to collapse
zip files are easy. . . . download, boot into clockworkmod, select install zip fiel, boom! done.
This useless app won't even install. all it does is give me stupid information about what a release candidate is...well least I get my refund. back to square one.
Can anyone help me install a new version of clockwork mod? for desire z/G2 PLEASE?

Hi, ok i will try to help you guys...
Its a long time ago, but probably this is a easy way.
https://market.android.com/details?id=ext.recovery.control&feature=search_result
Try, to install 4ext, an than push recovery install in this app.
Thats it.
Lg ivi
---------- Post added at 11:22 AM ---------- Previous post was at 11:17 AM ----------
Ops, i see, the link above tells the more or less the same...
Hmmm, ok probably you guys knew to less of root,bootloader and flashing.
Ok, maybe this will help you
http://forum.xda-developers.com/showthread.php?t=1682479
Lg ivi

I have one question and a short unrelated diatribe. My question is: I just rooted a G2, and this was the first rom I installed. Occasionally I'm losing service/gps etc and I'm assuming I just need to update the radio. Through my research I understand I'll need a matching RIL file for my rom to accompany the radio firmware update. How would I do that for this rom? Or do I need to?
On an unrelated note, I'd like to say thanks so much for continuing to provide nightlies for this phone. I just bought a G2 because the form-factor/hardware feature-set is perfect for me and is also super rare/no longer produced (qwerty slide-out kb, trackpad). Having the hardware feature-set along with up-to-date functional software to boot is HUGE for me. Especially considering the latest nightly upload patched stagefright. KitKat runs almost flawlessly considering the fact that I overclock to 1.5Ghz (didn't seem to effect battery life), reduce animations, don't use the gapps package / google play framework and shy away from bloated apps (besides spotify). With a little thought and creativity in configuration and app selection I have no major issues. For example, good ol brut mod gmaps runs super fast (with some bugs). The classic rolle tube modded youtube app works better than any version of google's youtube app ever has and it even lets me shut off the screen when listening to music.
I've always been bothered by the fact that the android after-market rom dev community seems to mostly abandon projects and let them drift into link-rot hell about as fast as manufacturers put out new phones. No disrespect to the people volunteering their time to make old phones last a couple more years, but when a dev puts themselves out there as a service provider I believe there's a certain degree of responsibility that comes with the implied trust and reliance others are giving the dev by using their rom. So anyways thanks for keeping this one alive. If development ever dries up for the G2 I'll likely roll up my sleeves and figure out rom dev for myself.
---------- Post added at 02:49 PM ---------- Previous post was at 02:22 PM ----------
Nevermind, I figured out updating the radio thanks to this post:
http://forum.xda-developers.com/showpost.php?p=58542873&postcount=57
But my diatribe still applies. Thanks!!!!

hardwarekeyboard problem
hello,
I've installed cyanogenmod 11.0.
It is not possible to type numbers or symbols with fn+letter on the hardware keyboard. exept [email protected] gives a !.
I tried serveral language mappings but it is always the same result.
thanks
Led

x9076 with R63419 LCD working recoveries

TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...

tonyjih said:
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
Click to expand...
Click to collapse
Could you please explain the difference between these 3 recoveries?

GaroRobe said:
Could you please explain the difference between these 3 recoveries?
Click to expand...
Click to collapse
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/

tonyjih said:
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
Click to expand...
Click to collapse
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model
2. My phone is x9076 int'l, manufactured in december 2014
3. I have the "bleached screen" bug on 3rd party ROMs and namelessTWRPs
4. The twrp-x9076 takes only half of a screen area (it does work though, but still identifies my phone as find7a which is incorrect)
5. you still didn't describe the difference between the other two

I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).

GaroRobe said:
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
Click to expand...
Click to collapse
you have to wait CM update their drivers , otherwise it just .... don't work.

I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!

sof006 said:
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
Click to expand...
Click to collapse
Same here. Other than the official beta rom there seems to be nothing available for us. I am seriously considering returning the Oppo since I can't even get hold of 1.2.8i (only stable version which ships with the phone).

So sad... I really want to use 5.0 on my OPPO Find 7. I've reached out to Cyanogen but had no replies, reached out to other ROM developers only to either be ignored or have my question washed away by a sea of people complaining that they can't get a game to work on their phone.

Just found out that cyanogen is working on the new oppo find 7 with new lcd panel issue. So anyone disappointed they'll have it sorted soon hopefully!

Does the offical TWRP and CM support this find7 with new LCD????

Any updates on this? I have managed to get the official AOSP ROM working but nothing else unfortunately.

Double the question. Lack of working TWRP is just fatal to any tinkering.

GaroRobe said:
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model [...]
Click to expand...
Click to collapse
Test with adb (requires root):
Code:
adb devices
adb shell
su
cat /proc/devinfo/lcd
the answer for me (X9006 with COS 2.0.8i) is
Code:
Device version: R63417
Device manufacture: JDI
close the shell
Code:
exit
exit

Maybe if the ROM is compiled from source, the extra driver could be included? I am noob to this so if someone experienced could take a look that'd be great!

Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks

betoNL said:
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
Click to expand...
Click to collapse
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!

djzic said:
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
Click to expand...
Click to collapse
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.

betoNL said:
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
Click to expand...
Click to collapse
Edit I did a backup of the stock recovery (2.0.8i) with Flashify app for instance so I think I am going to try this out anyway ....

Twrp cant seen to find my internal storage. Im using unified storage setting on colorOS 2.1

Problems with Lineage OS

Hi, I'm not sure if it's the right section where to post such a thread but I didn't found a better one for my problem.
I flashed lineage-14.1-20170213-nightly-find7s-signed.zip on my rooted Find 7 (2k version so Find 7s) with TWRP following all the standard steps (full wipe, ROM and gapps install, wipe cache/dalvik and than reboot).
Than when the ROM flash was finished (it took not as much as I thought) I rebooted and my screen become white with a grey OPPO logo in the middle and purple "powered by android" at the bottom (the usual power up screen but with inverted colors) and when I touch the screen it makes quick flashes with flashing black horizontal lines and it keeps being stuck in that way for minutes (way too much and it keeps doing that also after many reboots). The only way to recover the phone is to flash again Color OS (Android 5.0).
So i was wondering what's the problem with that ROM? How can i upgrade my old Android 5.0 to a newer 6.x or 7.x? Is there any rock solid ROM compatible with my F7s that I can flas with no such problems ?
Thankyou all for help!

OmniROM 6 is a mature and solid daily driver with the option to try OmniROM 7 which is still being improved regularly. Arguably the best ROM for Find 7.

RobboW said:
OmniROM 6 is a mature and solid daily driver with the option to try OmniROM 7 which is still being improved regularly. Arguably the best ROM for Find 7.
Click to expand...
Click to collapse
It also has LVM support which allows you to merge your partitions so you will have more than 3gb of space for apps.
I've been running it for months, there are a few things that I miss from previous roms but is very stable and since this phone is getting old the ROM choices are getting slim. It's also the only one I can find that still supports LVM.

RobboW said:
OmniROM 6 is a mature and solid daily driver with the option to try OmniROM 7 which is still being improved regularly. Arguably the best ROM for Find 7.
Click to expand...
Click to collapse
_Clint-Beastwood_ said:
It also has LVM support which allows you to merge your partitions so you will have more than 3gb of space for apps.
I've been running it for months, there are a few things that I miss from previous roms but is very stable and since this phone is getting old the ROM choices are getting slim. It's also the only one I can find that still supports LVM.
Click to expand...
Click to collapse
Thankyou both for helping me I found a list of omnirom ROMs in this thread https://forum.xda-developers.com/find-7/orig-development/omni-testbuilds-7a-7s-t3237065 , can i choose one of the last 6.0.1 to be sure it will work or can I trust the 7.1.1 updates?

You can trust both! And im not a hyper flashholic....

Just another few questions, LVM means that i can unify partitions in order to have more than 3 GB on device memory, right? I found that thread https://forum.xda-developers.com/showpost.php?p=55187001&postcount=558 is it better to use the .iso or the .zip to apply LVM? And when do I have to apply the LVM setup, before or after flashing the new ROM/Gapps?
Thanks again

Frank_Z said:
Just another few questions, LVM means that i can unify partitions in order to have more than 3 GB on device memory, right? I found that thread https://forum.xda-developers.com/showpost.php?p=55187001&postcount=558 is it better to use the .iso or the .zip to apply LVM? And when do I have to apply the LVM setup, before or after flashing the new ROM/Gapps?
Thanks again
Click to expand...
Click to collapse
Flash the setuplvm zip file in twrp BEFORE flashing ROM and gapps

Guys, thanks to all of you! Really, you all made my day with all your advices
With past ROMs i was desperate because none of them worked but now i got rooted android 7.1.1 with merged partitions on my dear Find 7 so thanks again for helping me!

[ROM] [Unofficial] [LOS15.1] Lilly's LineageOS CookieJar

Hi everyone!
This is just my corner where I drop the builds of Lineage-15.1 that I personally use. They do contain a few smaller customisations, like a custom kernel and other goodies that I personally need. I'm posting this here in case somebody finds them to be useful.
Nooby Disclaimer:
I'm not a developer and just because I've got a thread here, doesn't mean I fully know what I'm doing when modding or building ROMs. What I publish is used by myself personally and thereby tested as daily driver. If something still breaks and your phone doesn't survive the smoke test, that's your problem and not mine.
Builds will mostly cater towards my needs if I have any special wishes with the hopes that the changes are useful or interesting for someone else as well (won't be too deep changes I think).
Some info/bugs specific to this build:
SELinux defaults to permissive
Make sure you tell OpenGapps to keep LineageOS Snap installed, Google Camera crashes.
Fails SafetyNet Test, don't use if you need that to verify.
OTA Support (Can somebody confirm that it works?.). The Updater should notify you of a new version.
Other than that, there's not much to say about it. It's LineageOS 15.1, what more could you wish for?
Download link:
http://tf2glados.dynv6.net:8080/
(It's in the LineageOTA folder)
Sources:
http://github.com/LineageOS
http://github.com/LineageOS/android_device_nextbit_ether
http://github.com/LineageOS/android_kernel_nextbit_msm8992
https://github.com/linckandrea/Pop-kernel-ether-LOS14.1-15.1
http://review.lineageos.org/

Mine mineminemineminemineminemine

Another one

It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.

javelinanddart said:
It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.
Click to expand...
Click to collapse
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.

Alexandroid99 said:
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.
Click to expand...
Click to collapse
No need to get snippy. Just commenting that I've been running builds for weeks now bringing up 15.1, and there's 40+ people in the hangouts group I made. I can't stop you from releasing builds or building from my sources (and nor do I care to), just letting you know that it's incorrect to say nobody's been building unofficials.

Sorry, I do apologise, but your comment did sound passive-aggressive even after reading over it multiple times. My point still stands though.

working like a champ but having issue with the figer print

karthikpl said:
working like a champ but having issue with the figer print
Click to expand...
Click to collapse
Working for me just fine. Just a tiny bit inaccurate as always.

http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180401-NIGHTLY-ether.zip

Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?

kinhkinhls said:
Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?
Click to expand...
Click to collapse
Not sure what you are asking, but I had to override the build type branding to NIGHTLY in order to have the OTA server working. Just flash it over the old version. If you're using twrp and it doesn't want to flash, I'll have a Lineage recovery here, flashing that and then flashing the update using the lineage recovery always worked for me. http://tf2glados.dynv6net:8080/LineageRecovery/
Otherwise, just update TWRP. I tried it with the latest TWRP version just now and it works.

Download link is not working
Link is not working bro. Send me link

Quick note:-
OP is away at the moment and shall update the links upon return. :good:
Edit :- Download links are up an running.

Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.

batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I haven't had any issues with that and I wouldn't consider it a build-specific bug, but I might be able to help you anyway. Plug in the phone, go to developer options and tap on "Select USB Configuration" and set it to MTP. That mostly fixes hiccups with USB modes for me. Otherwise, try replacing the cable if you're using the original Nextbit one that came with it. Mine became really unreliable soon after buying the phone, so I replaced it with a better (USB 3.1, even) cable and now it just works.

batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I might have found the technical reason behind it.
https://github.com/LineageOS/androi...mmit/99a8ea97e55cc7f9e28a2b7009325647110dc638
I'll rebuild when I get home, so that will include this fix.

Short note here, my Raspi server died on me again, so sorry for the dead links again. Buuut I'll be home soon, so I can get around fixing the Pi and the downloads will be up again just in time for a new build.

Enjoying the new build so far! Pretty good for me.

http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180605-NIGHTLY-ether.zip