Database Users

Samsung s4 i9505 bootloop

Every time I flash cyamogenmod rom in clockwork mod or twrp on my s4 I get stuck on boot symbol. I follow instructions but always fail please help.

Hi,
This thread is being moved to your own dedicated forum , where the experts may be able to help you better.
Good luck!

JaguarBeast said:
Every time I flash cyamogenmod rom in clockwork mod or twrp on my s4 I get stuck on boot symbol. I follow instructions but always fail please help.
Click to expand...
Click to collapse
1. You have to wipe all (system, data, cache and dalvik) before flash Cyanogen Mod.
2. Boot symbol needs time normally (~ 10 min loading the config).

In what order do you wipe everything ?
I do a factory reset, then wipe cache and finally wipe the dalvik cache

That's it, buddy. With emphasis on "FACTORY RESET".
Let's us know if that worked for ya...

Does it matter what custom recovery you have ?
thundastruck said:
That's it, buddy. With emphasis on "FACTORY RESET".
Let's us know if that worked for ya...
Click to expand...
Click to collapse
Is clockworkmod or team win better ?

TWRP. Certain ROMs will not install with Clockworkmod as the recovery.

I want cyamogenmod 12.1 nightly on my s4
Strephon Alkhalikoi said:
TWRP. Certain ROMs will not install with Clockworkmod as the recovery.
Click to expand...
Click to collapse
I have already downloaded the file and placed it on my internal sd card. Which gapps should I chose ?

Android 5.1.1. Which package you desire is up to you. I personally use the nano package.

Bootloop once again
Strephon Alkhalikoi said:
Android 5.1.1. Which package you desire is up to you. I personally use the nano package.
Click to expand...
Click to collapse
I did a factory reset, wiped the cache and dalvik cache. I flashed cyamogenmod alone and it hasn't booted in 20 minutes. Please help

Let's clarify something. What model number shows up when you enter download mode? Also, is it hanging on the Samsung logo or the boot animation?

Stuck at cyamogenmod logo
Strephon Alkhalikoi said:
Let's clarify something. What model number shows up when you enter download mode? Also, is it hanging on the Samsung logo or the boot animation?
Click to expand...
Click to collapse
It gets stuck at cyamogenmod logo and the download mode model number is Samsung MSM8960

Umm, no. The model number should be GT-I9505 or something similar. Regardless, what GApps package are you using? CM12.1 has trouble with some of the GApps packages and bootloops occur because of it.

Sorry the model is i9505
Strephon Alkhalikoi said:
Umm, no. The model number should be GT-I9505 or something similar. Regardless, what GApps package are you using? CM12.1 has trouble with some of the GApps packages and bootloops occur because of it.
Click to expand...
Click to collapse
I have tried to install cyamogenmod 12.1 alone without gapps but had no success.

Something with your phone isn't right. Either you're missing a step in installing Cyanogenmod, or else your phone's internal storage spaces are not configured correctly. I would recommend starting from scratch, meaning installing the latest stock ROM from your carrier. Once you're satisfied that the S4 is working properly with the stock ROM, install TWRP and then install Cyanogenmod.

Already done that XD
Strephon Alkhalikoi said:
Something with your phone isn't right. Either you're missing a step in installing Cyanogenmod, or else your phone's internal storage spaces are not configured correctly. I would recommend starting from scratch, meaning installing the latest stock ROM from your carrier. Once you're satisfied that the S4 is working properly with the stock ROM, install TWRP and then install Cyanogenmod.
Click to expand...
Click to collapse
I've installed the stock rom(lollipop), rooted my phone and used flashify(Google play app) to download and flash recovery(TWRP). Should I use a cyamogenmod nightly or a stable version ?

That's up to you. Development channel ROMs have a greater possibility of bugs that could stop you cold. Release channel ROMs have fewer bugs but generally lag behind the Development channel in terms of bug fixes and, occasionally, features.
I personally use Optimized CM12.1 from AntaresOne.

