Develop Bugs

Stuck in bootloop. Cant boot into recovery. CAN boot into download.

What do I do? Sorry for noob question... Also do i just odin back to stock? if so how?

Just boot into recovery, plug in your usb cable to your phone and computer, and flash a stock image using Odin. I would suggest you go ahead and flash a rooted stock image using these instructions.
http://forum.xda-developers.com/showthread.php?t=1739426
If you want straight stock:
http://forum.xda-developers.com/showthread.php?t=1737848
Odin can be found here:
http://forum.xda-developers.com/showthread.php?t=1722686
These are all stickied at the top of Android Development Thread. In the future, please search first.

tocirahl said:
Just boot into recovery, plug in your usb cable to your phone and computer, and flash a stock image using Odin. I would suggest you go ahead and flash a rooted stock image using these instructions.
http://forum.xda-developers.com/showthread.php?t=1739426
If you want straight stock:
http://forum.xda-developers.com/showthread.php?t=1737848
Odin can be found here:
http://forum.xda-developers.com/showthread.php?t=1722686
These are all stickied at the top of Android Development Thread. In the future, please search first.
Click to expand...
Click to collapse
I flashed to stock and it is still in boot loop. it can go to download mode still but no recovery and still bootloop. Please help.

Bmatthews11 said:
I flashed to stock and it is still in boot loop. it can go to download mode still but no recovery and still bootloop. Please help.
Click to expand...
Click to collapse
Ummm Pull your battery for a minute or so. Put batt back in the press power,home and volume up. When you see the blue writing at top of screen relase all 3 buttons.

I had a similar problem, you don't mention which carrier you are on, but I suspect you are using the wrong stock ROM, or an incompatible stock ROM. You need to locate one for your carrier. This is the same problem I had last week.

Same problem.
I'm having the same problem. I followed the no-counter-tripping method to flash a root-injected stock ROM and it worked fine.
I flashed to CM9 and the camera wasn't working, so I used Odin to flash back to the same root-injected stock ROM and now it never finishes booting.
I noticed that flashing to the root-injected ROM didn't delete my apps, which seems strange. I suspect that there's something lingering from CM9 that is causing the loop in stock. I don't know any way to wipe the device and flash only the root-injected ROM, but I'm hoping that will fix it. Is there a way?

Scrawson said:
I'm having the same problem. I followed the no-counter-tripping method to flash a root-injected stock ROM and it worked fine.
I flashed to CM9 and the camera wasn't working, so I used Odin to flash back to the same root-injected stock ROM and now it never finishes booting.
I noticed that flashing to the root-injected ROM didn't delete my apps, which seems strange. I suspect that there's something lingering from CM9 that is causing the loop in stock. I don't know any way to wipe the device and flash only the root-injected ROM, but I'm hoping that will fix it. Is there a way?
Click to expand...
Click to collapse
Have you tried flashing to stock ROM first (non-rooted)?
I had similar bootloop on GSII and had to go to stock to get it working. then I re-rooted.

