yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] el_charlie:
Download factory image, put phone in fastboot mode, execute flash-all.bat, profit.

It will wipe your phone, so make a backup and copy it to your PC.

I still don't get why would you go back to stock. This port is amazing!

Cheers!
[Nexus 4 Android Development] ramjet73:
I'd suggest doing the factory reset in TWRP 2.7.1.0 or higher, which is the default wipe option, then flashing the ROM and booting it. Be aware that the part of the data partition used for apps and settings will be formatted, so you will have to redo those, but the portion used for the simulated SD card does not get formatted by the default TWRP wipe.

Good luck!

Edit: This assumes that you are flashing the stock ROM zip file and not the factory image downloaded directly from Google. Downloads and instructions for both methods of returning to stock are contained in this post.

ramjet73
[Nexus 4 Android Development] LuketaD2:
Ok, tks!

I'm selling this phone, and I need to go back to stock rom!

I'm leaving android =/

Ok thank you!

I'll try this Flashable rom

http://xdaforums.com/nexus-4/development/rom-flashable-stock-rom-radio-kernel-t2527806
[Nexus 4 Android Development] ramjet73:
That should work and that ROM zip is the "P" version rather than the "O" version in the post linked from the edit to my previous post.

If you use the flashable zip method you might want to format the whole data partition as a separate wipe before flashing the stock ROM. Since you are selling the phone you probably don't want to leave your data on the simulated SD card that is part of the data partition.

ramjet73
[Nexus 4 Android Development] LuketaD2:
Tks again!!!
[Nexus 4 Android Development] manueltts:
Ok! It booted. First time instantaneous systemUI FC, and reboot. Second time started setup, and rebooted at 2nd or 3rd step. Going for the third!

Edit: Couldn't use keyboard for setup, so skipped everything. Now I'm on launcher but both launchers FCs continuously.
[Nexus 4 Android Development] ph37rd:
Have you searched the thread? I'm curious, do you think all the people posting here run chrome as their browser or opera? Keep in mind chrome is the only browser installed when flashing... Something to think about.

Now that you're done thinking, did you come to the conclusion that it's something that's wrong with your individual setup? Ib knew you would.

How did you do your install? What kernel are you running? What tweaks or mods have you done? Have you tried uninstalling all the updates, clearing chrome cache and databases?

The more information you provide up front, the better chance you have at getting an answer that isn't sarcastic and meant to make you think after the fact.

---------- Post added at 08:34 PM ---------- Previous post was at 08:29 PM ----------

Beta 5 has been around for awhile and it's just now happening to both of you? Amazing how all those using defconoi's kernel haven't been speaking up all this time.

Having used this since [MENTION=1050103]sykopompos[/MENTION] initial release, I've not had any such problems with chrome. I'd start fresh and install an app at a time, doing some tests, next app etc to see what you can come up with.

There's something in your configurations causing the problem. The two of you should compare notes to see what is common between your phones. Your findings may help others.
[Nexus 4 Android Development] ramjet73:
You're welcome.

One last thing since you are selling the phone.

Unless the person you sell it to wants a custom recovery, using the ROM zip method will leave it in place so you might want to flash the stock recovery zip file located in this post, and then lock the bootloader with fastboot as documented in the Google factory image flashing instructions.

That should get you back to 100% stock.

ramjet73
[Nexus 4 Android Development] sykopompos:
Can you pull a log?

Sent from my LG-D851
[Nexus 4 Android Development] ph37rd:
You can run the default kernel on any ROM. That's how the ROM is created.

The difference to me has been purely one of feel. Five feels snappier, if you will. Anything that matters to me that I couldn't do in beta 3 or 4, I can't do in beta 5, such as VPN.

Anything else?
[Nexus 4 Android Development] manueltts:
I'm into it, installing Adb on a Windows pc

Edit: There it is; tell me if you need something longer... I named it "L_SystemUI" because Now Launcher is running, Setting too... but navbar and statusbar are all the time trying to appear, but can't.

Edit 2: SystemUI stable now, keyboard working. Seems to be a problem with wifi because I can't connect. Attached log.
[Nexus 4 Android Development] justthefacts:
Man. Love this thread. Million things going on at the same time. Who was it that was complaining about this thread being off development track?

