yashsingh1/xdaforums huggingface dataset:
[Optimus L3, L5, L7 Original Android Development] raul338:
That's not the order, i installed in this order and had no problems

Format system, format data & data/media, format cache

wipe dalvik cache

flash rom

flash gapps

flash kernel (optional)

reboot

flash supersu

flash rootfixer

reboot

And done!
[Optimus L3, L5, L7 Original Android Development] ztrange:
I didn't need to enable developer options. They were already enabled. And there is no root access setting available there.

---------- Post added at 02:41 PM ---------- Previous post was at 02:17 PM ----------

I tried again like you said but no luck with Gallery settings. Still, a blank screen.

I'm wondering if maybe the gapps zip or the kernel zip are not the ones I should be using...

C'mon this is the only decent AOSP ROM for L5... Any ideas?
[Optimus L3, L5, L7 Original Android Development] raul338:
I dunno about that.... I dont like default gallery, i use quick pick
[Optimus L3, L5, L7 Original Android Development] ztrange:
Ok, I was wrongly installing SuperSU from Play Store. Didn't realize that I needed to flash it (the su post has a link to the PlayStore and I went with the first one I saw). So now I have root.

Well, the L5 is not mine, so IDK if they'll be using the Gallery app. I just needed the Gallery settings to be able to set the default storage location for new photos to the external sd. Is there another way to do it?

Also, I was having trouble with Google Now, so I figured I'd try with another set of gapps. I used the pa_gapps-modular-mini-4.4.2-20140117-signed and it works much better.
[Optimus L3, L5, L7 Original Android Development] cocconut:
tried this rom, but i got very often and randomly some google service that kees crashing...

already tried to reinstall gapps,

reinstalled rom->reboot->wait the first screen->reboot->install gapp->reboot

at the end, go back on cm11...
[Optimus L3, L5, L7 Original Android Development] Lukijs:
lol, you're doing it wrong... install rom,install gapps, reboot
[Optimus L3, L5, L7 Original Android Development] Loulou-13:
+1 !

- full wipes

- mount and storage => format "system"

-instal rom

-instal Gapps

-reboot phone

that's all ! :angel:

but on every roms at the first install , you have to reboot 2 or 3 times after ,for to fix all eventually problems like "fc" ,drain baterry ...
[Optimus L3, L5, L7 Original Android Development] AfonsoADR:
really batery drains so faster :\ no one know how to solve this?

in stock rom i use the phone 2 days .

in this rom i use it max 17-20 hours ....

ive read others users with others phone with kitkat with the same problem...
[Optimus L3, L5, L7 Original Android Development] raul338:
use e6t12 kernel, use deep sleep battery saver on night, ... just 1 day :P
[Optimus L3, L5, L7 Original Android Development] AfonsoADR:
i did but really.... no big diference ... i think its a problem with KK source and not in device so much users are talking about it too .

nexus 5 , moto x,g. , nexus 4. :\ i sleep 7 hours and 12% batery go way....
[Optimus L3, L5, L7 Original Android Development] raul338:
Even in stock rom my phone doesn't last 2 days :P so... i dont worry... charge it almost every day :P
[Optimus L3, L5, L7 Original Android Development] AfonsoADR:
report bugs

i found some errors in this ROM . ex in stock launcher names of apps show cutted by that line. look to imagens.(widgets too)

2. when i open google driver and click upload the android.process.media stop . . the same happens when i try to open anything to upload in chrome . it only stop but van continue .
[Optimus L3, L5, L7 Original Android Development] bkr32:
crash after wifi is activated
[Optimus L3, L5, L7 Original Android Development] nundoo:
Cannot turn off Bluetooth. Any ideas?
[Optimus L3, L5, L7 Original Android Development] SuperSkill:
Reboot, but if I remember right, only sometimes shutting og BT won't work....
[Optimus L3, L5, L7 Original Android Development] nundoo:
I can confirm this.

Another bug I've noticed today: the lock screen shows the correct time, but in the notification bar it's stuck right now on 11:51 :)
[Optimus L3, L5, L7 Original Android Development] AfonsoADR:
anyone knows how to use art on this ROM ? why when i put it get a bootloop...
[Optimus L3, L5, L7 Original Android Development] Lukijs:
How long did you wait?
[Optimus L3, L5, L7 Original Android Development] raul338:
Did you try on clean install? Or you switched after installing some apps?
[Optimus L3, L5, L7 Original Android Development] AfonsoADR:
i installed the ROM flashed Gapps cleared and then try change to art. no sucess...
[Optimus L3, L5, L7 Original Android Development] raul338:
weird... Try with rom only... and then flash gaps

