Database Users

[Q] SGH-I337 Download Mode Problem?

Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html . From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight. From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight.

Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help

bryantjb said:
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
Click to expand...
Click to collapse
I don't want to give you useless information, but make sure you're using the right steps to get into download mode.
1) Power off your device
2) Remove battery for 10 seconds
3) Replace battery
4) Hold POWER + HOME + VOLUME DOWN until you see the "Warning" Screen
5) Quickly hit the VOLUME UP button.
Then you can connect to ODIN, and go from there.

[Q] Phone has no recovery and other issues.

First want to say hi and that this site is full of knowledge so any help with my subject will be great.
Got a att s4 sgh-i337 phone. I rooted it before the lollipop ota update was out and everything went fine. Then the lollipop update came out and I followed one of the methods on keeping root and updating to 5.0.1 lollipop on the phone. Everything went fine with that. Still showed root status and never did the phone brick or have any issues in the updating.
At some point though, I did run triangle away because I would have the custom logo and opened padlock when the phone would boot up. I knew it wasn't a huge deal but the counter showed correct and never could just figure out how to get it to go away. Either way, I did run it and I think rebooting twice, the factory loading image came back to it. Now it shows my current status as 0 for the counter and the binary is Official.
I have not tried to load any roms or nothing like this to the phone, just followed the instructions to give it root access so I could run a few different apps and adaway for when I listen to Spotify.
One day, I was trying to install a new version of Words with Friends and it failed because I think wwf was open, but I did go back and install it. For some reason now, my phone never notifies my with a wwf notification when somebody plays me. Every now and then, it might pop up when I restart the phone but that is it. I don't think facebook notifies me everytime also but was more worried about words with friends.
Searching google, it says to go into recovery mode and flash the cache of the phone there. I have done the cache memory in the phone but that has not fixed my problem. When trying to go to recovery, it never works, it would always show, recovery booting and then load the phone up as normal.
I have download quick boot and rom manager since they all have an option to boot into recovery rather than pressing the buttons but it always does the same thing. Reading the web though, it seemed like I needed to install a different recovery than the factory I guess, so using rom manager, I tried twrp and that didn't work so I installed ClockworldMod 6.0.4.7. Rom manager shows that as the current recovery method.
When I try to boot into recovery, it still shows that recovery is booting and then goes straight to loading the phone as it should normally.
Now though, every time I restart my phone, it says recovery is trying to boot but never does.
How do I fix my phone to be able to boot into recovery and it not try to boot every time it powers on. I have tried searching google but I just just can find an answer to my direct problem. I know how to hold the buttons and go to recovery but does not work, and I also know how to get to it from the different app programs(rom manager and quick boot) but they do not work either. It would be nice to get the wwf notifications to work properly again also.
If you need any information from my phone, please ask. Thanks for any help on my matter,
Charlie

Odin stock and start over.

Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.

creepyncrawly said:
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
Click to expand...
Click to collapse
Thanks for the replies guys, I really don't know a whole lot about rooting other than following instructions about it. I was unaware you could not use the twrp or cwr as a recovery. My recovery did not work before so that is why I was trying to install those. I knew you could not install custom roms but I did not know that you could not use rom manager to install custom recoveries.
I appreciate the help so far and I will look into that thread you mentioned. I haven't read it but will this take me back to stock lollipop 5.0.1 and I just reinstall apps or will I have to re-root the phone.
Charlie

please delete, sorry
Charlie

You have to go back to 4.4.4, to the nb1 base, root with towelroot, and then use the keeproot method to get back to 5.0.1 rooted. The instructions are in the guide, and also a link to the keeproot thread is there.
By the way, for future reference, questions, help and troubleshooting issues should go in the Q&A forum, not the general forum.

not having any luck
Ok guys,
I am trying to follow the guide but not having much luck.
I downloaded the I337UCUFNB1_4.4_Stock_Odin_tar and put it in the AP Odin file. I'm not sure if I should be using it or the other file named I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to begin with. The instructions said to use the first one so that is the one I was trying to use.
After putting the first file in the AP slot of Odin and hitting start, it begins to try to do it's thing and then says it fails!
What do I do now? Am I doing something wrong or what because I'm trying to follow instructions but not having much luck.
Please help. Sorry for posting in the wrong area also in the beginning.
Charlie