this is development at it's best....:cowboy:
[Nexus 4 Android Development] sykopompos:
I'm assuming that you did a clean flash so if that is the case, I believe it is the n5 apps that I decided to try to use and the reason it went through for bitstra is because he dirty flashed.

Let me give it a try with the n7 specific apps

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
I don't see any log attached. System ui covers the nav bar and title bar

Sent from my LG-D851
[Nexus 4 Android Development] manueltts:
Seems like I'm not being able to attach files; how do we do that using Chrome for Windows? Right now the only big problem is WiFi stuck at athenticating. Let's wait for next version.
[Nexus 4 Android Development] sykopompos:
So the system stabilized? Any idea what happened?

WiFi isn't working still?

Sent from my LG-D851
[Nexus 4 Android Development] manueltts:
​

Sent you logcats by e-mail. Wifi isn't working; SystemUI, keyboard, Now Launcher, Settings, are working after a few FCs. I'm having dinner, so out for a while.
[Nexus 4 Android Development] sykopompos:
I see what is going in with it through your logcat. It really really doesn't like the n5 systemui and settings apk and that is probably taking WiFi out with it when it is restarting those services

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
I think this was covered before, but unless you are using a private VPN server, the Private Internet Access app works fine with this ROM. The cost for that service is $6 per month or $40 per year which is pretty reasonable compared to the other alternatives.

ramjet73
[Nexus 4 Android Development] sykopompos:
You gonna be around for awhile [MENTION=275009]ramjet73[/MENTION]? Gonna start working on hammerhead soon. We already got a working boot image so that won't be an issue (the one that was the pain in the ass for flo) so this should go pretty smoothly and quick. Just gotta track down the specific hammerhead files and add them back in

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
Yea, I've already got a flashable ROM zip here that works except for superuser so you can just add/change/delete files there if that works.

Edit: NVM, I forgot that zip flashes the factory image for the preview before the mods.

ramjet73
[Nexus 4 Android Development] :
Revisiting PIN Screen Lock

Albeit it's an inconceivably irrelevant problem, [MENTION=1050103]sykopompos[/MENTION] what's causing "PIN lock Relock of Death?"

In unrelated news...
[Nexus 4 Android Development] sykopompos:
test three for flo [MENTION=4756018]manueltts[/MENTION] [MENTION=2981094]bitstra[/MENTION] https://drive.google.com/file/d/0By0vn8iv_zrVZ2RiUVBMbmRUS28/edit?usp=sharing

FLO/N7 Wifi only
[Nexus 4 Android Development] sykopompos:
We are going for the whole thing this time so N5 users don't have to be jealous anymore and so I can use it for a base on the g2, g3, and 1+1
[Nexus 4 Android Development] sykopompos:
Google screw up on the lockscreen in the closed source frameworks. Most likely not something related but not fully tested before release to see if other lockscreen modifications borked it
[Nexus 4 Android Development] ramjet73:
Could you describe exactly the sequence that causes the lockup so other users can try it and provide a logcat? You won't be able to use an app for the logcat but may still be able to get one via ADB even if the phone is locked up.

Thanks.

ramjet73
[Nexus 4 Android Development] sykopompos:
[MENTION=2383735]jayfallen[/MENTION] if this latest flo build checks out, then be ready for a deb build shortly after. The edits at this point will be extremely minor and can be done within a half hour or so of a good flo build.

Anyone running one of these test builds on flo, deb, hammerhead once they get up, I'm gonna need you guys to have adb working and pull avc dmesg logs so I can craft the sepolicies to them since we are using a aosp base, things are slightly different and by removing the avc spam, we improve speed and stability.

Also as much as I hate to say it, please don't use SuperSU on those test builds. SuperSU spams the crap out of the avc denials over and over and that is for chainfire to resolve, koush's superuser hasn't been updated for selinux so the log spam is a lot less

Once the sepolicies are crafted for each device, I will make a thread for each device in their forum as a release build

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
Nothing I can do about it anyways. It is in Google's closed source L code and a well known bug :(

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
For anyone that needs it here is the flashable zip for Koush's superuser. It used to be linked from the OP but I think that was removed after it got integrated into the ROM.