Are you using OP gapps?
[Optimus L3, L5, L7 Original Android Development] Tupic Perez1:
To change to art, you need this procedure:

1. Obviously wipe everything except sd card and external

2. Flash Rom

3. Reboot

4. Change to art(You are going to wait some time)

5. When it boot, reboot in recovery and then flash art compatible gapps

6. Wait to boot, first 5-10 minutes after boot you will feel laggy, but then smooth

Enviado desde mi LG-E610 mediante Tapatalk
[Optimus L3, L5, L7 Original Android Development] bkr32:
i keep getting bootloops with wifi on,immediately after pin screen,with wifi off everything seems alright
[Optimus L3, L5, L7 Original Android Development] SuperSkill:
You should then try another kernel. Used this rom a while and one of [MENTION=4343949]PecanCM[/MENTION] kernels, don't remember which one. But, it's related to the kernel.
[Optimus L3, L5, L7 Original Android Development] DodoKoce:
Help

Can ya help me. I want to flash original KDZ for v20d but instead of dl mode it goes to FAST BOOT
[Optimus L3, L5, L7 Original Android Development] 4Freedom:
open kdz

switch off you phone,remove sim,sd,battery and keep pressed vol- connecting your phone to your pc, set EMERGENCY and open the .kdz file

start

wait 15/20 minutes and finish:good:
[Optimus L3, L5, L7 Original Android Development] DodoKoce:
kdz fw upd has stopped working wtf -.-
[Optimus L3, L5, L7 Original Android Development] kristijan505:
That means it finished working it, you did it.
[Optimus L3, L5, L7 Original Android Development] 4Freedom:
run the kdz-offline-fix

it is normal thaat said stop working in windows, wait some minutes and it will run
[Optimus L3, L5, L7 Original Android Development] AfonsoADR:
android 4.4.3

the new Android kk 4.4.3 is out.

sprint in USA already giving it for nexus 5.

:p
[Optimus L3, L5, L7 Original Android Development] AfonsoADR:
android 4.4.3 is now out,

sorry for asking ,but, [MENTION=4343949]PecanCM[/MENTION] are you going to update here too?

i use your rom for a long time and i love it . i think others persons too, count with you.

thanks bro
[Optimus L3, L5, L7 Original Android Development] pdeadm:
I also used it for a while. I liked it. Very smooth.
[Optimus L3, L5, L7 Original Android Development] francescus28:
Please can you update this fantastic rom?[emoji120][emoji120]
[Optimus L3, L5, L7 Original Android Development] PecanCM:
Not Pure AOSP but I will try to bring up CAF just like Xperia m next month After releasing new cm version, right now I'm busy in study and other device.
[Optimus L3, L5, L7 Original Android Development] francescus28:
Thank You.Take your time :)
[Optimus L3, L5, L7 Original Android Development] raul338:
Just got another kernel panic with phone inactive

https://www.mediafire.com/?ssp2nd4vdrnc98o
[Optimus L3, L5, L7 Original Android Development] ZhaoPH:
Will this work on LG L5 E612 running android ics rooted? :confused::confused::confused:
[Optimus L3, L5, L7 Original Android Development] CzarnyUrok:
yea, but you must install v20 baseband before install rom
[Optimus L3, L5, L7 Original Android Development] Antonio Almeida Filho:
PecanCM, you could help me develop a pure ROM like this?
[Optimus L3, L5, L7 Original Android Development] giaki3003:
NFC Tag not working.
[Asus  Eee Pad Transformer Prime] I am Zurvan:
Hi all, noob here. I used the new flatline-nvflash guide (linked to from this site) to create backup blobs and files for my TF201 running JB. Worked marvelously...JOY!!! After doing so I thought I had a recoverable tf201 in case of accidental bricking. So I went ahead and flashed a custom rom (CMB). Didn't realise that during the backup process my bootloader was changed and the flashing failed resulting in a brick. A long story but I only have APX access now, no recovery. I've tried to find a guide to how to use my flatline-nvflash generated recovery blobs and files but haven't been able to find one. There is an old guide for the ICS based nvflash recovery but not the spanking new JB flatline-nvflash recovery.