Could you recommend a custom rom specifically for s4 i9505 ?
Strephon Alkhalikoi said:
That's up to you. Development channel ROMs have a greater possibility of bugs that could stop you cold. Release channel ROMs have fewer bugs but generally lag behind the Development channel in terms of bug fixes and, occasionally, features.
I personally use Optimized CM12.1 from AntaresOne.
Click to expand...
Click to collapse
So I download the rom zip I want in the root of internal storage, go into recovery and do factory reset, wipe cache + dalvik cache. I choose install and select zip I downloaded. What else did I miss ?
P.S Can you flash gapps later on cyamogenmod if it boots ?

Nothing from what I can see. I simply think that the Cyanogenmod ROM you downloaded didn't like your phone. I've had no issues with Optimized CM12.1, which is why I recommended it.
Re GApps: Yes.

Strephon Alkhalikoi said:
Nothing from what I can see. I simply think that the Cyanogenmod ROM you downloaded didn't like your phone. I've had no issues with Optimized CM12.1, which is why I recommended it.
Re GApps: Yes.
Click to expand...
Click to collapse
Boot loop again XD. I followed the instructions exactly in the link below.
http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696
Must be bad luck or something.

Now what?

Hi guys, new to the Android rooting community and just wanted some help figuring out what's what.
Today I bought a Samsung Galaxy S4, unlocked, I9505. It's on Android 5.0.1 (I believe that's lollipop?). Now I just wondered now that I have rooted it, what do I do now? I've rooted and done nothing else other than check my root permission which I have. I wanted to install a clean, stock Google Play Edition rom and then remove the bloatware from it and use that as my phone. How am I doing that? Do I need to have rooted a specific Android version to install roms? I was reading around about a custom recovery, do I already have that installed from root or is that another thing that I need? :crying:
Any help would be appreciated as I am super new to this having come from iPhone jailbreaking.
Thanks!

You need a custom recovery to install just about any custom rom. Custom recoveries don't from rooting, you have to flash it manually. I recommend TWRP. Just google twrp s4. They also have an installation guide. After you flashed TWRP you can flash one of the GPE roms from the forum. There are 2. One is untouched and the other has slight modifications.

GDReaper said:
You need a custom recovery to install just about any custom rom. Custom recoveries don't from rooting, you have to flash it manually. I recommend TWRP. Just google twrp s4. They also have an installation guide. After you flashed TWRP you can flash one of the GPE roms from the forum. There are 2. One is untouched and the other has slight modifications.
Click to expand...
Click to collapse
Thanks for the reply, at this moment I just need all the info I can get before I do anything! Is TWRP the best? I'm sure "which is the best recovery" is asked a lot, so I'll have a look around. Do they do different things or are the premise of them generally the same? And that's fantastic about GPE, so I won't need to upgrade any higher than 5.0.1?

Dannilad said:
Thanks for the reply, at this moment I just need all the info I can get before I do anything! Is TWRP the best? I'm sure "which is the best recovery" is asked a lot, so I'll have a look around. Do they do different things or are the premise of them generally the same? And that's fantastic about GPE, so I won't need to upgrade any higher than 5.0.1?
Click to expand...
Click to collapse
Just tried installing the JFLTE-GPE latest version using TWRP and it's not worked, I'm stuck in TWRP :/ Any help?

Did you perform a full wipe of the system, data, and cache before flashing gpe?

audit13 said:
Did you perform a full wipe of the system, data, and cache before flashing gpe?
Click to expand...
Click to collapse
Hey, I just looked around and one video I watched did not specify that I needed to wipe System. Just tried wiping System, darvik cache, cache and data so I'll see what happens and let you know if it's worked fingers crossed
EDIT: No, it hasn't worked, I've been kicked straight back into TWRP screen again Any ideas?

