Develop Bugs

KIN Two setup tool:SPST

I got a file and some apps & drivers.
You can find a PDF file in the attachement.
Please read it to see whether it can help.
Apps & Drivers:
http-//rapidshare.com/files/455584224/KinTwoSetupApp.rar
( - should be replaced with : )
Hi guys, here is another USB driver for KIN TWO which is a little bit different to the one uploaded above.
http-//rapidshare.com/files/456921463/KUSBDrivers.rar
( - should be replaced with : )
Thanks to every one here.
Let's work together/

This looks to be exactly what we are looking for. This will definitely open up the possibilities of modifying the current kin os, or porting a new os to the device. However, this guide is useless without the tools and files mentioned in the document. You said you had some files as well, do you have these files?
SPST Vn.n.n.msi.
PB10ZUnPB20ZU (Lab) Vn.n.n.msi.
SPSTUSBDriverInstall.msi.
InstallPMXMTP.msi
With these files we be able to finally successfully hack this phone.

This is great. We have the resources, now we must figure out how to get a modified os on the phone using the tools.

Awesome find KinPhoneLover; not sure how and where you got this SPST, but it could be the very thing that is needed. For people who bricked their kin phones, they should try the "refurbish feature" to see if that will successfully reset their phones back to "factory mode". As for getting a new OS on the phone, in the pdf at the "Upgrade section", when you browse for the firmware file, it is a .ecn file. Not sure how flashing is done for Cyanogen and those other Android custom firmwares, or their file type extensions. If SPST only supports/allows .ecn files, that could be a problem trying to use those Android custom firmwares.

wow, this is exactly what we needed....did this get leeked or something? it says its from the sharp corp., so im guessing they got it somehow by chatting with them? why isnt there a lot of buzz about this??? i can read my phone number and everything off of this...so close to getting android, or just putting java apps on it..

Too bad its only 32 bit But yes. This is one step closer. Please, people with brick kin, test it out. See if we can get the ball rolling again.

Radar2004 said:
Too bad its only 32 bit But yes. This is one step closer. Please, people with brick kin, test it out. See if we can get the ball rolling again.
Click to expand...
Click to collapse
yes, i have to use my slow home computer, instead of using my quad core 64bit laptop

Just got everything up in running. Is anyone else having a problem with the SPST constantly dropping the connection with the phone and reconnecting? I'm not sure if this is due to running XP in a virtual box or if its something I can readily fix.

Short Answer: doesnt work.
Long Story: This needs your phone to be ON even for refurbish option and then, able to connect to a COM port. Unfortunately, that doesnt happen in SBL / APX mode and phone doesnt boot (autoreboots) so no COM mode available.
Just another software installed (for me).
No news in the front, guys. I guess i just need to get rid of verizon software (the one trying to get an OTA), not something from "normal" kin states.

Okay so now that we have a tool to upgrade the software all we need are custom firmware files to flash to it. However I don't see any option to read/dump the firmware using this software.

dezgrz seems to be correct, there don't seem to be a way to read/dump the current OS to make a backup of it. The PRL and ERI options don't seem to be what we want. The Provision option is the only option where we can read stuff from the phone. Could someone run that option, check all those settings (NAM1, security, feature, data, etc) and write it to a file and upload it? Maybe there will be something useful in there.

I gotta order a new battery, then I'll see if I can get anywhere with this... need to load up a 32bit OS first, apparently.
Either way, this is a huge step. Maybe not complete, but still a huge step. Thanks OP.

Hm..??
This seems interesting. I been watching this site until someone "Exploited" the phone. I have a mac, and does this work for kin? What does it do?

zero2duo said:
Could someone run that option, check all those settings (NAM1, security, feature, data, etc) and write it to a file and upload it? Maybe there will be something useful in there.
Click to expand...
Click to collapse
That features seem to be available already with "QPST" software... which didnt make anything advance (yet).
As i said, i renamed my NAM succesfully, and changed some security options (which i guess that doesnt matter, cause i *was* able to work anyway).

not much you can do that you cant do already, besides looking at your phones info. I was able to change voicemail numbers, was *86, i changed it to to just 8, and it says voicemail, but doesnt connect. Still playing around.

Why don't you just take it back to Verizon and get a replacement. How would they ever know you messed it up trying to hack it?

MicroNateDram said:
Why don't you just take it back to Verizon and get a replacement. How would they ever know you messed it up trying to hack it?
Click to expand...
Click to collapse
You should read the whole threads and/or other threads to understand why.

