As some of you already know, version 4.4 BETA 1 of Paranoid Android is problematic — it results in a boot loop, with recovery mode being unaccessible.
(I was stupid enough to perform a flash without bothering to check PA's dedicated thread. I know, dumb move.)
Now, download mode is still available, but my computer will not recognize my phone. Therefore, Odin is unusable, I have installed Samsung's USB driver for mobile phone version 1.5.34, but my phone was still not recognized after that.
Any ideas?
same thing happened to me but I downloaded odin 3.09 and booted to download than I succed to flash philz kernel with recovery and restored my backup.
And I think you my have problem with OS, usb port or usb cable.
Try reboot PC, change windows profile, usb port.
Good luck
waro470 said:
As some of you already know, version 4.4 BETA 1 of Paranoid Android is problematic — it results in a boot loop, with recovery mode being unaccessible.
(I was stupid enough to perform a flash without bothering to check PA's dedicated thread. I know, dumb move.)
Now, download mode is still available, but my computer will not recognize my phone. Therefore, Odin is unusable, I have installed Samsung's USB driver for mobile phone version 1.5.34, but my phone was still not recognized after that.
Any ideas?
Click to expand...
Click to collapse
These are the drivers that you downloaded?:
http://downloadcenter.samsung.com/c...Driver_for_Mobile_Phones_v1.5.23.0-retail.exe
What operating system you are using?
If you are using Win 8, I recommend using odin 3:07 or 3:09. Also work well with win7
Odin all versions:
http://www74.zippyshare.com/v/18196321/file.html
panamera2011 said:
These are the drivers that you downloaded?:
http://downloadcenter.samsung.com/c...Driver_for_Mobile_Phones_v1.5.23.0-retail.exe
What operating system you are using?
If you are using Win 8, I recommend using odin 3:07 or 3:09. Also work well with win7
Odin all versions:
http://www74.zippyshare.com/v/18196321/file.html
Click to expand...
Click to collapse
I guess I'll make a rule about not flashing my phone after soccer... Too tired to even think straight. Well, it turns out I was using the wrong version of USB driver and Odin, too.
I will keep you guys updated. Thanks for the quick replies, everyone!
[EDIT]: Awesome. I've been able to install Philz's recovery (using Odin v3.07), but not the latest version. I'm under the impression that that old version of the recovery is not letting me install Kitkat-based PA ROMs.
Should I flash PA 3.99 first, and then upgrade to PA 4?
waro470 said:
I guess I'll make a rule about not flashing my phone after soccer... Too tired to even think straight. Well, it turns out I was using the wrong version of USB driver and Odin, too.
I will keep you guys updated. Thanks for the quick replies, everyone!
[EDIT]: Awesome. I've been able to install Philz's recovery (using Odin v3.07), but not the latest version. I'm under the impression that that old version of the recovery is not letting me install Kitkat-based PA ROMs.
Should I flash PA 3.99 first, and then upgrade to PA 4?
Click to expand...
Click to collapse
Recovery is build into the kernel, so flash a kernel instead of a full rom.
I recommend Forest-CM11
This kernel and recovery will be overwritten by the rom anyway.
waro470 said:
I guess I'll make a rule about not flashing my phone after soccer... Too tired to even think straight. Well, it turns out I was using the wrong version of USB driver and Odin, too.
I will keep you guys updated. Thanks for the quick replies, everyone!
[EDIT]: Awesome. I've been able to install Philz's recovery (using Odin v3.07), but not the latest version. I'm under the impression that that old version of the recovery is not letting me install Kitkat-based PA ROMs.
Should I flash PA 3.99 first, and then upgrade to PA 4?
Click to expand...
Click to collapse
If you want to try last PA KK, you must first install Forest CM11 kernel V3B, Wipe data / factory reset, wipe cache, wipe davlik cache, then install PA KK, reinstall Forest CM11 V3B kernel, wipe cache, wipe davlik cache reboot.
But now, I recommend to wait for new updates
If you want to try a great rom KK, I recommend using CarbonRom KitKat, I'm testing latest nightly, and it works really great.
Go to in recovery
install, Forest CM11 kernel V3B http://www.mediafire.com/download/t1imczaknfmid69/Forest-CM11-kernel-V3b.zip
Wipe data / factory reset
wipe cache
wipe davlik cache
install rom https://carbonrom.org/mirrors/?file=n7000/nightly/CARBON-KK-NIGHTLY-20140603-1127-n7000.zip
install pa gapps modular http://goo.im/devs/paranoidandroid/roms/gapps-full
Reboot
enjoy
For some reason, I thought it wasn't logical to flash a recovery while being in recovery mode... Anyhow, it's been a smooth ride thanks to you guys.
(Going back to my old Nokia 5230 sure was a scarring experience...)
waro470 said:
For some reason, I thought it wasn't logical to flash a recovery while being in recovery mode... Anyhow, it's been a smooth ride thanks to you guys.
(Going back to my old Nokia 5230 sure was a scarring experience...)
Click to expand...
Click to collapse
Why was it not logical? You just installed a new kernel to get the recent version of cwm which is selinux compatible, abki to flash 4.4 roms.
nokiamodeln91 said:
Why was it not logical? You just installed a new kernel to get the recent version of cwm which is selinux compatible, abki to flash 4.4 roms.
Click to expand...
Click to collapse
I know practically nothing about Android when it comes to under the hood stuff. That and I always have the worst scenario in mind. Since kernel flashing hasn't been trouble-free for me under Linux generally speaking (except for Manjaro), I tend to be careful, and imagine that there could be conflicts.
Firest kernel does not provide a tar version... only the zip file which can only be flashed from recovery
and the problem is exactly this that we cannot access recovery now (after flashing pa 4.4.3)
please suggest a way of getting back my phone again
odin 3.07 is stuck at NAND write start ... i am trying to flash philz recovery 6.07.9 from the source mentioned above
cant seem to fix my phone..pleas Help
Azeazezar said:
Recovery is build into the kernel, so flash a kernel instead of a full rom.
I recommend Forest-CM11
This kernel and recovery will be overwritten by the rom anyway.
Click to expand...
Click to collapse
Here is what i would do in your situation. Note that i am not an expert.
If odin doesnt flash your file, download it again, and try again maybe its a bad download.
If it still does not work try heimdall
If that does not help, include a pit file in odin. <- Can be rather dangerous.
I tried falshing a pit file...even that failed
Azeazezar said:
Here is what i would do in your situation. Note that i am not an expert.
If odin doesnt flash your file, download it again, and try again maybe its a bad download.
If it still does not work try heimdall
If that does not help, include a pit file in odin. <- Can be rather dangerous.
Click to expand...
Click to collapse
Related
This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.
Try flashing a different compatible kernel.
ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app
I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!
Glad it's working out for you.
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.
hey all,
so i am incredibly new to this scene and just recieved my s4. i was preparing to flash a ROM onto my phone, and got it rooted and installed CWM.
I forgot to download the actual ROM zip file, and went into CWM via goo manager, wiped factory/data and cache. It was only AFTER i wiped everything that i realised i didnt download the ROM zip file, so i rebooted the phone and now it is stuck on the start-up splash screen where it displays "Samsung galaxy S4 GT-I9505" and will not continue :crying:
I was running on stock, and had only rooted the phone.
PLEASE i urgently need to fix this ASAP. Help!
Hi,
is there a Odin Version of the Rom you tried to flash? If yes, you could simply bring your device to download-mode and flash the Rom with Odin.
Alternatively search for a odin flashable Recovery and flash this first. Then you could boot to recovery and flash the zip of the Rom.
Sent from my GT-I9505 using xda app-developers app
i tried installing the liquid smooth rom, and from what i can see there is no odin version of the rom :\
Are you able to direct me to an Odin flashable recovery I can use?
im really stressing out about this
i'm in the process of downloading a stock firmware and will try to flash it on, but it's taking forever to download
I don't see why you can't boot again if you have only wiped the user data and cache, just press the home button for 10 seconds and see if it restarts with your reset stock firmware. Otherwise you can reboot into recovery and do the wipes again (not the option to install a new ROM), or put the ROM zip you want to flash on an SD card and then flash from the SD.
I hope this helps.
suwidji said:
hey all,
so i am incredibly new to this scene and just recieved my s4. i was preparing to flash a ROM onto my phone, and got it rooted and installed CWM.
I forgot to download the actual ROM zip file, and went into CWM via goo manager, wiped factory/data and cache. It was only AFTER i wiped everything that i realised i didnt download the ROM zip file, so i rebooted the phone and now it is stuck on the start-up splash screen where it displays "Samsung galaxy S4 GT-I9505" and will not continue :crying:
I was running on stock, and had only rooted the phone.
PLEASE i urgently need to fix this ASAP. Help!
Click to expand...
Click to collapse
You should of made a backup with CWM. That's what it's used for also, besides flashing .zips. Always make a backup that you can restore and keep an extra copy on ur computer and/or a usb drive.
You have to use Odin to flash a stock firmware from Sammobile website. Make sure you download the correct firmware for your phone.
Dont worry, your phone isn't brick.
when i first did the wipe, i chose the option that i was going to install a new ROM. I'm now assuming that's where i made a mistake.
I did make a backup before i wiped everything onto my SD card, but now i can't even access that backup because it's saying there's nothing.
I've tried flashing a ROM onto it, but it says aborted.
Yes SORF ist right. It should boot into resetted stock firmware.
First try to copy the Rom to SD and then boot to recovery an try flashing it.
If booting to recovery doesn't work (but it should work if you just wiped user data and cache) you should try flashing new recovery with odin.
You could use Philz recovery for GT-I9505 from here http://forum.xda-developers.com/showthread.php?t=2281367
Installation Instructions for installation with odin you find here http://forum.xda-developers.com/showpost.php?p=39433857&postcount=4
windozeanti said:
You have to use Odin to flash a stock firmware from Sammobile website. Make sure you download the correct firmware for your phone.
Dont worry, your phone isn't brick.
Click to expand...
Click to collapse
Thanks, that's what I'm doing right now, but the file is about 1.8GB and taking so long to download...
i wish there was a faster server, but this is the only option i could find :\
Have you tried to boot into recovery again and then flash your already downloaded rom from sd? So you don't have to download a complete sammy rom.
j0ch3 said:
Have you tried to boot into recovery again and then flash your already downloaded rom from sd? So you don't have to download a complete sammy rom.
Click to expand...
Click to collapse
yes i have tried that, and it says that install aborts.
Also when i re-wipe everything and then try to reboot, it says my device is missing root.
When i try to re-root, and the device reboots, it gets stuck on the intro screen again so the root doesn't actually complete installing
have you fixed it yet?
so im going to try a different ROM other than the liquid smoothe one i wanted (since it keeps saying aborted)
question: does it matter if i use ANY s4 ROM regardless of carrier? I'm from Australia and there is no specific carrier for my phone on xda
Why does it fails to install? Are there any more error messages?
Also you can try the point "Fix Permissions" under Advanced Options. This could help.
suwidji said:
so im going to try a different ROM other than the liquid smoothe one i wanted (since it keeps saying aborted)
question: does it matter if i use ANY s4 ROM regardless of carrier? I'm from Australia and there is no specific carrier for my phone on xda
Click to expand...
Click to collapse
try something lite like miui - it will save you time on download and is a good solid base to work from. dont flash the lite gapps without a reboot.
for a solid Sami based rom then i suggest using GoldenEye.
scottyf79 said:
try something lite like miui - it will save you time on download and is a good solid base to work from. dont flash the lite gapps without a reboot.
Click to expand...
Click to collapse
ok so i went ahead and found the cyanogenmod one
http://forum.xda-developers.com/showthread.php?t=2317040
and installed this and it works
though i dont like the look of this ROM lol, i prefer something a little more stock looking.
Any recommendations?
When reflashing a new ROM, what is the process i need to follow?
Cyanogenmod is themeable. So you could search for a stock like theme and install that.
If you like an overall more stock rom try scottyf79's recommendation.
If you want to flash a complete new Rom first copy zip onto sd, then boot into recovery, wipe data and cache, then falsh zip file.
Try the Omega Roms. They are close to stock.
Closest to stock are the prerooted DJembey ROMs (the CWM ones) or the Wanam Lite ROM (it's what I am on now)
suwidji said:
ok so i went ahead and found the cyanogenmod one
http://forum.xda-developers.com/showthread.php?t=2317040
and installed this and it works
though i dont like the look of this ROM lol, i prefer something a little more stock looking.
Any recommendations?
When reflashing a new ROM, what is the process i need to follow?
Click to expand...
Click to collapse
personally -
i use Philz recovery
before install of a new rom - i use the "new rom" wipe option rather than the normal data,cache and dalvik wipe (it does this but adds in some extra steps)
then flash the rom of choice
if you get any other messages before reboot - select no
like i said before, if you want a stock looking Sami rom then try Golden Eye.
Try the Omega Roms. They are close to stock.
Closest to stock are the prerooted DJembey ROMs (the CWM ones) or the Wanam Lite ROM (it's what I am on now)
Hi,
I am pretty new to custom roms ect, I have tried installing Battery King v8.2, Vision X II, Carbon Nightly and Google Edition. All of those roms are compatible with i9505, I have also tried using both recoveries CWM 6.0.3.1 and TWRP 2.6.3.1 and on each i wiped data, cache, dalvik, battery stats and system, then after each rom installed successfuly i wiped the dalvik cache again and rebooted to find the stock rom (Prerooted).
Any advice to what i am doing wrong?
I am currently downloading the official stock rom for my phone now to see if that makes a difference.
AGAWhitty said:
Hi,
I am pretty new to custom roms ect, I have tried installing Battery King v8.2, Vision X II, Carbon Nightly and Google Edition. All of those roms are compatible with i9505, I have also tried using both recoveries CWM 6.0.3.1 and TWRP 2.6.3.1 and on each i wiped data, cache, dalvik, battery stats and system, then after each rom installed successfuly i wiped the dalvik cache again and rebooted to find the stock rom (Prerooted).
Any advice to what i am doing wrong?
I am currently downloading the official stock rom for my phone now to see if that makes a difference.
Click to expand...
Click to collapse
I had the same, I forgot to flash a custom recovery. Samsung's stock recovery will only flash/install Samsung signed ROMS. Flash a custom recovery like CWM, TWRP or Philz (I'm using philz). Then boot into your recovery and flash your ROMS.
If you have done that, ensure the MD5 of your ROM is correct.
RossFixxed said:
I had the same, I forgot to flash a custom recovery. Samsung's stock recovery will only flash/install Samsung signed ROMS. Flash a custom recovery like CWM, TWRP or Philz (I'm using philz). Then boot into your recovery and flash your ROMS.
If you have done that, ensure the MD5 of your ROM is correct.
Click to expand...
Click to collapse
Hi,
Thanks for your reply, i have installed both CWM then TWRP but havent tried Philz (i will try that now) but how do you mean ensure the MD5 of my rom is correct? How would i do this? Because i have downloaded the roms from the i9505 sections therefore i know they are compatible if that is what you mean.
AGAWhitty said:
Hi,
Thanks for your reply, i have installed both CWM then TWRP but havent tried Philz (i will try that now) but how do you mean ensure the MD5 of my rom is correct? How would i do this? Because i have downloaded the roms from the i9505 sections therefore i know they are compatible if that is what you mean.
Click to expand...
Click to collapse
Ok, just checking the basics first, I made that mistake, TWRP didn't flash correctly and I was on stock recovery!
the MD5 is a unique code attributed to the file. It will be given with the download and look something like (as an example only) 1565fs15f1s65f1w8e1wf8f1sw When you download the file you can run a program (have a look, loads free for PC and the phone) that will generate an MD5 sum also, the two should match, if not your download corrupted (this happens me a lot).
Hmmm. What error are you getting, what exactly happens in the recovery when you flash the zip?
RossFixxed said:
Ok, just checking the basics first, I made that mistake, TWRP didn't flash correctly and I was on stock recovery!
the MD5 is a unique code attributed to the file. It will be given with the download and look something like (as an example only) 1565fs15f1s65f1w8e1wf8f1sw When you download the file you can run a program (have a look, loads free for PC and the phone) that will generate an MD5 sum also, the two should match, if not your download corrupted (this happens me a lot).
Hmmm. What error are you getting, what exactly happens in the recovery when you flash the zip?
Click to expand...
Click to collapse
Okay, ill have a look for a pc tool that will do that. I am currently installing the stock 4.3 i9505 rom then ill flash the Philz recovery and try installing the custom rom if the md5 matches. Ill reply with the results as soon as im done.
AGAWhitty said:
Okay, ill have a look for a pc tool that will do that. I am currently installing the stock 4.3 i9505 rom then ill flash the Philz recovery and try installing the custom rom if the md5 matches. Ill reply with the results as soon as im done.
Click to expand...
Click to collapse
Cool, best of luck with it. I'm not too familiar with doing this on the S4 but got it all working last night. If I'm not full of ideas there's many, many poeple on this forum who know their stuff back to front who will get you sorted!
Any errors you encounter note them down! Make backups!! Then backup your backup on the PC!
FIXED
Just to update, it finally worked. Before i flashed the custom rom i installed the latest official firmware which was 4.3 from sam mobile, then before flash i went onto CWM and did the following:
format cache system and data x 2
wiped cache partition
wiped dalvik cache
rebooted recovery
formated cache system and data
rebooted recovery
installed from sd card
then wiped data/factory reset then rebooted
Awesome! Enjoy your new ROM!
Sent from my GT-I9505G using xda app-developers app
I wanted to update my note 1 to 4.4.1 kitkat but unfortunately it did not happen.
first i rooted my phone installed cwm with 6.0.3.2v and then when i flashed 6.0.4.2v rom but after that my phone it not able to boot after after samsung.
pls help me
and i am sorry for my english
Rohangarg4388 said:
I wanted to update my note 1 to 4.4.1 kitkat but unfortunately it did not happen.
first i rooted my phone installed cwm with 6.0.3.2v and then when i flashed 6.0.4.2v rom but after that my phone it not able to boot after after samsung.
pls help me
and i am sorry for my english
Click to expand...
Click to collapse
im having the same problem But with ANY aosp rom after samsung logo it bootloops and doesnt do anything else. so it just wont boot
Rohangarg4388 said:
I wanted to update my note 1 to 4.4.1 kitkat but unfortunately it did not happen.
first i rooted my phone installed cwm with 6.0.3.2v and then when i flashed 6.0.4.2v rom but after that my phone it not able to boot after after samsung.
pls help me
and i am sorry for my english
Click to expand...
Click to collapse
4.4.1? why are you flashing incredibly old nightlies?
Also it sounds like you flashed from a very old CWM build which likely didn't set selinux contexts properly. The included Omni kernel has a recent TWRP, reflash omni and wipe using that.
Entropy512 said:
4.4.1? why are you flashing incredibly old nightlies?
Also it sounds like you flashed from a very old CWM build which likely didn't set selinux contexts properly. The included Omni kernel has a recent TWRP, reflash omni and wipe using that.
Click to expand...
Click to collapse
how should just start my phone because i ried to install a new firmware through recovery mode it says some error.
so how should start up my phone
PLS DO HELP FAST
Rohangarg4388 said:
how should just start my phone because i ried to install a new firmware through recovery mode it says some error.
so how should start up my phone
PLS DO HELP FAST
Click to expand...
Click to collapse
Flash this file in recovery:
http://ge.tt/7mJqhvw/v/0?c
Then, reboot to recovery again and perform a full wipe (factory reset/data wipe, wipe cache, wipe dalvik cache, wipe system, wipe preload). You'll find those options in various places there, so dig around. Once that is done you can flash OmniROM and Gapps
and @zachdees - you most probably didn't do a full wipe, so do those steps above and it will work for you too
can you send the omni rom file
Rohangarg4388 said:
can you send the omni rom file
Click to expand...
Click to collapse
you should find your rom version here if it's officially supported: http://dl.omnirom.org/
If not..find it via the search function in the forum.
If i just want to install stockrom instead of omni rom , can you pls tell me how to do it.
pls tell me each thing step by step
http://forum.xda-developers.com/showthread.php?t=1424997
How to flash official ROM through recovery. Particularly 4.0.4 .
No...as i said use the search function and look in your device specific forum. The probability is high that your questions have already been answered. As well as sources which have already been linked. You might want to have a read of the forum rules as well as general guidelines before posting.
Sent from my Find 5 using XDA Premium 4 mobile app
Hi my phone seems to hate custom roms like cyamogenmod and gapps because everytime i flash them a bootloop inevitably comes to haunt me. Other roms like Albe95 Ports work. http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564
My current rom is Phoenix Rom. http://forum.xda-developers.com/showthread.php?t=2349584
The roms listed above work flawlessly.
A rom that I wanted to try was cyamogenmod 12.1 optimized by JDC team but it wouldnt boot. I followed exact instructions for each rom. Every time i used TWRP.
Could my problem be that gapps screw with the custom rom ?
Google apps are integrated in phoenix rom and albe95.
Maybe thats why they work ?
Please help.
Thank you for youre time.
JaguarBeast said:
Hi my phone seems to hate custom roms like cyamogenmod and gapps because everytime i flash them a bootloop inevitably comes to haunt me. Other roms like Albe95 Ports work. http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564
My current rom is Phoenix Rom. http://forum.xda-developers.com/showthread.php?t=2349584
The roms listed above work flawlessly.
A rom that I wanted to try was cyamogenmod 12.1 optimized by JDC team but it wouldnt boot. I followed exact instructions for each rom. Every time i used TWRP.
Could my problem be that gapps screw with the custom rom ?
Google apps are integrated in phoenix rom and albe95.
Maybe thats why they work ?
Please help.
Thank you for youre time.
Click to expand...
Click to collapse
You can easily test that theory by not flashing Gapps. Just only flash the rom and try to boot it.
Also are you running a Lollipop bootloader and modem?
Ive tried flashing only custom rom but the bootloop comes back. Right now i am running a lollipop modem and bootloader.
JaguarBeast said:
Ive tried flashing only custom rom but the bootloop comes back. Right now i am running a lollipop modem and bootloader.
Click to expand...
Click to collapse
Ok do this:
Backup everything that you want to save stored on your internal storage.
1. Make sure you are running the latest TWRP. This is important because using an outdated version will not let you boot the rom.
2. Start TWRP and do a advanced wipe. Format /data (this will wipe your internal storage), format /system, format /cache and /dalvik.
3. Flash the rom.
Unfortunately that does not help. I have advanced wiped ever time before flashing rom. Maybe permisions are the problem ?
JaguarBeast said:
Unfortunately that does not help. I have advanced wiped ever time before flashing rom. Maybe permisions are the problem ?
Click to expand...
Click to collapse
What version of TWRP are you using? And did you try booting it without simcard and sd card?
Im using 2.8.7.2 twrp. I havnt tried to boot without sd or sim. Would that be the problem ?
JaguarBeast said:
Im using 2.8.7.2 twrp. I havnt tried to boot without sd or sim. Would that be the problem ?
Click to expand...
Click to collapse
No idea. I'm just guessing because that rom should just boot.
Are you sure the file you downloaded is not damaged? Check the MD5 signature. For example, the latest version of the JDC CM rom has MD5:
3a1af890b87c11256c943759459ec3e4
So transfer the file to your phone. Then download a MD5 checker from the market and compare it.
Md5 matches. Looks like the insides of my phone are screwed up
Reparation your device
As those are caused by a screwed partition
As a reparation fixes this
You are going to need :-
0.a PC
1.a PIT file for your Galaxy s4 (depending on your variant)
2.Odin
3.Samsung USB drivers installed in the PC
Sent from my GT-I9505 using Tapatalk
Start with flashing the stock rom using odin. Then go for root,then recovery and then try flashing. I had the same problem but it never bothered me after flaahing the stock.