UPDATE! Latest version flashes fine
Just a heads up there at least 2 of us who have flashed Xposed Framework arm64 who are now stuck in a boot loop, whilst we don't have access to any Stock H815 Firmware (or any LG G4 firmware) at the moment we are kind of stuck, I was dumb and don't even have a nandroid to fall back on but others have reported that their nandroid failed to restore anyway. So for the time being steer clear of Xposed on the G4. I can still get into recovery so at least when something does come along i'll be able to try and recover it.
Update: We now have a fully working stock Rom and an updated TWRP that allows you to restore your nandroids so don't despair you can now recover if you missed this warning.
So people who have done a full backup in twrp are unable to boot after restoring the backup?
LancerV said:
So people who have done a full backup in twrp are unable to boot after restoring the backup?
Click to expand...
Click to collapse
No they are unable to restore the backup at all
The bootloop is caused by flashing Xposed Framework
DarthEwok said:
No they are unable to restore the backup at all
The bootloop is caused by flashing Xposed Framework
Click to expand...
Click to collapse
Super alpha software on a just released phone isn't always the best idea. But curious can you get into recovery? And if so disable xposed through the file explorer
There is another thread here asking for the system.img. I plan to dump mine tomorrow when I receive my H815. Will this also help you?
http://forum.xda-developers.com/g4/help/h815-dump-t3126629
The main problem here is that the G4 may not be running in 64 bit mode just 32 bit
macdaddie87 said:
The main problem here is that the G4 may not be running in 64 bit mode just 32 bit
Click to expand...
Click to collapse
No
{
"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"
}
macdaddie87 said:
The main problem here is that the G4 may not be running in 64 bit mode just 32 bit
Click to expand...
Click to collapse
I don't think it is either at least not US version. The processor supports it but not sure it is yet
Sent from my S5 using your mom
LancerV said:
No
Click to expand...
Click to collapse
The kernal maybe 64bit because the chip is 64bit and the kernal contains the drivers. The libs that LG has compiled maybe compiled as 32bit. This makes sense that LG would do it like this since they have plans to bring UX 4.0 to the G3 and possibly the G2. They would have to compile UX 4.0 from the ground up to make it completely 64bit. Then compile a 32bit version of UX 4.0 for the previous models.
macdaddie87 said:
The kernal maybe 64bit because the chip is 64bit and the kernal contains the drivers. The libs that LG has compiled maybe compiled as 32bit. This makes sense that LG would do it like this since they have plans to bring UX 4.0 to the G3 and possibly the G2. They would have to compile UX 4.0 from the ground up to make it completely 64bit. Then compile a 32bit version of UX 4.0 for the previous models.
Click to expand...
Click to collapse
... The os is 64. The 64 bit libs are there.
LancerV said:
No
Click to expand...
Click to collapse
Lance-
Could you tell me which app you are using in that screenshot?
thanks.
sideone said:
Lance-
Could you tell me which app you are using in that screenshot?
thanks.
Click to expand...
Click to collapse
Terminal Emulator
LancerV said:
Terminal Emulator
Click to expand...
Click to collapse
thanks, now i feel at home on my g4.
jupp, did the same mistake, this saved me:
http://forum.xda-developers.com/g4/development/rom-h815-10a-stock-rooted-rom-t3129036
Anyone hear anything regarding an ETA on this working on our phone?
The LG stock rom is odexed; I think the rom needs to be deodexed b4 Xposed Framework can be installed (working on it). Will report back
Sounds good, did you have any luck?
Are you guys trying to flash xposed for 5.0.1 or the one for 5.1? Rovo89 is still working on his xposed for 5.0, but there's another for 5.1 not by him.
I have been able to deodex the rom, but it is not booting (bootloop) so there is an error somewhere in the deodexed rom. Still looking I want a bootable deodexed stock rom first, then I will be able to try to install Xposed Framework again.
I have tried flashing the special version for arm64/sdk22 but no luck so far (ends in bootloop) on the odexed stock rom. Nandroid backup to the rescue!
Edit 1: deodexed system/app and system/priv-app: G4 boots but FC errors with NFC/Bluetooth. Deodexed framework results in bootloop. When i have more time i will try to get a logcat while in bootloop with deodexed framework.
Edit 2 (20-06-2015): edited a flashable zip i found to set stock kernel to permissive/not enforcing (and the zip works) (still can't install xposed though...)
mimefly said:
I have been able to deodex the rom, but it is not booting (bootloop) so there is an error somewhere in the deodexed rom. Still looking I want a bootable deodexed stock rom first, then I will be able to try to install Xposed Framework again.
I have tried flashing the special version for arm64/sdk22 but no luck so far (ends in bootloop) on the odexed stock rom. Nandroid backup to the rescue!
Click to expand...
Click to collapse
I spent many hrs trying to install Xposed. Boot loop every time.
One later version of the arm64/sdk22 zip, did appear to install the framework, but red messag"... wrong chip or architecture..".
Thanks to Team Win, the phone works but not in use. Waiting for Xposed.
If you can fix this issue you'll be very popular!
Yes a de-odexed ROM could help here.
Wonder why no custom ROM yet. The G4 (h815) was unlocked in May.
Will look out for your next post.
Related
Can anyone help me finding stock Kernel w/ kexec-hardboot patch for Android 4.4 for multirom?
Im not able to get the version of my primary ROM is based on
(or)
Can i use third-party kernel?
...
Im on 4.4 (KRT16O) Manually flashed factory image (developers.google. com/android/nexus/images#occamkrt16o).
Unfortunately i tried installing other kernel and encountered boot-loop and I had to flash factory image again..
(I used multirom before [before flashing stock 4.4] and used stock 4.3 JWRXXX kexec-hardboot patch kernel. That worked fine.)
{
"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"
}
Instead of flashing the whole factory image again, what you do is something called a backup in your custom recovery. Select to backup "boot" partition, which is the kernel, so if the kernel doesn't work, you can restore just the boot partition. Or you can just use fastboot to restore the stock kernel. Some kernels package flash other files to your system though, so you can do a full restore.
You can give NEO kernel a try, wifi will not work (due to 4.3 kernels lacking the new PRIMA driver) (it'lll work with KitKat), but you can flash the dePRIMAtor package to fix it: http://www.androidfilehost.com/?a=show&w=files&flid=9271
You can try and use the faux kernel from this AOKPK rom as well: http://goo.im/devs/kecinzer/aokpk/mako
eksasol said:
Instead of flashing the whole factory image again, what you do is something called a backup in your custom recovery. Select to backup "boot" partition, which is the kernel, so if the kernel doesn't work, you can restore just the boot partition. Or you can just use fastboot to restore the stock kernel. Some kernels package flash other files to your system though, so you can do a full restore.
You can give NEO kernel a try, wifi will not work (due to 4.3 kernels lacking the new PRIMA driver) (it'lll work with KitKat), but you can flash the dePRIMAtor package to fix it: http://www.androidfilehost.com/?a=show&w=files&flid=9271
You can try and use the faux kernel from this AOKPK rom as well: http://goo.im/devs/kecinzer/aokpk/mako
Click to expand...
Click to collapse
Thanks a looot for kernel backup information it worked flawlessly..
But the above mentioned kernels didn't work either i encountered boot-loop again and restored it by the method u suggested.
I need any 4.4 kernel with kexec-hardboot patch (http://forum.xda-developers.com/showthread.php?t=2472316)..
Sidnexus4 said:
Thanks a looot for kernel backup information it worked flawlessly..
But the above mentioned kernels didn't work either i encountered boot-loop again and restored it by the method u suggested.
I need any 4.4 kernel with kexec-hardboot patch (http://forum.xda-developers.com/showthread.php?t=2472316)..
Click to expand...
Click to collapse
there arent any. considering that the code has to be built into the kernel, and 4.4 kernel source hasnt been releaded yet.
simms22 said:
there arent any. considering that the code has to be built into the kernel, and 4.4 kernel source hasn't been releaded yet.
Click to expand...
Click to collapse
Thanks for the information..
Planning to install rom : http://forum.xda-developers.com/showthread.php?t=2472316
and flash Linaro 4.8.2 kernel : http://forum.xda-developers.com/showthread.php?t=2414064 for multirom hope it works.
i will post the result by an hr.
Sidnexus4 said:
Thanks for the information..
Planning to install rom : http://forum.xda-developers.com/showthread.php?t=2472316
and flash Linaro 4.8.2 kernel : http://forum.xda-developers.com/showthread.php?t=2414064 for multirom hope it works.
i will post the result by an hr.
Click to expand...
Click to collapse
you can try trinity kernel as well, it has the multirom stuff included, and runs on 4.4 roms. heres the latest trinity, tf18b http://goo.gl/RvKALI
Lianro kernel Neo17 worked great for multirom on NEXUS 5 PORT 4.4 KRT16O : http://forum.xda-developers.com/showthread.php?t=2507021 (Rom is far better than the original stock image. It includes all the missing features on stock)
Thanks everyone for the support :victory:
I am using Neo kernel with my stock kitkat and multirom boot into other android roms just fine. No need for ports.
eksasol said:
I am using Neo kernel with my stock kitkat and multirom boot into other android roms just fine. No need for ports.
Click to expand...
Click to collapse
Yeah i realized that later thanks i flashed older Neo version which doesn't have kitkat black screen fix..
In port rom i got "transparent navigation bar" , left swipe "googlenow" which are missing in stock and "ok google" on home-screen worked better then the stock one.
Sidnexus4 said:
Yeah i realized that later thanks i flashed older Neo version which doesn't have kitkat black screen fix..
In port rom i got "transparent navigation bar" , left swipe "googlenow" which are missing in stock and "ok google" on home-screen worked better then the stock one.
Click to expand...
Click to collapse
Have you got knex hardboot then because I need that for Ubuntu touch you don't need knex hardboot for android roms
JJMACCA said:
Have you got knex hardboot then because I need that for Ubuntu touch you don't need knex hardboot for android roms
Click to expand...
Click to collapse
I think its needed for android roms too. when ever i need to boot into another rom after flashing it says knex hardboot needed and it doesn't start up..
As i posted earlier neo kernel worked fine on 4.4(internal rom) with dePRIMAtor file (www.androidfilehost. com/?a=show&w=files&flid=9271).
Hopefully Tasssadar is patching the stock 4.4 kernel with kexec-hardboot.
To be able to get 4.4 running as "internal" Multirom.
mar_sch said:
Hopefully Tasssadar is patching the stock 4.4 kernel with kexec-hardboot.
To be able to get 4.4 running as "internal" Multirom.
Click to expand...
Click to collapse
Great!
Can you give us the link here??
activexda said:
Great!
Can you give us the link here??
Click to expand...
Click to collapse
here z the page... check for the link in second post..
http://forum.xda-developers.com/showthread.php?t=2472295
I know - now - is too early, but any plans to prepare Android 5.0 for Mi2S?
Bucci said:
I know - now - is too early, but any plans to prepare Android 5.0 for Mi2S?
Click to expand...
Click to collapse
Officially I don't think so.
By the way I guess Cyanogen will support CM12 for our Mi2S, so we shoud have ROMs L based.
I hope the same, the only official is miui (currently v5 - but plan v6 - problem is on 4.1.2)
I hope CM12 or another CM/AOSP roms should be available for Mi2S
i think that L for mi2s is sure. In fact nexus 4,which has the same HW of mi2s, will be updated officially by google.
In my opinion the big challenge is to achieve 3.10 from our 3.4 kernel
only when m11kkaa will work on it **** miui they suck :silly:
http://m.weibo.cn/u/1697247850
If we knew Chinese, we will know that Autumn Ivan prepares a Lollipop AOSP for MI2s
@akiba is already working on it! So it seems we will have Lollipop based system in our Mi2S:
I wanted to share clickable link for it but not allowed, anyway copy it to address bar with prefix www as usual:
gizchina.com/2014/11/06/breaking-xiaomi-mi2-spotted-running-android-5-0-lollipop/
...but I hope M1cha already working also on Lollipop based CM12 for Mi2S.
CM12 work in progress: https://plus.google.com/app/basic/p...ovi&sview=25&cid=5&soc-app=115&soc-platform=1
Lollipop is here
http://en.miui.com/thread-61384-1-1.html
Android 5 is Up! Thanks to IVAN
...Hours after using it.
I cannot achieve rooting this device, with any Superuser or SuperSU flashable ZIP, neither with xbin/su from ALL CHINISE 6.0.5.1 Ivan Unofficial CWM (OMG). It doesn't officialy support TDB (I don't care, i just mention that), it has not GAPPS but ok, there is a package for Lollipop ready on the Web, and it fits to Mi2s ROM space, without Micha's repartitioning (i think the 4.4.x GAPPS was junk in terms of size as i check that Lollipop needs half the size of 4.4.x). Advanced Reboots don't worked, CM buttons for App kill, neither. But it's a very early stage (alpha i think) and it doesn't have bugs, it works, it boots, you can test it, but not for every day ROM, avoid it, wait for CM12, or sth better from OmniROM
PS. BACKUP everything, and of course, have ready to flash back the Micha's CWM 6.0.5.0. because with the Chinese Recovery i am facing psychological issues.
PS2. After these hours of testing, i am back to CM11 Latest Snapshot!
PS3. You should turn off TDB before flashing Lollipop.
PS4. Again, wait for a release!
"if you have flashed CWM 6.0.5.0, you can flash latest CM11, go to settings "about phone" and set checkbox "update recovery" and reboot. CWM will be 6.0.5.1 english"
M1cha,
can you confirm it? Thanks?
graw2 said:
"if you have flashed CWM 6.0.5.0, you can flash latest CM11, go to settings "about phone" and set checkbox "update recovery" and reboot. CWM will be 6.0.5.1 english"
M1cha,
can you confirm it? Thanks?
Click to expand...
Click to collapse
I don't have such option. Am on Mokee. But I also couldn't find any other link to CWM 6.0.5.1. Can somebody provide such a link?
no_means_no said:
I don't have such option. Am on Mokee. But I also couldn't find any other link to CWM 6.0.5.1. Can somebody provide such a link?
Click to expand...
Click to collapse
there is a link to CWM 6.0.5.1 http://en.miui.com/thread-61143-1-1.html
but who has 6.0.5.0 no necessary to change it just be aware to install and setup system1 only
It looks better then I expected, cant wait to use this with Xposed Framework!
Would love it to look more like KitKat though, it just looks more professional.
Why no screencast?
Well, because I thought this was faster and easier... plus you get to see the M2(S) and the M2S has a great screen which still looks great on video.. I was just amazed by the speed of 5.0
Why didn't you screen cast, i know it works?
btw, thanx for the video
Robin>Hood said:
It looks better then I expected, cant wait to use this with Xposed Framework!
Would love it to look more like KitKat though, it just looks more professional.
Why no screencast?
Well, because I thought this was faster and easier... plus you get to see the M2(S) and the M2S has a great screen which still looks great on video.. I was just amazed by the speed of 5.0
Click to expand...
Click to collapse
xposed won't be released for lollipop
bobanbg said:
xposed won't be released for lollipop
Click to expand...
Click to collapse
Source?
The Xposed developer said that's difficult 'cause ART, but he didn't say that he will not release Xposed at all.
bobanbg said:
xposed won't be released for lollipop
Click to expand...
Click to collapse
Lol.... says who? I totally agree with @Fortinho .... Rovo has never said it won't come, it's just a matter of if and when
And otherwise I'll just go with CM12 ^^
Btw... Impressive Antutu score on the M2S:
{
"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"
}
no_means_no said:
I don't have such option. Am on Mokee. But I also couldn't find any other link to CWM 6.0.5.1. Can somebody provide such a link?
Click to expand...
Click to collapse
I have tried the solution what I asked here and working perfectly! So easy to change from CWM6.0.5.0 to CWM6.0.5.1 and keep English CWM menu language. I f you just simple flash CWM 6.0.5.1 than it will be Chinese...
Only problem is, I have tried to clean install CM11 NIGHTLY on system2 and it has stacked at boot logo, but I have successfully installed sMIUI onto system 1. What is the reason? (CWM recovery version is 6.0.5.1 )
Thanks for your reply in advance!
Hi Friends,
Everyone tasted the tweaks and uses of Xposed framework in KITKAT stock roms surely missing it in lollipop rom and waiting for it or running behind bugful CM12 ROMS... And Happy news is @rovo89 (developer of Xposed framework) claims that he tested and running fine in ART devices as he tested in Nexus 5 and he also said that xposed framework will be coming soon , not so long... Fingers crossed.... I believe it will out within March or April .....
{
"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"
}
Source: http://www.reddit.com/r/Android/comments/2verta/xposed_for_lollipop_progress_teased_by_rovo89/
http://forum.xda-developers.com/showpost.php?p=58751037&postcount=37
Check this
Sent from my Moto G using Tapatalk
there is already an alpha release of Xposed 3.0 which you can get it from here
have tried on stock asia 5.0.2 and bootloop
I was able to flash the zip and boot but the app simply wouldnt install.
Also the ui felt extremely sluggish. Asia retail 5.0.2
I got memory full message after the zip, with 4gb free. Did a reset now the app won't run, just getting need to reboot message.
eemgee said:
I got memory full message after the zip, with 4gb free. Did a reset now the app won't run, just getting need to reboot message.
Click to expand...
Click to collapse
flash system files without other or erase data, i got this too, is no way at the moment to make it work from what i readed. and we dont have an uninstaller for the zip.
I readed its works fine on gpe 5.0.1 but not in 5.0.2 motorola
Im also on 5.0.2 brazilian and got this too
Is all 4.4 modules working on lollipop?
eddydc1 said:
Is all 4.4 modules working on lollipop?
Click to expand...
Click to collapse
if them are updated for lollipop will work. i readed @ xposed GEL experience and it is updated. I dont know about others. u should take a look on modules pages
eddydc1 said:
Is all 4.4 modules working on lollipop?
Click to expand...
Click to collapse
Modules that make changes to SystemUI don't work. Some still retain partial functionality.
You can refer to this Reddit thread for a list modules that don't work (yet).
zerro4cool said:
flash system files without other or erase data, i got this too, is no way at the moment to make it work from what i readed. and we dont have an uninstaller for the zip.
I readed its works fine on gpe 5.0.1 but not in 5.0.2 motorola
Im also on 5.0.2 brazilian and got this too
Click to expand...
Click to collapse
I had another go and was a but laggy after first boot but it's fine now. I've only installed one module, lollipop power menu and it's working great
eddydc1 said:
Is all 4.4 modules working on lollipop?
Click to expand...
Click to collapse
Rovo said in the portal that ones that ones that just change normal apps should work. Ones that change system might not, but he said that the Dev would just need to move the code to a different place
I have working xposed on 5.0.2 rom so what is the problem? error with empty memory? wipe cache and dalvik, no working modules? take time there is less then 24h when xposed come and you want to work everything...
grenify work in boost mode, close apps all in one moment, when witout xposed close one by one
boot manager don see activation,
cpufreq in statusbar shows frequency
youtube background works
plantator said:
I have working xposed on 5.0.2 rom so what is the problem? error with empty memory? wipe cache and dalvik, no working modules? take time there is less then 24h when xposed come and you want to work everything...
grenify work in boost mode, close apps all in one moment, when witout xposed close one by one
boot manager don see activation,
cpufreq in statusbar shows frequency
youtube background works
Click to expand...
Click to collapse
What firmware/ROM do you have?
xt1032 220.21.28.falcon_umts.Brasil.en.BR
Tried it on XT1033 Asia Dual Sim Retail and works like a charm! Used TWRP.
I'm using xposed and worked a bunch of modules...
TIp: Change the SELinux to permissive... some modules need this (APM+ worked after this)
Yeah, for me amplify start working after change SELinux
Not working with CM12, installed but not active
you flashed zip first? then try to install apk.
Hey guys thought I'd let everyone know that Wanam's custom xposed framework for Samsung 5.1.1 firmware is working on the SM-P600.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Wanam states that CWM and deodexed ROM needed or recommended but with the testing I've done so far it's working well using TWRP and rooted stock odexed DOJ3 firmware.
marxses said:
Hey guys thought I'd let everyone know that Wanam's custom xposed framework for Samsung 5.1.1 firmware is working on the SM-P600.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Wanam states that CWM and deodexed ROM needed or recommended but with the testing I've done so far it's working well using TWRP and rooted stock odexed DOJ3 firmware.
Click to expand...
Click to collapse
Please educate on anything I might not be thinking about. I cannot make xposed framework function. stock rooted 5.1.1 SM-P600. Following everything exactly. I have DOK1.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
I have to agree with radpp16 above, I followed the instructions but I still can't get it working. The app installed properly, I was able to boot to recovery and flashed it, but after I restarted the app was unable to detect the flashed files.
Tried both the P600UBUDOL2 and P600XXUDOJ3 firmwares and didn't work. Using TWRP 2.8.6.0 and below will cause softbrick on DOL2 firmware.
radpp16 said:
Please educate on anything I might not be thinking about. I cannot make xposed framework function. stock rooted 5.1.1 SM-P600. Following everything exactly. I have DOK1.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
What version of xposed framework have you been trying? I am using v75.8. Maybe give that a go.
https://www.androidfilehost.com/?w=files&flid=38719
You're running a different firmware which could possibly be causing problems.... not sure if I can offer much more help. I just followed the instructions exactly and it worked.
Pact said:
I have to agree with radpp16 above, I followed the instructions but I still can't get it working. The app installed properly, I was able to boot to recovery and flashed it, but after I restarted the app was unable to detect the flashed files.
Tried both the P600UBUDOL2 and P600XXUDOJ3 firmwares and didn't work. Using TWRP 2.8.6.0 and below will cause softbrick on DOL2 firmware.
Click to expand...
Click to collapse
Try v75.8 on DOJ3 and let me know how you go.
https://www.androidfilehost.com/?w=files&flid=38719
marxses said:
Try v75.8 on DOJ3 and let me know how you go.
Click to expand...
Click to collapse
Thanks for this info, right now I'm using the tablet to do important work so I can't flash a new one, but I'll likely do it in the next 3 - 4 days.
In the meantime, just to confirm, all I need to do is get a rooted DOJ3, install the xposed app, then boot to recovery, flash that v75.8, bootup and then finish the installation in the main xposed app, yes? I'll probably use enotar's in the development section, his fourth beta that's still on the DOJ3 version. That one's pre-rooted and all so simplifies a lot of the work. His newest B5 release is using the very latest firmware that Samsung outs though I haven't been able to get xposed to work on it. So I'll just use the DOJ3 release then.
I've been flashing numerous times but can't get xposed to work with the many firmwares out there so I'm being a bit cautious lol
Pact said:
Thanks for this info, right now I'm using the tablet to do important work so I can't flash a new one, but I'll likely do it in the next 3 - 4 days.
In the meantime, just to confirm, all I need to do is get a rooted DOJ3, install the xposed app, then boot to recovery, flash that v75.8, bootup and then finish the installation in the main xposed app, yes? I'll probably use enotar's in the development section, his fourth beta that's still on the DOJ3 version. That one's pre-rooted and all so simplifies a lot of the work. His newest B5 release is using the very latest firmware that Samsung outs though I haven't been able to get xposed to work on it. So I'll just use the DOJ3 release then.
I've been flashing numerous times but can't get xposed to work with the many firmwares out there so I'm being a bit cautious lol
Click to expand...
Click to collapse
You're welcome.
Not sure what you mean by finish the installation in the main app though? The xposed framework should be installed and locked in, meaning no ability to flash or upgrade the framework within the app.
{
"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"
}
EDIT 2: Boy, did this take a lot of derpin around, but xposed versions are rather specific to firmwares, and after a number of testing I finally found that for the fifth beta of Enotar's ROM, which is based on firmware P600UBUDOL2, the one that works is v 79.0, specifically xposed-v79.0-sdk22-arm-custom-build-by-wanam-20151217.
====================================================================
EDIT: I flashed Xluco's kernel on Enotar's B4, that somehow removed the device's root. Giving up on that firmware, I now reformat the device. flashed the fifth beta, installed the alpha 3.0 Xposed app, flashed the latest wanam xposed, v79.1, and now after rebooting the app wasn't even able to detect it.
===============================================================
Well, I flashed the lollipop firmware, installed the xposed app, boot to recovery, flashed the aforementioned xposed file and when I came back to the main app this appears.
Basically "CANNOT LINK EXECUTABLE DEPENDENCIES: library 'libdvm.so' not found"
Tried searching around, seems like the problem stems from an incorrect xposed module but I've followed the steps outlined in my previous post which mirrors marxses's suggestion. Any helping tips, eh?
Which Xposed version will work with DPC4 stock 5.1.1?
Hi,
I've built my own LineageOS 13.0 + Kernel + TWRP and flashed everything to my phone, but the phone just keep booting LineageOS (Logo + Language picker), can someone help me debug and fix this ?
I'm on ubuntu 16.04 with fresh LineageOS 13.0 repo and my device sources are from : https://github.com/MSM8226-Samsung/
Hi,
Well it seems that my /system/lib is empty after flashing my LineageOS rom... I don't actually know whats happening.
Looks like some proprietary blobs are missing (libloc_core.so), I'll try to pull them from STOCK Rom.
I've successfully launched my own LineageOS!
{
"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 getting log of EGL Errors, Wifi not working and graphic bugs. I'm trying to debug this but if someone which already developped for this phone is willing to help, I would be happy to share some logs.
yumi14 said:
I'm getting log of EGL Errors, Wifi not working and graphic bugs. I'm trying to debug this but if someone which already developped for this phone is willing to help, I would be happy to share some logs.
Click to expand...
Click to collapse
Flash rr experia rom
arjun1919 said:
Flash rr experia rom
Click to expand...
Click to collapse
? Its a ROM that I compiled on my own, why would I flash another ROM ?
yumi14 said:
I'm getting log of EGL Errors, Wifi not working and graphic bugs. I'm trying to debug this but if someone which already developped for this phone is willing to help, I would be happy to share some logs.
Click to expand...
Click to collapse
You can ask @neonkat .He is a good developer and has developed roms on grand 2 before
yumi14 said:
Hi,
Well it seems that my /system/lib is empty after flashing my LineageOS rom... I don't actually know whats happening.
Looks like some proprietary blobs are missing (libloc_core.so), I'll try to pull them from STOCK Rom.
I've successfully launched my own LineageOS!
Click to expand...
Click to collapse
Have you run the extract_proprietarty.sh shell script?
You could also take a look at Android Blob Utility (Google that)
@yumi14
WaseemAlkurdi said:
Have you run the extract_proprietarty.sh shell script?
You could also take a look at Android Blob Utility (Google that)
@yumi14
Click to expand...
Click to collapse
I did 3 things, 1st i downloaded blobs from MSM8226 github, 2nd I triied to extract my blobs with 'extract_proprietarty.sh' and last, I extracted my stock ROM system.img and ran 'extract_proprietarty.sh' on the extracted folder, but some blobs are always missing after flashing my own rom...
After some debugging, I found all missing blobs (some were not in my stock ROM so I had to copy em from another ROM (cyanogen 13)).
But I still have a lot of graphics errors and random crash.
I am not able to try anymore as I needed a phone, so I've just flashed a CyanogenMod 13.0 and everything is working great. Maybe I'll try to build a Custom ROM for another phone, dunno.
yumi14 said:
I did 3 things, 1st i downloaded blobs from MSM8226 github, 2nd I triied to extract my blobs with 'extract_proprietarty.sh' and last, I extracted my stock ROM system.img and ran 'extract_proprietarty.sh' on the extracted folder, but some blobs are always missing after flashing my own rom...
After some debugging, I found all missing blobs (some were not in my stock ROM so I had to copy em from another ROM (cyanogen 13)).
But I still have a lot of graphics errors and random crash.
I am not able to try anymore as I needed a phone, so I've just flashed a CyanogenMod 13.0 and everything is working great. Maybe I'll try to build a Custom ROM for another phone, dunno.
Click to expand...
Click to collapse
Try Android Blob Utility then. This will dump whatever dependent blobs a given blob needs. That'll give you all the blobs needed.
Also attach a logcat.
Hey! Please help me. I flashed marshmallow rom in my grand 2 smg7102. It is showing bootloops. I tried factory reset, wipe dalvik cache but it didn't start. Please help me.