Database Users

[Q] Stuck in boot loop with no recovery Please Help

Hi guys long time lurker, first time poster.
Here's the story:
Was running CM 10.2 on my Galaxy S4 AT&T. Everything ran great etc. I decided to flash a new kernel. Upon flashing the kernel I received an error (I must have not done such great research before I did this) but figured nothing had changed since the flash did not go successfully. I proceeded to reboot my phone and lo and behold I'm stuck with a black screen and a constant vibration as if the phone is going to boot up but it doesn't. I immediately went to Odin as I have done when things go awry. After flashing stock firmware Odin says that everything went successful and my phone reboots. However it does not reboot to any screen (no splash screen, no Samsung logo absolutely nothing) just constant vibration and I'm back to square one I cannot boot into recovery I have tried the button combo many, many times but the phone just keeps on fake vibrate booting. The only screen I can get to is the download menu. The things I have tried so far:
1. Flashing back to stock firmware with Odin.
2. Flashing stock kernel by itself with Odin.
3. Tried to flash a custom recovery but since my phone is no longer rooted Odin was giving me a failed message.
4. Tried flashing stock recovery by itself with Odin.
5. Tried Kies but no success either.
I assume no files from a custom ROM will flash successfully as my phone is not rooted. So I guess my question here is am I bricked forever? Odin recognizes my phone and I have read that there is some hope if this happens but I have come to many dead ends searching for a solution to this problem. Have I exhausted my resources on this one or are there a few more things to try? If I left out any information I'll be more than happy to provide what I missed. Thank you in advance.

You flashed a kernel not for your device and have hard bricked your phone. Look up jtag and mobiletechvideos.com

jd1639 said:
You flashed a kernel not for your device and have hard bricked your phone. Look up jtag and mobiletechvideos.com
Click to expand...
Click to collapse
Yep. That is exactly correct.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Thanks guys. I actually went to AT&T and played dumb. Since the phone was still under warranty they just replaced it on site.

dmesserr said:
Thanks guys. I actually went to AT&T and played dumb. Since the phone was still under warranty they just replaced it on site.
Click to expand...
Click to collapse
Replaced it with MDL or MF3? If MDL, you better block the OTA quickly, If MF3, you better do some reading.

[Q] Rewarded for my stupidity

Greetings, I'm having a cascade failure and I'm not sure what to do next.
I signed with AT&T on Saturday, and took home a new S4 for free. About 30 minutes later it was rooted, and the upgrade from MF3 to MK2 was installing I removed some obvious bloatware, patched the mail client to bypass an Exchange server's mobile device management, and began to use TB to restore my apps.
I encountered some odd behavior with a couple of restored apps, and did a factory reset. Then, I decided that I wanted to get the patched mail client off the system, so I reflashed the MK2 update through ADB.
The reflash of MK2 failed because I'd removed chrome.apk . D'oh.
Then I thought I'd flash a stock firmware. I quickly found the MF3 tars in another topic. And because I'm stupid and didn't read the whole topic, my nice new phone is showing an ugly yellow triangle and says, "Firmware upgrade encountered an issue." D'oh, d'oh, d'oh.
I'm stopping before I waste any more time or do any more damage (not that I think I can eff things up any more).
Can I fix this at home?
Or should I just take it to the Samsung Experience Shop at the nearby Best Buy store? Will they believe me if I tell them that the MK2 upgrade trashed my phone? The loader says, "Samsung Official," but, also, "custom." Both Knox lines read 0x0. Does any of that matter if they're reflashing as a courtesy?
If they flash MK2, can I get root ..... I'm guessing, no, but probably someone else knows for sure.
THANKS
.

Deleted

xpanmanx said:
Greetings, I'm having a cascade failure and I'm not sure what to do next.
I signed with AT&T on Saturday, and took home a new S4 for free. About 30 minutes later it was rooted, and the upgrade from MF3 to MK2 was installing I removed some obvious bloatware, patched the mail client to bypass an Exchange server's mobile device management, and began to use TB to restore my apps.
I encountered some odd behavior with a couple of restored apps, and did a factory reset. Then, I decided that I wanted to get the patched mail client off the system, so I reflashed the MK2 update through ADB.
The reflash of MK2 failed because I'd removed chrome.apk . D'oh.
Then I thought I'd flash a stock firmware. I quickly found the MF3 tars in another topic. And because I'm stupid and didn't read the whole topic, my nice new phone is showing an ugly yellow triangle and says, "Firmware upgrade encountered an issue." D'oh, d'oh, d'oh.
I'm stopping before I waste any more time or do any more damage (not that I think I can eff things up any more).
Can I fix this at home?
Or should I just take it to the Samsung Experience Shop at the nearby Best Buy store? Will they believe me if I tell them that the MK2 upgrade trashed my phone? The loader says, "Samsung Official," but, also, "custom." Both Knox lines read 0x0. Does any of that matter if they're reflashing as a courtesy?
If they flash MK2, can I get root ..... I'm guessing, no, but probably someone else knows for sure.
THANKS
.
Click to expand...
Click to collapse
I think Best Buy has the update now, but I'm not sure. If you have the unlocked padlock boot screen, they won't take it probably and not if system status is custom in download mode either. There is a chance they'll glance over it, but otherwise you have to follow these instructions: http://forum.xda-developers.com/showpost.php?p=47586777&postcount=135
You can get root, look in the general section for the safe root thread.

