Update 05/10/2011: So, at this point I've just fallen too far behind the curve, and it doesn't look like I will be updating GladiAtrix any further. I'll still support v4.2.3 for 1.57 (which is pretty stable, and almost all the issues I've seen users have up to this point are the installation). I may at some point throw something together for myself to use and release it (as I don't care for the themes/mods of GingerBlur/GreyBlur), but at this point I'm doing all the mods manually and have no current plans to make a flashable zip out of it.
GladiAtrix 2 for 1.5.7 v4.2.3 CWMNews and Important Info - READ FIRST
{
"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"
}
Looks horribly out of place I know
04/14/2011 @ 10:00am: Download links are fixed. Sorry all! As I stated in my last post, I will be unavailable for the next few hours. I DO see your questions and I WILL answer them. Please be patient, this isn't my full-time job and I have other things that need my attention today. Thanks!
04/13/2011 @ 11:17pm - NOTICE on theme: The THEMED version does not have reboot/recovery. I've been too busy working out the other kinks to add it in. The NOTHEME version is just like v3 and older, with the reboot/recovery options intact, as well as all the other changes up to this point. That is the only difference between the two.
All the bugs with the fingerprint scanner, wifi defaulting to on, custom keyboards not working, etc. etc. should all be resolved. Please PM me or reply to the thread if you have any issues.
Version 4.2.3 is going to be considered base from here on forward. It will create a backup of all the files it changes and copy them to the root of the internal SD card. PLEASE copy this backup to some place safe. Going forward, all updates will be released on top of 4.2.3, and will create sequential backups of any new files changed, if there's a need to back them up. It does not have any feature updates since 4.2.1, just many bug fixes.
04/13/2011 @ 11:00am(ish) - NOTICE on Reboot/Recovery power menu options: These are currently removed. I added a theme, and I haven't had time to add reboot/recovery options to it yet. If someone who knows what they're doing would like to add them and send me the updated files, it would certainly expidite the process as I'm not even sure how I got them working in the first place on v1-3. Screenshots will be in the second post as soon as I get a moment to upload some.History and SummaryCWM finally released! Sorry for taking so long with it, I'm very picky about my work and wanted to test EVERYTHING and make sure it was all working as it was supposed to. I hope the extra effort pays off and nobody has any issues with this
I've removed the script version as there's no need for it anymore. CWM is safer and does everything we need it to do with the latest version.
This is only for AT&T phones running firmware version 1.57. If you have 1.52 or 1.26 please go here first: [SCRIPT] GladRoot (Bell 0.37.4, AT&T 1.26/1.52/1.57 Supported) If you are a Bell user, DO NOT INSTALL.
If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
If you run into any issues, please PM me or post your /data/local/tmp/ga2.log here. This will help me diagnose what went wrong, in the very unlikely event something goes wrong.
Come chat with us!Features:
Deodexed
Creates a backup of your current /system/app and /system/framework directories (This does NOT delete anything outside specific AT&T bloatware files, however)
Custom boot logo (animated version coming soon!)
AppWidgetPicker (better widget management)
Enables sideloading
Ad blocking
Installs AT&T tethering APN
Enables desktop flash content, i.e. Hulu (You MUST install flashplayer 10.2 from market prior to installing the ROM. You must also use a browser that lets you set your user agent to Desktop, such as Dolphin Browser HD)
Clears Dalvik-cache (can cause some third party apps to behave strangely, just clear their data. Known to cause issues with Launcher Pro. Reset of LP data fixes)
Removes the AT&T bloat (see second post for list of what is removed.)
Enables HDMI mirroring
Disables background media scanning (speeds phone up a LOT)
Webtop without need for dock (through micro-hdmi cable)
Xperia Arc theme (ported to Atrix by olieebur)
Preferred install location
Various speed increase enhancements to settings
Replaces stock Gallery with Miui 3D Gallery
Full market access, no more restricted apps (Currently under testing, as it doesn't seem to be working properly)
Installation instructions:
Download and install Tenfar's latest CWM Recovery.
Download the GladiAtrix2 v4.2.3 THEME zip file here or GladiAtrix2 v4.2.3 NO THEME zip here
If you want the Hulu hack to work, install 10.2 from the market now, BEFORE installing GladiAtrix2 v4.
Put the GladiAtrix2v4.2.3 zip corresponding to the version you selected (normal or notheme) on either internal or external SD card.
Boot into recovery.
Select “Install zip from SDCARD” using the volume keys to navigate and power button to select.
Select "choose zip from sdcard" if you put it on your external SD card, or "choose zip from internal sdcard" if you put it in phone memory.
Browse to the location you put the zip.
Select GladiAtrix2v4.2.3 zip corresponding to the version you selected (normal or notheme).
Install it!
Read disclaimer below
DISCLAIMER
This script makes significant changes to the /system files on your phone.
By downloading the files you agree that you KNOW WHAT YOU ARE DOING and that you accept responsibility if something goes wrong.
This has been tested to the best of my ability.
We are NOT responsible if this bricks your phone. Thank you.
-ManagementDownload LinksDownload GladiAtrix2 v4.2.3 FULL here
Download GladiAtrix2 v4.2.3 FULL NOTHEME hereChangelog:* Version 4.2.3 - Released 04/13/2011
Split the theme and notheme into their own versions
Rolled all updates up to this point into a full install
New base install version is this version, all future updates will be incremental.
Cleaned up install methods to not mess with any user settings
* Version 4.2.2 - Released 04/13/2011
Permission fix update for settings.db causing a massive number of issues
* Version 4.2.1 - Released 04/13/2011
Fixed HDMI mirror errors
Changed fingerprint to allow unrestricted market access
Added Motoblur widgets/apps back in as people seem to use them (myself included). AT&T bloat still removed.
Replaced stock MediaGallery with Miui 3D Gallery
Added ability to use webtop without dock through micro-hdmi
Minor settings changes for increased battery life/performance
Fixed issues with flash hack (recompiled the lib as it was corrupt)
Added option for preferred installed locations to Settings -> Applications
Imported Xperia Arc theme (ported to Atrix by olieebur)
* Version 3 - Released 04/10/2011
Now removes some of the Motoblur/AT&T bloat
Added custom boot logo (Animated version coming soon!)
Added HDMI mirroring support (Credit to Weichel)
Turned off stagefright media scanning
Added local.prop tweaks for performance increase
Fixed issues with tethering on non-AT&T carriers
* Version 2 - Released 04/08/2011
Initial CWM release.
Added custom flash lib for desktop flash content (i.e. hulu)
Installation logged with errors to /data/local/tmp/ga2.log
* Version 1
Initial script release.
Notes/thanks:Special thanks to: kennethpenn for the base installation instructions, shawnbuck/dasmoover/cranch/thews/sogarth/brandon15811/(anyone else I missed, apologies if I did) for all their insight on the script, and Chainfire for the use of his .sh recovery output methods, olieebur for the great work on the theme, weichel for the HDMI mirroring trick, and everyone who helped test in IRC.If you see any spelling errors or have any other problems, feel free to PM me or post here.
If you have any feature requests, PM ME them. Please read post #2 for my current To Do list to make sure it's not already on there. If you know how to do anything on the to do list and would like to help out, send me a PM. I will ignore any "cn u add grhpix to the statuss bar?" in the thread.
To Do
bootanimation - Make static logo into animation
Fix reboot/recovery options - Anyone that wants to help with this is more than welcome to.
kill sound on sd mount - Possible?
Uninstall script - Coming soon!
List of Motorola/AT&T apps removed
com.telenav.app.android.cingular.apk
com.att.myWireless.apk
com.blockbuster.app.moto.apk
com.ea.nfsshift.apk
com.mobitv.client.tv.apk
com.mtag.att.codescanner.apk
com.wavemarket.waplauncher.apk
com.yellowpages.android.ypmobile.apk
com.qo.android.moto.apk
Screenshots (coming soon!)Will post screenshots of the major highlights here, but right now, I'm going to bed.
first !! thanks
Ririal, is it possible to add the option to set "Edge network only" as the stock Android would allow?
PM'd u
When I go to run this it asked too allow superuser, but superuser never asked to allow anything on the phone? Phone just sits there?
Running silky smooth. I'll report errors if they arise.
s0dhi said:
Running silky smooth. I'll report errors if they arise.
Click to expand...
Click to collapse
When you run the .bat file did you have too allow superuser on the phone?
JayRolla said:
When you run the .bat file did you have too allow superuser on the phone?
Click to expand...
Click to collapse
Yes. There are 3 (I think?) points at which you have to allow superuser.
The user interface for the install is really well done.
JayRolla said:
When you run the .bat file did you have too allow superuser on the phone?
Click to expand...
Click to collapse
Never mind had to reboot phone a few times and then it worked.
Ririal said:
To Do
bootanimation - Anyone up to making one is welcome, I'm bad with graphics :x
preferred install location - Need to figure out how to do this.
kill sound on sd mount - Possible?
Fix typo in splash screen - Sigh.
Click to expand...
Click to collapse
there are a handful of boot animations here if anyone is interested. if there's something in particular you want, i'd be happy to give it a go. i too suck at the whole graphics thing, so i wouldn't expect too much.
Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.
This is after you have done retain root and updated and the afterupdate retain root.
Sent from my MB860 using XDA Premium App
xyrovice said:
Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.
Click to expand...
Click to collapse
You need a 1.57 rooted to proceed with this as it says in the OP. if you are at 1.26 rooted then use the retainroot in xda to get rooted on 1.57 and then use this.
Will this work on the Atrix on Bell?
itsonlym3 said:
there are a handful of boot animations here if anyone is interested. if there's something in particular you want, i'd be happy to give it a go. i too suck at the whole graphics thing, so i wouldn't expect too much.
Click to expand...
Click to collapse
I was looking for a custom one. I have a friend who's going to be whipping up some images for me, but you're welcome to take a stab at it.
xyrovice said:
Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.
Click to expand...
Click to collapse
This rom does not update you to 1.57. You will need to be on 1.57 with root before this will work.
jayhammy said:
Will this work on the Atrix on Bell?
Click to expand...
Click to collapse
No, it will not.
I have a 1.57 w/ root (using before/after update script). Will Deodexing my Atrix make it faster/snappier?
kpfury said:
I have a 1.57 w/ root (using before/after update script). Will Deodexing my Atrix make it faster/snappier?
Click to expand...
Click to collapse
A bit, yes.
Ririal said:
To Do
kill sound on sd mount - Possible?
Click to expand...
Click to collapse
If you figure this out please share how you did it.
I don't think that sound can be killed. But then again I'm no expert. Also are there any known issues with GladiAtrix?
I have it installed but can't really tell for now. Great great work man!!
Any chance of some screen shots of this theme? If we had CWM I would just flash and check it out.Thanks.
Sent from my MB860 using XDA Premium App
Related
[DISCONTINUED!]
There are so many good roms out there, no need for this one. I nowadays prefer CyanogenMod6 and will stick to it, with small modifications. I suggest you do the same ;-)
So, here it is! My first cooking
The ROM is VERY stable. About 170MB free ram standard. When using a task killer (kill ALL) the RAM boosts up to 225MB. So this is my first public release, been tweaking and trying out different combinations of apps, more changes will come!
SpeedLegend v0.6 - Update Base 2.03.405.3
Changelog:
Boot sound removed!
Facebook sync loop fixed!
Bluetooth fixed! (Successfully transfered pics between my nokia and legend both ways)
Flickr re-added.
LauncherPro, ROM Manager, XDA-App, EStrong File Manager removed (d/l what you want from market! customize yourself!)
Full changelog of ALL removed files coming up at a later point. Right now? I'm too tired!
No more A2SD version as it didn't seem to work properly.
SpeedLegend v0.511 - Minor update Base 2.03.405.3
Changelog:
Dialer One re-added (sorry about that)
HTC Lockscreen removed (Now using Vanilla Lockscreen)
HTC Peep Removed (now using Official Twitter, uninstallable)
Removed some more useless HTC stuff (nuff said! )
Home Switcher removed (just get it from market if you want it)
SpeedLegend v0.51 - Minor update Base 2.03.405.3
Changelog:
Added XDA-App (uninstallable)
Added ROM Manager (Uninstallable)
Removed HtcMusic (Replaced by Eclair Music)
Removed HtcWorldClock (Replaced by DeskClock)
Removed some more useless HTC stuff
Deodex'd!
Without and with a2sd (a2sd untested! Please report!)
SpeedLegend v0.5 - Initial Release Base 2.03.405.3
What is Removed
Startup Wizard -> No wizard at first boot! (Useless?) Add accounts by Settings -> Accounts & Sync!
Sense UI (Rosie)
All HTC Widgets (or at least most of, until I know what all htc-files do. WIP!)
HTC Dialer (Replacement: Dialer One)
Weather (and all there is to it)
FieldTest (what is it?)
HTC Flickr
Footprints
PicoTts (text to speech)
And possibly alot more I've forgotten all about...
Moved to Uninstallable:
Calculator
Facebook
FriendStream
Peep (Twitter)
Voice Recorder
PDF Viewer
Maps
QuickOffice
Teeter
YouTube
Added to System:
ROOT (of course)
Dialer One (check out the screenshot)
Added (Uninstallable)
LauncherPro 7.1.0
Home Switcher
EStrong File Manager
USB Switcher
Other:
Facebook support remains intact! Syncing contacts with pics perfectly!
Download v0.6 - 4shared
Download v0.511 - 4shared
Download v0.511 a2sd - 4shared
Download v0.51 - Link removed!
Download v0.51 a2sd - Link removed!
Download v0.5 (no waiting time)
Download v0.5 a2sd (no waiting time) [UNTESTED! Can't test it myself due to class2 sd-card! (min class4 required!)]
{
"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"
}
Known Issues/ToDo (v0.511)
No popup when connecting the phone to a computer, eg. no disk drive. Added USB Switcher (widget) until I manage to fix this (probably removed somthing that is needed). Add USB-widget to homescreen, connect phone to USB, press the widget - Now you have a disk drive connected.
Some options in Settings (Personalize, Text to Speech, Connect tp PC) cause FC because of Rosie and Tts-services removed.
Not ROM-related:
Want Live Wallpapers? Go Here!
Looks good : D
But I'll wait, as I haven't been doing any flashing with my phone yet, and I kind of like it as it is.
If possible without too much hassle, why not remove the messaging-app and install handcent(or something) instead?
And btw, why are you using the 2.03 ROM now when the 2.05 is out?
Looks good
no-one has released a 2.05 to use as base is pretty much the answer, i will use 2.05 as a base for my rom when someone releases it
jonaseg said:
If possible without too much hassle, why not remove the messaging-app and install handcent(or something) instead??
Click to expand...
Click to collapse
It's very possible, I just like the stock HTC messaging app I have never tried hanscent, maybe I should check what it's all about..
I liked it too, until they made it unusable(doesn't scroll all the way down when opening a thread..) in 2.05..
jonaseg said:
I liked it too, until they made it unusable(doesn't scroll all the way down when opening a thread..) in 2.05..
Click to expand...
Click to collapse
When base 2.05 comes, and if that bug still persists - I will definetly change the app to something else. But I'm trying to keep the memory usage minimal, I will have a look at handcent and compare it to the standard Eclair app. But as long as the base is 2.03 I'm guessing I'll keep it stock..
Still trying to deodex the ROM. damnit.. boot loop persists :<
Hi...
Thanks for your release and efforts..
Now I am using RODRIGUEZ STYLE v 2.3 and it works good...
But today I faced with a problem that the nexus start page repeated after restarting the phone and the phone did not log in, I tried many ways but that was not fixed, so I decide to choose another ROm, I am not sure which rom should I use, but yours looks good.
I have some questions, then I am going to start installing it..
MY PHONE DATA:
Baseband: 47.26.35.04U_7.05.35.26.L
Build number: 1.31.405.4
-----------------------------------
Can I use your rom without any problems???
My phone was rooted with r4 modaco.
But Can I Unroot it after installing your rom and get the FROYO UPDATE that HTC is gong to release..???
I dont want to brick my phone because of wrong Radio version,and I dont know how can I find that, which rom is suitable for my phone and which one is not.,would you please tell me that, is this rom suitbale for my phone and i am not going to brick it?..
And, Does this Rom contain Persian or Arabic characters support for reading SMS and Web Browsing..???
Is the bluetooth works smoothly with this rom..??
Thanks for your answer...
efex said:
When base 2.05 comes, and if that bug still persists - I will definetly change the app to something else. But I'm trying to keep the memory usage minimal, I will have a look at handcent and compare it to the standard Eclair app. But as long as the base is 2.03 I'm guessing I'll keep it stock..
Still trying to deodex the ROM. damnit.. boot loop persists :<
Click to expand...
Click to collapse
Did you remember to sign the apk's after the deodexing? That can be what is causing the bootloop... always sign all apk's when making a change..
mercury700ir said:
Can I use your rom without any problems???
My phone was rooted with r4 modaco.
But Can I Unroot it after installing your rom and get the FROYO UPDATE that HTC is gong to release..???
I dont want to brick my phone because of wrong Radio version,and I dont know how can I find that, which rom is suitable for my phone and which one is not.,would you please tell me that, is this rom suitbale for my phone and i am not going to brick it?..
And, Does this Rom contain Persian or Arabic characters support for reading SMS and Web Browsing..???
Is the bluetooth works smoothly with this rom..??
Thanks for your answer...
Click to expand...
Click to collapse
Yes, since your phone is rooted you can install this, and it will remain rooted. You can unroot the same way as with r4, eg. just install the RUU and it's done.
Persian/arabic did not work, neither menues or keyboard. I can look into that, see if I can find the solution for it.
whitetigerdk said:
Did you remember to sign the apk's after the deodexing? That can be what is causing the bootloop... always sign all apk's when making a change..
Click to expand...
Click to collapse
Oh, thats why then.. I signed the apk:s BEFORE deodexing.. wondered why it worked yesterday, but not today (guess I managed to change the order somehow.. shame on me!) Thank you!
efex said:
Yes, since your phone is rooted you can install this, and it will remain rooted. You can unroot the same way as with r4, eg. just install the RUU and it's done.
Persian/arabic did not work, neither menues or keyboard. I can look into that, see if I can find the solution for it.
Click to expand...
Click to collapse
thanks man...
I am really a fan of you....
Now I am downloading the rom..
My ROM ver is 1.31, if I upgrade it with your rom to 2.03, Can I install 1.31 RUU again?? or I should find a 2.03 RUU..??
And, I know that KYOSA add persian characters support to his ROM, maybe it can help you to do this for your next release...
mercury700ir said:
My ROM ver is 1.31, if I upgrade it with your rom to 2.03, Can I install 1.31 RUU again?? or I should find a 2.03 RUU..??
And, I know that KYOSA add persian characters support to his ROM, maybe it can help you to do this for your next release...
Click to expand...
Click to collapse
You can unroot with any stock RUU, 1.31 if you want, or 2.03 if you prefer that. The RUU updater wont care which version of a rooted ROM you have.
I'll see what I can find about the languages. Found a way for G1 that should work for Legend roms too, but I'll se if I can find anything else.
Okay, found this one update that should give arabic support to any ROM. I don't have a chance to test myself (I cant read arabic so I wouldn't know if it's right?). I did not make this file, I don't know who did, but I'm not taking any creds for it.
Download
Install the rom, then (without wiping), update with this. Please let us know if it works as it should.
Ok, this looks very nice. Ill try iy out.
oh btw, does this rom have app2SD ?
efex said:
Okay, found this one update that should give arabic support to any ROM. I don't have a chance to test myself (I cant read arabic so I wouldn't know if it's right?). I did not make this file, I don't know who did, but I'm not taking any creds for it.
Download
Install the rom, then (without wiping), update with this. Please let us know if it works as it should.
Click to expand...
Click to collapse
Ok, Thanks...
Tomorrow I'll try...
The internet connection bandwidth here is dead I think, the download speed is about 14 KB/Sec now..
I don't know why...
But tomorrow absolutely I'll give you the result.
nafnist said:
Ok, this looks very nice. Ill try iy out.
oh btw, does this rom have app2SD ?
Click to expand...
Click to collapse
No A2SD on this ROM (I dont have my class10 sd anymore, running on a class2 so cant use a2sd). I can make one with a2sd, but I can not test it myself..
EDIT: Added A2SD version in first post. Untested, feel free to try it and please report any problems!
arh kom så, viking! 200 dkr for 8gb class4!! hehe
This needs app2SD hehe
anyhow,
First boot was really fast, and noticed that after scrap'in all HTC on this ROM you forgot to replace the Screen-Lock !
Im personally fond of this vanilla one; http://forum.xda-developers.com/showthread.php?t=709183
needs a deodexed rom tho ;-(
i left the lockscreen on purpose, and the htc music player (they are connected). i should change both, just havent really checked in to it yet. Still lots and lots of htc-files in the system/app, needs cleaning, but I'm working on it.
About the deodex, Im running into problems there.. Deodex (+ sign apk's) = reboot loop. Can't seem to figure it out!
I liked that lockscreen btw. I'll probably change to it, remove htc world clock (replace with eclair clock) and change the music player.
whitetigerdk said:
Did you remember to sign the apk's after the deodexing? That can be what is causing the bootloop... always sign all apk's when making a change..
Click to expand...
Click to collapse
Short: Don't sign the apks, it's not necessary, even dangerous. And it breaks your precious ROMs.
Long explanation:
If you compile the sources yourself, the scripts will at a certain point create your private and public platform keys, store them in /etc and also sign all apks with it. So this wouldn't be a problem if you could compile Sense.
If you blindly re-sign every package you run into a problem: You use a key that differs from the one in the key-storage (the one HTC uses to build and sign). And there's nothing you can do about that.
Eventually you will face the biggest troubles with four packages.
Vending:
Resign it and no paid apps will available at all (which is obviously caused by replacing Google's signature with yours).
GoogleCheckin, GoogleSubscribedFeedsProvider and NetworkLocation (and some non proprietary ones I don't remember):
Now these are even trickier as they require access to features that the platform strictly locks away from apps.
No app, downloaded or pre-installed is granted these rights except for when it was signed with the platform key. This was done to protect the users.
Resign these and you will see "Package xyz has no signatures that match those in shared user android.uid.system; ignoring!" in your log-files.
That being said there are lot's of reasons why odexing could fail. I've had a few unsuccessful attempts of using dexopt-wrapper on my device without any obvious reasons - I know for sure that bootclasspath and everything else was correct.
But, there's a nice little trick to make it work: Don't do it (yourself)!
Instead you can grab the files from /cache/dalvik-cache, they are exactly the same.
GladiAtrix for OLYFR_U4_1.5.2 v0.3
Deodexed the 1.5.2 SBF and repackaged everything up, including the WiFi and Market fixes. Just like Adeo, you do not need to root first.
Working on getting the reboot/recovery power options, preferred install location, and unknown sources (this now enables sideloading, though) tweaks installed. The new version adds options to root, add the tethering APN, init.d support and sideloading at the same time this installs.
This is only for AT&T phones running firmware version 1.5.2. If you have 1.2.6 please go here: GladiAtrix for 1.2.6 v1
Come chat with us!
Features:
Standard Features
Works on rooted and non-rooted devices
Deodexed
Da_G's WiFi fix
ghost_o's Market fix
Ad blocking
v0.2+ Optional Features
Root
Tethering APN
Sideloading
init.d support
Installation instructions:
Read the instructions all the way through before starting
Read them again and make sure you understand them
Download the file from the link below
Extract the files to any folder
Connect your phone with USB debugging, set USB mode to none (unsure if this is required, but I always do it to be safe)
Run INSTALL.bat
Follow the on-screen instructions for rooting, sideloading, tethering APN, and init.d support
Confirm installation of the ROM
Wait PATIENTLY for it to finish and reboot your phone
Read disclaimer below
DISCLAIMER: I've only tested this on my device. I ran it twice to be sure, once with aRoot, once without, both on fresh SBF reflash. I am not responsible if this bricks you.
Download Links
Direct Download Link: http://goo.gl/B8T6L
Alternate Download Link: http://goo.gl/Eue6I
Changelog:
* Version 0.1
Initial release
* Version 0.2
Updated installer script
Added options for rooting, tethering apn, sideloading, and init.d support.
* Version 0.3
Major improvements to installer script
Fixed syntax bug on root/tethering/sideloading/init.d to make it function properly again
Notes/thanks:
I have not tested the wifi fix as I haven't had any wifi issues in the first place. If someone could confirm this, I would appreciate. Feel free to PM me if you have any issues or see anything that needs to be changed.
Special thanks to: Da_G for wifi fix, ghost_o for market fix, designgears for the use of his Adeo and aRoot scripts, Sogoth for the batch sorcery, and gitbrew.org for hosting
Reserved
To Do:
Add reboot option to power menu
Add recovery option to power menu
Add support for 1.2.6
Very good work.
great! thank you!
Awesome! I've got GingerBlur but I know a lot of people loved using Adeo and with this update it will help. Good work!
Damn son! I wanna try this but I don't wanna start over from sbf. It scares me to brick though. Lemme know how it goes
Sent from Atrix ;-)
Sweet! Nice job man.
frankiedizzle87 said:
Damn son! I wanna try this but I don't wanna start over from sbf. It scares me to brick though. Lemme know how it goes
Sent from Atrix ;-)
Click to expand...
Click to collapse
There should not be any bricks resulting from this software, the creator just does not want to be held responsible for any mistakes the user may make.
frankiedizzle87 said:
Damn son! I wanna try this but I don't wanna start over from sbf. It scares me to brick though. Lemme know how it goes
Sent from Atrix ;-)
Click to expand...
Click to collapse
Updated first post with instructions and a little more info. This shouldn't brick you if you do everything correctly.
Also, if anyone has run this and can confirm market or wifi fixes for me, I would definitely appreciate.
It won't work on the Bell Atrix, would it?
i.mac said:
It won't work on the Bell Atrix, would it?
Click to expand...
Click to collapse
I don't really see any reason why it wouldn't. You might get the default AT&T apps loaded (which can just be easily removed through the app management in settings), but I find it hard to believe the apps are that much different. I would probably hold off on it, though. If you want to get me a /system dump from a stock Bell Atrix (there might be one already I haven't really looked), I can deodex it and make a new package for it.
Ririal said:
I don't really see any reason why it wouldn't. You might get the default AT&T apps loaded (which can just be easily removed through the app management in settings), but I find it hard to believe the apps are that much different. I would probably hold off on it, though. If you want to get me a /system dump from a stock Bell Atrix (there might be one already I haven't really looked), I can deodex it and make a new package for it.
Click to expand...
Click to collapse
If you tell me how... I would be more that happy to do so.
How to add power menu options. Hope this helps.
http://forum.xda-developers.com/showthread.php?t=811532
doesn't gingerblur already deodexes whatever SBF you have? if so, i don't see the point in this.
Anyway, if you want to enable unknown sources, just download aroot and copy the script from there, it's way easy, it's just a sql statement via sqlite to make it happen.
franciscojavierleon said:
doesn't gingerblur already deodexes whatever SBF you have? if so, i don't see the point in this.
Anyway, if you want to enable unknown sources, just download aroot and copy the script from there, it's way easy, it's just a sql statement via sqlite to make it happen.
Click to expand...
Click to collapse
Not all of us want a themed device. Some of us want to customize it ourselves. :x
franciscojavierleon said:
doesn't gingerblur already deodexes whatever SBF you have? if so, i don't see the point in this.
Anyway, if you want to enable unknown sources, just download aroot and copy the script from there, it's way easy, it's just a sql statement via sqlite to make it happen.
Click to expand...
Click to collapse
Yes it does, but afaik Gingerblur is optimized for 1.2.6, this is for the leaked 1.5.2 SBF. There were more than a few apps that were updated and are much smoother than the 1.4.6 apps (camera for one), so it's a nice option to have. Also, as darkamikaze mentioned, some people don't want the gingerbread theme stuff. I'm working to get this as close to a stock flash as possible, deodexed, with the basic tweaks and functionality addons that everyone can use without changing too much of the phone functionality.
Is this an update the the ones release last week (redux v.02...)? If so can i just install over the redux v.01.7?
sirkao said:
Is this an update the the ones release last week (redux v.02...)? If so can i just install over the redux v.01.7?
Click to expand...
Click to collapse
No, the other Adeo versions are for the retail SBF (1.2.6) this is for the leaked SBF (1.5.2).
nice,, would like to try
Giving it a try. I haven't come close to flashing my Atrix as much as my Captivate yet.
GingerBlur is giving me some wicked battery life though.
Edit : Maybe some alt download links though. The http://goo.gl/5slwi is killing me.
CyanogenMod 10.1 working on the Archos 80 Cobalt!
This is oma7144's ROM, I've been able to get it running under a bit of guidace from oma and I thought I'd share it here if anyone else is interested.
The original thread is here - but this ROM is designed for Odys Genio tablet, which has basically the same specs as the 80 Cobalt. (RockChip 3066 chip)
As always, only flash if you know what you are doing, I am not responsible for anything you do or break.
New Version 1.3.4
Thanks danielo83 for putting this zip together
Oma CM10.1 v1.3.4
Battery problem fixed and ROM is now ready for daily use
- CWM 6.0.1.5 recovery
- System ext4
- Internal Storage 2,5 GB
- PhabletUI & Multiuser
- Device spoofed as Nexus
- Ethernet Support
- Init.d support
- USB-Hub enabled
- Gameloft compatible
- Gamepad (PS2, XBox, ...)
- Kernel modules (cifs, tun, lan, serial)
- latest hosts, su, su-binary, busybox
- MX Video-Player, Apollo & FX Sound
- Reboot Menue, CPU Tweaker, Pimp my Rom
- Dateimanager HD (Root)
- Trebuchet & Nova Launcher
Instructions
Before you do anything, download the file below and extract everything to your desktop, find 'Oma RK30 CM10.1 Format NAND.zip' and copy to your externalSD card
then unmount and remove the externalSD, this is very important because if you try to boot after flashing the rom, you will not have access to the internal SD - which means you can't flash files from CWM or do anything basically
Boot to bootloader
Turn off the tablet
Unplug from charger and USB
Hold the 'volume down' button and then hold the 'power button' to turn the device on and boot into bootloader, keep holding both until you see the boot screen
Connect USB and you will get "Unknown Device" message in windows
Install device drivers included in the zip below under x64 or x86 depending on your system - see gavroche's root thread if you are having trouble
Open up RKandroidTool.exe as administrator (located in RKDevelopTool_v1.35 folder)
- if you have trouble try different USB ports on your computer
You should see at the bottom of the RKAndroidTool "Found RK Android Loader Rock USB"
Click 'erase IDB' button - this will only take a few seconds
Now click 'Run' button, this will take a few minutes to install the ROM
Insert your external SD card
The device will boot into CWM, now choose install zip from sdcard (not internal), install Oma RK30 CM10.1 Format NAND.zip that you copied to your external SD earlier
Reboot, and enjoy CM10.1
--------------------------------------------------------
Downloads
http://www.mediafire.com/download/15wh4o4xwhec11o/OMA_4.2.2_CM10.1_Rom.zip
--------------------------------------------------------
What is working
Wifi
Camera
Display
Touchscreen
Battery info showing
...everything apart from mentioned below
Known Problems -
Scren flicker when rotating screen,
When battery is low the tablet wont wake up from sleep and the power button will only reboot it instead of waking it up
- Thanks to danielolsman
- To "fix" this you could install "no sleep" from the play store.
--------------------------------------------------------
If anyone is interested in helping get rid of these three problems please don't be shy.
I'm not a dev and I'm looking at fixing the bugs but don't really know where to start...
Credits
oma7144, gavroche
kage00,
Thanks for your effort!!! You're breathing new life into our tablets. We (I am sure there's a very big community alongwith me) who have been waiting for this.
I don't have my cobalt with me right now but will try and install at some point and feedback how it goes.
Are you also willing to work actively on issues and improvements. I am happy to help wherever I can. Perhaps, others will join in as well.
Thanks
Looking at the forum feedback from HUKD, the rom is not far from being a stable rom for day to day use. I see following general issues raised with this rom so far
1. Waking up issues after deep sleep in case when the battery is low
2. Rotation issues
3. Default language
4. Nexus port and therefore certain apps incompatibility
As mentioned earlier, I am happy to help wherever I can.
Thanks
Hey nikunj87,
Thanks for your support! I would love to be able to work on the issues with this rom but to be honest, I'm not a dev, not even close, and I wouldn't even know where to begin to start fixing the problems.
For the moment I'm looking at putting together a kernel from Archos' source and adding overclocking, I've never built a kernel before so it's a learning curve... don't hold your breath, haha!
I just thought I'd post this rom here to see if we could get some interest in the project and maybe get a dev's (or two's) attention to take a look at the problems, but for the moment it's just you and me who are interested in this..
I think the best we can do is wait for an update to this rom from Oma (the original dev), as you mentioned all the problems with this rom on the cobalt are problems that exist with the same rom on other devices. So maybe with a new update it will work a bit better.
Unless if we can get someone else who knows what they are doing to take a look at it...
kage00 said:
Hey nikunj87,
Thanks for your support! I would love to be able to work on the issues with this rom but to be honest, I'm not a dev, not even close, and I wouldn't even know where to begin to start fixing the problems.
For the moment I'm looking at putting together a kernel from Archos' source and adding overclocking, I've never built a kernel before so it's a learning curve... don't hold your breath, haha!
I just thought I'd post this rom here to see if we could get some interest in the project and maybe get a dev's (or two's) attention to take a look at the problems, but for the moment it's just you and me who are interested in this..
I think the best we can do is wait for an update to this rom from Oma (the original dev), as you mentioned all the problems with this rom on the cobalt are problems that exist with the same rom on other devices. So maybe with a new update it will work a bit better.
Unless if we can get someone else who knows what they are doing to take a look at it...
Click to expand...
Click to collapse
willing to lend a hand tho I am only new to this stuff as well!
I tried this ROM, it seems that OMA posted an AKKU Fix here
I will trie it soon....
There are some problems with the camera; its inverted. The provides fix did not solve the problem, does someone know how to fix it ?
Akku fix does not work
Sent from my Nexus 4 using xda app-developers app
Cool! looks like we've got some attention from the devs!
So there is a new version of this ROM over at this thread
edit ----> please take note, if anyone tests this ROM you will need to keep the same kernel from the existing package in OP and use that to flash with new ROM, Otherwise you risk having a bricked device
Aparently the battery problem exists, but netlars has a possible fix on this thread if anyone can test it that would be great. My tablet is off getting fixed, I had some problems with the touchscreen.
Also Oma was asking if anyone could test this too
Are these paths there?
/sys/devices/platform/rk30-battery/startget
/sys/class/rk30_battery/rk30_battery_start_timer_work
Click to expand...
Click to collapse
If anyone can test and reply here please, then I can tell him on the other thread.
Thanks
Battery problem is solved (see original thread)
CM10.1 is now ready for daily use.
(@Kage00: maybe its possible for you to make a new zip package with the new boot image found here?)
EDIT:
made a zip package myself : CrewRKTablets_RK30_Cobalt 80 by Oma_CM10.1_v1.3.4.zip
Thanks danielo83,
Nice one, I'll update the OP,
I got news back from Archos repair about my tablet / touchscreen problem. They decided to replace the whole unit, so I'm going to sell the brand new one and get a Nexus 7, which means I won't be able to play around with this ROM anymore becuase I won't have the tablet. I'm happy to still keep the thread open and you guys can tell me if there's anything to update in the OP
Thanks
edit----------
In the new version do you still have the screen flicker artifacts on rotate?
danielo83 said:
Battery problem is solved (see original thread)
CM10.1 is now ready for daily use.
(@Kage00: maybe its possible for you to make a new zip package with the new boot image found here?)
EDIT:
made a zip package myself : CrewRKTablets_RK30_Cobalt 80 by Oma_CM10.1_v1.3.4.zip
Click to expand...
Click to collapse
Not sure if anyone will see this but I own an unrooted/untouched Archos 80 Cobalt which I haven't used for months. Decided to dig it out for my son to play with but I can hardly fit any apps on it so looking in to alternative roms.
Came across this rom which I want to flash but I'm unsure on how to start. Do I have to root and flash CWM on to the tablet before doing anything in this thread or are the instructions in this thread all that I need to do in order to flash this rom on to an unaltered tablet?
Yes you will need to be rooted first before using this ROM, please follow this thread to get root and CWM on your tablet then you can flash this ROM with the instructions in the OP
Yeah the storage space is limited for some stupid reason on the stock ROMs, that shouldn't be a problem on this ROM, also if you find you dont like this ROM there is also another custom ROM here based on stock 4.0.4 firmware with better app storage space
the new version still has the rotate "problem".
Sent from my Nexus 4 using xda app-developers app
I just wanted to say as well, that Archos have released kernel sources (downloadable from their website) that are from May or June 2013 from memory. The last stock ROM built for this device was released in February 2013. Which means if anyone wants to try their hand at compiling the kernel from Archos source, it would be a newer kernel than what you are using now and it could possibly fix any left over problems with this ROM. I don't have any spare time to do it anymore, but if anyone was interested I'm sure you could find a walkthrough on XDA to tell you how to do it easily enough.
The kernel for this ROM at the moment is still the stock kernel from the stock 4.0.4 ROM, which is working, but maybe if a newer kernel was made from the sources it may work a lot better
app space and vold.fstab
Does anyone know if this ROM exists with 6gb of app space? I currently have the supersport ROM with 6gb app space and edited the vold.fstab to swap the internal and external sd cards. I’d like to do the same with this JB ROM.
How difficult would it be to edit the ROM to change the app space?
Does this ROM use the vold.fstab to set where the internal and external sd cards are mounted? (I think this has been changed in JB 4.3 but I’m not sure about 4.2.2)
Cheers, T
To be honest I'm not sure if it is possible, but you could ask the devs who made the ROM they would probably be able to tell you if it was possible or not. Have a look over at http://www.arctablet.com
You'd need to ask oma7144 or netlars
You could try to post in this thread and see what they say
kage00 said:
Yes you will need to be rooted first before using this ROM, please follow this thread to get root and CWM on your tablet then you can flash this ROM with the instructions in the OP
Yeah the storage space is limited for some stupid reason on the stock ROMs, that shouldn't be a problem on this ROM, also if you find you dont like this ROM there is also another custom ROM here based on stock 4.0.4 firmware with better app storage space
Click to expand...
Click to collapse
Can you please tell me why I'm getting this error when trying to follow the root instructions from?
http://forum.xda-developers.com/showthread.php?t=2066972
{
"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"
}
I'm using Windows 8.1 64 bit
I'm doing this with USB debugging enabled and the device switched on as this is the only way I can get the 'ARCHOS' device to show in Device Manager under 'Other Devices.
If I put the tablet in to download mode (power + vol down) I get a dead Android symbol with red exclamation, is this normal? However when I insert USB cable in to the device at this point my computer doesn't bring up the 'ARCHOS' device in Device Manager...
All I get then is this:
I don't actually have this tablet anymore, but I remember mine being a bit strange when I first tried to root it too. It can be a bit temperamental... I remember reading someone saying somewhere about leaving the charger plugged in when trying to reboot into download or recovery mode, if that doesn't work try with the USB cable (or both) plugged in while you try.
I also remember with mine I had to direct windows to the specific driver folder extracted from the zip based on which drivers you need, eg, x86 or x64 etc.
You could also look at this thread http://www.freaktab.com/showthread.php?3244-Archos-80-Cobalt-900-supersport-rom where the might be more info on root.
I'm using windows 7 though, so I don't know exactly what differences there are with win 8.
If all else fails just keep searching and reading all/any forums you can find about rooting the thing, I'm sure you'll find that someone has had the same or similar problem
good luck
kage00 said:
I don't actually have this tablet anymore, but I remember mine being a bit strange when I first tried to root it too. It can be a bit temperamental... I remember reading someone saying somewhere about leaving the charger plugged in when trying to reboot into download or recovery mode, if that doesn't work try with the USB cable (or both) plugged in while you try.
I also remember with mine I had to direct windows to the specific driver folder extracted from the zip based on which drivers you need, eg, x86 or x64 etc.
You could also look at this thread http://www.freaktab.com/showthread.php?3244-Archos-80-Cobalt-900-supersport-rom where the might be more info on root.
I'm using windows 7 though, so I don't know exactly what differences there are with win 8.
If all else fails just keep searching and reading all/any forums you can find about rooting the thing, I'm sure you'll find that someone has had the same or similar problem
good luck
Click to expand...
Click to collapse
Hi do you have any idea how to get XBMC working with this rom? XBMC just goes back to home screen whenever i try launching it?
For xbmc you will need an older version of it. The one from August seemed to be the one to use for most people with the same issues on the HP slate 7 so am guessing it will sort your issue too. A quick search on Google should locate the archives for you
Sent from my ARCHOS 80G9 using Tapatalk
Credits:
Original version created in the summer of 2011. Thanks to birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch!
Special thanks to tiny4579 and ghul21 for testing on the OnePlus One!
Thanks to SDX
Requires:
Unlocked bootloader (shouldn't be a concern here!) and root access!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY select Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into a kernel /sbin directory, included in custom ROMs, etc).
Description:
This android application, FlashImageGUI, is a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: OnePlus One, HTC One M8 (GSM), Moto G, Sprint Galaxy S4, International HTC One (M7), T-Mobile HTC One (M7), Sprint HTC One (M7), HTC EVO 4G LTE, HTC One S, HTC EVO 3D CDMA and GSM, HTC One XL, HTC Droid DNA, HTC Amaze, HTC Vivid/Holiday, HTC EVO 4G, HTC EVO Shift, Google Nexus 5, Google Nexus 4, Google Nexus 10, Google Nexus 7, Samsung Google Galaxy Nexus, Nexus S/Nexus S 4G & LG Optimus
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
Let me know if there are any issues. Feel free to post the encountered issue and a link to the exact file that was flashed. Thanks for the support!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No.
Q: Can I flash nandroid kernel backups?
A: Yes. Rename the specific image to boot.img and select from inside of Flash Image GUI. **Make sure to also load the associated modules or WiFi might stop working!
Screenshots:
{
"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"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
Users Guide for flashing ONLY a Kernel (zip file):
1) Ensure the bootloader is unlocked and root access is properly setup
2) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
3) Download kernel zip file to /sdcard.
4) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
5) Flash Image GUI will validate that the kernel zip file contains the minimum required files
6) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
7) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel itself or the ramdisk packaged in the kernel is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot (or directly into the custom recovery) and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.
Completely surprised your thanks meter is not higher than what it is for the length of time you been helping out with your apps up in here. If I remember right you go way back to the winmo days right?
Thx for your app and allow me to be the first to thank you in the 1+ section :good:
playya said:
Completely surprised your thanks meter is not higher than what it is for the length of time you been helping out with your apps up in here. If I remember right you go way back to the winmo days right?
Thx for your app and allow me to be the first to thank you in the 1+ section :good:
Click to expand...
Click to collapse
I have been around a long while, and spent more time on here before the thanks meter was added (Dec 2010).
I appreciate the support and feel free to provide feedback as I'm always interested in improving!
Quick question, how does this app differ from one like Flashify? Is it another alternative?
Don't get me wrong, I'm all for lots of new development and different alternatives, just trying to understand if this app provides something different (or at least does it better) than some other similar apps.
Thanks!
pinoymutt said:
Quick question, how does this app differ from one like Flashify? Is it another alternative?
Don't get me wrong, I'm all for lots of new development and different alternatives, just trying to understand if this app provides something different (or at least does it better) than some other similar apps.
Thanks!
Click to expand...
Click to collapse
I can't speak to Flashify, other than it didn't exist when I created Flash Image GUI ~3 years ago. I'm also unsure about their business model, whether they're free and charge for usage or whether they charge for the app.
Either way, I host a free copy of Flash Image GUI for XDA users and do my best to monitor this thread for any issues, concerns, or bugs, as I've done for around 30 devices over the last three years!
Thanks for your support!
Nice to see you around here @joeykrim! I still have my Moment around here somewhere running something crazy from SDX.
Hi joeykrim
Nice to see you start a thread in here
Some time ago i post you an email to support Oneplus One and we made some tests
thx for the app and finaly full support for OPO on XDA. Glad it finally work for "all" of my devices
One more time THX for amazing app
Regards
Marcin :highfive:
ghul21 said:
Hi joeykrim
Nice to see you start a thread in here
Some time ago i post you an email to support Oneplus One and we made some tests
thx for the app and finaly full support for OPO on XDA. Glad it finally work for "all" of my devices
One more time THX for amazing app
Regards
Marcin :highfive:
Click to expand...
Click to collapse
Yes, I appreciated you reaching out and requesting support, plus spending time testing as I added support. I've added your XDA name to the credits at the top. Thanks again for your help!
Thanx for adding support for opo, but could you make recognize the "any kernel" zip files as it does not contain img's.several kernel dev's are using this method nowadays,so their kernel is compatible across all rom's..
zodiaxe66 said:
Thanx for adding support for opo, but could you make recognize the "any kernel" zip files as it does not contain img's.several kernel dev's are using this method nowadays,so their kernel is compatible across all rom's..
Click to expand...
Click to collapse
I do support the method on devices where the kernel devs follow common and standard usage of the anykernel method, but didn't see this on the OPO a few weeks back.
Can you provide links to the specific kernels on the OPO that are using this method? When I checked a few weeks back, there was only one and they were using an unusual variation of the anykernel method that I hadn't seen on any other device before.
Thanks for your support!
joeykrim said:
I do support the method on devices where the kernel devs follow common and standard usage of the anykernel method, but didn't see this on the OPO a few weeks back.
Can you provide links to the specific kernels on the OPO that are using this method? When I checked a few weeks back, there was only one and they were using an unusual variation of the anykernel method that I hadn't seen on any other device before.
Thanks for your support!
Click to expand...
Click to collapse
Here you go and thanx
Ups my link in gone
Posting it later when i'm home..it's AK kerne by AK in original Android dev
http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
EDIT: heres a screenshot of chosen kernel I tried to flash. Your app doesn't recognize the zImage..
Device not supported?
zodiaxe66 said:
Here you go and thanx
Ups my link in gone
Posting it later when i'm home..it's AK kerne by AK in original Android dev
http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
EDIT: heres a screenshot of chosen kernel I tried to flash. Your app doesn't recognize the zImage..
Click to expand...
Click to collapse
The link is helpful and that was the one kernel using the "AnyKernel" method but in a less common manner that I'm hesitant about adding support for. I appreciate the request and can investigate it further but at this point, that one kernel likely won't be a high priority unless many other people request it, mostly due to the less common manner it uses to load. I view there be additional risk to adding less common loading methods in that I don't want to damage any devices using less proven methods. Given that I don't own the device myself, I'm also less likely to ask testers to risk using a less common loading method to test support.
lqdcat said:
Device not supported?
Click to expand...
Click to collapse
The screenshot is very helpful and ironically shows that this is the kernel, quoted above, that I'm hesitant to add flashing support to as it uses less common methods of loading. It seems that either the kernel or the ROM changes how the device identifies itself and breaks compatibility with Flash Image GUI. Which ROM are you using?
While you're still using that kernel and ROM combination, can you share the output from the following adb shell command? adb shell getprop ro.product.device
joeykrim said:
The link is helpful and that was the one kernel using the "AnyKernel" method but in a less common manner that I'm hesitant about adding support for. I appreciate the request and can investigate it further but at this point, that one kernel likely won't be a high priority unless many other people request it, mostly due to the less common manner it uses to load. I view there be additional risk to adding less common loading methods in that I don't want to damage any devices using less proven methods. Given that I don't own the device myself, I'm also less likely to ask testers to risk using a less common loading method to test support.
The screenshot is very helpful and ironically shows that this is the kernel, quoted above, that I'm hesitant to add flashing support to as it uses less common methods of loading. It seems that either the kernel or the ROM changes how the device identifies itself and breaks compatibility with Flash Image GUI. Which ROM are you using?
While you're still using that kernel and ROM combination, can you share the output from the following adb shell command? adb shell getprop ro.product.device
Click to expand...
Click to collapse
Okay I understand, Thanx for your response and to clear things up.
PS. I have no problem with my opo getting recognized, so apparently it's as you pointed out, only the one kernel, sadly, but there are many other ways to flash it, so no worries.. :highfive:
it took about 2 seconds to flash a new recovery.img
Excellent
Thank you very much!!
*******MAY 2016 UPDATE
Android Pay is working on the PureNexus May 2016 layers build
To attain this, delete the following files
com.google.android.camera2.xml
Located in system/etc/permissions
And
com.google.android.camera2.jar
Located in system/framework
*******BEGIN PRELIMINARY NOTES*******
-->To go from system root to systemless root,
please use the SuperSU Uninstaller zip linked below and not the unroot feature built into the SuperSU app
-->To fully unroot if on systemless root or system root, use the unroot feature in the apk
*******END PRELIMINARY NOTES*******
If, like me, you've become increasingly desirous of having Android Pay functioning on your rooted device, yet preserving that which you love about your custom setup (see thread title), this thread attempts to provide the resources you need to attain your objective.
For me, I believe that the tipping point came as a matter of principle...I wanted a feature from which I'll likely derive zero utility.
Let me be clear: I see no use whatsoever for Android Pay, and yet, like most Americans, I absolutely must have it.
I found myself returning to the same excuse, "I have a debit card, why do I even want this goofy feature?" That's a good question, but the answer is equally obvious...because it exists.
And I'd see yet another user getting the bloody thing to work on a rooted, custom rom. I hope you can see the urgency.
Just like the one ring to rule them all, the lure of Android Pay is really due to its power that it holds over us...
We Wants It...Stupid HOBBITSES
Many users have grown weary of wading through...
-->Disparate posts within rom threads
-->Dedicated threads for various elements of in the title of this thread, now scattered across xda like the diaspora of a lost tribe (how many Viper4android threads are there?)
-->Posts cross-linked within other threads for a given feature
My reticence would again solidify every time I read another post or series of posts about the precise means a given user went about obtaining Android Pay, and the commensurate loss of a different feature...or, no mention of a feature about which I cared.
So this thread is an attempt to redress these issues; specifically, after reading this, you should be able to have...
1.1-1.5. Systemless Root - If Using System Root
1.6. Updating Systemless Root Versions
2. Properly Themed Apps
2a. Hard-coded themed apps
2b. Theme Ready Google Apps
3. Layers
4. Viper4android that does not break your AUX jack or Chromecast
5. Busybox
6. Android Pay
1. Systemless Root
Whether you are running stock, or one of the few AOSP roms claiming to have Android Pay functioning on your device, this is your first step
If you are running a rooted rom, installing a pre-rooted rom, or want to flash a rom that is pre-rooted, to attain Systemless Root, you'll need the following resources...
1.1. The Latest Systemless SuperSU Zip (scroll to the bottom
http://forum.xda-developers.com/showpost.php?p=64161125
1.2. System Root Removal Tool /unSU
http://forum.xda-developers.com/showpost.php?p=63615067
1.3. Busybox for All Devices (scroll down to the section labeled "Busybox Installer")
http://forum.xda-developers.com/showthread.php?t=2239421
1.4. These Two Terminal Commands (have them in a notepad file, on your computer, or just, literally written down on a piece of paper)
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
1.5. To Install Systemless Root
1.5.1. Boot into Recovery
1.5.2. Install Pre-Rooted Rom + Gapps if Needed
1.5.3. Flash unSU Zip
1.5.4. Go to TWRP Main Menu, Go to Advanced, Terminal Command, type each command exactly as above, one at a time), hitting return in between each line
***you'll only do this once if you plan on staying on systemless root
1.5.5. Flash Systemless Root Zip
1.5.6. Flash Busybox Zip
1.5.7. Flash Custom Kernel if Desired
1.5.8. Fix Folder Permissions
-->Boot your device
-->Using Root Explorer or similar app, navigate to the folder labeled "su," as below...
{
"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"
}
-->Then hard press on the folder labeled "bin" and select the pop-up option for permissions, so below...
-->Set permissions to 0751, or deselect the check boxes as below...
1.5.8. Keep Reading, or...
Boot to System if This Is All You Want
1.6. Updating Systemless Root Versions
If you're already running Systemless Root and wish to upgrade to the latest version, follow these steps...
1.6.1. Flash latest version of SuperSU
1.6.2. Flash custom kernel if desired
***Note that if you omit the second step above, and wish to stay on a stock, no force encryption kernel (like one that ships with PureNexus), there is no need to reflash the kernel that came pre-installed with your rom. Just flash the latest version of Systemless Root.
2. Viper4android
2.1. Grab a Zip from the Viper4android Atmos Thread Here (some recommend the Viper4android Atmos Sony Beats Edition...so why the heck not?)...
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
2.2. Flash in Recovery
3. Properly Themed Apps
If one wants properly themed apps, and since the Gapps packages that allow working Android Pay are minimal, one must add them
3.1. Hard Coded Themed Apps
Using the Team BlackOut Updater (linked below), download those you want and flash in recovery...make sure to grant the app write permissions to your internal SD storage
http://bit.ly/1OcThZg
3.1.1. Download the Gapps that you want, flash in recovery
3.2. Theme Ready Google Apps
Go to this thread, download what you want...
http://forum.xda-developers.com/android/apps-games/apps-themeable-hangouts-layers-cmte-t3113192
3.2.1. Flash is recovery
3.3. All At Once in TWRP, in Sequence
You can and should flash all of these one after the other in TWRP...here are a few reasons why...
3.3.1. If you're using Gmail, and the minimal Gapps doesn't include it, you'll now have it waiting for you upon boot
3.3.2. If you've got a ton of downloaded music from Google Music, it'll still be there waiting for you if you flash Google Music during install (ie, you'll not have to download all of your music again)
3.3.3. Do you really want to set up hangouts, Google Plus (I turn off notifications and sync for this app...why do that every bloody time...), etc?
3.5. Layers
3.5.1. Install the latest version of the layers manager, and install whatever layers your want
3.6. Busybox That Works
You've already done that
3.7. Android Pay
3.7.1. Download from the Play Store, Add Cards
3.7.2. Note that not all cards will work...it's not the fault of the tools you've been given on this site...it's symptomatic of the reality that none of your cards is issued by participating Android Pay partners
4. Test Android Pay
4.1. You can download SafetyNet Helper Sample from the Play Store...
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
The app is temperamental, and can throw up a false negative...but you will get a positive result most all of the time
4.2. Buy a dang soda, pack of gum at CVS, some cheap gift from Walgreens...I don't care from where...to see if it works (it should)
5. Odds & Ends
A few items of note...
5.1. All of your previously apps granted root permission will need so again
5.2. Stay on top of themed apps...layers can never properly theme certain apps if there's a stock version in the data partition of your device.
5.3. Thank all of the devs whose tools are linked in this thread, donate to them, and be sure to buy anything that they may have for sale...they are the best in class.
5.4. Many things may or definitely will break Android Pay, even if you've set it up properly, including Xposed, theme engine, some DPI changing apps, etc. Just be mindful that this could change if you install other items.
6. Credits
@nathanchance, for being such a good dude
@inffy, for being helpful at all times, while maintaining near pitch-perfect, subtle venom
@osm0sis, for just everything he has provided
@BeansTown106, for building his rom, and not just stumbling but actually figuring out what prevented Android Pay from working on his rom
@daveyannihilation, for being such a great guy, themer, forum moderator, and finest pineapple lover I've ever encountered
@Woody, for having done the heavy lifting on most all of this prior to me
Chainfire
Viewers like you that contribute to Public Television...thanks for your support
Good luck!
Solid work! Gonna add it to my signature and I will add it to my posts as soon as I can.
Great post, and thanks for the mention!
Venom indeed flings in my veins
Thanks for posting this. Curious what everyone is using in terms of Viper Audio? I just flashed the Huawei one for now.
Subiegsr said:
Thanks for posting this. Curious what everyone is using in terms of Viper Audio? I just flashed the Huawei one for now.
Click to expand...
Click to collapse
I am using the all-in-one package by @guitardedhero
Please link to my thread, not my zip. Thanks.
osm0sis said:
Please link to my thread, not my zip. Thanks.
Click to expand...
Click to collapse
Yes sir...taken care of it.
My apologies.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Awesome Post. Really covers everything that has been asked over and over, all in one easy to read format.
On Viper: In my testing, I made several backups at each stage after I checked that AP was working. I am glad that I did, as some Viper packages break Pay functionality. I would stress caution and/or patience when flashing, as a backup only takes a few seconds to make, but can save a whole bunch of time. The Viper package that I have linked above is an older one from the N6-Proper device, so it requires Permissive. You are free to use whatever you want, but this works for me. I flashed XTREMEmusic 6.0, 6.2 and 7.3 and all 3 broke Pay. It has been noted that Guitaredhero's zip package works, doesn't break Pay and sounds pretty good. Your choice.
Me from another thread said:
As an aside, I have an almost completely stripped down /system partition as far as gapps go and have even substituted several TBO ThemeReady versions, as well as Clear YouTube. So if I were to put a wager on what trips the Pay failure [I am speaking in systemless root terms], I would lay bets on system/bin, /system/xbin, busybox configurations and changes to some shadow policy that no one has figured out. Because simply adding or removing apks from /system (not including any signature checked apks such as a modified GMusic or Chrome) and utilizing the /su folder correctly doesn't trip the Pay verification, at least not for me.
Click to expand...
Click to collapse
Thanks
Bookmarked in my tips folder.
I'm sure I'll refer to it many times.
viper4android link is down
Sent from my Nexus 6P using Tapatalk
Most excellent! U Rock on XDA!!
galaxys said:
Most excellent! U Rock on XDA!!
Click to expand...
Click to collapse
For so long you've had the Oregon Ducks cheerleaders in your signature. Good to see your "affection" for the cheer spans to other schools.
Woody said:
For so long you've had the Oregon Ducks cheerleaders in your signature. Good to see your "affection" for the cheer spans to other schools.
Click to expand...
Click to collapse
This is true...LOL! I'll continue to scout the teams!
galaxys said:
This is true...LOL! I'll continue to scout the teams!
Click to expand...
Click to collapse
Sometimes looking at the forums via browser really has its advantages.
I'm so glad I looked at this exchange...I'm quite thankful for those cheerleaders...they really want me to have my device exactly as I like it.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Woody said:
Awesome Post. Really covers everything that has been asked over and over, all in one easy to read format.
On Viper: In my testing, I made several backups at each stage after I checked that AP was working. I am glad that I did, as some Viper packages break Pay functionality. I would stress caution and/or patience when flashing, as a backup only takes a few seconds to make, but can save a whole bunch of time. The Viper package that I have linked above is an older one from the N6-Proper device, so it requires Permissive. You are free to use whatever you want, but this works for me. I flashed XTREMEmusic 6.0, 6.2 and 7.3 and all 3 broke Pay. It has been noted that Guitaredhero's zip package works, doesn't break Pay and sounds pretty good. Your choice.
Click to expand...
Click to collapse
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
luigidk said:
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
Click to expand...
Click to collapse
Thanks for your input, and sharing your personal experience. This kind of feedback is especially helpful.
As to removing Busybox from the list, at the moment, many Viper4android packages are compatible with Android Pay, and require Busybox...for example, even though I linked one that seems pretty popular, others work, and folks may need Busybox in order to use certain Viper4android packages.
As to the new Layers Manager not requiring Busybox, I'll definitely note that once the app goes from alpha stage to final release.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
luigidk said:
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
Click to expand...
Click to collapse
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
micmars said:
Thanks for your input, and sharing your personal experience. This kind of feedback is especially helpful.
As to removing Busybox from the list, at the moment, many Viper4android packages are compatible with Android Pay, and require Busybox...for example, even though I linked one that seems pretty popular, others work, and folks may need Busybox in order to use certain Viper4android packages.
As to the new Layers Manager not requiring Busybox, I'll definitely note that once the app goes from alpha stage to final release.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
The V4A package at this forum: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137 doesn't require busybox, so that is just an option. Best V4A install out there in my opinion.
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
darkjedi said:
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
For V4A? If so it is here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
darkjedi said:
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The links in the OP all work for me...
http://forum.xda-developers.com/showthread.php?t=2952137
ViPER|Audio || ViPER|Atmos 4.1 * SQ Driver * Audiophile Profile * Beats * Huawei *
They are direct downloads at the bottom of the OP...
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
luigidk said:
The V4A package at this forum: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137 doesn't require busybox, so that is just an option. Best V4A install out there in my opinion.
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
For V4A? If so it is here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
Click to expand...
Click to collapse
Excellent...I'll add this to the OP, along with the one provided by Woody.
Do you mind telling me...
1. The rom you're running
2. The kernel you're on
3. If you're SELinux is set to permissive or enforcing
Many thanks.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression