So my problem is that I have an rooted phone (galaxy s4 gt-i9505) and was running Android 4.3 but since the 4.4.2 update came I wanted to Unroot via Odin I downloaded the appropriate file from samfirmware and used Odin first it gave me an pit error so I got a pit file and then I tried to flash it again but just got an error '' Complete(Write) operation failed.'' Then I took the battery out and restarted my phone well ofc it got soft bricked but I cant even flash TWRP nor the official firmware so how am i supposed to unbrick this phone. I am crying my eyes out right I hope you can help me fast or I wont be able to sleep tonight.
Ali4436 said:
So my problem is that I have an rooted phone (galaxy s4 gt-i9505) and was running Android 4.3 but since the 4.4.2 update came I wanted to Unroot via Odin I downloaded the appropriate file from samfirmware and used Odin first it gave me an pit error so I got a pit file and then I tried to flash it again but just got an error '' Complete(Write) operation failed.'' Then I took the battery out and restarted my phone well ofc it got soft bricked but I cant even flash TWRP nor the official firmware so how am i supposed to unbrick this phone. I am crying my eyes out right I hope you can help me fast or I wont be able to sleep tonight.
Click to expand...
Click to collapse
Which appropriate file hav you flashed
Sent from my GT-I9500 using Tapatalk
Hello, I also bricked my phone, and this flashing was successful:
I9505XXUFNB9_I9505EURFNB1_EUR.zip with CSB_signed_Fusion3_EUR_0325_V2.pit.
The whole story is: http://forum.xda-developers.com/showthread.php?t=2684499
I don't know, if the cf-autoroot will be successfull...
The appropriate file is called I9505XXUFNB8_I9505OXAFNB8_I9505XXUFNB8_HOME.tar.md5 its the germany dbt version
XM2000 said:
Hello, I also bricked my phone, and this flashing was successful:
I9505XXUFNB9_I9505EURFNB1_EUR.zip with CSB_signed_Fusion3_EUR_0325_V2.pit.
The whole story is: http://forum.xda-developers.com/showthread.php?t=2684499
I don't know, if the cf-autoroot will be successfull...
Click to expand...
Click to collapse
After every succesfull flashing there should b a sucessfull wiping/factory reset i hope u did so
Sent from my GT-I9500 using Tapatalk
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
Ali4436 said:
The appropriate file is called I9505XXUFNB8_I9505OXAFNB8_I9505XXUFNB8_HOME.tar.md5 its the germany dbt version
Click to expand...
Click to collapse
Do you check repartition option on using pit file
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
After every succesfull flashing there should b a sucessfull wiping/factory reset i hope u did so
Sent from my GT-I9500 using Tapatalk
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
Do you check repartition option on using pit file
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Yes it is always checked when I use the pit file for flashing
I think with repartitioning with pit file the wipe is unnecessary, but I made it.
The cf-autoroot is working on this ROM.
How can I use again CWM or TWRP?
Which recovery do you want
Sent from my GT-I9500 using Tapatalk
The main question is how...
I am using TWRP and CWN on my Galaxy S I9000 from 2011, and for a half year on I9505. I installed them several times and no problem.
Now I routed the stock I9505 4.3 ROM and flashing the CWM made it almost brick. I cannot reinstall the same 4.3, only a 4.4.2.
I have read it is "normal", so I am searching for another method.
XM2000 said:
The main question is how...
I am using TWRP and CWN on my Galaxy S I9000 from 2011, and for a half year on I9505. I installed them several times and no problem.
Now I routed the stock I9505 4.3 ROM and flashing the CWM made it almost brick. I cannot reinstall the same 4.3, only a 4.4.2.
I have read it is "normal", so I am searching for another method.
Click to expand...
Click to collapse
For sure you can flash your stock 4.3. Because while rooting and flashing a recovery, you didn't upgrade the bootloader. So you can flash your stock 4.3 firmware and try to flash the recovery again. If you want, you could also Odin flash a stock kitkat firmware, but that means: no going back to 4.3.
For sure you can flash your stock 4.3. Because while rooting and flashing a recovery, you didn't upgrade the bootloader. So you can flash your stock 4.3 firmware and try to flash the recovery again. If you want, you could also Odin flash a stock kitkat firmware, but that means: no going back to 4.3.
Click to expand...
Click to collapse
Yes, you are right...I know it is no downgrade, but my phone did not know. Really, I could not flash anything in that phase, even the original stock 4.3 ROM which was on the phone. I had no phone for 3 days, I tried to flash many times many images: oiginal stock ROM, modified 4.3 bootloader.
But I got in Odin everything is failed. No system, no recovery...
The only successful one was the 4.4.2 stock ROM, I tried it after 3 days. Now I have this version.
So I don't know how can I flash the CWM without bricking my phone.
XM2000 said:
Yes, you are right...I know it is no downgrade, but my phone did not know. Really, I could not flash anything in that phase, even the original stock 4.3 ROM which was on the phone. I had no phone for 3 days, I tried to flash many times many images: oiginal stock ROM, modified 4.3 bootloader.
But I got in Odin everything is failed. No system, no recovery...
The only successful one was the 4.4.2 stock ROM, I tried it after 3 days. Now I have this version.
So I don't know how can I flash the CWM without bricking my phone.
Click to expand...
Click to collapse
You can flash cwm without bricking nd thats sure ......download philz advanced cwm recovery or other nd flash via odin
Sent from my GT-I9500 using Tapatalk
Related
Hello Guys,
I'm stuck with my Samsung Galaxy S4. It's a GT-I9505 by Vodafone Germany. I came from stock Samsung Firmware 4.22 and wanted to root by using Odin3 an CF-Auto-Root. When flashing the cf-auto-root....tar.md5 Odin showed FAIL instead of PASS.
I think my big mistake was, not to switch the phone to USB-debugging ON. I forgot this. So now, when booting, the device asks me to do the emergency recovery with Samsung KIES. But unfortunately this doesn't work. Kies says Phone not connected. What can i do?
As far as i can figure out, i crashed the kernel with this flashing-attempt. i read something about using a PIT-File and a stock-rom to fix this.
Luckily i can boot to download-mode and also Odin seems to realize, that i plugged in the phone.
I would be VERY happy and thankful, if someone could give me a hint or even better a step-by-step instruction, how to get my Galaxy S4 back to work. Even with the stock Firmware. At least, it's working again....but how can i manage it?
Thanks guys!
Alex.
Look in the i9505 forum for a stock firmware tar and flash it via Odin and you will be back 100% stock as if you just bought it. Instructions for flashing the stock firmware tar will be in the post. I would search and link you but on my phone.
Sent from my SGH-M919 using xda app-developers app
Adam0524 said:
Look in the i9505 forum for a stock firmware tar and flash it via Odin and you will be back 100% stock as if you just bought it. Instructions for flashing the stock firmware tar will be in the post. I would search and link you but on my phone.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
MAy be you have a link for me? I'm new to this forum and site....
Thanks a lot!
Sy36 said:
MAy be you have a link for me? I'm new to this forum and site....
Thanks a lot!
Click to expand...
Click to collapse
Here ya go http://forum.xda-developers.com/showthread.php?t=2252982
Its possible you had a corrupted cf-autoroot image. If you have an MD5 on the stock rom you download, use ODIN 3.04 or 3.07 to flash as they check the MD5 sums before flashing as long as the rom has an MD5 extension - .tar.md5.
ultramag69 said:
Its possible you had a corrupted cf-autoroot image. If you have an MD5 on the stock rom you download, use ODIN 3.04 or 3.07 to flash as they check the MD5 sums before flashing as long as the rom has an MD5 extension - .tar.md5.
Click to expand...
Click to collapse
FIRST OF ALL:
Thank you very much for helping me!
I got my SGS4 back working! :laugh::laugh::laugh:
But it wasn't done with only flashing a stock ROM. I also had to use a PIT file for repartioning the phone.
Another trick (or was it just coincident?) was, i had to use to ORIGINAL usb-cable for flashing. First i used a third-party usb-cable. May this was also an issue.
So in the end, i followed this howto:
wccftech.com/how-to-unbrick-samsung-galaxy-s4
i downloaded the PIT-file and the stock firmware, recommended by Adam0524, from further above.
I hope my mistakes while flashing my SGS4 and the solution i found may help others, who run into the same problem. So if you have trouble flashing your S4's and get a FAIL message in Odin, but if you can still enter the download-mode, there will be a great chance to get it back working.
What you'll need is:
Odin 3.07
Stock firmware for GT-I9505 (about 1,7 GB)
PIT-File for your GT-I9505 (about 3 KB)
ORIGINAL Samsung usb-cable (!)
and relax, everything will be good in the end
P.S.: I'm so glad that my S4 is working again...!!!!! :laugh:
Your problem was in usb cable.
Btw, usb debug has to do nothing with flashing with odin. It is used only when you are booted in OS
Sent from my Galaxy
Also, just as a caution to all noob flashers, god that sounds rude, remember that flashing a pit file is generally the LAST thing you do before sending it back to Samsung... There is a very large amount of risk in flashing pit files. If you have the wrong one, this happens a lot with people new to playing with their phones, the file is corrupt or you just do something bad then you can end up with a true brick...
I have an S3 that someone played around with. I can boot to download mode, no recovery and can't repartition... Needs j-tag when I get the time....
i9505 bricked
I've been running 4.2.2 stock rooted with CF autoroot and using Philz recovery when tried to flash 4.3 through Mobile Odin, and I ended up having my phone bricked. It only goes in download mode and when trying to recover from kies it gets stuck in the same screen where it shoes *** SV REV. CHECK FAIL : Fused : 3 , Binary : 1 *** I desperately need some help with this guys.
Thanks in advance.
rubnduardo said:
I've been running 4.2.2 stock rooted with CF autoroot and using Philz recovery when tried to flash 4.3 through Mobile Odin, and I ended up having my phone bricked. It only goes in download mode and when trying to recover from kies it gets stuck in the same screen where it shoes *** SV REV. CHECK FAIL : Fused : 3 , Binary : 1 *** I desperately need some help with this guys.
Thanks in advance.
Click to expand...
Click to collapse
Hows it? I think you would have figured by now. Just flash a stock ROM via download mode / Odin
Btw, OP I was shocked that you wrote CF-Autoroot bricked your device, it is by far the safest root method available. As you have aknolwedged later it is not a problem caused by it.
dogmatism said:
Hows it? I think you would have figured by now. Just flash a stock ROM via download mode / Odin
Btw, OP I was shocked that you wrote CF-Autoroot bricked your device, it is by far the safest root method available. As you have aknolwedged later it is not a problem caused by it.
Click to expand...
Click to collapse
It was a problem with the bootloader as we all know android 4.3 has new ones -.-! I felt like the biggest noob ever. Do you happen to know about a GPe based rom for i9505?
Hello all, so i've run into a little problem and after a few hours i cant figure out what i did wrong so i reach out for help
i rooted my device successfully with odin and instlal CWM.
booted into recover, wiped data/cache/system/data as the walk through told me
then install a cx rom from here
http://forum.xda-developers.com/show....php?t=2391142
now when i turn my device on it gose stright into downloading mode with "could not do normal boot" in the top right
can any1 tell me waht i did wrong or missed?
oh i can sitll get into recovery
thanks in advanced
BurnAll said:
Hello all, so i've run into a little problem and after a few hours i cant figure out what i did wrong so i reach out for help
i rooted my device successfully with odin and instlal CWM.
booted into recover, wiped data/cache/system/data as the walk through told me
then install a cx rom from here
http://forum.xda-developers.com/show....php?t=2391142
now when i turn my device on it gose stright into downloading mode with "could not do normal boot" in the top right
can any1 tell me waht i did wrong or missed?
oh i can sitll get into recovery
thanks in advanced
Click to expand...
Click to collapse
Did you check the MD5 before flashing? Are you absolutely sure the ROM your flashing is compatible with your device? Were you on the latest MF3 firmware before you started flashing?
agent929 said:
Did you check the MD5 before flashing? Are you absolutely sure the ROM your flashing is compatible with your device? Were you on the latest MF3 firmware before you started flashing?
Click to expand...
Click to collapse
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142
BurnAll said:
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142
Click to expand...
Click to collapse
heck at this point i'd be happy just to get it back to normal as its late and i need to sleep and work tomorrow
BurnAll said:
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142
Click to expand...
Click to collapse
Anything that says i337 will work on your phone, given that the developer has it bug free (the US ATT Samsung Galaxy S4)
agent929 said:
Anything that says i337 will work on your phone, given that the developer has it bug free (the US ATT Samsung Galaxy S4)
Click to expand...
Click to collapse
okay so this should work i also put on kernal
http://forum.xda-developers.com/show...php?p=41675354
4.2.2 TW version.
but still saying could no do normal boot, while on downloading screen
BurnAll said:
okay so this should work i also put on kernal
http://forum.xda-developers.com/show...php?p=41675354
4.2.2 TW version.
but still saying could no do normal boot, while on downloading screen
Click to expand...
Click to collapse
It says page not found...get the dots out of your link
Did you use your carriers Kernel?
Hey I just noticed that your subject for this post says i337m. Can you confirm if you have a i337 or an i337m please? Thank you.
agent929 said:
Hey I just noticed that your subject for this post says i337m. Can you confirm if you have a i337 or an i337m please? Thank you.
Click to expand...
Click to collapse
i have the m
BurnAll said:
i have the m
Click to expand...
Click to collapse
it appears you have flashed an ATT rom for the i337 and not a Rom for the i337m -- you now have several options to restore your phone
1. flash the Loki'd fix to allow the kernel and rom you flashed to boot your phone or
2. flash a cutom kernel that does work with your phone such a Ktoonz kernel (read the install instructions, for your i337m you need the TMO version of his kernel) or
3 download the stock firmware package for your phone, I'd recommend MG1 either from a link on xda or from samMobile or Samsung updates and install using Odin -- this will completely reset you phone and then you can worry about root and custom recovery after
If you do decide to install fresh factory stock MG1 I can recommend using CF-root to root the i337m and then installing Philz Recovery rather than regular CWM as it installs more easily and plays nicer on the i337m in my experience.
Remember each phone is different but do not attempt to install ATT designed roms on your i337m unless you have the loki patch also on your SD card ready to flash also.
There are many great roms available that do fir the i337m and are specifically set up for our phone.
But first, let's get you out of the download loop. EIther of the 3 options above will do. Personally, I would recommend the Odin install of the stock MG1 firmware and start over with a factory reset and a clean phone.
agent929 said:
It says page not found...get the dots out of your link
Click to expand...
Click to collapse
sorry here it is.
another fella on bell said this one worked for him
http://forum.xda-developers.com/showthread.php?p=41675354
lgsshedden said:
it appears you have flashed an ATT rom for the i337 and not a Rom for the i337m -- you now have several options to restore your phone
1. flash the Loki'd fix to allow the kernel and rom you flashed to boot your phone or
2. flash a cutom kernel that does work with your phone such a Ktoonz kernel (read the install instructions, for your i337m you need the TMO version of his kernel) or
3 download the stock firmware package for your phone, I'd recommend MG1 either from a link on xda or from samMobile or Samsung updates and install using Odin -- this will completely reset you phone and then you can worry about root and custom recovery after
If you do decide to install fresh factory stock MG1 I can recommend using CF-root to root the i337m and then installing Philz Recovery rather than regular CWM as it installs more easily and plays nicer on the i337m in my experience.
Remember each phone is different but do not attempt to install ATT designed roms on your i337m unless you have the loki patch also on your SD card ready to flash also.
There are many great roms available that do fir the i337m and are specifically set up for our phone.
But first, let's get you out of the download loop. EIther of the 3 options above will do. Personally, I would recommend the Odin install of the stock MG1 firmware and start over with a factory reset and a clean phone.
Click to expand...
Click to collapse
okay thanks i'll try to restore it using odin with the MG1 and then give the philz a shot. i'll update u once i've done so.
CF root:
http://forum.xda-developers.com/showthread.php?t=2293800
Philz recovery
http://forum.xda-developers.com/showthread.php?t=2201860
Goldeneye Rom:
http://forum.xda-developers.com/showthread.php?t=2313469
stock rooted MG1 rom
http://forum.xda-developers.com/showthread.php?t=2375180
stock firmware download links:
http://forum.xda-developers.com/showthread.php?t=2269304
lgsshedden said:
CF root:
http://forum.xda-developers.com/showthread.php?t=2293800
Philz recovery
http://forum.xda-developers.com/showthread.php?t=2201860
Goldeneye Rom:
http://forum.xda-developers.com/showthread.php?t=2313469
stock rooted MG1 rom
http://forum.xda-developers.com/showthread.php?t=2375180
stock firmware download links:
http://forum.xda-developers.com/showthread.php?t=2269304
Click to expand...
Click to collapse
okay got it back to stock, now quick question for the philz do i flash the .tar with odin? or do something else with the .zip?
Its not the ROM that's incomparable its the kernal your using. Find one for a i337m then flash it immediately after you flash your ROM and see if it works.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
---------- Post added at 09:58 PM ---------- Previous post was at 09:58 PM ----------
Zip gets flashed in your recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
agent929 said:
Its not the ROM that's incomparable its the kernal your using. Find one for a i337m then flash it immediately after you flash your ROM and see if it works.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
---------- Post added at 09:58 PM ---------- Previous post was at 09:58 PM ----------
Zip gets flashed in your recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
so just to go over the steps to make sure i dont mess this up,
so i flashed to the origonal versoin with odin
that worked
then i rooted it using CF root
now i got 2 files from philz and i'm not 100% sure what to do with them, i got a .tar what i assume i flash with odin and a .zip i'm not to sure what i do with they are both named philz_touch_5.15.0-jfltecan.tar.md5 and philz_touch_5.15.0-jfltecri.zip
then once i get into recovery i know how to flash roms, its just this whole kernal thing thats got me confused.
BurnAll said:
so just to go over the steps to make sure i dont mess this up,
so i flashed to the origonal versoin with odin
that worked
then i rooted it using CF root
now i got 2 files from philz and i'm not 100% sure what to do with them, i got a .tar what i assume i flash with odin and a .zip i'm not to sure what i do with they are both named philz_touch_5.15.0-jfltecan.tar.md5 and philz_touch_5.15.0-jfltecri.zip
then once i get into recovery i know how to flash roms, its just this whole kernal thing thats got me confused.
Click to expand...
Click to collapse
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz
BurnAll said:
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz
Click to expand...
Click to collapse
READ THIS FIRST:
MAKE SURE YOU DO NOT HAVE THE MF3 FIRMWARE ON YOUR S4. THAT IS THE MOST IMPORTANT THING TO DO RIGHT NOW. IF YOU DO, DO NOT ATTEMPT TO INSTALL A CUSTOM RECOVERY.
You don't have a custom recovery already that's why. Did casual not install TWRP for you? If not try installing Goo Manager from the app market and try installing TWRP that way. MAKE SURE THAT WHEN YOU INSTALL IT, IT SAYS YOUR MODEL NUMBER EXACTLY! I CAN NOT STRESS THIS ENOUGH! When you have TWRP installed, then flash philz with TWRP and you'll have that custom recovery instead.
BurnAll said:
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz
Click to expand...
Click to collapse
do not use the zip you quoted it is not for your phone
use odin flash the tar philz_touch_5.15.0-jfltecan.tar.md5
now you have stock updated MG1 firmware with the latest baseband
root by CF root
Philz Recovery
Now follow the next steps:
1. set up your google account play store etc.
2.next, go into the recovery and do a full nandroid backup -- this gives you a stable base you can restore when needed
3. go flash a custom rom, I highly recommend the latest version of Goldeneye -- updated, well maintained, great developer, clear install instructions
4. try itt then again, use recovery to make a 2nd nandroid, this one of your custom rom install -- try different kernels, every phone is different and someone's favorite kernel just may not like your phone -- doesn't make it a bad kernel just makes it the wrong one for your phone, flash a different one
5. theme if you want -- this is where your recoveries become important as themes are notorious for not always sitting well and all is ok if you have a backup you can return to
6. NEVER flash a baseband from another variant -- stick with your MG1 from your carrier until your carrier updates stock firmware
Can someone please help me get out of this soft brick because I am really stuck. Currently I am getting the error message that "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." but I have done that and it has failed on both mac and windows 7. I have also tried flashing stock build UCUAMDL 4.2.2 firmware via odin 1.7, 1.85 and 3.07 and I have also used the PIT files along with re-partitioning and F. Reset Time. Every single time in odin it has gotten to system.img.ext4 and then failed immediately following. A couple of times I have been able to get into stock recovery mode and it stated an error that the /system partition could not be accessed and I wiped cache/system/data and then tried rebooting and it stayed in the big white galaxy s4 letters and didn't even go to the boot logo. Based on this can anyone help me please???? If there's an existing thread can you please let me know? Thanks!
Which model do you have? What firmware are you on?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
sounds like you wiped your phone when you wiped system/data, why did you do that
you have nothing to boot
kies don't work with iMac
yeah give all the phone info you have, model, build, etc. build may be on your box
i think you can now only flash stock firmware thru Odin to recover, but if you were mf3, you may need to go to bestbuy and see samsung reps to flash phone. don't have any experience at that or using odin
stay on windows pc to do this
may be tomorrow till you get some help from others
good luck
RAID Xero said:
Which model do you have? What firmware are you on?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Sorry I forgot to mention that it's a SGH-I337 as well and I was running the jamal 4.3 AOSP ROM
well then you are with what custom recovery?
and you are not mf3
sounds like the mf3 update was trying to flash. did you not delete the update files with Titanium so the Update would not run
can you boot into recovery and restore a nandroid
---------- Post added 2nd October 2013 at 12:00 AM ---------- Previous post was 1st October 2013 at 11:54 PM ----------
i gotta call it a nite. maybe some west coasters can help since they are 3 hours behind us
but, please don't say you don't have a nandroid--
i think this is fixable--:good:
restoring a nandroid backup could solve your problem, did you try flashing with fastboot instead? When you installed AOSP ROM were you using a toolkit? If so did you flash a temp recovery?
Sent from my Nexus 7 using xda app-developers app
Kelevra_96 said:
restoring a nandroid backup could solve your problem, did you try flashing with fastboot instead? When you installed AOSP ROM were you using a toolkit? If so did you flash a temp recovery?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you have an i337. We don't have fastboot. Our bootloader is locked.
Sent From My SGH-I337 Using Tapatalk 4
What custom recovery are you using?
Sent from my SGH-I337 using XDA Premium HD app
Br4nd3n said:
What custom recovery are you using?
Sent from my SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
I don't have one, although do you think that I can flash a custom recovery with a PIT file because that seems to be the only thing that works. Also I do not have a nandroid backup. Is there somewhere that I can download someone's already made?
adambombz said:
I don't have one, although do you think that I can flash a custom recovery with a PIT file because that seems to be the only thing that works. Also I do not have a nandroid backup. Is there somewhere that I can download someone's already made?
Click to expand...
Click to collapse
It's been asked a couple of times, but do you know what firmware your phone was on? It's important to know to be able to help you.
jd1639 said:
It's been asked a couple of times, but do you know what firmware your phone was on? It's important to know to be able to help you.
Click to expand...
Click to collapse
I was running a custom ROM AOSP 4.3 that's all I know sorry
adambombz said:
I was running a custom ROM AOSP 4.3 that's all I know sorry
Click to expand...
Click to collapse
That's close enough. That means you aren't on mf3.
Edit, have you tried to odin the stock firmware? Never mind I see you have
I would download the stock firmware from sammobile.com and try Odin again on a pc. Either version of odin is ok, 1.85 or 3.07.
When you use Odin only have auto-reboot checked, Don't check re-partition.
also, if you are running a custom rom you have a custom recovery
cwm or twrp?
jd1639 said:
That's close enough. That means you aren't on mf3.
Edit, have you tried to odin the stock firmware? Never mind I see you have
I would download the stock firmware from sammobile.com and try Odin again on a pc. Either version of odin is ok, 1.85 or 3.07.
When you use Odin only have auto-reboot checked, Don't check re-partition.
Click to expand...
Click to collapse
I have tried doing this many, many times and each time it gets to the system.img.ext14 and then fails.
rugmankc said:
also, if you are running a custom rom you have a custom recovery
cwm or twrp?
Click to expand...
Click to collapse
They key word here is that I WAS running a custom recovery when all of this started. It was actually the recovery that started all of this. What happened specifically was I tried to update TWRP via goo manager and whenever I tried to go into recovery it gave me the error that at&t has detected unauthorized software on my phone which I thought was weird because I believe that goo manager auto-lokis. Anyway I tried using other apps to add a custom recovery like ROM manager by clockworkmodz and nothing worked. I then tried to flash TWRP 2.6.3.0 via odin and that's what sent my phone into the state that it's in now. Something that confuses me even more is is that whenever I plug in my phone a battery logo comes up that I don't recognize and then freezes.
adambombz said:
I have tried doing this many, many times and each time it gets to the system.img.ext14 and then fails.
Click to expand...
Click to collapse
Have you re-downloaded the firmware? It could be a bad download. Are you using the .tar.md5 file
When you get it sorted use twrp 2.5.0.2. I think I posted a zip for you.
jd1639 said:
Have you re-downloaded the firmware? It could be a bad download. Are you using the .tar.md5 file
Click to expand...
Click to collapse
Yes I have tried multiple files and builds and I am using .tar.md5
adambombz said:
Yes I have tried multiple files and builds and I am using .tar.md5
Click to expand...
Click to collapse
When you flashed twrp with odin are you sure it was for your device? I think you might have borked your partitions.
jd1639 said:
When you flashed twrp with odin are you sure it was for your device? I think you might have borked your partitions.
Click to expand...
Click to collapse
That is possible, I know what is causing this has something to do with the partitions being messed up since I can't access /system in the stock recovery mode
Hey guys, first post, sorry it had to be a lame one asking for help!
I've been rooting my GS4 I9505 repeatedly over the last year or so and installing new roms and sometimes reverting back to the stock rom when I got bored. I've had no problems so far.
Today I tried to flash a new rom, which failed to install properly. I can now no longer boot into recovery, I can only boot into download mode but I can't flash anything with Odin because it gives me a fail message when I try.
I've done a fairly exhaustive search of the forums in case someone has answered this question before and they have. They suggested flashing the PIT file along with the stock rom. I tried that and Odin still gives me a fail message. I can't find any other solutions online and was wondering if someone here could help.
Thanks!
Hi if you've been rooting for over a year surely you have custom recovery like philz or cwm?
Why not just download pre rooted custom and forget about using Odin?
Is there actually a reason you want to flash a rom via Odin.
OK here's some tips why it's not working
1 you have new bootloader the one with Knox and you are trying to flash a pre Knox rom like 4.2.2.
2 the rom is for a different country.
MY short time with sg4 has educated me never ever ever touch pit files unless you know exactly what you are doing (noobs stay way) hard perminant brick!
Sent from my GT-I9505 using xda app-developers app
ranger4740 said:
Hi if you've been rooting for over a year surely you have custom recovery like philz or cwm?
Why not just download pre rooted custom and forget about using Odin?
Is there actually a reason you want to flash a rom via Odin.
OK here's some tips why it's not working
1 you have new bootloader the one with Knox and you are trying to flash a pre Knox rom like 4.2.2.
2 the rom is for a different country.
MY short time with sg4 has educated me never ever ever touch pit files unless you know exactly what you are doing (noobs stay way) hard perminant brick!
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I wasn't going to use Odin. I only gave it a go when I ran into problems with the phone not being able to load into recovery any more.
Your recovery is damaged
---------- Post added at 09:03 AM ---------- Previous post was at 09:02 AM ----------
Install a new one again with odin
Jellybbz said:
I wasn't going to use Odin. I only gave it a go when I ran into problems with the phone not being able to load into recovery any more.
Click to expand...
Click to collapse
Sounds like you've corrupted your recovery.
If I were in this position I would flash the .Tar version of PhilZ recovery via Odin to get recovery back.
then boot to recovery and flash a custom ROM.
I have the same problem can anyone help ???
Thanks
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.