Dannilad said:
Hey, I just looked around and one video I watched did not specify that I needed to wipe System. Just tried wiping System, darvik cache, cache and data so I'll see what happens and let you know if it's worked fingers crossed
EDIT: No, it hasn't worked, I've been kicked straight back into TWRP screen again Any ideas?
Click to expand...
Click to collapse
bump

Normally you have to wipe data, cache, dalvik cache and system before flashing a rom. This can either be done manually or as a factory reset from within the recovery. I don't see any reason why it wouldn't boot. Try another kernel. Or you might want to try the AOSP rom by JDC team. It's basically the same as GPE, but without any of the google apps. But those can be flashed. You need to download a gapps package. The most popular seems to be from open gapps. Choose ARM, the android version of the rom and then the type of package. Pico is the smallest and will give you only the google play store.
---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------
And don't change recoveries. The others are outdated. TWRP is the only one up-to-date. You might also try another version of TWRP. The newest is 2.8.7.2 I think.

Latest oreo roms and some problems...

When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:

Which recovery you using

poyraz4558 said:
When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:
Click to expand...
Click to collapse
Please provide specifics of ROM and TWRP Version. Did you load mods? Did you use custom kernel?

I installed this recovery for bootleggers 8.1 rom,
https://androidfilehost.com/?fid=673956719939820462 (twrp 3.2.1.0 It works well),
then I've installed Orangefox recovery for try and I used for long time without any problem,
later I flashed this recovery for Pixel Experience rom
https://androidfilehost.com/?fid=1322778262904027766 (twrp 3.2.3.0),
installed without a problem but a long time stuck in google logo, I rebooted three times a long press power button and the phone opened normally
No problem when using the phone but all times error on recovery.. such as 'vendor, invalid argument, mount error.
Always these errors during the rom installation and wiping..
Now is stock rom installed, I think there are some changes in the new rom because such problems did not happen before,
thank you for your answers and developers

poyraz4558 said:
I installed this recovery for bootleggers 8.1 rom,
https://androidfilehost.com/?fid=673956719939820462 (twrp 3.2.1.0 It works well),
then I've installed Orangefox recovery for try and I used for long time without any problem,
later I flashed this recovery for Pixel Experience rom
https://androidfilehost.com/?fid=1322778262904027766 (twrp 3.2.3.0),
installed without a problem but a long time stuck in google logo, I rebooted three times a long press power button and the phone opened normally
No problem when using the phone but all times error on recovery.. such as 'vendor, invalid argument, mount error.
Always these errors during the rom installation and wiping..
Now is stock rom installed, I think there are some changes in the new rom because such problems did not happen before,
thank you for your answers and developers
Click to expand...
Click to collapse
Okay... I'd recommend one thing.
Install the custom ROM. Then follow flashing procedure and do read the new FAQ posted by the devs. And after that... Try to reflash the recovery.img by pressing install image option. After this... If the problem persists, try to follow the procedure again and check if your recovery image isn't corrupt. Plus don't use the recovery from TWRP.ME

I have a recovery that can solve this problem but you can't restore ROMs you backed up

Phantom Slayer04 said:
Okay... I'd recommend one thing.
Install the custom ROM. Then follow flashing procedure and do read the new FAQ posted by the devs. And after that... Try to reflash the recovery.img by pressing install image option. After this... If the problem persists, try to follow the procedure again and check if your recovery image isn't corrupt. Plus don't use the recovery from TWRP.ME
Click to expand...
Click to collapse
thanks, I understand
I did actually try a second time, just flashed pixel experience rom and twrp 3.2.3.0 recovery on the stock rom - recovery.. same errors are happening and this problems improve only when I install stock rom with QPTS.. I will do clean installation in a short time again, just wonder why there is so much vendor error on recovery...

