Cliff Notes
Bug during ODIN after failed flash of MDL
battery pull to reset phone after bad flash of MDL
ODIN flash MDB worked fine
Rooted/recovery TWRP worked fine
ODIN flash to MDL worked fine
Rooted/recovery TWRP worked fine
Reboot and NO custom/padlock
wiped/reset and flashed new ROM
STILL have root/recovery and custom ROM/Kernel work 100%
restored old (that had Custom/Padlock on boot) backup
STILL no custom/padlock, but everything works
Had Goldeneye ROM 1.3, Ktoosez kernel running perfectly. Went to flash Goldeneye ROM 2.0 and Ktoonsez kernel, and decided to do a clean install, so used ODIN to go back to UCUAMDB baseband. At first i tried to flash a good copy of UCUAMDL, but it kept failing, and i used ODIN to flash UCUAMDB over the *still technically part done at 'download' mode* UCUAMDL, when the UCUAMDB flash worked, I then used 3-Way tool to Root/install TRWP, ODIN flashed to UCUAMDL, used 3-Way again to Root/install TWRP, when it booted, there was no padlock screen. I had to reinstall (rerooted too, to be safe) TWRP, then wiped/reset and flashed Goldeneye 2.0 and Ktoonsez kernel.
The padlock 'custom' screen is gone. I have root. I have custom recovery. I dont know why or how. So i made a full Nandroid backup. I then wiped/reset, and restored the Goldeneye 1.3 backup i had (also TiBU with all data/apps), i STILL have root, recovery, everything back to 1.3, and NO CUSTOM/PADLOCK screen.
I have no idea why; but i know it might be useful to figure out what happened so others with custom rom/kernel can get rid of the Custom/Padlock image as well; i couldnt get rid of it via other methods, and had given up. This happened randomly. Again, i have root, recovery, and custom ROM/Kernel working perfectly, i can even reflash 2.0 via recovery and not get Custom/Padlock screen, or restore the 2.0 backup and no Custom/Padlock screen.
I dunno what went wrong here...
1) I have GT-I9505 (SSN: -I9505GSMH). I installed Galaxy S4 toolkit
2) Reboot into download mode. Used toolkit/Odin to root phone. Boots up. See SU.
3) Reboot into download mode. Used toolkit/Odin. Flashed TWRP Recovery
4) Phone boots up normal. Reboot into TWRP recovery. Did a factory Reset. Format.
5) Installed Zip (Latest Omega 9.0 ROM), unchecked the things I didn't want to install. Completed install, no errors reported. Rebooted.
6) Phone stuck on Samsung boot screen. I left it overnight thinking sometimes it may take 15 mins to boot system after new install.
7) Woke up, battery dead. Tried to charge phone. No charging indicators when plugged in. With whatever juice I had left I booted into TWRP recovery, it starts to charge again as I see the % batter increase after 5 mins.
-=-=-=-=- Did the Following to try to repair
a) Reinstalled Omega, this time leaving alll options on. Rebooted, stuck in Samsung boot
b) Flashed Phil CWM touch recovery, did complete wipe to install new ROM. Rebooted into Phil recovery. Flashed OMEGA. Reboot, stuck in Samsung boot.
c) Rebooted into Phil recovery, installed echo ROM, rebooted. Black screen. Rebooted into Phil. This time cannot get into recovery.
d) Started panicking, used Odin flashed TWRP. Would not flash. Something displayed about PIT error. Flashed Phil again. Reboot into recovery, WORKS! (recovery only). Went back into Download mode flashed TWRP. Rebooted, also WORKS!. Did a factory wipe. During wipe there was an error. Format, factory reset, error during wipe. Flashed OMEGA. Reboot. Stuck on samsung boot loop.
e) Downloaded official Samsung kernal for i9505 thinking it was the full flash rom. Flashed with ODIN (hoping to put everything back to factory). Completed flash, phone boots. I get OMEGA ANIMATION!!! Waited for 15 mins. Stuck on Animation. Reflashed TWRP. Rebooted, installed OMEGA...again. Stuck on samsung boot screen.
-=-=-= Kinda frustrated. What did I do wrong in the beginning?
There are so many official roms for the S4 based on region. What can I do to put it back to factory again? I purchased phone in Australia @ Samsung store. I figured download the Australia ROM but there are like 5 of them 4 being network branded roms I think. THe other one XSA is unbranded?
I tried searching for help but so far nothing works.
omega ROM or any other custom ROM uses single CSC so before booting into system you must boot into stock recovery to apply CSC of that ROM, download stock recovery of that firmware the ROM was built from
after applying CSC it will work if not flash Omega 9.0 again , it will work :good::good:
arnob_xperia said:
omega ROM or any other custom ROM uses single CSC so before booting into system you must boot into stock recovery to apply CSC of that ROM, download stock recovery of that firmware the ROM was built from
after applying CSC it will work if not flash Omega 9.0 again , it will work :good::good:
Click to expand...
Click to collapse
Thanks for responding
So I take it when I did the full factory wipe and FORMAT the formatting part erased the CSC?
The steps are:
1) Find stock recovery of the original ROM OMEGA was built on. Use odin, flash that specific recovery. ( I might as well do a complete flash of the original stock firmware)
2) Use odin, replace recovery with TWRP, flash Omega this time no formatting
Reboot should be ok?
kabloomz said:
Thanks for responding
So I take it when I did the full factory wipe and FORMAT the formatting part erased the CSC?
The steps are:
1) Find stock recovery of the original ROM OMEGA was built on. Use odin, flash that specific recovery. ( I might as well do a complete flash of the original stock firmware)
2) Use odin, replace recovery with TWRP, flash Omega this time no formatting
Reboot should be ok?
Click to expand...
Click to collapse
first use CWM or TWRP or whatever you want and format everthing
flash a fresh firmware(latest i prefer)
then flash stock recovery via odin of the built version what v9 was used, simply reboot to recovery and it will say MULTI CSC APPLIED from fresh frimware you used
then flash TWRP/CWM and flash v9
again simply reboot to recovery and it will say MULTI CSC APPLIED from V9
it will reboot, you must need to apply CSC to boot your phone
I can confirm this!
I was trying to flash Omega 9 on top of jamal's 4.3 and my phone always booted to recovery. So I restored my stock touchwiz (no custom recovery or even root) nandroid backup and applied Omega 9: it worked!
douglascamata said:
I was trying to flash Omega 9 on top of jamal's 4.3 and my phone always booted to recovery. So I restored my stock touchwiz (no custom recovery or even root) nandroid backup and applied Omega 9: it worked!
Click to expand...
Click to collapse
thats right stock recovery boot is needed to apply CSC
problem
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
macoy_412 said:
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
Click to expand...
Click to collapse
Do you have an IMEI showing on your phone? What recovery did you use to flash Omega?
It matters, because some recoveries will screw it up.
Do you try to install with Philz recovery?
Sent from my GT-I9505 using xda premium
macoy_412 said:
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
Click to expand...
Click to collapse
At this point I think it is the CSC issue arnob-xperia mentioned.
This is how I corrected my issue.
1) Omega v10 uses newer base FW. In their description it tells u. (ex: ver 9 uses XUBMG5). Search on the i9505 forums here. I can't link for some reason I can't see any of the stickied threads, especially the one listing all avail stock firmwares.
Flash into Philz or TWRP do a complete wipe of everything including data. etc.
You MUST download the full firmware, Not just the smaller kernel and recovery or csc. The full stock fw is usually over 1.6 GB. Anything around that range and u got the right one for Odin flash with the md5. Use Odin to flash. I used 1.85 and it was fine.
2) Once done it will reboot and in theory you are stock everything. At this point, for me somehow the phone got stuck in fricken boot loop. I pulled out battery, reboot into stock recovery and made sure I saw the multicsc. Rebooted. Still boot loop.
After hours of doing all sorts of things and putting the phone aside for a day. Came back, flashed the stock fw again using Odin. Reboot into recovery. Check the multi csc. Reboot. Stuck in boot loop. Reboot to download mode. Then I decided to ROOT the phone for ****s and giggles. This worked!
Phone booted.
3) Now you have stock (for that specific OMEGA fw) w/ the matching CSC. From here on follow OMEGA flash instructions for the specific things it tells u to wipe. DO NOT DO A FULL WIPE/FORMAT like I did (what got me in the mess to begin with).
** For Galaxy S3s, S4s, for some reason I've always had problems with TWRP. I had better luck using Philz. Everyone's personal experience varies on this one.
** I think the problem has to do with the CSC which handles specific region phone and carrier modes. This doesn't mean that it won't work if you use a diff region CSC. Just that it has to match the FW base you are using otherwise you have all sorts of problems. After that you can go in android and setup your APNs etc if you have probs with data. I didn't have this problem and was testing using the UK fw base on AU network sim.
*** Why does Samsung make things so damn complicated. I remember way back in 2k3 using fricken ODIN (samsung flashing utitility) to flash **** and it was the same setup as now. This whole crap about CSC pairing is a bit annoying. It is bad enough there are 6+ variations of S4s lol...
Hope this helps.
wifi problem
kabloomz said:
At this point I think it is the CSC issue arnob-xperia mentioned.
This is how I corrected my issue.
1) Omega v10 uses newer base FW. In their description it tells u. (ex: ver 9 uses XUBMG5). Search on the i9505 forums here. I can't link for some reason I can't see any of the stickied threads, especially the one listing all avail stock firmwares.
Flash into Philz or TWRP do a complete wipe of everything including data. etc.
You MUST download the full firmware, Not just the smaller kernel and recovery or csc. The full stock fw is usually over 1.6 GB. Anything around that range and u got the right one for Odin flash with the md5. Use Odin to flash. I used 1.85 and it was fine.
2) Once done it will reboot and in theory you are stock everything. At this point, for me somehow the phone got stuck in fricken boot loop. I pulled out battery, reboot into stock recovery and made sure I saw the multicsc. Rebooted. Still boot loop.
After hours of doing all sorts of things and putting the phone aside for a day. Came back, flashed the stock fw again using Odin. Reboot into recovery. Check the multi csc. Reboot. Stuck in boot loop. Reboot to download mode. Then I decided to ROOT the phone for ****s and giggles. This worked!
Phone booted.
3) Now you have stock (for that specific OMEGA fw) w/ the matching CSC. From here on follow OMEGA flash instructions for the specific things it tells u to wipe. DO NOT DO A FULL WIPE/FORMAT like I did (what got me in the mess to begin with).
** For Galaxy S3s, S4s, for some reason I've always had problems with TWRP. I had better luck using Philz. Everyone's personal experience varies on this one.
** I think the problem has to do with the CSC which handles specific region phone and carrier modes. This doesn't mean that it won't work if you use a diff region CSC. Just that it has to match the FW base you are using otherwise you have all sorts of problems. After that you can go in android and setup your APNs etc if you have probs with data. I didn't have this problem and was testing using the UK fw base on AU network sim.
*** Why does Samsung make things so damn complicated. I remember way back in 2k3 using fricken ODIN (samsung flashing utitility) to flash **** and it was the same setup as now. This whole crap about CSC pairing is a bit annoying. It is bad enough there are 6+ variations of S4s lol...
Hope this helps.
Click to expand...
Click to collapse
I did flash the Omega v9.1 and applied the wifi fix but the wifi is still broken. I tried unrooting it by flashing the original rom and formatting the data but the wifi is still broken. I can't turn it on. Thanks for the instructions anyways. ))
no pit partition
also, when i tried to root it again, it fails and says there is no PIT partition..
Where is the csc in TWRP so I can so what ones on the phone..??
What stock firmware can I use for a Orange Network in the UK.
GT-i9505 stuck on boot when upgraded from omega v16 to v21
Hello guys,
Well, I followed all the instructions and flashed new bootloader and new modem and after that I installed omega v21 with Full swipe. After that I ended up stuck in boot animation. :s What to do? I already tried to re-flash modem and bootloader, updated CWM and tried to re-install that v21 and after that I flashed twrp over cwm and tried to re-install v21 but always I ended up stuck in that boot animation. :S All installs were successful, but it just wont boot.
What to do?
Hopefully you understand my problem.
Cheers from Finland!
Nico
EDIT:
Ok, I flashed omega rom v19 with full wipe and tried to boot. Didnt work, but then I installed Kies to my computer, opened Kies, Plugged USB in and started my phone and then Kaboom! It booted. What exactly happened there?
BizK1d said:
Hello guys,
Well, I followed all the instructions and flashed new bootloader and new modem and after that I installed omega v21 with Full swipe. After that I ended up stuck in boot animation. :s What to do? I already tried to re-flash modem and bootloader, updated CWM and tried to re-install that v21 and after that I flashed twrp over cwm and tried to re-install v21 but always I ended up stuck in that boot animation. :S All installs were successful, but it just wont boot.
What to do?
Hopefully you understand my problem.
Cheers from Finland!
Nico
EDIT:
Ok, I flashed omega rom v19 with full wipe and tried to boot. Didnt work, but then I installed Kies to my computer, opened Kies, Plugged USB in and started my phone and then Kaboom! It booted. What exactly happened there?
Click to expand...
Click to collapse
Hi, I am having the same problem. First I installed the new firmware (NA5) and modem, tested it with the Omega ROM v21 and boot caught on so now tested the rom Fox Hound 4.1 and am having the same problem.
Kies tested this option but have not had the same luck as you. = /
Anyone know the reason? The rom Google Edition Jamal runs on my phone.
i9505
I flash the stock firmware on the phone.
Installed root and safestrap recovery.
Booted into safestrap, wiped stock slot and installed Goldeneye by selecting all of the safestrap options.
Unselected reboot option and installed NB1 modules.
Rebooted into system
After this when it boots up, it shows safestrap disabled. If I wait, it goes to a black screen for a while and then reboots again into stock recovery. If I reboot again, it repeats the same thing over again. Yesterday, I got it to work using this same steps if I remember correctly, but the wifi wasn't working, so I needed to flash to stock again and try again making sure to install the modules.
UPDATE: I tried again, but with the GE-XXUGNK4-49.2 rom. I first tried to flash it to stock slot, but it didn't work. Then, I tried again by creating a new slot, flashing the rom to there. It didn't work, so I deleted it and tried the stock slot again. It worked this time. Now I'm going to try this again, but with the GE-XXUHOD7-53 rom.
UPDATE2: It didn't work. I'm not sure what's going on. It flashed just fine yesterday. I'm going to try again, but without wiping stock slot before installing.
UPDATE3: Didn't work. I'm so tired of this. Does anyone have any idea what's happening with this?
UPDATE4: I got it to work! I followed the safestrap instructions for GE EXACTLY. The thing that was throwing me off was that I thought I had to install the NB1 kernel and not the OC3 since I have NB1, but I did everything OC3. Also, I have no idea how I got it to work yesterday. I'm pretty sure all I did was just install and run.
Hi,
I have a SM-N900 Exoyns device. Whenever I flash any rom on it using a recovery (I have tried both CWM and TWRP) post flashing the phone doesn't turn on. I have tried CM12.1, Resurrection and Pekaka roms. Here are the steps I have tried.
1. Use Odin to first get Stock ROM
2. Boot phone up and transfer rom to the device
3. Install recover using Odin
4. Go to reocvery (CWM or TWRP) and install the zip (After formating /system and /data)
5. Reboot phone
I tried this with 3 custom roms and none seem to then boot up the phone. When the above process finishes and phone reboots I get the SM-N900 text and then when boot animation should come, nothing happens. The display is blank and stays that way.
I can however flash stock android using Odin as many times I want.
Any idea why the phone is behaving this way? Thanks
Blasphy62 said:
Hi,
I have a SM-N900 Exoyns device. Whenever I flash any rom on it using a recovery (I have tried both CWM and TWRP) post flashing the phone doesn't turn on. I have tried CM12.1, Resurrection and Pekaka roms. Here are the steps I have tried.
1. Use Odin to first get Stock ROM
2. Boot phone up and transfer rom to the device
3. Install recover using Odin
4. Go to reocvery (CWM or TWRP) and install the zip (After formating /system and /data)
5. Reboot phone
I tried this with 3 custom roms and none seem to then boot up the phone. When the above process finishes and phone reboots I get the SM-N900 text and then when boot animation should come, nothing happens. The display is blank and stays that way.
I can however flash stock android using Odin as many times I want.
Any idea why the phone is behaving this way? Thanks
Click to expand...
Click to collapse
Same problem here
What do you mean by stock? Are you trying to flash stock samsung firmware in odin but it has a problem?
Well it sounds to me that you are not even rooted dude. Flash the SuperSU zip from recovery, then you will be rooted. I don't know exactly which file to flash for Exynos models, but Google should be able to tell you.
I have searched and can not seem to find a solution
Here is where I am at:
Odin back to stock 4.4.2
Root with Towel Root
Install SuperSU, Update, and Disable KNOX
Install busy box
Install SafeStrap
Install Recovery
Boot into SafeStrap Recovery
Create Backup, Create a Partition and active Rom Slot 1
Wipe System, Cache, Data
Install Zip via External Card
Install goes perfect every time
Reboot
Phone gets stuck on the "Samsung Galaxy S5" screen
I can get into the stock recovery (not safestrap) and Download Mode
I then Odin back to stock and try again
I have tried 4 times and 4 different Roms. Has to be something I am missing
would using Flashfire possibly fix this?
EDIT:
Current set up
Android 4.4.2
Kernal 3.4.0
Build KOT49H.G900VRU1ANCG
update: Same problem with flashfire....
update 2: Could have been bad/wrong kernel. Going to odin to 5.0 and see what happens
67speeda said:
I have searched and can not seem to find a solution
Here is where I am at:
Odin back to stock 4.4.2
Root with Towel Root
Install SuperSU, Update, and Disable KNOX
Install busy box
Install SafeStrap
Install Recovery
Boot into SafeStrap Recovery
Create Backup, Create a Partition and active Rom Slot 1
Wipe System, Cache, Data
Install Zip via External Card
Install goes perfect every time
Reboot
Phone gets stuck on the "Samsung Galaxy S5" screen
I can get into the stock recovery (not safestrap) and Download Mode
I then Odin back to stock and try again
I have tried 4 times and 4 different Roms. Has to be something I am missing
would using Flashfire possibly fix this?
EDIT:
Current set up
Android 4.4.2
Kernal 3.4.0
Build KOT49H.G900VRU1ANCG
Click to expand...
Click to collapse
I think the problem may be you are trying to use the ROM slot. I thought I read that you are supposed to flash ROMs in the stock slot with safestrap.
Thank you for the help
I fixed it but not really sure how.
I THINK it was messed up because I had the wrong Kernel
Here is what I did:
Flashed latest Lollipop with Odin (on parrells on a Mac, worked really well)
Followed the KingRoot Guide to root phone
After a few attempts got root back
Installed the Rom suggested in the the Kingroot Thread
Found some script on XDA to debloat
I really wanted to try the toxic rom but going to play it safe for now...
ROM slot 1 is your problem, as it isn't supported on our devices.
Flash to stock slot only. Ignore the ROM slots.
If you did indeed have the wrong kernel flashed, you would never successfully boot.
Sometimes you also have to wipe cache and dalvik cache again after installing a ROM.