joshzdad2013 said:
Deleted
Click to expand...
Click to collapse
Deleted, why?
This post in your quoted topic makes it look like a viable option....
ETA: Ok, I get it. DeadlySin9 post has a link that drops you right onto the procedure.

Nutty. Following DeadlySin9's advice, I used Odin to flash recovery-mj6.tar.md5 into the bootloader slot, it was successful, the phone rebooted through the Samsung / open padlock screen and came right up into my old MK2 load. I immediately used TA to remove the open padlock and it now shows official/official. In the end I guess I didn't eff things up as badly as I'd thought.
How may I reflash MK2 from here? Being as there's only have an upgrade ROM out there, and we're waiting patiently for the whole ROM, I bet it will choke on the missing chrome.apk and other victims of my bloatware-removal party.

xpanmanx said:
Nutty. Following DeadlySin9's advice, I used Odin to flash recovery-mj6.tar.md5 into the bootloader slot, it was successful, the phone rebooted through the Samsung / open padlock screen and came right up into my old MK2 load. I immediately used TA to remove the open padlock and it now shows official/official. In the end I guess I didn't eff things up as badly as I'd thought.
How may I reflash MK2 from here? Being as there's only have an upgrade ROM out there, and we're waiting patiently for the whole ROM, I bet it will choke on the missing chrome.apk and other victims of my bloatware-removal party.
Click to expand...
Click to collapse
Follow deadly sins guide exactly...except replace the mj9 side load zip with the mk2...
The two emergency files will get everything you need for the phone to pass security checks (adds in missing files and apps) after you Odin the two emergency files Odin the recovery again. Reboot to recovery and it will perform a mini update. When the mini update completes reboot to recovery once more and side load mk2...so:
-Boot to download mode
-Odin emergency tar1 (it will fail that's ok)
-Reboot to download mode
-Odin emergency tar2 (it will fail that's ok)
-Reboot to download mode
-Odin recovery
-Reboot to recovery
-Let it auto update
-Reboot to recovery
-Sideload mk2
After I rooted mk2 I messed up with a mod and was left with a phone missing a system file which resulted in it not booting, I did the above and was able to successfully side load mk2 and was back to stock... :
All credit goes do Deadlysin9
Edit here is the link for the mk2 side load: http://www.mediafire.com/?ktkoogwz562p64k
Found like from this post: http://forum.xda-developers.com/showthread.php?p=48363444
Sent from my SAMSUNG-SGH-I337 using Tapatalk

mg2195 said:
Follow deadly sins guide exactly
Click to expand...
Click to collapse
Thanks so much, man.
Things went a little differently, but I let the phone walk me through it. All's well.
For me it went like this ....
-Odin recovery, reboot
-Odin emergency tar1, failed as expected, had to manually reboot
-Odin emergency tar2, failed as expected, had to manually reboot
-Let it boot to the pulsating blue LED, manually reboot
-Odin recovery, it automatically rebooted and applied updates and rebooted to pulsating blue LED
-Manual reboot to recovery, sideload mk2, reboot
-Blow through the initial setup
-Regain root with this procedure
-Drink beer
.

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-900V Need Help to Go Back to Stock from NC2!

So, what happened is I let a friend borrow my Note 3 running on NC2 with Safestrap and Hyperdrive rom. This guy decided to do a factory reset in Hyperdrive instead of wiping the data from safestrap recovery. Now the phone is stuck in a bootloop with the first splashscreen and the blue "recovery booting" message at the top left corner. Then it re-boots and on and on.
Looks like Safestrap was wiped, unless there's another way to get in I can't think of?
I assume that what I need to do is revert back to the stock image with Odin. The problem I have now is that I no longer have access to the stock NC2 rom images/firmware and everywhere I have looked has taken the files down. If anyone has those files and could either send them to me or point me in the right direction I would be eternally grateful! Without them I'm screwed other than installing the OEM rom and I'll lose my precious root forever I fear, if I've been reading the forums correctly.
Thank you for any help you could provide!

dustoleum said:
So, what happened is I let a friend borrow my Note 3 running on NC2 with Safestrap and Hyperdrive rom. This guy decided to do a factory reset in Hyperdrive instead of wiping the data from safestrap recovery. Now the phone is stuck in a bootloop with the first splashscreen and the blue "recovery booting" message at the top left corner. Then it re-boots and on and on.
Looks like Safestrap was wiped, unless there's another way to get in I can't think of?
I assume that what I need to do is revert back to the stock image with Odin. The problem I have now is that I no longer have access to the stock NC2 rom images/firmware and everywhere I have looked has taken the files down. If anyone has those files and could either send them to me or point me in the right direction I would be eternally grateful! Without them I'm screwed other than installing the OEM rom and I'll lose my precious root forever I fear, if I've been reading the forums correctly.
Thank you for any help you could provide!
Click to expand...
Click to collapse
Alright, so I booted into Download Mode and then pressed down to restart, and that took me back to Safestrap and into the rom again. So, if anyone else has this problem, I hope this helps!
Something to be aware of though is that pretty much all the links to the stock rom files for the Verizon Note 3 are dead for anything older than Lollipop. If you still have the files lurking around on your phone or PC you may want to hold on to them for dear life.

SOS - OneClick Brick

Greetings,
I need some help. I purchased OneClickRoot for my Verizon S5. Everything went swimmingly right up until it didn't. I got root after several hours with the oneclick tech team. he gave me instructions on how to flash a ROM, but left out the apparently important step where I should have skipped the signature verification. So I had SafeStrap, wiped everything and tried to flash an unsigned ROM. now the phone is dead wit no OS and seemingly no ability to get back to safestrap. Should I just toss this phone in the rubbish and buy a new one or can it be saved? When I boot to recovery, it is Android recovery and it keeps failing on the verification.
All advice is welcome.
Doug M.

dwmackay said:
Greetings,
I need some help. I purchased OneClickRoot for my Verizon S5. Everything went swimmingly right up until it didn't. I got root after several hours with the oneclick tech team. he gave me instructions on how to flash a ROM, but left out the apparently important step where I should have skipped the signature verification. So I had SafeStrap, wiped everything and tried to flash an unsigned ROM. now the phone is dead wit no OS and seemingly no ability to get back to safestrap. Should I just toss this phone in the rubbish and buy a new one or can it be saved? When I boot to recovery, it is Android recovery and it keeps failing on the verification.
All advice is welcome.
Doug M.
Click to expand...
Click to collapse
I'm unfamiliar with Verizon variants, but have you tried using Odin to flash the original stock?
https://forum.xda-developers.com/showthread.php?t=2784880
Sent from my Samsung SM-G900I using XDA Labs

Yea dude as long as you can get into download mode (or Odin mode whatever you feel like calling it) you're fine just flash whatever version you feel like being on and I would follow these instructions for root and ROMs and possible bootloader unlock since it's Verizon https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529

So Close!!
Thanks for the help. I followed this guide ( https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529) and got it back; ...sort-of.
In Step 13, I used the 6.0 firmware.
In Step 14 I used the "latest stock rooted Lollipop Rom" that was recommended.
I have what appears to be a rooted 5.0 factory rom installed. However, when booting, I get process stopped errors for the first 2 minutes. Maybe 15 or 20 of them. After that, they stop.
Current Problems:
1) the radios are dead. Wi-Fi will not turn on and it does not know that my SIM card is installed
2) when the screen times-out I have to pull the battery to get it back.
3) All the error messages (android.process.media)
4) It does not see the SD card
Questions:
A) Can you help me fix the radio problems?
B) Once I get the radios working again, can I flash any G900V ROM with safestrap and it will likely solve 2, 3 &4?
C) Are the custom roms on 6.0 and higher rooted? I was looking at this one (https://forum.xda-developers.com/galaxy-s5/unified-development/rom-cosmic-os-3-1-t3553838)
Thanks for any assistance you can provide.

Idk if i can help bt i can try haha Well first thing first it sounds like you used marshmallow firmware but then flashed a lollipop ROM which yes it will boot up bt stuff like your radio and GPS, etc won't work so first thing is first i would say is do a complete wipe and get your self back to stock through Odin and get everything working first before worrying about ROMs then I have to ask is what is what is your emmc are you 15 (bootloader unlock and can easily root 6.0.1 or higher) or emmc 11 (can only root 5.0)