Develop Bugs

[Q] Possibly Bricked

So, I dun messed up.
I was on stock rooted lk8, and tried to go directly to MA7, even though I knew better. My own fault.
Anywho, once I flashed to MA7 the phone lost root, lost custom recovery, and would not activate.
I flashed CWM to it, and CWM would show up, but not allow me to do anything (wipe phone, restore nandroid).
So I tried flashing the stock image (lj1) via ODIN, and now it fails whenever it gets to sboot.img.
I can not get to recovery, stock or otherwise, it tells me to do an emergency restore from Keis (which does not work).
I can still get into download mode but the odin flash fails every time. I've tried flashing the PIT along with the stock Image but still no luck.
Anyone have any ideas before I head out to get it replaced?
UPDATE: Tried flashing back to MA7 using the oneclick and it worked, but phone is still not activated. I can get to stock recovery now as will. Will keep working on it.

MA7 issue
lil_jimmy_norton said:
So, I dun messed up.
I was on stock rooted lk8, and tried to go directly to MA7, even though I knew better. My own fault.
Anywho, once I flashed to MA7 the phone lost root, lost custom recovery, and would not activate.
I flashed CWM to it, and CWM would show up, but not allow me to do anything (wipe phone, restore nandroid).
So I tried flashing the stock image (lj1) via ODIN, and now it fails whenever it gets to sboot.img.
I can not get to recovery, stock or otherwise, it tells me to do an emergency restore from Keis (which does not work).
I can still get into download mode but the odin flash fails every time. I've tried flashing the PIT along with the stock Image but still no luck.
Anyone have any ideas before I head out to get it replaced?
UPDATE: Tried flashing back to MA7 using the oneclick and it worked, but phone is still not activated. I can get to stock recovery now as will. Will keep working on it.
Click to expand...
Click to collapse
Have you tried the chameleon fix? It is here if you search for it. That might make the phone activate. If not, do what I did and flash LJC and then move up to MA7

soft bricked my phone

Merry Christmas everyone. I tried to resolve this issue my self but was unable to. I had stock 4.3 rooted and flashed MOAR. MD5 matched. Everything seemed ok but when I flashed, it was stuck on "updating apps" for over 20 min. I did a battery pull. My phone started and I was able to go to TWRP recovery. I did a cache wipe and factory reset with plans of reflashing but everything was gone, including my nandroid. I tried to flash stock firmware from http://samsung-updates.com/ it said "failed". I cannot get back into TWRP. Is there any way I can restore to 4.1.2? Or 4.3? I just want to get the phone working again. Ideally I would like to get root back but my main priority is obviously just to get the phone working. Thank you.

jeppuda said:
Merry Christmas everyone. I tried to resolve this issue my self but was unable to. I had stock 4.3 rooted and flashed MOAR. MD5 matched. Everything seemed ok but when I flashed, it was stuck on "updating apps" for over 20 min. I did a battery pull. My phone started and I was able to go to TWRP recovery. I did a cache wipe and factory reset with plans of reflashing but everything was gone, including my nandroid. I tried to flash stock firmwa.
Click to expand...
Click to collapse
I had a similar bad expreience with updating my rooted S3,
to recover your phone try to get md5 recovery room and install it using odin, try to get the one that called recovery (runs stock 4.0.4) then you can update by Kies to 4.3.

If stock means the Samsung update you need to flash the 4.3 firmware. If stock means the de-Knoxed version from here, I would start by flashing a new recovery image then reinstalling the de-Knoxed one.
Can you not get into any recovery at all?

mjkubba said:
I had a similar bad expreience with updating my rooted S3,
to recover your phone try to get md5 recovery room and install it using odin, try to get the one that called recovery (runs stock 4.0.4) then you can update by Kies to 4.3.
Click to expand...
Click to collapse
MD5 recovery room (or rom I googled both)? I could not find it. I'm sorry i have never done this before...could you post the link for it?

Kevets said:
If stock means the Samsung update you need to flash the 4.3 firmware. If stock means the de-Knoxed version from here, I would start by flashing a new recovery image then reinstalling the de-Knoxed one.
Can you not get into any recovery at all?
Click to expand...
Click to collapse
When I press the volume up, home and power button it says "firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
I installed the de-knoxed version..I would like to go back to the de-knoxed version if possible. Is there a way to flash new recovery image through ODIN...again, I'm not very confident in my abilities right now and don't want to flash anything to make it worse. Would it be possible to send me a link with what to flash. Thank you

Sorry I meant rom not room, but youv still can get it from the dev "room" forums. I got it from there.
sorry I cant post links here yet, i dont have the enough posts, but google "unroot sprint galaxy s3" it's one of he first links and once you get the md5 file you can use it with Odin, it's a simple process.

