Related
so the story goes like that.
few days ago (before ICS officialy came from asus) i've tried just for fun Paul's ICS port. i really dont see myself as a noob, so please treat my question as it is.
at first i've tried to flash it from cwm without wiping and stuff- got stuck at boot.
so i did i full wipe with "Android revolution super wipe".
and flashed ics port again- now with success.
after couple of days decided to go back to HC Revolver. so just went again to CWM and full wiped again, and flashed revolver 3.11.
then i started to get the bad news. it seems nothing can be flashed anymore from the recovery. when i flash a rom it finishing it too fast and when i reboot it just bootlooping on the splash screen. tried everything, including removing the cwm recovery and installing it again.
the one and only thing that worked is nvflashing a prime rom. but it still didnt fix the recovery problem.
i tried to flash also back HC kernel with no luck.
what did go wrong?!
please help me
num1gever said:
so the story goes like that.
few days ago (before ICS officialy came from asus) i've tried just for fun Paul's ICS port. i really dont see myself as a noob, so please treat my question as it is.
at first i've tried to flash it from cwm without wiping and stuff- got stuck at boot.
so i did i full wipe with "Android revolution super wipe".
and flashed ics port again- now with success.
after couple of days decided to go back to HC Revolver. so just went again to CWM and full wiped again, and flashed revolver 3.11.
then i started to get the bad news. it seems nothing can be flashed anymore from the recovery. when i flash a rom it finishing it too fast and when i reboot it just bootlooping on the splash screen. tried everything, including removing the cwm recovery and installing it again.
the one and only thing that worked is nvflashing a prime rom. but it still didnt fix the recovery problem.
i tried to flash also back HC kernel with no luck.
what did go wrong?!
please help me
Click to expand...
Click to collapse
You need to flash the stock kernel again, Paul's ICS kernel is still there, and that won't work. CWM does not flash the kernel when flashing a ROM unless the kernel is included with the ROM (like Paul's). Download Roach2010's kernel and CWM flash it, then reboot and see if that fixes it. Then, if you want to go to stock, use revolver parts to download the stock Asus kernel and return to stock.
Try hereee
http://forum.xda-developers.com/showthread.php?t=1513698
And then here
http://www.tabletroms.com/forums/tra...ing-tools.html
Ok, so I have been running a nice custom ROM of ICS on my phone, I then tried the updated version for a couple of days, but deceided to revert back to my previous back up. Did the back up through CWM manager, but from here, it failed to boot and went to the black "Samsung Galaxy note" screen.
I then went in to recovery, did a full wipe, and then just tried to re install my custom ICS ROM. It only got as far as flashing the modem, and then hangs, I tried this a few times, and with a few different roms. Pre ICS roms, and a stock KK9 rom just failed instantly.
I then put the phone in to download mode, and hooked it up to the PC to do a flash through ODIN.
I selected a stock KK9 rom, but this failed.
I now cant get to recovery, and I dont have the black "samsung galaxy note" screen, it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
I then try to do this, but Kies wont connect to the phone.
I am at a loss, please help
I'm really sorry about your trouble..I can't really help with your current issue but I can tell you what probably happened.
You probably tried to restore a gingerbread backup while using the ICS recovery. You just can't do that.
When you want to flash a gingerbread rom or gingerbread backup coming from a ICS rom you must ALWAYS flash a gingerbread kernel first. After that simply reboot recovery in advanced section and then restore gingerbread from there.
That way you know next time..Hope you get it fixed.
Sent from my GT-N7000
dannstarr said:
Ok, so I have been running a nice custom ROM of ICS on my phone, I then tried the updated version for a couple of days, but deceided to revert back to my previous back up. Did the back up through CWM manager, but from here, it failed to boot and went to the black "Samsung Galaxy note" screen.
I then went in to recovery, did a full wipe, and then just tried to re install my custom ICS ROM. It only got as far as flashing the modem, and then hangs, I tried this a few times, and with a few different roms. Pre ICS roms, and a stock KK9 rom just failed instantly.
I then put the phone in to download mode, and hooked it up to the PC to do a flash through ODIN.
I selected a stock KK9 rom, but this failed.
I now cant get to recovery, and I dont have the black "samsung galaxy note" screen, it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
I then try to do this, but Kies wont connect to the phone.
I am at a loss, please help
Click to expand...
Click to collapse
I assume the stock KK9 rom is from your region? Same thing happened to me because I stupidly flashed a rom that wasn't from my region (I have an unlocked phone from India). Hopefully that's what happened because it was an easy fix for me. Good luck!
Which custom ics rom did you have and which recovery?
Sent from my GT-N7000 using Tapatalk
When flashing between ICS ROMs I often flash the Abyss kernel first and then flash a new ROM from it's recovery. I think the issue is that your ICS ROM was not fully rooted. Try to flash Abyss kernel and the wipe and flash your next ROM.
csasek said:
When flashing between ICS ROMs I often flash the Abyss kernel first and then flash a new ROM from it's recovery. I think the issue is that your ICS ROM was not fully rooted. Try to flash Abyss kernel and the wipe and flash your next ROM.
Click to expand...
Click to collapse
Yes - this way always works for me. flash the abyss kernel in CW and then select reboot to recovery (do not select reboot the phone). When back in recovery, flash a GB ROM
Sent from my GT-N7000 using Tapatalk
Always use redpil from abyss to install a gb when comming from ics.
I have been running AOKP on my Fascinate for a while now, but something wierd is going on with the device. After about a week of running AOKP (I tried the Hacksung ICS builds as well), the Fascinate begins to bootloop, so I have to go through and ODIN (cannot wipe and reflash because it continues to bootloop after wipe and reflash) then flash AOKP again. The process repeats itself after roughly a week of use.
I went back and Odin'ed to 2.3.5, but ever since then, I have been unable to install a working recovery on my device. I can flash the recovery fine (Voodoo, and CWM fixed for CM7), but when it boots up, and I try to flash a file, the screen goes black for a minute, then goes back to the recovery menu, like it is rebooting recovery. I've tried Heimdall and Odin.
Anyone got any tips? Am I just forgetting something?
Sent from my SCH-I500 using Tapatalk 2
in odin did you use the atlas.pit repartition file when you flashed back to stock?
if not then try that. also, which CWM are you trying to flash?
I know my fassy had problems with certain versions, but a 2.5.x version always worked for me no matter what happened to my phone.
This guide always worked for me.... http://forum.xda-developers.com/showthread.php?t=1238070
Alright... where to begin? Lets start at what happened around yesterday. Prior to the whole weekend, I had CyanogenMod 10.1 installed on my rooted S4. Come Friday, I start to miss some of the stock Samsung features such as Air Gestures, Smart Stay, the stock Samsung camera, and all that. So, I install WanamLite (a custom rom) on my phone. It's good and all but for some reason, the Smart Stay isn't working. To fix this, I go online and start digging; I find people saying "yo, revert back to the original firmware and re-install the Rom, that should fix your LTE problem." I think to myself, "maybe this could help me too." And that's exactly what I do. I go online to SamMobile and download this ROM (http://www.sammobile.com/firmwares/?page=1&model=SGH-M919V&pcode=0#firmware). It installs with Odin and I was able to get back to the Stock Samsung firmware. I then proceed with my plan and install WanamLite; that also worked. So I'm all happy and stuff 'cause Smart Stay finally works but, shortly after fiddling with the re-stocked device, I get bored again. So, I start searching the forums for another rom to replace WanamLite (it was a good rom, but I wanted to try something else before settling down on it).
I find this ROM in the XDA-Developers S4 forum: http://forum.xda-developers.com/showthread.php?t=2303239. I try installing it; it works fine. But then, I notice that half my SD card is used up. So, I go into TWRP and click on Format Data (I'm not too sure about the name, I had CWM prior to the re-installation of Samsung stock firmware). After resetting the Data, I boot back into the phone and notice that the default layout is Easy Mode. (On the bright side, I freed 4 GB from my SD card). Easy Mode's incredibly annoying, so I wrestle with the phone for a while to change the launcher to Nova launcher, but to no avail. In the end, I decide to reflash the FoxHound ROM. I place the rom on my phone and boot into TWRP. That's where the problem comes. I selected: wipe cache, wipe delvic cache, wipe data. Then I wiped the cache and data, flashed the rom and, after that is when the phone started refusing boot up. From then on, it just displayed Samsung Galaxy S4 logo on the screen whenever I tried to start it.
What I tried to fix the issue: Re-installing the stock samsung firmware. (I think I ended up screwing up the phone even more with this. Before, I had TWRP installed but I couldn't boot into it, now I don't have any custom recovery installed and I still can't boot into the phone).
I can access the Download Mode and use Odin. I cannot boot into the recovery. When I hold Volume Up + Power + Home, it just says recovery in blue above the logo, and then, the phone reboots.
So, any ideas on how to fix it?
TL;DR: Tried installing FoxHound Rom. I wiped Delvic Cache, Cache, and Data, and after flashing the rom, the phone refused to boot up; it gets stuck on the Samsung logo. Before flashing, I did Format Data. After being unable to boot into the phone, I tried to flash the Stock Samsung Firmware on my S4. Nothing worked. Any ideas on how I should proceed?
splitinferno said:
So, any ideas on how to fix it?
Click to expand...
Click to collapse
Try using Odin mode to install Stock Samsung Firmware...
If it doesn't work,
Install Samsung Kies, put Phone into Odin mode, connect the USB and let KIES reinstall the whole firmware... Go to "Tools" -> "Emergency Firmware Recovery"
psycovirus said:
Try using Odin mode to install Stock Samsung Firmware...
If it doesn't work,
Install Samsung Kies, put Phone into Odin mode, connect the USB and let KIES reinstall the whole firmware... Go to "Tools" -> "Emergency Firmware Recovery"
Click to expand...
Click to collapse
I've already tried flashing the Stock Samsung Firmware using Odin, it didn't work. Also, I'm having no luck with Kies; it won't connect. Any other suggestions? :/
EDIT 1: Okay, so here's the deal right now: I was able to flash TWRP using ODIN. This granted me access to my recovery, somehow. So right now, I have the FoxHound_GearEngine0.2 ROM installation files on my SD card and I am booted into the recovery. What should I do? Should I try flashing again? For now, I'll just wait for a response.
EDIT 2: Out of curiosity and impatience, I tried flashing FoxHound but got an error:
Updating Partition Details
E: unable to mount data
E: unable to mount internal storage
TWRP v. 2.5.0.3
Go into the advanced menu in TWRP and try to mount data / internal storage. If you can't, then you're back to odin unless someone can find out something else
maazali said:
Go into the advanced menu in TWRP and try to mount data / internal storage. If you can't, then you're back to odin unless someone can find out something else
Click to expand...
Click to collapse
I tried to; it didn't work. I also tried clockworkmod recovery. That recovery said it said that the data was already mounted. For some reason, now the phone is stuck in a bootloop. On the bright side, I can freely access my recovery (although I can't do much in it). Should I try flashing other stock roms?
EDIT: Flashing the stock rom brought it back to the state it was in earlier. So now, it just hangs on the Samsung Galaxy S4 screen and no longer reboots continuously. I'm thinking of downloading other stock roms and flashing those.
UNBRICKED
splitinferno said:
I tried to; it didn't work. I also tried clockworkmod recovery. That recovery said it said that the data was already mounted. For some reason, now the phone is stuck in a bootloop. On the bright side, I can freely access my recovery (although I can't do much in it). Should I try flashing other stock roms?
EDIT: Flashing the stock rom brought it back to the state it was in earlier. So now, it just hangs on the Samsung Galaxy S4 screen and no longer reboots continuously. I'm thinking of downloading other stock roms and flashing those.
Click to expand...
Click to collapse
Alright, after struggling around with the device, I was able to unbrick it. I downloaded the stock ROM from samfirmware and flashed it using odin. After flashing it, it would stay on the Samsung Galaxy S4 logo and that's it and I wasn't able to boot into the recovery either. So, I flashed TWRP using odin and download mode, and found I was able to boot into recovery again. Screwing around with the recovery, I couldn't manage to do much so I decided to re-flash the stock firmware. After re-flashing, I had the same problem. This time, I tried accessing the stock recovery. I got access, which was something I couldn't get before. After getting access, I did Factory Reset/Data (it was something along those lines) and did a wipe cache. After wiping cache, the phone rebooted and, much to my delight, it was unbricked. After going through this, I think I might just like chill for like a month, or a year now with stock... .__.
Hahah nice job
Sent from my GT-I9505 using xda premium
splitinferno said:
Alright, after struggling around with the device, I was able to unbrick it. I downloaded the stock ROM from samfirmware and flashed it using odin. After flashing it, it would stay on the Samsung Galaxy S4 logo and that's it and I wasn't able to boot into the recovery either. So, I flashed TWRP using odin and download mode, and found I was able to boot into recovery again. Screwing around with the recovery, I couldn't manage to do much so I decided to re-flash the stock firmware. After re-flashing, I had the same problem. This time, I tried accessing the stock recovery. I got access, which was something I couldn't get before. After getting access, I did Factory Reset/Data (it was something along those lines) and did a wipe cache. After wiping cache, the phone rebooted and, much to my delight, it was unbricked. After going through this, I think I might just like chill for like a month, or a year now with stock... .__.
Click to expand...
Click to collapse
Next time don't wipe data in custom recovery because it will corrupt your data which would most probably end with not booting past the Samsung logo, if you want to wipe in a custom recovery for now you have to manually wipe system, cache and dalvik cache located in mounts in cwm recovery (not sure where to find it in twrp).
You should read a little before messing with things in recovery.
Ahahah that's funny because something similar happened to me. And I was going to suggest doing a factory reset via recovery because that's how I resolved my problem, then I see you did just that! (Y)
Sent from my GT-I9500
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