Help with finding a guide or advice on "how to do it" in the form of correct code and sequence would be much appreciated. Would change my TF201 from an attractive but expensive paperweight back to a functional unit.
[Asus  Eee Pad Transformer Prime] TacoNikky:
I suggest you to contact with flumpster. He is one who knows about rom&recovery more than most of us :)
[Asus  Eee Pad Transformer Prime] flumpster:
It doesn't matter how old the instructions are for nvflash, once you have your backups the restore method is all the same.

Here are instructions for the tf700 but they will apply to you also. Just get the tf201 firmware instead of tf700 where it says. This only uses nvflash to restore the parts you need to get fast boot working to do the rest.

http://xdaforums.com/showthread.php?t=2538028

Here is an older one for the prime that uses nvflash and unblobed files to do it all. Take your pick.

http://xdaforums.com/showthread.php?t=1927818&highlight=nvflash
[Android Apps and Games] bynodeapps:
Use Bynode TV to watch free live and on-demand video TV from Indonesia and more countries on your android phone and tablets.

Bynode TV is simple to use and free with following features:

A wide selection of public TV channels

Intuitive and friendly UI

Fast channels launch and switching

Video-on-demand

Onscreen controls

Adaptive Network Bandwidth support

High Quality streams

Currently supporting almost all popular free public TV channels in United States (US), United Kingdom (UK), Australia, Mexico, Brazil, Indonesia, India, Philippines, Russia, Spain, Germany, Turkey, Ireland, Israel and many other popular channels worldwide.

Please note that Bynode TV is offering public channels for free. Therefore, some channels may not be available in all regions.

Vitamio codec is necessary for streaming video. It is available for free on Google Play.

Testing and optimized for Nexus 5, Nexus 7, HTC One M7, Samsung Galaxy S3/S4/Note 2/Note 3/Note 8.0, Sony Xperia Z1 and XL

If you have any queries or support issues, please contact us at support@bynode.com

Download Bynode TV - Free TV Streaming on Google Play
[Google Chromecast] Cares:
Does anybody know why my tablet will always stop casting about 1 minute after the screen turns off? I thought it might be Wi-Fi sleep but it's disabled. I thought it might be Wi-Fi optimization but that's off. I've tested Pandora, Viki, and Songza so far. My phone does not have this issue and they have similar Wi-Fi profiles. I'm clueless.
[Google Chromecast] abuttino:
Songza definitely has a problem
[Google Chromecast] Cares:
I can't figure out for the life of me why this is happening. No issues on my phone but yes on the Nexus 7. I even wiped and flashed stock rooted OTA.
[Google Chromecast] abuttino:
This program is a hot mess. Serious instability problems. Great idea, poor execution.

Hopefully they know about this
[Google Chromecast] Cares:
It's not just Songza but also Viki and Pandora. I have no issues with my other devices: HTC One, GS4, and iPad.
[Google Chromecast] abuttino:
It quits working on my MotoHD as well. So, maybe it could be a problem with AOSP roms?

Edit:I emailed the dev.

---------- Post added at 12:41 PM ---------- Previous post was at 12:08 PM ----------

Here is the reply I got
[Google Chromecast] Cares:
Yea except I don't have the problem with my HTC One. My phone is left untouched for an hour and the music still keeps going. So his response is not 100% accurate in my opinion.
[Google Chromecast] Asphyx:
My guess is they are not doing this correctly...

If I'm not mistaken the best way to do what they are doing is to have the app send a player that will take control functions from the originating unit but gets everything else directly from the server.

They seem to be sending the audio and using the Phone as the player...

They should move to an indirect stream by sending a player not audio to Chromecast.

The Chromecast is not meant to send communication back just receive communication from the app that started the stream and you do that by sending a player app to the Chromecast that waits for input from the device but plays it's content directly from their servers.

I will point out however that his letter back to you seems to suggest they know this already and are working on it.

They just have to make an HTML5 Player that they can send and work out all the control functions.
[Google Chromecast] abuttino:
That's a pretty big mistake..
[Google Chromecast] Asphyx:
Not really though because thats more how Miracast works and the Chromecast is very different.

Easy to see how some Dev could overlook the other better method.

And I'm not 100% sure I am describing it properly above...

