Related
I was trying to flash my s3 back to 4.1.1. It failed when I was using odin. Now, I get the message Firmware encountered an issue..
I downloaded kies 3 but my phone will not connect to it.
Iv tried many different things and odin keeps failing after a couple lines.
What can I do?
b_rad_1983 said:
I was trying to flash my s3 back to 4.1.1. It failed when I was using odin. Now, I get the message Firmware encountered an issue..
I downloaded kies 3 but my phone will not connect to it.
Iv tried many different things and odin keeps failing after a couple lines.
What can I do?
Click to expand...
Click to collapse
Does your phone still boot? or do you have a Brick?
If it still boots Leave it alone. you can flash any rom you want to as long as there is no bootloader in it.
If you already bricked it, is it a soft brick or hard brick?
theramsey3 said:
Does your phone still boot? or do you have a Brick?
If it still boots Leave it alone. you can flash any rom you want to as long as there is no bootloader in it.
If you already bricked it, is it a soft brick or hard brick?
Click to expand...
Click to collapse
When I insert the battery and power on it has a message saying " firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
above that in the top left it says
odin mode
product name :sgh-1747m
custom binary download: yes (1count)
current binary: samsung official
system status: official
qualcomm secure boot: enable
warranty bit: 0
bootloader rp swrev: 1
This is all it does. I can get into download mode. But everytime I try to flash it says failed.
This is 4.3 touchwiz? or 4.3 custom rom?
If custom, I encountered a similar issue where going back to Odin failed. Trying to turn on the phone and going into recovery mode let "Firmware encountered and issue". I had also encountered the problem of Kies not connecting. It would say "connecting" but nothing would happen.
Can your phone boot in download mode?
If yes, you should be able to recover the firmware with Kies.
You may need to use the previous version of Kies and not Kies 3, as I think Kies 3 is only for 4.3 android touchwiz versions. If you had touchwiz 4.3 from the OTA, you may be stuck as I think people have had problems trying to go back to 4.1.
In Kies go in Firmware Upgrade and Initialisation. You will need to know your phone's model and serial number. They can be found behind the battery.
Follow the steps and you should be able to go back to 4.1.1.
chemicalseb said:
This is 4.3 touchwiz? or 4.3 custom rom?
If custom, I encountered a similar issue where going back to Odin failed. Trying to turn on the phone and going into recovery mode let "Firmware encountered and issue". I had also encountered the problem of Kies not connecting. It would say "connecting" but nothing would happen.
Can your phone boot in download mode?
If yes, you should be able to recover the firmware with Kies.
You may need to use the previous version of Kies and not Kies 3, as I think Kies 3 is only for 4.3 android touchwiz versions. If you had touchwiz 4.3 from the OTA, you may be stuck as I think people have had problems trying to go back to 4.1.
In Kies go in Firmware Upgrade and Initialisation. You will need to know your phone's model and serial number. They can be found behind the battery.
Follow the steps and you should be able to go back to 4.1.1.
Click to expand...
Click to collapse
Its 4.3 touchwiz ota last week.
I will try kies instead of kies 3. With kies 3 it just says connecting, wont connect. When I do the Firmware Upgrade and Initialisation. I type in my model and it just closes.
Im downloading kies right now...
Oh also, I had encountered the closing problem when in Windows.
I was able to not have the random closing problem when using Kies on a Mac.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
b_rad_1983 said:
Its 4.3 touchwiz ota last week.
I will try kies instead of kies 3. With kies 3 it just says connecting, wont connect. When I do the Firmware Upgrade and Initialisation. I type in my model and it just closes.
Im downloading kies right now...
Click to expand...
Click to collapse
Kies has be installed and when I click on tools- Firmware Upgrade...
I type in the model and it says "Please check the model name and enter it". I click ok and it goes back to the main screen, nothing happens.
when i open kies and plug in the phone it says "connecting".... 5mins has passed..same thing..
Hm, yeah it's odd.
I had the same issue with the main screen saying connecting forever, which didn't matter for upgrading the firmware.
Do you have the att version?
I'm assuming you put SGH-I747 for model?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
My fix
I'm not an expert but I had the same problem due to the 4.3 release. You can't go back to an earlier release because the new boot loader is
locked. Nothing worked until I googled and located the exact .pit file and flashed it in Odin. I was rather desperate by then as I had a two day old
phone, lol. Kies doesn't have the newer release so I don't think you can use it. I used cwm mod recovery and flashed to a rooted stock 4.3 rom.
Hope this helps or someone can help more.
chemicalseb said:
Hm, yeah it's odd.
I had the same issue with the main screen saying connecting forever, which didn't matter for upgrading the firmware.
Do you have the att version?
I'm assuming you put SGH-I747 for model?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Rogers
SGH-I747M
Im currently looking for the stock 4.3 rogers file
I cant find what I need as im not 100% sure what im looking for..
im currently downloading
SGH-I747M_RWC_I747MVLDMF1_I747MOYADMF1_Original.zip
b_rad_1983 said:
I cant find what I need as im not 100% sure what im looking for..
im currently downloading
SGH-I747M_RWC_I747MVLDMF1_I747MOYADMF1_Original.zip
Click to expand...
Click to collapse
I reached the download limit..cant download it
Which Odin are you using? If you arent using it try Odin 3.09.
theramsey3 said:
Which Odin are you using? If you arent using it try Odin 3.09.
Click to expand...
Click to collapse
3.07 is what i used.
b_rad_1983 said:
3.07 is what i used.
Click to expand...
Click to collapse
I just thought about it you have to go back with the 4.3 because if you do succesfully flash anything older you will Hard brick your phone, right now you should be able to recover with the 4.3 odin file.
theramsey3 said:
I just thought about it you have to go back with the 4.3 because if you do succesfully flash anything older you will Hard brick your phone, right now you should be able to recover with the 4.3 odin file.
Click to expand...
Click to collapse
Where can i get the 4.3 odin file?
Check sammobile.com
b_rad_1983 said:
Where can i get the 4.3 odin file?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/
You have to register for their site to be able to download. in the search bar about 1/3 page down on right type in SGH-I747M then find your carrier and download the appropriate file.
After that if you still dont like 4.3 you can flash whatever rom you want in CWM or TWRP or atleast thats whats been rumored. I have no clue I like 4.3 and havent had any issues with the rom I had a hard brick that I caused and recovered.
so I rooted my galaxy note 2 from Sprint with Odin and it said that it was rooted but the superuser would never work so I did a factory reset to make sure that wasn't the problem and it just got stuck on boot loader on the Samsung icon and it never turns on I tried installing the stock firmware for the Sprint Samsung Galaxy Note 2 with Odin and every time I got to S.boot it says fail my phone has been stuck like this for about a week now and I have not found anything to fix it I found a thread saying to install an alternate stock firmware without the s.boot file but it was only for Verizon phones I have not found one for the Sprint any help would be highly appreciated
thenewmessiah said:
so I rooted my galaxy note 2 from Sprint with Odin and it said that it was rooted but the superuser would never work so I did a factory reset to make sure that wasn't the problem and it just got stuck on boot loader on the Samsung icon and it never turns on I tried installing the stock firmware for the Sprint Samsung Galaxy Note 2 with Odin and every time I got to S.boot it says fail my phone has been stuck like this for about a week now and I have not found anything to fix it I found a thread saying to install an alternate stock firmware without the s.boot file but it was only for Verizon phones I have not found one for the Sprint any help would be highly appreciated
Click to expand...
Click to collapse
What file were you using?
Without more info I would suggest using odin and flashing a recovery then flashing mc2 stock with counter reset. Dont remember exactly who made it at this moment but scan through development section and you will find it.
Sent from my SPH-L900 using XDA Premium 4 mobile app
It's failing at sboot because you're trying to downgrade on a secured bootloader. You can't downgrade. You can only use the latest stock firmware.
This is the stock 4.3 image for use in Odin http://www.mediafire.com/download/7viivd985s7cp8l/L900VPUBMK4_L900SPTBMK4_HOME.tar.zip
To get into download mode use vol down, home, power. You'll need Odin 3.07 or 3.09. Put this in the PDA or AP tab. DO NOT MESS WITH ANYTHING ELSE IN ODIN.
Sent from my SPH-L900. Please hit the thanks button if I helped you out!
SPH-L900
i will try this when i get home and ill let you know how it goes one thing i forgot to mention when i try to turn on my phone it says i need to connect it to kies and it is no longer stuck on the samsung logo i had tried installing the software and thats what happened hopefully that doesnt matter but i will try to flash the 4.3. i dont know why i never thought of that hopefully it works out well.
Thank you ecs87 this worked like a charm I was frustrating for 2 1/2 weeks lol thank you very much
thenewmessiah said:
so I rooted my galaxy note 2 from Sprint with Odin and it said that it was rooted but the superuser would never work so I did a factory reset to make sure that wasn't the problem and it just got stuck on boot loader on the Samsung icon and it never turns on I tried installing the stock firmware for the Sprint Samsung Galaxy Note 2 with Odin and every time I got to S.boot it says fail my phone has been stuck like this for about a week now and I have not found anything to fix it I found a thread saying to install an alternate stock firmware without the s.boot file but it was only for Verizon phones I have not found one for the Sprint any help would be highly appreciated
Click to expand...
Click to collapse
I know exactly what you need to do, go download this and flash with odin, then flash a custom recovery and flash MC back to stock unrooted
http://forum.xda-developers.com/showthread.php?t=2541324
ecs87 said:
It's failing at sboot because you're trying to downgrade on a secured bootloader. You can't downgrade. You can only use the latest stock firmware.
This is the stock 4.3 image for use in Odin http://www.mediafire.com/download/7viivd985s7cp8l/L900VPUBMK4_L900SPTBMK4_HOME.tar.zip
To get into download mode use vol down, home, power. You'll need Odin 3.07 or 3.09. Put this in the PDA or AP tab. DO NOT MESS WITH ANYTHING ELSE IN ODIN.
Sent from my SPH-L900. Please hit the thanks button if I helped you out!
Click to expand...
Click to collapse
you saved my A$$ thxs
So, i decide to root my s3 because i wanted to do some cool stuff. I got odin, got the tar file and tried flashing it. For some reason it didn't work :crying: On odin it gave me a fail. I was in download mode too. So, when i turn on my s3 it is in odin mode but it says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." i did this in kies and when it was at like 99% it gives me an error. :crying:
so i tried flashing again in odin still fail, but i get on my s3 SV REV CHECK FAIL: Fused 2 > Binary 0. I have no clue what that means, So, i just want my phone to get working again i dont care about rooting anymore. JUST HELP ME FIX IT!!!!:crying:
BTW: I di root my Kindle Fire a while back so i thought I would have experience with this (i kind of do) but i guess I thought wrong.
Was your phone running a stock 4.3 AT&T ROM? What method did you use to try and root the phone?
audit13 said:
Was your phone running a stock 4.3 AT&T ROM? What method did you use to try and root the phone?
Click to expand...
Click to collapse
i think so and i tired using odin and i put the phone in download mode so i could flash the .tar file
Resistance225 said:
i think so and i tired using odin and i put the phone in download mode so i could flash the .tar file
Click to expand...
Click to collapse
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
audit13 said:
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
Click to expand...
Click to collapse
I will try to do this! Thanks for helping me though, i will keep you updated. :fingers-crossed:
audit13 said:
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
Click to expand...
Click to collapse
I installed a recovery and guess what, it started working again! All my data was still there too! Thanks i really appreciate you taking the time to help me! I also was able to succsessfully root it by using the CF auto root .tar file. Once again, thanks a ton!
Resistance225 said:
I installed a recovery and guess what, it started working again! All my data was still there too! Thanks i really appreciate you taking the time to help me! I also was able to succsessfully root it by using the CF auto root .tar file. Once again, thanks a ton!
Click to expand...
Click to collapse
Glad you got it working. We're all here to help.
Okayy ive searched around and looked through ALL the threads and guides on rooting this phone and even followed some but im still stuck. Yes ive read and searched before asking so now im asking, is there any thorough guide or youtube vid maybe that shows how to properly apply full root to the T999N version of the galaxy s3 on metropcs? Im updated to 4.3 btw. Please no sarcasm/smart remarks
Did you try Root66 4.3 version ?
Best if you can flash a Custom Recovery via Odin and then flash SuperSU package through that Recovery.
Perseus71 said:
Did you try Root66 4.3 version ?
Best if you can flash a Custom Recovery via Odin and then flash SuperSU package through that Recovery.
Click to expand...
Click to collapse
Ive tried to flash the recovery through odin but even though the box says PASS and reboots my phone, when i go into recovery mode it takes me to stock android recovery. I need help
Make sure that Recovery is compatible with your phone. Second post the complete odin log for that process.
I have it rooted now, just have to figure out a way to update twrp without removing root
Perseus71 said:
Make sure that Recovery is compatible with your phone. Second post the complete odin log for that process.
Click to expand...
Click to collapse
I have it rooted now, just have to figure out a way to update twrp without removing root
Take least TWRP and Flash via Odin.
Where can I find the MK7 kernel, that's the only way I can get wifi to work.
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks
And here we go again...... What version software was installed before trying to update? Were you rooted?
zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Flash whatever firmware u was on in odin
zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.
tried to do thru sd card ,but i get :
dm-verity verification failed
can i just go back to 5.1 lollipop with an official stock rom via odin ?
zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom
any firmware can get me back to lollipop with odin !!!
zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk
i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip