In the past, I had installed a SGH-T399N rom and later I had to erase that and revert back to stock and I noticed that the logo had the newer Android logo. Then I went to Download Mode and it said it was the SGH-T399 still! I have no idea how to revert the original Download Mode back to how it was before. If anyone has a solution please tell me. Thanks!
It really doesn't make any difference, unless you had to return the phone for warranty issues, which most likely isn't the case. But anyway, just flash the appropriate firmware here http://www.sammobile.com/firmwares/database/SGH-T399/ via Odin and you should be back to normal.
Related
I went in Odin from my stock Vibrant because I had lost my root. I tried to start over and tried to revert it back to stock, which lead to me getting the BSOD. I figured out how to get back into download mode, but I'm stuck in Odin now.
I'm in the stock rom...so I don't want to try and put that back into Odin. I just want to get back to having a stock phone so I can try and upgrade to 2.3.
So, I'm kind of in a situation where I don't know what exactly I need to do to get my phone back to working. I'm sorry if there's another topic like this but I couldn't find one, so I apologize in advanced if I totally missed it.
http://forum.xda-developers.com/showthread.php?t=849028
Read that.
And at first I thought your phone had a BSOD
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
ryanskeltis said:
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
Click to expand...
Click to collapse
In the stock recovery do a full wipe as well. The wipe is more comprehensive than the custom recoveries. Perhaps that will help with the booting.
Which version did you try flashing? Mj9? More recent?
ryanskeltis said:
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
Click to expand...
Click to collapse
I understand you are probably panicking a bit over the trouble you have gotten yourself into with your Note, but I think you've been around long enough to know where to start this sort of topic. If you posted in the correct sub-forum, then you'd get better results. Right? :good:
Anyway, I wish you the best of luck fixing your phone.
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
ryanskeltis said:
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
Click to expand...
Click to collapse
What image did you flash in Odin? Also, when you flashed it did you use the pit file with it?
So the first thing was I rooted a Samsung S4 SGH-M919.
I used Chainfire's files and Odin. it worked just fine.
Gave the phone to my wife but the firmware 4.4.2 was clearly outdated that none of the apps she played worked, everything just froze on her or crashed.
So I decided to install a custom rom, this led me to Imperium Lollipop 5.0.1
Well that in turn made the phone unbootable. It would continuously go into these 4 circular swirling balls and get stuck there. I cant even get into Recovery Mode. Only Download Mode.
So this made me do some searching and I dl'ed SGH-M919 stock firmware 4.2.2
I used Odin to flash that and it failed.
So now the phone boots into a screen that telling me to uses Kies to fix the issue.
I'm at a loss what to do next.
Can someone give me the necessary steps to fix the phone and where I intended to go with this?
Much appreciated. thanks.
catheapp said:
So the first thing was I rooted a Samsung S4 SGH-M919.
I used Chainfire's files and Odin. it worked just fine.
Gave the phone to my wife but the firmware 4.4.2 was clearly outdated that none of the apps she played worked, everything just froze on her or crashed.
So I decided to install a custom rom, this led me to Imperium Lollipop 5.0.1
Well that in turn made the phone unbootable. It would continuously go into these 4 circular swirling balls and get stuck there. I cant even get into Recovery Mode. Only Download Mode.
So this made me do some searching and I dl'ed SGH-M919 stock firmware 4.2.2
I used Odin to flash that and it failed.
So now the phone boots into a screen that telling me to uses Kies to fix the issue.
I'm at a loss what to do next.
Can someone give me the necessary steps to fix the phone and where I intended to go with this?
Much appreciated. thanks.
Click to expand...
Click to collapse
Are you sure that you have the right bootloader installed for the lollipop rom? Did you factory reset before installing custom rom? Try to wipe davlik after installation completes before restarting device. Also follow the instructions given by the rom thread op.