I'm screwed
Now when I turn my phone on, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?

doing better now
Pretty sure I got it going finally. I changed cords and then changed ports on my computer and it finally did go back to stock without an error. I'm currently back on Lollipop and rooted so now is the fun of reinstalling contact info and anything else. So far I have not rebooted but it was not showing the recovery booting option when it did reboot. Hoping my notifications work properly now also!
Thanks!!!
Charlie

Stuck on Recovery Boot Loop after Rooting

Hello there,
I am having a little bit of an issue with a new Galaxy Note 4 that i got for my wife. We both bought our devices yesterday, mine from Three, and hers from EE (we are in the UK), both SM-N910F, so i proceeded to root my device and it worked all great. So earlier today i started the exact same procedure, unfortunately, my wifes Note 4 got stuck in a Recovery Boot Loop, and i genuinely don't understand what is happening.
As for the rooting method, i went with the [SM-N910*] CF-Auto-Root and choose the right .tar file, or else it wouldn't of had worked on the first device.
I have read quite a few posts, saw a few videos on youtube, but it far beyond me. I have seen a few people mention that i need to download the German (?) version of the Stock firmware, and then flash it. I seem to have found a link for it on SamMobile but it's gonna take 5 hours to finish, and i don't understand why i would download the German Stock firmware, is that the correct one for her device ?
At this point, is there any way around it ? Why did my device which is the same work perfectly, but not hers ?
I would appreciate any and all help, if you could make it quite detailed for me i would appreciate it even more.
Thank you!

Hi @Vaskie!
Can you enter in download mode?

Hello there @_mone, the following has happened since i posted:
Went ahead and flashed the following: N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.tar and it made the device reach the home screen, from there i attempted to root using the same method which worked, but it ended installing a few extra applications, which i don't understand how. I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
On the other hand, most things seem to be working perfect, but i am having some issues with the front camera. I have two Note 4s, both bought yesterday from the same place, but one was flashed with the Stock rom (N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.ta r) due to being stuck in a boot loop. The front camera seems to be massively over exposed compared to the other Note 4, not just a little bit either, making it almost unusable.
Would anyone be able to help ?

Vaskie said:
I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
Click to expand...
Click to collapse
That's because you "dirty" flashed a new ROM on top of the old one.. it was like an "update".
What I suggest you (because you already rooted your phone and your knox is 0x1) is to flash TeamWin Recovery Project from ODIN and then flash a TW ROM from the Galaxy Note 4 Android Development (Snapdragon) page
To do so download "twrp-2.8.7.0-trltexx.img.tar" from here, put your phone in download mode, connect it to the pc via usb, from the pc launch odin, let it recognize your phone, add the downloaded .img.tar file on the pda button, click on the "start" button and let it flash the recovery.
Now download a TW ROM like _alexndr's DevBase from here and this modem and this bootloader.
Then put the downloaded ROM (N910FXXU1POF2_DevBase_alexndr.zip) in your external SDcard. Reboot your phone in recovery mode. From TWRP go Wipe/AdwancedWipe/ and tick DalickCache, System, Data, Internal Storage, Cache and "Swipe to Wipe". After go back to the first page, hit "Install" search "N910FXXU1POF2_DevBase_alexndr.zip" in "/external_sd" and install it. Wipe Dalvick and Cache again and reboot into download mode. Again connect your phone to the PC and launch ODIN now put the downloaded modem "CP_N910FXXU1POF1.tar.md5" in the CP button and the bootloader "BL_N910FXXU1POF2.tar.md5" in the BL button and click on the "start".
Once it is done switch off and on your phone and start again with the latest samsung rom for N910F already with root, busy box and all the fixes by _alexndr
And let us know if you still have problems.

Thank you very, very much for the very well detailed reply @_mone
I will attempt to go ahead with your explanation tomorrow. Would that somehow fix the camera, and i guess the other question is.. is the front camera issue that i explained myself above to do with me "dirty flashing" ?
Is there anything inherently wrong with "dirty flashing" ?
Thank you yet again!

