I am getting stuck on any and every custom ROM no matter what kernel I install with it. It seems as though my device is not accepting system to be installed. I end up installing ROM and then when I try to boot I get a reboot 10 seconds later after failing to get past the Boot Logo and then I check file manager inside of TWRP and don't get anything inside of System folder along with boot folder no matter what ROM Or kernel. have attempted wiping everything through TWRP. Have attempted Odin back to stock(Which Boots Me Up Flawlessly But Happens Again When Installing Recovery Through Odin And Reinstalling ROM) and even happens when attempting to restore backup I have. Weird since Odin works but not ROM nor kernel boots me up. Started happening last night and continues to happen again and again and again now with zero success. Any ideas?
Sent from my SPH-L720 using Tapatalk 4 Beta
Also, when installing Rooted Stock ROM Odexed from within TWRP I get "Not Rooted" message from recovery but when installing DeOdexed I get "Incorrect Permissions, Do You Want To Fix" message. I have tried selecting yes AND no on both to no avail.
Sent from my SPH-L720 using Tapatalk 4 Beta
Really!? Not a soul has an idea!? Lol
Sent from my SPH-L720 using Tapatalk 4 Beta
I would suggest going back to stock with ODIN and then trying a different recovery. I've had no issues flashing many custom ROMs with OUDHS recovery.
http://forum.xda-developers.com/showthread.php?t=2254678
I didnt have an issue whatsoever when I first obtained the device. Ia also getting the infamous "Get PIT Mapping" message when runnung ODIN. Looks like I just needs to repartition the device once I get my hands on the PIT file. Either way, I have gone to stock and tried all of the available recoveries I am aware of to no avail. Weird.
Sent from my SPH-L720 using Tapatalk 4 Beta
was having this ame issue when i first got my S4 and it was because my root was not sticking. get a SU.zip (easily found if you google it) and try flashing that before you flash anything and see if it helps. i am told this was an issue with earlier binarys being used in recovery but im by no means a dev so i could say for sure. also if your using TWRP make sure that when wiping your doing system,data,dalvik,cache.
Related
Alright I have searched all day and can not seem to find a resolution to my problem. It is my fault I shouldn't fix something that isn't broke but it has resulted in issues and I would appreciate it if someone could help me.
I had twrp 2.5.0.2 installed running GE 4.2.2 ROM with MF3 radios installed and GE kernel v11. I saw twrp had a update to 2.6.0.0 and I decided to install it via goo manager it booted up in recovery with the "the software is unauthorized by att" screen and I can do volume down + power after that to reboot phone and not have issues as far as getting my phone booted and working on all the above. But the problem I am having now I have lost custom recovery. I have tried goo manger again as well as some on click root/recovery methods from these forums and all result in the same back to the unauthorized screen mentioned above its like it won't boot into a custom recovery. Any advice is greatly appreciated.
Sent from my Nexus 7 using xda app-developers app
Maybe try ROM manager and install cwm .it will pop up in ROM manager as the T-Mobile s4 but that's what I used to install the first recovery image,then I used that recovery to flash the auto Loki recovery.I have used the same plain auto Loki recovery since then.
Sent from my SAMSUNG-SGH-I337 using xda premium
Just tried that as well. Still not working. When I takes me to that unauthorized page top left it says "secure fail: kernel". But when I reboot the phone normal it comes up just fine....so that tells me its getting past with Loki to boot up my ROM and kernel but for some reason it will not take a custom recovery anymore when I have had one installed previously.
Sent from my SGH-I337 using xda app-developers app
If memory serves me right the Google Edition ROM will make TWRP / GooMananger think you have a 9505(G) and thus it will install that version. So you installed a non-loki'd recovery.
Use Odin, go back to AMDL firmware. (Take SIM out before doing so so it wont download the AMF3 update). Redo Root + Recovery. BEFORE you flash another rom, install GooManager and then update from there. You will be running stock firmware so it will identify the model correctly. Then flash your custom ROM.
Forgive me for being noob when it comes to Odin. But does this OTA the software or will I need to get Odin on my desktop?
Sent from my SGH-I337 using xda app-developers app
RESOLVED:
- Flashed a stock firmwire image from Sammobile using Odin. (AMDL)
- Did a factory reset in the stock recovery TWICE to get it to finally boot.
- Rooted with motochopper
- Installed TWRP
- Back to Task650.
Okay, so I'm a bit stuck. I was running the newest Task650 rom and KT's 9/17 kernel.
I updated to the 10/20 kernel as soon as it was released and it bugged my phone. Blew up everything, glitched my DPI and colors. It was unusable, however the weirdest part is that my custom recovery was removed so I can't seem to flash the old kernel to get my device back to normal.
I tried using odin but it just keeps failing, so I really am unsure what to do now. If I could get the previous kernel back onto it, it would be fine.
Any help? I can't seem to find a .tar.md5 file for TWRP or clockworkmod to flash a new recovery in Odin. I tried Philz .tar.md5 files but it fails as well.
Click to expand...
Click to collapse
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
jball said:
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
I cannot use the Google Playstore.. my entire screen is over scaled and impossible to navigate.
So no use of DPI settings.can you use ADB or terminal emulator
Sent from my SAMSUNG-SGH-I337 using xda premium
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
xBeerdroiDx said:
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Click to expand...
Click to collapse
I managed to get the latest stock firmwire (AMDL 4.2.2) off of Sammobile. I did successfully flash the stock .tar.md5 image through Odin, using the PDA slot. Phone seemed to restart and boot right up, but now gets stuck at the AT&T logo. It makes the boot sound and than BAM; frozen.
Now I am truly stuck. Seems flashing the stock image didn't work.. unless I did it wrong through Odin but I doubt it. These are the steps I took,
- Start Odin
- Connect phone in downloaded mode
- Click PDA (select the I337UCUAMDL_I337ATTAMDL_ATT.tar.md5 file)
- Wait for it to confirm the firm, than hit start.
- After waiting about 5 minutes it's successful.
Am I doing ANYTHING wrong?
Te3k said:
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
Click to expand...
Click to collapse
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
jd1639 said:
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
Click to expand...
Click to collapse
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Br4nd3n said:
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Click to expand...
Click to collapse
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
jd1639 said:
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
Click to expand...
Click to collapse
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Good deal
Sent from my GT-I9505 using xda premium
Br4nd3n said:
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Click to expand...
Click to collapse
:good:
Let me preface this by saying I have searched here and other websites and have tried the methods I have found and cannot get the issue fixed. ANY help is greatly appreciated.
I have a sprint s4 l720. I rooted it and installed a custom rom and twrp a few months ago. I recently saw that 4.4 came out and wanted to try a new rom. I first booted into recovery and tried to restore my system back to the original stock rom that I had backed up when I first installed the new one. I was able to restart it and it loaded fine but if I pull the battery or do a restart it gets stuck at the samsung splash screen. I have tried advanced wipe, format data, wipe dalvik and cache and even installing other roms and it still gives me the same behavior. I have tried other methods to re-install the stock rom and I keep encountering issues. I downloaded the most recent ODIN and the samsung USB drivers and "jflterspr16gb.pit" and sprints .tar.md5 file. It loads into odin fine and shows the added on the dialogue box and I load the respective files into odin and it keeps failing. I am at a lost.
All I want is to be able to add either the stock rom or preferably the custom 4.4 rom and work as it used to. Restart when needed and not get stuck at the boot screen. ANY help is much appreciated. any ideas on what I am doing wrong? Thanks guys!
Anything 4.4 at this point is custom. Just boot into recovery, wipe and flash the 4.4 ROM.
Sent from my SPH-L720 using Tapatalk
if your at ota MJA then trying to odin md5 will not work. Did you take the MJA update?
frostedunit said:
Anything 4.4 at this point is custom. Just boot into recovery, wipe and flash the 4.4 ROM.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I have tried that. I boot into twrp and have tried formatting all data and just wipe data and then I restart and load gummy 4.4 and the gapps for it and then wipe the dalvik and cache. It will boot into the gummy rom fine and give me no issues, but it is if I try to restart it or power it down and power it back on is where it gets stuck at the samsung splash screen.
rheller219 said:
if your at ota MJA then trying to odin md5 will not work. Did you take the MJA update?
Click to expand...
Click to collapse
I am not for sure what the MJA is. Could you pleaes elaborate to me? Thanks.
pgrim85 said:
I have tried that. I boot into twrp and have tried formatting all data and just wipe data and then I restart and load gummy 4.4 and the gapps for it and then wipe the dalvik and cache. It will boot into the gummy rom fine and give me no issues, but it is if I try to restart it or power it down and power it back on is where it gets stuck at the samsung splash screen.
I am not for sure what the MJA is. Could you pleaes elaborate to me? Thanks.
Click to expand...
Click to collapse
Where does it stop on the odin error? And dont use the pit file. Try again without the pit file.
Sent from my SPH-L720 using xda app-developers app
You should always be on a stock ROM of the latest version prior to flashing an unofficial, newer Android ROM.
For example:
If you're trying to flash 4.4, you should be on stock 4.3 such as this: http://forum.xda-developers.com/showthread.php?t=2505025
MJA is the latest official 4.3 build for the Sprint S4.
If you're on 4.2, you should update to 4.3 stock, then flash 4.4. This generally prevents any unexpected results.
Furthermore, always ensure you are flashing from a trusted recovery such as TWRP and CWM.
Occasionally, one recovery will not run the install script properly.
If you are certain you are doing the install right, you can try from another recovery.
Additionally: If you are having trouble with Odin on Windows 8, ensure your computer does not report a driver malfunction when you plug your device in after entering download mode.
This can possibly be fixed by running Odin as administrator. Or, you can attempt to manually install the USB drivers by downloading them, disconnecting from the Internet, uninstalling previous drivers, then manually installing the USB package you downloaded.
Sent from my SPH-L720 using xda app-developers app
R0CKSTAR3N3RGY said:
You should always be on a stock ROM of the latest version prior to flashing an unofficial, newer Android ROM.
For example:
If you're trying to flash 4.4, you should be on stock 4.3 such as this: http://forum.xda-developers.com/showthread.php?t=2505025
MJA is the latest official 4.3 build for the Sprint S4.
If you're on 4.2, you should update to 4.3 stock, then flash 4.4. This generally prevents any unexpected results.
Furthermore, always ensure you are flashing from a trusted recovery such as TWRP and CWM.
Occasionally, one recovery will not run the install script properly.
If you are certain you are doing the install right, you can try from another recovery.
Additionally: If you are having trouble with Odin on Windows 8, ensure your computer does not report a driver malfunction when you plug your device in after entering download mode.
This can possibly be fixed by running Odin as administrator. Or, you can attempt to manually install the USB drivers by downloading them, disconnecting from the Internet, uninstalling previous drivers, then manually installing the USB package you downloaded.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Is there a way I can fresh restart my phone? I do not have any recovery files since I wiped my phone in its entirety and I had no backed it up on the SD card, rookie mistake, I know. I don't necessarily need 4.4, but what I do need is my phone to boot up properly whenever I choose and not have to boot into recovery, wipe the phone and then when I turn it on have to go through the setup process.
ROMANTiC KiD said:
Where does it stop on the odin error? And dont use the pit file. Try again without the pit file.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I will have to look where it stops again tonight. but it does connect by showing the "pass" on the odin box on the left. could it be that I have the wrong odin? I noticed the top of odin it shows epic 4g when I have a galaxy s4, is this ok or is there a way I can change that? I dl the odin from a forum that was specifically a tutorial on how to flash the galaxy s4, sprint specifically, so I figured it would be the correct one. Also, I did try again without the pit file and it still failed.
Thanks for the help so far guys
Some of the Odin packages have multiple versions thrown together. Make sure to use the highest version number (3.07?) And that you are putting the .tar in the PDA slot. If all else fails, try deleting the .md5 off the end of the file before you load it in Odin. Used to work on OG Epic sometimes.
Sent from my SPH-L720 using Tapatalk
So I was running along running a dandroid ROM based on 4.4 with no issues. Decided to flash Ktoonez kernel with newest 12/14/13 ROM. Went to CWM did full wipe and format /system as I usually do when install new ROM. Flashed ROM then flashed ktoonez which failed with status 0 then flashed loki and rebooted, decided to reboot instead of reinstall cause the kernel installation failure said it didnt change anything to I though I would be ok...guess not
Stuck with phone just vibrating on black screen. Can't access any recovery, only Download mode.
In download mode I flashed the STOCK ATT Rom with Odin and it said PASS but the phone is still doing the same vibrating every couple seconds on a black screen unless in DOWNLOAD mode.
Any advice would be greatly appreciated.
There's a 16 gig pit file floating around here that might help you get back into recovery after that flash the stock ROM back after you flashed the pit file.
http://forum.xda-developers.com/showthread.php?t=2323019
I think this is it I'm not too sure because instructions say flash via heimdall but there's an Odin zip somewhere in the thread.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I never had problems with flashing new firmware. But yesterday I thought to flash the newest stock rom I9505XXUFNC4, and I got:
Nand write start!
Complete(Write) operation failed.
After that, I cannot boot anymore until I flash a Pit file. I also tried to install TWRP, CWM and the last rom. Nothing, nothing and nothing. Now my root is gone and my wifi doesn't work anymore.
I'm scared that when I factory reset the thing, that I can't install a new rom. Can someone 'please' advice me what to do? For example, can I install stock rom with ADB?
I would re-download the stock firmware and try again. Maybe try an older version
Sent from my SAMSUNG-SGH-I727
I downloaded it a few times. And the other version was working fine. But as you can read in my post: I can't install anything but the pit file.
Sent from my GT-I9505 using Tapatalk
choice2rejoice said:
I downloaded it a few times. And the other version was working fine. But as you can read in my post: I can't install anything but the pit file.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
So, it'll boot only of you flash the pit first in Odin?
Sent from my SAMSUNG-SGH-I727
When I try to flash something, I got that error. After that it's not booting anymore. 'Problem updating firmware' message. After flashing the pit, it's booting like normal.
I tried other USB ports and cable, as some people on the net ar suggesting, but that didn't worked.
Sent from my GT-I9505 using Tapatalk
choice2rejoice said:
When I try to flash something, I got that error. After that it's not booting anymore. 'Problem updating firmware' message. After flashing the pit, it's booting like normal.
I tried other USB ports and cable, as some people on the net ar suggesting, but that didn't worked.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I'll have to say, I've never seen that before. I'm not sure what to tell you.
Sent from my SAMSUNG-SGH-I727
I guess that's why I can't find a solution
Sent from my GT-I9505 using Tapatalk
choice2rejoice said:
I guess that's why I can't find a solution
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Can you boot into recovery or download mode?
What recovery do you have installed?
I have a Galaxy S4 LTE-A E330SK and have had problems similar to that when trying to install an older firmware or same version on top of the version already on there. Recovery wouldn't boot, and if Android booted, everything would force close. (I like breaking my own phone just to see if I can fix it lol.)
Any time I had severe problems that would not enable me to boot or use Odin, I boot into Recovery, under Advanced, format System, Data, Cache, sdcard, media/sdcard and reboot. That erases everything (your operating system and everything on sdcard0) and if you are stuck on the Samsung Galaxy S4 logo, then you are good to go. Reboot into Download mode, connect your cable, and open Odin. (By the way I also found out you will get errors if you try to flash twice in a row without closing and reopening Odin, so keep that in mind.)
This I would consider a clean install of Android.
Now for the iffy part... Everybody says do NOT check the repartition box when you flash the new ROM. But what I do is make sure I have the correct PIT file for my firmware version. Add PIT file under PIT in Odin, add your firmware md5 file under PDA (or AP,) tick repartition, untick Auto-Reboot (my E330SK would automatically revert back to stock recovery with Auto-Reboot selected.) F Reset Time ticked, and Start. You should have no errors now.
There might be a better way without having to format those filesystems I've stated, but haven't found it. This way has always gotten me out of a sticky situation.
Keep in mind as well, I have never been able to downgrade to an older version of Android. So recommended if you try this do it with the same firmware or newer version that is currently on your phone.
---------- Post added 4th April 2014 at 12:02 AM ---------- Previous post was 3rd April 2014 at 11:56 PM ----------
choice2rejoice said:
I guess that's why I can't find a solution
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Might I mention I am using CWM Recovery as well
Yeah but I tried to install a new version and tried afterwards the current version on my phone. Tried as I already stated, several things to install and the only thing I could install, was the pit file.
Yesterday I installed CMW with Heimdall method. That worked. After that I install root from within CMW with ADB. And because I got an old backup, I didn't wanna go back that far and only flashed (with ADB) boot.img. Now I got a working phone.
I really want to update to latest firmware, but I'll try after the weekend. Don't want my weekend to be headached
Anyway. Thx for your response!
Sent from my GT-I9505 using Tapatalk
After trying and trying and trying, finally one of the USB ports let me push the new firmware (NC9) to my phone! (with Odin). After that my sd-card was unmounting itself all the time and giving errors as filesystem not recognized and being blank. Location methods didn't work correct etc.
Yesterday I managed to flash the NC4 firmware, and all is working well now!
Sent from my GT-I9505 using XDA Premium 4 mobile app