So I finally get my Spanking new Nexus 5 this morning I switch it on and its running Keylime Pie?!!?! WHY? whats going on? Phone was sealed in box brand new i'm shocked
Slorks said:
So I finally get my Spanking new Nexus 5 this morning I switch it on and its running Keylime Pie?!!?! WHY? whats going on? Phone was sealed in box brand new i'm shocked
Click to expand...
Click to collapse
Interesting. DO A BACK UP and upload the rom. I wonder if there are some goodies in there?
Kernel build date is different too. Mine says October 22nd
Sent from my Nexus 5 using xda app-developers app
egofreak said:
Interesting. DO A BACK UP and upload the rom. I wonder if there are some goodies in there?
Click to expand...
Click to collapse
Its horrible its laggy buggy and everything force closes i was lucky i got a screen shot in.
Slorks said:
Its horrible its laggy buggy and everything force closes i was lucky i got a screen shot in.
Click to expand...
Click to collapse
There could still be goodies?
Still interesting. Whats the build number on that phone? Sounds like you have one that either missed getting updated before being shipped, or an old one from the back of the store room. Who knows, might have the code for "Always listening" Google now hiding under all the bugs?
egofreak said:
There could still be goodies?
Still interesting. Whats the build number on that phone? Sounds like you have one that either missed getting updated before being shipped, or an old one from the back of the store room. Who knows, might have the code for "Always listening" Google now hiding under all the bugs?
Click to expand...
Click to collapse
its all up there in that one screen shot i put in build number and everything.
I emailed the seller waiting to either return it or just update it myself.
Well, I came into this thread expecting completely different results.
OP, do a system dump and upload it. Maybe there are some goodies on there that we can use. It seems you've got your hands on a test/debug build of Android. Does the phone hardware look like it should? "nexus" printed on the back, area where the IMEI sticker should be, etc.?
Johmama said:
Well, I came into this thread expecting completely different results.
OP, do a system dump and upload it. Maybe there are some goodies on there that we can use. It seems you've got your hands on a test/debug build of Android. Does the phone hardware look like it should? "nexus" printed on the back, area where the IMEI sticker should be, etc.?
Click to expand...
Click to collapse
yup its legit sticker on the screen IMEI sticker on the back i switch it on and the boot animation was from the first build of ICS only it was cropped in the middle of the screen then to my surprise i'm running Keylime pie. Ive never done a system dump before i'm on this other thread now figuring out how to flash stock kit kat. It's frustrating. You're like "this is not what i paid for" you know?
Slorks said:
yup its legit sticker on the screen IMEI sticker on the back i switch it on and the boot animation was from the first build of ICS only it was cropped in the middle of the screen then to my surprise i'm running Keylime pie. Ive never done a system dump before i'm on this other thread now figuring out how to flash stock kit kat. It's frustrating. You're like "this is not what i paid for" you know?
Click to expand...
Click to collapse
Maybe don't buy a brand-new device second-hand.
That's always a bad sign. Either the device had issues and they're too lazy to return it or it's fake...possibly they don't like it but there's probably reasoning behind that to merit immediately selling a $400 phone a week max after receiving it.
That's REALLY strange. Kinda cool. I think you got a test device.
Jubakuba said:
Maybe don't buy a brand-new device second-hand.
That's always a bad sign. Either the device had issues and they're too lazy to return it or it's fake...possibly they don't like it but there's probably reasoning behind that to merit immediately selling a $400 phone a week max after receiving it.
Click to expand...
Click to collapse
Where did you see he got it second hand?
Interesting. Under "Model Number" it also says "AOSP on Hammerhead". Also why would it say "KeyLimePie" instead of an actual number like "4.4" under Android Version. Something odd is going on here.
Slorks said:
its all up there in that one screen shot i put in build number and everything.
I emailed the seller waiting to either return it or just update it myself.
Click to expand...
Click to collapse
Hold up on that. At least do a system dump first.
If you don't know how use this guide.
http://forum.xda-developers.com/showthread.php?t=2380797
If you don't have the android SDK go here and download the platform tools attached in the 8th comment and open command line there then follow that guide.
http://forum.xda-developers.com/showthread.php?p=33510112
Also you need to enable android debugging.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Going to also say "Do a system dump" simply because A) You seem to be one of the very "lucky" few to have an older device and B) Who knows what kind of things are hiding in that system image.
I mean, its your phone and you paid for it so I don't blame you for wanting to just flash KitKat onto it. However, that system image could benefit the development community somehow. Either way, this is really interesting.
Looks like a test build for sure - if you google sangjoon84.lee you'll find that kernel build referenced in all the FCC info and prior N5 leaks.
Don´t update it for Pete´s sake, that might be a treasure! "Early Development device" ...in 10 years that´s gonna be worth something on ebay!
netsyd said:
Looks like a test build for sure - if you google sangjoon84.lee you'll find that kernel build referenced in all the FCC info and prior N5 leaks.
Click to expand...
Click to collapse
I just checked that aswell. It's weird though because other mentions of it have KyeLimePie whereas this screenshot shows it spelt correctly.
Sent from my HTC One using XDA Premium 4 mobile app
This isn't the first time a non shipping build came with a nexus phone.
In fact, all of our N5's shipped with key lime pie. It just forced an update at setup.
The reason why this didn't update is its not in an OTA path. Its a test build.
Sent from my Nexus 5 using XDA Premium 4 mobile app
OP if you are willing to dump the system image for us here are some easy steps on doing that.
Download the Android tools here
All you have to do is dump the contents of the zip onto your C: directory. Enable USB debugging on your phone and plug it in via USB. Then open CMD prompt and type:
CD C:\
You should then see
C:\
Now just type:
adb.exe pull /system/
This will dump the image which you can then zip and share later if you wanted. I would advise doing a dump seeing as how this is extremely rare. Again though, its your call.
Is it already unlocked? Would be wild if this was just some Google employee's test device for a couple weeks or simmering!
Sent from my Nexus 5 using Tapatalk
Yup, my device as I am sure everyone else's here aksed for an immediate update once it booted up so who knows what was there before.
Related
Short Story:
----------------
Yesterday I bought Google Nexus from my local MacMall (Chicago), and I was pretty stoked. The first thing I noticed upon opening it was that the box had been re-sealed. Then I tried to turn it on and the battery was dead. I thought that was kind of unusual, but not unheard of. Then I charged it and turned it on...
Below are pictures describing what I saw. I am going to exchange the device this afternoon. I was wondering if anyone has ever seen something like this and would anyone be interested in playing around with this ROM. I would imagine it is a proprietary ASUS build, but they sold it to me so it's mine now. I would be happy to post a link to the ROM, but I don't know how to extract it. (I'm sure there is a post explaining that, please direct me to it).
Here are links to the pictures:
There is a weird bar at the top:
moworldenterprises(dot)com(slash)Testing(slash)Nexus(slash)SS01.jpg
Here is the version info:
moworldenterprises(dot)com(slash)Testing(slash)Nexus(slash)SS02.jpg
Here are some of the testing apps:
moworldenterprises(dot)com(slash)Testing(slash)Nexus(slash)SS03.jpg
The serial number is all 1's:
moworldenterprises(dot)com(slash)Testing(slash)Nexus(slash)SS04.jpg
let me know if you want me to post any other information/pictures about the device.
PhatWebah said:
Short Story:
----------------
There is a weird bar at the top:
www.moworldenterprises.com/Testing/Nexus/SS01.jpg
Here is the version info:
www.moworldenterprises.com/Testing/Nexus/SS02.jpg
Here are some of the testing apps:
www.moworldenterprises.com/Testing/Nexus/SS03.jpg
The serial number is all 1's:
www.moworldenterprises.com/Testing/Nexus/SS04.jpg
let me know if you want me to post any other information/pictures about the device.
Click to expand...
Click to collapse
Fixed the links for you.
sweet, hopefully there is something useful
Do NOT return this! This is a very good find! Maybe if you could unlock the bootloader and make a Nandroid backup in CWM...
Perhaps stick it on ebay as a Buy It Now for the price it would cost you to order another one...
That way if it is truly interesting to someone, they have to opportunity of putting up (or shutting up).
No do not unlock it yet, it will erase everything. Do a system image dump. There is a toolkit in the developers section. Post it in there.
Also i noticed its running ICS
Don't send it back yet, let the devs get what they need
DroidHam said:
Don't send it back yet, let the devs get what they need
Click to expand...
Click to collapse
Lol.
The devs don't need anything from this unless you actually want to DOWNGRADE your device.
We can build AOSP from source, we don't need this build for anything at all.
Just put it on eBay :good:
Sorry I'm a Noob
nerfman100 said:
Do NOT return this! This is a very good find! Maybe if you could unlock the bootloader and make a Nandroid backup in CWM...
Click to expand...
Click to collapse
I thought someone here might want this, but I have to return it today (it is for my wife). I'm "good with puters" so I can follow instructions well, but I've never rooted or jailbroken anything in my life. I'm at work so I don't have lots of time to search forums for the proper instructions. If someone really wants this, you have about two hours to post instructions for me to backup or image or whatever it is called a copy of this ROM before I return it. I'll check back every five.
I am downloading the Root Toolkit now
KiNG OMaR said:
Lol.
We can build AOSP from source, we don't need this build for anything at all.
Just put it on eBay :good:
Click to expand...
Click to collapse
Thanks, that's all I needed to know, I'll just return it and get a stock one. Just out of curiosity, and in case someone on the forums wants it, how would I go about "copying" this ROM? and could it be done in the next hour?
DroidHam said:
Don't send it back yet, let the devs get what they need
Click to expand...
Click to collapse
This actually made me lol
You do know this is a nexus tablet right???
Sent from my Nexus 7 using xda premium
ICS on it. How strange. Makes you wonder if they were intending to launch with that on it instead of JB.
Does it have any screen raise issues or faults?
Again, I'm a Noob.
Arthur Hucksake said:
Does it have any screen raise issues or faults?
Click to expand...
Click to collapse
I'm not really sure what you mean by "raise issues or faults". It's hard to show, but when I drag my finger accross the screen, it draws a line with many dots and H and V coordinate lines. That was a horrible description. Basically, it looks like it is mapping the touchscreen feedback and then rendering a line. The line quickly disappears. The white and red boxes at the top of the screen acually have numbers written on them and those numbers change as you touch the screen. There is also like a red Frame the flashes on the screen when I select an app. I will try to post some some pictures/maybe a video. My phone sucks though so the quality wont be that good.
PhatWebah said:
I'm not really sure what you mean by "raise issues or faults". It's hard to show, but when I drag my finger accross the screen, it draws a line with many dots and H and V coordinate lines. That was a horrible description. Basically, it looks like it is mapping the touchscreen feedback and then rendering a line. The line quickly disappears. The white and red boxes at the top of the screen acually have numbers written on them and those numbers change as you touch the screen. There is also like a red Frame the flashes on the screen when I select an app. I will try to post some some pictures/maybe a video. My phone sucks though so the quality wont be that good.
Click to expand...
Click to collapse
What you're describing is the 'Show touches' and 'Pointer Location' options that can be enabled in Settings>Developer options on Jelly Bean.
Video:
moworldenterprises(dot)com (slash)Testing(slash)Nexus(slash)weirdness.3pg
KiNG OMaR said:
Lol.
The devs don't need anything from this unless you actually want to DOWNGRADE your device.
We can build AOSP from source, we don't need this build for anything at all.
Just put it on eBay :good:
Click to expand...
Click to collapse
It appears to have test apps not included in AOSP.
You should try to cold boot to recovery from the bootloader and see if it'll go without being hooked up to a computer. Maybe the bootloader is different than production.
Can't he try flashing the stock rom over this? If there are no hardware faults, why risk getting one that might be defective?
What would devs need from this ... This isn't a Samsung / HTC device
Sent from my HTC One X using Tapatalk 2
Please do a nandroid. Tests have shown ICS has better raw performance than JB. I would love to see an ICS ROM on these at least to just test it out.
Sent from my Nexus 7 using xda app-developers app
Hi,
I was really hoping the rumors would have been true and the Nexus 7 2 would have been announced. I was ready to pre-order last week. That didn’t happen so I pulled the trigger on the current Nexus 7. While I'm disappointed that I didn't get to get the brand new one I am VERY happy with it so far. I also got the official Nexus dock and a keyboard case. I have to say the official dock is so great I may buy a 2nd one! It’s overpriced but soooo nice.
Anyway, one thing I want to do right away is be able to get and send SMS texts from my phone on my N7. I have a Droid Razr Maxx by the way. What is the best software to do this?
Is there a free way to turn on the wireless tether on my Razr so I can connect my N7 to it? I also play Ingress and it would be cool to be able to use the N7 for that.
I'm not ready to root and try a custom ROM yet but what are some of the "must have" apps for the N7? Any info would be great!
Thanks
:cyclops:
Tablet Talk
Text from Tablet-SMS Messaging
Fox-Fi
Droid9 said:
While I'm disappointed that I didn't get to get the brand new one I am VERY happy with it so far.
Click to expand...
Click to collapse
lol the "new one" doesn't even exist, the disappointment is unfounded for the time being
lolcopter said:
lol the "new one" doesn't even exist, the disappointment is unfounded for the time being
Click to expand...
Click to collapse
Well yes but I think we all know there will be a new one sometime in the next 6 months.
Droid9 said:
Well yes but I think we all know there will be a new one sometime in the next 6 months.
Click to expand...
Click to collapse
Possibly, but being mad about not being able to buy something which doesn't even exist yet is a waste of time and energy
lolcopter said:
Possibly, but being mad about not being able to buy something which doesn't even exist yet is a waste of time and energy
Click to expand...
Click to collapse
He didn't say he was mad. He was hoping for a new release, there wasn't so he just bought what was available now.
Sent from my LG-P999 using xda app-developers app
Save the disappointment for when the new version is actually released I guess
Current logic is flawed, that's all. I'll shut up now, carry on.
FWIW OP, I was expecting an updated OS, when that didn't happen I unlocked, rooted, and began flashing whatever I wanted
redmonke255 said:
He didn't say he was mad. He was hoping for a new release, there wasn't so he just bought what was available now.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Exactly. I wasn't going to buy the current one until after the big Google announcement. That would just be dumb. But again, I love this device so lets stop talking about "what if" or "when it does come out"... I want to talk about the cool things this one can do.
:cyclops:
Since its brand new, i'd recommend unlocking and rooting right away, just to get that out of the way should you wish to flash stuff later. Better to do it early since unlocking wipes everything and there's little data to keep that early. Having said that, I just finally unlocked/rooted after months of ownership and replacing all the data was trivial. Just a recommendation.
It's a very capable tablet completely stock, I just like tweaking things and the tablet UI is cool IMO.
lolcopter said:
Since its brand new, i'd recommend unlocking and rooting right away, just to get that out of the way should you wish to flash stuff later. Better to do it early since unlocking wipes everything and there's little data to keep that early. Having said that, I just finally unlocked/rooted after months of ownership and replacing all the data was trivial. Just a recommendation.
It's a very capable tablet completely stock, I just like tweaking things and the tablet UI is cool IMO.
Click to expand...
Click to collapse
Can you direct me to the easiest unlocking instructions?
Droid9 said:
Can you direct me to the easiest unlocking instructions?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1766475
Used this yesterday it worked perfectly, just follow the instructions, fix the drivers etc and it's a cakewalk
Droid9 said:
Can you direct me to the easiest unlocking instructions?
Click to expand...
Click to collapse
I think Wugs tool is pretty easy.
http://forum.xda-developers.com/showthread.php?t=1766475
Hello
As you know the release of Samsung Galaxy S4 GE and HTC One GE offering the same flavour as Nexus users already have a taste for.
Do you think inclusion of the new type of camera app and various other features in these junks defeats the purpose of owning a Nexus? It is we who should get the update of even a minute bug squash or changes to any core app.
What would be the update cycle of these junk phones? Will the Android updates be prioritised for the Nexus or will it released for the junks together?
Sorry for being rude, as a loyal Nexus fan, I seriously hate these so called idiotic Google Edition.
ngr.hd said:
Hello
As you know the release of Samsung Galaxy S4 GE and HTC One GE offering the same flavour as Nexus users already have a taste for.
Do you think inclusion of the new type of camera app and various other features in these junks defeats the purpose of owning a Nexus? It is we who should get the update of even a minute big squash or changes to any core app.
What would be the update cycle of these junk phones? Will the Android updates be prioritised for the Nexus or will it released for the junks together?
Sorry if I was rude, being a loyal Nexus fan, I seriously hate these so called idiotic Google Edition.
Click to expand...
Click to collapse
Well, this killed it for me
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
trentreed said:
Well, this killed it for me
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
Click to expand...
Click to collapse
I'm right there with you buddy. The reason I love Nexus devices is, if something goes wrong I can flash the factory image and everything is good again. No factory image from Google = no go for me.
Edit: Before I start to see "HTC has the ruu and Samsung phones use Odin to flash back to stock". I don't like one click methods. I want to fastboot flash all the images one at a time so I can see what's going on.
Sent from my Nexus 4 using xda premium
trentreed said:
Well, this killed it for me
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
Click to expand...
Click to collapse
Bullseye!
Just wondering if you can flash sense/touchwiz to these phones.
LoVeRice said:
Just wondering if you can flash sense/touchwiz to these phones.
Click to expand...
Click to collapse
Why would someone do that? Just get the regular version...
Sent from Holy Terra on a paranoid nexus 4
lyall29 said:
I'm right there with you buddy. The reason I love Nexus devices is, if something goes wrong I can flash the factory image and everything is good again. No factory image from Google = no go for me.
Edit: Before I start to see "HTC has the ruu and Samsung phones use Odin to flash back to stock". I don't like one click methods. I want to fastboot flash all the images one at a time so I can see what's going on.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Its the same thing... You can see it happening step by step and what's occurring during each step.. That's silly if you ask me..
What turns me off is the simple fact that they are fake nexus devices.. While we will get Google updates almost immediately, those devices still have to rely on HTC or Samsung remembering to keep their thumbs out of their asses..
Sent from my Nexus 4 using xda app-developers app
http://www.droid-life.com/2013/06/2...eive-updates-shortly-after-they-are-released/
trentreed said:
Well, this killed it for me
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
Click to expand...
Click to collapse
I sound like a broken record saying this since day 1. The OEMs have to put their proprietary drivers and kernels (firmware) into the image or the software wont' know how to communicate with the hardware. I guess if the OEMs were willing to release them to Google then I guess Google could handle the updates. Then you have to ask: why would Google take on that responsibility? Would the OEMs openly give Google those drivers in a day and age where anyone can sue anyone over anything because something looks similar to something else? None of that makes sense.
Yeah I'm kinda dissapointed... I want the latest and greatest on my N4 but still don't have it... Hopefully it's just a matter of days... Hopefully hours....
Sent from my Nexus 4 using xda app-developers app
PJcastaldo said:
Its the same thing... You can see it happening step by step and what's occurring during each step.. That's silly if you ask me..
What turns me off is the simple fact that they are fake nexus devices.. While we will get Google updates almost immediately, those devices still have to rely on HTC or Samsung remembering to keep their thumbs out of their asses..
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
One click methods are in no way "the same thing".
Edit: I'm not trying to start an argument here, its my personal preference. If you like one click methods then thats fine.
ngr.hd said:
Do you think inclusion of the new type of camera app and various other features in these junks defeats the purpose of owning a Nexus? It is we who should get the update of even a minute bug squash or changes to any core app.
Click to expand...
Click to collapse
I don't understand what you are saying. What other "features" are you talking about? A red phase beam wallpaper? These phones haven't been released yet. My guess is the N4 will get those changes when 4.3 is released which may come before the GE phones are even released. Most likely lots of backend changes to the camera were needed to get it to work with the new driver hardware in the GE phones.
Once they launch will be the last time they have something the Nexus doesn't. The moment Google said that HTC/Samsung were responsible for updates and they weren't hosting/posting source means those phones will almost certainly be behind the Nexus.
bozzykid said:
I don't understand what you are saying. What other "features" are you talking about? A red phase beam wallpaper? These phones haven't been released yet. My guess is the N4 will get those changes when 4.3 is released which may come before the GE phones are even released. Most likely lots of backend changes to the camera were needed to get it to work with the new driver hardware in the GE phones.
Click to expand...
Click to collapse
That's the point, why are GEs getting the new camera app with new arc like settings and Nexus are left behind. Why is that "we" should wait for 4.3 and expect that the new camera would be included in that. It is a clear blow to the loyal Nexus owners who actually gets all updates to the Android first, even a small bug squash.
And talking about other features, I'm sure there would be some still hidden not available to the Nexus owners.
lyall29 said:
I'm right there with you buddy. The reason I love Nexus devices is, if something goes wrong I can flash the factory image and everything is good again. No factory image from Google = no go for me.
Edit: Before I start to see "HTC has the ruu and Samsung phones use Odin to flash back to stock". I don't like one click methods. I want to fastboot flash all the images one at a time so I can see what's going on.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
+1 Only Nexus reveal the real beauty of Android.
ngr.hd said:
That's the point, why are GEs getting the new camera app with new arc like settings and Nexus are left behind. Why is that "we" should wait for 4.3 and expect that the new camera would be included in that. It is a clear blow to the loyal Nexus owners who actually gets all updates to the Android first, even a small bug squash.
And talking about other features, I'm sure there would be some still hidden still not available to the Nexus owners.
Click to expand...
Click to collapse
Oh boo-hoo. We'll get an update soon enough.
Sent from my Nexus 4 using xda premium
El Daddy said:
Oh boo-hoo. We'll get an update soon enough.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Hmm...wait and watch.
why are some people sooo sensitive, "my nexus should get this first" , "all others must wait" ...
look a little out of the box, these Google Edition phones are promoting stock android, whether they'll get updates parallel with the nexus or will join after a few days/weeks delay it doesn't matter. We all want more stock android options, and that's a step in the right direction, popularizing stock bloat-free android.
So, yeah, grow up and stop acting like samsung galaxy/iphone/etc.. blinded fanboys.
Can't believe you guys are complaining about a new camera app and live wallpaper. Nexus is just asop pure android 100% Google stuff... Doesn't mean Google owes us latest of the latest updates.
Sent from my Nexus 4 using xda app-developers app
ngr.hd said:
That's the point, why are GEs getting the new camera app with new arc like settings and Nexus are left behind. Why is that "we" should wait for 4.3 and expect that the new camera would be included in that. It is a clear blow to the loyal Nexus owners who actually gets all updates to the Android first, even a small bug squash.
Click to expand...
Click to collapse
How do you know the GE phones will get those features first? They haven't even been released yet? And they won't be in users hands until after July 9th.
Hello everyone!
This is my first attempt at porting Android Wear to the Galaxy Gear! I am not an experienced dev and this was done fairly quickly using null_23 as a base and the Gear Live system dump. This is not at all ready and definitely not ready to flash. If you do decide to flash it, you risk bricking your device. That being said, I am requesting that a more experienced dev check over my work. If it seems in order, then it will be tested, until such a time, test at your own risk.
Link: http://d-h.st/go2
UPDATE: [ONLY FOR BRAVE PEOPLE INTERESTED IN TESTING]: Since I used null_ as the base, the addons are still available, but please do not flash any of them! And use the stock kernel for the time being!
UPDATE 2: It might be a good idea to try using the custom kernel we have available to us. If I can get an updater script from the gear live or other android wear device and look in to modifying the bootclasspath in the preexisting custom kernel that we have.
UPDATE 3: I have figured out how to modify the bootclasspath, will make the modification shortly. I just need an updater script for an android wear device and we may have a booting android wear port.
UPDATE 4: Link to Attempt 2 coming soon. This has a modified updater script that will hopefully set all permissions correctly. This may be all it needs to boot properly. If not, then I may still need some help getting the Gear Live Kernel to modify our kernel's bootclasspath. If anyone would like to flash this, same as before, I can't guarantee anything will work or that your device will work afterward.
Link: AWAttempt2.zip
UPDATE 5: added my slightly modified updater files from fomey's null_ ROM attached at the bottom. fomey, if we get this working, could you package it in to null_ as a second ROM option?
TekGadgt said:
Hello everyone!
This is my first attempt at porting Android Wear to the Galaxy Gear! I am not an experienced dev and this was done fairly quickly using null_23 as a base and the Gear Live system dump. This is not at all ready and definitely not ready to flash. If you do decide to flash it, you risk bricking your device. That being said, I am requesting that a more experienced dev check over my work. If it seems in order, then it will be tested, until such a time, test at your own risk.
Link: http://d-h.st/go2
Click to expand...
Click to collapse
Dude, you are fast!
I will not try it out right away because i just set up Null 23 and cloudnotifier so that to have notifications on the iPhone.
BTW, is there any chance that it will work with an iPhone. Ala Google Glass, that is.
TekGadgt said:
Hello everyone!
This is my first attempt at porting Android Wear to the Galaxy Gear! I am not an experienced dev and this was done fairly quickly using null_23 as a base and the Gear Live system dump. This is not at all ready and definitely not ready to flash. If you do decide to flash it, you risk bricking your device. That being said, I am requesting that a more experienced dev check over my work. If it seems in order, then it will be tested, until such a time, test at your own risk.
Link: http://d-h.st/go2
Click to expand...
Click to collapse
I just tried it out with the installation through TWRP, definitely not working as you said yet, just boot loops. I've been looking around in the zip and I see no problems that were noticeable. Hopefully this port of android wear can happen!
Sent from my SM-N900V using XDA Premium 4 mobile app
sandvich123127 said:
I just tried it out with the installation through TWRP, definitely not working as you said yet, just boot loops. I've been looking around in the zip and I see no problems that were noticeable. Hopefully this port of android wear can happen!
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for testing so quickly! I'm glad it did not cause any serious issues to your device. I will do some talking with some devs I know and see what I can get worked out. Porting to the 1 will actually be easier than to the 2 or Neo, since there is an android base for the 1, unlike the 2 and Neo which are Tizen only.
Do you have a change log? If this is based on Null, it's still 4.2, while the wear launcher, if I remember correctly, requires a newer version of Android, probably 4.4. Just curious what your plans are to deal with that. Seems to me the only real options are either editing the wear app or porting 4.4 aosp and hoping the launcher works. Theoretically, the gear live dump could be ported but the major difference between cpus makes it a much more difficult task than people originally hoped. I think the best chance would be if a dev team (ie CM) were to pick up the protect, but there's the downside to a large bounty: there's a lot of people wanting to go it alone for the cash.
Sent from my VS985 4G using XDA Free mobile app
Trust me, I'm not doing this in an attempt to get the bounty. The money doesn't interest me at all. As far as the change log goes, this is the absolute first attempt, so there hasn't been anything changed yet. So again, this was a quick attempt in an effort to get the ball rolling and get the community involved in the development.
TekGadgt said:
Trust me, I'm not doing this in an attempt to get the bounty. The money doesn't interest me at all. As far as the change log goes, this is the absolute first attempt, so there hasn't been anything changed yet. So again, this was a quick attempt in an effort to get the ball rolling and get the community involved in the development.
Click to expand...
Click to collapse
No worries, I didn't think you were. You didn't have the typical billion "Donate please!" links that they would.
But what does first attempt mean? Just null kernel and modules with gear live system folder? I know a little about these things so I'd like to take a look, mostly out of curiosity, so I'd like to know what you've already done, preliminary as it is.
I agree though, we needed some kind of thread started and I agree that it's too early to put anything in the development forum.
Sent from my VS985 4G using XDA Free mobile app
Sent from my VS985 4G using XDA Free mobile app
JesusFreak316 said:
No worries, I didn't think you were. You didn't have the typical billion "Donate please!" links that they would.
But what does first attempt mean? Just null kernel and modules with gear live system folder? I know a little about these things so I'd like to take a look, mostly out of curiosity, so I'd like to know what you've already done, preliminary as it is.
I agree though, we needed some kind of thread started and I agree that it's too early to put anything in the development forum.
Sent from my VS985 4G using XDA Free mobile app
Sent from my VS985 4G using XDA Free mobile app
Click to expand...
Click to collapse
Not just a swapped out system folder. the base of the null_ system folder is still there. I only migrated the things necessary for a standard port. The only issue is that there is no ROM for the gear live yet, so a proper permissions section is not available for me to port from the updater script of the live to the updater script of the galaxy gear. I'm pretty convinced that if someone with a little more knowledge than myself edited the updater script permissions section to set the proper permissions for the new files, that this would at least boot.
Hi guys, I stumbled across this ebay listing item number 161368138405 . The seller claims he will update your gear to 4.4.2 for £25 + p & p , I have emailed the developer a link to the bounty thread, hopefully he may be able to help.
Sent from my SM-T320 using Tapatalk
Its some fake **** i think.
Would like to se a device info screen screenshot.
In the pictures he wirtes "This is not for the watch"
And later on "(1) Watch will become android 4,4,2"
Does he know what he is selling or not?
When he says "This is not for the watch", I think he means that you are not buying the watch in the picture. That is, you are not buying the physical watch, just the software upgrade.
I think it is high risk when you send your watch to him.
TekGadgt said:
...........
Click to expand...
Click to collapse
But for you rom is started?
4.2.2.
I wouldn't be surprised if he means 4.2.2.
He was pretty sure on his reply to me it was 4.4.2
RevengeDevTeam said:
But for you rom is started?
Click to expand...
Click to collapse
gingerdude said:
He was pretty sure on his reply to me it was 4.4.2
Click to expand...
Click to collapse
RevengeDevTeam: I have not necessarily classified this as a ROM, since it currently doesn't boot. That's why this is listed in the general thread. I am working on it, but there are no guarantees right now.
gingerdude: I'm pretty sure it's a scam. I wouldn't send him my watch if I were you.
gingerdude said:
Hi guys, I stumbled across this ebay listing item number 161368138405 . The seller claims he will update your gear to 4.4.2 for £25 + p & p , I have emailed the developer a link to the bounty thread, hopefully he may be able to help.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Yeah, the listing was ended by the poster because there was an error in the listing. I bet he got scared cause people started to figure him out.
Oh that's a shame. I thought it might give you guys a head start
Will be watching with interest
Sent from my Nexus 5 using Tapatalk
richlum said:
When he says "This is not for the watch", I think he means that you are not buying the watch in the picture. That is, you are not buying the physical watch, just the software upgrade.
Click to expand...
Click to collapse
So I emailed the seller and he said it was Null Rom but it was 4.4...apparently he was mistaken haha
--------------------------------------------------------------------------------
From: shagmeimbj
To: lexirodster81
Subject: Details about item: shagmeimbj sent a message about Samsung gear watch SM- V700 unlocking service to android 4.4.2 #161368138405
Sent Date: Jul-16-14 06:37:52 PDT
Dear lexirodster81,
Can you maybe send a screenshot of the 4.4.2 in the settings menu...not saying I don't believe you haha these pics could be from Null rom though which is 4.2.
- shagmeimbj
This was his response...
"Dear shagmeimbj,
Hello
This service is to install the null rom what is 4.4.2
- lexirodster81
Click "respond" to reply through Messages, or go to your email to reply
Respond
The support page for the Galaxy S6 has been updated to reflect that it’s going to receive the Marshmallow update on AT&T in the near future. The support page shows that version number G920AUCU3CPC2 will land on the handset, bumping it up to Android 6.0.1 Marshmallow.
Now that it has been confirmed that the update is going to start rolling out soon it’s not going to take long for the OTA to hit the airwaves
Nice.. I hope the edge is updated at the same time
Sent from my SAMSUNG-SM-G925A using Tapatalk
Well I see that the OTA can be manually downloaded and installed on the S6, hopefully the file for the S6 Edge is uploaded soon.
i gotta wait fot the odin ?
What's funny is that the build that is available for the s6 is nearly 2 months old so clearly AT&T has just been sitting on it. It has the March security update, not even the April. If this is indeed the final build and what we will see on the S6 Edge I'm very disappointed in both AT&T and Samsung. The 2016 Nexus can't come out fast enough for me.
I know that back in the day we were able to flash 920 Images onto the 925 but would lose the edge features. which . . . havbe been pretty ****ty TBH
+1
So apparently in the regular s6 thread going on they found there are much newer versions of 6.0.1 available right now, the latest being PD6 vs the PC2 reference by samsung that's nearly 2 months old. I guess Samsung jumped the gun and posted the wrong build so we have literally no idea when the update is actually coming right now.
I have absolutely had it with AT&T, their utterly STUPID reps, and their mind-numbingly slow software updates. If anyone else is in the same boat, I ask you to call them whenever you have free time and literally bug the living **** out of them. This is the only way we'll get the update sooner and if nothing else, it's payback. Here's some arguments I've used:
Other carriers have had it for weeks
Two months (today) since the last update
Marshmallow came out 7 ****ING MONTHS AGO and they have a whopping 4-5 phones updated to it (s7, g5, g4, g3, and v10 pretty sure)
Android N is already late in the beta stages
Also, ask for a manager or supervisor. They're more likely to escalate this issue to the higher-ups.
At this point, I honestly think it's just a way of them forcing us into buying the s7. From a business perspective, it makes perfect sense. They do it every year, they don't give us any information on the development of the software, and if no one makes a big deal over it, what's in it for them? Absolutely ****ing nothing.
Together maybe we can move them along.... slightly.
#marshmallow2018
troybrostrom said:
I have absolutely had it with AT&T, their utterly STUPID reps, and their mind-numbingly slow software updates. If anyone else is in the same boat, I ask you to call them whenever you have free time and literally bug the living **** out of them. This is the only way we'll get the update sooner and if nothing else, it's payback. Here's some arguments I've used:
Other carriers have had it for weeks
Two months (today) since the last update
Marshmallow came out 7 ****ING MONTHS AGO and they have a whopping 4-5 phones updated to it (s7, g5, g4, g3, and v10 pretty sure)
Android N is already late in the beta stages
Also, ask for a manager or supervisor. They're more likely to escalate this issue to the higher-ups.
At this point, I honestly think it's just a way of them forcing us into buying the s7. From a business perspective, it makes perfect sense. They do it every year, they don't give us any information on the development of the software, and if no one makes a big deal over it, what's in it for them? Absolutely ****ing nothing.
Together maybe we can move them along.... slightly.
#marshmallow2018
Click to expand...
Click to collapse
I really wouldn't waste your time/effort on this. AT&T is already aware, and they do not care.
Do you really want to get their attention? Stop buying their branded phones (a lesson I keep having to tell myself since purchasing this AT&T GS6 Edge..). This is a HUGE revenue stream for them - both from the sale of the actual phones at jacked up prices, as well as the kickbacks received from 3rd party bloatware contracts. Get an unbranded unlocked phone and make AT&T your dump pipe. They hate being that.
Suffice to say, I plan on getting either the HTC 10 or one of the new Nexus phones this year. Update and bloatware problems solved.
EDIT: MAJOR props to jetta311xx! He found a new .bin for MM for our GS6 Edges. See below:
https://xdmd.sl.attcompute.com/agents/48652/1488/SS-G925AUCU3BOJ9-to-U3CPD6-UP
Click to expand...
Click to collapse
brianbrain said:
I really wouldn't waste your time/effort on this. AT&T is already aware, and they do not care.
Do you really want to get their attention? Stop buying their branded phones (a lesson I keep having to tell myself since purchasing this AT&T GS6 Edge..). This is a HUGE revenue stream for them - both from the sale of the actual phones at jacked up prices, as well as the kickbacks received from 3rd party bloatware contracts. Get an unbranded unlocked phone and make AT&T your dump pipe. They hate being that.
Suffice to say, I plan on getting either the HTC 10 or one of the new Nexus phones this year. Update and bloatware problems solved.
EDIT: MAJOR props to jetta311xx! He found a new .bin for MM for our GS6 Edges. See below:
Click to expand...
Click to collapse
Good point. In regards to that link, it's asking me for credentials. Is this this a download for the Odin file so I could flash it to my phone?
Sent from my SAMSUNG-SM-G925A using Tapatalk
troybrostrom said:
Good point. In regards to that link, it's asking me for credentials. Is this this a download for the Odin file so I could flash it to my phone?
Sent from my SAMSUNG-SM-G925A using Tapatalk
Click to expand...
Click to collapse
Sorry about that - the download link is fixed now.
Rahilm has posted great instructions HERE. These are for the regular GS6 obviously, but the same flashing steps would apply for the Edge, just make sure you're using the right image first :good:
brianbrain said:
I really wouldn't waste your time/effort on this. AT&T is already aware, and they do not care.
Do you really want to get their attention? Stop buying their branded phones (a lesson I keep having to tell myself since purchasing this AT&T GS6 Edge..). This is a HUGE revenue stream for them - both from the sale of the actual phones at jacked up prices, as well as the kickbacks received from 3rd party bloatware contracts. Get an unbranded unlocked phone and make AT&T your dump pipe. They hate being that.
Suffice to say, I plan on getting either the HTC 10 or one of the new Nexus phones this year. Update and bloatware problems solved.
EDIT: MAJOR props to jetta311xx! He found a new .bin for MM for our GS6 Edges. See below:
Click to expand...
Click to collapse
I've tried and tried different commands, but I keep getting " cannot read 'sideload' ". Am I doing something wrong?
troybrostrom said:
I've tried and tried different commands, but I keep getting " cannot read 'sideload' ". Am I doing something wrong?
Click to expand...
Click to collapse
Make sure you have a working ADB installation. Try this one
---------- Post added at 03:10 PM ---------- Previous post was at 02:11 PM ----------
troybrostrom said:
I've tried and tried different commands, but I keep getting " cannot read 'sideload' ". Am I doing something wrong?
Click to expand...
Click to collapse
Troy - I was looking around, and you may want to try rebooting your workstation if you're sure you're running the most recent version of adb. This should resolve the cannot read issue.
brianbrain said:
Make sure you have a working ADB installation. Try this one
---------- Post added at 03:10 PM ---------- Previous post was at 02:11 PM ----------
Troy - I was looking around, and you may want to try rebooting your workstation if you're sure you're running the most recent version of adb. This should resolve the cannot read issue.
Click to expand...
Click to collapse
I am in the same boat, nothing I do will allow it to read the file. I tried on 2 PC's renaming it multiple times, even tried to make it into a zip file nothing is working.
justda said:
I am in the same boat, nothing I do will allow it to read the file. I tried on 2 PC's renaming it multiple times, even tried to make it into a zip file nothing is working.
Click to expand...
Click to collapse
I've tried restarting, reinstalling, re-anything lol. Also tried using .bin and .zip with no luck. Is there a video tutorial anywhere? Good luck to you, and let me know if you figure anything out!
I wish I had better news for you guys. It just seems that ADB can be a little finicky - it's not the update file. I ran into the same issue and once ADB decides to start doing this, it doesn't even bother reading the file.
These are the steps I took and I eventually got it to work:
Make sure that the update file is in the same directory as ADB
Verify that you are running the latest version of ADB
Rename the update to a short filename like "ota" and add the .zip extension
Verify in cmd that the file renamed with only a .zip extension and not something else (eg: not ota.zip.bin or ota.zip.zip)
Restart your computer
Before plugging phone in, run "adb devices" and verify daemon is started with no devices listed
Plug phone in and enter adb sideload mode
Run adb devices again and verify the presence of your device
Run adb sideload update.zip
If doing things in this order doesn't work, all I can suggest at that point is to completely remove all ADB installations, reboot, and do a fresh install of the latest version of ADB. Some people have reported success with going the nuclear route and loading the latest SDK, but it's all very much YMMV.
Its here and working!!!
bunnycool said:
The support page for the Galaxy S6 has been updated to reflect that it’s going to receive the Marshmallow update on AT&T in the near future. The support page shows that version number G920AUCU3CPC2 will land on the handset, bumping it up to Android 6.0.1 Marshmallow.
Now that it has been confirmed that the update is going to start rolling out soon it’s not going to take long for the OTA to hit the airwaves
Click to expand...
Click to collapse
Hit me up if you need a walkthrough.
Omfg I hate and love you at the same time. I'm at work right now, but will DEFINITELY be trying this as soon as I get home.
Sent from my SAMSUNG-SM-G925A using Tapatalk
Just finished the update and everything worked properly. Thank you for posting information on this. Now, the true test . . . a month later . . will it still speed along like its doing right now?