Hello!
Usually I mainly consult this forum to get unofficial builds of LineageOS or look for support when occasionly something goes wrong. Some time ago I wondered, why it has to be so annoying to install LineageOS (or most of the other custom ROMs). There have been several attempts to create a graphical installer for LineageOS (most famously this one) and some installers for specific ROMs like calyxos. But support for devices is rather limited and hard to extend.
So I decided to give it a try myself and create a new attempt to build a graphical installer for alternative Android ROMs.
Repository: https://github.com/openandroidinstaller-dev/openandroidinstaller
Features:- Graphical installer with instructions.
- onefile executable.
- adb, fastboot, heimdall and some drivers included.
- Works on Linux (mainly tested on Ubuntu 20.04), MacOS (not on ARM, M1, M2) and windows (you might need to install some drivers manually).
- some checks if the selected LineageOS image and recovery works for your device.
- Installation steps are based on config files to add support for new devices.
- written in python
Supported devices:- Currently, the alpha version mainly supports Google, Samsung, Fairphone and Sony devices, but should be fairly easy to extend to other devices.
Alpha version release download:https://github.com/openandroidinstaller-dev/openandroidinstaller/releases
How can you help?All kinds of feedback are useful! Let me know what you think in this thread.
If you have a unused device that supports LineageOS, perhaps you could try out this tool and report your results in this thread! I bought a bunch of different android devices, but more testing on all kinds of devices is needed and very welcome! Also testing the tool on different platforms (windows, macos, etc.) would be super helpful.
Note that:
- It may screw up your device. No automatic restore process is implemented yet, so make sure to have some sort of recovery tool handy.
- When you report back, please include the version of the program you used (as identified in the Downloads section), along with your device.
- Read the repository's README for further details!
- This installer is not associated with official LineageOS.
Getting a new phone this week, will give it a shot
SigmundDroid said:
Getting a new phone this week, will give it a shot
Click to expand...
Click to collapse
Thanks a lot! I'm looking forward to your feedback!
What phone are you getting? I might be able to help you with support
FP3. Was hoping it'll arrive today... alas, didn't come, so probably I can check not before the weekend.
Great! I'll make sure, that there is support for the FairPhone 3 on the weekend, but note, that it hasn't been tested yet, since I don't have a FairPhone 3. So I'm super happy about any feedback I can get
If you have questions, let me know!
Devices that should work out of the box now:
VendorDevice NameCodeNameModelsStatusSamsungGalaxy A3 2017a3y17lteSM-A320FLtestedSamsungGalaxy A5 2016a5xelteSM-A510FtestedSamsungGalaxy S7herolteSM-G930FtestedSamsungGalaxy S9starlteunder developmentGooglePixel 3asargosargotestedSonyXperia ZyugaC6603testedSonyXperia Z3z3under developmentFairphoneFairphone 2FP2under developmentFairphoneFairphone 3FP3under developmentMotorolamoto g7 poweroceanunder development
In general, it should be pretty easy to use the tool for all kinds of Samsung, Pixel, Sony Xperia, Fairphone and Motorola devices. Let me know if you need help with your devices.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OK, it works with FP3! Awesome! Actually, that might become a nice little helper for flashing LOS!
Ran into some problems:
Had to OEM-unlock first. Could be little bit more elaborate (I usually forget to reboot the phone after that and authorize my PC, lol)
First 2 times it hang, only the console told me it looks for https://lineageosroms.com/fp3/ (not official, is it?)
Had to unlock with fastboot flashing unlock
That can be a big problem for beginners if you face it the first time
A little bit more feedback during flashing would be nice, console (and phone) showed more than the installer
Overall very good approach! Well, except for the lack of feedback (errors/progress from console). Is there any logging?
PS: Used it on Debian Bullseye with KDE.
PSPS: Perhaps an overview of the steps would fit in there as well (so one can see past, current and future steps)?
Awesome! Thanks for giving it a try!
Had to OEM-unlock first. Could be little bit more elaborate (I usually forget to reboot the phone after that and authorize my PC, lol)
Click to expand...
Click to collapse
Very good point!
First 2 times it hang, only the console told me it looks for https://lineageosroms.com/fp3/ (not official, is it?)
Click to expand...
Click to collapse
In the next release it will point to the official page. I wasn't aware that this page is not at all related to LOS and not so well perceived in the community as some of the devs pointed out to me. The check is done, to find out if there is an official release of LOS and then recommend the download. There might be a better way to guide users to find an appropriate image for their device, but that was simple.
Had to unlock with fastboot flashing unlock
That can be a big problem for beginners if you face it the first time
Click to expand...
Click to collapse
That was my bad... I didn't read the "unlock bootloader" instructions of the FP-support page carefully enough and stopped after part 1. This should be easy to address by updating the config. It will be fixed in the next release.
A little bit more feedback during flashing would be nice, console (and phone) showed more than the installer
Click to expand...
Click to collapse
That's very true! I'm trying to figure out, what kind of feedback is appropriate to keep people informed, but not scare them. A progress bar for flashing is in the making. Optimally, the installer can also show images of what should be going on on the phone. But that will mostly rely on community contributions for phones I don't own.
Thanks a lot for the detailed feedback! I will try to address most of them in the next release, especially more information and feedback for the user.
PS: Are you using the FP3 as your daily driver now, or would you be open to test the installer again in a few weeks or so?
PPS: I'm thinking about moving away from LOS recovery all together and only support TWRP since it allows for much more automation. What are your thought on that?
__sterby__ said:
official release of LOS
Click to expand...
Click to collapse
Would that link do it?
https://download.lineageos.org/FP3
__sterby__ said:
That was my bad... I didn't read the "unlock bootloader" instructions of the FP-support page carefully enough
Click to expand...
Click to collapse
Hmm, I vaguely remember the exact same thing happened to me as well at my first manual flashing. Don't other phones do that as well nowadays? I could swear the S5 i flashed 2 weeks ago did it also...
__sterby__ said:
what kind of feedback is appropriate to keep people informed, but not scare them
Click to expand...
Click to collapse
Hmm, I would certainly appreciate the "real" output as provided in console. Without it I wouldn't have really known what your installer is trying to do.
Putting some pictures wouldn't hurt but I really think that a "map" of steps is useful, too. Besides, one can see the whole progress at once (so far it's a somewhat nebulous process in my mind... and I always! tend to forget something).
__sterby__ said:
using the FP3 as your daily driver now
Click to expand...
Click to collapse
Nah, not yet... that's actually why I got this second phone, so can test stuff without killing off my daily driver (after some horrible experiences I am insisting to try a new phone/ROM for some weeks before I switch).
So, yes, keep it coming Your idea is awesome (and saves me some time as well).
__sterby__ said:
moving away from LOS recovery all together and only support TWRP
Click to expand...
Click to collapse
Awesome! A recovery without backup (like LOS) seems moot anyway (seems like a must have to me). Was thinking to switch already but wasn't sure about any implications (A/B vs TWRP, didn't fully grasped the A/B stuff yet)...
Uhm, rooting wouldn't be on your agenda, too? That is a thing still causing me trouble (I have to read up on it every single time).
SigmundDroid said:
Would that link do it?
https://download.lineageos.org/FP3
Click to expand...
Click to collapse
Yes And probably also to the relevant TWRP page soon.
SigmundDroid said:
Hmm, I vaguely remember the exact same thing happened to me as well at my first manual flashing. Don't other phones do that as well nowadays? I could swear the S5 i flashed 2 weeks ago did it also...
Click to expand...
Click to collapse
No, other phones also require this step. Since the fairphone 2 doesn't require it (as far as I know the bootloader is already unlocked), I assumed that could be similar for the Fairphone 3.
SigmundDroid said:
Hmm, I would certainly appreciate the "real" output as provided in console. Without it I wouldn't have really known what your installer is trying to do.
Click to expand...
Click to collapse
Thanks for the suggestion, I'm working on an "advanced output mode" that lets you see all the terminal input and output.
SigmundDroid said:
Putting some pictures wouldn't hurt but I really think that a "map" of steps is useful, too. Besides, one can see the whole progress at once (so far it's a somewhat nebulous process in my mind... and I always! tend to forget something).
Click to expand...
Click to collapse
yeah, I'm thinking about how to integrate this in a useful way. A bit more overview would be nice.
SigmundDroid said:
Nah, not yet... that's actually why I got this second phone, so can test stuff without killing off my daily driver (after some horrible experiences I am insisting to try a new phone/ROM for some weeks before I switch).
So, yes, keep it coming Your idea is awesome (and saves me some time as well).
Click to expand...
Click to collapse
Perfect! Thanks a lot, I'm already working on a new release and hopefully there will be much more automation and more user information (and a fully working config for the fairphone 3). I keep you updated!
SigmundDroid said:
Awesome! A recovery without backup (like LOS) seems moot anyway (seems like a must have to me). Was thinking to switch already but wasn't sure about any implications (A/B vs TWRP, didn't fully grasped the A/B stuff yet)...
Click to expand...
Click to collapse
So far, it works kind of okay with TWRP I would say, but I'm having weird issues on the Google Pixel with it and wasn't able to find anyone who might know anything about it. Using twrp commands in the adb shell seems to be not so common...
Either way, I would try to get away with just booting into TWRP, wiping and flashing from there. This is an approach that seems to work fine with A/B-partitioned phones as far as I can tell.
SigmundDroid said:
Uhm, rooting wouldn't be on your agenda, too? That is a thing still causing me trouble (I have to read up on it every single time).
Click to expand...
Click to collapse
It's not on the short-term agenda. But definitely something I'm thinking about. I should probably put a proper roadmap on github
Soooo, now there is a new alpha Release
Release Alpha release v.0.2.1 · openandroidinstaller-dev/openandroidinstaller
This is an alpha release of the OpenAndroidInstaller. Linux, MacOS and Windows are supported, but the testing is mainly done on under Ubuntu 20.04. Note, that currently there is no support for ARM-...
github.com
This time mainly visual improvements and more automation. This is mainly achieved by switching recovery support completely to TWRP (currently only booted, only flashed on samsung devices).
There is now an option to get advanced output, printing commands run and terminal output in the tool. This is still early stage and needs a fair amount of improvements, but gives some more hints about whats going on.
Logs are written in the same directory you run the tool in.
...and support for quite some new devices!
@SigmundDroid : Now the support for the Fairphoen 3 should be fixed and TWRP should work A/B devices (tested with google pixel 3a). Give it a try, if you want!
I would be grateful about any feedback! Let me know how it works for you!
Just tried the 2nd version:
+ Nice, comes with log now, good!
- failed at fastboot_oem_unlock twice... but actually it was the "fastboot flashing unlock" (not the oem). Not sure about the proper names for these two unlock (one in dev settings and the other one per fastboot). So, I set both correctly and restarted but it kept hanging here (and no way to skip your test).
The TWRP install worked well... just, how do I start it later? It was installed on A and on B is the LOS recovery - is there some easy way to use TWRP? (really don't have a clue as A/B is fairly new to me)
PS: Shall I drop you the log somewhere?
SigmundDroid said:
Just tried the 2nd version:
Click to expand...
Click to collapse
Great! Thanks a lot!
SigmundDroid said:
+ Nice, comes with log now, good!
Click to expand...
Click to collapse
Thanks! Did you also try the "advanced output" feature?
SigmundDroid said:
- failed at fastboot_oem_unlock twice... but actually it was the "fastboot flashing unlock" (not the oem). Not sure about the proper names for these two unlock (one in dev settings and the other one per fastboot). So, I set both correctly and restarted but it kept hanging here (and no way to skip your test).
Click to expand...
Click to collapse
That's a very good catch, I noticed an issue there. I followed this official tutorial from Fairphone: https://support.fairphone.com/hc/en-us/articles/360048646311-Manage-the-bootloader-of-your-FP3-FP3-
And they used `fastboot oem unlock`, which I noticed now doesn't even exist. I fixed it now.
SigmundDroid said:
The TWRP install worked well... just, how do I start it later? It was installed on A and on B is the LOS recovery - is there some easy way to use TWRP? (really don't have a clue as A/B is fairly new to me)
Click to expand...
Click to collapse
Ah, right now, I just boot to TWRP recovery, not flash it for A/B devices, since I was not sure how to best do it for now (without potentially destroying stuff). For Samsung devices it will be flashed.
Do you think this is an issue in general? I might try to add it as a feature for power users, that can also handle the risk a bit better. What do you think?
SigmundDroid said:
PS: Shall I drop you the log somewhere?
Click to expand...
Click to collapse
For now, it's fine and I guess I know whats the issue.
I'm planning another release next week, probably mostly a bugfixing and user-interface release. I will post it here again
Hey there!
Today I released the Version v.0.3.0-alpha of the OpenAndroidInstaller with many improvements and newly supported devices!
The release includes 11 new devices (now 27 officially supported devices):
Motorola moto g7 power (ocean)
Motorola moto g5 (cedric)
Samsung Galaxy Note 9 (crownlte)
Samsung Galaxy Note 10 (d1)
oneplus 6
oneplus 6T
oneplus 7
oneplus 7 Pro
oneplus 7T
oneplus 7T Pro
OnePlus Nord N200
Give it a try, if you want!
I would be grateful about any feedback! Let me know how it works for you!
Clean shot, eh!
No, really, worked like a charm! No hickups, nothing, just awesome! Thanks!
PS: Fun fact... Yes, one hickup: Was trying to use LOS recovery three times in a row until I realized it should be TWRP
SigmundDroid said:
Clean shot, eh!
No, really, worked like a charm! No hickups, nothing, just awesome! Thanks!
PS: Fun fact... Yes, one hickup: Was trying to use LOS recovery three times in a row until I realized it should be TWRP
Click to expand...
Click to collapse
Great! Thanks a lot for testing again!
Looks like the thing is slowly moving to a more stable state. Maybe moving to beta next year
PS: Good point! In the next release I will try to make it clearer. At least you could not use the LOS recovery
__sterby__ said:
will try to make it clearer. At least you could not use the LOS recovery
Click to expand...
Click to collapse
Yeah, perhaps some bold print of the file templates for unteachable people like me Nah, just kidding...
In any case, thanks so far and Merry XMAS
SigmundDroid said:
Yeah, perhaps some bold print of the file templates for unteachable people like me Nah, just kidding...
In any case, thanks so far and Merry XMAS
Click to expand...
Click to collapse
Thanks a lot! Merry Christmas to you as well!
Hey everyone!
I did some work in the last weeks and now the OpenAndroidInstaller is available in alpha version 0.3.1, with improved user experience and newly supported devices.
New features:
new images to guide in the process
steps indicator header
remove step-progressbar and move the header to different column container to keep it attached to the top
pop-up box to explain custom recovery and OS images.
dialog to help finding the android or firmware version
5 New devices (now 32 officially supported devices):
Sony Xperia 10 (kirin)
Sony Xperia 10 Plus (mermaid)
Sony Xperia XA2 (pioneer)
Sony Xperia XZ3 (akatsuki)
Sony Xperia XZ2 (akari)
If you're interested in trying out alternative ROMs on your device, now is the perfect time to give OpenAndroidInstaller a try. Over the holiday season, you might to play with OpenAndroidInstaller on your old or new devices and see what it can do.
Thank you for supporting open source software and giving OpenAndroidInstaller a chance. Happy holidays and happy installing!
PS: There is a brand new, shareable website now! https://openandroidinstaller.org/
Hey you all! I have been quiet for while here, but the work continued!
Now I'm happy to release the first beta release of the OpenAndroidInstaller.
The major new feature is the option to install addons like GApps, MicroG or F-droid with the Installer. Also there are now 52 officially supported devices and more to come!
If you want to try it, I'm happy about all kind of feedback (positive and negative). Have a great day and happy flashing!
Release: https://github.com/openandroidinstaller-dev/openandroidinstaller/releases/tag/v0.4.0-beta
Download: https://openandroidinstaller.org/download.html
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome To The One Stop Xoom Shop!
AKA: Xoom Heaven. Please Enjoy Your Stay.-A thread brought to you exclusively by: StrifeSoldierVII of XDA Forums-
(This thread is best viewed on a web browser rather than the XDA app)
DISCLAIMER: I am not held responsible for any boot loops, bricks, or damages that may occur from improper usage of rooting tools. Please read and make sure that you know what you are doing, and as always... proceed with caution. I do not take any credit for all the hard working people who made all the threads that I have linked to, I have merely gathered all of the links into one giant thread to make it easy for all to find.
There will be no further updates to this thread. I am in the process of selling my Xoom. It is a wonderful device, but since getting the Galaxy Nexus and my powerful all in one PC with a touch screen, I do not use it any longer. Thanks for your understanding. Until then, have a good time y'all!
-StrifeSoldierVII
I am selling my whole bundle of items with my Xoom. If you are interested in buying it you can find my ultimate Xoom bundle here:
http://swappa.com/listing/ECH678/view
The goal - To collect as much information as I can that relates to the Xoom, while providing a one stop shop for all users: rooters and non rooters alike. This thread will not only be for the newcomers, but also for the more advanced users alike! No one else has ever attempted to make something like this, so I have personally decided to take it into my own hands and bring it alive. Please bear with me as this is an ongoing project and will take awhile for me to fully complete.
I will continue editing, updating, and adding as much content as I possibly can to this thread until I feel that it can be called a final product. Please feel free to help me build the list by giving me some suggestions as to what I could add or do. So, link back to this thread, and tell all of your Xoom buddies about this.
If you noticed something is not right, or linked improperly... please let me know and I will fix it ASAP. Thanks!
ROOT USER SECTIONS:
SDK:
What SDK Actually Means
Downloading The SDK
ADB:
What ADB Actually Means
How To Use ADB: All Commands And Options
A Real Guide On Using ADB/Fastboot On Your Xoom By okantomi of XDA
Fastboot:
What Fastboot Actually Means: All Commands And Options
Universal Xoom Root - ANY XOOM ANY UPDATE
This is the brand new rooting method from Team Tiamat. It does not matter what model you have, what country it's from, or what Honeycomb version you're running.
This will root any Xoom you throw at it without a problem!
Universal Xoom Rooting Method By Team Tiamat
ClockworkMod Recovery:
[Recovery] ClockworkMod 3.2.0.0 (R4c)
[Recovery] CWM Rogue Recovery v1.1
More will be added over time.
Recovering Your Xoom:
If you have a softbrick or a bootloop follow these instructions: This is fairly simple to solve. Since you will not be able to boot your Xoom normally you will want to boot into recovery mode. To do this: Turn the Xoom on like normal, wait about 2 seconds after your see the Dual Core logo, then press the volume down key. In the upper left corner it should now say "Android Recovery", then press the volume up key to select it. It should then bring up the recovery menu after a few seconds. If you have a Nandroid backup, I suggest that you go and restore to that point when you made the backup, otherwise you will want to select the wipe data/factory reset option to completely wipe out the entire Xoom so that you can start fresh. Wiping data and losing everything... that is a bit extreme though, which is why you NEVER go without making a Nandroid backup when it comes to flashing a file to your Xoom. It's always a good idea to make a backup before you do anything major to the system, like flashing a new custom ROM.
Stock ROMs: (US Models Only)
3G Xoom only: Honeycomb 3.0 Stock - Builds HRI39 and HRI66
Wifi and 3G Xoom: Honeycomb 3.1 Stock - Build HMJ37
Wifi Xoom only: Honeycomb 3.2 Stock - Build HTJ85B
3G Xoom only: Honeycomb 3.2 Stock - Build HTJ85B
[ROM/UPDATE] Android Honeycomb 3.2.2 - Stock & Rooted
Stock ROMs: (Euro Models Only)
This section may or may not happen. On hold until further notice.
Help needed!
Custom ROMs:
[ROM]Team Tiamat Xoom Rom 2.1 Hammerhead
[ROM] Team Tiamat Xoom Rom 2.2 - Moray
[ROM] Xoom Zone [Derivative of Tiamat Xoom Rom]
More will be added over time.
Stock Kernels: (US Models Only)
This section may or may not happen. On hold until further notice.
Help needed!
Stock Kernels: (Euro Models Only)
This section may or may not happen. On hold until further notice.
Help needed!
Custom Kernels:
[KERNEL][AOSP]Tiamat Xoom 2.1.0 "Tachi"
[KERNEL][AOSP]Tiamat Xoom 2.0.0 "Katana"
[Kernel] Launchpad 1.3.0 Gemini
[Kernel] Rogue 1.3.1 "Arcturus"
More will be added over time.
Custom Themes:
Honeycomb XML Info: For Theme Makers And Developers
[THEME] ☢ BigDX Xoom|Zoom Theme ☢
[Theme]TouchWiz for Tiamat 2.1
[Theme] US Wifi 3.2 Deodexed Honey Bread Port
[THEME - WIP] Stargate
[THEMEs] StockRed & StockGreen & StockGrey
More will be added over time.
Custom Boot Animations:
Bootanimation Installer v3.3
Boot Animation Collection - 14 Total
Xoom Forums: Boot Animations Section
Because there are just too many to list, I have included the Xoom Forums website since they now have a dedicated boot animation section. You will find all types of boot animations there.
Custom Battery Icons:
Ultimate Online Theme Kitchen: UOT - Easily Make Your Own Battery Icons
[MOD] Stock Battery and UA for Tiamat Xoom Rom 2.1
More will be added over time.
Root Apps To Help You Get Started:
Superuser
Superuser Update Fixer
Titanium Backup
ROM Manager
SetCPU for Root Users
AutoKiller Memory Optimizer
AdFree Android
Root Explorer (File Manager)
Bloat Freezer - Root
CacheMate for Root Users Free
Screenshot ER 2
LCD Density Changer
Quick Boot (Reboot)
Autostarts
Battery Calibrator
Sixaxis Controller
SuperDim [root]
adbWireless (Widget version)
MicroSD Mounter
TabletBar Hider (Root)
Virtual Button Bar
Absolute System Root Tools
More will be added over time.
Other Useful Root Information:
1. If you plan on re-locking the bootloader for some reason, please only use the stock image files straight from Motorola. The official image files can be found here. You must have a Motodev account in order to download the image files. Once you have an account, download the appropriate image file for your Xoom model, and then follow the instructions on the Motodev website for the fastboot commands to re-lock your Xoom. Once you are finished, you will be back to factory stock with no root at all. Useful if you are returning the Xoom back to a retailer, or a similar situation.
2. When using ClockworkMod Recovery, please do not update it when ROM Manager tells you there is an update, just leave it alone. Only use the CWM Recovery found in the section above, otherwise you may run into a few issues.
3. When installing a custom Rom, it is usually a good idea to not only make a Nandroid backup, but to also wipe data and caches before installing. Sometimes you can get away without having to do a data wipe, but it is not recommended. Here is what you should always do: First, back up only your apps with their data via Titanium Backup, boot into recovery mode, make a Nandroid backup of your current Rom, wipe the data and caches after that, and then finally you will want to restore your apps and their data via Titanium Backup.
4. When backing up and restoring data... DO NOT EVER back up system apps and system data or restore them! If you are on a 3.1 Rom and are updating to a 3.2 Rom, it is not a good idea to restore your system apps and system data from the previous 3.1 Rom. Doing so may cause some very strange issues, and possibly a bootloop in some cases. You only want to backup and restore your apps with their data, please remember that.
5. Make life easier: If you happen to have the Pro version of Titanium Backup, then you will like this one if you already don't know about it. Within the app you will want to bring up the menu, hit market tools, then hit market auto updates, select all, then save auto updates configuration. Thus, from here on out: Most/all apps in your market installed list will do all of the updating for you. Much easier than selecting auto update one by one for each app. And this literally takes a second to do.
NON ROOT USER SECTIONS:
Non Root Apps To Help You Get Started:
Adobe Flash Player 10.3
Adobe Reader
Adobe AIR
Equalizer
Amazon Appstore
Kindle for Android
Amazon.com Mobile App
Barcode Scanner
Beautiful Widgets
Bluetooth File Transfer
File Manager HD
CircleLauncher
ADWLauncher EX
Dolphin Browser HD
Dolphin for Pad V1.0 Beta
Easy Uninstaller
Google Sky Map
Google Earth
Music Beta By Google
Google Voice
Google Body
Tiny Flashlight + LED
GrooVe IP (For Making Phone Calls)
IMDb Movies & TV
MP3 Ringtone Maker
News360 For Tablets
Pandora Internet Radio
TuneIn Radio
PicSay Pro
PowerAMP Music Player
RealCalc Scientific Calculator
Smart Keyboard PRO
Thumb Keyboard (Phone/Tablet)
SoundHound Music Identifier
DeskSMS
SyncSMS
NVIDIA Tegra Zone
WeatherBug For Honeycomb
Writepad Stylus
Power Widget
MultiPicture Live Wallpaper (For Setting High Res Wallpapers)
Screen Filter
Night Clock
Musical Pro w/ Piano
NOOK for Android By B&N
Official eBay Android App
Quick Settings
MyBackup
XDA-Developers (Of course!)
Autorun Manager
Netflix
Wizz Bar
NFL ‘11 for Android Tablets
More will be added over time.
A Special Thanks Goes To:
All the hard working developers, as well as all the hard working people that put all of these individual threads together! Without you guys we would not get anywhere! You all are truly awesome!
Please Visit My Other Personal Threads:
Music Beta by Google: A Must Read For All Root Users!
Adding Spice To Your Xoom's Life: Skin It!
[TIP] How To Enhance Screen Quality For Xoom
[TIP] How To Get A More Stable Xoom Startup From Lockscreen
More will be added over time.
Don't be afraid to leave any comments or questions that you might have, and please don't forget to give me some kind of thanks if you found this thread was useful to you. I'm working very hard to gather and to put together all of the content by myself, so don't forget to spread the word about this thread so that more people can enjoy it.
If you appreciate what I'm doing, please consider making a donation to me. I'm a college student and all that with all of the typical expenses. I do this on my own free time when I can. Any donations would be very much appreciated. If you would like to donate, click the "Donate to me" link above my avatar picture. Thanks!
Thanks man the Xoom thread needed something like this...
This is terrific...it's the beginning of that wiki we've discussed. At the least, this should be made into a sticky.
It would be nicer if you update few more links about how to fix problem like boot lop, softbrick, motorola factory cable, back-to- stock....
okantomi said:
This is terrific...it's the beginning of that wiki we've discussed. At the least, this should be made into a sticky.
Click to expand...
Click to collapse
I think it should be as well. I might need some help with this though.
tritran18518 said:
It would be nicer if you update few more links about how to fix problem like boot lop, softbrick, motorola factory cable, back-to- stock....
Click to expand...
Click to collapse
Great idea! I was going to add that in soon, but it took me awhile to put this together and collect all the proper links. I'll get right on that.
I'm getting ready to root my Xoom, but have a question more a concern of confusion. I updated my wifi only Xoom to 3.2 when it became available manually here and the build is HMJ85B and not MZ604 as stated for my model here. I've had no issues or problems whatsoever from this, but I'm confused on how and why it took and no problems have arose whatsoever. I'm accustomed to jailbreaking idevices and I've even rooted and unlocked a few friends android phones. So in knowing what little I do know, my question and or concern is if I root my Xoom with this build currently on it, will there be a greater margin for failure or maybe bricking and should I try to manually push build MZ604 onto it before hand? Thanks to any and all input and or advice in this matter. Once again I've experienced no issue whatsoever since updating and really it improved my Xoom experience! As I know I'm a NOOB at rooting though and I'm looking for the more experienced input and direction.
Sent from my Xoom using XDA Premium App
Great, very useful thread....this should definitely be stickyed.
Sent from my GT-I9000 using XDA Premium App
rmax67 said:
I'm getting ready to root my Xoom, but have a question more a concern of confusion. I updated my wifi only Xoom to 3.2 when it became available manually here and the build is HMJ85B and not MZ604 as stated for my model here. I've had no issues or problems whatsoever from this, but I'm confused on how and why it took and no problems have arose whatsoever. I'm accustomed to jailbreaking idevices and I've even rooted and unlocked a few friends android phones. So in knowing what little I do know, my question and or concern is if I root my Xoom with this build currently on it, will there be a greater margin for failure or maybe bricking and should I try to manually push build MZ604 onto it before hand? Thanks to any and all input and or advice in this matter. Once again I've experienced no issue whatsoever since updating and really it improved my Xoom experience! As I know I'm a NOOB at rooting though and I'm looking for the more experienced input and direction.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I hope I didn't make a mistake with the build number for the 3.2 Wifi model... there's so many builds, and areas of the world. I'm trying to cover the US models... I may have matched it with the wrong build, as I have always had the 3G Xoom... I'm not too familiar with the Wifi builds. I'll double check these.
EDIT: Thanks! I did have the wrong build number for the stock 3.2 Wifi Rom. All fixed. I know I'm really tired, I mixed it up somehow.. lol. You'll be a-ok. I had the wrong build number but the link is correct.
cause it is all-in-one thread, a warning section might be usefully such as: only relock bootloader on xoom wifi version by using stock 3.0.1 image provided by Motorola...
P/s:I would like you to add links about install sdk/fastboot and how to use adb/fastboot command .
tritran18518 said:
cause it is all-in-one thread, a warning section might be usefully such as: only relock bootloader on xoom wifi version by using stock 3.0.1 image provided by Motorola...
P/s:I would like you to add links about install sdk/fastboot and how to use adb/fastboot command .
Click to expand...
Click to collapse
That's good! These are the ideas I need to make this a true all-in-one list. Thanks again! I will add these in as soon as I can. For now I need some sleep.
I need some help, XDA community! I need help putting together the stock kernels section. If you guys can help me collect the stock kernels from Honeycomb 3.0, 3.1, and 3.2, that would be great... for both the Wifi and 3G Xoom models. I would appreciate it!
The stock kernels section will be delayed for a bit until I can get a hold of the necessary files.
Am I right in thinking this is just for US Xoom's
If so a note saying that might be useful to stop non US rooting with wrong files.
Big_Ted said:
Am I right in thinking this is just for US Xoom's
If so a note saying that might be useful to stop non US rooting with wrong files.
Click to expand...
Click to collapse
Yes, this thread is currently focused on the US Xoom models only. I will add a note about this right now. Thanks!
I might get into adding the other Xoom models to my list in the near future when my thread is more complete. Until then, I apologize for that.
If someone were to help me with the other models outside of the US, I could finish this much faster. Just the US models alone is a lot of work.
EDIT: Added US only model notes to thread. Thank you! I should have added that in right away.
diablo2224 said:
I need some help, XDA community! I need help putting together the stock kernels section. If you guys can help me collect the stock kernels from Honeycomb 3.0, 3.1, and 3.2, that would be great... for both the Wifi and 3G Xoom models. I would appreciate it!
You can PM me, or post in my thread here. I'm currently still working on all sections, but the stock kernels section will be delayed for a bit until I can get a hold of them.
And more suggestions I can add into this list would be great!
Click to expand...
Click to collapse
How would you prefer submissions? You are doing a tremendous job. I know you need help.
okantomi said:
How would you prefer submissions? You are doing a tremendous job. I know you need help.
Click to expand...
Click to collapse
Thanks for the compliment!
I would actually prefer people to PM me either working links to a direct download or working links to a thread that has the files I need. I'll put the people who helped me in a special thanks section of the thread to give credit to them.
Just want to double-check before I plow away at this...as to getting completely back to stock for a return or warranty work, we do not need to create images of stock. just use the images in the first post? This will put back the stock 3e recovery and everything?
Thanks
Barsky said:
Just want to double-check before I plow away at this...as to getting completely back to stock for a return or warranty work, we do not need to create images of stock. just use the images in the first post? This will put back the stock 3e recovery and everything?
Thanks
Click to expand...
Click to collapse
It's recommended that you flash the stock images found at the Motodev website and then re-lock the bootloader for a return or warranty work. Especially since being rooted voids the warranty. That's why it's important to use the official stock images from Motodev before doing anything like this. It's said that they will never know you had been rooted in the first place by using this method, thus the warranty was never voided. Hope this was the answer you were looking for.
diablo2224 said:
. That's why it's important to use the official stock images from Motodev before doing anything like this.
Click to expand...
Click to collapse
Wait, diablo from Samsung Captivate roms? dude, you always rock
"before"? wouldn't images be used after to return it to factory condition? again, just going ultra-safe mode here
Thanks, as always!
Barsky said:
Wait, diablo from Samsung Captivate roms? dude, you always rock
"before"? wouldn't images be used after to return it to factory condition? again, just going ultra-safe mode here
Thanks, as always!
Click to expand...
Click to collapse
The stock images provided by Motodev will get you back to a completely stock factory Rom, but your bootloader will still be unlocked, which the retailers will be able to tell. You''ll want to flash the image file to get back to a factory stock Rom, and then run the Fastboot commands on their website to lock the bootloader back up. Thus the end result is: a factory stock Rom, a locked bootloader, and no trace of root. It's just as you bought it from the retailer out of the box.
I'm not sure if this is what you are looking for, but it's good info nonetheless.
diablo2224 said:
The stock images provided by Motodev will get you back to a completely stock factory Rom, but your bootloader will still be unlocked, which the retailers will be able to tell. You''ll want to flash the image file to get back to a factory stock Rom, and then run the Fastboot commands on their website to lock the bootloader back up. Thus the end result is: a factory stock Rom, a locked bootloader, and no trace of root. It's just as you bought it from the retailer out of the box.
I'm not sure if this is what you are looking for, but it's good info nonetheless.
Click to expand...
Click to collapse
Got it. Thanks much
Hey guys just wanted to share this with you. I am working with Team Win to get a touch recovery on the A500. So far is still inop, but progress is bring made. We are gonna give another go tomorrow so wish us luck. Will keep you all posted.
Updates
1-5-12: So we are finding the using the tablet interface makes the recovery too large for our recovery partition. Team Win is probably going to have to build the recovery without an interface and then I will create a flashable zip that will flash the recovery as well as place a ui.zip on the external sdcard under twrp/theme(we can then just replace that ui.zip for different themes that come out, got a cool ICS one in mind already). The battery precentage is working but we are still working on the touch screen. New test build coming today and will have active logging enabled so that we can see more of what is happening, if touch is being recongnized but TWRP 2.0 is just not reacting to it. It's coming along though.
1-6-12: SO we got TWRP 2.0 up and running for the most part. Touch screen works and most all functions work. Get backup failures and is not sized properly but we are really, really close. Did install a rom and booted just fine. Release will be real soon, possible monday. Still have to get the resolution figured out as well, but what we have so far is very usable.
2-17.. So work on this has slowed way down due to dev on teamwin side has other projects that he is working on that is more important to him(which there is no problem with that, would just like to get this project completely going). But TWRP 2.0 has gone completely opensource. So just wondering if we can tackle this and get it up and running. We are on #twrp on freenode irc usually everyday M-F around 11am-1pm Mountain Time. If you are able and willing to help, please come and give us some fresh ideas.
3-8. Everything is working and is ready for release very soon. Some final testing and will be release. Data/media fixed and flexrom fixed. PLEASE HOLD!!
3-13. New features being added. We will have the ability to toggle back and forth between internal and external for backup location. Doing some code clean up and making sure all features are working properly. Have used it to install many roms/flashes and have yet to have any issues. It's coming along nicely. Huge thanks to Dees_Troy on TeamWin for his work on this. You da man!
I run TWRP 2.0 on my Evo 3D. Would love to see it on my A500. So much better then all the button presses to navigate through the recovery menu.
I would love to see TWRP 2.0 on the A500. I have it on my Sensation and think it is some of the absolute best development to come out of the Android development community recently. Best of luck guys.
Muahahaha. Can't wait!!!
Sent from my HTC EVO 3D using Tapatalk
Updated OP with some status update.
I used a steam recovry on my captivate that was full touch and really liked it. I dont remember any sort of oddities to get it running. Maybe talk to one of them and see how they got theirs set up.
if i can make one request i sed it on my phone and it was awesome. One thing the when selecting ROMS the font is small and often hard to hit the right one
IIRC you need to have the "itsmagic" script run at boot. When I came to the A500 scene it was already figured out so I'm not 100% sure on what it was or what exactly it does but I would recommend looking in to it. I'm sure some more senior A500 developers could help with its purpose.
Sooooooo close!
Updated OP, she is almost ready!
That is looking sweet, I like that 2nd gui alot better than the first one. A lot cleaner. rstuckmaier brought up an important point, are you including the "Its Magic" script in the recovery. I thought that was needed to fix the checksum values.
I don't see where any of the new recoveries do anything with "itsmagic" during the install process. The new GPL complient does nothing with itsmagic. Nor do thors.
Here are some screens of the boot up screen and a ICS theme.
pimpmaneaton said:
Here are some screens of the boot up screen and a ICS theme.
Click to expand...
Click to collapse
Great job!
cruise350 said:
That is looking sweet, I like that 2nd gui alot better than the first one. A lot cleaner. rstuckmaier brought up an important point, are you including the "Its Magic" script in the recovery. I thought that was needed to fix the checksum values.
Click to expand...
Click to collapse
Yeah the first shot we were running the phone layout, Second is a tab layout but not correct res. We should get it all figured out monday.
pimpmaneaton said:
Yeah the first shot we were running the phone layout, Second is a tab layout but not correct res. We should get it all figured out monday.
Click to expand...
Click to collapse
I'm certain you'll post it up in the DEV sections as soon as it's ready for "prime time"!
Thanks again for your dedication and hard work!
kjy2010 said:
I'm certain you'll post it up in the DEV sections as soon as it's ready for "prime time"!
Thanks again for your dedication and hard work!
Click to expand...
Click to collapse
Yes I will, no need to just have small talk about it in the DEV thread untill she is ready to Rock&Roll. I am hoping that this will breather new life into this thread and Iconia A500 communtiy. I know I have not done a whole lot, but plan on doing more. 1st-TWRP 2.0, 2nd- New Galaxy Rom.
pimpmaneaton said:
Yes I will, no need to just have small talk about it in the DEV thread untill she is ready to Rock&Roll. I am hoping that this will breather new life into this thread and Iconia A500 communtiy. I know I have not done a whole lot, but plan on doing more. 1st-TWRP 2.0, 2nd- New Galaxy Rom.
Click to expand...
Click to collapse
We need a good new Galaxy ROM! Back when these tabs first came out, M-Deejay's Galaxy port was my favorite ROM. Of course that was back when I was flash crazed, and looking for a fit to my preferences. Can't wait for it!
pimpmaneaton said:
Yes I will, no need to just have small talk about it in the DEV thread untill she is ready to Rock&Roll. I am hoping that this will breather new life into this thread and Iconia A500 communtiy. I know I have not done a whole lot, but plan on doing more. 1st-TWRP 2.0, 2nd- New Galaxy Rom.
Click to expand...
Click to collapse
Thanks for this. Read up on TWRP and it sounds and looks great. Definitely looking forward to your Galaxy offering.
Great job spear-heading these efforts. They are appreciated.
pimpmaneaton said:
I don't see where any of the new recoveries do anything with "itsmagic" during the install process. The new GPL complient does nothing with itsmagic. Nor do thors.
Click to expand...
Click to collapse
"itsmagic" is needed to recalculate the ROM checksum for the encrypted bootloader, which is verified every time you boot. Either you need to execute it (and Thors DOES do that, just read the install instructions for his 1.6 V2 recovery), or you need to incorporate its code into your recovery.
If you flash a new rom without recalculating the checksum afterwards, the checksum verification will fail and you won't be able to boot, essentially bricking the device.
FloatingFatMan said:
"itsmagic" is needed to recalculate the ROM checksum for the encrypted bootloader, which is verified every time you boot. Either you need to execute it (and Thors DOES do that, just read the install instructions for his 1.6 V2 recovery), or you need to incorporate its code into your recovery.
If you flash a new rom without recalculating the checksum afterwards, the checksum verification will fail and you won't be able to boot, essentially bricking the device.
Click to expand...
Click to collapse
If you manually install thors kernels then yes you do use itsmagic. But his flash script does not use it nor is it included in the flash zip either. I ensure you it will be tested thoroughly before its release. I have flashed virtuous galaxy with it and it booted fine.
Sent from my Sensation Rockin MIUI 1.12.16!
Hey guys,
can you say me if there will be custom roms for this tablet in the future?
would be very nice, cause i love flashing all my devices
I would like to know too. Lenovo has crippled this version of Android.
willgreg21 said:
I would like to know too. Lenovo has crippled this version of Android.
Click to expand...
Click to collapse
They absolutely have. I was able to "semi-root" with framaroot, so thankfully su is added BUT I still can't uninstall bloatware...although there isn't much it still bugs me. full root and ROM still needed.
Custom ROM for S6000 would be very nice. Searching for it every day.
KitKat
Hopefully someone will add a KitKat ROM when possible, don't see lenovo upgrading us to it when it becomes available. Don't think the tablet is popular enough unfortunately though.
Just use titanium back up to remove bloat.... Work great for me
Sent from my IdeaTab S6000-F using xda app-developers app
Yea, I wish there was a custom ROM too. I just got my S6000-H yesterday, rooted it right away and used TiBu to remove some of the bloatware (I froze some more that I wasn't sure of). But it's missing simple things I'm used to from my N7000, like the advanced options in the shutdown menu.
I read in another thread that we do have a type of recovery built in - could someone tell me where to find it?
Never mind, found it ... and finally installed CWM today too. Now all I need is a nice custom ROM, but it doesn't look like any devs have that tablet
Use xposed to add modules. .. reboot, multi Window, floating, etc...etc... my S6000 tab works great. .. Still not good as my note 3 but...almost! My wife is jealous of all my tab can do... She think it stock that way. .. And her weird little Ellipses 7 Verizon gave hercan't do half of it. ... Guess I'll have to pimp her tab up for her! ! Look up x posed installer on xda, or Google it, then just follow where it leads. ... Easy
Sent from my SM-N900V using Tapatalk
Nimueh said:
Yea, I wish there was a custom ROM too. I just got my S6000-H yesterday, rooted it right away and used TiBu to remove some of the bloatware (I froze some more that I wasn't sure of). But it's missing simple things I'm used to from my N7000, like the advanced options in the shutdown menu.
I read in another thread that we do have a type of recovery built in - could someone tell me where to find it?
Never mind, found it ... and finally installed CWM today too. Now all I need is a nice custom ROM, but it doesn't look like any devs have that tablet
Click to expand...
Click to collapse
please a link for working CWM for b6000 h (3g) Thank you!
criszz said:
please a link for working CWM for b6000 h (3g) Thank you!
Click to expand...
Click to collapse
If you mean S6000-H then it's http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
I followed that step by step and it worked flawlessly
sorry my mistake , mean lenovo yoga tablet 8' b6000, sorry again , i was in a hurry, im wonder if that tool will work for me also, i'm afarid of briking
mpdayii said:
Use xposed to add modules. .. reboot, multi Window, floating, etc...etc... my S6000 tab works great. .. Still not good as my note 3 but...almost! My wife is jealous of all my tab can do... She think it stock that way. .. And her weird little Ellipses 7 Verizon gave hercan't do half of it. ... Guess I'll have to pimp her tab up for her! ! Look up x posed installer on xda, or Google it, then just follow where it leads. ... Easy
Click to expand...
Click to collapse
Thanks for that tip ... I just installed xposed and 3 modules, going to have a look through that huge list these days to see if I find more.
I installed the one to show the temperature in the status bar, the advanced reboot one and the one that shows RAM used/free in the task switcher. Pretty neat so far - if you know of any other "must-have" modules feel free to let me know
And sorry criszz, but no idea if that'll work on your tablet too
Nimueh said:
Thanks for that tip ... I just installed xposed and 3 modules, going to have a look through that huge list these days to see if I find more.
I installed the one to show the temperature in the status bar, the advanced reboot one and the one that shows RAM used/free in the task switcher. Pretty neat so far - if you know of any other "must-have" modules feel free to let me know
And sorry criszz, but no idea if that'll work on your tablet too
Click to expand...
Click to collapse
for xposed module i use a must have module : Gravity box and Boot manager
I installed Advanced Power Menu ... but Gravity Box I'm not sure about, way too much stuff in there I'll probably never need
I came across this:
http://lenovokitkatrom.blogspot.com/2013/09/upgradeupdate-ideatab-s6000-to-44-kitkat.html
Anyone have a look here? I'm usually sceptical of something not on XDA.
PRGS3 said:
I came across this:
http://lenovokitkatrom.blogspot.com/2013/09/upgradeupdate-ideatab-s6000-to-44-kitkat.html
Anyone have a look here? I'm usually sceptical of something not on XDA.
Click to expand...
Click to collapse
Blog was closed but I think you meant these: http://lenovoideatabs6000442kitkatrom.blogspot.de/ !?
I thinks this is a fake because as I know Mediatek chipsets aren't running on 4.4
But maybe this news can let us hope: http://news.softpedia.com/news/Medi...Coming-to-Tablets-by-Month-s-End-436176.shtml
schubi82 said:
Blog was closed but I think you meant these: http://lenovoideatabs6000442kitkatrom.blogspot.de/ !?
I thinks this is a fake because as I know Mediatek chipsets aren't running on 4.4
But maybe this news can let us hope: http://news.softpedia.com/news/Medi...Coming-to-Tablets-by-Month-s-End-436176.shtml
Click to expand...
Click to collapse
Thanks for that update!
I won't hold my breath for anything official seeing as Lenovo didn't even bump up to 4.3,
and zero ROMS out there? Or am I rubbish at searching?
I read in an other Forum that there is no Custom ROM yet because Mediatek isn't releasing Source Code of their ROMs. After Browsing Lenovo Site of the S6000 I have found this:
mobilesupport.lenovo.com/us/en/products/s6000_tablet?tabname=manuals
You get linked to Manuals, click on Downloads section and then there is:
Open Source Code - S6000 Tablet 10/12/2013 - 320MB
Don't know if it's the right thing, just wanted to mention it here.
And other News on KitKat:
news.softpedia.com/news/Android-4-4-KitKat-Update-for-Lenovo-Yoga-8-Inch-and-10-Inch-Tablets-Coming-in-June-438474.shtml
It's getting closer now, first 4.4 mediatek tablet ( lenovo yoga ) get's update in June. Let's hope for a compatible version / port for the S6000.
In am wondering if the Updates for the Yoga Tablets are compatible with the S6000, cause they use same processor and overall same specs.
Greetings JanDr0id
ps: i erased the httttttp in front of the links cause its my 1st post and xda isnt allowing me to post links yet.
I saw that mediatek released their source for kitkat. All the parts are there. Just need a Dev with one of these to assemble it.
barc0d3 said:
I saw that mediatek released their source for kitkat. All the parts are there. Just need a Dev with one of these to assemble it.
Click to expand...
Click to collapse
Lets hope there is a developer that can help compile it.
\o/ yey thanks to the moderator for letting me post links!
[update 25th February: modem now semi-working! Here's a pic ]
Hi all,
I'm excited to announce the availability of the inaugural release of SailfishOS for the M7 (GSM variant).
Instructions, information and download links are available here.
The adaptation is very much a work in progress: modem and camera not yet functional being the largest of the issues but we're actively working on them and hope to have functionality in place in the coming weeks. Regarding the US variants, the Sprint version has been successfully tested but public images for this adaptation are not yet available. There is an outside chance the 'vanilla' M7 SailfishOS image will function when paired with the appropriate Cyanogenmod 11.0 release but I wouldn't necessarily recommend it and don't have a device/am in the wrong continent to test.
So if you have an M7 kicking around that you don't use as your daily or are keen to see what is going on beyond the world of Android please take this for a spin. Who knows, you might even like it.
We chat about all* of our hardware adaptations on FreeNode in the #sailfishos-porters channel if you want to drop by.
Cheers,
Steph ([email protected], @chucisteph)
* if you're interested in other devices we're currently working on over 35 hardware adaptations and are actively engaging communities for more.
I wanna try sailfish OS
chucisteph said:
Hi all,
(links all disabled as I'm a new user. Could a moderator please PM me)
I'm excited to announce the availability of the inaugural release of SailfishOS for the M7 (GSM variant).
Instructions, information and download links are available here.
The adaptation is very much a work in progress: modem and camera not yet functional being the largest of the issues but we're actively working on them and hope to have functionality in place in the coming weeks. Regarding the US variants, the Sprint version has been successfully tested but public images for this adaptation are not yet available. There is an outside chance the 'vanilla' M7 SailfishOS image will function when paired with the appropriate Cyanogenmod 11.0 release but I wouldn't necessarily recommend it and don't have a device/am in the wrong continent to test.
So if you have an M7 kicking around that you don't use as your daily or are keen to see what is going on beyond the world of Android please take this for a spin. Who knows, you might even like it..
We chat about all* of our hardware adaptations on FreeNode in the #sailfishos-porters channel if you want to drop by.
Cheers,
Steph (FreeNode: stephg Twitter: @chucisteph)
* if you're interested in other devices we're currently working onover 35 hardware adaptations and are actively engaging communities for more. Please stop by #sailfishos-porters if you're interested.
Click to expand...
Click to collapse
I wanna try this sailfish rom. Can you send me a link on MP.
thanks
Wow, wasn't expecting that! I also want to try the ROM please . Thanks in advance
HerrNieschnell said:
Wow, wasn't expecting that! I also want to try the ROM please . Thanks in advance
Click to expand...
Click to collapse
Could a mod *pretty please* let me post links? (or post them for me, or another user post them, don't mind, I just want to share the info)
Never mind. Found it myself: https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_m7
Could you say how long it will be till we can expect a ROM with gsm working or are there problems you can't say how long it will take to solve them?
HerrNieschnell said:
Never mind. Found it myself
Could you say how long it will be till we could expect a ROM with gsm working?
Click to expand...
Click to collapse
Days hopefully but probably weeks. The modem is there and detected but I'm having difficulty turning it on. Once that's solved it should (hopefully!) Just Work(tm).
I am installing this rom on my HTC m7. Thank you so much. Will love to assist you people in any way possible.
Update:
Everything works perfectly except, GSM, camera and store. Have played with it for around half an hour. There is another bug with power off menu. It got stucked when i tried to do so forcing me to soft reset my mobile. And i tried adding my sim card and after the reboot it get stucked in boot loop.
Hoping to see fully working SFOS in nearest future.
I wanna try this sailfish rom. Can you send me a link please
HerrNieschnell said:
Never mind. Found it myself: https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_m7
Could you say how long it will be till we can expect a ROM with gsm working or are there problems you can't say how long it will take to solve them?
Click to expand...
Click to collapse
Touch screen not work my device :crying:
Hi all!
Happy to say that I have managed to get some modem support working this afternoon. I'll do my best to bake an image tonight. Where we're at at the moment:
* Modem functional but currently not showing SIM status correctly in UI
* SMS sending and receiving works
* Mobile data works (and shows correctly in the UI
* Call functionality works: can make and receive calls, however call audio not currently working
These are all problems that other devices have had in the past, and they all have solutions so I am going to work as quickly as I can to get them resolved and make an image in with fixes.
marslan81 said:
Touch screen not work my device :crying:
Click to expand...
Click to collapse
Sorry to hear. Your device is definitely a GSM m7? could you try re-flashing and see if it persists? if it does, are you happy using linux tools? we can debug it together.
utsavkoju said:
I am installing this rom on my HTC m7. Thank you so much. Will love to assist you people in any way possible.
Update:
Everything works perfectly except, GSM, camera and store. Have played with it for around half an hour. There is another bug with power off menu. It got stucked when i tried to do so forcing me to soft reset my mobile. And i tried adding my sim card and after the reboot it get stucked in boot loop.
Hoping to see fully working SFOS in nearest future.
Click to expand...
Click to collapse
That's great to hear. Once I have the modem properly working I will need help both for testing but also to enable store support (I need to send two IMEIs to Jolla so they can verify that the port works properly. Regarding your boot loop, the SIM should make no difference but I have noticed that the boot can sometimes be upset if the phone is started whilst plugged into a computer:- the GUI sometimes never comes up. I'm working on that but it only happens to me maybe 1 in 10 times so it's low down my list of priorities.
chucisteph said:
Sorry to hear. Your device is definitely a GSM m7? could you try re-flashing and see if it persists? if it does, are you happy using linux tools? we can debug it together.
That's great to hear. Once I have the modem properly working I will need help both for testing but also to enable store support (I need to send two IMEIs to Jolla so they can verify that the port works properly. Regarding your boot loop, the SIM should make no difference but I have noticed that the boot can sometimes be upset if the phone is started whilst plugged into a computer:- the GUI sometimes never comes up. I'm working on that but it only happens to me maybe 1 in 10 times so it's low down my list of priorities.
Click to expand...
Click to collapse
Yes my device HTC ONE M7_UL, TR devices, Unlocked, Super Cid, S-Off, TWRP 3.0 and Firmware 7.19.401.51 Hboot 1.61.0000
do not have touch the language selection screen.
marslan81 said:
Yes my device HTC ONE M7_UL, TR devices, Unlocked, Super Cid, S-Off, TWRP 3.0 and Firmware 7.19.401.51 Hboot 1.61.0000
do not have touch the language selection screen.
Click to expand...
Click to collapse
What kind of computer do you use? Windows/Mac/Linux?
chucisteph said:
What kind of computer do you use? Windows/Mac/Linux?
Click to expand...
Click to collapse
Windows 10 fastboot driver ok
marslan81 said:
Windows 10 fastboot driver ok
Click to expand...
Click to collapse
ok so sailfish is a fully blown linux distribution, means that once it's booted, even if the gui is messed up you can still SSH into it and ask it what it's doing (similar to adb shell). I just need to go RTFM how to make Windows recognise the USB network that your phone is presenting when you plug it in.
marslan81 said:
Windows 10 fastboot driver ok
Click to expand...
Click to collapse
Did you try the re-flash by the way?
chucisteph said:
Did you try the re-flash by the way?
Click to expand...
Click to collapse
Thanks for your help.
I tried 3 times,
I'm doing the setup with the following steps
1- Full wipe
2- İnstal "cm-11-20141112-SNAPSHOT-M12-m7"
3- Shutdown and Powered up again by launching android
4- Reboot Recovery and instal "sailfishos-m7-release-2.0.0.10-sg-rel-201602180750.zip", and reboot again
5-Normaly boot but touch does not work in the language of choice
Sorry for my bad english
marslan81 said:
Thanks for your help.
I tried 3 times,
I'm doing the setup with the following steps
1- Full wipe
2- İnstal "cm-11-20141112-SNAPSHOT-M12-m7"
3- Shutdown and Powered up again by launching android
4- Reboot Recovery and instal "sailfishos-m7-release-2.0.0.10-sg-rel-201602180750.zip", and reboot again
5-Normaly boot but touch does not work in the language of choice
Sorry for my bad english
Click to expand...
Click to collapse
Your English is fine!
ok so your steps 1) and 2) only need to be done once:- Sailfish relies on the CM version for hardware support but once CM has been installed, when you install the SFOS zip it goes next to the CM /system and /data.
4) You're using an older SFOS image: does this one work: http://images.devaamo.fi/sfe/m7/sfe...s-m7-release-2.0.0.10-sg-rel-201602191147.zip
Out of interest, in step 3, does touch work?
No am sorry
Perhaps in a different firmware version required, because the power button works. Maybe that's enough for tonight I'll try again tomorrow. Thank you, good night
chucisteph said:
* Modem functional but currently not showing SIM status correctly in UI
* SMS sending and receiving works
* Mobile data works (and shows correctly in the UI
* Call functionality works: can make and receive calls, however call audio not currently working
Click to expand...
Click to collapse
Thanks for all your hard work. I am really impatient for your next release. These fixes are really important and one m7 will be my daily driver for next few months .
chucisteph said:
Once I have the modem properly working I will need help both for testing but also to enable store support (I need to send two IMEIs to Jolla so they can verify that the port works properly.
Click to expand...
Click to collapse
Count me In.
chucisteph said:
Regarding your boot loop, the SIM should make no difference but I have noticed that the boot can sometimes be upset if the phone is started whilst plugged into a computer:- the GUI sometimes never comes up. I'm working on that but it only happens to me maybe 1 in 10 times so it's low down my list of priorities.
Click to expand...
Click to collapse
I did a quick reflash and its working perfectly now.
Was just wondering if it was possible and if so, what version of Cyanogenmod would I need?
First off, there is no more CyanogenMod. The CyanogenMod people started a new project called Lineage.
Now to answer your question. Yes, it is possible.
The Optimized LineageOS ROM should work on your device.
Pwnycorn said:
First off, there is no more CyanogenMod. The CyanogenMod people started a new project called Lineage.
Now to answer your question. Yes, it is possible.
The Optimized LineageOS ROM should work on your device.
Click to expand...
Click to collapse
Ok, thanks.
Is it easy to install? (my first Android phone and my first time installing a custom rom)
razerphynx said:
Ok, thanks.
Is it easy to install? (my first Android phone and my first time installing a custom rom)
Click to expand...
Click to collapse
The install process is a subjective matter.
For me it's easy since I've been doing these things for over 4 years.
For you it might seem complicated at first.
There are various guides and video tutorials that will show you how to do it. The process is usually the same for every phone and for every ROM.
Pwnycorn said:
The install process is a subjective matter.
For me it's easy since I've been doing these things for over 4 years.
For you it might seem complicated at first.
There are various guides and video tutorials that will show you how to do it. The process is usually the same for every phone and for every ROM.
Click to expand...
Click to collapse
Fair enough, I guess I'll have to educate myself on the matter before attmepting to install anything.
I do have a couple more questions;
1. Does Lineage improve performance and battery life like Cyanogenmod claims to do?
2. I think Lineage is based on a newer OS (Android 7.x.x) then my phone natively supports (Android 5.0.1), would that be an issue?
razerphynx said:
1. Does Lineage improve performance and battery life like Cyanogenmod claims to do?
Click to expand...
Click to collapse
Yes and yes.
razerphynx said:
2. I think Lineage is based on a newer OS (Android 7.x.x) then my phone natively supports (Android 5.0.1), would that be an issue?
Click to expand...
Click to collapse
Yes, although the LineageOS guys, the XDA community and devs (who work on it for free, during their spare time) manage to port the last version of Android to this device, you can expect some bugs, a degraded camera quality (because of proprietary blobs Samsung do not publish), and to loose some functionalities (smart pause, smart scroll).
However, the stock Android experience is worth the switch and you will learn a lot of things here, which is invaluable.
Try the unofficial LineageOS by side (original development forum).
Ok, thanks for the answers
Last question, would you be able to send me a download link to it? I couldn't find the right one for my phone.
razerphynx said:
Ok, thanks for the answers
Last question, would you be able to send me a download link to it? I couldn't find the right one for my phone.
Click to expand...
Click to collapse
I already told you, you need the Optimized Lineage ROM. It has your device listed as "supported".
It's in the GT-I9505 Original Development section. Impossible to miss, it's always around the top of the list.
And it is universal, meaning that there is no special version for your device.
Do note that the developer himself has a GT-I9505, and so do most of his test team members. So there's no guarantee that it will be a flawless experience.
Sorry, I must've missed that. Will report back once I get it installed
Thanks for all the help
Edit: On the download page there's two different versions
"Optimized-LineageOS-14.1-20170120-jflte-AROMA.zip"
and
" Optimized-LineageOS-14.1-20170120-jflte.zip"
Which one do I download?
YAY, it's all set-up and working now. Thank you all very much
Whenever I lock my phone, the screen stops working. I then have to restart my phone to get the screen working again. Any solutions?
razerphynx said:
Whenever I lock my phone, the screen stops working. I then have to restart my phone to get the screen working again. Any solutions?
Click to expand...
Click to collapse
Use the stock kernel. On the download page there should be an "extras" folder.
If you can't find it then download the aroma version and flash it. This one gives you some options during the install process.
Thanks, that fixed the issue.
Got another question,
How do I make my phone show up on my PC? Like it shows up as "GT-I9507" but when I open it, it's just empty. Before on stock Android it had 2 main folders, something like "Internal" or "System" and "SDCard" and they both had multiple subfolders.
razerphynx said:
Thanks, that fixed the issue.
Got another question,
How do I make my phone show up on my PC? Like it shows up as "GT-I9507" but when I open it, it's just empty. Before on stock Android it had 2 main folders, something like "Internal" or "System" and "SDCard" and they both had multiple subfolders.
Click to expand...
Click to collapse
That I do not know.
Should work straight away normally.
Try enabling/disabling USB debugging while the phone is connected.
Tried that, still nothing
razerphynx said:
Got another question,
How do I make my phone show up on my PC? Like it shows up as "GT-I9507" but when I open it, it's just empty. Before on stock Android it had 2 main folders, something like "Internal" or "System" and "SDCard" and they both had multiple subfolders.
Click to expand...
Click to collapse
Select notification "USB charging this device" or anything similar, select MTP. It'll auto reconnect and it should work.
Sent from my Redmi 3 using XDA Labs
Oh, yeah. Try what he said.
I haven't connected my phone to a PC in years, so I wouldn't know what to do.