Related
Hi,
I really am embarrassed for having to ask this question considering I've been an Android user for almost a year now and rooting all my devices.
I went to Asus' website a moment ago to download the upgrade to Jelly Bean since I need to do it manually.
What is the difference between the 'firmare' and the 'source code'?
Which one would you use to flash the upgrade.
Also, just so I have a better understanding of the two would you be kind enough to provide a simple reason as to what each type is used for?
My gut guess is that we use 'firmware' to do the actually flash.
And the source code lets you look at what is inside and is 'uncomplied'
Where the firmware is the 'compiled and ready to go package.
Did I get it correct?
Thanks!
Rob
Rob
Sent from my SPH-D710 using Tapatalk 2
You are indeed correct. You need to download the firmware not source code
Sent from my Nexus 7 using Tapatalk 2
Yeap he's right you are pretty much spot on with the source code and firmware.
The firmware is the software package with the OS and drivers and libs and things such as that.
The source code is what developers use to modify the software, my analogy isn't the best but its kind of like if I needed to do a big structural renovation/addition on an existing building I would use the blueprints from original construction instead of reverse engineering by taking the entire building down one piece at a time to see what's load bearing, where hidden plumbing and electrical is, etc.
Source code is kinda like those blueprints.
Sent from my ADR6425LVW using xda premium
Hi,
The Source Code is really the code written by hand with a keyboard of the System Android. It is not compiled.
Compiled : It is the result of compiling the source code. It is in a state where you can use the system. Probably where you're looking for.
If you want the stock 4.1.1 Image for Nexus 7, check at the bottom of this page https://developers.google.com/android/nexus/images#nakasi
Sent from my Nexus 7 using xda premium
jamesst20 said:
Hi,
The Source Code is really the code written by hand with a keyboard of the System Android. It is not compiled.
Compiled : It is the result of compiling the source code. It is in a state where you can use the system. Probably where you're looking for.
If you want the stock 4.1.1 Image for Nexus 7, check at the bottom of this page https://developers.google.com/android/nexus/images#nakasi
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Question: The file from that link is in .tgz format.
Aren't the flashable files in .zip format?
How does one use the .tgz to get their Nexus 7 back to stock? Is there a link to the step by step instructions?
Thanks
Rob has sent this from his Nexus 7 using Tapatalk 2
If I were you, I would use Nexus 7 Toolkit V2, it has the option to 1st Download Stock Rom, 2nd Flash it , so yeah all you gotta have to do is enter some number to select what you want from menu
Just to make sure you understand few words :
Adb : Normal state when your device is turned on
PS: To flash a rom, your bootloader must be unlocked, there is the option to unlock it on the Nexus 7 Toolkit too Ah and if it is the first time you do that on your computer you gotta install the driver. Press 1 on the menu think
Sent from my Nexus 7 using Tapatalk 2
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
Other info:
Doesn't matter if it is a .tar.gz or a zip or a rar, because these extensions do likely the samething, they 'compress' files to distribute them easily. The reason why it doesn't matter is that the rom is gonna be extracted/decompressed
Sent from my Nexus 7 using Tapatalk 2
Does anyone have a link to the OTA update IAN76K from IAN76H? I know factory images are available for IAN76K, but I'm looking for the actual OTA file that was pushed to Nexus Q devices. Thanks in advance!
oldblue910 said:
Does anyone have a link to the OTA update IAN76K from IAN76H? I know factory images are available for IAN76K, but I'm looking for the actual OTA file that was pushed to Nexus Q devices. Thanks in advance!
Click to expand...
Click to collapse
I have this sneaking suspicion that the I/O Q's shipped with H loaded but K in the recovery or whatever. I noticed that mine had changed when i did a factory reset. I don't know for sure though. Doubt anybody is able to get a logcat at this point in time. Do you have a device with ian67 H installed?
animal24 said:
I have this sneaking suspicion that the I/O Q's shipped with H loaded but K in the recovery or whatever. I noticed that mine had changed when i did a factory reset. I don't know for sure though. Doubt anybody is able to get a logcat at this point in time. Do you have a device with ian67 H installed?
Click to expand...
Click to collapse
No. I don't own a Q actually. I operate a firmware repository for every Nexus device from the Nexus S onward. I mirror official factory images and OTA updates for posterity. The site is http://randomphantasmagoria.com. I just added a page for the NQ today and was looking to see if anyone had the OTA link so I could mirror it.
Sent from my Galaxy Nexus using Tapatalk 2
If anyone that has a NQ is willing to take about 30 minutes to assist: I'd like to find the IAN67K ota:
If you would like to help, here's what you can do:
Reflash IAN67K (if you are not already on stock, and you must be on stock to do this)
Root your device
Change the following lines in build.prop:
Code:
ro.build.date.utc=1339795569
ro.build.fingerprint=google/tungsten/phantasm:4.0.4/IAN67H/384240:user/release-keys
Check for updates
Post the name of the update zip it downloads
TheManii said:
If anyone that has a NQ is willing to take about 30 minutes to assist: I'd like to find the IAN67K ota:
If you would like to help, here's what you can do:
Reflash IAN67K (if you are not already on stock, and you must be on stock to do this)
Root your device
Change the following lines in build.prop:
Code:
ro.build.date.utc=1339795569
ro.build.fingerprint=google/tungsten/phantasm:4.0.4/IAN67H/384240:user/release-keys
Check for updates
Post the name of the update zip it downloads
Click to expand...
Click to collapse
I'll give it a try in a little while.
You might need to check adb logcat while doing the check for updates, as we do not have the actual URL for it, just giving the filename will only give the filename.
I'm not sure how setting up adb works on the NQ though, I assume it's like normal devices as it has a usb port(?)
(if you know how to set up adb you can skip to step 7)
Download platform tools
Download usb drivers
extract both packages
Turn on usb debugging (I dont know the exact steps to do this on the NQ)
Install the drivers if windows requests it (and I am assuming you are using windows)
go to where you extracted platform tools and do "adb logcat"
Check for updates, if there is one available then post the contents of logcat
If you are able to get that far you can just directly post the logcat if you do not know how to read it.
animal24 said:
I'll give it a try in a little while.
Click to expand...
Click to collapse
Any luck?
Sent from my Nexus 4 using Tapatalk 2
oldblue910 said:
Any luck?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
http://android.clients.google.com/p...gned-tungsten-IAN67K-from-IAN67H.29d5a723.zip
Booya!
You, sir, are the man! Thank you!
Sent from my Nexus 4 using Tapatalk 2
oldblue910 said:
You, sir, are the man! Thank you!
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
No problem. I wish I would have seen this thread months ago. I would have done it then. I don't get over to the Nexus Q forums too often.
Sent from my Nexus 7 using xda premium
Well we only realised that this works a couple days ago, unless you actually had a NQ with IAN67H the entire time
TheManii said:
Well we only realised that this works a couple days ago, unless you actually had a NQ with IAN67H the entire time
Click to expand...
Click to collapse
I don't ever remember seeing IAN67H. As far as I can remember its been "k". I really hope its not the last version we'll see...
Sent from my Nexus 7 using xda premium
Given the current (lack) of news on the NQ, it seems unlikely.
I dont even own one but I'd hope it does too.
Like a hypothetical merger of NQ type media streamers and google TVs into KLP like how ICS merged tablets and phones.
But I digress
Because we now have this information, I have created a Nexus Q page on the website to mirror the firmware.
oldblue910 said:
Because we now have this information, I have created a Nexus Q page on the website to mirror the firmware.
Click to expand...
Click to collapse
Nice! Glad I could contribute.
Sent from my Nexus 7 using xda premium
looks like very few things were updated. framework-res, hub broker,libwvstreamcontrol, all the stuff in /app is about 1.8 to 2k..
animal24 said:
looks like very few things were updated. framework-res, hub broker,libwvstreamcontrol, all the stuff in /app is about 1.8 to 2k..
Click to expand...
Click to collapse
Yeah it seems like a very minor update.
User facing changes:
Hubbroker.apk got updated (what is this? is it the NQ's launcher?)
Music2.apk got updated
Lib/frameworks/non user facing updates:
/system/bin/common_time
/system/framework/ext.jar
/system/framework/framework-res.apk
/system/vendor/lib/libWVStreamControlAPI_L1.so (WV as in widevine?)
and that's it, every other file is simply updating the timestamp.
OK, so maybe a dumb question, so bare with me here. I m new to the Q but not the android world.
How would us users who have a stock Q go about updating to this latest version. I am having issues with my Q after about 20 minutes and was hoping to give this a whirl and see if it fixes it.
-Kovs
Kovs said:
OK, so maybe a dumb question, so bare with me here. I m new to the Q but not the android world.
How would us users who have a stock Q go about updating to this latest version. I am having issues with my Q after about 20 minutes and was hoping to give this a whirl and see if it fixes it.
-Kovs
Click to expand...
Click to collapse
I can almost guarantee you have the latest version as its been around since I got the Q last July.
I have the same issue you have as well. I'm pretty sure its a Google back end thing and not a problem with the build. Although Google may release an update that fixes the problem.
Sent from my Nexus 7 using xda premium
hey guys, so i know just a few posts below me there's a topic about when 4.2 will come to the N7. But what i'm wondering is if anyone has gotten their hands on the 4.2 GAPPS or anything of the sort, such as the new 4.2 keyboard and the 4.2 camera (not that the camera would be much use on an N7). I have the 4.2 GAPPS, keyboard and camera running on my S3, can i just use those same .zip files and flash them on my N7? or does it not just work that way.
Sent from my Nexus 7 using xda premium
The apps can be flashed on any device running 4.1 or later
Link
Be careful mate. I flashed the 4.2 gapps and once i rebooted i was constantly getting force closes on all the apps that got flashed.
My device was a real mess. I have not tried the separate apps like keyboard etc so i cant comment on them.
Edit...i did not flash the ones that the fellow member linked you to in the post above.
The ones in that link say the for any androud 4.1 device so you should be ok.
Sent from my Nexus 7 using Tapatalk 2
Ah, I assumed the OP already had the apps in the link I posted as he said about his S3 and the thread linked was in the S3 forum.
So yeah, make sure you're using the apps from the link and you should be fine as the post says its for any device running 4.1 or over. If you're unsure you could always perform a nandroid backup beforehand in case anything does go wrong.
yeah, that link is where I got the GAPPS from. I guess I didn't see the part about being able to flash it on anything. lol
thanks a bunch
sent from my Galaxy S³ using XDA-Premium
Hi Friends, I was wondering how to compile android from source for My MAKO Device ?
before anyone says that What the Heck ?? ____ I have been through many tutorials, unfortunatily those are for compiline CM which i am not able to clone on my Laptop due to some GIT access issue from my Workplace.
Further i followed the official documentation for compilind android on source.android.com and was able to bild the IMAGE but as soon as i flashed the Image My Nexus's scren got blank and nothing happened .
so, can someone please guide me on how to compile Android from Source (NO CM/ ETC.) for MAKO ..
Thanks in Advance.
AOSP (source.android.com) is android. Are you sure you compiled the right packages. That you included the prebuilts and everything?
Ya . I did everything step by step. And finally I got the images but after flashing the images on my N4 I got a blank screen after boot animation.
Do you have another link so that I can try that method !.
Sent from my Nexus 4 using XDA Free mobile app
gur-i said:
Ya . I did everything step by step. And finally I got the images but after flashing the images on my N4 I got a blank screen after boot animation.
Do you have another link so that I can try that method !.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Did you compile for the right device? I believe the guide on source.android.com is for the emulator.
Well they also have a device guide, which i followed , do i have to manually add device driver binaries as i did not do that as ot was not there in the guide.
Sent from my Nexus 4 using XDA Free mobile app
gur-i said:
Well they also have a device guide, which i followed , do i have to manually add device driver binaries as i did not do that as ot was not there in the guide.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
It is, maybe you should read it again to see if you haven't missed anything.
Sure SMillerNL, i will do it again and report back.
Another thing, is actually , when i compile the sorce, I get various images, bootloader.img, system.img, etc. So, How to make a flashable zip out of those, so i can test the rom on MultiRom on my device, rather than flashing from ground 0 , as nexus4 is my kinna daily driver mobile phone.
You have to run "make mako otapackage"
I've been learning and figuring out how to port MIUI, and I have a general understanding of it, would anyone be interested in a port for Nexus 4? I do not have a Nexus 4 on the ready though, so it'd have to have others testing it.
CrashDSB said:
I've been learning and figuring out how to port MIUI, and I have a general understanding of it, would anyone be interested in a port for Nexus 4? I do not have a Nexus 4 on the ready though, so it'd have to have others testing it.
Click to expand...
Click to collapse
Is it the global version of MIUI 8? Must be based on cm13. Right? I will be glad to be a tester.
Me...
Would be great to have a Miui8 for N4! I will be glad to be a tester.
im so interested
Miui 8? of course
Somebody tell me the procedure... I can port it...
I was reading the porting guide myself the other day... but it seems to be quite a bit of work!
Count me in. Currently running the last version.
Bleh........
Sent from my Nexus 4 using Tapatalk
CrashDSB said:
I've been learning and figuring out how to port MIUI, and I have a general understanding of it, would anyone be interested in a port for Nexus 4? I do not have a Nexus 4 on the ready though, so it'd have to have others testing it.
Click to expand...
Click to collapse
What's the status?
I'm interested
Past monday I've made one version based on AOSP 6.0.1 from xda
I can't test it yet, because I've only one nexus 4 and it's used on my work.
I've tried to flash but, I can't, get stuck on the begining of updater script. I think it was because I'm on TWRP and I need to change to Clock Work Recovery.
I have no time to flash it beacuse I need to travel out from home this week. All rejects should be repaired.
If some want to test, i'll put a link to my drive. It's a heavy zip about 650 Mb, I think some apk's should be removed like FM that will not work on our nexus 4 but I can't do it today..
magnus48 said:
Past monday I've made one version based on AOSP 6.0.1 from xda
I can't test it yet, because I've only one nexus 4 and it's used on my work.
I've tried to flash but, I can't, get stuck on the begining of updater script. I think it was because I'm on TWRP and I need to change to Clock Work Recovery.
I have no time to flash it beacuse I need to travel out from home this week. All rejects should be repaired.
If some want to test, i'll put a link to my drive. It's a heavy zip about 650 Mb, I think some apk's should be removed like FM that will not work on our nexus 4 but I can't do it today..
Click to expand...
Click to collapse
It's not a problem with TWRP, it's a rom size problem. Fullota.zip is too big and compatible with TWRP 3.0.2.
I'm reducing his size deleting sounds, apk's inside the zip.
I've made a first version that can be flashed (takes really long long time it's about 550Mb).
Unfortunatelly, boot begins, miui animation is charged, but get stuck with this message in logcat
11-09 07:24:07.017 186 186 E kickstart-qcks: File '/firmware/image/efs1.mbn'
was not found
E kickstart-qcks: Prepend failed.
Seems a problem with boot.img but don't know yet how to resolv this...:crying:
whats the latest news
I love you miui
Efs partition relates to the modem and radio I'm pretty sure are you sure its not that
Sent from my Nexus 4 using Tapatalk
It's a boot.img problem. I Need to study it, but i have no time...
I just bought a Redmi note 3 pro. So my, now, i have a spare nexus 4 just for test, so feel free to send me roms and i'll give you the logcat.
Hope i can help!
---------- Post added at 02:30 AM ---------- Previous post was at 02:30 AM ----------
I just bought a Redmi note 3 pro. So my, now, i have a spare nexus 4 just for test, so feel free to send me roms and i'll give you the logcat.
Hope i can help!
miuı 7 problems rom