Nothing wrong with dirty flashing.. but sometimes doing so you can create conflicts between old and new rom or leaving "bugs" from the old to the new generating problems in your new os that may wont be there if you performed a clean install. :good:

SM-P613. Error vbmeta image.

Hello!
I was recently gifted a Samsung Galaxy Tab S6 SM-P13. I only use my tablet to watch chess videos on Youtube, so I was happy to get a tablet to mess around a bit with it. I did not know much about rooting, but I thought installing Lineage OS and learning from it would be exciting.
I'm good at following instructions, but with some overenthusiasm, I realized that Lineage OS did not support my model a bit too late. So I reached step 5 of "Installing a custom recovery using heimdall" in the official instructions (https://wiki.lineageos.org/devices/gta4xlwifi/install).
But I could not do step 6 as it could not boot into recovery mode. It will stay in download mode with the following message:
<!>
_partition recovery
Reason recovery: Error verifying vbmeta image: invalid vbmeta header(6)
CUSTOM recovery
VBMETA P613XXU1AVG5, 54410278R
I have looked around to see fixes, but I have felt slightly overwhelmed. So I have installed Odin, and at this moment, as Lineage OS is not an option, I don't care which ROM to install (stock, lite, etc...).
Can someone guide me on what to do now so I won't worsen things?
Thank you for your help in advance!

Hey Pablosky000, have you tried using odin to flash stock firmware to fix it back to how it orignally was?

oFluffy said:
Hey Pablosky000, have you tried using odin to flash stock firmware to fix it back to how it orignally was?
Click to expand...
Click to collapse
Hi. Liked I said, I feel a bit overwhelmed and risk-averse at the moment. I have Odin installed and a the stock lite version downloaded. Was hoping for a "Try Odin with stock first" before making any further mistakes.

Pablosky000 said:
Hi. Liked I said, I feel a bit overwhelmed and risk-averse at the moment. I have Odin installed and a the stock lite version downloaded. Was hoping for a "Try Odin with stock first" before making any further mistakes.
Click to expand...
Click to collapse
I don't fully understand whether or not you are wanting to return it to normal or not here, but I do know about the S6 lite. I have my own S6 lite, and I noticed no one has been updating the patched files for it. A recent update forces it to have the file it was talking about, and unless someone makes a specific twrp for that device specifically, we won't be able to use a custom recovery to flash a rom.
If your issue is getting it into recovery mode however, you aren't alone. The Samsung tablet's usually have the same method for launching, but this one specifically was weird.
You have to:
1.Unplug it
2.Hold power and volume down
3. As soon as it turns off plug it back in and begin holding the recovery key buttons
4.If it isn't in recovery you may have just missed the small window you had to do it, which is fine just start from step one until it works.
If you did flash your own recovery and expected it to show the stock Samsung recovery menu, that won't happen since you overwrote it by flashing a recovery. You should be able to find your device model on https://sfirmware.com/
In odin "AP" is where you flash your recovery files. If the device isn't working you may have to also flash the "BL" or binaries for your device. I usually do anyway just to make sure it is going to work correctly. Make sure you have adb, and any Android drivers needed for it to work. Let me know if you need more help! Thanks.

oFluffy said:
I don't fully understand whether or not you are wanting to return it to normal or not here, but I do know about the S6 lite. I have my own S6 lite, and I noticed no one has been updating the patched files for it. A recent update forces it to have the file it was talking about, and unless someone makes a specific twrp for that device specifically, we won't be able to use a custom recovery to flash a rom.
If your issue is getting it into recovery mode however, you aren't alone. The Samsung tablet's usually have the same method for launching, but this one specifically was weird.
You have to:
1.Unplug it
2.Hold power and volume down
3. As soon as it turns off plug it back in and begin holding the recovery key buttons
4.If it isn't in recovery you may have just missed the small window you had to do it, which is fine just start from step one until it works.
If you did flash your own recovery and expected it to show the stock Samsung recovery menu, that won't happen since you overwrote it by flashing a recovery. You should be able to find your device model on https://sfirmware.com/
In odin "AP" is where you flash your recovery files. If the device isn't working you may have to also flash the "BL" or binaries for your device. I usually do anyway just to make sure it is going to work correctly. Make sure you have adb, and any Android drivers needed for it to work. Let me know if you need more help! Thanks.
Click to expand...
Click to collapse
Perfect!!! Thanks a lot. I didn't have much expectation apart from "not bricking it". I just wanted to make sure I did not do anything stupid. Follow your instructions. And it worked perfectly! Thanks a lot for the help! I truly appreciated. I am usually alright at a lot of these things, but I ended up being a bit lost, and just wanted to make sure I stopped doing stupid stuff!
Million thanks!!!!

