I'm not so excited about posting a question as I see many have gone unanswered specifically in this variant's section, but here goes nothing.
I accidentally downloaded DU (Dirty Unicorns) for the T-Mobile variant by searching up DU for tje S4 on Google and sadly i forgot to specify "Sprint" or "L720". While there where no issues running the ROM, I decided I had to flash back to a Sprint based rom. Somewhere down the road I decided to flash back to stock (using the stock OD2 currently available) and now my device still shows up as an M919 with absolutely no data (seems to be roaming if I'm not mistaking).
I tried to reflash TWRP, flash Sprint based roms (AOSP will fix the issue temporarily, while TW roms such as Wicked X will experience the same issue), FULL wiping through TWRP, and then reflashing stock, but the issue persists. Does anybody happen to have a solution, suggestion, or idea? And a HUGE thanks in advanced.
I think you need to flash a full firmware with a pit file in Odin. Just visit sammobile, create an account and you're good to go. Lemme know if you have further questions
Try to flash OD2 .tar (get it from sammobile) with odin and then root ur phone again. That should fix the problem
Never heard of a pit file, always thought that it was limited to .tar and .bin, but I found my solution which I will post below.
PS How do I hit the thanks button on your comment since it has no "interface" to it?
I tried that and it didn't work. I already had OD2 as my default "flash if something goes wrong".
I'll post my solution in a new answer below.
Sorry for neglecting my own thread to the both of you who answered, I'm just not liking all of the new updates to the XDA website which will crash my browser or freeze all my tabs due to an overloaded amount of crap and ads running in the background of the site (sorry XDA, huge fan, but not as of lately). Apart from that, I also experience issues on the mobile version and right now I cannot find the button to thank the both of you.
ANYWAYS, back on topic, I was able to solve my issue by flashing an older 4.4.2 based stock (NAE) THEN flashing the OD2 right after that. Oddly enough, I was able to update to OH2 (stagefright patch) over the air. Doesn't the ability to update OTA die once you trip the KNOX Warranty bit???
And thank you both. If somebody explains how I can hit your thanks button now that XDA has updated yet again, I will thank you both properly
Related
Hello Guys
Well, let me get straight to the point. After my old rom (Revolution HD3) was draining my battery pretty fast, i decided to update to 4.4.2. Well, i downloaded the latest 4.4.2 for switzerland from sammobile.com. I flashed it and it somehow was all laggy and i had fc's the whole time. After some time i was able to use the phone anyway, but it was laggy. And the problem was that my 3G connection was EXTREMELY slow. I got connection time outs the whole time and wasnt able to download anything. Well, i thought it was the rom i flashed trough odin, so i downgraded to 4.2.2, my original rom, and updated trough KIES. The rom wasnt laggy anymore, but the 3g/4g was slow. I tried different Modems and Kernels. Nothing Helped. I then decided im going back to a custom rom but the flash failed. Then i tried another rom and it failed again. So i thought it may was cause i was on 4.4.2 and tried to flash a custom rom that was 4.2.2. I then tried to reflash my stock rom trough odin, and it FAILED. And that's how i bricked my phone. I can still enter Download Mode, but can't enter the recovery anymore. What do i do? I'd like to solve both problems.
Thanks guys
Btw: I've got an I9505
I assume you didn't wipe anything before you flashed stuff? Thats like rule number 1 to do.
You can try flashing a recovery true Odin.
Hej Guys
Um.. Just to let you guys know, it is possible to downgrad to 4.2.2 from 4.4.2. I just did it this morning and had sucess. But the problem with the really slow internet connction still is here, when im on a 4.4.2. And, it is the same with custom roms running 4.4.2. I tried different kernels and modems, nothing helped so far. As soon as i was back to 4.2.2 it had the usual connection speed. I called my provider and also called samsung itself. Obviously, they both told me to bring the phone back for garantuee. But well, as i know it's a software problem and not hardware, i wont do that. So can you guys help me? What should i do next? Actually im back on 4.2.2. Thanks
Edit: Oh, and ofc, i did everything like wiping/factory resetting, wipping preoload etc. It's not my first time flashing.
It's not possible to downgrade from 4.4.2 to 4.2.2! End of..
Sent from my GT-I9505 using xda premium
Are you serious dude? Im running 4.2.2 right now. What is your point?`I didnt even ask about it. I asked about a solution to the problem that i get slow 3G/4G on my I9505 when running 4.4.2. If you want a proof Pic about it running 4.2.2, i can give you one. But i dont really get what your point is.
Hang on hang on hang on, it is common knowledge that you cannot downgrade from official samsung 4.4.2 to official samsung 4.2.2 because in odin you will get failure at aboot.bin because you cannot downgrade bootloader.
How ever what would be really good is instead of just trying to say it then jumping out saying what's your point, we'll my friend the point is, it would be advantageous to everyone in the entire samsung galaxy s4 i9505 community if you can tell everyone how you did it.
My perspective is your doing a bit of flaming.
Pictures really won't prove a whole lot as anyone can do some build.prop edits and show different rom name and version.
Sent from my GT-I9505 using Tapatalk
Well, if it sounded like flame to you, it wasnt. I didnt create this thread to flame others. But i wasnt kidding saying that i downgraded to 4.2.2. Here how i did it:
Was running 4.4.2 (I9505XXUFNB9)
Flashed TWRP recovery.
Flashed custom Rom 4.2.2, which FAILED!
Flashed Official 4.2.2 trough odin, which FAILED!
Flashed TWRP recovery again, since it was somehow damaged from the flash before
Flashed Wanamlite 4.4.2
Flashed Custom Rom 4.2.2
Flashed Official 4.2.2 with succes.
Im not sure what part of those flashes were essential, but i have no reason for liying to you. What would be the perks if i did?
But now again BTT, Did anyone else have that problem of slow interenet connection? Or is it just me? Maybe some ideas?
Regarding slow Internet maybe it's your carrier with issues.
Maybe the downgrade back to 4.2.2 has created issues in its self. Have you checked your baseband matches bootloader and build?
A problem we have is we can't see the version of the 4G modem (non-hols) so that might be also an issue.
When you flashed back did you do a factory reset?
In regards to downgrade do you still have the Knox bootloader?
Sent from my GT-I9505 using Tapatalk
Well, i called my operator and the girl on the phone said that some people already called with the same issue, but its not on their side. It's a problem with the update samsung released. After the downgrade i had my Knox Bootloader and everything worked like it always did.
Yesterday Sammobile released a new ''rom'' for my country. Downloaded it, flashed it and it works great now. I have a bit of a fast battery Drain, but the problem with the slow internet seems to be fixed.
Again: 4.2.2 worked perfectly after downgrade. It had no issue, No FC nothing at all. Maybe i was lucky? No idea, but im happy my 4.4.2 works now
Thanks anyway for your help guys
Edit: Yeah, my bootloader matched both baseband and build.
Joku1981 said:
Mod Edit
Click to expand...
Click to collapse
If you had done your homework, you would know that in almost all cases Samsung repairs it even with Knox set to 0x1. They even publicly stated it in the Netherlands that they will repair your phone even with custom roms.
And you don't know the law in Switserland. Nor do I. So you can't say that in Switserland his rights are voided by flashing.
If Samsung doesn't give you the warranty, then you still have your consumer rights in the European Union (not that Switerland is in it). No flashing, modding or other chances decleine you your rights if it's not related to a hardware failure. In the countries that you and I live in, it will never void your rights if the damage is not related to flashing or modding.
So well, i think that in switzerland they actually WONT repair it if you flash it, but i aint sure about that, since i never had to send it to repair. But anyway, it was only a software problem on their side. They released another version for switzerland and it seemed to have fixed the problem. I have a bit more of a battery drain, but i actually think im just too used to some other custom roms. Anyways, thanks for the help guys
Purchased my S4 at launch, only rooted it and never really got around to tweaking it much. It has slowed down a bit so now is the time.
I'm on MDL, stock 4.2.2, and rooted with TWRP 2.5.0.2 On to the questions/clarifications, hopefully these aren't egregious. I know the info is out there but for actually finding specific information, the xda forums are a bit overwhelming and sometimes conflicting...
1) Recovery - Latest/preferred recovery for the s4 (on MDL) with auto-loki baked in? Are any of the latest versions of TWRP/CWM dangerous/incompatible or can I just install the latest/greatest with ROM Installers and go from there?
2) Modem - Flashing an updated modem, regardless of ROM/OS # should not break anything and/or lock down the bootloader any more so than it already is at MDL, correct? Updating the baseband will have no effect on the build # and thus loki is still and option (versus safestrap)? Preferred modem at this time? (ATT, SF Bay Area)
3) ROMS - Any ROM, followed by loki patch or flashed via an auto-loki capable recovery should be fine, correct? Is a ROM specifically built for safestrap applications and thus would not work with MDL, or are ROMs noted as being safestrap ready just able to be used via safestrap, but loki as well?
4) Hard to keep track of all the ROMs and the builds and branches etc - Can anyone point me in the right direction of either a) the latest stock touch-wiz 4.4.4 ROM that can be flashed over MDL without essentially updating past MDL? b) the best/most recent pure google (Play Store S4 Edition) ROM, same story with not breaking MDL?
Again, I apologize I am sure the info is all buried in here somewhere, it just gets to a point where pointed questions rather than multiple 500+ post threads are hopefully less likely to brick my phone. Ideally I just want to get on the latest software (and enable screen casting, for one). Assuming it comes quick enough, once I get this process down I will probably make the jump to 5.0 when it is ready, anticipate a couple months? Who knows.
Thanks, much appreciated.
Norcalz71 said:
Purchased my S4 at launch, only rooted it and never really got around to tweaking it much. It has slowed down a bit so now is the time.
I'm on MDL, stock 4.2.2, and rooted with TWRP 2.5.0.2 On to the questions/clarifications, hopefully these aren't egregious. I know the info is out there but for actually finding specific information, the xda forums are a bit overwhelming and sometimes conflicting...
1) Recovery - Latest/preferred recovery for the s4 (on MDL) with auto-loki baked in? Are any of the latest versions of TWRP/CWM dangerous/incompatible or can I just install the latest/greatest with ROM Installers and go from there?
2) Modem - Flashing an updated modem, regardless of ROM/OS # should not break anything and/or lock down the bootloader any more so than it already is at MDL, correct? Updating the baseband will have no effect on the build # and thus loki is still and option (versus safestrap)? Preferred modem at this time? (ATT, SF Bay Area)
3) ROMS - Any ROM, followed by loki patch or flashed via an auto-loki capable recovery should be fine, correct? Is a ROM specifically built for safestrap applications and thus would not work with MDL, or are ROMs noted as being safestrap ready just able to be used via safestrap, but loki as well?
4) Hard to keep track of all the ROMs and the builds and branches etc - Can anyone point me in the right direction of either a) the latest stock touch-wiz 4.4.4 ROM that can be flashed over MDL without essentially updating past MDL? b) the best/most recent pure google (Play Store S4 Edition) ROM, same story with not breaking MDL?
Again, I apologize I am sure the info is all buried in here somewhere, it just gets to a point where pointed questions rather than multiple 500+ post threads are hopefully less likely to brick my phone. Ideally I just want to get on the latest software (and enable screen casting, for one). Assuming it comes quick enough, once I get this process down I will probably make the jump to 5.0 when it is ready, anticipate a couple months? Who knows.
Thanks, much appreciated.
Click to expand...
Click to collapse
I will try to help with a few of these questions, but others I am not familiar with very much. On that note DO NOT update your bootloader!!! It will be locked down further and Loki will NOT WORK. And you could NOT flash any kernels with safestrap. So with safestrap ONLY the stock kernel can be used. Now on to your questions...
1) I am using TWRP 8.1 if I remember correctly. You can find it in the Original Android Development section. It does NOT Auto Loki, so keep the loki-doki flashable zip on your sdcard OR use Roms that already have/use the boot.Loki kernels like ShoStock-i 8.1
2) Modem flashing will NOT lock anything up further as far as the bootloader. You can flash ANY or ALL of them from my modem thread. See which works BEST FOR YOU in YOUR AREA. I am in So Cal and the best for me has been either MDL. But I have and do test ALL of them. You can always flash back to whichever one works best for you.
3.) Like I said I use ShoStock-i 8.1 because it has and does EVERYTHING I need my phone to do and does it without any issues. I have NOT tried to use a Safestrap modified ROM so I have very little experience with that. Normally most devs will have two separate versions, one for safestrap compatible and one for us without safestrap. ShoStock-i is already built with Loki in the kernel so you do not NEED to flash Loki-Doki patch.
4) there are NO Touchwiz 4.4.4 Stock Roms for ATT yet. But I did try out one of the Touchwiz 4.4.4 T-Mobile based Roms and it worked perfectly. You can either get it from the ATT forums and I believe it is already lokified, or get it from the T-Mobile forum and make sure to flash Loki-Doki patch before booting up phone after flashing the ROM. Again the will NOT update your bootloader past your MDL bootloader, so you are good as you are with no worries. By the way on ShoStock-i 8.1 the screen casting to Chromecast works PERFECTLY without having to flash any other .apk's or mess with ANYTHING
This is the exact same boat I'm in. Trying to track down the answers as well. Will keep an eye here as well to watch for answers.
awesome reply thanks RockRatt, that just about covers it. I will maybe give the ShoStock ROM a go and see how I like it. As long as all the normal features are working fine, I should be good.
One last thing I forgot - Odin. I have the stock odin firmware files from when my phone was new (The MDL package). As long as I dont update the bootloader, I should be able to Odin back to the brand new in box state should something go awry or not dig the other ROMs, correct?
Thanks again,
Norcalz71 said:
awesome reply thanks RockRatt, that just about covers it. I will maybe give the ShoStock ROM a go and see how I like it. As long as all the normal features are working fine, I should be good.
One last thing I forgot - Odin. I have the stock odin firmware files from when my phone was new (The MDL package). As long as I dont update the bootloader, I should be able to Odin back to the brand new in box state should something go awry or not dig the other ROMs, correct?
Thanks again,
Click to expand...
Click to collapse
Yep. Just don't update the bootloader...So no flashing newer firmware that contains the bootloader files. Most if not all custom Roms do not have the bootloader files in them. So no problem flashing back to MDL stock if the need never arises. I still in fact have the original MDB bootloader installed that came with the phone before the MDL firmware update.
Hi guys,
I really hope someone can point me in the right direction here, I'd really appreciate it!
I've never had to ask for help before with flashing one of my devices, and have flashed hundreds of times with my previous phones, S3, S5 and Note3 .. However this one has me a bit stumped. I have the Note4 N910F and I see many awesome LP ROMS seem to require that you flash stock 5.0.1 via Odin before flashing the custom ROM.
I managed to do this successfully with the ROM listed at Sammobile called "Unknown 5.0.1 N910FXXU1BOC3 N910FTPD1BOC1" - Everything is OK, boots perfectly and I have cell signal and LTE. Rooting was also a non-issue. The problem I have though is that no matter which custom recovery I try, and regardless of ROM that I try, all seem to get stuck in a boot loop at the Samsung screen.
Am I doing or have done something horribly wrong?
Please help!
I think I may have answered my own question. The stock ROM I flashed was BOB3, it seems I need to be on BOB4, which is the German based ROM. Busy downloading that now!
korval said:
I think I may have answered my own question. The stock ROM I flashed was BOB3, it seems I need to be on BOB4, which is the German based ROM. Busy downloading that now!
Click to expand...
Click to collapse
Why can't you flash custom rom's with BOB3 installed?
Thanks
New to the I337. AT&T with NC1. Android 4.4.2. Stock ROM with the 3.4.0-1125940 kernel. Rooted, SE Linux permissive, Safestrap installed. Compared to other phones I have owned, rooted and installed custom ROMS for this one is way more complex.
Today I tried to Safestrap flash a couple of different ROM's- the Goole Play edition (jflte GPE) and the Lollipop 5.1 ROM 2015061jflte both times using Safestrap. Neither worked. In the case of the Google Play edition, it wanted to install a new kernel as well, I tried with the recommended kernel on the install GUI (wow an install GUI on Android). Both times stuck in a boot loop. I ended up using for the second time, the excellent information here
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
to get back to stock NC1 (thanks again guut13 for the excellent guide and links to resources) and restored via Safestrap the present stock configuration.
My questions are as follows (I am posting this after a LOT of reading here)
1)Can I use LokiDoki ? I understand it resolves problems with the locked boot loader where one can flash pretty much any S4 ROM on the I337.Is this true?
2) I wanted to give the two ROMS I mentioned today a try. Neither worked although I followed the instructions carefully (wipe, install and reboot). I also would like to try the Phoenix ROM. Is it compatible with Safestrap? Are the two I tried today compatible with Safestrap?
3) I am on 4.4.2. I understand that 4.4.4 is out there as well as 5 but when I check either via Kies or OTA I am told this is the latest firmware for my phone. Any way to update this?
As I said earlier this phone is a lot more complex from a modding standpoint than any other I have experience with. I am unclear on which ROM's will work with the NC1. Before I knew about Safestrap and the boot loader problem I tried installing TWERP and ended up having to rebuild things with guut13's excellent thread.
With NC1 am I stuck on the stock ROM ? Can kernels be updated on NC1 using LokiDoki?
Any light or advice to be shed on my confusion wold be very much appreciated.
Expat
Look at this other excellent thread started I by guut13,î answers all.
http://forum.xda-developers.com/showthread.php?t=2616221
Loki doki is not an option for you, and you can only install tw based roms.
Cats_PJ's
Thanks for the link. Have seen this thread. So I am on 4.4.2. So can I flash a 5.x ROM on the phone provided its TW --or does the phone have to be updated via OTH or another method to 5.x first? Or am I stuck on the ROMS specifically available on 4.4.2?
Thanks again very much for your interest and the link. Wish I had shopped more carefully and bought a non AT&T phone, one of the 5xxx models but I couldn't find anything other than the AT&T ones here in Ecuador.
Expat
http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
That will get you to 5.0.1. You can flash the lollipop roms after that.
I wish I had known more before I bought my phone too. Live and learn, I'm about do for an upgrade though. Good luck.
Cats_PJs said:
http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
That will get you to 5.0.1. You can flash the lollipop roms after that.
I wish I had known more before I bought my phone too. Live and learn, I'm about do for an upgrade though. Good luck.
Click to expand...
Click to collapse
Again many kind thanks for the help. This is the most complicated chain of BS to go through just to update a ROM thanks to the locked boot loader I have ever seen..... however you and others here deserve a lot of credit for finding workarounds...... the phone has been made needlessly complex with the BL and efforts by Google and AT&T to "protect" their turf and monetise the user. I would upgrade today were I not in Ecuador where everything costs double what it does in the US. The phone thief crop here is thick- this is the fourth phone in 2 years although the Galaxy Grand Prime I bought after the last robbery I still have. Broke the screen on that one and it was repaired improperly, I get a blank white screen on startup so can't get into recovery so its worthless to me for what I want it for..... so I have the S4 AT&T. Ah well.
Many thanks and enough of my *****ing.
Expat
I just got the Verizon variant of the Galaxy S5 (SM-G900V). I rooted it very easily using odin without tripping knox; that was easy.
I then began looking for ROMs; which for this phone, isn't easy with the locked bootloaders.
I came across a custom ROM, forgot off the top of my head but may go back to retry loading it.
Because these devices have locked bootloaders, any ROM flashed to it will need to have a separate bootloader flashed as well. The aforementioned ROM had one and I understood why, but after I odin flashed the new bootloader, i kept getting a black screen. OK no biggie, factory flash, re-root look for another ROM, except this time, I'm looking for a pre -rooted factory ROM. I came across a lollipop one, 0A8, was hoping for 0G5, but will deal with that later. Of course the ROM had to have, I guess for lack of a better word, a custom bootloader, or index, to tell the phone it's okay to use this software right? So now have lollipop, but have lost TWRP on boot. I'm not sure as to why this has happened, but it's a real pain I want to install and use ROMs on this phone. If I need to downgrade to have TWRP, that's no big deal. So here I am a lollipop stock ROM, rooted wihout TWRP, ugh.
Is there anyone who can help me find a solution to this, it's driving me mad. I just want to have a recovery installed and the klte version won't install. It must be a lollipop thing, but I would love to have cm12.1 when it comes out. And why does this stupid script keep popping up while I'm trying to type this. Just thought I'd share my frustrations or see if there is a way to get TWRP on lollipop?
Thanks in advance.
Hello,
Welcome to XDA.
To better assist you, your thread will be moved to your device Q&A forum linked below.
http://forum.xda-developers.com/verizon-galaxy-s5/help
The experts there may be able to help. Good luck.
U cannot load into twrp or safestrap above the n12 kernal.
If you want to access your recovery, you could try loading the n12 kernal via odin. Then use your recovery. Then reflash the right kernal for your rom via Odin to return to loading status.
That's what I hear is possible- you sound like you can rebuild if u get in trouble.
As for CM - we don't have an unlocked bootloader so that's unfortunately killing it at this time. We are stuck on stock rooted TW roms, or slight variations of TW roms.
Sent from my SM-G900V using XDA Free mobile app