Not you, but if we know exactly how he is using the lockscreen there may be some workaround. A lot of the problems reported for the L preview have viable alternatives.

However, the logcat probably won't be necessary.

ramjet73
[Nexus 4 Android Development] sykopompos:
I'm working through hammerhead right now [MENTION=275009]ramjet73[/MENTION] , gonna be about a hour.

Deb is halfway done, just waiting on it compiling and feedback in the latest flo build to see if the changes I made are good or not

Sent from my LG-D851
[Nexus 4 Android Development] Sierra35:
Bluetooth still does not connect as phone in the car. :(
[Nexus 4 Android Development] johnb380:
Hey sorry of this had been asked but has the clear comment screens in Facebook and twitter been fixed. And is there a confirmed way to tether now? I used this in beta 2 and before... Sorry this ROM thread is ridiculously big
[Nexus 4 Android Development] ramjet73:
I just did thread searches for "facebook", "twitter" and "tether" that returned less than 400 posts total and the most current ones are at the top of each list of hits.

Sorry, but I'm kind of tired of hearing how big this thread is. That's why the search feature is provided. :good:

ramjet73
[Nexus 4 Android Development] ph37rd:
I should probably apologize. While the content of my post stands, my delivery wasn't the best.
[Nexus 4 Android Development] sykopompos:
[MENTION=275009]ramjet73[/MENTION] you are coming up https://github.com/Android-L-Porting-Team/Android-L-Hammerhead

uploading now
[Nexus 4 Android Development] sykopompos:
Whoa, you guys seem like you are feening for an update like it is crack..... I'm all out of mako right now but I got some flo, deb and hammerhead.... Its good stuff man

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
Still borked unfortunately and I did do some investigating into it and it isn't good. Bluetooth routes through audio, audio routes through audio flinger, audio flinger routes through media server, media server routes through surface flinger, surface flinger.... Well you get the point.

Way too much that has so much closed sourced code and new APIs that until we can start merging some of these new APIs into aosp (which most likely has changed since the L preview so we would be putting half borked code in with newer code so we could break a lot in the process) we are kinda unable to fix this one right now

Sent from my LG-D851
[Nexus 4 Android Development] justthefacts:
Trying to push some flo, deb and hammerhead to mako addicts?
[Nexus 4 Android Development] sykopompos:
Well I gotta expand my line up to get as many addicts in as I can, I got all this kool-aid sitting here that I need to distribute to someone...

Bacon/1+1 is coming tomorrow and maybe just maybe g2 and g3. (Need to pick up a competent tester for g2)

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
here you go [MENTION=275009]ramjet73[/MENTION] https://drive.google.com/file/d/0By0vn8iv_zrVOGZVR3lFc3VJdzQ/edit?usp=sharing

This is a bit iffy with the new props for it because I can't test them myself to see if any of them are gonna kill the boot like I could on the n4.

I stayed away from the ones I know kill it like the egl files or libgsl.

HAMMERHEAD TEST

I didn't get a chance to go over the updater-script either so there is a possibility that you might need to grab one out of a n5 rom and replace the one in here. That could also be the problem with flo if there is still wifi issues. Should still boot though

I'm just really tired and groggy tonight
[Nexus 4 Android Development] ph37rd:
If someone wants to sell me a t-moo compatible g2 for $100 I'd be willing to test stool samples for you.
[Nexus 4 Android Development] sykopompos:
I could use one too

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
Umm...

Is there a reason that the hammerhead test starts with "flo"? ;)

ramjet73
[Nexus 4 Android Development] sykopompos:
I just c+p the name, it is hammerhead though if it says 5.3 at the end

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
OK, just wanted to be sure before I spend the time flashing and testing it.

I doubt that it would brick the phone even if it was the flo version given that the partition references in the updater-script are by name and not number.

Downloading now....

ramjet73
[Nexus 4 Android Development] sykopompos:
Completely understand. The updater script would have stopped it from flashing though because the first thing I did was change it for hammerhead so there wouldn't be any accidental flashed by someone not realizing it was a test build for another phone

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
I really liked how the n5 was setup on some things. Almost everything device specific was in the vendor folder so I didn't have to go digging around in lib hunting for it. The only thing I could have wished for of it was separated by the vendor and all of it was in vendor.

