Database Users

Possible Brick

I just got a replacement Galaxy S4 today. I didn't even bother to check what ROM it was on because I didn't think to pay attention. I flashed CWM with a tool (http://forum.xda-developers.com/showthread.php?t=2297033) and CWM booted fine. I went to install the Paranoid Android 4.3 beta, and all went as planned. I rebooted, and it just hung on the Paranoid Android boot screen. If I then turn the phone off and reboot, it get stuck on the Samsung locked screen. I'm praying I didn't brick this thing for good, but reading about the MF3 headaches, I'm not so sure. Can anyone offer some insight? I can't access USB in CWM either.
Edit: The box says SW-VER: 1337UCUAMDL; does that mean I'll be able to odin to stock?

geokhentix said:
I just got a replacement Galaxy S4 today. I didn't even bother to check what ROM it was on because I didn't think to pay attention. I flashed CWM with a tool (http://forum.xda-developers.com/showthread.php?t=2297033) and CWM booted fine. I went to install the Paranoid Android 4.3 beta, and all went as planned. I rebooted, and it just hung on the Paranoid Android boot screen. If I then turn the phone off and reboot, it get stuck on the Samsung locked screen. I'm praying I didn't brick this thing for good, but reading about the MF3 headaches, I'm not so sure. Can anyone offer some insight? I can't access USB in CWM either.
Edit: The box says SW-VER: 1337UCUAMDL; does that mean I'll be able to odin to stock?
Click to expand...
Click to collapse
If you are on AT&T MDL firmware you should be able to ODIN to stock, do a factory reset and take it from there. I suggest you do a lot more reading before you touch anything else. You can start by reading the "pinned" threads in the General section. Everything you need you will find there. Good luck

You need to flash Loki doki after each custom ROM if you're in CWM or any non auto loki'd recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

djpharoah said:
You need to flash Loki doki after each custom ROM if you're in CWM or any non auto loki'd recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
What he said...you are not on mf3 dont worry about that...if you were on mf3 you wouldny have been able to even get a recoveryjust odin to stock and start over...either find and use the "loki doki" zip (google can find it) and flash it after every rom flash or use the auto loki recovery which pretty much runs the loki doki script every rom rom flash for you right before it reboots
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

mg2195 said:
What he said...you are not on mf3 dont worry about that...if you were on mf3 you wouldny have been able to even get a recoveryjust odin to stock and start over...either find and use the "loki doki" zip (google can find it) and flash it after every rom flash or use the auto loki recovery which pretty much runs the loki doki script every rom rom flash for you right before it reboots
Click to expand...
Click to collapse
The tool he linked contains auto-loki CWM so I'm not sure that's his problem.
Definitely ODIN back to stock with this procedure:
http://forum.xda-developers.com/showthread.php?t=2261573
Using the MDL download you can find here:
http://forum.xda-developers.com/showthread.php?t=2263533
And try again! Make sure you read the stickies in the general forum too.

[Q] Another "phone not booting" issue

NOTE: AT&T variant. Phone is running 4.2.2 with MF3 baseband
So I'm helping a friend root his phone and run a custom ROM. The root went successfully (motochopper) and we installed SafeStrap and then we did a backup and wipe and then installed a 4.3 Google Play edition ROM (first mistake as we meant to download the 4.2 version)
I have the stock firmware zip for the phone and figured that that was the way to fix it, but I can't figure out how to get it to install. Through ADB it gives me an error after starting DAEMON. I converted the zip to a .tar and tried to use ODIN but ODIN stops working as soon as I tell it to run. I made sure I had the most current, correct drivers and am running ODIN3 v1.85. I thought maybe if I put it on the SD card I could install it though that method via the stock recovery but it says there is an invalid arguement.
What am I doing wrong?
Help

h_smith said:
NOTE: AT&T variant. Phone is running 4.2.2 with MF3 baseband
So I'm helping a friend root his phone and run a custom ROM. The root went successfully (motochopper) and we installed SafeStrap and then we did a backup and wipe and then installed a 4.3 Google Play edition ROM (first mistake as we meant to download the 4.2 version)
I have the stock firmware zip for the phone and figured that that was the way to fix it, but I can't figure out how to get it to install. Through ADB it gives me an error after starting DAEMON. I converted the zip to a .tar and tried to use ODIN but ODIN stops working as soon as I tell it to run. I made sure I had the most current, correct drivers and am running ODIN3 v1.85. I thought maybe if I put it on the SD card I could install it though that method via the stock recovery but it says there is an invalid arguement.
What am I doing wrong?
Help
Click to expand...
Click to collapse
What stock firmware zip do you have? You have to have the mf3 .tar.md5 file if you're trying to use odin

How does he have mf3 and motochopper works? It shouldn't. Also you have to have a custom recovery to flash the gpe rom and we don't. The closest thing we have is safestrap.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

HiTideBlastoise said:
How does he have mf3 and motochopper works? It shouldn't. Also you have to have a custom recovery to flash the gpe rom and we don't. The closest thing we have is safestrap.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure. I just used the first method I found and it worked. Then when it came to the recovery part that's when I found out about his baseband

jd1639 said:
What stock firmware zip do you have? You have to have the mf3 .tar.md5 file if you're trying to use odin
Click to expand...
Click to collapse
I'm on the SamMobile site trying to find the firmware and it says that they don't have it. I find that weird that such a popular model doesn't have the firmware needed to do this. I put in the correct model and country
EDIT: nevermind.

[Q] Set Warranty Bit : recovery

Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
RECOVERY BOOTING....
Click to expand...
Click to collapse
Set Warranty Bit : recovery
Click to expand...
Click to collapse
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.

MrGovernor said:
Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.
Click to expand...
Click to collapse
no its fine all n3 rooted will have that when and if you go back to stock it will go

jaythenut said:
no its fine all n3 rooted will have that when and if you go back to stock it will go
Click to expand...
Click to collapse
Thanks a load!

MrGovernor said:
Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.
Click to expand...
Click to collapse
it's normal

hhai2pth said:
it's normal
Click to expand...
Click to collapse
Now... Another issue...
I installed PhilZ Touch Recovery and that has worked fine...
However, I went full retard and 'Wiped System for a New ROM' before I made a backup...
I then tried to flash FoxHound ROM, I managed to get through the install process flawlessly, BUT, when the device rebooted it stays on the boot screen...
What can be done to fix this? As I failed to make a backup of my original 4.3 firmware...
Thanks Again!

MrGovernor said:
Now... Another issue...
I installed PhilZ Touch Recovery and that has worked fine...
However, I went full and 'Wiped System for a New ROM' before I made a backup...
I then tried to flash FoxHound ROM, I managed to get through the install process flawlessly, BUT, when the device rebooted it stays on the boot screen...
What can be done to fix this? As I failed to make a backup of my original 4.3 firmware...
Thanks Again!
Click to expand...
Click to collapse
Did u use correct ROM for 4.3? Did u tried flash stock rom again?

hhai2pth said:
Did u use correct ROM for 4.3? Did u tried flash stock rom again?
Click to expand...
Click to collapse
I can't find the 4.3 firmare... Only the 4.4.2 firmare...
I just realized I may have to flash with O2's stock firmare as it is an O2 device...

MrGovernor said:
Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.
Click to expand...
Click to collapse
oh man...
You are running 4.3, but you flash cwm for KK (4.4.2) ?
You should flash cwm for 4.3 instead.
Try to find the stock firmware, and reflash it.
Cheers!
---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------
MrGovernor said:
Now... Another issue...
I installed PhilZ Touch Recovery and that has worked fine...
However, I went full retard and 'Wiped System for a New ROM' before I made a backup...
I then tried to flash FoxHound ROM, I managed to get through the install process flawlessly, BUT, when the device rebooted it stays on the boot screen...
What can be done to fix this? As I failed to make a backup of my original 4.3 firmware...
Thanks Again!
Click to expand...
Click to collapse
if you have installed the ROM flawlessly and stuck at the boot screen, try go into recovery again and make a full wipe (but not the wipe for new rom). Then reboot.
But the custom ROM you are flashing is 4.3 also right ?
Because very simple, if you were on stock 4.3, and you flash custom ROM 4.4.2 without update your bootloader first to 4.4.2, the custom ROM won't run.
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
MrGovernor said:
I can't find the 4.3 firmare... Only the 4.4.2 firmare...
I just realized I may have to flash with O2's stock firmare as it is an O2 device...
Click to expand...
Click to collapse
if your device N9005, you may use any other firmware so long as for N9005.
You can try to flash 4.4.2, but you have to tick "update bootloader" at ODIN. Please note, once you are on 4.4.2, you are not able to go back to 4.3, due to different bootloader.

antique_sonic said:
oh man...
You are running 4.3, but you flash cwm for KK (4.4.2) ?
You should flash cwm for 4.3 instead.
Try to find the stock firmware, and reflash it.
Cheers!
---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------
if you have installed the ROM flawlessly and stuck at the boot screen, try go into recovery again and make a full wipe (but not the wipe for new rom). Then reboot.
But the custom ROM you are flashing is 4.3 also right ?
Because very simple, if you were on stock 4.3, and you flash custom ROM 4.4.2 without update your bootloader first to 4.4.2, the custom ROM won't run.
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
if your device N9005, you may use any other firmware so long as for N9005.
You can try to flash 4.4.2, but you have to tick "update bootloader" at ODIN. Please note, once you are on 4.4.2, you are not able to go back to 4.3, due to different bootloader.
Click to expand...
Click to collapse
That's cleared a load up! I'll install the 4.3 firmware and get back to you (Samsung's Firmware Download Servers are incredibly slow <,<)

yeah. good luck

Thanks for all the help!
I used ODIN to flash this file:
N9005XXUENB4_N9005O2UENB1_N9005XXUENB1_HOME.tar.md5
From SamMobile's Firmware.
It's all working now, and it on the 4.4.2 KitKat Built.
Does this mean the bootload has updated and I can install the 4.4 Omega ROM?
This time I will make a restore point on PhilZ Custom Recovery!

MrGovernor said:
Thanks for all the help!
I used ODIN to flash this file:
N9005XXUENB4_N9005O2UENB1_N9005XXUENB1_HOME.tar.md5
From SamMobile's Firmware.
It's all working now, and it on the 4.4.2 KitKat Built.
Does this mean the bootload has updated and I can install the 4.4 Omega ROM?
This time I will make a restore point on PhilZ Custom Recovery!
Click to expand...
Click to collapse
when you flash it, u did tick the update bootloader right ?
If yes, means you are now on the 4.4.2 bootloader, and you can install the 4.4 custom ROM (but please read the respective thread on how to flash that custom ROM of your choice)
And when you want to flash Philz CWM, do choose the one for 4.4.2. Try to use the latest one.
Good luck!

antique_sonic said:
when you flash it, u did tick the update bootloader right ?
If yes, means you are now on the 4.4.2 bootloader, and you can install the 4.4 custom ROM (but please read the respective thread on how to flash that custom ROM of your choice)
And when you want to flash Philz CWM, do choose the one for 4.4.2. Try to use the latest one.
Good luck!
Click to expand...
Click to collapse
Thanks!
But... On last problem...
I've downloaded and used ODIN to install PhillZ Recovery ("philz_touch_6.08.9-hltexx.tar.md5").
It passes in ODIN, and boots straight to android.
However, when I try to boot into recovery mode, I get the normal 3 lines of text, but after a few seconds it reboots back to android...
What do?
P.S: I tried holding down all 3 buttons through the whole process (that just reboots), holding down only the Home and Volume + buttons once the text appears (still reboots)... I've also tried to Re-Flash the same version twice.
I just want to make a backup for this ROM in-case I f*ck up with other ROMs. Sorry for being such a scrub!
------NOTE----------
Installed Latest Version of PhillZ, all works A-OK!

MrGovernor said:
Thanks!
But... On last problem...
I've downloaded and used ODIN to install PhillZ Recovery ("philz_touch_6.08.9-hltexx.tar.md5").
It passes in ODIN, and boots straight to android.
However, when I try to boot into recovery mode, I get the normal 3 lines of text, but after a few seconds it reboots back to android...
What do?
P.S: I tried holding down all 3 buttons through the whole process (that just reboots), holding down only the Home and Volume + buttons once the text appears (still reboots)... I've also tried to Re-Flash the same version twice.
I just want to make a backup for this ROM in-case I f*ck up with other ROMs. Sorry for being such a scrub!
------NOTE----------
Installed Latest Version of PhillZ, all works A-OK!
Click to expand...
Click to collapse
Sorry was bit busy.
But if you do read my last post... I did mentioned you have to use the latest one better
Cheers, mate!
btw :
why do you like to use KK recovery on 4.3, and when you are on KK, you use 4.3 recovery ?

Set warranty bit is different than set warranty kernel

jerryspring said:
Set warranty bit is different than set warranty kernel
Click to expand...
Click to collapse
And what exactly is the point of posting this in a 4.5 years old thread ?

Dejan Sathanas said:
And what exactly is the point of posting this in a 4.5 years old thread ?
Click to expand...
Click to collapse
Cuz I asked a question and no one answered me. What would be causing the bootloop on my phone? With stock and custom ROMs, it is bootlooping in and out of recovery and saying set warranty bit recovery ...

But no user has to answer you .
Post and if somebody sees it and has the answer they will .
But on the Q&A board as very few read it now and a day is not long enough.

JJEgan said:
But no user has to answer you .
Post and if somebody sees it and has the answer they will .
But on the Q&A board as very few read it now and a day is not long enough.
Click to expand...
Click to collapse
The o.p is different than my question! So, instead of making a duplicate thread with basically same issue, I posted in here.

[Q] may have bricked my nc1

Ok so I had a nc1.. used towel root,rf, and safe strap.made a backup and tried flashing gravitron... now I'm in a nonstop bootloop or I'm at the warning custom o's found.... can any one tell me where to start to fix? Currently downloading Odin to try and flash a stock image if it has?

cbrewington75 said:
Ok so I had a nc1.. used towel root,rf, and safe strap.made a backup and tried flashing gravitron... now I'm in a nonstop bootloop or I'm at the warning custom o's found.... can any one tell me where to start to fix? Currently downloading Odin to try and flash a stock image if it has?
Click to expand...
Click to collapse
Do you still get the Safestrap splash screen on boot? If so you can just restore or reflash. Otherwise, you'll need to use the NB1 Odin and take the NC1 OTA.
Before you flash again, make sure you wipe in Safestrap (all but external SD) and check your ROM. Make sure it doesn't need an updater-script in the All Things MK2 & NB1 thread and for gravitron specifically download the Safestrap version of it.
Sent from my SGH-I337 running GPE

DeadlySin9 said:
Do you still get the Safestrap splash screen on boot? If so you can just restore or reflash. Otherwise, you'll need to use the NB1 Odin and take the NC1 OTA.
Before you flash again, make sure you wipe in Safestrap (all but external SD) and check your ROM. Make sure it doesn't need an updater-script in the All Things MK2 & NB1 thread and for gravitron specifically download the Safestrap version of it.
Sent from my SGH-I337 running GPE
Click to expand...
Click to collapse
man this has taken all day....
1. basically i did make a intial backup with safstrap in slot 1 cause thats all i could use.
i flashed gravitron the att version but i guess there is a kernal mod i need to be flashing after.
needless to say i finally got into odin and got a tar. file for a fully rootable 4.4.2
ive flashed since my evo....this new safstrap especially anything to do with flashing, do i have a recovery or no, can i even flash right now or is it just to freeze things in TB??
so much stuff on xda.....yes i used search ...thats why im back to a normal phone....but geeze man
Thanks for the help

cbrewington75 said:
man this has taken all day....
1. basically i did make a intial backup with safstrap in slot 1 cause thats all i could use.
i flashed gravitron the att version but i guess there is a kernal mod i need to be flashing after.
needless to say i finally got into odin and got a tar. file for a fully rootable 4.4.2
ive flashed since my evo....this new safstrap especially anything to do with flashing, do i have a recovery or no, can i even flash right now or is it just to freeze things in TB??
so much stuff on xda.....yes i used search ...thats why im back to a normal phone....but geeze man
Thanks for the help
Click to expand...
Click to collapse
Man i did the same thing when i first got this phone 3 weeks ago . i read a lot a first but i was so used to a phone without a locked boot loader. if you ahev any ?'s feel free to ask away . Im willing to help out .. i learned a ton since 3 weeks ago .. especially after bricking twice . If you have to use safetstrap then after falshing a rom do not reboot . flash the approiate kernel modules and Su if it calls for it in the install instructions.. Good luck

[Q] What's next

I'm going to flash the new ROM over my 4.4.2 S4 LTE. After flashing this new ROM, what are the necessary steps I should do to get my phone rooted?
Which are the compatible flashing/rooting programs to use for this new ROM?

greeny2010 said:
I'm going to flash the new ROM over my 4.4.2 S4 LTE. After flashing this new ROM, what are the necessary steps I should do to get my phone rooted?
Which are the compatible flashing/rooting programs to use for this new ROM?
Click to expand...
Click to collapse
You're talking about official 5.0.1?

GDReaper said:
You're talking about official 5.0.1?
Click to expand...
Click to collapse
Yes. That's the ROM I'm talking about. I've just flashed Philipz recovery using Odin and everything looking fine. However, I still get the default recovery and not the PhilipZ version.
Is the 5.0.1 not ready for the present recover like Chainfire or Philipz?

greeny2010 said:
Yes. That's the ROM I'm talking about. I've just flashed Philipz recovery using Odin and everything looking fine. However, I still get the default recovery and not the PhilipZ version.
Is the 5.0.1 not ready for the present recover like Chainfire or Philipz?
Click to expand...
Click to collapse
I had problems flashing recovery on stock kitkat. Used a workaround with Nandroid manager from play. But you need root for that..
Maybe try a different recovery. I don't see why PhilZ would be the only one to work with the 5.0 rooting method presented somewhere around the forum.

A recovery has nothing to do with the version of the rom you have flashed.
Uncheck auto-reboot before flashing the rom with Odin.

Lennyz1988 said:
A recovery has nothing to do with the version of the rom you have flashed.
Uncheck auto-reboot before flashing the rom with Odin.
Click to expand...
Click to collapse
Will give this a try.
Update - No go with what you have described. Stuck at the end of Odin flashing. Have to pull out the battery. Luckily, phone still can boot but with the default recovery.