Problems turning on phone after flashing xposed framework. - Xposed General

Hello.
My phone is a SM-G903F with an android version of 6.0.1 and with an architecture of armeabi-v7a.
After flashing the xposed-v76-sdk23-arm.zip into my phone using TWRP (I also tried newer versions of the xposed framework) I end up getting a blue light and the samsung logo breathing constantly in a loop.
I can flash the xposed unistaller zip using the TWRP in the recovery mode and the phone works okay. But I would like to be able to install the xposed framework and make it work.
Can anyone help me or suggest anything I can do?
Thank you very much for your time,
Enrique

Try latest v86. It should works....

Samsung devices running TouchWiz have a tendency to bootloop when installing Rovo89's version of Xposed because it is developed for AOSP/Google Edition ROM's and their respective version of ART, whereas Samsung has made several changes in 5.0/5.1 that put it's functionality and code structure somewhere between 5.0/5.1 & 6.0, Vanilla Xposed v86 will likely not solve this issue, instead try flashing arter97's Xposed v79 (or v85 if you prefer, however I have not tested that version) of Xposed for Deodexed TouchWiz ROMs running on 5.0/5.1 (API21/22). If you are running 6.0 (API23) I am fairly certain you are out of luck as I don't believe a version of Xposed for TouchWiz 6.0 exists yet.

tiaxdaun said:
Samsung devices running TouchWiz have a tendency to bootloop when installing Rovo89's version of Xposed because it is developed for AOSP/Google Edition ROM's and their respective version of ART, whereas Samsung has made several changes in 5.0/5.1 that put it's functionality and code structure somewhere between 5.0/5.1 & 6.0, Vanilla Xposed v86 will likely not solve this issue, instead try flashing arter97's Xposed v79 (or v85 if you prefer, however I have not tested that version) of Xposed for Deodexed TouchWiz ROMs running on 5.0/5.1 (API21/22). If you are running 6.0 (API23) I am fairly certain you are out of luck as I don't believe a version of Xposed for TouchWiz 6.0 exists yet.
Click to expand...
Click to collapse
Hello.
I'm going to try these solutions and I will inform here on any feedback. Thank you very much!
Enrique

Just to expand on this
Arter xPosed for 5.0.x
Wanam xPosed for 5.1 and (yes) 6.0'x so you want a deodexed ROM and wanam's build of xPosed

Nergal di Cuthah said:
Just to expand on this
Arter xPosed for 5.0.x
Wanam xPosed for 5.1 and (yes) 6.0'x so you want a deodexed ROM and wanam's build of xPosed
Click to expand...
Click to collapse
I apologize but I didn't understand your answer. I have 6.0, so I must use 'wanam's build of xPosed' but what is a 'deodexed ROM' ?
Thank you and sorry but I'm new here.
Enrique

Go to your device's board and search deodex (odex is a android function that creates executables out of app files)
Read this
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
It's not so important to understand the hows of it, you just need to find a ROM (there are many) that is deodexed. There are likely even a few completely stock touchwiz which have been deodexed. You should go to the XDA board for your device and should be able to find a working ROM

When a ROM is Odexed it means that a system application's cache files will be compressed in a separate odex file, so /system/priv-app/Email/Email.apk would also be accompanied by Email.odex in the same folder. The advantage of this was back when the Dalvik interpreter was used, it would speed up boot times. Deodexed on the other hand is the opposite, it stored the cache files inside an application's APK file, so Email cache would be in Email.apk/cache/com/google/android/Email.dex. Again back when the Dalvik interpreter was used this would slow down boot times significantly. However I believe that since ART became the new runtime the only time boot is slowed down is the very first one after a ROM is installed (albeit by about 15 minutes). If you aren't familiar with modifying ROMs (assuming you want to keep TouchWiz) I would recommend finding a Stock TouchWiz ROM that comes Deodexed, and pre-rooted with SuperSU already installed, make sure you backed up your data (either through google or manually) and install the Deodexed TouchWiz ROM, wait a while, as I said first boot with Deodexed ROMs are about 15 minutes slower than normal, and restore your data. After that you should be good to install Xposed for TouchWiz (beit Wanam or Arter97's is dependent on your OS version and what recovery you're using.) ?