[Q] "Kernel is not seandroid enforcing" :(

I have PayPal for which I will use to donate an amount to the person(s) who can help me.
I just recently got a new GS4 becuase of an insurance replacement. I looked at the specs before I flashed TWRP. After failing to install 4.2.2 ROMS, I finally found a 4.3 mk2 stock ROM to install. I have the phone working. But TWRP is not installed. My phone tests positive for ROOT with Rootchecker
Currently I'm getting this message everytime I boot "Kernel is not seandroid enforcing"
I have multiple 4.4.2 and 4.3 ROMs I like to use on my SD card, I'd like to continue from a TWRP backup i've made using that recovery.
Here are my current specs:
Model
SGH-M919
Android Version
4.3
Baseband
M919UVUEMK2
Kernel Version
[email protected] #1
Build Number
JSS15J.M919UVUEMK2
SELinux status
Permissive
Secure boot status
Type: Samsung

The replacement phone was probably already on the MK2 bootloader and modem when you received it. Which means you had Knox pre-installed and tripped it when you rooted the phone. The "kernel is not seandroid enforcing" error message does not affect the functioning of your phone in any way. It's just a part of the Knox bootloader. You can continue to re-install TWRP recovery and flash any ROM you want. Your phone will function as normal. Just don't try reverting to the 4.2.2 MDL baseband/modem because it won't work. There's currently no way to revert to 4.2.2 MDL if you're on MK2 or higher. If you want to get rid of the message just flash the stock kernel in a recovery.
Try to be careful with your replacement phone now since you tripped Knox. It might be harder to get a replacement depending on how T-Mobile is.
No donations are needed for these kinds of things.

Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Did I miss a step? All my actions were using odin to flash the twrp recover, and then flash another ROM, or restoring a Previous Back. Should I have flashed a rooted bootloader, or rooted firmware or anything besides those two?

nopotential said:
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Click to expand...
Click to collapse
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.

brian117 said:
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
Click to expand...
Click to collapse
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?

nopotential said:
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
Click to expand...
Click to collapse
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.

brian117 said:
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Chain's Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
Click to expand...
Click to collapse
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.

nopotential said:
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
Click to expand...
Click to collapse
Like I said donations are not needed. It does take a while for it to flash through Odin so that's normal.

It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.

nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous

nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
nopotential said:
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
Click to expand...
Click to collapse
If you continue to have WiFi problems, flash this via recovery.

brian117 said:
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
If you continue to have WiFi problems, flash this via recovery.
Click to expand...
Click to collapse
It looks like everything is looking good by following your list. Thank you.

nopotential said:
It looks like everything is looking good by following your list. Thank you.
Click to expand...
Click to collapse
Awesome! Good to hear man. Enjoy KitKat and the newest modem. The new modem has gave a significant reception boost for a lot of people. Hope it's the same for you. And please check your PM.

-Deleted-

Hard Bricked S3 At&t, booting from unbrick but no recovery or download mode

I follow this thread: http://forum.xda-developers.com/showthread.php?t=2549068
I put this file on the sd card debrick-SGH-I747U-CUEMJB3.img, made sure phone battery was charged up. Tried to enter download mode, it completely skipped it and phone is now running stock 4.3?? I try to enter recovery mode and it still just starts up with Stock 4.3.
So I assume it is running completely of the sd card. I can enter Stock Recovery but not sure what I do now. If i pull the card the phone is dead like before. Red light when plugged in, nothing happens with any button pushes.
I guess I am wondering what my next step is?
Thanks

Ruscicap said:
I follow this thread: http://forum.xda-developers.com/showthread.php?t=2549068
I put this file on the sd card debrick-SGH-I747U-CUEMJB3.img, made sure phone battery was charged up. Tried to enter download mode, it completely skipped it and phone is now running stock 4.3?? I try to enter recovery mode and it still just starts up with Stock 4.3.
So I assume it is running completely of the sd card. I can enter Stock Recovery but not sure what I do now. If i pull the card the phone is dead like before. Red light when plugged in, nothing happens with any button pushes.
I guess I am wondering what my next step is?
Thanks
Click to expand...
Click to collapse
The device is indeed booting off the SD card. However, if you can boot into system, you should also be able to boot into download and recovery modes using the 3-button combo. If you can get into download mode, you can try using Odin v 3.07 to flash the complete 4.3 stock image. Download the Odin flashable zip file from the link below to your computer. Extract the tar.md5 file and verify the MD5 to be sure it downloaded correctly.
http://www.androidfilehost.com/?fid=23329332407590581
Download Odin v3.07 and run Odin.exe for the flashing tool. With your debrick card, boot into download mode by pressing the Volume Down, Home and Power button. If you can't get into download mode with the 3-button combo, suggest you try a USB jig. Use Odin to flash the stock file to your phone. If the flashing is successful, the device should be able to boot normally after this without the debrick card.

Cool thanks Larry2999. I will have to go the USB jig route it won't go into recovery or download. I can only get into Stock recovery. Any specifics I need to know when getting a usb jig? Thanks again for you response. I am just glad it is working now. But probably don't want to run off SD forever.

Ruscicap said:
Cool thanks Larry2999. I will have to go the USB jig route it won't go into recovery or download. I can only get into Stock recovery. Any specifics I need to know when getting a usb jig? Thanks again for you response. I am just glad it is working now. But probably don't want to run off SD forever.
Click to expand...
Click to collapse
There is a thread somewhere on how to make a D-I-Y jig. You can, however, buy it cheaply online for about $3. In buying one, you'd only need to be sure it states that it works with the S3.
Looks like you are able to get into recovery now but you have stock, rather than custom, recovery. There is only one recovery partition and the default is stock, unless, you flash a custom recovery. If you had custom recovery, it would have been possible to flash a 4.3 stock restore zip via (custom) recovery. To flash custom recovery, however, you'd need Odin in download mode so we are back to the problem with getting into download mode.

Thanks Larry ordering jig tomorrow
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Larry2999 said:
There is a thread somewhere on how to make a D-I-Y jig. You can, however, buy it cheaply online for about $3. In buying one, you'd only need to be sure it states that it works with the S3.
Looks like you are able to get into recovery now but you have stock, rather than custom, recovery. There is only one recovery partition and the default is stock, unless, you flash a custom recovery. If you had custom recovery, it would have been possible to flash a 4.3 stock restore zip via (custom) recovery. To flash custom recovery, however, you'd need Odin in download mode so we are back to the problem with getting into download mode.
Click to expand...
Click to collapse
Do you suggest a reliable 4.3 stock to flash or install through ODIN? This is how I got to where I am, something screwed up trying to install stock 4.3 through ODIN.
Thanks again for your help. Jig should be here in a couple days.

Ruscicap said:
Do you suggest a reliable 4.3 stock to flash or install through ODIN? This is how I got to where I am, something screwed up trying to install stock 4.3 through ODIN.
Thanks again for your help. Jig should be here in a couple days.
Click to expand...
Click to collapse
Yes, the ONLY way to recover is to flash a complete 4.3 stock image. Are you sure you bricked in the first instance by flashing 4.3 via Odin? The only Odin compatible stock 4.3 file I'm aware of is the one in the link I forwarded earlier. This was only recently developed and appears to have been used by several people without problem. You may check to be sure you were not trying to flash a 4.1.1 file in error. Apologies if I sound like I'm second guessing you but flashing 4.1.1 via Odin usually results in the kind of hard brick you experienced.
The other alternative would be to flash custom recovery (TWRP or CWM) via Odin and then use custom recovery to flash a complete 4.3 stock image. You will find the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Download the stock restore zip for your preferred custom recovery option to your PC and save to your phone's internal storage. If you want to use TWRP, you can find the Odin flashable file for TWRP via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
If, however, you go the first option and flash the 4.3 file via Odin, be sure to use Odin v 3.07. You'll see the Odin flashable file and instructions on page 4 of the following thread ...
http://forum.xda-developers.com/showthread.php?t=2722660&page=4
or you can download directly from here ...
http://www.androidfilehost.com/?fid=23329332407590581

Thanks again. Not really sure what went wrong, tried to use odin to install 4.3 Stock from this thread. http://forum.xda-developers.com/showthread.php?t=2658486
I will try to follow your threads and get it right this time.

Ruscicap said:
Thanks again. Not really sure what went wrong, tried to use odin to install 4.3 Stock from this thread. http://forum.xda-developers.com/showthread.php?t=2658486
I will try to follow your threads and get it right this time.
Click to expand...
Click to collapse
The file from that thread is for (custom) recovery only. You can't flash zips via Odin so if you are using that file, you would need to first install custom recovery via Odin and then flash the zip via custom recovery.

Hey Larry, just wanted to say thanks. Phone is back working properly, 4.3 installed with no problem. Took me awhile never had the time. So fathers day was my chance to get this working. Flashed twrp and then the stock zip. Worked great.
Thanks again for all your help, I very much appreciate it.

Ruscicap said:
Hey Larry, just wanted to say thanks. Phone is back working properly, 4.3 installed with no problem. Took me awhile never had the time. So fathers day was my chance to get this working. Flashed twrp and then the stock zip. Worked great.
Thanks again for all your help, I very much appreciate it.
Click to expand...
Click to collapse
Glad to know it's working OK now. Kind regards

Help...semibrick or not?

Hi,
All was good in the SM-T705 world rocking 5.0.2 Rooted Stock.
But one day, decided to take the plonge and update to the 5.1.1 Unnoficial CM12.1 to try things out.
Well, all was good, but kinda lost the 4G connectivity (even after flashing the radio file provided on the thread)
So i decided to try again something, and start from Stock again.
Got myself the latest 5.0.2 image from kies and "odin it away".
Everything ok with the flash, but the device remains on the boot screen ....meaning bootloop.
Never seen a bootloop on a stock flash.
When bootlooping, i can only access download mode/recovery. Nothing else works.
Any hints?
Thanks guys.

Bootloader maybe?

rookie12 said:
Bootloader maybe?
Click to expand...
Click to collapse
Any hint how to fix this?

Idk ask a prof
Maybe flash the whole frimware via odin again

I advice you to download a stock firmware (or at least a TW based one) from here in the forum, instead of Kies.
You can try also first with a manual EXT4 reformat of System, Data and Cache though Recovery. Do NOT touch other partitions.
Then reinstall with Odin, NO tick on repartition.
It must work

Thank you guys for all your replies.
Thing is, i cant seem to be able to flash twrp. I do it through Odin and goea fine, but when it reboots it is overriding to the stock recovery again (since it can't complete the stock flash boot process)
That would be the desired scenario, since I even have a twrp backup that I'm wishing to restore.
Any other ideas?

You need to boot to twrp immediately after flashing or recovery will be overwritten with stock.
Second, once in recovery wipe data and you should be good to go.

ashyx said:
You need to boot to twrp immediately after flashing or recovery will be overwritten with stock.
Second, once in recovery wipe data and you should be good to go.
Click to expand...
Click to collapse
Got my tab back.
Thank you very much for all your help...that's why xda works most of the time.
Sent from my SM-T705 using XDA Free mobile app

Device won't boot after root install?

I recently installed a root zip file VIA CWM Recovery. After installing said root file, my device won't load. It will turn on and give me the Samsung boot logo, but will not go any further that. I get the "kernel is not seandriod enforicing" text and set bit warranty : kernel.
I tried factory wipe, cache wipe and davlik wipe. nothing is working.
I can however, go into recovery.
How can I get my phone working normally again?

lordramos said:
I recently installed a root zip file VIA CWM Recovery. After installing said root file, my device won't load. It will turn on and give me the Samsung boot logo, but will not go any further that. I get the "kernel is not seandriod enforicing" text and set bit warranty : kernel.
I tried factory wipe, cache wipe and davlik wipe. nothing is working.
I can however, go into recovery.
How can I get my phone working normally again?
Click to expand...
Click to collapse
Did you do a NAND Backup using CWM before the flash? If so, restore it.
Assuming you are on Stock, since most Custom ROMs are already rooted, you way want to use ODIN to flash the full firmware. That will get rid CWM, root, etc. But, you should be able to get past the boot logo. Do you know which version of Stock you were on?
You can download the previous firmwares here:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
and, the latest is here:
http://forum.xda-developers.com/gal...mware-firmware-kernel-modem-recovery-t3193835
Rob

rlichtefeld said:
Did you do a NAND Backup using CWM before the flash? If so, restore it.
Assuming you are on Stock, since most Custom ROMs are already rooted, you way want to use ODIN to flash the full firmware. That will get rid CWM, root, etc. But, you should be able to get past the boot logo. Do you know which version of Stock you were on?
You can download the previous firmwares here:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
and, the latest is here:
http://forum.xda-developers.com/gal...mware-firmware-kernel-modem-recovery-t3193835
Rob
Click to expand...
Click to collapse
I was on the latest OTA Update T mobile pushed out. Should be 4.4.4 , since T-Mobile didn't bless us with Lollipop

Once you get straightened out use the CF Autoroot to get your root. I use the one you flash with Odin and it has worked every time.
Jim