Related
Hello!
So, I've read through the beginner guides (and that is a hilarious video btw!) and just want to double check a few things. I'm on Fido (Canada) with a stock S4 (i337M) that I got a couple days ago.
1. I assume I use the instructions here: http://forum.xda-developers.com/showthread.php?t=2314494 [HOW-TO] and here http://forum.xda-developers.com/showthread.php?t=2298299 [Canadian Root and Recovery].
1a. That tool will allow me to un-root in case I need the warranty, yes?
2. I also want to flash to vanilla Android (aka Pure Google / Google Edition)... which ROM do I use? There are so many I can't tell.
2a. I know the Samsung camera app doesn't work on the Pure Google ROM, but is basic functionality still working, i.e. can I still take a picture / video / etc.? Is there any other basic functionality missing? (I heard something about the volume button?)
3. Which ROM do I use if I want to restore to factory?
4. I also need to backup my SMS, contacts, call log, app data, settings etc. so I can restore them easily after flashing to new ROM, or after restoring to factory ROM. Will Titanium handle all of this?
Thanks
kabutar said:
Hello!
So, I've read through the beginner guides (and that is a hilarious video btw!) and just want to double check a few things. I'm on Fido (Canada) with a stock S4 (i337M) that I got a couple days ago.
1. I assume I use the instructions here: http://forum.xda-developers.com/showthread.php?t=2314494 [HOW-TO] and here http://forum.xda-developers.com/showthread.php?t=2298299 [Canadian Root and Recovery].
1a. That tool will allow me to un-root in case I need the warranty, yes?
2. I also want to flash to vanilla Android (aka Pure Google / Google Edition)... which ROM do I use? There are so many I can't tell.
2a. I know the Samsung camera app doesn't work on the Pure Google ROM, but is basic functionality still working, i.e. can I still take a picture / video / etc.? Is there any other basic functionality missing? (I heard something about the volume button?)
3. Which ROM do I use if I want to restore to factory?
4. I also need to backup my SMS, contacts, call log, app data, settings etc. so I can restore them easily after flashing to new ROM, or after restoring to factory ROM. Will Titanium handle all of this?
Thanks
Click to expand...
Click to collapse
That guide should be fine. If you want "vanilla Android", right now the closest thing would be CM, you can get it from http://get.cm and select "jfltecan" (the canadian S4 model). Ye,s, Titanium can backup all of those things you mentioned, although I am not certain about system settings - there will be a lot of different settings between TouchWiz and AOSP.
CommentProvider said:
That guide should be fine. If you want "vanilla Android", right now the closest thing would be CM, you can get it from http://get.cm and select "jfltecan" (the canadian S4 model). Ye,s, Titanium can backup all of those things you mentioned, although I am not certain about system settings - there will be a lot of different settings between TouchWiz and AOSP.
Click to expand...
Click to collapse
awesome thanks. I'm not worried about system settings just apps and their settings.
for the factory ROM would this work?: http://forum.xda-developers.com/showthread.php?t=2261573 (again, I'm on Fido in Canada)
and lastly, I'm still not clear on the difference between Odin/Loki/whatever you use to root and/or flash - would someone be able to clarify?
Also, just to be clear, what is meant by 'recovery'?
Thanks again
http://forum.xda-developers.com/showthread.php?p=41989987
Loki
refers to the exploit that allows us to run custom recoveries as well as custom roms. You only need to have a loki'd rom if you have a model with a locked bootloader (AT&T).
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs4) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
Sent from my SGH-I747
mymusicathome said:
http://forum.xda-developers.com/showthread.php?p=41989987
Loki
refers to the exploit that allows us to run custom recoveries as well as custom roms. You only need to have a loki'd rom if you have a model with a locked bootloader (AT&T).
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs4) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
Sent from my SGH-I747
Click to expand...
Click to collapse
ok, great, thanks. just to clarify one last time: am I correct in understanding that I don't need to have a custom recovery in order to flash a ROM? or is that what installing clockwork mod/TWRP means? (or is that what rooting means?)
Lastly... is there somewhere with a list of what each custom ROM is, and/or what things don't work in the ROM? I do want vanilla, but I'd also be interested in checking out the other ROMs to see if there's one that will keep some TouchWiz functionality while removing the ridiculous skin.
Also, for vanilla Android, would you recommend waiting till devs release a MOD based off of the S4 GE?
kabutar said:
ok, great, thanks. just to clarify one last time: am I correct in understanding that I don't need to have a custom recovery in order to flash a ROM? or is that what installing clockwork mod/TWRP means? (or is that what rooting means?)
Lastly... is there somewhere with a list of what each custom ROM is, and/or what things don't work in the ROM? I do want vanilla, but I'd also be interested in checking out the other ROMs to see if there's one that will keep some TouchWiz functionality while removing the ridiculous skin.
Also, for vanilla Android, would you recommend waiting till devs release a MOD based off of the S4 GE?
Click to expand...
Click to collapse
Check out the link in my first post. A plethora of knowledge that will help you in your Rom journey.
Play around and test the options of roms you have. Each user has different likes/dislikes. MAKE SURE YOU READ THE ORIGINAL POST OF THE ROM YOU ARE PLANNING ON FLASHING. They will contain the basic inductions to flash the Rom and usually any bugs that exist.
Check out this thread for a list of compatible roms -
http://forum.xda-developers.com/showthread.php?p=41834056
[GUIDE][NOOB'S]These non-AT&T ROMs work on AT&T/TMO/Canadian S4 devices. Here's how!
A quick search can be a beautiful thing
Sent from my Nexus 10 using xda premium
mymusicathome said:
Check out the link in my first post. A plethora of knowledge that will help you in your Rom journey.
Play around and test the options of roms you have. Each user has different likes/dislikes. MAKE SURE YOU READ THE ORIGINAL POST OF THE ROM YOU ARE PLANNING ON FLASHING. They will contain the basic inductions to flash the Rom and usually any bugs that exist.
Check out this thread for a list of compatible roms -
http://forum.xda-developers.com/showthread.php?p=41834056
[GUIDE][NOOB'S]These non-AT&T ROMs work on AT&T/TMO/Canadian S4 devices. Here's how!
A quick search can be a beautiful thing
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Thanks again for the link! I have actually seen several of those... but am just still very confused. mainly on these points:
- FIDO's rom isn't in those lists, and the variety of options for flashing (e.g. some ROMs say they need to be flashed with ODIN not TWRP) is a bit overwhelming!
- there's a post saying the Canadian ROMs are for odin not recovery flashing?
- I'm still not clear on whether I need to install a custom kernel just to flash a different ROM
- Also not clear on how to restore to factory stock (to take it to store for example)
- In the link you sent, the OP said non-ATT people should use the versions in their own forums... but does this apply to Canadian users too or is this ok for them?
Feel free to tell me if I'm being really dumb, but I really am a little lost lol.
As for buggy ROMs... would it be better to wait for one based off the S4 Google Edition?
Thanks again
Canadian dont need loki dont use loki never use loki
Take time to understand everithing before flashing
rodger is the same as fido exept for the rodger bloatware (my accout,visual voicemail etc)
what i did root with cf auto root
installed goomanager on google play ,this app can installed twrp and it really easy
in recovery i flash mint jelly rom ,after its done i flash faux kernel for canadian
To factory restore you have to installe stock rom thru odin ,(from what i understand) it change the rom and the kernel at the same time
zild8 said:
Canadian dont need loki dont use loki never use loki
Take time to understand everithing before flashing
rodger is the same as fido exept for the rodger bloatware (my accout,visual voicemail etc)
what i did root with cf auto root
installed goomanager on google play ,this app can installed twrp and it really easy
in recovery i flash mint jelly rom ,after its done i flash faux kernel for canadian
To factory restore you have to installe stock rom thru odin ,(from what i understand) it change the rom and the kernel at the same time
Click to expand...
Click to collapse
ok, so I'm just sorting through all of this. Successfully rooted and flashed CM nightly. However, now I see 'rogers' instead of 'fido' and 4G in the status bar, which I understand means that I'm on LTE according to stock JB icons.
So to sort this out:
a) what do I do about this incorrect network name?
b) if I restore to stock rom through odin, and it installs the 'rogers' rom, how do I get back to the fido apps? will I still have the network access / wrong name problem?
c) if I want to go BACK to stock eventually, I seem to have two options:
http://forum.xda-developers.com/showthread.php?t=2261573 [FACTORY STOCK]
http://forum.xda-developers.com/showthread.php?t=2269304 [12 May Official STOCK firmware collections for Canadian S4]
which do I use?
d) I took a nandroid image, BUT: can I restore from this (after wiping all data) to get back to factory ROM, or MUST I use ODIN? Or, do I need to use ODIN and then nandroid to restore everything about the stock ROM?
Thanks!!
A = I think cm have an option to rename carrier label if not you can install xposed framework and notach xposed and the go in frameword,module then activate nottach .open nottach then chose any option that you want ,over 100...
or i think you can try change your apn to show fido ( not sure)
B= check playstore for fido app
C= ? i dont know i think both of then are good, iwould use the one that say canadian stock firmware
D = if you restore from nandroid i think you flash counter gonna still show that you running cutom rom ,best way should be thru odin
Read a lot before you do anithing,you have to understand ..seem to be easy to brick .did not happen to me since one years ,but i read a lot..
And hit the thanks button when somebody helps you
zild8 said:
A = I think cm have an option to rename carrier label if not you can install xposed framework and notach xposed and the go in frameword,module then activate nottach .open nottach then chose any option that you want ,over 100...
or i think you can try change your apn to show fido ( not sure)
B= check playstore for fido app
C= ? i dont know i think both of then are good, iwould use the one that say canadian stock firmware
D = if you restore from nandroid i think you flash counter gonna still show that you running cutom rom ,best way should be thru odin
Read a lot before you do anithing,you have to understand ..seem to be easy to brick .did not happen to me since one years ,but i read a lot..
And hit the thanks button when somebody helps you
Click to expand...
Click to collapse
AWESOME, thanks for all that. Successfully flashed, so hopefully that's the end of it all. And thanks for pointing out the thanks button!!
Two LAST quick things:
- if I use the Canadian stock firmware, do I still end up with a wrong carrier name sign? I imagine I may need to ask the dev that, but just in case you happen to know. I actually can't seem to fix it using the methods you suggested, so I'd prefer not to have this happen.
- ok so I can flash with ODIN and then use nandroid to restore a snapshot of the filesystem I assume?
kabutar said:
AWESOME, thanks for all that. Successfully flashed, so hopefully that's the end of it all. And thanks for pointing out the thanks button!!
Two LAST quick things:
- if I use the Canadian stock firmware, do I still end up with a wrong carrier name sign? I imagine I may need to ask the dev that, but just in case you happen to know. I actually can't seem to fix it using the methods you suggested, so I'd prefer not to have this happen.
- ok so I can flash with ODIN and then use nandroid to restore a snapshot of the filesystem I assume?
Click to expand...
Click to collapse
-If you flash back to your stock carrier specific firmware with ODIN the carrier will be correct. You will be back to just as when you first got it from the dealer (provided they didn't set it up for you first).
-You shouldn't be able to restore the nandroid if you ODIN back to stock because you will no longer have a custom recovery.
blyndfyre said:
-If you flash back to your stock carrier specific firmware with ODIN the carrier will be correct. You will be back to just as when you first got it from the dealer (provided they didn't set it up for you first).
-You shouldn't be able to restore the nandroid if you ODIN back to stock because you will no longer have a custom recovery.
Click to expand...
Click to collapse
- Well the problem is that my carrier is Fido, a subsidiary of Rogers, and so CM only has a 'Rogers' release. Similarly there is only a 'Rogers' stock firmware, so I don't want to flash back to that and have the carrier still wrong...
- OK, well I assume I could root, flash nandroid, and then unroot - yes?
Thanks!
kabutar said:
- Well the problem is that my carrier is Fido, a subsidiary of Rogers, and so CM only has a 'Rogers' release. Similarly there is only a 'Rogers' stock firmware, so I don't want to flash back to that and have the carrier still wrong...
- OK, well I assume I could root, flash nandroid, and then unroot - yes?
Thanks!
Click to expand...
Click to collapse
-I see the dilema.
-Well as opposed to even flashing to stock with ODIN in the first place. I would suggest booting to recovery (TWRP or CWM), and restore your Nandroid backup. This should bring you to the point before you flashed any ROM. Keep in mind this won't however remove status showing 'custom'.
If you happened to already ODIN back to stock you would have to root again, install custom recovery and perform the step above.
blyndfyre said:
-I see the dilema.
-Well as opposed to even flashing to stock with ODIN in the first place. I would suggest booting to recovery (TWRP or CWM), and restore your Nandroid backup. This should bring you to the point before you flashed any ROM. Keep in mind this won't however remove status showing 'custom'.
If you happened to already ODIN back to stock you would have to root again, install custom recovery and perform the step above.
Click to expand...
Click to collapse
that is what I was thinking... there are ways to unroot as far as I know so hopefully that should be ok!
thankfully I did take a nandroid backup. speaking of which - I have 3 files, does this sound ok?:
- boot/sys/data (these were originally selected so just went with it)
- efs
- other (everything else)
last clarification: I thought nandroid was not recommended if switching between ROMs? like if I had a computer backup (i.e. nandroid) but took the backup in Windows XP (i.e. stock rom) and then tried to restore it over Windows 8 (i.e. CM rom), bad things would happen? or is the nandroid more like an acronis boot image thing where it completely wipes everything?
lastly, if I do that... do I need to wipe factory data, dalvik cache, etc or will nandroid take care of that for me?
many thanks again!
kabutar said:
that is what I was thinking... there are ways to unroot as far as I know so hopefully that should be ok!
thankfully I did take a nandroid backup. speaking of which - I have 3 files, does this sound ok?:
- boot/sys/data (these were originally selected so just went with it)
- efs
- other (everything else)
last clarification: I thought nandroid was not recommended if switching between ROMs? like if I had a computer backup (i.e. nandroid) but took the backup in Windows XP (i.e. stock rom) and then tried to restore it over Windows 8 (i.e. CM rom), bad things would happen? or is the nandroid more like an acronis boot image thing where it completely wipes everything?
lastly, if I do that... do I need to wipe factory data, dalvik cache, etc or will nandroid take care of that for me?
many thanks again!
Click to expand...
Click to collapse
I think when you go into recovery and restore nandroid everything will restore.
I would just restore the nandroid from your current state via recovery. If you are worried about it or it causes a problem, it isn't to many more steps to flash to stock via ODIN, root and install recovery and proceed with restore.
I think it is always safe practice to wipe first, and not to dirty flash.
blyndfyre said:
I think when you go into recovery and restore nandroid everything will restore.
I would just restore the nandroid from your current state via recovery. If you are worried about it or it causes a problem, it isn't to many more steps to flash to stock via ODIN, root and install recovery and proceed with restore.
I think it is always safe practice to wipe first, and not to dirty flash.
Click to expand...
Click to collapse
ok thanks.
However: I may be SAVED! I just realized that Fido is often tagged as FMC, and there's a stock firmware for that one in this thread. Thank the heavens!
kabutar said:
ok thanks.
However: I may be SAVED! I just realized that Fido is often tagged as FMC, and there's a stock firmware for that one in this thread. Thank the heavens!
Click to expand...
Click to collapse
Didn't know that! Never been with Fido. Great news for you, all you have to do is ODIN that firmware
blyndfyre said:
Didn't know that! Never been with Fido. Great news for you, all you have to do is ODIN that firmware
Click to expand...
Click to collapse
Yeah, very relieved, and now just gotta figure out why my phone is showing up as a Rogers phone when the nightly is tagged Rogers + Fido and I'll be good to go. I must say I miss multi-window a little and the handwaving over screen a lot, but by god TouchWiz was ugly.
hey kabutar
Yesterday i flash the 12 may stock firmware thru odin ,to revert backt to stock
Here what i did
-latest odin 3.07
-put your phone in download mode with usb not pluged to computer ...
-closed all kies software
-plug your phone in computer
add firmware on pda button ,dont touch any other option.
reboot i add a lot of crashing app so i went to recovery and errase data
reflash thru odin the stock firmware ,and boom everthing was stock ,no more custom in os or in download mode
I've generally managed to root and/or customize most of my devices with the help from these forums, but this one has me stumped. I picked up an AT&T Galaxy S4 recently, and unfortunately it was already on a locked bootloader. I was able to root and install Safestrap 3.71 with little trouble. After some tweaking of the stock ROM, I decided to have a go with some custom ones.
Until recently, I'd been able to flash just about any SS-compatible ROM to any slot with little to no issue. Some required flashing of GApps, or Kernels, but aside from a few FC's or signal issues, the actual flashing portions always went smoothly. I ended up flashing DarthStalker vX1 to my stock slot with the MK2 kernels and have had zero issues with the ROM functionality. Being curious about recent developments with other ROM's, I decided to try flashing a few. The problem I'm having is that 90% of the ones I try to flash are going into a boot loop. Even those that worked previously (Hyperdrive, SHOstock) are boot looping.
I have tried deleting and recreating various ROM slots and at one point I managed to get SHOstock (SS) 3.0 to boot, but all of the GApps were crashing to the point where it was unusable, regardless of GApps I flashed over it for testing purposes.
I guess I'm wondering if there may be some sort of issue with having a custom ROM in the stock slot? Perhaps some sort of file or data corruption that is stopping these ROM's from working, even though they all worked previously? It just doesn't seem to be making sense because I don't believe I've changed anything since the last time I was able to flash to any SS slot. I've tried searching, but pretty much all of the boot loop issues I've come across were related to something that I've either already ruled out, or simply didn't apply to my configuration. Any hints or tips would be great. Please let me know if anyone needs more information about the config, or steps I've taken so far. Thanks all!
@remedee
I believe for HyperDrive u also need to install Att compatible pack and u also need flash ATT mk2 kernel modules .... check this thread about MK2 INDEX and ROM LISTS by @guut13 http://forum.xda-developers.com/showthread.php?t=2616221 anything u should know about all the compatible roms and instruction. ....u might get better help on that thread since alot of Rom flashaholic there. ...check with @ddubz he is flashaholic Master..... :thumbup::thumbup:.... Goodluck.....
Swyped From MK2 Dark Venom SS Edition
Once you flash a bad ROM on Stock slot and you boot loop, you are cooked. Only way to fix it is to Odin back to stock. Then you can restart the process.
If you flash a bad ROM on a ROM slot, you can just delete the ROM slot, recreate it, and you will be good to go for another try.
That's been my experience, anyways.
ted77usa said:
@remedee
I believe for HyperDrive u also need to install Att compatible pack and u also need flash ATT mk2 kernel modules .... check this thread about MK2 INDEX and ROM LISTS by @guut13 http://forum.xda-developers.com/showthread.php?t=2616221 anything u should know about all the compatible roms and instruction. ....u might get better help on that thread since alot of Rom flashaholic there. ...check with @ddubz he is flashaholic Master..... :thumbup::thumbup:.... Goodluck.....
Swyped From MK2 Dark Venom SS Edition
Click to expand...
Click to collapse
Thanks for the reply. I've read through quite a few of the threads for the individual ROMs, but unfortunately the issue isn't related to any one specific ROM. I do have the compatibility pack and modules for HyperDrive and I was able to successfully get that installed previously. I was using that as an example of a ROM that worked before with this same configuration, which is why it's bugging me. I'll wipe out the existing slot 1 and give it another go, making sure I flash those as well. Unfortunately that doesn't explain why SHOstock (which I tested extensively before), and others go into a boot loop as well.
The only thing I can think of is perhaps I'm not wiping properly. So far, whenever I attempt to install a new ROM, I create a new slot with the default size values, do a factory reset, install ROM and any module/kernel recommended with it, wipe cache, reboot. Not sure what else I could be doing wrong.
guut13 said:
Once you flash a bad ROM on Stock slot and you boot loop, you are cooked. Only way to fix it is to Odin back to stock. Then you can restart the process.
If you flash a bad ROM on a ROM slot, you can just delete the ROM slot, recreate it, and you will be good to go for another try.
That's been my experience, anyways.
Click to expand...
Click to collapse
Thankfully I don't think I've had any truly bad flashes that resulted in a brick, or even a partial brick. My stock slot is running a custom (Darthstalker) ROM that is still fully functional through all of this other testing. I do have backups of my original stock config, as well as a recent backup of the DS ROM in the stock slot, so I'm not sure it's related to a bad ROM in that slot. It's just really strange that ROMs that were working just fine before in any slot are now causing loops. I haven't had to Odin back to stock or anything, but I'm considering doing that just to get back to a clean base. It just seems unnecessary since my stock slot is still 100% functional. No signal drops, all wifi and bluetooth connections work flawlessly, etc.
I'm usually the guy that scours these forums until I find a solution, but this problem is just plain weird. As you can see from my post count, this is the first time I've thrown up my hands and asked for help. I'm not even sure there is anything really broken. It could very easily be something stupid I have or haven't done. It's just frustrating when I flash a ROM that I've verified the MD5 on, and I know for a fact has worked previously. I'll keep plugging away at it and post back if I figure out what's going on. Thanks again!
@remedee If I were u..... Follow my thread to go back to stock MK2 http://forum.xda-developers.com/showthread.php?t=2621279 check post #2 for guide on how to. After u got fresh MK2 firmware ..... root it.... install safestrap v3.71 and then create rom slot 1 first to see if the rom stable enough ....If it does then make your rom slot 1 back up .....then wipe your stock slot..... restore your rom slot 1 back up to stock slot or follow @guut13 instruction noted on every compatible rom lists from his thread. ..... Goodluck....:good:
Swyped From MK2 Dark Venom SS Edition
remedee said:
Thankfully I don't think I've had any truly bad flashes that resulted in a brick, or even a partial brick. My stock slot is running a custom (Darthstalker) ROM that is still fully functional through all of this other testing. I do have backups of my original stock config, as well as a recent backup of the DS ROM in the stock slot, so I'm not sure it's related to a bad ROM in that slot. It's just really strange that ROMs that were working just fine before in any slot are now causing loops. I haven't had to Odin back to stock or anything, but I'm considering doing that just to get back to a clean base. It just seems unnecessary since my stock slot is still 100% functional. No signal drops, all wifi and bluetooth connections work flawlessly, etc.
I'm usually the guy that scours these forums until I find a solution, but this problem is just plain weird. As you can see from my post count, this is the first time I've thrown up my hands and asked for help. I'm not even sure there is anything really broken. It could very easily be something stupid I have or haven't done. It's just frustrating when I flash a ROM that I've verified the MD5 on, and I know for a fact has worked previously. I'll keep plugging away at it and post back if I figure out what's going on. Thanks again!
Click to expand...
Click to collapse
Just to be clear, I didn't necessarily mean bricked when I said cooked, but kind of. I tested a bunch of ROMs for my threads. If i flashed one that didn't work, my phone would usually boot loop...
samsung logo, safestrap menu, black screen, reboot, samsung logo, safestrap menu, black screen, reboot, and so on...
If I stopped the boot loop by going back into safestrap, no matter how many times I wiped or which ever ROM I flashed next (even known working ones), I always went back into a boot loop after rebooting. Only thing that worked was odin back to stock. (Can't remember if I tried restoring, though.)
ROM slot was different. Deleting it and recreating was all it took. That's why I learned my lesson and just test new roms on ROM slot first.
remedee said:
Thanks for the reply. I've read through quite a few of the threads for the individual ROMs, but unfortunately the issue isn't related to any one specific ROM. I do have the compatibility pack and modules for HyperDrive and I was able to successfully get that installed previously. I was using that as an example of a ROM that worked before with this same configuration, which is why it's bugging me. I'll wipe out the existing slot 1 and give it another go, making sure I flash those as well. Unfortunately that doesn't explain why SHOstock (which I tested extensively before), and others go into a boot loop as well.
The only thing I can think of is perhaps I'm not wiping properly. So far, whenever I attempt to install a new ROM, I create a new slot with the default size values, do a factory reset, install ROM and any module/kernel recommended with it, wipe cache, reboot. Not sure what else I could be doing wrong.
Click to expand...
Click to collapse
next time you try to flash one and it fails try making the data partition smaller. Had a guy pm me and couldn't get rom to boot and i had him do this and bam it booted right up. Worth a shot. Also i have switched phones i went to the nexus 5 and i am not as fresh with the s4 stuff as i was a few weeks ago. PM if you need any help
I still plan to Odin back to stock but I didn't have time tonight. I did however grab a ROM from the link provided by ted77usa (thanks man, I can't seem to figure out how to mention at the moment). The Wicked v10 ROM installed to a clean Slot 1. I know that DarthStalker installed using Aroma, and Wicked is one of the few that I've tested that also uses Aroma. I don't know if it makes a difference, but this is the first ROM to install without a boot loop since I started having trouble.
I'm also wondering if the fact that this ROM had never been installed before has anything to do with it. I'm going to back it up since it's functional, then wipe and try to reinstall just to see if I get a boot loop. Thanks again to everyone for all of the input.
Sorry for the delay in getting back on this. My toddler finds new and interesting ways of keeping me from my hobbies Just wanted to say thanks to @ted77usa @guut13 and @ddubz. I tried resizing the partition and that didn't seem to help. I ended up starting from scratch and everything seems to be running properly. I've got DarthStalker back in the stock slot, Wicked in slot 1 and Hyperdrive in slot 2. I'm quite certain it's overkill, but just knowing I can switch between them and tinker makes me happy. Thanks again for all the input. XDA is definitely an awesome community.
As the title says I have an International GT_I9500 unlocked
Until now I was always able to install any custom rom I wanted , no problem, just wipe and install and away we went.
Now with KitKat, I AM COMPLETELY UNABLE TO INSTALL ANY OF THE CUSTOM ROMS FOR 4.4.2 -0 NONE WORKS. I can't believe i am jinxed.
I wiped everything, cache, dalvik, system and internal and also did a full wipe - NOTHING WORKED, There are 3 custom roms for 4.4.2 so far and NONE = NOT A SINGLE ONE WANTS TO INSTALL.
I downloaded one of Samsung original 4.4.2 firmware and using Odin I WAS ABLE TO INSTALL AND MAKE IT WORK, yet after doing this, I tried to install any of the 3 customs roms and BOOM, COMPLETE FAILURE
Can anyone help PLEASE GUYS, I feel like BROOMHILDA LONE PERSON WITH A CLOUD ONLY ON MY HEAD
I am curious as to why this is happening
maybe its a i9505 or i9506 rom
provide the Odin messages here.
custom roms failure, huh?
spamtrash said:
provide the Odin messages here.
Click to expand...
Click to collapse
I loaded the custom roms via recovery, not via odin,
so i go into recovery mode via TeamWin, wipe everything and load the custom rom, message says "successful" and i reboot system, that's it
the phone hangs into one of the boot animations and never finishes, left it for longer than 30 minutes, all of them , nothing loads.
go back the same custom roms but with android 4.3 and first shot, loads fine, all of them, same ones that won't load the 4.4.2 load the 4.3
most custom roms load via recovery not odin -
last try was load samsung original firmware 4.4.2 via download Odin, then root then install teamwin recovery. - worked fine
now removed it and reinstalled Thor 4.3 (thor 4.4.2 doesn't work) but tomorrow i'll wipe it and reinstall the samsung 4.4.2 unless you have an idea
*i hope)
sorry about the capitals - NO IT IS AN EXYNOS UNLOCKED GT-I9500 - almost a year after playing with nova settings, xposed and about a dozen custom roms, i THINK i know it's a 9500 - skip the silly suggestions - we're all noobs but not necessarily all boobs
thanks for your help - appreciated if we can solve it
custom roms failure, huh?
KingOfDope said:
maybe its a i9505 or i9506 rom
Click to expand...
Click to collapse
roms were downloaded exclusively from GT=I9500 AREA -
i don't go anywhere else because i know beforehand that they won't work - so why bother
thanks for your suggestion but obviously out of context - i don't live in the US in addition
Maybe wrong recovery ¿?
funny 4.4.2 roms
robertostorm said:
Maybe wrong recovery ¿?
Click to expand...
Click to collapse
i usually use teamwin version 2.6.3
and funny thing in one of the wipes even the teamwin was wiped so i wound using the regular android recovery, with the tiny tiny blue characters
that doesn't have all the teamwin recovery options - so even then it failed
after installing the saunsung 4.4.2 i downloaded a fresh teamwin version and installed via odin/download - like starting from zero. guess what
nope even then the roms freeze at the bootanimation - but the joke is ONLY IF THEY ARE VERSIONS 4.4.2 -they work fine with version 4.3
and when i mean wipe i mean wipe - cache/dalvik/system/internal - and even the other option where you have to type YES for the wipe to go on.
short of reformating the whole memory which i think is excessive, i THINK i tried with a clean clean memory install (according to me)
thanks for your patience
btw most of the custom roms install via recovery so there's no way to get a download install version
exlaval said:
i usually use teamwin version 2.6.3
and funny thing in one of the wipes even the teamwin was wiped so i wound using the regular android recovery, with the tiny tiny blue characters
that doesn't have all the teamwin recovery options - so even then it failed
after installing the saunsung 4.4.2 i downloaded a fresh teamwin version and installed via odin/download - like starting from zero. guess what
nope even then the roms freeze at the bootanimation - but the joke is ONLY IF THEY ARE VERSIONS 4.4.2 -they work fine with version 4.3
and when i mean wipe i mean wipe - cache/dalvik/system/internal - and even the other option where you have to type YES for the wipe to go on.
short of reformating the whole memory which i think is excessive, i THINK i tried with a clean clean memory install (according to me)
thanks for your patience
btw most of the custom roms install via recovery so there's no way to get a download install version
Click to expand...
Click to collapse
Once you flashed stock 4.4.2, your bootloader gets updated, so you can only use 4.4+ roms, also TWRP is full of bugs, just use cwm 6.0.4.5 and you're set.
Also, did you root the stock 4.4.2?
custom roms failure, huh?
robertostorm said:
Once you flashed stock 4.4.2, your bootloader gets updated, so you can only use 4.4+ roms, also TWRP is full of bugs, just use cwm 6.0.4.5 and you're set.
Also, did you root the stock 4.4.2?
Click to expand...
Click to collapse
as i said in a previous message - i used odin in download mode and flashed an original samsung 4.4.2 and it worked, i rooted and reinstalled teamwin
AFTER ALL THIS I tried to install one of the 4.4.2 custom roms - IT FAILED CONSISTENTLY - BY THIS I MEAN ALL ROMS DIED AT BOOTANIMATIONS - AND ALL FAILED TO START
thanks so much
Try with latest Philz recovery or any up to date CWM recovery.
And when coming from stock, you generally have to FULL wipe you phone
custom roms failure, huh?
ayedarts said:
Try with latest Philz recovery or any up to date CWM recovery.
And when coming from stock, you generally have to FULL wipe you phone
Click to expand...
Click to collapse
just downloaded cwm version 6.0.4.6 installed via recovery. launched recovery installed latest wanamlite for 4.4.2 - message was "installed successfully" please reboot
i rebooted and for the last 15 minutes all i have is a BIG SAMSUNG on the screen - nothing beyond
just another hitch with kitkat - i have a SONY XPERIA Z TABLET with wifi and sim - a couple of weeks ago i rooted it but the cwm version is not good because it's on the vertical side and you cannot see the bottom of the menu so it's useless - anyhow. i rooted it and left it at that.
i got notice from sony that a new os version (kitkat) was ready for install - so I just told the tablet to start - and the os install screwed the tablet,
there was no way to reload and it completely deleted the memory , it went to sony to reload - so i have a big hunch there is something not right somewhere -
anyway the phone still has the SAMSUNG and it ain't going anywhere while i am writing all this
very discouraging = sure as heck i ain't buying no more galaxys of any sort, i was ready to preorder the s5 at 455british pound, unlocked - but since this i am dropping samsung, i like very very much the xperia tablet it's faster than the s4 so perhaps i'll jump to the sony xperia fone and bbye korea
maybe i9505 rom
custom roms failure, huh?
i know you're trying to help - but if you read all the previous (long and boring) messages - there's no mistakes, there's no 9505
ALL THE ROMS I DOWNLOAD AND USE - ALL OF THEM WITHOUT EXCEPTION come for the i9500 development area, I DON'T BOTHER WITH
9505 - MOSTLY BECAUSE I DON'T HAVE A 9505
UPDATE - today after loading the latest cwm recovery i got lucky to be able to load ONE - READ IT - ONE CUSTOM ROM ( rom from HASAN)
this is the very only that i got to work, the other two just refuse to finish the boot - i don't know where they freeze.
even the wanamlite custom rom for 4.4.2 freezes - this is really annoying and a puzzle - this is my fourth samsung fone and never ever did i
find the bug that freeze everything. I hope that some of the other developers will come up with new kitkat versions for the 9500 and see if the bug persists or not -
any help will absolutely be appreciated, guys, some sort of boot log that can help pinpoint,
thanks again
You know the fact you keep using capital letters (so you might be trying to scream) is a little annoying.
I have a Samsung Galaxy S4 GT-I9500. I live in Costa Rica (so not in the US obviously).
I installed stock 4.4.2 using ODIN, then flashed ROOT and finally installed a custom CWM. First I tried Philz and ended up with 6.0.4.6.
I have already tried 2 different custom ROM's but I didn't like them so I went back to stock. I am very satisfied with the performance of my phone with stock, but that's not the point.
The thing is that I have the same phone you have, i installed the same software you installed, I followed the same steps you have followed yet I am able to install any custom ROM i like.
Maybe it is your phone, or maybe you're just looking for an excuse to quit Samsung and you're simply blaming kitkat your inability of installing ROMs now.
I'm just saying... there are several options you can tried if you quit being angry and actually try them.
Personally, I would start from scratch. Flashing via ODIN again, rooting accordingly with the right files, using a recovery that is recognized to work with 4.4.2, and finally using the right custom ROM.
custom roms failure, huh?
pinktheater said:
You know the fact you keep using capital letters (so you might be trying to scream) is a little annoying.
I have a Samsung Galaxy S4 GT-I9500. I live in Costa Rica (so not in the US obviously).
I installed stock 4.4.2 using ODIN, then flashed ROOT and finally installed a custom CWM. First I tried Philz and ended up with 6.0.4.6.
I have already tried 2 different custom ROM's but I didn't like them so I went back to stock. I am very satisfied with the performance of my phone with stock, but that's not the point.
The thing is that I have the same phone you have, i installed the same software you installed, I followed the same steps you have followed yet I am able to install any custom ROM i like.
Maybe it is your phone, or maybe you're just looking for an excuse to quit Samsung and you're simply blaming kitkat your inability of installing ROMs now.
I'm just saying... there are several options you can tried if you quit being angry and actually try them.
Personally, I would start from scratch. Flashing via ODIN again, rooting accordingly with the right files, using a recovery that is recognized to work with 4.4.2, and finally using the right custom ROM.
Click to expand...
Click to collapse
-------------------------------------------------------
First - The capitals I used were ONLY to emphasize certain aspects and not intended as screaming, which is the usual sense - That was not my intention,
Second - I have being using Samsung for the last 7 years, I was not intending to leave until I hit this brick and further I nearly went to Clove, UK (where I usually pre-ordered my last 3 Galaxy's - months ahead of delivery) so thumping me by saying I am looking for an excuse to dump Samsung, is way off base, so much so, that if that indeed was my intention, why for all heavens would i bother to find a solution, and waste so much time and effort to make it work
Third - I have being as polite as any person can be, with or without, this hitch, don't judge, about being angry or not, you don't know me well enough to know the difference, just stick to the point in question without getting personal.
Fourth - What I have described is EXACTLY to a tee what is happening to me, what happened to YOU , is IRRELEVANT, you may be one of the lucky ones who has no issues installing the roms in questions. so unless you do have a suggestion as to finding the reason the fone loops on boot, skip what you did or didn't do, they are IRRELEVANT, because they don't provide a solution.
Fifth - If you read my descriptions you will notice the many times I installed customs roms on the many galaxy's and Note's I have/had.That ought to clue you that i know a basic way on how to do the installations (Odin, recovery, teamwin. cmw,) you name it I've done it, and i've unbricked more than once my fones. so yes i do know how to use Odin
Sixth - For some reason I was able to install the "HASSAN" rom (the ONLY and ONLY) 4.4.2 custom that worked. the others they just won't, PERIOD
So if you have a technical solution as to how to get a log of the looping so we can tell exactly at what point the fone loops. or some other technical solutions, please let me know them asap I am dying to see my fone with a custom 4.4.2,
Seventh - Yes I am extremely disappointed that the S5 is just not fantastic enough to lay 455GBP to pre-order. there are a few more advances but it is "ALMOST" good = the bezel didn't disappear - the 2K display isn't there - the sharper casing is still missing - the better battery is still not there - the wireless charging - To have 2000 horse power engine under the hood of a beat up VW beatle. doesn't make you good looking enough to go cruising on a saturday nite and brag about your "car" -
BTW = I am absolutely no fan of the Iphone (yuk) nor of Sony (which is as restricted as apple)
Can you help solve my issue - thanks
Alright, so, I'm not a huge modder, but I do like to remove the stock OS once things start slowing down (as they always do).
When I upgraded my LG G2 D800 to Cyanogenmod 11, I noticed the Accelerometer was no longer working. No big deal, I thought, it would eventually be fixed. So I just used a manual control app in the meantime.
Well, Yesterday I got a ColorCross VR headset, so I want that Accelerometer to work again. I've tried nearly everything. short of going back to stock. I think I know the solution but can't find a reliable download/get TWRP to work with my downloads. I had cm-11-20140504-SNAPSHOT-M6-d800 Installed
I found this thread http://forum.xda-developers.com/showthread.php?t=2705509 stating that a modified Kitkat Modem/baseband is needed, but the files are gone.
Then, I found this thread: http://forum.xda-developers.com/showthread.php?t=2451426 with these downloads http://downloads.codefi.re/autoprime/LG/LG_G2/G2_modems it had two modems or the LGD800, "10D_Radio" and "10O_Radio" neither worked when trying to flash the zip as downloaded using TWRP. I tried both wiping data/Cavik and flashing it right before and right after a fresh install of Cyanogenmod, both Lollipop and Kitkat versions but no luck. Couldn't open the zip file TWRP said.
So I tried a few 5.0 ROMS, CM 12 (second to latest nightly and a few others), Cloudy, Vanir, but none of them turned on my Accelerometer.
So, what I need, is an explanation on how to flash those modem files or if I was doing it correctly, a link to valid modem files. Preferably one that works with an Android 5.0.x ROM, but if I have to go back to KitKat, I can live with that, I just want my sensors to work.
Failing that, I guess I can revert all the way back to stock. But let me ask one question: Can I just flash a .zip file using TWRP if I'm not worried about making it appear completely stock (not planning on returning or selling it) without having to do the extra stuff in the guide intended for a complete return to stock? I don't need recovery to be reverted, just the original stock ROM (I tried to flash just the ROM, but either the download was damaged or I can't simply flash the stock LG G2 AT&T ROM).
I have five bucks in bitcoin I can tip whoever helps me out, either a custom ROM that installs the right modem/baseband by default and is KitKat or above or some instructions on how to get the right modem files to install + a link to them.
If a new build needs to be compiled to get the accelerometer working again, I might be able to donate a little more than that.
Right before posting this I tried downgrading to CM11-20140210-SNAPSHOT but while it installed, it still says there is no accelerometer (and doesn't auto-rotate, even when on). I also tried downgrading to CM10 (the only LG d800 CM10 on the official site) but TWRP didn't want to open the zip.
Thanks!
Neverminc, figured it out, sorry for the noob questions
Hi All,
So trying to simply flash 1 rom onto my phone. Being only moderately computer minded and over the age of 21 most written guides using the variety of abbreviations that accompany this type of thing leaves me having to google every other word.
I've rooted m N9005 UK Note 3 fine without a hitch. I've downloaded root checker and it confirms my note 3 is now rooted. Great I think this is going well.
All I want to do is install the Aryamod and the Lean Kernel 6.3 for faster and smoother running. Nothing complicated you say, well it is for the feeble of mind I can assure you!
So first step in the guide is install TWRP. Not that it explains how to do this, so after googling it I find a handy youtube guiding explaining it.
"Great!" I think. Alas no.
I follow the first step and download twrp manager, then it wants to know what version of the note 3 I have. Unfortunately the app thinks EVERYONE lives in North America so I'm presented with several options for which note 3 I have. The options are as follows: Canadian, International Exynos (tried this it doesn't work), International Qualcomm, Neo, Sprint, T-Mobile, US Cellular and Verizon. As I live in the UK all of these networks are meaningless to me.
As I can't be the only Brit to have ever attempted to install twrp, which version is mine? It's an unlocked note 3 originally with Vodafone ?
Please help! I'm stumbling at the first hurdle here
http://lmgtfy.com/?q=N9005+twrp
yeah I've tried that mate I can't find where it says which version is for UK tho...
Does it even say anywhere that you need a country specific twrp? Except for that stupid manager app which nobody uses.
You have an 9005, and that's it.
like I said dude, I'm feeble minded!! I'm just trying to do what the instructions tell me!
The first link in my previous post is all you need to know.
Does the aryamod come with lean kernel 6.3 in the download or do I need to install something else separate?
So found the Lean Kernel 6.3 .zip and tried to flash using twrp but when I try and boot it says "this kernel is not deandroid" or words to that effect. What am I doing wrong?
Orta117 said:
So found the Lean Kernel 6.3 .zip and tried to flash using twrp but when I try and boot it says "this kernel is not deandroid" or words to that effect. What am I doing wrong?
Click to expand...
Click to collapse
So... do you have TWRP installed?
The message is pretty much irrelevant - it says 'this kernel is not seandroid enforcing' or similar. Google use the setting to remove apps from Playstore if they mess with the setting but Custom ROMs always change it. To check if the kernel installed just go to [Settings] [About Phone] and have a look.
While in [Settings] check if [Developer Options] is there. If it isn't, while in [About Phone] tap [Build Number] 7 times to turn it on. Then go into Developer Options and tick ON [Android Debugging]
If you don't have TWRP - go to the Team Win site and DL the .TAR or .MD5 version (think it's TAR) You have the HLTE version so look for that one. It's at THIS PAGE
Then use Odin 3.09 to flash it in AP. Phone should restart once briefly into Recovery then restart properly. Turn phone off and 3-fingers to Recovery or if your ROM allows reboot into Recovery, choose that.
Flash the kernel in Recovery. Wipe Dalvik and Cache. [Wipe][Advanced] tick only those 2. Note TWRP might offer a [Wipe Cache and Dalvik] on screen after you flash the kernel. OK to do it that way.
If you wish to play with kernel settings for performance or battery, DL Kernel Adiutor (spelling is correct ) from Play - it's free and gives you pretty much all Faux CLock will provide.
Yeah I have twrp and running aryamod. All the links to downloads for the kernel talk about needing to be running stock rom and there's no mention of my model. Could anyone advise on correct download file for this for my phone?
The deandroid message comes up when I try and boot after flashing the kernel and the phone won't boot it just kicks me off onto recovery mode again. That's even when following the guidelines you've given?
Anyone shed any light on why the kernel won't work? Googled it and has yielded nothing
Make sure it's hlteeur. Unless yours is TMO
Sent from my SM-N920C
I'm afraid I don't know what those abbreviations mean? And how would I go about finding if my phone is one or the other?
Just flash any of it. If eur doesn't work then try tmo. But yours is eur right?. Eur - international note 3 tmo - tmobile note 3
Sent from my SM-N920C
Managed to check this working! I now have the note 3 running aryamod and lean kernel I wanted in the beginning!
Thanks so much everyone