It really is a lot cleaner. Oh well, something to look into doing on my developer resource project to make it even more cleaner

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
[MENTION=1050103]sykopompos[/MENTION],

I've installed (clean) Flo-L-Breadcrumbs-Bunnies-and-Witches-5.1-TEST-2.zip...

The Test3 I've seen to late!

With Test 2 it booted as secondary multirom to 1st setup Screen

- No Wifi with DHCP, but Wifi works with static IP address+WPA2!

- Bluetooth cannot be enabled...

- Playstore works fine - google apps are updating...

- no keyboard issues - nor other issues.

Going now (clean)-install Test3 on Flo ...

thanks for your work!:good:
[Nexus 4 Android Development] ramjet73:
Booting now...

I'm at the colored fireflies so it looks like it is going to boot OK.

I will update this post once the setup is complete.

Update1: Initialization complete with no errors or FC's so far. :) Apps are updating from Play Store and as soon as that completed I will install QuickBoot and see if superuser works. It's good that the Koush superuser is installed by default. :good:

Update2: Apparently the binaries for root (su and reboot) aren't accessible (see attached screenshot). I checked the ROM zip file and they are there in xbin, but the superuser app shows no authorization requests. There is a symlink for su in the updater-script so that's not the problem. Time for a logcat?

I will resume updates in a new post. Everything else but superuser seems to work fine so far. :highfive:

ramjet73
[Nexus 4 Android Development] sykopompos:
I was curious about the Bluetooth and if I could update the hal driver for it on the n7 because on the preview it is designed for the n7 but with as many changes in the preview I was hesitant

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
Well that is promising. I was wondering about some of those proprietary files since I couldn't test them myself. Might get some screwiness because of me not updating the updater-script though and things not getting symlinked

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
OMG the avalanche of ports to other devices teard off...

congrats [MENTION=1050103]sykopompos[/MENTION]!:good:

Oh, oh, I'v forgotten [MENTION=1316336]defconoi[/MENTION] and all others - so also congrats to them too...
[Nexus 4 Android Development] sykopompos:
I guess that means test 3 was good and beautiful?

Notice any increased smoothness and speed vs the official previews?

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
remember guys, since we are using a different sepolicy and init than the official previews, there is going to be some new avc spam going through the logs. I'm gonna need those so I can make a specific to the device sepolicy.

adb shell

su

dmesg | grep avc

and then c+p to a txt file and upload it so I can work on them tomorrow and fine tune them.

Also, I will get deb up, I just gotta make the edits to flo for the radio and we will be good, everything else is already in there. Then I will post them up for the masses with their own threads
[Nexus 4 Android Development] sykopompos:
wth is going on with superuser on the n5. U are permissive so that isn't the problem and it is the same exact apk and binary in mako. Actually I know why.

I'll fix it in the am but it isn't hitting on the install-recovery.sh that should be in etc because I forgot it and the boot.img still points to the bin

edit, actually the github packager automatically adds it to etc I think so it should just be a matter of pointing it to /etc/
[Nexus 4 Android Development] ramjet73:
That makes sense.

Do you still want a logcat and the grep for dmesg for reference?

ramjet73
[Nexus 4 Android Development] sykopompos:
[MENTION=275009]ramjet73[/MENTION] push this to /bin/ and replace the install-recovery.sh with this one and su should work https://drive.google.com/file/d/0By0vn8iv_zrVU19aRTBiblRybEE/edit?usp=sharing
[Nexus 4 Android Development] sykopompos:
yes sir, I'm not too concerned with su as I am with crafting the sepolicy
[Nexus 4 Android Development] avinab:
[MENTION=1050103]sykopompos[/MENTION] Thanks a lot ... :) Now that there is of barrage of L ports coming up for different nexus devices,Don't forget about Mako.;) Is some progress going on Mako ??
[Nexus 4 Android Development] iPwn_:
Is there any kernel based on Franco r210 that works with this ROM?
[Nexus 4 Android Development] sykopompos:
The goal is to get all the other ports exactly to where we are at so we can update as a whole and it helps smooth out the wrinkles on other devices that I don't have to diagnose problems if they have the same base as us.

I'll spend the weekend on the other devices, then back to mako to merge up the latest binaries and up pull in the 81c stuff (apparently some apps have improved design on them from what I hear)