This phone needs to get hacked. I love my phone but i dont like the OS that the phone has. If this phone isnt hacked by the time summer comes, ill be glad to participate. I've hacked many phones but this may be a challenge. I would like to see apps on this phone.
PS I know the phone has java so where can i go to play games or apps for java?

Kinuser1 said:
PS I know the phone has java so where can i go to play games or apps for java?
Click to expand...
Click to collapse
Javascript

johnkussack said:
Javascript
Click to expand...
Click to collapse
Out of all the things I know, why wouldn't I know that its Javascript? Jeeezus. I would happily spend time on this phone but my grades are more important. Now what site could I go to on my phone to play apps/games.
P.S your post didn't really help me.

[Q] Toro plus binaries for SPH-L710 AOSP build?

I have built and slightly tweeked CM 10.1 but to be honest, it does drain that battery quite a bit and sometimes it freezes in landscape mode.
So I sync'ed up the source for the AOSP and then I realized that I needed binaries and I don't have the stock ROM to extract them from.
Are these "Galaxy Nexus (Sprint) binaries for Android master (20130603)" the right binaries for SPH-l710 ?
Under the Toroplus section at the very bottom of this page https://developers.google.com/android/nexus/drivers
Basically I just want try moding from stock because of the battery thing, I need to add Arduino support and maybe tweek USB or write an app, so that my phone can hook up over usb to an Arduino board and chit chat. I want the Arduino to control motors while Android gathers sensor data and decides where to go, Arduido will just follow orders. Anyways, battery consumption is huge in this project.
EDIT-1: Also, what version of Android are the 20130603 binaries for?

These are the binaries
https://github.com/themuppets/proprietary_vendor_samsung
d2spr folder.
That's not all you need to build for our device though.
I suggest just building an existing rom rather than syncing AOSP....you're gonna need to make a TON of edits to even get it to build, much less boot. I know because I'm very much involved with a new AOSP rom called omnirom and bring ups for that rom. It's not easy. We're still making edits to the source to even get it to build for non-nexus devices

CNexus said:
These are the binaries
https://github.com/themuppets/proprietary_vendor_samsung
d2spr folder.
That's not all you need to build for our device though.
I suggest just building an existing rom rather than syncing AOSP....you're gonna need to make a TON of edits to even get it to build, much less boot. I know because I'm very much involved with a new AOSP rom called omnirom and bring ups for that rom. It's not easy. We're still making edits to the source to even get it to build for non-nexus devices
Click to expand...
Click to collapse
hmm
I thought it would be a lot easier than it has been to build a stock rom, but I guess not, I am not trying to build kit-kat though, I want to build for 4.1.2 as I think thats where their updates left off but maybe I am way outta the loop.
What about the factory images? Are those flashable with the "flash-all.sh" over fastboot? Idk either way I haven't been able to get fastboot working, I don't think I have even been able to boot into fastboot, when I "adb reboot bootloader" I go to what looks like Odin's download mode, and when I do the volume up+down+power I just boot into "safe mode" and get to the launcher like normal but its in safe mode. I rooted it on Windows about a half a year ago or so using Odin and some dude's tuts on YouTube "High on Android" or something. I haven't really studied rooting so I guess thats my bad not knowing really what I was doing, but I haven't looked back and wouldn't be here now if it wasn't for it.
I'll take your word for it but I am going to keep trying to figure it out, Figureing out all this proprietary stuff is tuff, maybe I should get a device or board targeted to developers lol, didn't know Id ever say that, I thought I was going to major in Chemistry.

Edge-Case said:
hmm
I thought it would be a lot easier than it has been to build a stock rom, but I guess not, I am not trying to build kit-kat though, I want to build for 4.1.2 as I think thats where their updates left off but maybe I am way outta the loop.
What about the factory images? Are those flashable with the "flash-all.sh" over fastboot? Idk either way I haven't been able to get fastboot working, I don't think I have even been able to boot into fastboot, when I "adb reboot bootloader" I go to what looks like Odin's download mode, and when I do the volume up+down+power I just boot into "safe mode" and get to the launcher like normal but its in safe mode. I rooted it on Windows about a half a year ago or so using Odin and some dude's tuts on YouTube "High on Android" or something. I haven't really studied rooting so I guess thats my bad not knowing really what I was doing, but I haven't looked back and wouldn't be here now if it wasn't for it.
I'll take your word for it but I am going to keep trying to figure it out, Figureing out all this proprietary stuff is tuff, maybe I should get a device or board targeted to developers lol, didn't know Id ever say that, I thought I was going to major in Chemistry.
Click to expand...
Click to collapse
All of the downloads on the Google site are for and will only work with nexus devices
Those proprietary files are the bare minimum to "inject" our device's characteristics into a rom. That's how I ported Sense actually