fixed it
Fixed it, got to keep root also. Flashed a new recovery image through ODIN (link for recovery in case anyone else needs it: http://forum.xda-developers.com/showthread.php?p=38079994). Then flashed ROM. Thanks for your help guys.

help! bricked my phone i think

I was on the Swampmonster rom but i kept having issues with hands free activation do i decided to unroot and start over.
Here's what i did, i used to flash the back to stock mc2 rom here https://forum.xda-developers.com/showthread.php?t=2086769
After I flashed this, I flashed the root. zip and then rebooted back to the special recovery and it finished the install. Rebooted but am stuck at the samsung splash screen, I can get into odin and stock recovery. Is there a way to odin back to mc2 stock and get my phone working again? Thanks

scottypeterson said:
I was on the Swampmonster rom but i kept having issues with hands free activation do i decided to unroot and start over.
Here's what i did, i used to flash the back to stock mc2 rom here https://forum.xda-developers.com/showthread.php?t=2086769
After I flashed this, I flashed the root. zip and then rebooted back to the special recovery and it finished the install. Rebooted but am stuck at the samsung splash screen, I can get into odin and stock recovery. Is there a way to odin back to mc2 stock and get my phone working again? Thanks
Click to expand...
Click to collapse
Have you tried to flash a custom recovery using Odin for PC? If you can then you should try to install Billards back to stock counter reset mc2 ROM. You may have to reroot and I recommend CF Auto Root. Heres zip file for Odin. A flashable tar file to use in Odin
When running Odin make sure ONLY thing checked is Auto reboot. You are in download mode on phone...(vol down-home-then power..holding all three till it boots into download mode). Make sure com port is lit on Odin.Click on PDA and locate the cwm file and click on it. Should put it into the PDA slot, hit start. If it fails change usb input slots with cable, hit reset and try again. Make sure you have the Billard 412 Rom on external/internal before doing tthis. Once the recovery is flashed try to install the Rom.
Let me know how it goes and by the way is been awhile since Ive seen you from the OG EVO days!

ianmb said:
Have you tried to flash a custom recovery using Odin for PC? If you can then you should try to install Billards back to stock counter reset mc2 ROM. You may have to reroot and I recommend CF Auto Root. Heres zip file for Odin. A flashable tar file to use in Odin
When running Odin make sure ONLY thing checked is Auto reboot. You are in download mode on phone...(vol down-home-then power..holding all three till it boots into download mode). Make sure com port is lit on Odin.Click on PDA and locate the cwm file and click on it. Should put it into the PDA slot, hit start. If it fails change usb input slots with cable, hit reset and try again. Make sure you have the Billard 412 Rom on external/internal before doing tthis. Once the recovery is flashed try to install the Rom.
Let me know how it goes and by the way is been awhile since Ive seen you from the OG EVO days!
Click to expand...
Click to collapse
I ended up flashing Philz recovery thru odin then i was able to fix my phone. Thanks for the help.
Sent from my SPH-L900 using XDA Premium 4 mobile app

[Q] Help CWM Recovery not working

I have successfully installed Omni ROM with Android 4.4.2 to my Note 2 and I don't like it and want to go back to stock. Before installing the ROM I made a CWM recovery using version 6.0.4.3. When I boot the phone into restore I am able to restore everything but system data. When I try to restore system data I get a message that says .android_secure . img not found skipping restore. How do I fix this so I can have my phone back?

RyanGN2 said:
I have successfully installed Omni ROM with Android 4.4.2 to my Note 2 and I don't like it and want to go back to stock. Before installing the ROM I made a CWM recovery using version 6.0.4.3. When I boot the phone into restore I am able to restore everything but system data. When I try to restore system data I get a message that says .android_secure . img not found skipping restore. How do I fix this so I can have my phone back?
Click to expand...
Click to collapse
Did your restore boot?

Yes, I have restored boot. After I perform the restore everything seems to be normal during, but it gets stuck on the ATT screen during boot.

RyanGN2 said:
Yes, I have restored boot. After I perform the restore everything seems to be normal during, but it gets stuck on the ATT screen during boot.
Click to expand...
Click to collapse
Try this.
From Zen Arcade's [ROM][4.3][Dec-2013] AT&T I317-UCUBMK6/MJ4 *Stock* Rooted Odex/De-Odex/Odin thread
After flashing one of the stock packages, you may need to flash the MK6 tz.img and optionally the param.bin from the MJ4 leak. The zip below contains two Odin packages.
Try flashing the tz only package first (in Odin), then the tz+param package to see if this gets your phone to boot. You may also need to boot recovery and do a factory reset.
AT&T i317 ODIN 4.3 UCUBMK6 TZ.IMG & UCUBMJ4 (Leak) PARAM.BIN (AT&T Note 2 ONLY)
I317UCUBMK6-TZ-PARAM.zip
http://d-h.st/CDK
- Run Odin3 v3.07.exe
Download Link http://www.mediafire.com/download/77...x2/Odin307.zip
Unzip to where you can run it.
- Put your Note 2 in Download Mode
Entering download mode is very simple. First you will need to turn off your device. Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device.
Plug into a RELIABLE usb port and a RELIABLE usb cable (preferably the white Samsung cable) and wait for it to show up in Odin (COM5 or something like that)
Unzip the I317UCUBMK6-TZ-PARAM.zip file you downloaded
- Click the PDA slot in Odin and locate the I317UCUBMK6-TZ.tar.md5 that you downloaded and unzipped
The filename that goes into the PDA Slot is I317UCUBMK6-TZ.tar.md5
MAKE SURE IN THE OPTION AREA ONLY AUTO REBOOT AND F.RESET TIME ARE CHECKED!!!
- Click START and wait. It will complete and reboot.
Try flashing the tz only package first. See if it boots.
If not, repeat the above steps using I317UCUBMK6-TZ-PARAM.tar.md5.
You may also need to boot recovery and do a factory reset. Do this after second ODIN flash.
If your phone still hangs after second flash, pull the battery, and boot into recovery mode.Just hold down UP volume button and power button until recovery screen pops up.

Ok, I did all of that perfectly and my phone is still booting with Omnirom. I want to put the phone back to stock. I understand that at this point the android_secure.img cant be fixed but before rooting I backed up with Kies so putting the phone back wont be hard. I want the stock rom back and unroot and be done with it.

RyanGN2 said:
Ok, I did all of that perfectly and my phone is still booting with Omnirom. I want to put the phone back to stock. I understand that at this point the android_secure.img cant be fixed but before rooting I backed up with Kies so putting the phone back wont be hard. I want the stock rom back and unroot and be done with it.
Click to expand...
Click to collapse
Since you tried everything above and it didn't HELP..
I'm wondering have you tired the kies emergency firmware recover. I taught I screwed my phone up flashing a Odin file. Then the phone was stuck not doing anything. Couldn't boot up, nada.
But after running it thru that set up, the phone was back to completely stock...
Look HERE»»»http://goo.gl/J0P1ZX
Not sure if it'll help but worth a try right. It helped me when I was in need.
Sent from my SAMSUNG-SGH-I317 using Tapatalk

I did not know kies had a recovery option as I rarely use it. I did find a CWM stock rom but it has 4.1.2 but its working and I going to try an OTA 4.3 update and see what happens. It looks like I will manually have to restore everything which I was hoping to avoid but I thank you for your help.

RyanGN2 said:
I did not know kies had a recovery option as I rarely use it. I did find a CWM stock rom but it has 4.1.2 but its working and I going to try an OTA 4.3 update and see what happens. It looks like I will manually have to restore everything which I was hoping to avoid but I thank you for your help.
Click to expand...
Click to collapse
I'm beyond lost of what you have done and where you're at.
Appears after doing the stuff in my post #4, your phone is booting past ATT screen ???? Understand it booted into OMNI, but at least it booted.
That's all I was trying to do was to get it past the ATT screen.
If I would have know you wanted to go back to stock 4.3, you could have done this....
http://forum.xda-developers.com/showthread.php?t=2618447
You may still have too, if the OTA does not work from the CWM stock 4.1.2 ROM.
Whenever you flash ROMs rule of thumb is back up apps and anything else you want to save, with Titanium Backup or MyBackup, etc. etc. Then restore apps after new ROM is installed.
Doing a wipe/factory rest prevents residual crap from the previous ROM leftover.
Unless its an update to a ROM you already have running, and the OP says no worries, dirty flash.
69%+ of problems with ROM flashes is the flasher didn't follow instructions or half-a$$ed it and didn't wipe or factory reset.
I've been guilty of that also, so not trying to be combative or accusatory.
Good luck with OTA.

When I did the steps in post #4 it never did anything it stayed in omnirom, which I have not had a problem getting to boot. It doesn't boot when I restore from my backup created before I installed Omni with CWM. I don't like Omni and I am tired of everything root. I'm a heavy jail breaker and thought I could do this however its more learning than I wanted and want to be done with root entirely. The OTA update did fail. Should I still use the 4.3 rom above or is there something else I should that will also remove root? I did backup apps with titanium and I also backed up everything with Kies.

[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-