same errorSent from my GT-N5110 using xda app-developers app
same errorSent from my GT-N5110 using xda app-developers app
I came from sac's rom, it's not working yet. I'd wait still. I'm wiped and have no rom D:Might be a dumb question lol.... but I'm on Sac's ROM right now, can I just flash this and I'll 100% be on 4.3 MJA?! Or will there be some missing stuff and be different like if I took the OTA from stock unrooted? Thanks!
My MD5 matches, but won't flash with same error.Got md5 mismatch too.
No worries. CNexus will figure it out.
F5, F5, F5![]()
Not yet, still waitingis there a firmware/modem file us rooted folk can flash to get on the new base?? or we still waiting for a dev to rid the OTA apart?
No. Not right now.is there a firmware/modem file us rooted folk can flash to get on the new base?? or we still waiting for a dev to rid the OTA apart?
should be a simple fix just back out to General in the main Sprint S4 forum your going to see Stock MF9.zip file *or you might be best going to Orig Android Dev thread and going to the firmwares with Recovery/BusyBox etc etc than just simply use ODIN (they'll be links and tutorials) YOU CAN DO ITTT ------ODIN thats it...i did that ishboo a few weeks ago ur good just be patient....read everythin and write it down tooso guy's i am truly ****ed.so i went back to mdc stock earlier and then i updated to mdl then mf9 and afterwards mja stock. but... then i had a issue so i had to go to recovery and factory wipe. then it booted but i had nothing left. so i tried going back to mf9 deodexed and well i couldnt. so i used the cf root and installed twrp recovery and then tried restoring my back up then it wouldnt boot so afterwards i tried to odin back to mdc stock and it didnt work.it would fail because in download mode knox blocked it i guess. anyway i tried restoring and on top it says kernel is not seandroid and well it took a while to boot. so my baseband and software are at mja ._. wifi doesnt work and i just tried this and it had error :/ so im basically screwed
I think I am a little worse, I can't even boot into my MJA anymore.so guy's i am truly ****ed.so i went back to mdc stock earlier and then i updated to mdl then mf9 and afterwards mja stock. but... then i had a issue so i had to go to recovery and factory wipe. then it booted but i had nothing left. so i tried going back to mf9 deodexed and well i couldnt. so i used the cf root and installed twrp recovery and then tried restoring my back up then it wouldnt boot so afterwards i tried to odin back to mdc stock and it didnt work.it would fail because in download mode knox blocked it i guess. anyway i tried restoring and on top it says kernel is not seandroid and well it took a while to boot. so my baseband and software are at mja ._. wifi doesnt work and i just tried this and it had error :/ so im basically screwed
When I was in a tight spot, flashing the stock MF9 tar through Odin always saved the day for me. In my experience, the Odin + tar method has been more reliable than a zip method.I think I am a little worse, I can't even boot into my MJA anymore.I wasn't having success with root, so I started modifying the system partition (made a backup first). I removed some Knox.apks, etc, etc. But then when I tried to boot, it would just hang on the Galaxy S4 screen. So I thought no problems, restore system from backup, same issue. So then I thought I'd flash this Stock/Rooted Zip. Errors on flashing, so I copied over the system/boot/update script files and replaced it in an existing root MF9 zip, making sure only MJA files where there, and the flash worked successfully. But a reboot still hangs at the Galaxy S4 logo. I am now doing a complete restore of my backup system, boot, and data. If that doesn't work I will try wiping data, and if that doesn't work, maybe I can flash a stock MF9 zip in the meantime...
The problem is you can't ODIN back to MF9 from what everyone has tried. That is why the zip is the only method that might work. From what crawrj said MF9 zip worked for him. Then I can wait for a better MJA zip to restore my boot/system.When I was in a tight spot, flashing the stock MF9 tar through Odin always saved the day for me. In my experience, the Odin + tar method has been more reliable than a zip method.
I think im In the same boat as you try flashing 4.3 rom I got all the same things as you did do I flashed 4.3 PACMAN and my phone working fine except the wording on the boot screen everything else is good including wifi just an idea for uThe problem is you can't ODIN back to MF9 from what everyone has tried. That is why the zip is the only method that might work. From what crawrj said MF9 zip worked for him. Then I can wait for a better MJA zip to restore my boot/system.
**** Update, restoring system, boot, and data didn't boot, factory resetting didn't fix the stuck at boot screen, and now I am flashing MF9 with the zip.
---------- Post added at 12:11 AM ---------- Previous post was at 12:07 AM ----------
One more update, flashing the MF9 zip didn't work either.... I get the same conditions as the others. One final note, it doesn't hang on the boot screen (S4 Logo), it sits there for about a minute, then goes to a blakc screen, vibrates twice and then shows the boot logo again, and repeats. I am going to have to turn it off, charge it, and maybe activate an old LG Optimus on my account until I can get my S4 fixedMessage me if you have ideas or post to this thread, I'll be watching it. But I'm going to head to bed in a minute
You mean like the Verizon S4 people, we're no longer able to Odin back to a previous build? If so, that's horrible~! Friggin Samsung and/or Sprint.The problem is you can't ODIN back to MF9 from what everyone has tried. That is why the zip is the only method that might work. From what crawrj said MF9 zip worked for him. Then I can wait for a better MJA zip to restore my boot/system.
**** Update, restoring system, boot, and data didn't boot, factory resetting didn't fix the stuck at boot screen, and now I am flashing MF9 with the zip.
---------- Post added at 12:11 AM ---------- Previous post was at 12:07 AM ----------
One more update, flashing the MF9 zip didn't work either.... I get the same conditions as the others. One final note, it doesn't hang on the boot screen (S4 Logo), it sits there for about a minute, then goes to a blakc screen, vibrates twice and then shows the boot logo again, and repeats. I am going to have to turn it off, charge it, and maybe activate an old LG Optimus on my account until I can get my S4 fixedMessage me if you have ideas or post to this thread, I'll be watching it. But I'm going to head to bed in a minute
bro trust me you HAVE TO 1. boot into w.e recovery you have if u dont have one skip this than 2. d.l the TAR file/firmware etc etc for (MF9) u can choose rooted unrooted stock etc w/recovery w/stock recovery etc w.e you want (u want to be able to boot into recovery to wipe wipe wipe wipe wipe but im not an expert so maybe u dont just download ODIN follow the directions everything that u said up there just made me dizzy lol (sorry not being mean) just go to a tutorial or youtube/google it i want to say 85% chance that fixes ur phone completelyThe problem is you can't ODIN back to MF9 from what everyone has tried. That is why the zip is the only method that might work. From what crawrj said MF9 zip worked for him. Then I can wait for a better MJA zip to restore my boot/system.
**** Update, restoring system, boot, and data didn't boot, factory resetting didn't fix the stuck at boot screen, and now I am flashing MF9 with the zip.
---------- Post added at 12:11 AM ---------- Previous post was at 12:07 AM ----------
One more update, flashing the MF9 zip didn't work either.... I get the same conditions as the others. One final note, it doesn't hang on the boot screen (S4 Logo), it sits there for about a minute, then goes to a blakc screen, vibrates twice and then shows the boot logo again, and repeats. I am going to have to turn it off, charge it, and maybe activate an old LG Optimus on my account until I can get my S4 fixedMessage me if you have ideas or post to this thread, I'll be watching it. But I'm going to head to bed in a minute
http://forum.xda-developers.com/showthread.php?t=2485502 (SORRY IF I JUST DID SOMETHING IM NOT SUPPOSED TO I JUST FEEL FOR THIS SITUATION BECAUSE IT HAPPENED TO MEbro trust me you HAVE TO 1. boot into w.e recovery you have if u dont have one skip this than 2. d.l the TAR file/firmware etc etc for (MF9) u can choose rooted unrooted stock etc w/recovery w/stock recovery etc w.e you want (u want to be able to boot into recovery to wipe wipe wipe wipe wipe but im not an expert so maybe u dont just download ODIN follow the directions everything that u said up there just made me dizzy lol (sorry not being mean) just go to a tutorial or youtube/google it i want to say 85% chance that fixes ur phone completely
The problem is you can't ODIN back to MF9 from what everyone has tried. That is why the zip is the only method that might work. From what crawrj said MF9 zip worked for him. Then I can wait for a better MJA zip to restore my boot/system.
**** Update, restoring system, boot, and data didn't boot, factory resetting didn't fix the stuck at boot screen, and now I am flashing MF9 with the zip.
---------- Post added at 12:11 AM ---------- Previous post was at 12:07 AM ----------
One more update, flashing the MF9 zip didn't work either.... I get the same conditions as the others. One final note, it doesn't hang on the boot screen (S4 Logo), it sits there for about a minute, then goes to a blakc screen, vibrates twice and then shows the boot logo again, and repeats. I am going to have to turn it off, charge it, and maybe activate an old LG Optimus on my account until I can get my S4 fixedMessage me if you have ideas or post to this thread, I'll be watching it. But I'm going to head to bed in a minute