I am facing a similar issue, but I can't seem to find a recovery image, so can you please help with that? I went to the sfirmware website, but can't locate the recovery image for sm-p613, though I did find it for other models such as p610. At this point, I'm fine with going stock os if it means I haven't bricked the tablet.

mr_scientific127 said:
I am facing a similar issue, but I can't seem to find a recovery image, so can you please help with that? I went to the sfirmware website, but can't locate the recovery image for sm-p613, though I did find it for other models such as p610. At this point, I'm fine with going stock os if it means I haven't bricked the tablet.
Click to expand...
Click to collapse
I softbricked mine with Snapdragon last night. See the fix and link to a working recovery image here. Developer says there's no hope for Snapdragon support for the S6 Lite Wifi now or in the future. Samsung doesn't even support the firmware reload for this device in their own Smart Switch Windows app.

deckardsdream1988 said:
I softbricked mine with Snapdragon last night. See the fix and link to a working recovery image here. Developer says there's no hope for Snapdragon support for the S6 Lite Wifi now or in the future. Samsung doesn't even support the firmware reload for this device in their own Smart Switch Windows app.
Click to expand...
Click to collapse
Thank you, I managed to get my tablet working. Really wish samsung made the firmware more available.

Bad Day - Kernel Panic trying to update TWRP

I should have left well enough alone.
I was updating things so... I used twrp to install a new rom, magisk etc...
Then just though why not update twrp while I am at it.
I tried installing twrp-3.6.2_9-0-h910.img while inside my old version of twrp (not sure what version...)
Anyway - chose to install the .img file to recovery partition
Went to boot straight away back into my new recovery and got a kernel panic screen.
Booting to recovery gives me kernel panic every time
Regular boot gives me the LG symbol forever - more than 10 minutes
Now seems I am completely ____________'d
Seems I should know what to try next - but it's been a while since I have been doing this...
Thanks in advance.

wantpizza said:
I should have left well enough alone.
I was updating things so... I used twrp to install a new rom, magisk etc...
Then just though why not update twrp while I am at it.
I tried installing twrp-3.6.2_9-0-h910.img while inside my old version of twrp (not sure what version...)
Anyway - chose to install the .img file to recovery partition
Went to boot straight away back into my new recovery and got a kernel panic screen.
Booting to recovery gives me kernel panic every time
Regular boot gives me the LG symbol forever - more than 10 minutes
Now seems I am completely ____________'d
Seems I should know what to try next - but it's been a while since I have been doing this...
Thanks in advance.
Click to expand...
Click to collapse
I think you may need to root your phone again.
h910_root_pkg.zip "DirtySanta root package"
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)

Thanks @Darnrain1 . It's been a while. Thanks for the reminder links.
I changed laptops since I did this... Plus I am 99% Linux now but a struggle I am used to.
I also found my initial LGUP before I rooted last time so the nerves have calmed and the tremors have stopped. HaHa. It was too late last night and I SOOOO should not have been flashing in TWRP.

wantpizza said:
Thanks @Darnrain1 . It's been a while. Thanks for the reminder links.
I changed laptops since I did this... Plus I am 99% Linux now but a struggle I am used to.
I also found my initial LGUP before I rooted last time so the nerves have calmed and the tremors have stopped. HaHa. It was too late last night and I SOOOO should not have been flashing in TWRP.
Click to expand...
Click to collapse
No problem.
Another thing you could try and do is flash twrp via fastboot and see what happens.
Update twrp. twrp-3.6.2_9-0-h910.img
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h910.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset.

Thanks a ton @Darnrain1 !!
Yep - that was all I had to do to get TWRP back was fastboot flash it in and now I restored an old backup and have my phone back.
I appreciate it. Happy New Year and all the best.