Just a heads up. The lollipop gapps (Slim_zero_gapps.BETA.5.1.build.0.x-20150612.zip) located here http://104.236.22.120/index.php?device=gapps/lollipop md5 codes do not match. I tried several times they never matched. just thought you'd like to know
Related
I successfully built Omni from the Android-4.4 branch today for my N8013, but when I go to flash it I get an error:
set_metadata_recursive: some changes failed
and then the flash fails. I was on TWRP 2.6.0.0 so I updated to 2.6.3.0 which appears to have fixed this error on Nexus 7 (see http://forum.xda-developers.com/showpost.php?p=47027929&postcount=114 ), but that didn't help. Anyone have any ideas?
I realize this is completely bleeding edge stuff so I'm perfectly happy to wait a few days, but that said it would be awesome if anyone knows how to fix this. One thing I haven't tried is flashing the recovery image built in tree, but as I just copied the recovery parameters from a repository that's over a year old I'm not sure if they're still valid. And mine is 5.1MB whereas the one from TeamWin is 6.4MB, so probably something is not right there.
My device tree(s) are below:
https://github.com/ibrahima/android_device_samsung_n8013/tree/android-4.4
https://github.com/ibrahima/android_device_samsung_n80xx-common/tree/android-4.4
Using TheMuppets for proprietaries.
edit: Maybe this is promising? http://forum.xda-developers.com/showthread.php?p=47156977
Last time I had a set_metadata_recursive issue, it was actually from changing the order of the vendor/omni/custom.mk include
But there are probably many ways this could happen - especially on the 4.4 branch, you can assume that this is going to be highly unstable and break in all sorts of strange ways for the first few weeks.
I would suggest that if you're doing a device bringup, start with the 4.3 branch and don't mess with 4.4 until you know it's at least working with 4.3
Ah thanks, that's interesting. I did get 4.3 to work, but that was kind of boring . I also realized that the reason my recovery was smaller was that it was the AOSP recovery, rebuilt with TWRP and it was fine. Will try flashing again with the in tree built recovery later today (after resyncing and all that).
Update: Flashed the recovery built in tree, and then was able to flash my build successfully, so that's that. However, now I'm getting a black screen upon booting and nothing else. To me this seems kind of odd because the same blobs worked fine for Omni 4.3, but I don't know what's changed since then or whatnot. Probably should do a resync and rebuild in case anything that's recently gone into android_device_samsung_smdk4412-common helps.
Oh, I see, I think I might need to update to mali r3p2? Will give it a shot...
Just finished my 2nd time flashing. Been having some issues with FC's and some functionality of apps not working as it should, so I did a few things and wanted to restart from a clean install. So the first issue isn't uncommon, I think i read like 50 people talking about it already lol Keeps saying there is no Boot.sig, System.sig, Recovery.sig and so on. Generally the fix has been to just extract the Boot-Recovery-System, etc files out of the archive, drop it in with the others, and just flash them each individualy i.e /fastboot flash system system.img etc.
These last 2 times, that did not work. When ever I go to flash the radio/modem, I get this error saying the partition doesn't exist. Not sure what I did wrong. Did it the exact way I've been doing it since the beginning of me doing it lol*
So yea just wanted to see if anyone else was getting *"Error flashing Partition, Partition Does Not Exist"*
So what does work for me tho, is with the original error, where it says the archive doesn't contain Boot.sig and so on, if i just let it sit for like 2-3 min, then hit enter, it jumps back to life and finishes the process and my phone boots right into 4.4 lol*
Kit *Kat is playin tricks on me*
Anyone else ?*
Hey guys! I was on Liquidsmooth v3.1 when I decided to update to v3.2 on the 07-27 nightly. I did a clean flash, wiped everything etc but when it first boots up I get hit with this error: "unfortunately themes provider has stopped" when I close out of it it just pops up again in a second. So I'm just stuck on the setup page with that error popping up over and over again. I clean flashed but I still don't know what I did wrong. Can anyone help? THanks!
can anyone help?
Best place for this is LS thread were you will get more exposure. I read your posts there.
You can do the basics over, then try another rom as maybe something in the newer nightlies aren't playing well with your particular phone. Could be something on your internal card.
My basics would be:
ReDownload rom and gapps checking the md5's before flashing--
Wipe all 3x times. That would be System/Data/Both Caches, thru recovery--I use TWRP 2.5.0.2--never an issue. There is a flashable zip for it. Just wipes, no formats, factory resets etc.
If all else fails try reformatting your internal--back up first
Or try another rom for awhile--
Good Luck
Well, after ROM hassles, TWRP hassles and most important of all, GAPPS hassles, I finally got the bastard working.
I tried literally a dozen different ways and zip files, poring over thread for the better part of an entire day, but finally the instruction on this thread, worked on my RN2: http://en.miui.com/forum.php?mod=viewthread&tid=118691
I installed the four .APK files and rebooted. I was able to login to the play store (first time after like 15 attempts to get this working) and not only that, I was able to download an app I previously purchased.
So much simpler in the end, than any other method via recovery and so forth. My phone isn't rooted yet, that wasn't an issue either.
Let me know how it works for you and give me some sugar (or Thanks!)
Flashing the 5.0 ARM64 version off opengapps.org with TWRP worked fine for me. Only worked with the micro version though; it complained about no free space left with anything above.
Where did you find the correct version of TWRP? Did you put it in the downloaded rom folder as update.zip, and flash it in the MIUI stock recovery?
Ok, I think I'm in a deeper trouble than usual.
I've made a nandroid backup like usual and flashed the latest Dirty Unicorns ROM (http://forum.xda-developers.com/nex...-dirty-unicorns-v10-0-official-6-0-1-t3326798). It didn't work as well as I had hoped - was getting force-closes on practically everything. So I wanted to restore the backup. It restored, but didn't load. Odd, so I thought let's restart the phone. So I did, but the phone just kept sitting on the DU logo and not load at all. Ok, so let's clear both Dalvik and Cache. Still doesn't boot, just sits on the logo. Ok, let's factory-reset the phone, re-download, re-install the ROM, clear everything and try again - still the same, never boots. Ok, super weird by now, never happened to me before. Already took out the trusty old Nexus 5 as the backup, as things are getting more complicated.
So I tried flashing two other ROMs (CM13 and Exodus), but the same thing happens - it just sits on the respective ROM's logo. Can anyone tell me what's happening? I'm including a pic of my bootloader. Looking at the BL and Baseband values, they looks different - are they supposed to be the same?
Might be worth going back to the latest stock build to get all your firmware in order then flash a different rom afterwards.
Ok, don't know why or how it happened, but my TWRP version was still on 2.8.x.x, even though I'm sure I flashed the newest one. I flashed the 3.0.2.0 again, but the situation is still the same.
brichardson1991 said:
Might be worth going back to the latest stock build to get all your firmware in order then flash a different rom afterwards.
Click to expand...
Click to collapse
From here? http://forum.xda-developers.com/nexus-6p/development/rom-nexus6p-stock-roms-t3234067
From here sorry: https://developers.google.com/android/nexus/images#angler
if you get stuck follow Heisenberg's guide step 10 :
10. How To Flash The Factory Images (And Return To Stock)
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Yep, all good now. Followed all the steps, loaded stock images, flashed custom recovery, followed by the ROM, all good now. Thanks a bunch!
Was too quick to report success - now my SIM doesn't work. It populates the APNs, says LTE from the quick slide menu, but stays on no signal in the status bar, plus errors out when refreshing web pages, etc.
I've tried flashing different (including the latest) vendor images as well as different radios.
EDIT: never mind; the freaking Mobile Data was turned off (why the **** does it happen?). Turned it back on; all good now.