Related
Android 3.x Honeycomb for the Samsung Galaxy Tab
Download Rom: CDMA - GSM | Source Repository | Development Log | Donate
(New development thread here.)
The Alpha 2 Series Archive
Alpha 2.5 Download & Installation:
GSM:
Download the installation guide for specific instructions here.
Download the rom here.
CDMA:
Download and instructions page here.
User submitted tips, tricks, mods, apps and notes for 2.5:
(if you wish to add to this list, PM your additions to me)
jjhiza's amazing app post: http://forum.xda-developers.com/showthread.php?t=1114916
Ssserpentine: “Tired of that red border? 1) Open up Dev Tools 2) Go to Development Settings 3) StrictMode Visual Indicator - turn it off 4) back out of app and now open it again. 5) If this doesn't get rid of MOST of the red borders, REBOOT and open app again.”
Ssserpentine: “WANT IMPROVED UI, LESS RED BORDERS, LESS FC'S AND SCROLLING AND SOFT KEYS THAT PLAY NICER? Try adw launcher. for some reason just having it installed helps just as much as using it.”
mattman83: "to mount UMS if you have no external SD then use the below line. Same changes as above... echo /dev/block/mmcblk0p1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file"
corodius: "if you have an external sd, by extending the commands to: su mount -t vfat /dev/block/mmcblk0p1 /mnt/sdcard/ mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/external_sd/ This will mount the cards the way they are originally mounted in the samsung/overcome roms."
anfalas: "get Gallery3D to play nice by going into settings, applications then 'Clear Data' - works great, can change wallpaper etc. Only downside is it has to be done each reboot....."
chris49424: (List of suggested apps: Picsaypro.apk electrumdrum.apk drawingpad.apk Picasatoolpro.apk jefitpro.apk flickfolio.apk flickfolio upload.apk pulse.apk bedside.apk newsroom.apk makeyourownclock.apk “quickofficepro.apk must have if in college or for personal business i love this app” screenshot ER.apk slideit keyboard.apk smugfolio.apk tv showsstream.apk tvshowfav.apk “google body.apk awesome app must download everyone it kick ass” beautifulwidgets.apk “ADW launcher ex only say ex because never tried free version, but this is a must have you don't have to use the adw launcher you can still use HC launcher and will get same results.” AutoKiller Memory Optimizer Donate v5.1 pen supremacy.apk)
iamodogg: "one way to load keyboards On the language/keyboard settings page, turn physical keyboard to "no" or "off" or something like that. Now when on a text field, you should see a small keyboard tray in bottom right corner.."
oldmacnut: "LCD DENSITY ISSUES finally got LCD Density to change, however....I noticed it screws with the Wifi when it reboots to apply changes, then a hard reset is required. Only thing that works and doesnt mess with the Wifi is changing the Build.Prop."
TheDub: "OPTIMAL LCD DENSITY Playing with build.prop, Density 160, the maximum tablet interface value, is much easier on the eyes."
ztag100: "If you download barcontrol from the market, you can set it so that a notification links to the rotation app, thus when the notification is clicked it will change the orientation."
Credits:
There isn't enough room here to thank everyone individually, but here is a list
of some of those who have directly affected the development of this project:
* oldmacnut – is a master craftsman and all-around stand-up guy. Always on the ball with testing , throwing out fresh ideas, file hosting and helping new friends out of tough spots, I do believe that there is nothing that this man can’t do. * ssserpentine – The GSM boss. Always active and lively in the forums, (even if he is a bit off-topic,) Sserp adds fun and a touch of insanity to balance everything out. I do believe he will stay attached to this project in the future, (in one form or another,) so get used to this fleshy smell-bag as he marches through this project like giant radioactive rubber pants. * alexgogan – I owe this man a debt of gratitude, (though I cannot disclose what for just yet,) but you will likely see his name attached to the credits in all future releases of this project. * Mattman83 - for never failing to help out other users. * jjhiza – As a rom dev, this is the exact sort of guy you want lurking about in your thread. He shares ideas, contributes, and generally elevates the level of conversation (when he’s not in a flame war, lol). Always a pleasure. * corodius - for helping folks keep thier HC tabs running smoothly. * Sҡȳᴪʌɩҡͼṟ - wrote a spectacular guide for installing the GSM build, and deserves thanks for a job well done. * betolley – He is working on a similar project at another site and many of the ideas we exchanged in PMs helped me to think my way through a lot of technical issues. * chriskader – did some very nice video reviews of both the a2 and a2.5 releases on YouTube, making him the unofficial project journalist. Thanks a lot! * snprkllr76 – put his GSM tab in harm’s way for the greater good. Without it, the GSM release might have never happened. Big thanks to you! (And let me know if you need this tab back, I’ve had it forever!) * fattiemcdoogles – When my CDMA tab was crushed to death under the mighty weight of Odin, this guy stepped in and saved the day by helping me to obtain a replacement. Much appreciated! * Herbiced – provided the initial file hosting for this project, saving us all from the dreaded queues at the “free” file-hosting sites. Gracias! * And there are many others, these are just a few I wanted to shout out to.
A list of a few of those that indirectly contributed to this project through their
contributions to the general independent Android development community:
* Boushh –whose work on the schi800 kernel was used as the basis for my CDMA kernels. * deeper-blue –his work on the Nook color demonstrated the possibility of porting HC and inspired this project (and many others, no doubt.) * alterbridge86 – whose work on the p1000 kernel was used as the basis for my GSM kernels. * supercurio – for providing easy access to his assortment of Voodoo goodies. * Technomancer - whose work on the p1000 kernel was used in my early GSM builds.
And, of course, a huge thanks to XDA for allowing me to host this project here,
and to the XDA mods who help keep the place running smoothly.
Lastly, I want to thank every individual who sent a kind word in a PM or in the thread...
Reading your words of encouragement at 4 am when I was out of ideas, exhausted and ready to give up was sometimes the only thing that kept me going.
Thanks for all of your support.
(If you feel that there is someone who belongs on this list but isn’t please let me know.)
The Future:
I am going underground for a while. I tend to work best uninterrupted behind closed doors.
The next release will be full of surprises and many new features. It is my hope that this project
will no longer need the tag "Alpha" when I am ready to release it.
Time will tell.
Thank you for being patient while I work.
Downloading...
Sent from my SCH-I800 using XDA Premium App
Downloading =)
:'(
Waiting for GSM version.....great job! Post up results people.
Sent from my GT-P1000 using Tapatalk
Downloading now Will report back soon
well when it boots up there is a bunch of fc. laggy, but it's great the fact this has honeycomb !! Awesome work..
keeps locking up
no home button on bottom I'm sure there is more ...
Post YouTube videos please...I want to see if its worth attempting
Sent from my SCH-I800 using XDA App
I just flashed the rom stuck at samsung screen = ( .. Have a sprint tab running Boush's kernel V4.. any suggestions?
Metalsteel said:
I just flashed the rom stuck at samsung screen = ( .. Have a sprint tab running Boush's kernel V4.. any suggestions?
Click to expand...
Click to collapse
try using adb to get into recovery and re-flash
up and running - sprint with Boushh's kernel
is anyone able to get data on Verizon or even wifi working. ?
Herbiced said:
try using adb to get into recovery and re-flash
Click to expand...
Click to collapse
I can get into recovery fine, i reflashed couple times, couldnt boot up the rom...
Metalsteel said:
I can get into recovery fine, i reflashed couple times, couldnt boot up the rom...
Click to expand...
Click to collapse
i know it took a few mins too boot it into HC. It hung on Samsung for awhile for me. i would Suggest installing the K-lean rom and re-flash from there that worked for me.
samsung stuck aswell all good probably kernal issue gonna switch kernals
after changin still same used boush kernal no luck
cmoreno911 said:
up and running - sprint with Boushh's kernel
Click to expand...
Click to collapse
What process did you use exactly to get yours to boot? I'm not at all unfamiliar with the recovery menu/ workings, and I've been messing with roms, themes, and kernals ever since i had a hero when it first came out. But i just cant for the life of me get this thing to boot. I have same setup as you, and tried wiping all and re-flashing a couple of times, tried a fresh download. Nothing works. Furthest I got was about a 10 minute hang on the samsung splash screen. Then I just manually rebooted. Tried a dalvik wipe then boot again and then I was boot-looping lol. I've never failed at getting something to work in the past and I certainly won't let this glorious day of days be my first! Haha.
Any help would be appreciated. Thanks
TylerMF said:
What process did you use exactly to get yours to boot? I'm not at all unfamiliar with the recovery menu/ workings, and I've been messing with roms, themes, and kernals ever since i had a hero when it first came out. But i just cant for the life of me get this thing to boot. I have same setup as you, and tried wiping all and re-flashing a couple of times, tried a fresh download. Nothing works. Furthest I got was about a 10 minute hang on the samsung splash screen. Then I just manually rebooted. Tried a dalvik wipe then boot again and them I was boot-looping lol. I've never haulers at getting something to work in the past and I certainly won't let this glorious day of days be my first! Haha.
Click to expand...
Click to collapse
All I did was CWM flash via zip, hung on the samsung logo for a bit then started up
cmoreno911 said:
All I did was CWM flash via zip, hung on the samsung logo for a bit then started up
Click to expand...
Click to collapse
are you getting data or working wifi? does it keep locking up like windows 2000 ?
might also be an ext4 partition over looked peronaly unsure how to convert to ext4 do have voodo cwm
Herbiced said:
are you getting data or working wifi? does it keep locking up like windows 2000 ?
Click to expand...
Click to collapse
no data or wifi, when it locks up I hit the search button and it unlocks. Home and settings buttons do not work but back button does
cmoreno911 said:
All I did was CWM flash via zip, hung on the samsung logo for a bit then started up
Click to expand...
Click to collapse
Maybe I'll try that then (via regular CWM). I was trying using boushh's Voodoo CWM. Thanks!
Hello all...yes, I am a noob! I recently discovered the joys of rooting my Evo4g...talk about breating new life into outdated technology! Anyway I have been flashing roms for about the past month (drives the wife nuts, always tinkering with my EVO!!) and I have learned how great theming can be - I love the look of ICS and JB but I prefer to not sacrifice the built in features (4G, FFC...etc) that have not been developed for the newer systems. I finally settled on DroidGTR-Turbo (wonderful rom for GB, btw!) and got all my apps reinstalled and convinced myself that the time had come to finally just enjoy my EVO instead of playing with it when...(GASP!)...Microsoft released XBox SmartGlass for Android!!! I had been waiting with eager anticipation for weeks since I heard about it so I went to download it and (GASP! again) "For Android 4.0 or higher"!!! I googled for ways to get it to work, wiped phone and installed on a ICS rom to get the apk reinstalled GB and even found a hacked apk file but I got a parsing error when I tried to install both. So now I am running MazWoz-EVO JB rom (LOVELOVELOVE it btw! Great Job) and as an added surprise I now have shutdown animation, which I never considered before. Here is my issue (after that long winded yet hopefully entertaining introduction to meself!) - and it is in no means a "deal breaker" issue - the shutdown animation uses the bootanimation.zip and I would like to know what file to edit to use a different zip for shutdown than for startup - if that is even possible at this stage in developement. Also, it seems after about two weeks of googling and researching that bootsounds in ICS and JB are not possible at this point. Is this indeed the case or did I miss something somewhere? And of course what would make both of those (very minor) issues completely null and void to me - has anyone found a way to get SmartGlass to install and run on GB?
Thanks for your time!!
Not sure where it is on Rom your running. But using WinZip, or 7-Zip you can check to see if it's in Data - Local. It will be named downanimation.zip .
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: kernel, device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_kernel_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
10/17/13:
http://forum.xda-developers.com/showpost.php?p=46554268&postcount=271
10/12/13: alpha
http://forum.xda-developers.com/showpost.php?p=46407049&postcount=138
10/3/13: Super alpha
http://forum.xda-developers.com/showpost.php?p=46147336&postcount=74
I would love to help, but I admit I don't know much about Android development. I've got an AT&T G2 and I know C# and a bit of C++, so I'm sure I can figure out C. I think it's awesome that you're working on CM, if I can help out somehow I'd love to!
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
bose301s said:
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
Click to expand...
Click to collapse
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
fonix232 said:
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
Click to expand...
Click to collapse
Ok, that is what I was thinking but I have never done any dev work or anything so I figured I would ask.
I cant help but I sure want to thank you folks for trying to get this up and running. This phone is an absolute BEAST! Coming from the gnex I'm excited about the G2's potential.
Sent from my VS980 4G using Tapatalk 4
Thanks!
I just wanted to thank you very very much for working on this! I knew this was going to be a well developed phone and I bet before 4 months we will have a good amount of choice as far as roms go. Thanks again!
I've been trying to port beanstalk to the G2 but I need the same information you are trying for. I need device trees to sync with. I can PM you with what info I've came up with So far if you are interested.?
Edit: tress are up! Great work
Sent from my LG-D800 using xda app-developers app
If you lived in my town I'd probably help by cleaning the gutters for you hehe. Thanks for your work!
Sent from my EVO using xda app-developers app
I am definitely willing to help in any way I can.
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
grandmasterlarry said:
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
Click to expand...
Click to collapse
same goes for me, I have the Korean version.
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
mrbig012 said:
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
Click to expand...
Click to collapse
LG UI feature. I'm fairly sure it will be ported to an AOSP/CM10/LGUI hybrid ROM at some point. I believe part of the issue that devs are running into is that a lot of the custom LG software appears to be tied together.
Can you guys keep us updated on your progress, this is a make or break thing for me with this phone, CM is just so much better than any stock ROM that I don't know if I can deal with a phone that has no prospect of official support.
JackpotClavin said:
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
Click to expand...
Click to collapse
Are we going to try getting mobile network and wifi working first? Is adb working?
droid_<3er said:
Are we going to try getting mobile network and wifi working first? Is adb working?
Click to expand...
Click to collapse
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
JackpotClavin said:
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
Click to expand...
Click to collapse
I am NOT a developer, but this could help perhaps?
http://opensource.wolfsonmicro.com/content/wm5110-linux-driver-released
Not sure if it really is open source or only available as binaries, but the WM5110 is the audio SoC in this phone... I am probably not helping.
Additionally, I think the S4 uses this SoC as well. It's a pretty new part but is gaining a lot of momentum.
Edit: My god that WM5110 is a hell of a part... quad-core, 600 MIPS... dayum!
Glad to hear an update, even if it's about issues. Seeing that there are people actively working on this to make it happen makes me much happier and less worried about keeping this phone vs. returning it tomorrow or Friday to see how the Nexus 5 plays out etc.
Have any of you tried talking to Ricardo Cerqueira? He is in fact the primary maintainer for all LG Devices with regards to Cyanogenmod. I am sure he is planning on supporting this device in the near future, I just don't know when. It will probably be when the device is more readily available since it was pretty much just released.
We’ve just announced the release of Remix OS 2.0 ROMs for Nexus 9 and Nexus 10. The Nexus 9 and Nexus 10 ROMs are now available for download here:
Nexus 9 ROM
http://www.jide.com/remixos/devices/nexus9
Nexus 10 ROM
http://www.jide.com/remixos/devices/nexus10
We’ve been conscious of all the interest that Nexus 9 and 10 users have expressed in being able to experience Remix OS 2.0 on your tablets. We definitely heard your comments and are excited to finally have Remix OS 2.0 ready for you to experience.
Thanks!
Hey Jason!
I read about the RemixOS and it looked awesome!
I have a question, will you ever support or port the OS to the galaxy note pro in the future?
Thank you in advance!
Great news!. Installed now on my Nexus 10. Good job and thank you for your effort Remix Team!
Took me forever to get it working...
First boot took 35 mins. I shut down a while ago and attempted to restart, but it's been more than an hour now and my Nexus 9 is not back up. Completely stock RemixOS 2... Wtf?
Thank you so much for this. This has added a new life to my Nexus 10. Please keep releasing updates for Nexus 10.
Great Android distribution for my Nexus 10, fast and good enough to give more life for my tablet.
There are some issues sometimes, such as Firefox will not show the rendered text, it will show a white browser area with text behind a white overlay.
Also, in the Play Store, the device appears as a phone, this is because the ro.product.model and name are changed from the default values for Nexus 10.
Is there a root method for this yet?
I'm impressed with this OS. It makes sense on a bigger tablet like my Nexus 10. There are not very many issues I have come across. It makes me want to get a dedicated mouse and keyboard and use it as more of a laptop. I know Remix OS is still new and developing, but I can only think of a few things that I look forward to seeing.
1. Widgets. I did see a video that 2.0 had widget support. Am I missing it or is it just not in this build yet. https://youtu.be/ledz0FTlzKA
2. Removing apps from the home screen.
3. Persistent notifications. I've always used apps like battery widget reborn and weather apps and Calendar Status Pro that give me notifications that stay in the notification shade. They seem to go away once the app is closed on this OS. Maybe it would cause multitasking issues if it had to keep stuff like that in memory and that's why they don't exist but if it's possible, that would be nice.
4. And on a not so important note, the lock screen could be more useful as far as notifications and all.
Also, questions about updates. I think I read somewhere that Remix OS is updated pretty often. Will the Nexus 9 and 10 get the same updates every other devices get? Will they be OTA and do we need the recovery that came with the download in order to use the OTA (I am using TWRP still)? And will being rooted effect the OTA (I rooted with SuperSU)?
Thanks for this awesome new OS. I love how different it is from normal Android but is still Android.
+1 great first impresión. Great work and the same few things to improve if the remix team is open to suggestions.
Bluetooth issues? nexus 10?
I have no issue connecting either 1 mouse or 1 keyboard, however when i want to sync both a mouse and a keyboard, i cannot locate the second device. For example if i connect my keyboard then my mouse becomes undiscoverable, even though my other devices can see the mouse. If i pair the mouse first then i cant see the keyboard. BTW im using a nexus 10.
Is there a way i can have both be paired at the same time?
I have a bluetooth mouse and when i connect to the tablet the mouse is skippy, laggy and jumpy. whatever you want to call it. Any way to remedy this? is it a bad bluetooth mouse? or can the tablet not handle it?
anyone know how to revert back to stock from remix os? i try to flash image, failed. try to enter recovery also failed. help anyone?
Do I have to revert to stock from Remix OS 1.5 to upgrade to Remix 2.0?
tyyyyyyyyyyyyyyyyyyyyyyyyyy
---------- Post added at 01:10 AM ---------- Previous post was at 01:06 AM ----------
:d:d:d:d:d:d:d:d:d:d:d:d:d
tribalfusionaxe said:
anyone know how to revert back to stock from remix os? i try to flash image, failed. try to enter recovery also failed. help anyone?
Click to expand...
Click to collapse
Did you try simply forcing bootloader mode and flashing with fastboot from a PC with the flash-all script that comes in stock images? I mean, hold power + volume down long enough for the tablet to reboot, then let go the power button but hold the volume down. Then select fastboot and finally, connect the tablet to the computer and follow the normal steps for flashing.
What are the chances for eventual Nexus 7 (2013) support?
Hey there, I'm very new to Remix OS, and I just installed version 2.0 on my Nexus 9 and it works flawlessly. My only question is, when I set a Pattern as a lockscreen password, the lockscreen with the clock disappears only leaving the Pattern dots. Is there a way that I can keep the lockscreen clock while still having a Pattern? Thanks!
I just get a boot loop on my Nexus 9 WiFi (volantis).
Reflashed all the images twice.
Does it matter what version we are coming from? I was on the N Dev preview. I'm currently flashing Marshmallow stock images, then I might try to go to remix from there to see if it makes a difference.
Also the flash instructions say to flash userdata, but there is no userdata.img, the instructions also don't say anything about vendor.img, but I flashed it anyways.
EDIT: It didn't make a difference. It just says GOOGLE, then the Remix OS logo flashes for a second or 2 then its back to GOOGLE and does this infinitely.
EDIT2: Looks like flashing the stock 5.1.1 images, and then flashing the RemixOS images worked.
Remove Remix OS from Nexus 10
So, I installed Remix OS on my Nexus 10. So, Now I want to remove it and install CyanogenMod on it. Using Win7, adb can't see the current device even though it worked fine when it had a stock Android on it? Suggestions?
Cant detect SU Binary
I ran SuperSU (Chainfire) and it cant detect the su binary. is there a workaround for this? can I reroot my nexus 10 using typical methods without flashing the stock firmware?
Will there be a version for the Nexus 9 LTE per chance? I'd love to make the switch...
Hi all,
First post, new member at this site. Thanks for all of your hard efforts and kind sharing of knowledge. I'm a US Navy sailor, and my rooted S5 (GP900) just bit the dust. I'm seeing if I can get this old dog (SGH-T989) going.
So far, I have bombed out on installing any ROM. I find myself without a stock T989UVMC6 file, as many file servers (in 2017) have understandably stopped serving this old image. I have the T-Mobile SGH-T989 (gen 1) phone. Clean IMEI.
Background: This phone was on stock firmware 2.3.x at the beginning of this ROM voyage, and had no service to do an OTA Jelly Bean push. This phone is in immaculate condition, gifted to me by my grandfather two weeks ago, after he finally upgraded. Known to work (just not in my hands).
Tools I have at my disposal (Windoze 7 machine):
Odin 3.10.7
PITmagic 1.3.10
T-Mobile_t989_GSII_ADB_Drivers (Samsung_USB_Driver_for_Mobile_Phones_v1_3_2200_0)
Tools I have at my disposal between my 5 linux machines:
Terminal
XTerm
Terminator
(terminal emulators, which is all Linux really needs )
MicroUSB 5-pin Cables I have tried
Anker Powerline Micro-USB **** I like this one a lot ****
Samsung OEM Micro-USB
Samsung OEM Tab 3 Micro-USB
Generic Micro-USB
ROMS and Zips I have tried pushing through TWRP 3.0.2, TWRP 2.8.4, and TWRP 3.1.0:
1) Validus (specifically Validus-LP-v8.0-2015-06-06-validus_hercules, a 2015 image, Android 5.1 Lollipop) + open_gapps-arm-5.1-stock-20170513
2) CyanogenMod 14.1 (specifically cm-14.1-20161031-UNOFFICIAL-celox, a 2016 image, Android 7.1 Nougat) + open_gapps-arm-7.1-stock-20170513
3) CyanogenMod 13.0 (specifically cm-13.0-20160327-UNOFFICIAL-celox, a 2016 image, Android 6.0 Marshmallow) + open_gapps-arm-6.0-aroma-20170513
4) LineageOS 14.1 (specifically lineage-14.1-20170314-UNOFFICIAL-celox, a 2017 image, Android 7.0 Nougat) + open_gapps-arm-7.1-stock-20170513
5) ParanoidAndroid 5.1 (specifically pa_hercules-5.1-20151011-vp, a 2015 image, Android 5.1 Lollipop + open_gapps-arm-5.1-stock-20170513
I have tried several versions of Odin (3.9.2 on), I have tried several versions of TWRP (2.8.4 on), I have tried flashing both modified and unmodified SGH-T989 PITs via both Odin and PITmagic. So far, I have been unsuccessful in all attempts of getting a stable OS on this thing, I have followed these old posts here at XDA to the 'T', and simply cannot for the life of me figure out why only Validus seems to do "anything" (as in optimize apps at bootup and then freeze at 64/105). Disheartening, but I'm an IT by trade, and a Linux fan by hobby, so I'm used to suffering for my art. I should also mention that I have used DARKSIDE.SUPER.WIPE / DARKSIDE.CACHE.WIPE by thederekjay and really feel this might be a PEBKAC (Problem Exists Between Keyboard And Chair) error.
Speaking of errors... what am I getting? Okay, so to answer on that: mostly it's Error 7, sometimes it's no error at all (as in a bootup screen that timelessly animates for a whole night, etc), other times it's an Encryption Unsuccessful. Depends on the ROM, depends on the GAPPS, and the stars and the moon on what error I get. -_-
However, I've been at this now for 2 weeks, off-and-on, and am now turning to you great minds to help this tired fellow out. I promise I will not be snarky (as other posters have been), and I greatly appreciate your pearls of wisdom in getting this SGSII up and running again.
:good:
-Gouda
[SOLVED] - Root issue
I feel so embarrassed. For anyone facing a similar issue, please triple check (read: distrust your instincts) and ensure the phone is unequivocally, unquestionably, absolutely rooted. SuperUser must be correctly installed via TWRP or CWM. Get past that, and your ROM + GAPPS procedure should allow you to access your OS/UI and get busy. Facepalming over this.
Gouda, out.