Related
I have soft-bricked my GS3 - SGH-i747M.
I can still get into the Galaxy S3 Download Mode screen (Pressing VOLUME Down + HOME + POWER button), and am running ODIN3 v3.07.
But I have not been able to restore my backed ROM, nor a couple of "stock" ROMs that I have downloaded.
I ran into trouble trying to get the proper ClockwordMod installed.
Any suggestions would be appreciated. Thanks
Start from scratch. Load a image using Odin and re do it all. Root etc
Sent from my Samsung Galaxy S3
when i soft bricked my phone i just followed this thread and reflashed the stock rooted rom. This method of rooting involves flashing a stock rom with root injected into it so in essence you are just flashing back to stock. No need to wipe data before doing this process (at least in my experience)
The thread also includes the steps to get clockworkmod
success
that got it Florad, thanks much
*HELP* Friend Soft Bricked my phone
Let my self proclaimed tech savy friend borrow my phone for a few days... He decides to root it for me in thanks.
Now, all it is able to do is access the Download Function. No Recovery, instead I get a message saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Kies will not recognize the phone and connect. On boot it shows the SAMSUNG logo and shuts off. Sometimes on boot it just shows an empty battery. LED no longer comes on...
It is a Samsung gs3 sgh-i747m from the MTS Allstream carrier.
I have searched forum after forum to find what to do. Downloaded every Firmware rom from a Canadian provider (except MTS 'cause there just isn't any out there with valid links), tried to flash with Odin3 v3.07 .... no luck. Everything fails.
Phones are not really my language. From what I get he was trying to root:
RecoveryGalaxyS3USCanada.tar
SuperUser.zip
which worked but SuperSU kept crashing so he tired:
Siyah-s3-v1.9.1.tar
which caused the crash. since then I can only imagine what other things he tried in attempts of recovery before giving it back to me to figure out.
As for the few Roms (This one being Telus) I have attempted in hopes to reverse it, this has always been the result in Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I747MVLALE8_I747MOYBALE8_20120523.225040_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Any help would be greatly appreciated.
Did you install latest 4.3 firmware. Do you have a line that says Knox in download mode.?
SaHiLzZ said:
Did you install latest 4.3 firmware. Do you have a line that says Knox in download mode.?
Click to expand...
Click to collapse
There is nothing saying anything about Knox
Odin Mode
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: YES (15 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWERV: 1
SECURE CHECK FAIL: aboot
As for the latest firmware, Im not exactly sure what I am looking for or where to get it. Like I said, not my language.
Wow 15 counts.. awesome!
S it looks like it was on 4.3 at some point of time.
1. You will need to pick a carrier file from here, http://forum.xda-developers.com/showthread.php?t=2543854 , and download it (really slow downloads) and use ODIN to install it.
OR
2. Follow this thread here, it is for Note 2, but same idea applies to your S3 for Emergency firmware recovery: http://forum.xda-developers.com/showthread.php?t=2261153
Good luck and post back, I will suggest #2 as it is not your language..
help v.v
first, im new here and don't know much on how things work, so im sorry if ive caused problems posting this. i rooted my galaxy i747. didn't install clockwork like an idiot and tried to put siyah firmware on my phone. when Odin tried to reboot my phone my phone just shut off and Odin said <something> Removed! except with numbers where i put something. since then ive tried to put normal fiemwares back on and nothing has worked. i even tried the method here http://forum.xda-developers.com/showthread.php?t=1739426 and that just failed or froze every time. i don't know what to do. i can try to start my phone. the Samsung white letters pop up then vanish and nothing. sometimes it will get to the galaxy s 3 screen then blackness. im stressed and have been trying to fix this for two days and really need help :crying: :crying:
anyone who can help will be greatly appreciated!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
formulaF said:
first, im new here and don't know much on how things work, so im sorry if ive caused problems posting this. i rooted my galaxy i747. didn't install clockwork like an idiot and tried to put siyah firmware on my phone. when Odin tried to reboot my phone my phone just shut off and Odin said <something> Removed! except with numbers where i put something. since then ive tried to put normal fiemwares back on and nothing has worked. i even tried the method here http://forum.xda-developers.com/showthread.php?t=1739426 and that just failed or froze every time. i don't know what to do. i can try to start my phone. the Samsung white letters pop up then vanish and nothing. sometimes it will get to the galaxy s 3 screen then blackness. im stressed and have been trying to fix this for two days and really need help :crying: :crying:
anyone who can help will be greatly appreciated!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
What bootloader was on your phone before flashing? Can you get into download mode?
So this problem just started today and came out of no where without any precursors. Worse thing is away from home working in the middle of nowhere in New Mexico without any real Tmo stores in the 5 hour vicinity.
My phone pretty much vibrates and turns on when battery is put in. Sometimes it will boot up, sometimes it wont. And when it does boot up, it will easily shut off or stay on for 10 minutes at the most.Tried a few other batts, but same thing. i even reflashed frosty rom and same thing.
I called tmo and they're working on sending me a phone as it is apparent that its a hardware issue- however it won't help my dependence on this phone as it I rely on it for work and daily duties.
I'm rooted via samsung toolkit and running frosty JB. I completely forgot how to revert back to stock as I am also using custom recovery from toolkit. Any direction? Also, will Tmo care if I leave the flashcounter untouched?
Yes they care if the flash counter is touched . use the search button or Google how to revert back to stock with 0 flash counter ..
Sent from my SGH-T999 using xda premium
can i just triangle away -> reflash stock recover thru odin via toolkit -> flash stock boot image via toolkit ....and done?
liberalswine said:
can i just triangle away -> reflash stock recover thru odin via toolkit -> flash stock boot image via toolkit ....and done?
Click to expand...
Click to collapse
heres the tutorial http://forum.xda-developers.com/showthread.php?t=2136921
ok why not go back to nandroid? its not a hardware issue there must be some kind of bugs
re: step by step info.
liberalswine said:
So this problem just started today and came out of no where without any precursors. Worse thing is away from home working in the middle of nowhere in New Mexico without any real Tmo stores in the 5 hour vicinity.
My phone pretty much vibrates and turns on when battery is put in. Sometimes it will boot up, sometimes it wont. And when it does boot up, it will easily shut off or stay on for 10 minutes at the most.Tried a few other batts, but same thing. i even reflashed frosty rom and same thing.
I called tmo and they're working on sending me a phone as it is apparent that its a hardware issue- however it won't help my dependence on this phone as it I rely on it for work and daily duties.
I'm rooted via samsung toolkit and running frosty JB. I completely forgot how to revert back to stock as I am also using custom recovery from toolkit. Any direction? Also, will Tmo care if I leave the flashcounter untouched?
Click to expand...
Click to collapse
If you can get the phone into download mode here is a sure fix for it, if you have a windows computer handy you
will need to use that OR you can go to the play store and download "mobile odin" and flash the stock rooted T999
rom without the need for any computers at all.
This guide will get your phone back up and running properly, doing anything else will just prolong your problem.
Easy and sure way to fix error 7 and other issues or problems - Here is the step by step guide:
After doing this you will end up with a stock-pre-rooted T999 Tmobile Touchwiz 4.1.2 rom which works properly.
You will not loose any of your pictures, videos or music by doing this.
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: http://d-h.st/Q14
Download ODIN which is required for flashing the stock rooted firmware (a windows app)
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
umm, well i was able to setup and root the new phone that came in.
However, i'm having issues loading the stock .tar file I downloaded through Odin and receive this message:
<OSM> All threads completed. (succeed 0 / failed 0)
I also was unable to flash stock recovery file via odin and received the same message. Any thoughts?
re: Odin flash
liberalswine said:
umm, well i was able to setup and root the new phone that came in.
However, i'm having issues loading the stock .tar file I downloaded through Odin and receive this message:
<OSM> All threads completed. (succeed 0 / failed 0)
I also was unable to flash stock recovery file via odin and received the same message. Any thoughts?
Click to expand...
Click to collapse
There are a lot of people who don't have a tmobile T999 phone but instead they have a I9300 I hope you are not one of those people.
Everything found here in this thread pertains to the T999 Tmobile S3 phones. (sorry about having to make this comment but I just had to)
Forget about flashing stock recovery file with ODIN that was not part of the step by step instructions.
Only follow the step by step or things may get more complicated.
Did the [COM:XX] light up green or yellow in Odin after you plugged it into the usb of the computer before you started the flash?
BE SURE YOUR PHONE IS A Galaxy S3 Tmobile T999 (or you might end up with a shiny brick).
Unplug the usb cable from the phone before anything else and do NOT change any of the default settings in Odin.
#1: Open Odin
#2: Put the TAR file into the PDA slot in Odin
#3: Put the phone into download mode
#4: Connect the usb cable from computer to the phone
#5: Be sure that the [COM:XX] lights up in Odin
#6: Start the flash and have patience it may take up to 10 minutes
Good luck!
I was able to get it connected after trying out several different USB ports as the main culprit. But now Odin has been stuck for an hour and a half...
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
I'm not sure if I should let it sit longer. It has been exactly one hour, 32 minutes. What to do...?
re: try this.
liberalswine said:
I was able to get it connected after trying out several different USB ports as the main culprit. But now Odin has been stuck for an hour and a half...
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
I'm not sure if I should let it sit longer. It has been exactly one hour, 32 minutes. What to do...?
Click to expand...
Click to collapse
It should not take any more than at most 10 minutes. No need to let it sit there not doing anything.
Perhaps the TAR file got corrupted during the extraction or perhaps for whatever reason the
actual download of the rom got corrupted during downloading.
If I were you I would re-download the T999 stock rooted rom again and start all over, be sure you delete the
download which you first downloaded as to not make a mistake and use the first download.
Be sure that your battery is charged, if the battery is too low it may not want to continue the Odin flash.
So turn off the phone and plug it into the WALL charger it will charge 20% faster than usb, let it charge
for at least 45 minutes before trying to flash again.
Good luck.
i'm trying once more. The download file seems legit. =/
You can also find the firmware and a lot of info in my thread. Link in sig.
Do you have kies installed? If so get rid of it. It screws with Odin.
Sent from my SGH-T999 using xda premium
Currently stuck in this process:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDLJC_T999TMBDLJC_T999UVDLJC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
its been about 12 minutes
It's been over 30 minutes again and this is beginning to frustrate me. Everything looks good, but Odin just seems unresponsive and doesn't get anywhere past the firmware installation. I've tried two different stock firmware downloads. One directly from the tutorial previously listed, and one updated through samsung toolkit. Not sure what's going on and I need to return this phone back to Tmo
That sounds like a problem a lot of people have when kies is installed. If you don't have it installed you may want to try reinstalling the latest usb drivers. Ill post the link in a few mins.
For now though, be patient and see if it fails out. Avoid interrupting the process unless absolutely necessary.
Sent from my SGH-T999 using xda premium
Just uninstalled kies though I'm not quite sure if it's culprit here. Re attempting, i hope this works otherwise I'm out of options to getting my phone back to stock in time.
Does any one know if tmo/samsung really checks the phone once my "defected" unit is sent back?
liberalswine said:
Just uninstalled kies though I'm not quite sure if it's culprit here. Re attempting, i hope this works otherwise I'm out of options to getting my phone back to stock in time.
Does any one know if tmo/samsung really checks the phone once my "defected" unit is sent back?
Click to expand...
Click to collapse
Kies also contains the USB drivers, so you will probably need to reload those.
Here is the link to my drivers folder. Latest version I have is 1.5.23.0.
http://androidfilehost.com/?a=show&w=files&flid=1368
re: Odin flash.
DocHoliday77 said:
Kies also contains the USB drivers, so you will probably need to reload those.
Here is the link to my drivers folder. Latest version I have is 1.5.23.0.
http://androidfilehost.com/?a=show&w=files&flid=1368
Click to expand...
Click to collapse
About 5-6 or so posts ago I told liberalswine to uninstall kies, reboot computer and I gave him the official samsung
link for the proper usb drivers, I am not sure if he already uninstalled kies and & installed the samsung usb drivers
and if he rebooted the computer one more time before trying to odin flash the stock-rooted T999 4.1.2 firmware.
It's really strange that he is having so much trouble flashing the firmware with Odin
unless the actual TAR file is corrupted in one way or another.
I already told him to re-download the firmware and try the odin flash again a couple hours ago.
Just thought to let you know.
re: don't understand the question
richadorsey4 said:
Do we need to uninstall the stock app to flash this
Click to expand...
Click to collapse
I would like to give you a informed answer, but your question lacks any specifics,
I just don't know exactly what you mean or are talking about, looking back at some
previous posts here I see nothing that pertains to uninstalling any apps.
Try to ask your questions with a lot more details so we can know what exactly are asking about.
Misterjunky said:
About 5-6 or so posts ago I told liberalswine to uninstall kies, reboot computer and I gave him the official samsung
link for the proper usb drivers, I am not sure if he already uninstalled kies and & installed the samsung usb drivers
and if he rebooted the computer one more time before trying to odin flash the stock-rooted T999 4.1.2 firmware.
It's really strange that he is having so much trouble flashing the firmware with Odin
unless the actual TAR file is corrupted in one way or another.
I already told him to re-download the firmware and try the odin flash again a couple hours ago.
Just thought to let you know.
Click to expand...
Click to collapse
Any official FW will have an md5sum that Odin will check. If using anything else its wise to always check the md5 on dev-host or AFH and make sure what you download matches.
As for drivers, Sammy doesnt release the usb drivers as a standalone install, only with kies. Never found them anyway. Also forgot to mention, that link you posted is bad, so you may want to recheck it.
Sent from my SGH-T999 using xda premium
I just cannot believe this happened.
After all the drama with the Sony Z2, my brand new Galaxy Tab S 10.5 died on me.
This morning it woke me up, I unplugged it from the charger, put it in my bag and went to work.
After some time I wanted to check my messages, but I was looking at big SAMSUNG logo.
I restarted it with Power key + Volume Down. It gets past the Samsung Galaxy Tab S logo and gets stuck at the SAMSUNG logo.
I can get into Download Mode (Power key + Volume Down + Home key) but I cannot get into recovery (Power key + Volume Up + Home key) this combination of buttons gets me stuck at the Samsung Galaxy Tab S logo.
Any advice?
BUMP
I've tried Kies, but no luck.
It downloads the firmware after I enter my serial number, but then it stays at 0% and nothing happens.
Is there any way I can reset it with Odin, but keep my warranty, because I will return it tomorrow... but my account and data is on it.
I hope it will be unaccessible...
No help for me?
Download your device firmware from sammobile. Its has to be your exact model. Once its downloaded extract it to your desktop and open up odin. Go into download mode, and plug the tab s into your pc. Now in odin click the ap or pda tab and pick the extracted firmware. Then just hit start and it will flash. It shouldnt viod warrenty. Your gonna take it back anyway? If so tell them to reset everything so it doesnt have your info on it.
Thank you for your response, but no luck for me...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T805XXU1ANG1_T805VFG1ANG2_T805XXU1ANF7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
I just hope they can delete everything
And I'm giving up on buying a new tablet.
This is insane.
dhalan said:
Thank you for your response, but no luck for me...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T805XXU1ANG1_T805VFG1ANG2_T805XXU1ANF7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
I just hope they can delete everything
And I'm giving up on buying a new tablet.
This is insane.
Click to expand...
Click to collapse
The firmware has to be from your country. Personally I never use odin to flash anything. I use twrp recovery. Anyway this could be a pit problem or a country firmware lock. Sometimes I hate odin lol
That's the firmware Kies downloaded after the serial no. input.
I tried different versions of Samsung USB drivers and different version of Odin, but nothing works.
Time is running out, I have to return the device...
dhalan said:
That's the firmware Kies downloaded after the serial no. input.
I tried different versions of Samsung USB drivers and different version of Odin, but nothing works.
Time is running out, I have to return the device...
Click to expand...
Click to collapse
Solved? i have same problem. I need help.
Tiago Antunes said:
Solved? i have same problem. I need help.
Click to expand...
Click to collapse
Can you get into stock recovery? If not flash the stock recovery for your device then wipe the cache.
DUHAsianSKILLZ said:
The firmware has to be from your country. Personally I never use odin to flash anything. I use twrp recovery. Anyway this could be a pit problem or a country firmware lock. Sometimes I hate odin lol
Click to expand...
Click to collapse
thanks. solved.:laugh:
Have same problem
I have same problem after installing miracast enabler and activated 2nd option. It get stuck on Samsung logo and can't go to recovery or anything else. Tablet is rooted with CF-ROOT and even PC dun detect it.
Any ideas ?
Thx
Flash twrp and then do a factory reset. Press and hold Power + Vol down + Home. As soon as it restarts keep holding Power + Home but hold Vol up instead.
This will boot into recovery.
grA$ said:
I have same problem after installing miracast enabler and activated 2nd option. It get stuck on Samsung logo and can't go to recovery or anything else. Tablet is rooted with CF-ROOT and even PC dun detect it.
Any ideas ?
Thx
Click to expand...
Click to collapse
IInstaller original firmware for you country.
grA$ said:
I have same problem after installing miracast enabler and activated 2nd option. It get stuck on Samsung logo and can't go to recovery or anything else. Tablet is rooted with CF-ROOT and even PC dun detect it.
Any ideas ?
Thx
Click to expand...
Click to collapse
I am stuck on the logo as well.... Can somebodi help?
svetlio89 said:
I am stuck on the logo as well.... Can somebodi help?
Click to expand...
Click to collapse
Nothing is stopping you from going into recovery. It's highly unlikely you have lost it.
Press the right combination of buttons at the right time and you will enter recovery.
Power + Vol down + Home then when the screen goes blank change to Vol up while still holding the other 2 buttons. Hold until recovery boots
Thanks! This worked
I received OTA Update from 4.4.4 to 5.0.2
But I rooted My device and replaced recovery partition
I think if Apply ota update my device will break ! ( Because of loosing stock recovery )
Can anyone Uploade stock recovery for T805
rasoooli said:
I received OTA Update from 4.4.4 to 5.0.2
But I rooted My device and replaced recovery partition
I think if Apply ota update my device will break ! ( Because of loosing stock recovery )
Can anyone Uploade stock recovery for T805
Click to expand...
Click to collapse
The update will replace the recovery with stock. It won't brick your device.
T805 won't boot after a TWRP advanced wipe
Dear friends,
Today I have met an error saying me that "Emergency service has stopped" and this message continued to reappear after every boot.
So I have choosen to do a wipe. I have installed TWRP recovery, after that I did an advanced wipe selecting all but ext-sd checkbox.
After that wipe my device stuck on galaxy tab logo and won't boot, neither I have been able to enter recovery mode.
So, I have used Odin to install twrp again, and now I am able to enter in recovery mode, but when I restart the device it won't exit from boot logo.
Why it cannot boot?
What can I do?
Thanks guys!
It won't boot now you've wiped everything. You need to reinstall the stock Rom.
ashyx said:
It won't boot now you've wiped everything. You need to reinstall the stock Rom.
Click to expand...
Click to collapse
Thank you ashyx!
What options have deleted what we do not have to delete to do a factory reset?
And yes, I'm downloading the firmware, but it will take almost 10 hours!
Rapidgator free is very slow!
Do you know any faster resource? Version is T805XXU1BOD2
Cheers
About a week ago, I updated my CyanodgenMod 12.1 rom and, suddenly, my note began acting nuts!
It started to freeze and randomly shut down with no warning. I wouldn't be able to power it back on immediately either. I'd have to remove the battery and wait at least 30 seconds before putting it back in and starting it.
I tried downgrading to back to the previous version but, it continued to do same thing even on the previous one.
I used Odin to go back to latest Touchwiz stock firmware and the firmware did it too. I've tried almost everything and now whenever I try use Odin to go back to the previous firmware before 5.1.1 December, Odin fails and gives me this message:
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My bootloader says this:
UDC Start
sw REV Check Fail: [aboot] Fused 4 > Binary 3
[1] eMMc write fail: aboot
Any suggestions on what to do or what's wrong?
greyhoshi said:
About a week ago, I updated my CyanodgenMod 12.1 rom and, suddenly, my note began acting nuts!
It started to freeze and randomly shut down with no warning. I wouldn't be able to power it back on immediately either. I'd have to remove the battery and wait at least 30 seconds before putting it back in and starting it.
I tried downgrading to back to the previous version but, it continued to do same thing even on the previous one.
I used Odin to go back to latest Touchwiz stock firmware and the firmware did it too. I've tried almost everything and now whenever I try use Odin to go back to the previous firmware before 5.1.1 December, Odin fails and gives me this message:
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My bootloader says this:
UDC Start
sw REV Check Fail: [aboot] Fused 4 > Binary 3
[1] eMMc write fail: aboot
Any suggestions on what to do or what's wrong?
Click to expand...
Click to collapse
You're trying to go back to a firmware your phone dosen't support anymore. Try OG5 or the latest OK1
Sent from my SM-N910P using XDA Free mobile app
arielovin said:
You're trying to go back to a firmware your phone dosen't support anymore. Try OG5 or the latest OK1
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
My phone is still acting ridiculous. It keeps shutting down randomly and I can't restart it without removing the battery first and waiting at least 30 seconds before I put it back in.
I have no idea what to do.
greyhoshi said:
My phone is still acting ridiculous. It keeps shutting down randomly and I can't restart it without removing the battery first and waiting at least 30 seconds before I put it back in.
I have no idea what to do.
Click to expand...
Click to collapse
" My phone is still acting ridiculous. It keeps shutting down randomly and I can't restart it without removing the battery first and waiting at least 30 seconds before I put it back in. " hey, greyhoshi, is your phone still doing this?... and if not, what did you do to fix it?...
It's still doing it but, not as frequently. I think it's something with the kernal.
Was anyone able to help you out? My Note 4 has been doing this for a few month and I haven't been able to find a fix for it.
I'm still in the same boat. Sorry.
My note 4 started doing this a couple weeks ago too... after everything was working fine with my emotion kernal for 6+ months. Issues started with no apparent change to my phone. What kernal were you guys using?
I'm pretty sure this is a hardware issue. My phone is also doing this, and its getting worse. I have to pull the battery, sometimes multiple times and wait anywhere from 30 seconds to 30 minutes to get to start. Then once it starts, it will sometime hang on the first screen and or sometimes on the sprint screen with a blue light flashing.
I had been on a rooted rom and I went back to Stock and still have the problems.
Same exact issue. Wtf?
Battery fails at 9-12 months. Now hardware failures at 12-18?
The Anker 2x + wall charger fixes the battery problem but I'd be very curious to know if anybody can find a solution for the ridiculous freezes and random reboots. I even got stuck in a boot loop earlier between "Samsung Note 4 + Sprint Spark"
I have the exact same problem with my T-Mobile version. Been running stock non rooted since November with no issues now it's doing the exact same thing as described. Even a factory reset doesn't make it go away. I'm selling this phone as is for parts on eBay and am done with Samsung. Wish i had a warranty on mine.
http://forum.xda-developers.com/note-4-tmobile/help/whats-wrong-note-4-slowdowns-galore-t3317254
The exact same thing happened to my wife's N4, Friday. I finally gave up trying to fix it, and took it to a Sprint store. The technician knew less than I did, and couldn't fix it either. They ordered me a new N4.
Sent from my SM-N920P using Tapatalk
Same problem here. While im listening to music the phone runs fine. As soon is i turn off the music the screen turns off it freezes sometimes reboots in to download mode.
Sent from my SM-N910P using JellyBombed Tapatalk 2
cushgrunt said:
Same problem here. While im listening to music the phone runs fine. As soon is i turn off the music the screen turns off it freezes sometimes reboots in to download mode.
Sent from my SM-N910P using JellyBombed Tapatalk 2
Click to expand...
Click to collapse
I think "mmc_read failed" is probably the main evidence of the start of hardware failure.
Sent from my SM-N920P using Tapatalk
If it is that sucks because my phone is out of warranty. Has anyone tried to pull and Odin the PIT file to see if the partition is corruppted. I cant find it for my phone
Sent from my SM-N910P using JellyBombed Tapatalk 2
Brand new? Is it still under warranty? Insurance? I think the usually give a refurbished unit.
Sent from my SM-N910P using XDA Free mobile app
cushgrunt said:
If it is that sucks because my phone is out of warranty. Has anyone tried to pull and Odin the PIT file to see if the partition is corruppted. I cant find it for my phone
Sent from my SM-N910P using JellyBombed Tapatalk 2
Click to expand...
Click to collapse
Do you have insurance on it, from sprint?
Sent from my SM-N920P using Tapatalk
I have never carried any insurance on my phones ive been lucky untill this week ive had it for 1y and 3 months
Sent from my SM-N910P using JellyBombed Tapatalk 2
I do. The question is whether you get a brand new unit or refurb
Sent from my SM-N910P using XDA Free mobile app
cuteman said:
I do. The question is whether you get a brand new unit or refurb
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
I'm getting a brand new, not refurbished N4
Sent from my SM-N920P using Tapatalk
Hi all,
I already searched here and found no solution of my problem. I hope you could help me out.
- I have my Note II for 3 years and it never had any problem until today, when it rebooted by itself and now stuck at "Galaxy Note II" screen. I have tried all of the following:
1) Removed battery, retry many many times, same thing
2) Try to put it in recovery mode by VOL_UP+HOME+POWER, the same "Galaxy Note II" showed up and nothing further
3) I was able to put it in download mode but that didn't help
4) I tried different battery, same thing
5) when I plugged in the USB charger, the battery icon showed up with no battery level and only a circle on top of it.
Please advise what I should do next? My Note II was running stock firmware 4.1.2 and rooted. No CWM. It's a T-Mobile (model SGH-T889) if that makes any difference.
THank you very much in advance!
Mike
Did you try reflashing a stock rom?
Btw, T-Mobile note 2 forum is here: http://forum.xda-developers.com/note-2-tmobile
No I haven't tried. Will reflashing stock firmware remove all my data?
Thank you!
Sent from my SM-T230NU using Tapatalk
It's kind of dangerous to reflash the firmware now that the battery level is not known and it's not charging.
Sent from my SM-T230NU using Tapatalk
Ok, I tried almost everything in xda and I just could not get into recovery. It always stuck at the "Galaxy Note II" logo.
At this point, I'm willing to try anything, I have nothing to lose, right?
Things I already tried:
- Reflash OEM firmware with ODIN (from Sammobile, different version from 4.1.2 to 4.3)
- Flash TWRP
- Restore firmware with Kies
ODIN always said PASS. When rebooted, it just stuck on logo and I could not put it in RECOVERY using VOL-UP+HOME+POWER. Putting it in DOWNLOAD is fine.
Any suggestions? Anything at all?
Thank you!!!
mike-
PS: It's not carrier specific so I'm putting it here to solicit more inputs. Thanks.
When the phone powers on, which code runs first? I would assume the 'bootloader'? Then it tries to load the kernel.
When we press VOL-UP+HOME+POWER, the RECOVERY code runs. Yes? The flashing of stock firmware would restore this RECOVERY code but I could not put it in RECOVERY.
When we press VOL-DOWN+HOME+POWER, the download mode is run. Where is the download mode code?
What happens when you try to reboot to recovery? You let the power button go when the phone powers up but keep holding down home and volume up?
audit13 said:
What happens when you try to reboot to recovery? You let the power button go when the phone powers up but keep holding down home and volume up?
Click to expand...
Click to collapse
When I pressed VOL_UP+HOME+POWER, the logo "Galaxy Note II" came up. I released the POWER button while keeping VOL_UP+HOME. The logo stayed there forever.
Believe me, I have tried almost everything several times
I try to understand what happened (I'm an embedded software engineer but in a totally different discipline).
- The RECOVERY code is in a different partition/section of the ROM, yes? Same as DOWNLOAD code is in a different partition, I assume? because I could go into DOWNLOAD mode with VOL_DOWN+HOME+POWER just fine. Does it mean that the RECOVERY code was corrupted? But it doesn't make sense, because by reflashing the stock firmware, the recovery code was replaced, together with the bootloader and OS, yes?
I reflashed many times and nothing was changed. I could never go into RECOVERY and it always stuck at the logo.
- I reflashed TWRP too but I could not go into RECOVERY after flashing with ODIN.
- What exactly is the boot sequence when power is ON? I would assume the bootloader got executed, then it tried to initialize the hardware, then loads the kernel from the flash.
Any other suggestions? Again, I already tried all the "normal" recovery stuffs without success...
Thank you!
mike-
Tried flashing stock rom with a pit file? If this doesn't work, a jtag fix may be required.
Boot sequence sounds right but I am not a software or hardware engineer.
audit13 said:
What happens when you try to reboot to recovery? You let the power button go when the phone powers up but keep holding down home and volume up?
Click to expand...
Click to collapse
audit13 said:
Tried flashing stock rom with a pit file? If this doesn't work, a jtag fix may be required.
Boot sequence sounds right but I am not a software or hardware engineer.
Click to expand...
Click to collapse
ODIN reported no error when fetching PIT file though...
I briefly looked at the JTAG patch and if all ever fails and I have no more suggestions, I may go there
I searched here on XDA and google and it seems this is a pretty common problem and there was no real solution. Everyone said to go into RECOVERY and wipe cache but I could not go into RECOVERY. Everybody said to reflash the firmware but I already did that at least a dozen times with different versions for stock firmware. ODIN always reported PASS and SUCCESS. But it still stuck on logo .
Does Odin have auto reboot checked?
audit13 said:
Does Odin have auto reboot checked?
Click to expand...
Click to collapse
I tried it with and without. With AUTOBOOT checked, it reboots by itself then stuck at logo.
WIthout autoboot checked, I removed the battery then reinsert and power it on, same thing: stuck at logo.
Yes, I tried almost everything and combination of them
ODIN never gave any error. I even tried different version of ODIN. Here is a typical log:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_T889UVBMD1_T889TMBBMD1_935627_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> sboot.bin
<ID:0/005> tz.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!
Do no check auto reboot. After a success flash, remove USB cable from the phone, remove battery, replace battery, and then use button combination to boot to recovery,factory wipe, and reboot. Letting the phone boot after flashing a stock rom without wiping first may be causing the problem.
audit13 said:
Do no check auto reboot. After a success flash, remove USB cable from the phone, remove battery, replace battery, and then use button combination to boot to recovery,factory wipe, and reboot. Letting the phone boot after flashing a stock rom without wiping first may be causing the problem.
Click to expand...
Click to collapse
I already tried what you just said. No luck. It wouldn't go into RECOVERY, so I could not wipe.
That's what I'm confused: if the RECOVERY was bad, reflashing it would replace the RECOVERY code in flash. But it did not seem to work...
I have also reflashed just TWRP, with NO check on AUTOBOOT. Then I pulled the battery, reinserted it, pressed VOL_UP+HOME+POWER, still stuck at logo and it would not go into RECOVERY.
I think you may be out of options except for a jtag.
If the service is too expensive, maybe look for a phone with a smashed screen and working motherboard?
Any particular reason you are flashing such an old rom?
http://www.sammobile.com/firmwares/database/SGH-T889/
audit13 said:
I think you may be out of options except for a jtag.
If the service is too expensive, maybe look for a phone with a smashed screen and working motherboard?
Click to expand...
Click to collapse
I think I'm going to get a Note 4 from ebay, then I will use this Note 2 as an exercise to explore JTAG...
testrider said:
I think I'm going to get a Note 4 from ebay, then I will use this Note 2 as an exercise to explore JTAG...
Click to expand...
Click to collapse
I have your same problem.
Do you think it's a hard brick or just a soft brick?
If you can solve, can you tell me how you did?
There was really no reason for it to brick, . I was running stock firmware as from the factory...
Sent from my SM-T230NU using Tapatalk