poyraz4558 said:
thanks, I understand
I did actually try a second time, just flashed pixel experience rom and twrp 3.2.3.0 recovery on the stock rom - recovery.. same errors are happening and this problems improve only when I install stock rom with QPTS.. I will do clean installation in a short time again, just wonder why there is so much vendor error on recovery...
Click to expand...
Click to collapse
Did you wipe the partitions? Did you format data partition?

Phantom Slayer04 said:
Did you wipe the partitions? Did you format data partition?
Click to expand...
Click to collapse
yes I did, including vendor..Today I searched the topics in the forum; return to old rom is not recommended after installing the new rom, I see similar troubles in rom forums..

poyraz4558 said:
yes I did, including vendor..Today I searched the topics in the forum; return to old rom is not recommended after installing the new rom, I see similar troubles in rom forums..
Click to expand...
Click to collapse
If you want to install latest update roms then read this FAQ:https://forum.xda-developers.com/showpost.php?p=77872447&postcount=2325:confused:
if you want to revert to old roms then you have to flash stock nougat rom using qfil and install twrp 3.2.1.0 and install old roms
don't do it wrongly otherwise you will get updater error 7 or can't mount vendor, etc,

Sudhar123 said:
If you want to install latest update roms then read this FAQ:https://forum.xda-developers.com/showpost.php?p=77872447&postcount=2325:confused:
if you want to revert to old roms then you have to flash stock nougat rom using qfil and install twrp 3.2.1.0 and install old roms
don't do it wrongly otherwise you will get updater error 7 or can't mount vendor, etc,
Click to expand...
Click to collapse
Thank you, I learned later that.. That's why i'm using an old rom because sometimes I can't any process on recovery, There are too many errors..

poyraz4558 said:
When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:
Click to expand...
Click to collapse
You should be on latest nougat that is with november security patch. All rom after 14/10/2018 should flash with latest twrp that is 3.2.3.0. all roms before that should be flashed with twrp 3.2.1.0.

sk.vyshak said:
You should be on latest nougat that is with november security patch. All rom after 14/10/2018 should flash with latest twrp that is 3.2.3.0. all roms before that should be flashed with twrp 3.2.1.0.
Click to expand...
Click to collapse
Ok..Which sections will be deleted on twrp 3.2.3.0 during wipe, is vendor partition included ?

poyraz4558 said:
Ok..Which sections will be deleted on twrp 3.2.0.3 during wipe, is vendor partition included ?
Click to expand...
Click to collapse
The thing is with new twrp there is decryption support which was lacked in old. Vendor partition is present in both i think. All the new roms are encrypted by default

[T560] All Android 7 ROMs not working, stuck on bootloop