I was under the impression that the apps like Netflix, Pandora and YouTube just send the player with a URL string to play and the rest is all done by chromecast. The player that gets sent then only communicates for Command signals.
[Google Chromecast] abuttino:
From the looks of it, they have to revamp the entire system
[Google Chromecast] Asphyx:
Yes probably....

I bet the Majority of their support was written with the Advanced version of the SDK and now that they have the Official RC version from the Hackathon it will be easier to code it properly.

Seems a lot of apps who have added support did it this way as well.

The issues is some HAD to because they didn't have a server to work with (Like aVia) but things like Pandora and Songza should have gone the YouTube and Netflix route to streaming.

And if they don't someone else will! LOL So I expect they will figure it out in the end.
[Galaxy Tab Q&A, Help & Troubleshooting] brenzef:
I upgraded my P1000 from cm-10.1-20131117-NIGHTLY-p1.zip to cm-11-20131210-NIGHTLY-p1.zip

After the update it was kinda working fine. Gapps did not work yet since I did not upgrade that yet, so I installed pa_gapps-full-4.4-20131126-signed.zip.

And rebooted.

That's where the trouble started.

Apps crashed and the P1000 did not startup fine.

I decided to do a full wipe, cleared all caches and re-flashed the P1000.

I does not start anymore (stays on the CM11 boot screen).

What did I miss?
[Galaxy Tab Q&A, Help & Troubleshooting] MarviXDA:
It's not your fault.

It's many different but similar errors in past few days on experimental CM11 builds.

Read http://xdaforums.com/showthread.php?t=2560605 for example.
[Galaxy Tab Q&A, Help & Troubleshooting] brenzef:
Thanks,

It seems I updated to CM11 a bit to early, having confidence :)

If there is someone having a glorious idea...I'm open to those, hehe....
[Galaxy Tab Q&A, Help & Troubleshooting] brenzef:
I flashed back to cm10... Maybe it was a bit too early to go to CM11....

This thread can be closed ;)
[Galaxy Tab Q&A, Help & Troubleshooting] ulev:
Your original problem was using PA GAPPS full. Its to big for the /system partition. You should use one of the BaNkS Gapps versions instead. CM11 runs extremely well on SGT 7, especially after switching to ART.
[Galaxy Tab Q&A, Help & Troubleshooting] brenzef:
That was a very good tip!!!!!

THANKS, upgraded to CM11 with BaNkS Gapps.

+1 :)
[Galaxy Tab Q&A, Help & Troubleshooting] ulev:
Glad I could be of help.:)
[Nexus 7 Q&A, Help & Troubleshooting] heterodoxy:
I followed androidroot.mobi's guide to pulling nvflash blobs for a Nexus 7. I was able to successfully do this, but I had problems trying to go back to stock. I flashed the stock recovery and then tried to flash the stock bootloader; first I used "fastboot flash boot bootloader.img" using the bootloader.img from JDQ39 but the bootloader version did not change. I then used "fastboot flash bootloader bootloader.img" and got the signature mismatch error mentioned elsewhere in the guide thread.

By this point for some reason the device would not boot to Android though the bootloader continued to work. I've tried to "unbrick" using wheelie --blob <path to blob.bin> --unbrick <path to bricksafe.img>

It gets stuck here:

Wheelie 0.1 - Preflight for nvflash.

Copyright (c) 2011-2012 androidroot.mobi

========================================

Waiting for device in APX mode...

[=] Chip UID: 0x15d4a826d48040b

[=] RCM Version: 0x30001

[=] CPU Model: Tegra 3

[+] Sending BCT

And now the bootloader doesn't seem to work; I can't get into anything other than APX.

This is just a comedy of errors, and of course it isn't my device; I didn't have any trouble with mine. :/ Any ideas on how to recover?
[Nexus 7 Q&A, Help & Troubleshooting] heterodoxy:
After some more research I'm really starting to suspect that I borked the kernel by doing this (boot vs. bootloader, why was flashing a bootloader to the former allowed?!) and that wheelie then borked the bootloader. If I can get the bootloader back I can get the kernel back, but I need help with the misbehaving nvflash... :(
[Nexus 7 Q&A, Help & Troubleshooting] xateeq:
U need to rma your tablet to get it fixed and about bootloader flashing every thing u do to your device is your choice no one is forcing u to do so. Thats y every op say i am not responsible.

