Hey, hope everyone is having a good long weekend. I have a Bell S4 that refuses to boot any 4.3 ROM. I have tried at least 6. I made sure they were all jfltecan (jfltexx ROMs also work), wiped everything, flashed the ROM, flashed 4.3 gapps, wiped cache and dalvik and rebooted. It shows the Galaxy S4 screen then just goes black. Anyone else experiencing this?
What recovery are you using. There are new versions to flash 4.3
I'm using PhilZ Touch 5 because TWRP takes anywhere from 1-3 minutes to pass the TWRP opening screen.
Use TWRP 2.5.02
Sent from my SGH-I337 using XDA Premium 4 mobile app
TWRP won't even go passed the Teamwin screen anymore. It will sit there till I turn it off.
I was having the same issue earlier. Just installed Philz recovery because TWRP 2.6 was taking so long to come on or flash anything. Received the same black screen after flashing multiple roms. I had an old TWRP 2.5 flashable zip file and flashed it from Philz, pulled battery, rebooted to TWRP again, flashed 10.2 nightly and Gapps and it worked.
If you are still having the same problem, let me know and I'll upload the file for you for the TWRP flashable zip.
Thanks & good luck!
Related
I'm not having much success in switching to a 4.3 rom. I would appreciate any feedback I can get. I have repeated these steps multiple times including re-flashing twrp with no luck.*
SGS4 L720 4.2.2 MF9
CF autoroot
GooManager -> TWRP v2.6
Factory reset
Wipe data, cache, dalvik & system
Install pa_jfltespr-3.98.zip
Install pa_gapps-full-4.3.zip
Reboot system and I'm still in *4.2.2 with all data intact.*
TWRP is not wiping or installing but at each step it says successful. What am i missing?*
Try installing twrp 2.5.0.2 here http://forum.xda-developers.com/showthread.php?t=2361378 . Alot of people are reporting problems with 2.6...
Thanks for the quick response. Ok, I downloaded and used Odin to install TWRP 2.5.0.2
I again went through the steps outlined above - wipe, and install but no joy.
I still have all my files intact - nothing was wiped and 4.3 was not installed.
This is so bizarre I have to assume I am royally screwing something up.
I can't seem to find anyone else having a similar problem so that further confirms it must be operator error. But I can not figure it out!
Again, all suggestions would be much appreciated!!!
I just tried flashing cwm in recovery without success. Still stumped.
I have used all available custom recoveries and I stay on 4.3 much of the time. I've had the best luck with latest cwm recovery. I have not had any wipe issues that I know of but what I have had is I do get stuck on Samsung screen after I reboot from time to time on various 4.3 roms. I was told by Cordell to just hold power down, reboot and that has been how ive gotten around that. Currently using Slim Bean beta 3 and have NOT had the issue since updating. I was also told its not rom related but I don't quite understand as beta 3 slim is fine but 2 outa 3 reboots on beta 2 would have me stuck on Sammy screen until another reboot... Glad it hasn't been.an issue since beta 3 for whatever the reason.. anyway thats what my issues have been with 4.3.. I know the 1st thing to go when a phones been flashed too much is recovery but I've been crackflashing since 2010 (daily, sometimes multiple times one day..;o ) and never had a phone crap on me yet. (KnockonWood) Hope you get this resolved.
I suggest maybe odining back and catching ETAs to mf9 then flash supersu and see if that changes anything for you. Just try things and maybe something will fix it. Looking forward to twrp update. I used 2.5.0.2 for a while with no probs but if it is a recovery issue some are having i believe DTroy will address it and either him or Koush would probably know the answer.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Solved!
Thanks for the advice!
Odin to MDC
Forced OTA to MF9
Rooted& TWRP 2.5.0.2
Success!
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Try going here
Tallyphillips said:
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Click to expand...
Click to collapse
you need to try to install the Triforce MJA/4.3.1 kernal/MJA modem all at the same time. IDK what happened on the first try to boot loop you but once you updated the modem to mja you can't flash MF9 modem/kernel on top of it. Try that and let me know.
Tallyphillips said:
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Click to expand...
Click to collapse
You cant go from aosp to tw. You need to go back to stock. Just odin back to mj9 stock. Then reroot and use that rom with philz rec
Sent from my SPH-L720 using xda app-developers app
Hi,
I'm currently running CyanogenMod KitKat version with ClockWorkMod. Since the rom has several bugs and for the past few months they haven't published any updates to my Galaxy s4 I9505, I've decided to switch to WanamLite.
There I found out I need TWRP recovery so I went ahead and downloaded GooManager which installed an outdated version, as I've found out.
I tried wiping my internal storage as recommended but the recovery couldn't mount any of my partitions.
So now CyanogenMod won't boot. I know this issue is fixed in the updated version of TWRP but I'm not sure how to update it without the phone booting (Odin perhaps? It doesn't recognize it currently... Should I move to download mode for it to be detected?)
Anyways, I'm kind of stuck as of now. Any help would be very much appreciated!
Btw I have a question, what's the difference between using Odin 1.85 and 3.09? Why do people still use the old version?
Thanks in advance!!
Neta
Edit:
Alright, now I can't get into recovery either. When I try, I can see the Samsung logo and there's "recovery" written in the top left but then it just restarts again into the same logo without "recovery". I'm starting to lose my cool now. Anyone have any ideas?
Try flashing latest stock through download mode and see if it boots.
Sent from my GT-I9506 using Tapatalk
Flash this recovery through odin. It's TWRP 2.6.3.1. Worked alwys for me.:fingers-crossed:
https://db.tt/SwLvOrZl
Uncheck auto-reboot in Odin.
Thank guys
I got freaked out and just did everything I could to make the phone working again.
I found a thread on XDA explaining how to return your phone to stock version, so I followed it, rooted with auto root, (btw Odin didn't recognize my phone because I used the front usb... how annoying!), then flashed the latest TWRP (2.7.0.1, not 2.6.x.x as GooManager downloaded for me), then booted to recovery and flashed WanamLite.
Everything is working now!
Except one thing - I'm still not able to access recovery mode through physical buttons, only using boot apps. Is this a kernel issue?
Could be some incompatibility since CyanogenMod uses it's own kernel and CWM recovery.
The recovery itself is working fine, but when I try to access it using buttons it shows the Samsung logo with the recovery on the top left, and then reboots again to normal boot.
What do you think?
Thanks!
Hello
I was trying to update my friend´s i9505 to the latest AntaresOne CM12 build, but forgot to flash gapps, and since i coulnd´t for some reason enter CWM (the phone just reboots), i had to flash stock firmware over again so i could start over.
But now the phone isn´t booting even on stock firmware. That usually did the trick.
The wierd thing is that Phils Touch Recovery was working before, but ever since i used Triangle Away to reset binary counter, the recovery won´t boot up anymore.
The only way that i could get into Phils Recovery was to install the TWRP recovery installer, and throught the app i would tell it to flash, and it would reboot into Phils Recovery
Now since system isn´t booting, i can´t install and use the TWRP installer to reboot into recovery mode for me.
Tried to flash stock recovery, the same thing happens: the phone just black screens, vibrates and reboots.
Any ideas of why this might be happening?
Go to stock recovery if you can and wipe data/factory reset. Install stock ROM then.
@guguts
As clearly wrote in 1st post of my thread, you need to do "format /system" before installing ROM's builds starting from 26/11 one and latest ones, including 3/12 and the ones that will come in the future.
I strongly suggest you to take a look again at installation instructions, but this time carefully.
If you need anything else, write directly in its Q&A thread (you can find it in this section) where surely you can be helped more and better
Inviato dal mio GT-I9505
Flash a custom recovery with Odin. Uncheck auto-reboot before flashing.
Then boot into the recovery using the botton combo. Keep holding it as long as it takes to enter recovery.
Hey guys, i managed to work it out.
It was probably a loose vol up or home button, because i didn´t do anything but a few moments later i tried to enter stock recovery and it went fine.
The issue was not with the custom rom (which by the way is great, my friend says its running smooth).
The issue happened because i forgot to do i data wipe after installing the rom and prior to installing the stock rom.
So the stock ROM was trying to load using lollipop data and cache, and thats why it got stuck in the samsung logo.
As soon as i managed to enter stock recovery again, and made a data wipe, the stock room booted fine.
So i tried again, but this time didn´t forget to flash gapps, and even better, now Phils Recovery is booting up normally (go figure...)
So i formated /system and /data, flashed AntaresOne ROM and gapps, and everything went fine.
Just posting here in case anyone in the future goes througyht the same hassle.
Thank you so much for your work Antares.
Its people like you, quarx and pawtip (and many others top developers) that makes this community great.
Hello all, I have an issue with recovery on my i9505 which hopefully someone can assist with?
I'm using the excellent Optimised CM12.1 and had TWRP 2.8.7.2 (f2fs) as my recovery all working fine. I've recently flashed the newest 2015-11-1 ROM over the top (clear cache and dalvik, but not data wipe) and all seemed great.
However, I went to 'reboot to recovery' in order to install exposed and got stuck on the teamwin splash screen of recovery. Every time I tried to power off it would bootloop into the same splash screen!
Using Odin I was able to flash a new recovery (TWRP 2.8.6.0) and reboot the phone as normal. All worked fine until I tried recovery again and found the same issue!
I've now got CWM (6.0.4.7) flashed to see if that would help but nothing is mounted when using that and so I cannot get to the zip files! When attempting to mount within CWM it errors and cannot mount.
I'm open to any suggestions and would like to learn why this is occurring. Let me know if there's any logs or files I can post that would help.
Many thanks in advance!
Stu
StuKeeler said:
Hello all, I have an issue with recovery on my i9505 which hopefully someone can assist with?
I'm using the excellent Optimised CM12.1 and had TWRP 2.8.7.2 (f2fs) as my recovery all working fine. I've recently flashed the newest 2015-11-1 ROM over the top (clear cache and dalvik, but not data wipe) and all seemed great.
However, I went to 'reboot to recovery' in order to install exposed and got stuck on the teamwin splash screen of recovery. Every time I tried to power off it would bootloop into the same splash screen!
Using Odin I was able to flash a new recovery (TWRP 2.8.6.0) and reboot the phone as normal. All worked fine until I tried recovery again and found the same issue!
I've now got CWM (6.0.4.7) flashed to see if that would help but nothing is mounted when using that and so I cannot get to the zip files! When attempting to mount within CWM it errors and cannot mount.
I'm open to any suggestions and would like to learn why this is occurring. Let me know if there's any logs or files I can post that would help.
Many thanks in advance!
Stu
Click to expand...
Click to collapse
Do not use CWM. It's outdated and not compatible with Lollipop.
You could try flashing a stock rom with .pit and re-partition. After that flash TWRP again.
Lennyz1988 said:
Do not use CWM. It's outdated and not compatible with Lollipop.
You could try flashing a stock rom with .pit and re-partition. After that flash TWRP again.
Click to expand...
Click to collapse
Thanks for the advice. I don't like CWM myself.. just tried it as an attempt to get TWRP flashed back properly!
I will go the stock re-flash route as a last resort. I'm sure it will fix the issue but is a little drastic.
What caused this? - is it something to do with the F2FS filesystem? TWRP recovery was working fine in order for me to flash the updated CM12.1 (2015-11-1).