CNexus said:
All of the downloads on the Google site are for and will only work with nexus devices
Those proprietary files are the bare minimum to "inject" our device's characteristics into a rom. That's how I ported Sense actually
Click to expand...
Click to collapse
Makes Sense.
So if I am learning anything... I would need binaries ("blobs"), I am sure Sprint, Google, and Samsung proprietary apps, and the nessiccary make (Android.mk) files, maybe some kernel patches and/or kernel object files, and hopeful to all hell I don't have to do too much XML modification I need to go find a trust-worth factory zip for the sph-l710 and rip everything I need out of that, and the bootloader I need to get it all back to stock eventually in case kit-kat does get updated by the Samsung (I am guessing thats whose hands it is in, I think they have a counter), who knows maybe the open source community will get there first.
Thanks for your help, saved me a ton of hassle.

[GUIDE][ROOT][CWM] ARCHOS 97b Platinum HD

I came upon this device on Christmas (a gift from my girlfriend to her father) and wanted to root it and also install clockworkmod recovery, so I could mess with it a bit without bricking it. Since I found a lack of tailored guides for it, I decided to write this one, although I really did no actual development whatsoever. Normally I would be posting this on general, but given the spirit of this forum, I guess I'll just leave it here. Also, keep in mind I don't have the device anymore and am writing this from memory. If I missed anything or you have any doubts, please let me know (for example, I can't recall specifically the drivers I installed to make it work properly).
Please, please read the whole guide before trying anything, and if you are a novice user, just leave this be, I don't want you to turn your tablet into a paperweight because of my shoddy instructions written from memory and you probably don't need any of this anyway as there are no custom roms yet.
!!!DISCLAIMER!!!: As stated above, anything you do is at your own risk. I provided the procedures that worked for me on a Qilive 97r tablet, which is an Auchan branded ARCHOS 97b Platinum HD, so my step by step should work for all of you. There are probably easier ways to do this, and I hint at them in the guide, but beware I have not tried them and cannot vouch for them. In fact, I cannot and will not take any responsability if you brick your device following these instructions, correctly or otherwise. You do this at YOUR OWN RISK. You have been warned!
Rooting:
I followed this guide on Windows 7 x64 and it worked perfectly.
So thanks to dhigby for that. I would just like to make a couple of remarks:
When you get to step 7 (Installing Superuser by ChainDD), don't. Install SuperSU by Chainfire instead, Use it to update the superuser binary (I think a prompt shows up) and when asked, let it delete the "other" superuser applications, that is, the chinese one. Clean and easy, you don't need to follow any more steps.
Congratulations, you now have (english language) root!
Clockworkmod Recovery:
There is no specific recovery for this device. Fortunately, thanks to AndroTab.info, there's a generic version for 3188 devices that you'll see should work quite nicely, albeight with some caveats.
What works:
Nandroid backup to/from external SDCard (won't recognize internal)
Installing zip files should also work, although I didn't try it at the time, as the device wasn't mine and I can't since I don't have it anymore, but since it mounts system partitions perfectly well I wouldn't think there would be a problem. Try it at your own risk though.
Other things probably work, give it a try.
What doesn't work:
Internal SDCard access
Probably other things
Installation:
Now that you have a rooted tablet, installing clockworkmod recovery is easy-peasy. Go to developer options and enable USB Debugging, then make sure you have a working adb daemon (look it up) that recognizes your tablet.
NOTE: I'm not sure if I had to install any specific drivers for this to work, I think if so they were installed while rooting by the chinese app. Anyhow, here's the Rockchip drivers, you might want to try to install them if you can't get a connection: http://www.rockchip.nl/downloads/
Download the file RK30GENERIC_CWM.zip from here - that's the recovery.
Now extract flash_image and recovery.img from the downloaded file above to the folder where you have your adb and follow the following commands.
Push the files to /dev partition on the device:
Code:
adb push flash_image /dev/
adb push recovery.img /dev/
Then enter root shell, like so:
Code:
adb shell
su
Now flash recovery.img into recovery partition with flash_image:
Code:
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
Now power off your device. To enter recovery press volume down then the power button and keep them pressed until CWM boots. Voilá!
NOTE: The instructions above were adapted from here and all credit goes to AndroTab.info ; I posted these particular instructions because they are the ones I used and worked for me; there are other methods listed on that page which might or might not work, TRY THEM AT YOUR OWN RISK.
Backing up your original recovery (for warranty, if anything goes wrong, etc.)
To obtain a backup image of your recovery \ restore it back afterwards, follow this guide here. All credit goes to Originalas.
Don't follow it to the letter though: first and foremost, you need a working linux installation. If you don't have one, I recommend Wubi.
Then:
Follow step 1;
Ignore step 2 (it's outdated);
Follow 3;
Follow 4 - but don't expect the screen to turn on, it won't, just hold the volume down button for 10 seconds or so after plugging it in, don't press the power button!
Ignore 5, 6 and 7
Follow 8, but don't use the last command to flash the CWM recovery onto the device. This is because since it is a generic version, it relies on the original recovery kernel. Flashing the image like stated in step 8 would probably overwrite the kernel and result in no recovery at all (I might be wrong about this).
Do follow the last command to restore your own backup if you ever need to.
I am unsure if recovery dumps obtained in this way are device specific; I don't see a reason why they should be, so I'll provide you with my own backup:
ORIGINAL RECOVERY
Flash through any method of your choice, but keep in mind I haven't tried this on other devices, so, as you know by now DO IT AT YOUR OWN RISK.
Closing remarks:
There you have it. Sorry for not holding your hand through every step, but this is meant for people who know a bit of what they're doing, making it faster than having to look up and figure out all these things and quirks on their own. If you have any doubts don't hesitate to ask, but keep in mind I don't have the device anymore and don't know much more than what I have written here. I do appreciate feedback and corrections, and will gladly change the guide giving you full credit - if it's really urgent just PM me, I might not check this thread often.
Cheers!

thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site

Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.

Newbleeto said:
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.
Click to expand...
Click to collapse
hi and thanx for the answer
yes i saw that it's almost stock but crappy optimized...in the very first start of the tablet i had 1.8gb occupied by nothing and clean master always notifies me that 90% of the ram is busy...meh
maybe just a kernel will fix like you say but you know, android 4.4 will be a must (rockchip already released sdk for 3188). I am not a coder (totally zero) but i will try your suggestion...just a question about the performance governor, does it drain more battery?

i am trying to backup my rom but cwm is so buggy...first was impossible, now i'm stuck on backing up boot image
there is a twrp available for this tablet?
solved

ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you

Dump stock ROM QiLive 97R
Jammed_Death said:
ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you
Click to expand...
Click to collapse
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.

Redinpais said:
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.
Click to expand...
Click to collapse
you can upload it on mega or gdrive or something like that
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
about the cwm, there is a way to mount sdcard?

Dump stock ROM QiLive 97R
Jammed_Death said:
you can upload it on mega or gdrive or something like that
Click to expand...
Click to collapse
Here he are...
https://www.wetransfer.com/download...556a9cf8fdbc6ddd7ab35ab820141126224717/09298e
Is only available until Decenber, 3 ,so Download it now.
Jammed_Death said:
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
Click to expand...
Click to collapse
I've been watching but I can not understand. Is confused. There are many files and do not know what to do to "fix".
If you are Portuguese, I would like to talk to you on Skype.
Can be?
Jammed_Death said:
about the cwm, there is a way to mount sdcard?
Click to expand...
Click to collapse
I don´t know how I can answer that. I'm new in android, so I sorry.

Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
Try this. Sooooooooo beautiful.:good:
(Because this - "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!" i can not put link now. So ask me by Skype) SORRY
:victory:
Follow the instrutions ther and enjoy KK 4.4.2 Oma ROM Iron KK v1.2 - 24-05-2013 (My QiLive say now - Nexus 7 :angel:
Regards

Qilive 97r
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.

Denysorlyk said:
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.
Click to expand...
Click to collapse
I'm interested

please ROM stock
Hello, i need help , if somebody know where I can download original rom , and original installer, I will be thankful for that's.

[test][rom]Anyone willing to do some ROM testing for this device?

I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
So, building asteroids and syncing with latest sources and also trying to fix bluetooth is my main goal here.
First test build is complete! Link: [urlhttp://www.mediafire.com/?0c0xusva0z5e0[/url]
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/asteroid-image-tetra.ext4 /sdcard/linux/rootfs.ext4 (pushes the file to the virtual sdcard)
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/zImage-dtb-tetra.fastboot
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).

RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?

amunarjoh said:
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?
Click to expand...
Click to collapse
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version

RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
I am willing to be a beta tester

Alright, stay tuned. Building rom right now, also getting instructions for how to flash it (I don't think it is a simple twrp flash, not sure, we need some tester to confirm that).

RAZERZDAHACKER said:
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version
Click to expand...
Click to collapse
That sounds interesting. Looking forward to further development

Build finished after a couple of hours. Since I am new to this whole android wear thing, I am a bit confused as to which files to flash, but I assume it is the one that is the largest and has the correct file format, right? So here is where the beta tester thingy comes into place. I am still experimenting on flashing the rom (the flashing method can be a bit confusing for new people) so I am planning on coding a toolkit that does all of that for ya, but the main thing is that I use linux and I don't really have a windows machine available to test this and quickly be able to change some things in the code (or either the rom files and then pack em up) so if someone is willing to perhaps skype or something similar where they can test such things that would be amazing, since I don't believe that a lot of people are running linux and want to flash this particular rom for this particular device etc.
Enough ranting! Here comes the rom link! http://www.mediafire.com/?0c0xusva0z5e0
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext4
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/file.fastboot.
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).

Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.

niai_mack said:
Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.
Click to expand...
Click to collapse
Thanks for trying, and you followed the instructions here I assume. I'll try to compile a new one today (I got some interesting warnings when compiling)

Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.

You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.

niai_mack said:
Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.
Click to expand...
Click to collapse
Can you perhaps try "adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext2" ? Thanks.

I can test as well

d_crossfader said:
I can test as well
Click to expand...
Click to collapse
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.

drakonizer said:
You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.
Click to expand...
Click to collapse
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.

RAZERZDAHACKER said:
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.
Click to expand...
Click to collapse
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.

drakonizer said:
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.
Click to expand...
Click to collapse
I can always try :/

RAZERZDAHACKER said:
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.
Click to expand...
Click to collapse
I can do the steps on the first page, not sure about replacing the virtual sd though

d_crossfader said:
I can do the steps on the first page, not sure about replacing the virtual sd though
Click to expand...
Click to collapse
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2

RAZERZDAHACKER said:
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2
Click to expand...
Click to collapse
cool, will try in a few

Question Reverting from GrapheneOS

I tried GrapheneOS and it's ok but too many compromises I have to make with several apps I'm using not working and small issues here and there.
Has anybody ever used Android Flash Tool to revert back from GrapheneOS to stock? If so, any issues?

Yeah plenty of times, no issues. Download firmware, extract it then flash-all in CMD

Thanks. No need to download FW or for CMD there, flashing is web based: https://flash.android.com/
Worked flawless.

sabai27 said:
Thanks. No need to download FW or for CMD there, flashing is web based: https://flash.android.com/
Worked flawless.
Click to expand...
Click to collapse
Can't wait to see more devs implement this system. My laptop is borked so it's really cool seeing such a simple alternative emerge

I've been thinking of using GrapheneOS for a bit. What was some stuff that didn't work for you?

Opensystem said:
Can't wait to see more devs implement this system. My laptop is borked so it's really cool seeing such a simple alternative emerge
Click to expand...
Click to collapse
I would definitely love to see this with other manufacturers. I got a Windows ARM laptop that has become unresponsive in BIOS, meaning I can't tell the system to install a new Windows version via the Boot menu. Such a tool would save that device. It should be mandatory to offer decent web flashing tools.

asj0422 said:
I've been thinking of using GrapheneOS for a bit. What was some stuff that didn't work for you?
Click to expand...
Click to collapse
Most things work with Sandboxed Google Play. But a few things don't like Android Auto, Google Pay and Chromecast. But other than that, I haven't had anything not work. They are close to getting Android Auto to work if I remember correctly - and Google Games ( I don't use either but looks like release is imminent). Check the other GrapheneOS threads on here or you can message me if you have any specific questions.
One thing I recommend though, is to leave "oem unlocking" enabled on the device after locking your bootloader. that way if something goes wrong, you can flash factory image. You don't want to brick your new phone. (I always leave my bootloader completely unlocked but that's a personal preference and I know the risks).

In other words, only a bunch of proprietary closed source gooble spyware crap doesn't work. The best thing about going to graphene or other security minded distributions of AOSP, is specifically *to* eradicate all of that.
It can be difficult initially, to clear yourself of all the gooble spyware, but its worth it and you don't even notice it after you get used to it. You're just much more safe and secure.