Related
wrong section i know, the 10post cap before i can post in development section.
im coming from Trigger 3.0.1 and i had the overstock kernel on, i followed the directions in the MIUI section to install ... i managed to flash the vibrant-efsbackup and then odin and flash the kernel from cyanogenmod and then i went back into the new recovery and flashed the miui rom. but when i reboot the phone, it reboots and shows the cyanogenmod kernel screen and then it jumps back into recovery. it doesnt go into the rom at all, it just loops back into the recovery. what can i do? i dont want to odin to stock just yet.
You're going to have to go back to stock. Use a stock Voodoo kernel instead of Overstock to do the Voodoo conversion next time.
just got back from work. im going to odin and just use a stock voodoo kernel this time around, will post as soon as i do it.
got it to work completely, so thx for the info!
Hi everyone. .
What's the easiest way to go back to an OEM ROM? I rooted my S4 and flashed several different ROMs ( which were awesome) but none let me encrypt my phone. I need to encrypt it so that I can access my work email. Ive decided to try and go back to stock and just root the stock ROM so I can delete all the sprint bloat and just be happy for now. Any thought on the easiest way to accomplish this? Im using TWRP recivery
Appreciate all the help!
R
rvv2002 said:
Hi everyone. .
What's the easiest way to go back to an OEM ROM? I rooted my S4 and flashed several different ROMs ( which were awesome) but none let me encrypt my phone. I need to encrypt it so that I can access my work email. Ive decided to try and go back to stock and just root the stock ROM so I can delete all the sprint bloat and just be happy for now. Any thought on the easiest way to accomplish this? Im using TWRP recivery
Appreciate all the help!
R
Click to expand...
Click to collapse
Everything you need is in this post: http://forum.xda-developers.com/showthread.php?t=2277480
Have you tried just flashing the stock rooted MDL rom from recovery? This is the fastest way to go back to stock rooted. The link to crawrj's stock rooted MDL rom is in that post as well. If that doesn't do it for some reason (not sure why it wouldn't) about your only choice then is to Odin back to stock.
Boom. Worked perfectly. I just flashed stock rooted MDL rom from recovery and rebooted a couple of times and it let me encrypt! I don't know why the first time I flashed it, it wouldn't let me encrypt. Weird.
over the last few days I've flashed a number of ROMs, mostly the Google Edition 4.2.2 and 4.3 ones and every single one of them eventually fails to boot hanging on the Samsung bootloader screen. and i say eventually because the first boot is almost always flawless, but then each time i reboot or power down, its almost guaranteed to loop.
I've tried so many different combinations that there's really not a single path I've taken every time, but the general steps are:
-root original firmware using motochopper
-install TWRP via GooManager
-reboot recovery and wipe everything, typically I do Advanced and select everything, then format Data
-then flash through ADB sideload, I do this since I wipe everything before flashing and I don't have an external SD card
-immediately after flashing ROM, I flash loki-doki also through ADB sideload. some of the ROMs I tried said they were lokied, but I still got the ATT invalid ROM message, so I reflashed with loki and it worked.
-then reboot system and the first time it comes up and works fine on every ROM I've tried
But if I power down or restart, on a very rare occasion it'll come up, but almost every time it hangs on bootloader screen. I also noticed once it's stuck on bootloader, power button becomes unresponsive, sometimes holding it powers down device, sometimes does nothing (have to press and hold twice)
If I flash back to stock using Odin, it works, boots, reboots, powers down just fine.
I've also tried flashing with a ROM and then immediately after with the stock ATT kernel, also booted up fine, but looped on restart.
Could this be hardware issue?
I'm about to give up on this and go back to stock for good, which would be really disappointing, can anyone help?
Flash a KT kernel and see what happens, I suppose you know which one correct?
TheAxman said:
Flash a KT kernel and see what happens, I suppose you know which one correct?
Click to expand...
Click to collapse
I assume KT means http://forum.xda-developers.com/showthread.php?t=2292341 ?
I've tried that too with jamal2367's 4.2.2 GE ROM (http://forum.xda-developers.com/showthread.php?t=2341794). It refused to boot all together.
First time I flashed with AOSP version since I thought that was an AOSP ROM, then reading more comments in the other thread it said I needed the TW version for GE ROMs, so I tried that too. Either way, neither of them booted at all, even the first time, so I gave up on KT and only used either ROMs' included kernels or ATT stock.
It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.
TheAxman said:
It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.
Click to expand...
Click to collapse
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?
collegebored said:
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?
Click to expand...
Click to collapse
You know, I don't even look at anything that says loki anymore, I flash the rom I want and use MY carriers kernel, bootloops and hangs are just not there, I do not see these issues everyone has, because, I have this procedure everytime. So...
Btw, your good on your files you want to flash, but, if this does not work ie, GE and that kernel, try a TW rom with the kernel, bet it boots properly. I do not give a rats
a$$ about goole roms. They are not worth it. Btw, I use this procedure on TW and aosp roms, no issues. Just because it says it loki'ed, flash the kernel you know works, loki just confuses people.
The Ax says again an again..My opinion only!
Good luck sir.
BTW, I ran that rom with the kernel you chose, it should work just fine. Remember, flash the TW version.
Thanks Ax for your help here, your welcome.
So yesterday I decided to install TWRP and installed this rom: http://forum.xda-developers.com/showthread.php?t=2356429
Well, once I loaded up wifi wouldn't work, so I tried restarting the phone. Phone now stay stuck at the GS4 load screen. I tried switching to clockwork mod, installed this rom: http://www.androidfilehost.com/?fid=23032113221600575
Wifi wouldn't work, restarted. Same thing. Wiping stuff, reinstalling, etc doesn't work.
Do I need to go back to stock? Is there a kernal issue?
I've done this on my note II without issue, so not sure what problem would be.
Any help is appreciated.
amishbobinc said:
So yesterday I decided to install TWRP and installed this rom: http://forum.xda-developers.com/showthread.php?t=2356429
Well, once I loaded up wifi wouldn't work, so I tried restarting the phone. Phone now stay stuck at the GS4 load screen. I tried switching to clockwork mod, installed this rom: http://www.androidfilehost.com/?fid=23032113221600575
Wifi wouldn't work, restarted. Same thing. Wiping stuff, reinstalling, etc doesn't work.
Do I need to go back to stock? Is there a kernal issue?
I've done this on my note II without issue, so not sure what problem would be.
Any help is appreciated.
Click to expand...
Click to collapse
Only thing I can think of is if you flashed the MF9 version to an MDL phone, or vice versa.
Double check the version compatibility, do a wipe from TWRP and then reinstall the ROM. That's my opinion.
Cytality said:
Only thing I can think of is if you flashed the MF9 version to an MDL phone, or vice versa.
Double check the version compatibility, do a wipe from TWRP and then reinstall the ROM. That's my opinion.
Click to expand...
Click to collapse
I think I did....is that bad?
amishbobinc said:
I think I did....is that bad?
Click to expand...
Click to collapse
I don't know if I'd say "bad." It just won't work right lol.
Just look at what version you downloaded before, was it MF9 or MDL? If it was MF9 then download the MDL version of that ROM and try that. Remember you should always be doing TWRP full backups of cache and ROM, so you have something to fall back on if you screw up.
Cytality said:
I don't know if I'd say "bad." It just won't work right lol.
Just look at what version you downloaded before, was it MF9 or MDL? If it was MF9 then download the MDL version of that ROM and try that. Remember you should always be doing TWRP full backups of cache and ROM, so you have something to fall back on if you screw up.
Click to expand...
Click to collapse
What about the stock MDL, if I flash that rom it should work - right?
amishbobinc said:
What about the stock MDL, if I flash that rom it should work - right?
Click to expand...
Click to collapse
Any MDL ROM should work if you KNOW you're on MDL baseband. I can't tell if you are or not, only you would know that. Did you ever do the new MF9 update? If not then you're probably on MDL.
So if you download any MDL ROM, doesn't have to be a stock one unless you want it, then it will probably work.
Cytality said:
Any MDL ROM should work if you KNOW you're on MDL baseband. I can't tell if you are or not, only you would know that. Did you ever do the new MF9 update? If not then you're probably on MDL.
So if you download any MDL ROM, doesn't have to be a stock one unless you want it, then it will probably work.
Click to expand...
Click to collapse
I'll give that a shot. The internet here at work is awful, so its going to take a while.
Also, what if I the mf9 kernal got flashed at some point? Does that make any difference?
amishbobinc said:
I'll give that a shot. The internet here at work is awful, so its going to take a while.
Also, what if I the mf9 kernal got flashed at some point? Does that make any difference?
Click to expand...
Click to collapse
You can always flash an MDL kernel back, like the KT kernel. Whatever ROM you pick, it will come with the appropriate kernel (unless you're doing a stock ROM.)
I'm assuming you're running MDL modem and baseband, because your post implies you just flashed TWRP for the first time yesterday as if you just bought the phone or something.
So let's assume for all intensive purposes that you are MDL. Then you need to find a kernel and a ROM that are MDL, not MF9, and flash those via TWRP after you do a wipe of everything (also from within TWRP).
An alternate option is you could attempt to just upgrade yourself to MF9 right now... download the updated modem and stuff from noobnl's post, Odin flash it as per the instructions, when done boot back into TWRP recovery and then install a new MF9 ROM, like TriForce or something.
Cytality said:
You can always flash an MDL kernel back, like the KT kernel. Whatever ROM you pick, it will come with the appropriate kernel (unless you're doing a stock ROM.)
I'm assuming you're running MDL modem and baseband, because your post implies you just flashed TWRP for the first time yesterday as if you just bought the phone or something.
So let's assume for all intensive purposes that you are MDL. Then you need to find a kernel and a ROM that are MDL, not MF9, and flash those via TWRP after you do a wipe of everything (also from within TWRP).
An alternate option is you could attempt to just upgrade yourself to MF9 right now... download the updated modem and stuff from noobnl's post, Odin flash it as per the instructions, when done boot back into TWRP recovery and then install a new MF9 ROM, like TriForce or something.
Click to expand...
Click to collapse
Ok so I flashed the stock kernal and then tried flashing a MDL rom. The phone now starts up, but after logging into my google account I only get a black background screen, like the launcher is missing. I CAN hover use my notification bar to turn things on and off but I can't get to settings.
amishbobinc said:
Ok so I flashed the stock kernal and then tried flashing a MDL rom. The phone now starts up, but after logging into my google account I only get a black background screen, like the launcher is missing. I CAN hover use my notification bar to turn things on and off but I can't get to settings.
Click to expand...
Click to collapse
Whats the rom you are using?
Cytality said:
Whats the rom you are using?
Click to expand...
Click to collapse
ROM | MDL & MF9 | iNTriNsiC | Simplicity is Performance | Odexed | 7/16/13
http://forum.xda-developers.com/showthread.php?t=2356429
I downloaded the MDL version.
amishbobinc said:
ROM | MDL & MF9 | iNTriNsiC | Simplicity is Performance | Odexed | 7/16/13
http://forum.xda-developers.com/showthread.php?t=2356429
I downloaded the MDL version.
Click to expand...
Click to collapse
While you have the phone turned on, go in settings and see what your baseband version is. If it ends in MDL then you're good.
After that, I don't know. I've never used that rom personally, it could be an issue with the rom itself, nothing really wrong with your phone. You can try to wipe and reinstall, or just try a different ROM.
Ok got it!!
TWRP and clockworkmod were both NOT formatting like they said they where. I had to manually go in and erase everything except the external SD. Then I did a clean install and everything works great.
Thank you for your help!
Hi everyone,
So i'm a complete noob at this whole .. custom rom thing, and I just googled instructions, and followed them. Except now I think I may have lost my recovery mode ... everything.
I bought the phone off craigslist, and it had a 4.4 kitkat installed. But I didnt like it and wanted the stock version, so i tried installing 4.3 on it. Except now I cannot get past the samsung logo (not to mention the boot animation is not right) and I cant even get into recovery mode.
When i press the buttons I just get a "recovery booting' on the top left corner, the samsung galaxy s4 logo for about 5 seconds and then everything turns off.
HELP! Ive not even had this phone for 24 hours yet!
I tried using Kies and Odin to get the roms to install, but I think theres something wrong with recovery or the boot.. both kies and odin say that the installation was successful, but I cannot get past boot or get into recovery at all. (i can get into download fine)
I read about the whole mf3 soft-bricking but I'm using a i337m phone, the Canadian one. is there a chance that that could happen to me too? I didnt check which version I was using before I tried odin because stupid me thought that all i337m devices work the same.
Best course of action would be to download the complete stock ROM and modems. As much stock as you can find. There's a thread for all the customs. Boot into download mode, then use Odin to flash the ROM.
If it then fails to boot ... try flashing CWM and reboot into recovery ... erase and restore all data and hope for the best.
ChrisDuffy20 said:
Best course of action would be to download the complete stock ROM and modems. As much stock as you can find. There's a thread for all the customs. Boot into download mode, then use Odin to flash the ROM.
If it then fails to boot ... try flashing CWM and reboot into recovery ... erase and restore all data and hope for the best.
Click to expand...
Click to collapse
Ok, so I tried using a 4.2.2 stock ROM, and now I got recovery to work... Except I can't get wifi to work and i now have..
"kernel not seandroid enforcing
set warranty bit: kernel"
I also tripped Knox... (cannot reset?)
Is the whole kernel thing a problem? and How should I go about trying to get back wifi? Would it be a bad idea to use Kies or Odin to install 4.3 over what I have now, now that I have recovery working again?
For WiFi flash mf3 module files on safe strap forum
mf3 rooted SHOstock
chiynadoll said:
Ok, so I tried using a 4.2.2 stock ROM, and now I got recovery to work... Except I can't get wifi to work and i now have..
"kernel not seandroid enforcing
set warranty bit: kernel"
I also tripped Knox... (cannot reset?)
Is the whole kernel thing a problem? and How should I go about trying to get back wifi? Would it be a bad idea to use Kies or Odin to install 4.3 over what I have now, now that I have recovery working again?
Click to expand...
Click to collapse
I would definitely go back as far stock as you can if you just want essential functionality. However, if you want something fun....there's no harm in putting it to a custom ROM / Kernel / Modem
I personally use MDOB (stock, rooted and runs my Galaxy Gear) with Toonzez (sp?) Kernel.
Check the MDOB thread. I was given a lot of help by members in there on the last few pages.
Do factory data reset, and without letting the phone boot into OS pull battery and Odin flash 4.3 official software
chiynadoll said:
Ok, so I tried using a 4.2.2 stock ROM, and now I got recovery to work... Except I can't get wifi to work and i now have..
"kernel not seandroid enforcing
set warranty bit: kernel"
I also tripped Knox... (cannot reset?)
Is the whole kernel thing a problem? and How should I go about trying to get back wifi? Would it be a bad idea to use Kies or Odin to install 4.3 over what I have now, now that I have recovery working again?
Click to expand...
Click to collapse
Knox cannot be untripped, nor will it ever. So forget that idea. Flash a stock firmware with odin, reroot, and go from there. Easiest way to get kernel back stock if you're new to odin and flashing in general. Tick auto - restart in odin, use pda button in odin to select the firmware, and flash. Lots of guides with steps and captures to assist with odin around here. Check out a return to stock thread for your make /model/region
Sent from my SGH-I337M
Just so you know. If you update OTA or via kies to the stock firmware you will no longer be able to flash custom ROMs anymore. I would download a custom 4.3 TW ROM. For your WiFi issue I would check your APN setting under more networks.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Hey everyone,
So after a whole month, I still haven't gotten anywhere. I managed to get an OS onto the phone so that its no longer "soft bricked" but it cannot connect to wifi, and can't call. The call goes through, but then the phone freezes. It also will be lagging for a long time after the call attempt.
I'm wondering if I should just try flashing it a couple of times again with a custom rom since I can't use kies? Btw, I dont know if this is possible, but i feel like i might have lost stock recovery. I can't factory reset, or anything that has to do with recovery what so ever. It just does not exist on this phone.....
Bricked SG4
I have the Samsung GS4 i337 mk2 v4.3 (rooted) for a month and ending up with just the wait..... android downloading, don't know if that is a hard or soft brick, but took it to the AT&T distribution center in Portland, Or and they flashed it back to stock, FREE, no questions asked. Just though everyone would like to know.
I am having the same issue
ChrisDuffy20 said:
I would definitely go back as far stock as you can if you just want essential functionality. However, if you want something fun....there's no harm in putting it to a custom ROM / Kernel / Modem
I personally use MDOB (stock, rooted and runs my Galaxy Gear) with Toonzez (sp?) Kernel.
Check the MDOB thread. I was given a lot of help by members in there on the last few pages.
Click to expand...
Click to collapse
ChrisDuffy20 said:
Best course of action would be to download the complete stock ROM and modems. As much stock as you can find. There's a thread for all the customs. Boot into download mode, then use Odin to flash the ROM.
If it then fails to boot ... try flashing CWM and reboot into recovery ... erase and restore all data and hope for the best.
Click to expand...
Click to collapse
I still want to go with something like slim or carbon so can I use odin and just flash the rom I have on my comp??
SaHiLzZ said:
Do factory data reset, and without letting the phone boot into OS pull battery and Odin flash 4.3 official software
Click to expand...
Click to collapse
JLopez149 said:
Just so you know. If you update OTA or via kies to the stock firmware you will no longer be able to flash custom ROMs anymore. I would download a custom 4.3 TW ROM. For your WiFi issue I would check your APN setting under more networks.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can someone post a link to some stock firmware... I've looked for hours
Tank you