Hi!
I had a g900x phone. I flashed it with Omega rom, but got stuck in bootloop. I installed other TouchWiz roms and even tried the nandroid restore but I always get stuck in bootloops.
I tried reinstalling the pit with odin, but that did not change anything.
I installed CM11 and the phone booted without issue. I tried other aosp roms and they all worked without issues.
Another weird issues is that when I switch off the phone then plug it, a grey battery appears, except with aosp roms.
Any one knows what is wrong and how I can once more install a stock or TW rom?
Found this http://forum.xda-developers.com/showthread.php?t=2566816
Not the same handset, but will give it a try.
coami said:
Hi!
I had a g900x phone. I flashed it with Omega rom, but got stuck in bootloop. I installed other TouchWiz roms and even tried the nandroid restore but I always get stuck in bootloops.
I tried reinstalling the pit with odin, but that did not change anything.
I installed CM11 and the phone booted without issue. I tried other aosp roms and they all worked without issues.
Another weird issues is that when I switch off the phone then plug it, a grey battery appears, except with aosp roms.
Any one knows what is wrong and how I can once more install a stock or TW rom?
Click to expand...
Click to collapse
I would suggest installing a different kernel.
SM-G900W8, 0x1
I have. But only aosp kernels work. Offical ones and TouchWiz based kernels result in bootloops.
coami said:
I have. But only aosp kernels work. Offical ones and TouchWiz based kernels result in bootloops.
Click to expand...
Click to collapse
Are you using the latest bootloaders and modems?
What actual version do you have 900?
What recovery do you use?
SM-G900W8, 0x1
It is a g900x (demo)
I root with CF-Auto-Root-klte-kltexx-smg900f.tar.md5 using Odin3 v3.09
For recovery philz_touch_6.57.8-klte.tar.md5
I tried:
- the official Samsung rom g900f xef from sammobile http://www.sammobile.com/firmwares/download/37911/G900FXXU1ANJ1_G900FOXX1ANJ1_XEF.zip/ I deleted some files and renamed it ldu900x.tar by following this tutorial http://forum.xda-developers.com/showthread.php?t=2733083
- Omega http://omegadroid.co/samsung-galaxy-s5-g900f/
- the stock version inside Omega
- Samsung Galaxy S5 G900F - Alliance ROM
- Pyrana V0.2 SM-G900F-NJ1 Aroma
And the all end up in bootloops
But aosp
- CM 11 http://download.cyanogenmod.org/?device=klte
- XtreStoLite http://downloadandroidfiles.org/fil...te/XtreStoLite_ROM_v1.2.1_XXU1ANE4-signed.zip
Booted without issue. It also solves they grey battery issue when phone is off and plugged.
One thing that I did notice is that both CM and xtrestolite are 4.4.4 while the others are 4.4.2 Not
ragz said:
I would suggest installing a different kernel.
SM-G900W8, 0x1
Click to expand...
Click to collapse
Sorry, I confused rom and kernel for a moment. You were right, installing a Kernel did work.
Just need to find an official Samsung one since the one I used says "kernel is not seandroid enforcing"
coami said:
Sorry, I confused rom and kernel for a moment. You were right, installing a Kernel did work.
Just need to find an official Samsung one since the one I used says "kernel is not seandroid enforcing"
Click to expand...
Click to collapse
Seandroid not enforcing is normal and no problem, it is booting up right.
SM-G900W8, 0x1
Solved: Bootloops with TouchWiz Roms
Yes but I really do not want to have it. And problem solved:
I downloaded Full-S5-SM-G900F-DUMP.zip from http://forum.xda-developers.com/showthread.php?t=2696410
Took the boot.img and put it in .tar file with Total Commander and problem solved
Related
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!
After months of using my S4, I decided to flash custom ROM and kernel. Unfortunately, after flashing KT-SGS4 kernel, my phone gets stuck in Galaxy S4 logo and keeps flashing blue LED. I've tried using CM11 and AOKP, same results.
I hope, someone know how to fix it, thanks!
Mastirion said:
Hi!
After months of using my S4, I decided to flash custom ROM and kernel. Unfortunately, after flashing KT-SGS4 kernel, my phone gets stuck in Galaxy S4 logo and keeps flashing blue LED. I've tried using CM11 and AOKP, same results.
I hope, someone know how to fix it, thanks!
Click to expand...
Click to collapse
You have to factory reset when installing a custom rom
MrAndroid12 said:
You have to factory reset when installing a custom rom
Click to expand...
Click to collapse
I know, I'm always doing cache and data wipe. Roms are working correctly, but when i try to change kernel, this happens.
Then you are flashing the wrong kernel. There are 3 different types of that kernel.
Lennyz1988 said:
Then you are flashing the wrong kernel. There are 3 different types of that kernel.
Click to expand...
Click to collapse
I tried all of them in case if this one was wrong, maybe if there is said aosp, aokp is out of reach.
I need to service my device due to GPS problems.
Warranty would be most probably void if they find any traces of custom ROM installations.
I've install stock original stock ROM using ODIN.
As far as I know No Knox was ever installed on my device.
Would the lab be able to discover any traces of custom ROM installations?
How can I check that?
Thanks!
amir77a said:
I need to service my device due to GPS problems.
Warranty would be most probably void if they find any traces of custom ROM installations.
I've install stock original stock ROM using ODIN.
As far as I know No Knox was ever installed on my device.
Would the lab be able to discover any traces of custom ROM installations?
How can I check that?
Thanks!
Click to expand...
Click to collapse
Hi mate,
go to download mode if there is no mention at all of knox , then you are knox free ...your warranty is ok , if there is any mention of knox there check if the knox bit is set to 0x1 if so your warranty bit is set., if not then you are ok
I have always careful to install only Knox free ROMS, so no Knox mention at all.
The stock ROM is Android 4.2.2 prior to Knox.
Will they be able to find somehow any other traces of those ROM's ?
amir77a said:
I have always careful to install only Knox free ROMS, so no Knox mention at all.
The stock ROM is Android 4.2.2 prior to Knox.
Will they be able to find somehow any other traces of those ROM's ?
Click to expand...
Click to collapse
hi,
If you flashed rom with Odin , and you kept your bootloader at all times in 4.2.2 and there are no traces at download mode.....they will not find out
I did flashed with Odin, but I don't know if I kept the bootloader in 4.2.2 at all times.
In the past the custom ROM's were 4.4.3, but after the Odin stock ROM flashing, I never installed in ROM/bootloader/root etc. Is that suffice?
amir77a said:
I did flashed with Odin, but I don't know if I kept the bootloader in 4.2.2 at all times.
In the past the custom ROM's were 4.4.3, but after the Odin stock ROM flashing, I never installed in ROM/bootloader/root etc. Is that suffice?
Click to expand...
Click to collapse
If you flashed a 4.2.2 stock rom with odin and had no errors at all and settings /about device shows a 4.2.2 rom then you have a 4.2.2 bootloader...there is no way to flash a older bootloader on top of a newer one....
I did flash stock ROM with Odin, and had no errors at all, and the about device shows a 4.2.2, BUT I had several ROMs with 4.4.3, such as Omega, and also Philz touch CWM.
So it seems that I was able to flash older bootloader over newer one. Am I wrong?
Sorry if I'm asking to much questions.. just trying to understand that.
Thanks again!
amir77a said:
I did flash stock ROM with Odin, and had no errors at all, and the about device shows a 4.2.2, BUT I had several ROMs with 4.4.3, such as Omega, and also Philz touch CWM.
So it seems that I was able to flash older bootloader over newer one. Am I wrong?
Sorry if I'm asking to much questions.. just trying to understand that.
Thanks again!
Click to expand...
Click to collapse
no problem
Custom roms do not have bootloaders only stock roms , there is no way ( yet) to flash a 4.22 bootloader on top of a 4.3 bootloader...so if you have right now a stock 4.2.2 firmware you never flashed a 4.3 bootloader
Omega never have bootloaders in their rom
OK got it!
I never flash stock 4.3.x ROM, hence bootloader remains 4.2.2.
Thanks so much!
Guys, im wondering if someone can help me to get out of bootloop. I just installed AEL kernel on my SM-N910G and now its bootlooping.
It says kernel is not seandroid enforcing set warranty bit: kernel.
Can you help me?
That happened to me flashing stock ROM via odin, so I searched for other version of odin, also I was using a non Samsung USB cable(no idea if this was the issue), reflashed ROM and wahla no more bootloop.
see this thread
Goodluck
homer285 said:
That happened to me flashing stock ROM via odin, so I searched for other version of odin, also I was using a non Samsung USB cable(no idea if this was the issue), reflashed ROM and wahla no more bootloop.
see this thread
Goodluck
Click to expand...
Click to collapse
Im kinda new to rooting so what I have to do is download stock ROM and flash it through odin? And btw where to get stock ROM?
Either stock ROM or Kernel, available from Samsung, Sammobile, XDA etc.
Hey guys, I'll keep it short. I was rooted, installed TWRP, running Simple Rom and was just feeling to flash erobot. Flashed it doing full wipes and then rebooted, cool. Got to the samsung logo and within a second back to the note 4 screen. Okay I said, maybe the file I downloaded was corrupted or I installed it wrong. Did it over again, this time trying a few variations in the aroma installer (not installing xposed) thought maybe that was the problem. Bam same issue.
No worries I still had the old simple rom on the sd card. Went back with the same install and what do you know, that rom is now in a bootloop as well. Tried flashing through odin but I always get a nand write failed to start or something like that. Tried 3 different usb ports and same issue.
Am I missing something? Any advice would be greatly appreciated.
So you are using the Exynos model? Last I checked there is this OJ5 bootloader which can't be downgraded from!
ithehappy said:
So you are using the Exynos model? Last I checked there is this OJ5 bootloader which can't be downgraded from!
Click to expand...
Click to collapse
Yes I'm on the exynos model. So what did I do wrong, I went from lollipop to a lollipop rom. I didn't go back to KK or anything. What do I have to do?
guys help me im having bootloop because i was trying to install the su suser .in my note 4 Note 4 N910C lolipop in tw recovery still boot loop? because i want to root it .send me a maasage thank you
Anyone?
Did you flash a kernel for your variant after flashing the ROM?
No but that is my next move today, had a feeling it might be the problem, I'll try it and report back.
Oj5 bl doesn't let the flash of older rom even lp 5.1.1 older then oj5 but erobot 12 and 13.4 are newest then oj5 so it must be something else like the supersu v2.65 have issues with some costum kernels try to flash v 2.45
radium56ad said:
Oj5 bl doesn't let the flash of older rom even lp 5.1.1 older then oj5 but erobot 12 and 13.4 are newest then oj5 so it must be something else like the supersu v2.65 have issues with some costum kernels try to flash v 2.45
Click to expand...
Click to collapse
Will try that, thanks. On a side note, flashed custom kernel after flashing the ROM and nothing same bootloop.
try this! http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132
migsguerra said:
guys help me im having bootloop because i was trying to install the su suser .in my note 4 Note 4 N910C lolipop in tw recovery still boot loop? because i want to root it .send me a maasage thank you
Click to expand...
Click to collapse
Had the same problem, solved it by flashing cf auto root using ODIN.
can't you just flash the previous rom again??
Enter your recovery and flash your "old" rom