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.
Related
Hi! I have encountered a problem, and really hope someone can help me!
Two days ago i flashed Omnirom Nightly on my n7105 to get Android 4.4. I was running cmw recovery but couldnt get the ota updates to work, so i was trying to flash open recovery instead. I used an apk that was supposed to install a script.
When i rebootet my phone, all i could get was the Note 2 boot image. It wont boot into recovery mode, or the rom. I am however able to boot into download mode.
Custom Binary download: Yes (4 counts).
Current binary: Custom
System Status: Custom.
How should i proceed? I've already tried to reflash cwm recovery, which did work, but didnt solve the problem. I am currently downloading stock firmware, but the file is 1.2 GB so it will take i while. Figured i should ask here in the meanwhile.
I'm not an expert at Android at all, im just a guy enjoying having custom roms and playing around a little. I do know that there are a lot of very talented people in this forum, and i really hope someone can help me find a solution. I've been googling for hours, but cant find anything that seems to work for me / or i dont fully understand and wont risk try before someone approves it.
Thank you, Vetle
EDIT: Is it correct that i cant flash any custom rom trough Odin? Or could i just flash omnirom again trough Odin?
If i manage to flash the stock rom and the bootloop goes away, will everything go back to normal, so i can flash cmw again and then a custom rom again?
No custom rom can be flashed through odin, as most of them are zip cwm/twrp base.
When u can only go to download mode, an official firmware only can help u through odin.
Sent from SM-N9005 with xda-app
Thanks for the answer!
Yup, i have flashed a stock rom now and i got the stock recovery. Everything was working fine.
Then i proceeded to do a factory reset in the stock recovery and flashed cwm trough Odin. When it was done, it wouldnt let me into recovery again! I can still boot up the phone tough.
I've also tried Open recovery. CWM via Rom manager. Open Recovery trough Goo Manager... Still cant get recovery to work, the stock rom works tough.
Any ideas?
Okay, i tried to flash the stock rom again and installed Rom Manger.
It still showes TWRP and CWM under installed recovery and i guess these its these two who makes the problem.
My plan now is to figure out how to completely remove them. I've never done anything related to adb before, so i hope it possible to remove them in another way?
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
vetle666 said:
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
Click to expand...
Click to collapse
I had recovery problems in the last few days also.
Installed DN3 rom using philz recovery, because its capable of prepare the phone to a new rom in a easy way.
It all went fine until first reboot.
I had a recovery boot loop. All I could see were some buttons and then reboot again.
Like you I had download access and flashed philz with Odin, but no luck.
Installed twrp via Odin and all was fine, and flashed philz new version.
Then I had to flash a new kernel (to be able to access wifi) and it all started again. Now I'm back on twrp.
Let's see what happens on my next flash.
My suggestion is to flash the recovery, and if that's OK flash the rom and use it
Next time you need recovery get Odin to help, but not all the way from an original rom. Just the custom recovery.
But if you want to get rid of your strange recovery configuration, and you are not already on new 4.3 recovery(which in your case could explain some of the problems you had) , with knox, install an older original rom, 4.1, and make all the steps, root it, install a custom recovery, and from there the room you want.
Reading your path sorting this problem, that was what would do next
Best regards
I've flashed plenty of custom ROMs on this phone and my old Captivate so I'm not new to the process, but I have come across an interesting issue. At first, I had a version of RootBox (4.2.2) on my phone. I don't remember exactly what it was and I can't go check anymore. When I tried to install a new custom ROM, any, it said that my phone was d2spr even though it should be d2att and promptly failed. Never had the happen before so I thought I might need to go back to a stock ROM. Used Odin to flash a stock ROM, tried I747UCDLK3 first. Flashed successfully, but now it won't boot. So I'm stuck with a non-booting ROM and stock recovery. I tried flashing CWM using Odin. Flashed successful. When I try to boot into CWM it just shows a blank screen. Phone is still on since holding the power button doesn't attempt to start it. And that's where I'm now stuck. I'm attempting to get a Sprint ROM for this phone, figured it couldn't hurt at this point. I've tried TWRP and some other stock AT&T ROMs, but same things happens. I'm not really sure where to go from here since it seems to be unusual circumstances.
Does anyone know what's going on or what I should try?
Did you run an OTA update to take your d2att to 4.3? If you did, you cannot flash anything that is lower than 4.3 because the 4.3 update upgrades the bootloader.
I am assuming from your post you are not on the 4.3 mjb boot loaders.
Can you get into download mode. If so you could try the Odin back to stock again. Once complete you may need to boot into factory recovery and perform a full reset to clear the boot loop.
Did you root before flashing CWM?
Sent from my I-747 using xda app-developers app
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
My phone was rooted using Kingo Root, I flashed SlimKat rom, when I tried using Odin to flash back to stock, it bricked, it doesn't boot, it goes directly to "Firmware Upgrade Encountered an issue. Please Select recovery mode in Kies & try again"
I tried using Kies, it won't detect it, I had two techns who tried legally they can't do anything obviously, it won't even boot into recovery bootloader.
Is my phone really dead?
WOOO. Thank you XDA, all I had to do was flash a custom recovery again, and it booted no issues,
Odin probably tried to downgrade your bootloader. If you were on a bootloader at or beyond MJB that is probably what bricked your phone.
You might be able to bring it back with a debrick image. Debrick images are usually specific to your bootloader, so if you know what firmware you were running prior to this it would be helpful.
You'll need an external SD card to stand in for your internal storage until you get things synced back up, and you'll have to do some very specific formatting and image writing to that external SD.
Search the forums for debrick image and you should find some helpful threads. I've never had to do this myself, but I have heard some success stories. Good luck.
If you see the upgrade firmware screen, your phone is not totally bricked.
Can you get into download mode? If you can, just flash a custom recovery, flash the latest cm10.2, verify your boot loader, and post back here.
audit13 said:
If you see the upgrade firmware screen, your phone is not totally bricked.
Can you get into download mode? If you can, just flash a custom recovery, flash the latest cm10.2, verify your boot loader, and post back here.
Click to expand...
Click to collapse
I can go into downloading mode, I flashed CWMS3ATTrecovery before thats what was on it.
Copy the most recent cm10.2 to an external SD card.
Use Odin to flash the most recent tar.md5 from Philz for the d2lte from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
After flashing Odin, boot to recovery and flash cm10.2 so you can get your phone running and determine the bootloader on your phone.
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.