just a question i got the same problem but i flashed my s6 with TYRANNUS ROM v28.1 and keep getting a bootloop when i try to flash xposed-v86-sdk23-arm64
Recovery is twrp-3.0.2-1-zeroflte
I did all the same like in the tutorial shown
and i dont know why can someone help me ? just want that xposed framework works and im stucking since hours of trying :/

As I mentioned before if you are running TouchWiz 5.0/5.1 you will have to use Arter97's Xposed for TouchWiz v79, API 21 if 5.0, API 22 if 5.1, Wanam Xposed for TouchWiz v79, API 23 if 6.0. ROM has to be Deodexed either way, use FlashFire version 0.24+ if flashing Arter97's Xposed, use TWRP 2.8.4.0+ if Wanam Xposed. Do keep in mind Rovo89's Xposed will not work with TouchWiz on 5.0+, you will have to use one of the above two alternatives.

tiaxdaun said:
... I would recommend finding a Stock TouchWiz ROM that comes Deodexed, and pre-rooted with SuperSU already installed ...
Click to expand...
Click to collapse
Would you have any suggestions on where I can find ROMs like that? Is there a main thread or a portal somewhere that lists all the popular ones?
And I have another side question if you don't mind me asking: The device I'm playing around with is a Canadian Galaxy S4 [SGH-I337M], does that mean the ROM I use needs to be compatible with that model specifically? Or are ROMs inconsiderate of the exact model and would work on all Galaxy S4's?
(There's also the different processor issue that depends on the S4's model; Snapdragon 600 vs. Exynos 5 Octa).
Thanks for the descriptive difference between the odexed and deodexed btw, yours is the best I've read so far

RaniKheir said:
Canadian Galaxy S4 [SGH-I337M],
Click to expand...
Click to collapse
Start here
http://forum.xda-developers.com/galaxy-s4-att

Nergal di Cuthah said:
Start here
http://forum.xda-developers.com/galaxy-s4-att
Click to expand...
Click to collapse
Hmmm, seemed a bit off at first since I see the American AT&T everywhere, but then I noticed the thread [SGH-I337M] CF-Auto-Root there and realized the I337 and I337M models are put together.
So I see ROMs under all of the following:
AT&T SAMSUNG GALAXY S 4 ANDROID DEVELOPMENT
AT&T SAMSUNG GALAXY S 4 ORIGINAL ANDROID DEVELOPMENT
SAMSUNG GALAXY S 4 UNIFIED DEVELOPMENT
Does that mean there's no main thread which keeps track of all the popular ROMs?
Also, since you linked me to that portal, does that also mean (for my second question) that the ROMs need to be designed for a specific model? It's not generic that any S4 can use any ROM designed for S4?
Thanks!

