Tmobile Galaxy S4 (SGH-M919) Non-rooted
Problem:
The phone was working and then suddenly went into boot loop. The Samsung screen displays and right before it would goto the animation screen, it loops. I can get to download mode and the recovery OS.
What I've tried:
- First thought it was power button, sent it away to replace button but tech says it's not power button. The phone doesn't turn itself on when the battery is inserted. I can use the power button to turn on/off the phone fine.
- Cache wipe
- Factory reset
- Kies update/recovery
- Burn different firmware version (NB4, NH7, NK2, OH3)
- Tried just to burn NB4 twice consecutively without reboot (first time OK. when burn second time w/o reboot, the phone would display error saying the percentage completed is incorrect since it just finished 100%. Odin continues to burn to finish fine.)
Nothing seems to work. It still loops.
I am desperate. Please help! Thanks in advance.
Beocop
An update:
I tried CF Root and was able to get past he first Samsung screen, past the white TMobile screen, but it went back to boot loop again. Don't know what else to do. Any suggestions?
By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
lordodin912 said:
By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
I've tried flashing OH3 (twice) also. It still boot loops. Then I tried CF Root to see if it does anything. It flashes fine with no problem. It still boot loops.
I can get into download mode and recovery without problem. It just won't let me past the boot loop.
Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.
lordodin912 said:
Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.
Click to expand...
Click to collapse
update:
- I've tried different odin versions (3.07,3.09,3.10). I've tried different USB cables. There was no indication on any error during the flashing process.
- I can flash any stock ROM after NB4 (anything before NB4 => Odin fail). After flashing stock ROMS, it can never get past the Galaxy S4 screen. It just boot loop.
**** I tried to download the OH3 stock rom from Sammobile but I always get a corrupt file error in Winrar. Can someone verify if the OH3 ROM on Sammobile is error free?
- I've tried TWRP (2.6.0.0, 2.6.3.1, 2.8.4.0). I've used it to flash CM-12.1 and Darthstalker_S4_V3 ROMs.
- After flashing all the custom CM ROM, it got stuck with the pink screen.
- I get nothing from Darthstalker ROM, just blank.
I am so frustrated with this process. It seems that I am doing something wrong in my process to flash the ROMs. I am missing something.
Can you please list ALL the steps necessary to properly flash a ROM? Please list every single step that you would personally take, no matter how insignificant (remove battery, clear cache, settings, etc.). Just treat me like a 1st grader.
Thanks so much.
Another update...
- So far, I've tried to flash stock ROMS (NB4-OH3) with odin. None of the stock ROMs will boot fully. All stuck at Samsung logo and bootloops from there.
- The best, but not fully functional, solution I've found so far is from:
1- Flash stock rom NH7 (tried NB4,NH7 so far) with odin
2- Flash CF auto root (CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5) with odin
3- Flash CWM for recovery
4- boot into recovery, from CWM, install cm-11-20140110-SNAPSHOT-InstallerXNPQ02R-jfltetmo-signed.zip from sdcard1
5- From CWM, install gapps kk for 4.4.3 from sdcard1
6- Clear dalvik, format data + cache
It'll boot up fine. However, I get no sound (not from speaker or headphone). Google keyboard keeping turn on and off. The camera doesn't work. Video's cannot be played.
info "about phone":
Model: SGH-M919
Android version: 4.4.2
Baseband version: M9191UVUFNH7 (prob from CF auto root ?)
Kernel version: 3.4.0 cyanogenmod
Cyanogenmod version: 11.0-installer-XNPQ02R
Build date: 1/9/14
Build number: cm_jftetmo-userdebug4.4.2 KOT49H-installerXNPQ02R release-keys
Don't know what to do now. I've no idea why it won't take stock ROMs. I don't know why I am having problems in cyanogenmod. I freakin hate working on these phones.
Any ideas? suggestions? PLEASE!
Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.
Vicious89 said:
Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.
Click to expand...
Click to collapse
Update:
-OK. I tried using philz cwm and burned this ROM but went through the installation process and picking choices. However, it wouldn't even boot.
-I decided to open up the phone to verify I had a SGH-M919. The sticker underneath the battery indicated SGH-M919. The phone has been using and updating OTA with T-Mobile firmware, the latest being OH3 with stagefright fix.
-After I removed the motherboard, what I saw underneath was disturbing. There was one big stamping showing "I337", which is AT&T. Many other stampings on the chips also show I337.
-In download mode, the product name indicated "SGH-M919".
So the question is, do I have a I337 or M919 phone? Currently, I cannot flash or install any firmware that is not for M919. I tried flashing ATT stock rom (I337ATTFNB1) with odin but it failed, indicating many errors such as PIT. I tried installing CM 11 for ATT but it also failed indicating that I need jfltetmo (M919) version. Ever since the bootloop problem, I cannot get the phone to boot with stock M919 roms.
Related
So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?
kaif15 said:
So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?
Click to expand...
Click to collapse
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!
Misterjunky said:
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!
Click to expand...
Click to collapse
The app is constantly crashing!
It would start for a second then close. I tried the TWRP manager as well with the same result.
I've lost root access when I Odined back to stock, won't I need root access to install new recoveries?
Sounds like you flashed the stock 4.4 firmware and now need recovery to root. Flash this TWRP file using Odin http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.1-hltetmo-4.4.img.tar
Once you flash it, you need to boot into recovery to install supersu to root.
Switch off the Galaxy Note 3 (remove the battery and reinsert if needed)
Next, press and hold simultaneously Volume Up, Home and Power.Release the buttons when the screen flickers and wait for the TWRP menu.
Select Reboot, then System and install Supersu for root.
Once booted, open Supersu to update it and grant permission.
Hope this helps. Good luck.
Hello XDA,
it appears as though I have somehow managed to brick my S4 when using odin to return the phone to stock (MDL the device was never updated to 4.3 or 4.4.2)
Here is what I tried;
1. put the phone into download mode an flashed firmware (UVUAMDL, as mentioned above, I never updated)
2. put the phone into stock recovery to perform a data wipe
3. rebooted and the phone; once the t-mobile screen appeared, the phone went black.
Whenever I attempt to boot the device, I am presented with the main S4 splash screen for about 2 seconds, and then the phone turns itself off.
I can only enter download mode
I also cannot enter recovery mode
please help, thanks
Nightfrost95 said:
Hello XDA,
it appears as though I have somehow managed to brick my S4 when using odin to return the phone to stock (MDL the device was never updated to 4.3 or 4.4.2)
Here is what I tried;
1. put the phone into download mode an flashed firmware (UVUAMDL, as mentioned above, I never updated)
2. put the phone into stock recovery to perform a data wipe
3. rebooted and the phone; once the t-mobile screen appeared, the phone went black.
Whenever I attempt to boot the device, I am presented with the main S4 splash screen for about 2 seconds, and then the phone turns itself off.
I can only enter download mode
I also cannot enter recovery mode
please help, thanks
Click to expand...
Click to collapse
First, if you have updated your baseband/modem to MK2, NB4, or NH7, you need to find the MDL baseband/modem files and manually revert your modem. Once you've done that, you can then attempt to revert by simply flashing the MDL firmware in Odin again. If that still doesn't allow you to do anything but get into download mode, try the next suggestion.
Download an Odin-flashable custom recovery and a non-TouchWiz ROM... Cyanogenmod 11, SlimKat/Bean, etc... any Odin-flashable custom recovery will work for this purpose as well as any CM/AOSP-based ROM. No need to download GApps unless you plan to use whatever ROM you download some point in the future.
Using Odin, flash the recovery you picked.
Using the recovery you just flashed, flash the ROM you downloaded.
Boot into the ROM <Optional>
(Re)Boot into download mode
Use Odin to flash UVUAMDL.
At that point, since you're still on the MDL bootloader, you can then use TriangleAway to reset your flash counter or whatever else you want to do.
I've found that when using Odin to revert to stock while already running a TouchWiz ROM (custom or stock, doesn't matter) data and settings will, for some reason, survive the flash and cause problems. If you begin the process while already on a CM/AOSP ROM, going back to stock tends to go much smoother and there's no need for a factory reset after that.
Got it! Thank you
+Thanks button
No O/S - can only boot into download mode
I've got an interesting one. I was prepping my phone for selling, decided to clear out all the memory. Somehow I must have deleted more than I meant to b/c when I restarted the phone, it just hangs on the Samsung screen. I can get into download mode, but not into recovery and nothing ever loads. I tried at least one version of installing CWM but it doesnt look like I can boot into recovery even after the Odin install appears ok. Before the crash, I was running a modded 4.4.2 rom with the bootloader and other things that come with it. Is there anything I can do to get this thing up and running again?
Thanks!
I suggest you flash a custom recovery and CM10.2 to at least get the phone up and running so you can confirm the bootloader and modem on the phone before flashing anything. Flashing the wrong bootloader, modem, or bootloader/modem combintaion could hard brick the phone.
audit13 said:
I suggest you flash a custom recovery and CM10.2 to at least get the phone up and running so you can confirm the bootloader and modem on the phone before flashing anything. Flashing the wrong bootloader, modem, or bootloader/modem combintaion could hard brick the phone.
Click to expand...
Click to collapse
Thanks. I'm positive I was running 4.4.2 on the phone before I decided to turn it into a paperweight
Flashing a custom recovery would be the goal, problem is that I can't find a recovery that I can flash. I've tried the latest version of PhilZ Touch recovery and that doesnt seem to work. ODIN shows it as a good install but when I restart the phone, I can't get into recovery. So was hoping for some direction on a different way of going about it. Basically, had 4.4.2, now I can only get into Download mode...
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Open Odin, connect phone, uncheck everything except f.reset time. Flash Philz. When you see reset in the status windows, remove USB cable, pull battery, replace battery, boot into recovery, flash ROM.
There are different versions of the 4..4.2 so it is best to determine the exact bootloader.
Hey guys.
Little review of what happen:
Woke up today and my phone wasn't able to use any of my apps. So, I though no problem let me flash my rom. ( I use SlimKAT)
When I downloaded latest stable ROM I was ready to flash. I come across error while flashing "Executing update binary in <zip name>".
Things I tried:
Wiping:
davlik cache
cahe
system
Rebooting and flashing again. gave me same error.
Any suggestions?
UPDATE:
Now I cant even enter TWRP.
I don't know what went wrong, but at this point there is really no downside to just starting over. You could use odin to return your phone to stock then install TWRP or CWM then flash supersu then flash your rom again.
qwerty3656 said:
I don't know what went wrong, but at this point there is really no downside to just starting over. You could use odin to return your phone to stock then install TWRP or CWM then flash supersu then flash your rom again.
Click to expand...
Click to collapse
Honestly im not sure what I am doing at this point.
My ODIN MODE setting are followed:
Product Name: SGH T999
Custom Binary Download: Yes(4 count)
Current Binary : Custom
System Status: Custom
Qualcol Secure boot: Enabled
Warranty Bit: 1
Boot-loader RP SWREV:1
Im not sure how can i flash my stock rom.
Can you suggest where to start.
Thank you.
I'm no expert so do your own research - I think you can skip a step and get the route 66 version of your ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
IT should be the NC2 rom. follow the instructions there to use odin and install the route 66 rom onto your phone - you should then have a rooted stock phone. Then you can install cwm or twrp and flash your rom
qwerty3656 said:
I'm no expert so do your own research - I think you can skip a step and get the route 66 version of your ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
IT should be the NC2 rom. follow the instructions there to use odin and install the route 66 rom onto your phone - you should then have a rooted stock phone. Then you can install cwm or twrp and flash your rom
Click to expand...
Click to collapse
My problem is that i cant boot in TWRP mode at all. It wont let me enter there.
When i try to flash via ODIN it wont pass.
Any other suggestions?
I got a feeling it have something to do with Custom Binary.
UPDATE:
I was able to get TWRP to boot from ODIN and it passes.
When I try to enter my TWRP it wont let me enter it will skip and go to loading screen of my rom and that's when it get stuck.
To use ODIN, you don't boot into TWRP. You put your phone into Download mode (hold the DOWN volume along with home and hit the power button - when the screen comes up hit the UP volume). You need to be running odin on your PC.
Hi, i've been searching and searching but can't find an answer.
Device: Note 2 i317m
Bootloader: i317mvlalj2
Android: 4.1.1 JB
My Note 2 was running good with custom recovery (TWRP 2.8.0.0, i believe) and custom rom (Resurrection Remix 6.0) for a yr or so. I do get random reboots here and there but not that often.
Suddenly on April 1, the phone just reboot and was stuck in a bootloop. I figure i'll boot into recovery and wipe/cache/dalvic. Guess what, I can't even get into recovery. It got to the TWRP screen and it just rebooted.
I then decided I will re-flash TWRP, everything pass in ODIN 3.09. It still rebooted after the TWRP screen.
Ok, fine. i'll take the risk and wipe my entire phone by flashing Stock Rom. Flashed it with ODIN 3.09. Everything went well, ODIN PASS. Phone rebooted and guess what, its stuck in bootloop with RR logo.
I flashed my phone with many files, different version twrp, 4.1.1 and 4.1.2 then finally 4.4.2 stock rom, different version of ODIN and also CF auto root.
Also the weird thing, my counter is stuck at 3.
I read a lot of forums stating it could be eMMC or partition corruption. But I didn't encounter any of the symptoms mentioned.
Any ideas or suggestions?
Thanks in advance
lilblueboy said:
Hi, i've been searching and searching but can't find an answer.
Device: Note 2 i317m
Bootloader: i317mvlalj2
Android: 4.1.1 JB
My Note 2 was running good with custom recovery (TWRP 2.8.0.0, i believe) and custom rom (Resurrection Remix 6.0) for a yr or so. I do get random reboots here and there but not that often.
Suddenly on April 1, the phone just reboot and was stuck in a bootloop. I figure i'll boot into recovery and wipe/cache/dalvic. Guess what, I can't even get into recovery. It got to the TWRP screen and it just rebooted.
I then decided I will re-flash TWRP, everything pass in ODIN 3.09. It still rebooted after the TWRP screen.
Ok, fine. i'll take the risk and wipe my entire phone by flashing Stock Rom. Flashed it with ODIN 3.09. Everything went well, ODIN PASS. Phone rebooted and guess what, its stuck in bootloop with RR logo.
I flashed my phone with many files, different version twrp, 4.1.1 and 4.1.2 then finally 4.4.2 stock rom, different version of ODIN and also CF auto root.
Also the weird thing, my counter is stuck at 3.
I read a lot of forums stating it could be eMMC or partition corruption. But I didn't encounter any of the symptoms mentioned.
Any ideas or suggestions?
Thanks in advance
Click to expand...
Click to collapse
First. Update TWRP to the latest. Then try it again. You need to flash from 4.1 to 4.3 then update to a newer rom. SD card reading changes thru these roms do it in steps
Sent from my iPhone using Tapatalk