have looked through a different threads for a solution to this problem and cannot find anything to help me, i have a galaxy s4 running lollipop 5.0.1 ( Armv7), phone is rooted and has TWRP custom recovery installed tonight i have tried to flash xposed framework , it flashes fine i then clear my cache and dalvik and reboot phone only to have an infinite samsung logo. this is only solved by using the framework un-installer. i have tried all versions from v75-v85 but still get the same problem. anyone have a solution for this or should i just give up?
Have you read the part which mentions you need a special version for TouchWiz ROMs?
No i'm afraid i haven't seen it, just looked through my system files and came across touchwiz. Where do i go from here, do i have to reflash a new custom recovery or is it simply a different framework zip file?
GDReaper said:
Have you read the part which mentions you need a special version for TouchWiz ROMs?
Click to expand...
Click to collapse
I have follwed instructions on the thread, have download and tried to flash but keep getting an error because my ROM is not deodexed, i truly have no idea how to do this.
brian2291 said:
I have follwed instructions on the thread, have download and tried to flash but keep getting an error because my ROM is not deodexed, i truly have no idea how to do this.
Click to expand...
Click to collapse
You apparently haven't followed or read them carefully enough, because the thread also gives you links on how to deodex.
Just throwing this here.
brian2291 said:
have looked through a different threads for a solution to this problem and cannot find anything to help me, i have a galaxy s4 running lollipop 5.0.1 ( Armv7), phone is rooted and has TWRP custom recovery installed tonight i have tried to flash xposed framework , it flashes fine i then clear my cache and dalvik and reboot phone only to have an infinite samsung logo. this is only solved by using the framework un-installer. i have tried all versions from v75-v85 but still get the same problem. anyone have a solution for this or should i just give up?
Click to expand...
Click to collapse
Don't flash xposed on stock. Simple. Flash a ROM and then it.
gosha98_ said:
Don't flash xposed on stock. Simple. Flash a ROM and then it.
Click to expand...
Click to collapse
Have installed custom lolliRom and tried to flash framework still had same problem. Can't find a solution for this, pokemon go is driving me crazy ?
brian2291 said:
Have installed custom lolliRom and tried to flash framework still had same problem. Can't find a solution for this, pokemon go is driving me crazy ?
Click to expand...
Click to collapse
Follow the link I posted!
Related
I've been trying many things to no avail. I am able to get recovery on my i9505G (which I have read is built into the CWM version now for the i9505) and it seems to work fine. I have the 01/08 nightly CM11 on the phone, but whenever I reboot and select "recovery" it gives me this error. Sometimes if I hit the restart the device, it will boot into recovery correctly. I've even started fresh by wiping the entire phone and the multiple partitions (from having started on 4.2) and flashed a fresh 4.4.2 stock (rooted) tar through odin. From there I flashed the recovery, installed CM as I always have, but it is still happening.
What am I doing wrong?
The photo u attached is STOCK RECOVERY. If u want install CUSTOM RECOVERY for install CUSTOM ROMS: HERE
* EDIT: Dont flash custom recovery/Roms/Kernels/Basebands of i9505 for ur i9505G. Its completely different
Joku1981 said:
The photo u attached is STOCK RECOVERY. If u want install CUSTOM RECOVERY for install CUSTOM ROMS: HERE
* EDIT: Dont flash custom recovery/Roms/Kernels/Basebands of i9505 for ur i9505G. Its completely different
Click to expand...
Click to collapse
That is the weird thing, it does have the custom CWM recovery on it, but this happens when I click to reboot into recovery in CM11. I've tried reinstalling CWM numerous times, but I still get this same situation after the first time.
mrmartin86 said:
That is the weird thing, it does have the custom CWM recovery on it, but this happens when I click to reboot into recovery in CM11. I've tried reinstalling CWM numerous times, but I still get this same situation after the first time.
Click to expand...
Click to collapse
Coz u are installing CWM for i9505 no for i9505G maybe?
Joku1981 said:
Coz u are installing CWM for i9505 no for i9505G maybe?
Click to expand...
Click to collapse
I've read on many of the threads here that the i9505G build-specifics were incorporated into "jfltexx" builds.
mrmartin86 said:
I've read on many of the threads here that the i9505G build-specifics were incorporated into "jfltexx" builds.
Click to expand...
Click to collapse
No:
- GT-i9505 is into "jfltexx" builds
- GT-i9505G is into "jgedlteue" builds
Joku1981 said:
No:
- GT-i9505 is into "jfltexx" builds
- GT-i9505G is into "jgedlteue" builds
Click to expand...
Click to collapse
What I meant was the i9505G specifics were builts in the CWM and Cyanogenmod builds of the jfltexx.
mrmartin86 said:
What I meant was the i9505G specifics were builts in the CWM and Cyanogenmod builds of the jfltexx.
Click to expand...
Click to collapse
Yes and no, but we dont gona speak about that now. It will be soooo long :highfive:. You asked one thing sir in this thread... If i helped ya Im happy for it :good:
Joku1981 said:
Yes and no, but we dont gona speak about that now. It will be soooo long :highfive:. You asked one thing sir in this thread... If i helped ya Im happy for it :good:
Click to expand...
Click to collapse
Well here is what I am trying to do. Root isn't a problem, but getting recovery on it is. I've been using the jltflexx builds of CWM and Cyanogen because I read that it was built into it. They both install with no problem and I can get up and running. The problem I run into is getting back into custom recovery and I get that picture error above when I try. I don't know if the custom recovery is getting overwritten by something or what, but it does get installed otherwise I wouldn't be able to get CM11 on it in the first place.
mrmartin86 said:
Well here is what I am trying to do. Root isn't a problem, but getting recovery on it is. I've been using the jltflexx builds of CWM and Cyanogen because I read that it was built into it. They both install with no problem and I can get up and running. The problem I run into is getting back into custom recovery and I get that picture error above when I try. I don't know if the custom recovery is getting overwritten by something or what, but it does get installed otherwise I wouldn't be able to get CM11 on it in the first place.
Click to expand...
Click to collapse
How i see u still having the STOCK RECOVERY and u was telling me it worked ok. If i was u i will try the post #2
Joku1981 said:
How i see u still having the STOCK RECOVERY and u was telling me it worked ok. If i was u i will try the post #2
Click to expand...
Click to collapse
That is what I don't get. How could I have flashed the custom CWM recovery, used it to install CM, but then have stock recovery and can't get back into the custom one all the time? It is really bizarre.
mrmartin86 said:
That is what I don't get. How could I have flashed the custom CWM recovery, used it to install CM, but then have stock recovery and can't get back into the custom one all the time? It is really bizarre.
Click to expand...
Click to collapse
These are my sources about the i9505 jltflexx builds.
http://forum.xda-developers.com/showthread.php?t=2370101
http://forum.cyanogenmod.com/topic/75444-gt-i9505g-cyanogenmod/
EDIT: Seems this is a problem with CWM itself. When I just used TWRP to do all the same things, everything worked fine.
mrmartin86 said:
These are my sources about the i9505 jltflexx builds.
http://forum.xda-developers.com/showthread.php?t=2370101
http://forum.cyanogenmod.com/topic/75444-gt-i9505g-cyanogenmod/
EDIT: Seems this is a problem with CWM itself. When I just used TWRP to do all the same things, everything worked fine.
Click to expand...
Click to collapse
CWM 6.0.4.4 work fine on the i9505G. I use it on mine and have since it came out.
I'm trying to install a custom rom onto my ATT Galaxy S4. I have Safestrap installed and I can boot to the recovery.
I've tried putting BeanStalk on it and it shows the "SafeStrap Enabled" and then shuts off. So then I did some more searching and put ProjectChaos on it. It'll boot to the custom bootlogo that I've chosen and it just stays there. It won't go past that.
I don't exactly know what I'm doing wrong here...
Can anyone give me any insight?
Bbychaos said:
I'm trying to install a custom rom onto my ATT Galaxy S4. I have Safestrap installed and I can boot to the recovery.
I've tried putting BeanStalk on it and it shows the "SafeStrap Enabled" and then shuts off. So then I did some more searching and put ProjectChaos on it. It'll boot to the custom bootlogo that I've chosen and it just stays there. It won't go past that.
I don't exactly know what I'm doing wrong here...
Can anyone give me any insight?
Click to expand...
Click to collapse
which firmware are you coming from? Are you flashing the right kernel modules?
Thr33-F0ur said:
which firmware are you coming from? Are you flashing the right kernel modules?
Click to expand...
Click to collapse
I'm on 4.3 trying to get on 4.4
I'm not completely sure about the kernel. I tried 2 different ones with ProjectChaos
http://forum.xda-developers.com/showthread.php?t=2680868
Sent from my SGH-I337 running GPE using Tapatalk
Check this thread out as well please:
http://forum.xda-developers.com/showthread.php?t=2616221
I don't know about ProjectChaos, but thought Beanstalk was CM based. You can't run CM/AOSP roms. Only TW based with TW kernels--
Check out Mapleleaf rom.... it is tw based and runs beautifully with the googy-max kernel....dumb question but you are wiping between rom changes right?
Gage_Hero said:
Check out Mapleleaf rom.... it is tw based and runs beautifully with the googy-max kernel....dumb question but you are wiping between rom changes right?
Click to expand...
Click to collapse
Yes I am.
I'll check out the links. I've been busy so I haven't been able to try anything just yet. I'll report back when I get to mess with it
rugmankc said:
I don't know about ProjectChaos, but thought Beanstalk was CM based. You can't run CM/AOSP roms. Only TW based with TW kernels--
Click to expand...
Click to collapse
I am assuming ProjectChaos is TW, I got it installed and it's running nicely.
The only problem I've had thus far (I just got it installed a few hours ago) is when it boots up it says "com.android.phone" has stopped when it boots up.
I had to go back into SS and Fix Permissions and rewipe cache, etc. because I was having a reboot issue. But that solved that.
Thanks for the help everyone!!
Bbychaos said:
I am assuming ProjectChaos is TW, I got it installed and it's running nicely.
The only problem I've had thus far (I just got it installed a few hours ago) is when it boots up it says "com.android.phone" has stopped when it boots up.
I had to go back into SS and Fix Permissions and rewipe cache, etc. because I was having a reboot issue. But that solved that.
Thanks for the help everyone!!
Click to expand...
Click to collapse
Glad you got it.
Sent From My Samsung Galaxy S4
Hi Guys,
As you can see, I am new to this site. My phone is S4 19505. Yesterday, I tried to root my phone and that was a succes. Problem began when I want to install kernel for longer battery life. I have installed kernel from http://forum.xda-developers.com/showthread.php?t=2297379 and I have chosen Touchwiz KitKat 4.4 version. After I flashed this kernel my s4 is not starting. It just stuck at first screen "where we get first white letters samsung galaxy s4".
I have no idea what to do now.
Can anyone please help me?
Advance thanks.
safi_k19 said:
Hi Guys,
As you can see, I am new to this site. My phone is S4 19505. Yesterday, I tried to root my phone and that was a succes. Problem began when I want to install kernel for longer battery life. I have installed kernel from http://forum.xda-developers.com/showthread.php?t=2297379 and I have chosen Touchwiz KitKat 4.4 version. After I flashed this kernel my s4 is not starting. It just stuck at first screen "where we get first white letters samsung galaxy s4".
I have no idea what to do now.
Can anyone please help me?
Advance thanks.
Click to expand...
Click to collapse
Did you follow the instruction of the OP, wipe cache and wipe dalvik after installing it?
Interface23 said:
Did you follow the instruction of the OP, wipe cache and wipe dalvik after installing it?
Click to expand...
Click to collapse
Yes, I did everything as there said.
safi_k19 said:
Yes, I did everything as there said.
Click to expand...
Click to collapse
Are you using cmw or twrp? I believe your stock rom is 4.4 kitkat
Interface23 said:
Are you using cmw or twrp? I believe your stock rom is 4.4 kitkat
Click to expand...
Click to collapse
twrp. I dont know what you mean by stock rom because this is my first time I did. My device is running 4.4.2. and I chose for kernel 4.4 version of tw.
I think that you have to re-flash a new rom. Then, you have to retry installing root and the kernel.
msmlz said:
I think that you have to re-flash a new rom. Then, you have to retry installing root and the kernel.
Click to expand...
Click to collapse
I agree with msmlz, if you have nandroid restore it or download the firmware in sammobile and reflash it and before flashing the custom kernel again, read the thread, see if someone face bootloop like you. Hope someone with experience on it could help you, I never install custom kernel, just update the last stock kernel on my rooted stock rom.
With the recent files being dumped for note 5. Would it be possible to have it ported over to the s5 with some changes, without having to wait til the official release?
I do not think it's possible,as we do not have sources for 6.0 kernel on klte :| But still,hope someone can do some kind of workaround.
just to try the new marshmallow test cm 13 really to home
Wolf80 said:
I do not think it's possible,as we do not have sources for 6.0 kernel on klte :| But still,hope someone can do some kind of workaround.
Click to expand...
Click to collapse
Yeah that's what I was hoping.
superacc75 said:
just to try the new marshmallow test cm 13 really to home
Click to expand...
Click to collapse
I've tried it. It never boots on my g900t. No cm roms seem to work on my s5. Am I doing something wrong? Lol
It might be possible, as there are few unofficial CM13 (Android 6.0) builds already available for our Galaxy S5. Let's just wait and hope someone out there with kind heart and adequate time develop one for our phone.
Vineen said:
It might be possible, as there are few unofficial CM13 (Android 6.0) builds already available for our Galaxy S5. Let's just wait and hope someone out there with kind heart and adequate time develop one for our phone.
Click to expand...
Click to collapse
Yeah i cant get cm 13 to work. :/ or else i would use that.
daddymemoru said:
Yeah i cant get cm 13 to work. :/ or else i would use that.
Click to expand...
Click to collapse
The unofficial CM13 build by @albinoman887 can be actually used as a daily driver.
Vineen said:
The unofficial CM13 build by @albinoman887 can be actually used as a daily driver.
Click to expand...
Click to collapse
It always seems to get stuck in a bootloop for me. Help?
daddymemoru said:
It always seems to get stuck in a bootloop for me. Help?
Click to expand...
Click to collapse
Which varient you have? Which recovery? Which gapps? How are you downloading?
Zehlek said:
Which varient you have? Which recovery? Which gapps? How are you downloading?
Click to expand...
Click to collapse
I have the g900t (T-Mobile) using TWRP. Open gapps 6.0 (where you can choose your own). And I download off the XDA pages with my phone.
I should also note that only touchwiz Roms seem to work. Any cm ROM always gets stuck at bootloop, I can sometimes getting it to optimizing apps by switching kernel, but then it reboots over and over without starting.
daddymemoru said:
I have the g900t (T-Mobile) using TWRP. Open gapps 6.0 (where you can choose your own). And I download off the XDA pages with my phone.
I should also note that only touchwiz Roms seem to work. Any cm ROM always gets stuck at bootloop, I can sometimes getting it to optimizing apps by switching kernel, but then it reboots over and over without starting.
Click to expand...
Click to collapse
I use these gapps
https://www.androidfilehost.com/?fid=24269982086988288
What I do is
-Download ROM and gapps with chrome on my phone
-reboot into twrp
-wipe system, data, cache, dalvik
-flash ROM(klte unified)
-flash gapps
- boot
I have 900w8 variant but that shouldn't matter
Sent from my SM-G900W8 using Tapatalk
Zehlek said:
I use these gapps
https://www.androidfilehost.com/?fid=24269982086988288
What I do is
-Download ROM and gapps with chrome on my phone
-reboot into twrp
-wipe system, data, cache, dalvik
-flash ROM(klte unified)
-flash gapps
- boot
I have 900w8 variant but that shouldn't matter
Sent from my SM-G900W8 using Tapatalk
Click to expand...
Click to collapse
Yeah just get stuck in a bootloop.
daddymemoru said:
It always seems to get stuck in a bootloop for me. Help?
Click to expand...
Click to collapse
Make sure you've performed a full wipe before flashing it and if you're planning on using Google apps then make sure to flash them before booting into CM13 or else you'll get stuck with lots of FCs.
Vineen said:
Make sure you've performed a full wipe before flashing it and if you're planning on using Google apps then make sure to flash them before booting into CM13 or else you'll get stuck with lots of FCs.
Click to expand...
Click to collapse
Yeah I've tried that. CM Roms don't ever boot for me for some reason.
daddymemoru said:
Yeah I've tried that. CM Roms don't ever boot for me for some reason.
Click to expand...
Click to collapse
Have you tried downgrading to KitKat then repeating the process again?
Sent from my SM-G900F using XDA Forums
Vineen said:
Have you tried downgrading to KitKat then repeating the process again?
Sent from my SM-G900F using XDA Forums
Click to expand...
Click to collapse
I thought you couldn't do that with the latest 5.1.1 update. If you can I'd like some steps so I can try. because knowing me I'd get lost somewhere. >.<
daddymemoru said:
I thought you couldn't do that with the latest 5.1.1 update. If you can I'd like some steps so I can try. because knowing me I'd get lost somewhere. >.<
Click to expand...
Click to collapse
Is your bootloader unlocked? Because as far as I know, there are variants of the Galaxy S5 which have their bootloaders unlocked, making them impossible to downgrade or else making their device bootloop.
As for the steps, you only have to download the KitKat firmware (I recommend ANE2 - easiest to root) from sammobile.com then flash it via Odin.
Make sure you have Samsung Mobile Drivers installed if you are working on a Windows environment. Afterwards, root your Galaxy S5 by downloading towelroot from towelroot.com.
Once done, download SuperSU on Play Store. Flash custom recovery using Rashr. Make sure Reactivation Lock is disabled before flashing anything custom or else it will cause problems.
When you have custom recovery successfully installed, try flashing CyanogenMod again.
Sent from my SM-G900F using XDA Forums
Vineen said:
Is your bootloader unlocked? Because as far as I know, there are variants of the Galaxy S5 which have their bootloaders unlocked, making them impossible to downgrade or else making their device bootloop.
As for the steps, you only have to download the KitKat firmware (I recommend ANE2 - easiest to root) from sammobile.com then flash it via Odin.
Make sure you have Samsung Mobile Drivers installed if you are working on a Windows environment. Afterwards, root your Galaxy S5 by downloading towelroot from towelroot.com.
Once done, download SuperSU on Play Store. Flash custom recovery using Rashr. Make sure Reactivation Lock is disabled before flashing anything custom or else it will cause problems.
When you have custom recovery successfully installed, try flashing CyanogenMod again.
Sent from my SM-G900F using XDA Forums
Click to expand...
Click to collapse
OK I'll try that. I have T-Mobile g900t. I'm pretty sure its unlocked. Lol I'd be the happiest person ever if it works. I used to have blisspop, but now the ROM doesn't work.
daddymemoru said:
OK I'll try that. I have T-Mobile g900t. I'm pretty sure its unlocked. Lol I'd be the happiest person ever if it works. I used to have blisspop, but now the ROM doesn't work.
Click to expand...
Click to collapse
Report back if everything goes fine. TouchWiz Lollipop caused me a lot of problems in modding mainly because it's harder to mod it unlike KitKat which is pretty straight forward.
By reverting to KitKat, I was able to use XtreStoLite which stopped working on me for some time. Now I'm on Android Marshmallow 6.0.1 (CyanogenMod 13 unofficial by @albinoman887) and I'm satisfied than ever.
Sent from my SM-G900F using XDA Forums
Hi guys, I'm pretty new to custom roms and this forum so feel free to delete/move thread if i've posted in the wrong area.
Phone: Samsung J5 SM-J500FN
I am having trouble flashing custom roms. I have rooted my device, installed TWRP and got to the point where I can install the rom. After installing the rom through TWRP when I reboot the phone I get the classic boot screen then it freezes, I get a yellow line across the screen and the screen goes bright green and full of what look to be dead pixels. I have attempted to install Lineage, Aosp extended and Ressurection Reloaded and have had the same result with all 3. I have been able to reinstall back to stock each time. Is it possible to maybe get some tips on where I may be going wrong here? Thank you in advance.
Garz92 said:
Hi guys, I'm pretty new to custom roms and this forum so feel free to delete/move thread if i've posted in the wrong area.
Phone: Samsung J5 SM-J500FN
I am having trouble flashing custom roms. I have rooted my device, installed TWRP and got to the point where I can install the rom. After installing the rom through TWRP when I reboot the phone I get the classic boot screen then it freezes, I get a yellow line across the screen and the screen goes bright green and full of what look to be dead pixels. I have attempted to install Lineage, Aosp extended and Ressurection Reloaded and have had the same result with all 3. I have been able to reinstall back to stock each time. Is it possible to maybe get some tips on where I may be going wrong here? Thank you in advance.
Click to expand...
Click to collapse
Are you sure you're using the stock firmware required?
Some custom roms, like the 7.1.2s almost all of the threads tells you you need LL 5.1.1 before flashing the custom rom.
Or some need 6.0.1. Are you sure you're reading all the instructions correctly?
JohnTryingToRoot said:
Are you sure you're using the stock firmware required?
Some custom roms, like the 7.1.2s almost all of the threads tells you you need LL 5.1.1 before flashing the custom rom.
Or some need 6.0.1. Are you sure you're reading all the instructions correctly?
Click to expand...
Click to collapse
Thanks for the response mate, I did a bit more reading after posting this and found that out My own fault. I am currently downgrading to Lollipop 5.1.1 using odin but now it's stuck on the samsung logo on boot up after odin has done its bit. Maybe it just takes ages to install but I wouldn't be surprised if I've done something else wrong
Garz92 said:
Thanks for the response mate, I did a bit more reading after posting this and found that out My own fault. I am currently downgrading to Lollipop 5.1.1 using odin but now it's stuck on the samsung logo on boot up after odin has done its bit. Maybe it just takes ages to install but I wouldn't be surprised if I've done something else wrong
Click to expand...
Click to collapse
Got Lollipop installed now, just got to cross my fingers while I try and do this the proper way this time