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
Guys I know there are a ton of threads with this problem but no matter what I try, i'm still stuck on a boot loop.
So basically I had PA Rom 3.99 RC2 on my nexus and everything was fine. I then tried to flash PA AOSP kit kat build
but my phone would not boot so I went with a factory image occam 4.3 Phone booted and all was good. I was liking the
stock experience and then about 4 days later after a reboot, phone got stuck on the boot animation X. It would not get out of it
so I decided to flash PA Rom 3.99 rc2 again via ADB push zip. factory reset, installed the rom and gapps, wiped caches and thought i was good to go. Well the phone again would not get past the boot animation of PA.
i then decided to go with the Factory image occam 4.3 via fastboot and installed it and everything. Again stuck on the X. So then I tried PSX rom 4.3 again via adb push, did my factory reset and flashed the rom and gapps and superSu. Also got stuck on the boot animation. Left it for over 2 hours bootlooping and nothing.
Going crazy I went and fastboot the 4.2.2 JDQ39 img and downgraded bootloader, baseband. Installed it and again, stuck on the X animation. just hangs there.
Any help? i don't know what else to try, currently using my HD2 and it is sooo slow :cyclops:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
badboy47 said:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion but still nothing. Updated CWMR to 6.0.4.3 and tried the 4.3 stock image. Still hangs on bootup. android file transfer recognizes the device is plugged in via usb but just gives me the error "could not connect to device"
Oh man I don't know what's wrong with my nexus
bump bump
I'm having this same issue, and it happened just like you. I flashed CM 10.2 nightly 20131114 this morning and I tested it to make sure everything was working. I decided to reboot the phone, and after that I keep getting stuck at the boot animation no matter what I did. To no avail, I reflashed a working zip, restored a backup, restored another backup, flashed the 4.4 factory image (wiping the entire phone), the 4.3 factory image, and then I read that the 4.2 baseband can fix it, so I flashed the 4.2 factory image. That 4.2 image gets it to boot, but without baseband. Right now I'm trying different radios just to see if I can get service again. If it matters, I was running the hybrid 33/84 radio for T-Mobile's LTE when this happened. Very, very peculiar situation here. I've never had anything like this happen, and especially remain an issue after wiping the entire device. I'm hoping it's not a sudden hardware issue.
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Hmmy 4444 said:
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Click to expand...
Click to collapse
just re-flash 4.2, it'll work. I've been doing that since Monday. but I want kitkat too!!
my device is stuck on the boot animation too. is there a way to reinstall the default 4.3 recovery and just rerun the update or something basic like that? my device was almost at stock before running the update. the only two things: twrp and rooted via recovery. so i thought everything will work fine and now there is no backup...
badboy47 said:
Avoid using twrp recovery.
Click to expand...
Click to collapse
Why?
Just fastboot flash all the image files (boot.img,recovery.img....) from the factory image.
Hi!
I am getting crazy because I cannot understand the reason about this weird behavior.
This morning I got stuck in bootloop (rom pure nexus).
I tried a dirty flash but it didn't work so I made a data factory reset and flashed it again. I had some weird stuff like Bluetooth errors and so on. I restarted the phone and again I got stuck in bootloop.
So I flashed different rom by USB OTG (e.g. Bliss Rom, BEnzo Rom) and the problems are more or less the same: I flash the rom, I boot the rom and I get weird errors (e.g., I cannot use Titanium Backup) and if I restart the phone I got stuck in bootloop.
What is going on? Is it possible I have problem with the internal SD Card?
Thank you
sounds like your system is fcucked currenty. should probably boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
Try booting up after that.
e753 said:
Hi!
I am getting crazy because I cannot understand the reason about this weird behavior.
This morning I got stuck in bootloop (rom pure nexus).
I tried a dirty flash but it didn't work so I made a data factory reset and flashed it again. I had some weird stuff like Bluetooth errors and so on. I restarted the phone and again I got stuck in bootloop.
So I flashed different rom by USB OTG (e.g. Bliss Rom, BEnzo Rom) and the problems are more or less the same: I flash the rom, I boot the rom and I get weird errors (e.g., I cannot use Titanium Backup) and if I restart the phone I got stuck in bootloop.
What is going on? Is it possible I have problem with the internal SD Card?
Thank you
Click to expand...
Click to collapse
When flashing these ROMs are you wiping properly (system, data, cache, dalvik cache) first? You should try going back to stock, but you'll need to do more than the previous person who replied has said. First you need to wipe data in TWRP, then you need to flash the full factory images, not just the ones mentioned above. You'll find instructions for that in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
After these steps it seems working.
boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
It's very strange though..
I had that problem today. I traced it down to my wifi. Turning off wifi allowed me to boot with no further issues.
1) Boot loop as soon as I got to work.
2) Dirty flashed the ROM
3) Restored backup from 4 days ago.
4) Wiped system and reflashed ROM and gapps. Same issue.
Finally chased it to the wifi. The instant it connected, bootloop. I ran and app called FXR Wifi fixer. Ill see if it bootloops tomorrow at work. No problems on my home wifi after all of this.
e753 said:
After these steps it seems working.
boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
It's very strange though..
Click to expand...
Click to collapse
i wouldn't consider this to be strange really. something was not correct in the system partition probably. pretty standard when flashing different ROMs
Hi guys,
so, my LG G5 has just been sent in for RMA, meaning I need a phone while I wait for that, and I have a nexus 4, however, it is stuck in a bootloop. I can access fastboot and adb, and have tried flashing Android 4.4.4 and 5.1.1, with 5.1.1 reaching "Android is starting, loading apps" as the final screen and so far with 4.4.4, just on the google colours booting animation.
I've also tried clearing cache partition, and factory resets. Currently I am using googles flash_all script, but would it be worth flashboot flash recovery etc. etc.
Could anyone suggest how I go about things to fix this?
Thanks, Conn
update
So, as of yet, I have got it to boot into 4.2.2, however, it isn't reading a brand new sim card. also updating to 4.3 through software update causes bootloop, and 4.2.2 seems to be the only working android version. I tried installing custom recovery (twrp) and a custom os (lineage 14.1) and that bootlooped.
Thanks, Conn
EDIT: Also, the IMEI is not being displayed.. From what I've read, the phone is probably stuffed?
It the OS can't read the IMEI, yeah sounds like something is borked.
Are you running flashall wiping everything, or did you take out hte -w switch to leave personal data? I've had issues with my 4 (that led to my buying a refurb 5) that trying to flash but keeping personal data failed, I had to do a full open hose reflash.
\\ Sent from an Android or iOS device //