RaniKheir said:
Hmmm, seemed a bit off at first since I see the American AT&T everywhere, but then I noticed the thread [SGH-I337M] CF-Auto-Root there and realized the I337 and I337M models are put together.
So I see ROMs under all of the following:
AT&T SAMSUNG GALAXY S 4 ANDROID DEVELOPMENT
AT&T SAMSUNG GALAXY S 4 ORIGINAL ANDROID DEVELOPMENT
SAMSUNG GALAXY S 4 UNIFIED DEVELOPMENT
Does that mean there's no main thread which keeps track of all the popular ROMs?
Also, since you linked me to that portal, does that also mean (for my second question) that the ROMs need to be designed for a specific model? It's not generic that any S4 can use any ROM designed for S4?
Thanks!
Click to expand...
Click to collapse
Correct, as far as I remember the s4 was carrier dependent. My s4 for vzw was cdma only so only vzw roms/mods would have worked. Your device is GSM and Canadian GSM followed the AT&T device build (as far as I could tell). What I did was (on the XDA website) type I337 into device search and only that device shows. The name of that top board was AT&T, Canadian, Rogers thus it confirmed for me this was your phone. There is usually in one of those boards a curated index. There are dozens of ROMs, you just need to read, nobody here (worth a salt) will be able to just give you "the best" answer. You need to read, and understand what you are doing. If you do anything wrong, especially with Samsung touchwiz devices, you will void your warranty (samsungs have a hardware fuse that burns out if you Root or modify incorrectly) and could even hardbrick your phone. But if you just use search while in the forum I pointed to you should easily find what you need. (Hint, type xPosed into the searchbox on the website I should limit the search to your device's forum if you are already on the page I posted)
---------- Post added at 12:16 AM ---------- Previous post was at 12:10 AM ----------
Arrrgggg I promised myself not to spoon feed you but
http://forum.xda-developers.com/xposed/b-how-to-install-xposed-att-samsung-t3162866/post61985162
---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------
And here's an index http://forum.xda-developers.com/showthread.php?t=2616221&highlight=xposed
Please though learn from this then you too can help others
---------- Post added at 12:24 AM ---------- Previous post was at 12:19 AM ----------
And I understand it's not appealing to read 450+pages on threads but just skim through threads, 99 percent of problems you'll encounter will have been previously reported and likely solved. I lurked on XDA for at least a year before I spoke and read (at least topic titles of) every topic for both the devices I've had and read/subscribed to topics for every xPosed module I use.
Ok done preaching....sorry

Nergal di Cuthah said:
Correct, as far as I remember the s4 was carrier dependent. My s4 for vzw was cdma only so only vzw roms/mods would have worked. Your device is GSM and Canadian GSM followed the AT&T device build (as far as I could tell). What I did was (on the XDA website) type I337 into device search and only that device shows. The name of that top board was AT&T, Canadian, Rogers thus it confirmed for me this was your phone. There is usually in one of those boards a curated index. There are dozens of ROMs, you just need to read, nobody here (worth a salt) will be able to just give you "the best" answer. You need to read, and understand what you are doing. If you do anything wrong, especially with Samsung touchwiz devices, you will void your warranty (samsungs have a hardware fuse that burns out if you Root or modify incorrectly) and could even hardbrick your phone. But if you just use search while in the forum I pointed to you should easily find what you need. (Hint, type xPosed into the searchbox on the website I should limit the search to your device's forum if you are already on the page I posted)
Click to expand...
Click to collapse
I'm not looking for the "best" answer, most likely there isn't one "best" ROM anyway I was just wondering if there's a portal somewhere for all the popular ones where I can browse through them, maybe with a description for each with links to the original posts.
Reading and understanding is what I've been doing, to some extent at least, if someone wants to dig into the details it could take months of testing and source code reading to understand everything that's going on under the hood
Thanks for the warnings and hints
---------- Post added at 12:42 AM ---------- Previous post was at 12:36 AM ----------
Nergal di Cuthah said:
http://forum.xda-developers.com/xposed/b-how-to-install-xposed-att-samsung-t3162866/post61985162
And here's an index http://forum.xda-developers.com/showthread.php?t=2616221&highlight=xposed
Click to expand...
Click to collapse
I've seen both of those, they're both for AT&T [I337], which have a locked bootloader. Mine is an I337M, which has an unlocked bootloader, so the steps probably differ a little
But thanks for the links! All appreciated

RaniKheir said:
Would you have any suggestions on where I can find ROMs like that? Is there a main thread or a portal somewhere that lists all the popular ones?
And I have another side question if you don't mind me asking: The device I'm playing around with is a Canadian Galaxy S4 [SGH-I337M], does that mean the ROM I use needs to be compatible with that model specifically? Or are ROMs inconsiderate of the exact model and would work on all Galaxy S4's?
(There's also the different processor issue that depends on the S4's model; Snapdragon 600 vs. Exynos 5 Octa).
Thanks for the descriptive difference between the odexed and deodexed btw, yours is the best I've read so far
Click to expand...
Click to collapse
I do indeed have a recommendation, assuming you want stock TouchWiz (newer versions are growing more like Google edition) I have the SGH-I337 and am running Albe95 ROM (the port of S6's stock 5.1 firmware), now I have a unique copy of the NB1 bootloader but for that reason this OS should also work for you, it comes with all S6 features (theme engine included, but don't change your model number from SM-G920A or you wont be able to connect), can be installed from flash fire, is Deodexed, comes pre rooted with SuperSU installed, is fully compatible with the API21 version of Arter97's Xposed, and wont delete any user data during the pre-install wipe. As a bonus its also compatible with most AOSP tweaks and root modules including Android-Nify (so you can use some Nougat features before its released, though we obviously already have multiwindow and single row quick toggles, but still ).
BTW I do believe its for both SGH-I337 and SGH-I337M, or at the very least there is a port for it, however I do believe it works on both (again, it is Stock TouchWiz so locked or unlocked bootloader doesn't matter and it expects Flash Fire rather than a custom recovery either way as well ;P).

tiaxdaun said:
I do indeed have a recommendation, assuming you want stock TouchWiz (newer versions are growing more like Google edition) I have the SGH-I337 and am running Albe95 ROM (the port of S6's stock 5.1 firmware), now I have a unique copy of the NB1 bootloader but for that reason this OS should also work for you, it comes with all S6 features (theme engine included, but don't change your model number from SM-G920A or you wont be able to connect), can be installed from flash fire, is Deodexed, comes pre rooted with SuperSU installed, is fully compatible with the API21 version of Arter97's Xposed, and wont delete any user data during the pre-install wipe. As a bonus its also compatible with most AOSP tweaks and root modules including Android-Nify (so you can use some Nougat features before its released, though we obviously already have multiwindow and single row quick toggles, but still ).
BTW I do believe its for both SGH-I337 and SGH-I337M, or at the very least there is a port for it, however I do believe it works on both (again, it is Stock TouchWiz so locked or unlocked bootloader doesn't matter and it expects Flash Fire rather than a custom recovery either way as well ;P).
Click to expand...
Click to collapse
Albe95 sounds really good! Will give it a try, thanks
I have never used or read much on Flash Fire, so that will probably be another whole day of experimenting and hoping my device doesn't brick lol. Will make a nandroid backup and give it a shot, thanks again!

Related

[CFW][KK4.4] GomdoLight KitKat Custom Firmware Environment (System Enhancement Pack)

Hi all,
Today, I proudly present GomdoLight KitKat for KOREAN LG G / G2 / G3 / G3A / G3cat6 / Gflex / GK / Gpro / Gpro2 / LTE3 / Vu2 / Vu3 / Gpad7LTE, one of the most widely used (with 20,000+ users approximately) stock-based custom firmware in South Korea.
GomdoLight is more than 3 year old already (first version released on 19th December 2012), and is very mature.
Technically speaking GomdoLight is NOT a complete ROM, but rather a large-scale patch, which modifies official stock firmware to remove all the unnecessary components preloaded by operator/manufacturer, and reorganizes key system parts to 'basic' Android OS with manufacturer's flavor. For some devices GomdoLight's own specialized tool 'GomdoLight Sideloader' can make it possible to install GomdoLight directly over the stock firmware, even without rooting or flashing custom recovery!
GomdoLight is compatible with the following devices (BOLD indicates GomdoLight Sideloader support - no root required)
LG Optimus G: LG-F180S, LG-F180K, LG-F180L ("G")
LG G2: LG-F320S, LG-F320K, LG-F320L ("G2")
LG G3: LG-F400S, LG-F400K, LG-F400L ("G3")
LG G3A: LG-F410S ("G3A")
LG G3 Cat.6: LG-F460S, LG-F460K, LG-F460L ("G3")
LG G Flex: LG-F340S, LG-F340K, LG-F340L ("Gflex")
LG GK: LG-F220K ("GK")
LG G Pro: LG-F240S, LG-F240K, LG-F240L ("Gpro")
LG G Pro 2: LG-F350S, LG-F350K, LG-F350L ("Gpro2")
LG Gx: LG-F310L, LG-F310LR ("Gx")
LG Optimus LTE3: LG-F260S ("LTE3")
LG Optimus Vu2: LG-F200S, LG-F200K, LG-F200L ("Vu2")
LG Vu 3: LG-F300S, LG-F300K, LG-F300L ("Vu3")
LG G Pad 7.0 LTE: LG-V410 ("Gpad7LTE")
A very thorough and extensive (probably, the most extensive on entire xda) manual is provided at the download page, which contains literally everything you need to know to install GomdoLight. FAILURE TO READ THIS DOCUMENT BEFORE INSTALLING WILL ALWAYS LEAD TO VARIOUS UNEXPECTED PROBLEMS. PLEASE READ CAREFULLY. Needless to say, I WILL NOT ANSWER ANY QUESTIONS ALREADY ADDRESSED IN THIS DOCUMENT.
Due to xda forum's limits (in functionality) I am posting a link to the separate (external) DOWNLOAD PAGE. There is no way I can link to each section in the document in xda posts, since xda does not support HTML tag. However some portions of the document are also introduced here.
â–¶ GomdoLight Download / Manual Page
GomdoLight TUTORIALS:
Want to read the built-in user manual again?
Need help using GomdoLight Flag functions?
Installing an EasyMod package? (Sorry the tutorial is in Korean, but screenshots will help)
XDA:DevDB Information
GomdoLight KitKat, ROM for various LGE devices
Contributors
juniecho
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: STOCK FIRMWARE (Firmware compatibility table available)
Based On: STOCK FIRMWARE
Version Information
Status: Stable
Current Stable Version: 4.0
Created 2015-02-26
Last Updated 2015-12-31
CHANGELOG for older versions
Version History:
2015. 12. 31. - Wave 4, initial release
UPDATE LEVEL: MAJOR / IMPORTANCE: VERY HIGH
CHANGELOG:
Oh god, have I abandoned this thread this long? So many changes, sorry, I can't list them all.
A lot of things are now even better than ever. Trust me.
[#GLKITKATCOMMONUPDATE]
EMERGENCY NOTICE, etc.
For some unknown reason I cannot access my DevDB variables at this time. Though G Flex is not on the list of supported devices right now, it IS supported.
* For those who have waited for a long time, sorry for being late, and thank you very much.
Will we see a port to d959 ever? If so and you need a tester pm me!
EDIT: For those wanting to try it did install, but very few bloat was actually removed and no gomdo apps were installed.
dmifsud44 said:
Will we see a port to d959 ever? If so and you need a tester pm me!
Click to expand...
Click to collapse
I'm not sure yet, but it may not be necessary. Because gomdolight is a large-scale patch mainly focusing on script-driven features, just three of system apks are overwritten:
- /system/framework/framework-res.apk
- /system/priv-app/LGSystemUI.apk
- /system/priv-app/LGCameraApp.apk
Camera should be compatible for all variants, and only the FRAMEWORK RESOURCE and the SYSTEM UI might have compatibility issue.
You can first take a Nandroid backup, and try installing GomdoLight all the way to the end over your stock firmware, and see if it boots (and operates without crashes)
For model selection just choose LG-F340K.
1) If it works well: CONGRATULATIONS! You have fully-working GomdoLight.
2) If it fails: Restore Nandroid, and reinstall GomdoLight. However this time choose the 4TH option for battery percentage indicator. (Do not change) This options leaves both framework-res and SystemUI unchanged, so it will work 100%.
juniecho said:
I'm not sure yet, but it may not be necessary. Because gomdolight is a large-scale patch mainly focusing on script-driven features, just three of system apks are overwritten:
- /system/framework/framework-res.apk
- /system/priv-app/LGSystemUI.apk
- /system/priv-app/LGCameraApp.apk
Camera should be compatible for all variants, and only the FRAMEWORK RESOURCE and the SYSTEM UI might have compatibility issue.
You can first take a Nandroid backup, and try installing GomdoLight all the way to the end over your stock firmware, and see if it boots (and operates without crashes)
For model selection just choose LG-F340K.
1) If it works well: CONGRATULATIONS! You have fully-working GomdoLight.
2) If it fails: Restore Nandroid, and reinstall GomdoLight. However this time choose the 4TH option for battery percentage indicator. (Do not change) This options leaves both framework-res and SystemUI unchanged, so it will work 100%.
Click to expand...
Click to collapse
Wheres the download?
podagee said:
Wheres the download?
Click to expand...
Click to collapse
in the download/manual page. section 10. (see the first post) be sure to read the installation guide.
I installed in my d-958, well, some force closes in the settings, app manager and gallery sometimes, but everything else, at least the main functions, works well
Maikeu Locatelli said:
I installed in my d-958, well, some force closes in the settings, app manager and gallery sometimes, but everything else, at least the main functions, works well
Click to expand...
Click to collapse
do they CONSISTENTLY force close by certain actions? or just randomly?
I'm downloading now and will test it for the D95920s firmware. T-Mobile D959 on the latest KitKat 4.4.2 D95920s. Will report back later. I need my phone till at least 4pm central time so I can reach my son but I'll flash after that.
This intrigues me. Sprint supported? I don't feel like dealing with force closes mentioned in previous post in different variant.
Sent from my LG-LS995 using Tapatalk
mattwheat said:
I'm downloading now and will test it for the D95920s firmware. T-Mobile D959 on the latest KitKat 4.4.2 D95920s. Will report back later. I need my phone till at least 4pm central time so I can reach my son but I'll flash after that.
Click to expand...
Click to collapse
good luck. if it crashes revert to stock via nandroid backup and reinstall gomdolight, this time choosing the 4th option (do not overwrite the status bar) with battery percentage indicator.
felacio said:
This intrigues me. Sprint supported? I don't feel like dealing with force closes mentioned in previous post in different variant.
Sent from my LG-LS995 using Tapatalk
Click to expand...
Click to collapse
probably. the script set is practically compatible with all current LGE devices with JB or KK. only few apks should be troublesome.
if not sure, choose not to change the status bar during installation. then it will not overwrite both framework-res and systemui.
Gonna try it on my d950
---------- Post added at 01:31 AM ---------- Previous post was at 01:17 AM ----------
Mahh nothing different.... install went perfect,so far no force closes. What is this supposed to be? I dont see any difference. I used the f340u+. Nothing special going on with this. Restoring my back up now.
podagee said:
Gonna try it on my d950
---------- Post added at 01:31 AM ---------- Previous post was at 01:17 AM ----------
Mahh nothing different.... install went perfect,so far no force closes. What is this supposed to be? I dont see any difference. I used the f340u+. Nothing special going on with this. Restoring my back up now.
Click to expand...
Click to collapse
Don't you see messages like 'GomdoLight: System starting up'?
You usually don't see visible differences after installing GomdoLight, especially on non-Korean firmware, since it does not know what apps to debloat. You would have to debloat the system yourself. However its extensive startup script set provides very unique and useful functions. These functions are explained in the simplified user manual that is automatically displayed after installing. If you did not see the manual opening, and if you do not see the startup messages either, probably something is wrong.
juniecho said:
Don't you see messages like 'GomdoLight: System starting up'?
You usually don't see visible differences after installing GomdoLight, especially on non-Korean firmware, since it does not know what apps to debloat. You would have to debloat the system yourself. However its extensive startup script set provides very unique and useful functions. These functions are explained in the simplified user manual that is automatically displayed after installing. If you did not see the manual opening, and if you do not see the startup messages either, probably something is wrong.
Click to expand...
Click to collapse
I seen all the startups and everything. Gomdo warning of superuser, a major lag on my phone for abot 3-5 minutes of lag. It only uninstalled vutalj. I honestly havent noticed anything special. I even tried it with that status bar selection and it went through fine.
podagee said:
I seen all the startups and everything. Gomdo warning of superuser, a major lag on my phone for abot 3-5 minutes of lag. It only uninstalled vutalj. I honestly havent noticed anything special. I even tried it with that status bar selection and it went through fine.
Click to expand...
Click to collapse
gomdolight's optimizations are not much visually noticable, without drastic changes. if you expect a whole new experience this is not your type of rom.
or, you could install another stock-based rom that will bring significant changes, and install gomdolight over it (without status bar selection) to further aid with its performance.
think gomdolight as a special tool to streamline and 'properly' reorganize the stock firmware (or, stock-based roms). changes are not noticable at first sight, but they surely benefit the user somehow in the long run, and give you better control and (sometimes) superior disaster handling capabilities.
anyway, thank you for letting me know that selecting LGU+ model increases compatibility with non-Korean firmwares.
juniecho said:
gomdolight's optimizations are not much visually noticable, without drastic changes. if you expect a whole new experience this is not your type of rom.
or, you could install another stock-based rom that will bring significant changes, and install gomdolight over it (without status bar selection) to further aid with its performance.
think gomdolight as a special tool to streamline and 'properly' reorganize the stock firmware (or, stock-based roms). changes are not noticable at first sight, but they surely benefit the user somehow in the long run, and give you better control and (sometimes) superior disaster handling capabilities.
anyway, thank you for letting me know that selecting LGU+ model increases compatibility with non-Korean firmwares.
Click to expand...
Click to collapse
Okay. I will reinstall again and run it for a while to see its benefits. Thanks
podagee said:
Okay. I will reinstall again and run it for a while to see its benefits. Thanks
Click to expand...
Click to collapse
the built-in user manual explains some of its advantages... take a look at it, especially the section for what is called gomdolight flags.
UPDATE - Wave 2, revision 3
UPDATE LEVEL: MEDIUM / IMPORTANCE: HIGH
UPGRADE INSTRUCTIONS:
One-touch upgrade via 'Upgrade/Repair' option
CHANGELOG:
Improved GomdoLight Engine scripts
Faster boot time, reduced processor load during boot
Improved GomdoLight operational status notifications
Slightly improved battery efficiency
'Update Center' components updated

[EXPERIMENTAL] [UNOFFICIAL] Xposed for arm64 devices | 5.1 and 5.0 versions available

arm64 is now officially supported: See here
Old OP
Hello Everyone,
I have successfully compiled Xposed for android 5.1.x for arm64 devices.
I have so far tested this on my Nexus 9 running a custom CyanogenMod based Android 5.1 ROM with SELinux disabled (It may work on ROM's with SELinux enabled but testing has to be conducted.).
Install zip is attached to this post. (The SDK 22 one) This will only install Xposed framework for Android 5.1 for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
I compiled this based off of @romracer's source code for Xposed on Android 5.1.x.
So far I have tested the module Lolistat, It seems to be working well.
Please be patient during boot, let your device boot 10 minutes before reporting that it is "bootlooping"
====================
For Android 5.0.x
I have also compiled Xposed for Android 5.0.x for arm64 devices. I have had mixed results from testers so far. The install zip is also attached to this OP (The SDK 21 one). Many HTC M9 users have reported this caused a boot-loop for them. This will only install Xposed framework for Android 5.0.x for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
Remember to always backup all data before using. Use at your own risk.
Please note: There will most likely be arm64 related bugs with both of these. See this post for more information.
Please be patient during boot, let your device boot for 10 minutes before reporting that it is "bootlooping"
just in case...
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
I could also compile Xposed arm64 for android 5.0 if there is enough interest.
Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
Somebody would need to be willing to test, but I could try to compile Xposed for it.
Well, if you're willing to test and support it, you can post unofficial files for testing...
I have a Nexus 9 with Android 5.0 myself and it's running fairly well. I haven't used any complex modules though.
Be aware that 64-bit ROMs need different handling in a couple of places and break some expectations. For example, initZygote() will be executed twice, as there are two app_processXX processes now. Modules might not expect this. I also didn't succeed to enforce a certain startup order of the processes (app_process64 before app_process32) yet, so results might be a bit random. There are probably more differences like this and it's generally more complex than on 32-bit ROMs. That's why I have only posted files for ARM so far. On the other hand, if you're willing to look into issues that come up (e.g. installation problems, crashes, things that are not working) and do some pre-analysis, that's fine and could bring the project forward. If nothing to major comes up, I can then also include official files with the next version. Additional support would be very welcome anyway.
Framework installation zip attached to OP.
good
Only for 5.1?
auggie246 said:
Only for 5.1?
Click to expand...
Click to collapse
I made a version for android 5.0 but I would need somebody to test it before I release it.
5.0 for samsung galaxy s6 ?
koko115 said:
5.0 for samsung galaxy s6 ?
Click to expand...
Click to collapse
Are you kidding? Move along!
subscribed.
Feel free to post any problems you have with this here. (arm64 related problems)
Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo
YouTube adaway works fine
For me
Guitarboarder28 said:
Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo
Click to expand...
Click to collapse
From my understanding, gravitybox is not compatible with Android 5.1 at all.
joshuabg said:
From my understanding, gravitybox is not compatible with Android 5.1 at all.
Click to expand...
Click to collapse
Ohhh didn't even think about that. Would make sense
Thanks for taking this on, joshuabg. I couldn't believe it when I saw this thread. I thought that 5.1 jumped the arm64 shark and we'd never see xposed for N9.
Anyway, I flashed on AICP 4/6 with FireIce K8.3, SELinux disabled and it booted just fine. Tried the following modules, and I see what rovo meant in his post above. It's really hit or miss with the modules just like the [SUPER ALPHA] xposed for 32 bit arm devices. Thanks again for rolling this out to test.
YouTube Adaway - seemed to work, jumped to dozens of random videos and no ads
Minmin Guard - app opened and seemed to operate normally but I think it may have blocked ads across the board without my telling it to do so. I think it also caused an XDA Free force close on opening that wouldn't go away
Swype Tweaks - caused Swype to FC anytime the keyboard should have launched
Yup my bad. Gravitybox says right in the description it'll cause a boot loop on 5.1. Everything is working perfectly. Thanks!

Note 4 question

I just installed CM12 on my Internation Note 4. Will xposed work on it? And if so, what version should I get? (I'm pretty new to all this, and the arm64, x86, etc terms are pretty technical for me and confusing)
NimeniAltu666 said:
I just installed CM12 on my Internation Note 4. Will xposed work on it? And if so, what version should I get? (I'm pretty new to all this, and the arm64, x86, etc terms are pretty technical for me and confusing)
Click to expand...
Click to collapse
If you are new to all of the Xposed stuff, do a lot of research before you do anything. Xposed is a powerful framework, which can easily turn your device into a useless paperweight if flashed without any knowledge about it. You could go ahead and read at least the first and second post of the following thread:
[DISCUSSION] Xposed for Lollipop
There is an FAQ available to answer most of your questions. Use the flow chart in post #2 to determine the correct Xposed version for your device (links to the corresponding threads are linked below the flow chart). If you have further questions about your device/ROM and Xposed, use the search function to search this thread, if anyone else has reported that Xposed is working for your device/ROM.
But please, don't do anything without further investigation by yourself. This is some serious stuff.
Furthermore, I would suggest you do a little research about bootloops and how to recover from them. And don't forget to backup your entire system through your custom recovery before flashing anything.

[ROM][AOSP][4.4/6.0/7.1] Unlegacy Android Project

The Unlegacy-Android Project​Introduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining
Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Screeshots
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?
Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.
mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...
Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?

Is there any known bypass to older devices sign in blocking?

I've got android 4.0.4 and Google sign ins are now blocked on this old version, making it unusable, is there any way around this at all? I've tried various custom ROMs (AOSP 5.1, 7.1, CM11, CM9) all but CM9 face the "play services have stopped" every second and CM9 is the same version I was already using so no difference in sign ins made. Device is GT P3710 (P5 WiFi). I just want to be able to access the play store normally again, I'm not ready to accept this devices life is over yet.
You can spoof your device fingerprint using something like MagiskHide Props Config...
Otherwise, depending on the device, you can try to load a GSI, although Project Treble was introduced with Android 8.0 so it's possible your device isn't capable.
Is your device possibly the GT-P7310 (Galaxy Tab 8.9) and you just made a typo?
V0latyle said:
You can spoof your device fingerprint using something like MagiskHide Props Config...
Otherwise, depending on the device, you can try to load a GSI, although Project Treble was introduced with Android 8.0 so it's possible your device isn't capable.
Is your device possibly the GT-P7310 (Galaxy Tab 8.9) and you just made a typo?
Click to expand...
Click to collapse
Thanks I'll look into it! And yes sorry, I didn't catch that, I indeed meant the GT P7310
vengeancezak said:
Thanks I'll look into it! And yes sorry, I didn't catch that, I indeed meant the GT P7310
Click to expand...
Click to collapse
Okay. This thread will be moved to that section. In the future, please remember to search before posting; we have an entire section of the forum dedicated to the Tab 8.9.
As for helping you...A peek in that section shows that there's not only TWRP available for your device here but a custom AOSP 7.1 based ROM too.

Categories

Resources