Please ignore my spelling mistakes. English is not my native language.
[Nexus 7 Q&A, Help & Troubleshooting] heterodoxy:
It'd be quicker to do it myself and it should be possible; that's the whole point of the guide to gaining nvflash access (on androidroot.mobi), with which you may or may not be familiar. There's no hardware problem that would make an RMA the only option; I just need a little better of an idea of how to proceed from here with nvflash specifically.

That's a little apropos of nothing. I don't disagree, and I've never said that flashing boot instead of bootloader was anything but a screw-up on my part. But my impression was that this is a community of developers like myself, all of whom I dare say have screwed up at least once (I know this isn't the first time for me), and I figured someone else may have learned or may know the right incantation to recover from this particular situation and may be able to pass it on.

It'd probably have been easier for me to post in the thread that concerns gaining nvflash access and supports some of the tools therefor, but I can't do that yet as it's in a development forum, so I can only hope for the right person to stumble across this thread.

Thanks.
[Nexus 7 Q&A, Help & Troubleshooting] xateeq:
Please i mean no disrespect but every night i go to Q&A section and ever were i see is people having bricked device because of screwed bootloader that they flashed wrong, and i have yet to see a proper solution.

Only solution i have seen is that u do a backup of it before u doing any thing and to backup ur device specific files u again need to load custom bootloader and that on its own is scary.
[Nexus 7 Q&A, Help & Troubleshooting] TheDj408:
So there isn't a easy way to backup the device specific files? And I tried the nvflash method and flashed the stock bootloader without any issue... I guess I was just lucky to get away with it...
[Nexus 7 Q&A, Help & Troubleshooting] xateeq:
If you have correct files then it shouldn't be a problem. If u flash wrong file the **** hits the fan.

Please ignore my spelling mistakes. English is not my native language.
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
I have exactly the same Problem as the TO...

How exactly did you do this? And can you upload the wheelie binary you used, maybe theres only something wrong with our wheelie version...
[Nexus 7 Q&A, Help & Troubleshooting] heterodoxy:
You're getting the Sending BCT hang/Error 3 with wheelie?

I think there's definitely something wrong with wheelie in general. I've tried the two versions on androidroot.mobi's Web site and the 0.2 version of wheelie posted elsewhere on this forum and had no success with any of them, at least on the bricked device. On a regular device (I'm trying them side by side) it's fine, so there's that.

With the bricked device I've been having more success (and been learning more) just using nvflash with the --blob parameter. I still get errors, but they're actually errors from the device or from the bootloader instead of a generic error sending information to/receiving a response from the device.
[Nexus 7 Q&A, Help & Troubleshooting] TheDj408:
I did the method right... I was able to see the files in tab but failed to get them in pc... So Iflashed ooriginal stock bootloader... I meant this...
[Nexus 7 Q&A, Help & Troubleshooting] heterodoxy:
You need a CSI gif there. :)

You are made of brilliant. I think I was on the same track as you but I didn't know about bct_dump and so I don't think my flash.cfg is exactly right. I'll be experimenting all night too. :) On my working device I backed up ALL THE PARTITIONS but on this device I only have what was pulled during the creation of the blobs (blob.bin, bootloader.ebt, create.bct, recovery.bct, etc.)

Cheers!
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
So ist your device working again? If not:

I think the missing partitions shouldn't be a Problem... if you haf the 1GB Version it think you can use my BCT (I learned of the existence of this tool somewere on the third page on google, aftere reading all pages before). After you habe it on nvflash mode, try holding vol down and nflash --resume --go and it should go into fastboot mode were you can reflash the bootloader from the last Kitkat factory Image... I don't tested this way but i think it should work...

And would you mind hitting the Thanks Button? It costed me many houres to find out how to get it in nvflash mode again and I wrote the post before I rewrote my bootloader :D

EDIT: OK my device is now bricked again (wrote zeros to mmcblk0boot0) First I made the bootstrap command better:

./nvflash --setbct --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin --go

as you can see I removed --create and addet --go. The create command made the error (an because that my device wasn't wiped). I addet the go because without that I got "no command error". The go command dosen't do anything in my case, so i think the way i mentioned before in this post wouldn't work... And you need to flash something before...

EDIT2: ok the command above doesn't work because the --go command makes it leave nvflash mode, so the command with create in it is the best I found. Creat will fail but, but that ist good (so no wipe), but it was the only one I found that let you use setbct. And you can generate your flash.cfg file from create.bct. If you use create.bct instead auf recovery.bct for generating your flash.cfg file you don't have to remove this one line...