Then it is gonna be trying to go more aosp. I've tried merging more aosp in but we are hitting core services now which too many things rely on. This means we gotta take a different approach like smali the frameworks in the previews and then compile the L branch aosp (with the same proprietary files that were used in the preview so we have a as close as possible match) then diff the whole thing and track down where the new APIs are. Hopefully once we get the new APIs we can start backporting them into current aosp (at least some or enough to get some new libs we can merge in). This will be a difficult task and time consuming so any help with it (even if it is just smali'ing all the framework jars) is highly appreciated. Hopefully with branch out on more ports, we pick up a few more developers who can help out but the common consensus is it isn't worth the work when the source will be coming

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
I pushed that script to the SD card and tried to copy it to /system/bin, but it won't let me do that even after issuing the "su" command in ADB shell:

D:\Android\Minimal ADB and Fastboot>adb shell
root@hammerhead:/ # su
su
255|root@hammerhead:/ # cp /mnt/sdcard/install-recovery.sh /system/bin/install-recovery.sh
p /mnt/sdcard/install-recovery.sh /system/bin/install-recovery.sh <
cp: /system/bin/install-recovery.sh: Read-only file system
1|root@hammerhead:/ #

Pushing it directly to the /system/bin directory got the same error. :(

I'll get the logs for you then try putting that file into the ROM zip and re-flashing.

ramjet73
[Nexus 4 Android Development] sykopompos:
Not just nexus phones BTW, I'm gonna work on a 1+1 port tomorrow and I'm hoping I can get the g3 on L (since I got it, I can have something similar to the n5 then)

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
Test 3 is booting right now - download took me about 55 mins - damn bandwidth :(...

But Test 2 was a bit faster on animations than official preview...

I'll report back...
[Nexus 4 Android Development] sykopompos:
I always reboot into recovery, mount the system, then push it and reboot but I found that it isn't the most reliable to be honest

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
I'm curious what it is you are looking for in the mako ROM now that USB tethering is working again?

ramjet73
[Nexus 4 Android Development] avinab:
[MENTION=1050103]sykopompos[/MENTION] thanks. No problem..take your time. Just getting restless about addition of new aosp binaries might solve some on going issues on mako.:D:D:screwy:
[Nexus 4 Android Development] sykopompos:
Test 2 was a straight port from mako, test 3 has the n7 apks back in it along with the extra google bits. I think I put the regular n7 framework res in so it doesn't have the new animations and colors but the next major version when we merge in 81c across the devices will have all the new res files in (should be able to get away with the n5 res files but then you will have the dialer on a tablet)

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
I believe Test 2 was the better one :(

On Test 3 WiFi can't be activated; Bluetooth can't be acivated!

pulling logcat now...
[Nexus 4 Android Development] sykopompos:
I've found that I can add less and less of them on each new set of binaries because we are getting too new for the base. That's another reason why I used an older set of binaries on the other ports instead of the new new ones because I need to go through each one and test if they break anything (like sensor1.so breaks camera on the newer binaries)

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
Well I was doing some playing on WiFi in test 3, I can revert back to 2 and we just need to figure out Bluetooth and a bit more on WiFi

Sent from my LG-D851
[Nexus 4 Android Development] avinab:
In L port while playing games the screen brightness dims and it become somewhat dark but this doesn't happen in KitKat as long as we touch the screen.Is this due to new android L algorithm of adaptive brightness or due to some bug??
[Nexus 4 Android Development] sykopompos:
That would be adaptive brightness. I think there was some tweaks in L for power saving on it

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
The logs for hammerhead are attached.

I'm going to replace the install-recovery.sh in the /system/bin directory of the zip file and try re-flashing the ROM now. I'll just do a dirty flash in this case.

ramjet73
[Nexus 4 Android Development] avinab:
Okie thanks:)
[Nexus 4 Android Development] bitstra:
Here's the logcat out from Flo Test3:
[Nexus 4 Android Development] sykopompos:
[MENTION=2981094]bitstra[/MENTION] besides WiFi and Bluetooth on test 3, how did the rest of it run? Better then 2? Is it more stable? Are people gonna whine that it is not a true tablet version?

Sent from my LG-D851