Hi all,
so I can't install any Nougat ROMs as they all make my device go to bootloop on the first reboot after flashing, and just keeps the device on the boot animation for hours
This includes LOS14.1, DotOS and ViperOS all versions.
When I flash the CM13 ROM (what I'm using now), everything works normally on the first try.
I can't be the only one experiencing this bootloop, anyone else having these issues?
Did anyone else get bootlooped? Did you manage to circumvent the issue?
Any help is appreciated

phayme said:
Hi all,
so I can't install any Nougat ROMs as they all make my device go to bootloop on the first reboot after flashing, and just keeps the device on the boot animation for hours
This includes LOS14.1, DotOS and ViperOS all versions.
When I flash the CM13 ROM (what I'm using now), everything works normally on the first try.
I can't be the only one experiencing this bootloop, anyone else having these issues?
Did anyone else get bootlooped? Did you manage to circumvent the issue?
Any help is appreciated
Click to expand...
Click to collapse
Did you flash magisk or supersu before fist boot?

I tried with and without rooting, of course before flashing the ROMs (and GApps) I would wipe everything except sd card.
Really don't know what's the issue as the majority of people that reported bootlooping on these ROMs managed to get it fixed later, but none of that works for me.
I tried restoring back to 4.4 then trying again, I tried leaving the boot animation until the tablet runs out of battery then trying again, still no luck.
When I flash the CM13 rom from xda, everything works fine on the first try and first boot takes only a new minutes. I also managed to install the CM12.1 and the latest LightROM for the t560. Weird
Anyway I can only hope this gets resolved, willing to try anything as I don't use this tablet for anything relevant. It's the UK version, if that matters.

phayme said:
I tried with and without rooting, of course before flashing the ROMs (and GApps) I would wipe everything except sd card.
Really don't know what's the issue as the majority of people that reported bootlooping on these ROMs managed to get it fixed later, but none of that works for me.
I tried restoring back to 4.4 then trying again, I tried leaving the boot animation until the tablet runs out of battery then trying again, still no luck.
When I flash the CM13 rom from xda, everything works fine on the first try and first boot takes only a new minutes. I also managed to install the CM12.1 and the latest LightROM for the t560. Weird
Anyway I can only hope this gets resolved, willing to try anything as I don't use this tablet for anything relevant. It's the UK version, if that matters.
Click to expand...
Click to collapse
Try to flash rom without gaaps or magisk only base rom

gitanillo87 said:
Try to flash rom without gaaps or magisk only base rom
Click to expand...
Click to collapse
Make sure the ROM is for your Device. T560NU has a different chip set that the LTE model and you can't interchange roms.

@gitanillo87
Try to flash rom without gaaps or magisk only base rom [\QUOTE]
I did, still not working unfortunately
@magicmckinney Make sure the ROM is for your Device. T560NU has a different chip set that the LTE model and you can't interchange roms. [\QUOTE]
yeah all these roms are for my device (T560)
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Flash my stock rom,with TPRW and later flash any nougat rom

First of all flash clean stock rom using Odin
-Install TWRP
-Factory reset
-Install CM13 and gapps (root optional)
-Wait to boot and pass all the steps in the initial setup
-When tablet completely booted reboot to TWRP
-Install any Android 7 rom ang gapps without factory reset
-Reboot
-Cross fingers and eventually it will boot!!!

"No OS installed" after successful custom ROM flash

Hey, I'm trying to flash Lineage OS onto my Galaxy A20e (SM-A202F) and after I flash it from an SD card onto the system image partition, it says [IMAGE FLASH COMPLETED]. When I press reboot system from there, it tells me I have no OS installed. Trying to reboot anyway puts me in a bootloop. To get the phone working I need to flash the stock OS on to the phone.
I've tried a few versions of Lineage for the A20e to no avail. I have rooted the phone with Magisk and wiped the system, data, cache, and Dalvik, with the same result every time. I can't seem to find this problem mentioned anywhere else.
I've been at this for days and would appreciate any suggestions, cheers.

fixed by @hainguyenthao, thanks ^-^

turtpipchim said:
Hey, I'm trying to flash Lineage OS onto my Galaxy A20e (SM-A202F) and after I flash it from an SD card onto the system image partition, it says [IMAGE FLASH COMPLETED]. When I press reboot system from there, it tells me I have no OS installed. Trying to reboot anyway puts me in a bootloop. To get the phone working I need to flash the stock OS on to the phone.
I've tried a few versions of Lineage for the A20e to no avail. I have rooted the phone with Magisk and wiped the system, data, cache, and Dalvik, with the same result every time. I can't seem to find this problem mentioned anywhere else.
I've been at this for days and would appreciate any suggestions, cheers.
Click to expand...
Click to collapse
try my kernel
A20e Root,Kernel, TWRP and custom ROM
Root & TWRP from Xyn XDotnest https://forum.xda-developers.com/galaxy-a20/development/recovery-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767 Orange Fox Recovery from @Royna...
forum.xda-developers.com

turtpipchim said:
fixed by @hainguyenthao, thanks ^-^
Click to expand...
Click to collapse
can I ask how was it fixed? I have the same problem with A6+ Samsung device. thanks

turtpipchim said:
fixed by @hainguyenthao, thanks ^-^
Click to expand...
Click to collapse
How?