Develop Bugs

[Q] Phone stuck at "Samsung Galaxy S II" Logo

I'm not new to rooting, I'm coming from the Samsung Epic 4G.. My new Epic Touch 4G is stuck at the Samsung Galaxy II GT-I9100 Logo.. Really annoying. Here's what happened...
I rooted my new Epic touch with this link: http://www.forums.acsyndicate.net/s...lus-Stock-Rooted-BusyBox-CWM5-and-Plus-Tweaks
Everything was working fine.. I then wiped the phone (the usual) and flashed the stable Starburst ROM
I rebooted and started getting an error saying "Sorry! The application Status Bar (processcom.android.systemui) has stopped unexpectedly. Please try again."
The notification bar was not present at all.. Soft reboots started recurring so I tried to restart but it didn't work. I ended up pulling the battery.
I then entered CWM and took a different approach.. I followed some steps from "Weltwon" (http://forum.xda-developers.com/showthread.php?t=1276320&page=169) and it didn't even get pass the "Logo" screen.. I pulled the battery once again (uh-oh)...
After putting the battery back in, I entered download mode and tried to Odin back to EG30 but it still stalled at the "Logo" screen.
Being that I wasn't coming from another ROM, is it possible that I messed something up when I formatted system in the "mounts and storage" tab?
Hopefully it's not a goner.. Any help would be appreciated.

Here's my Odin log after using the stock kernal pulled tar file..
No pit was added..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)

so let me get this straight.. you odin and everything was working properly. then you wanted to flash a custom rom and then you got errors. now you tried to odin again and you get stuck at samsung screen?
have you done this?
- ODIN with a different usb cable, or computer?
- redownload the roms?
ODIn to stock should boot and fix your errors in my expereince..

SocialReject said:
I'm not new to rooting, I'm coming from the Samsung Epic 4G.. My new Epic Touch 4G is stuck at the Samsung Galaxy II GT-I9100 Logo.. Really annoying. Here's what happened...
I rooted my new Epic touch with this link: http://www.forums.acsyndicate.net/s...lus-Stock-Rooted-BusyBox-CWM5-and-Plus-Tweaks
Everything was working fine.. I then wiped the phone (the usual) and flashed the stable Starburst ROM
I rebooted and started getting an error saying "Sorry! The application Status Bar (processcom.android.systemui) has stopped unexpectedly. Please try again."
The notification bar was not present at all.. Soft reboots started recurring so I tried to restart but it didn't work. I ended up pulling the battery.
I then entered CWM and took a different approach.. I followed some steps from "Weltwon" (http://forum.xda-developers.com/showthread.php?t=1276320&page=169) and it didn't even get pass the "Logo" screen.. I pulled the battery once again (uh-oh)...
After putting the battery back in, I entered download mode and tried to Odin back to EG30 but it still stalled at the "Logo" screen.
Being that I wasn't coming from another ROM, is it possible that I messed something up when I formatted system in the "mounts and storage" tab?
Hopefully it's not a goner.. Any help would be appreciated.
Click to expand...
Click to collapse
Silly question, but did you actually flash a ROM or just kernels after performing Weltwon's steps? I don't know what he was posting that regarding, but it seemed his instructions asked you to format /system (ie erase your ROM) but never mentioned flashing your new ROM by CWM or by Odin. Perhaps that was just understood in the context he was replying to, but if you didn't do so, you'd have a kernel on your phone but no ROM, meaning you could boot into Recovery, but there would be no ROM to boot into.

sfhub said:
Silly question, but did you actually flash a ROM or just kernels after performing Weltwon's steps? I don't know what he was posting that regarding, but it seemed his instructions asked you to format /system (ie erase your ROM) but never mentioned flashing your new ROM by CWM or by Odin. Perhaps that was just understood in the context he was replying to, but if you didn't do so, you'd have a kernel on your phone but no ROM, meaning you could boot into Recovery, but there would be no ROM to boot into.
Click to expand...
Click to collapse
I think I'm gonna just throw it away...
I woke up this morning and tried to boot into recovery and got a black screen sorta like this... "Phone . . Triangle with exclamation mark inside . . Computer"
I go into download mode and it says my Product name is GT-9100 !?
No computer ever recognizes it as a device, it's just a paper-weight now smh

if you cant get into download mode you might be screwed.. if you can tho, i recommend flash the eg30 with root, not just a kernel.. using odin and having it put in the pda slot with just auto reboot checked.. flashing just a kernel won't fix your problems

elliwigy said:
if you cant get into download mode you might be screwed.. if you can tho, i recommend flash the eg30 with root, not just a kernel.. using odin and having it put in the pda slot with just auto reboot checked.. flashing just a kernel won't fix your problems
Click to expand...
Click to collapse
I can get into download mode but the phone isn't recognized at all, by any of my computers.. My product name says GT-I9100 rather than SPH-D710. weird

hm.. if you can get into download mode try this guid out.. http://forum.xda-developers.com/showthread.php?t=1282415
Make sure you have correct drivers of course, make sure you try dif usb ports if possible and dif cables if possible.. maybe even a dif. odin

SocialReject said:
I can get into download mode but the phone isn't recognized at all, by any of my computers.. My product name says GT-I9100 rather than SPH-D710. weird
Click to expand...
Click to collapse
when you flash a rooted kernel, all our phones say GTI9100....

wase4711 said:
when you flash a rooted kernel, all our phones say GTI9100....
Click to expand...
Click to collapse
Oh. Well, I've tried different drivers.. Even reinstalled Kies but the phone won't recognize at all. I'll try some more USB cords.

wase4711 said:
when you flash a rooted kernel, all our phones say GTI9100....
Click to expand...
Click to collapse
Yea.. it does say GT I9100 with a exclamation mark in a yellow triangle.. besides that, his phone still isnt booting lol.. all you need is to get your pc to see the phone.. when you open Odin and plug phone in while in download mode, you don't get a COM to light up?? try using different version of Odin.. try restarting your pc etc etc.. try another computer if possible too.. trial and error lol, id keep putting your phone into download mode too.. i had this problem with my OG Epic.. it took a while but I finally got it to read in ODIN

elliwigy said:
Yea.. it does say GT I9100 with a exclamation mark in a yellow triangle.. besides that, his phone still isnt booting lol.. all you need is to get your pc to see the phone.. when you open Odin and plug phone in while in download mode, you don't get a COM to light up?? try using different version of Odin.. try restarting your pc etc etc.. try another computer if possible too.. trial and error lol, id keep putting your phone into download mode too.. i had this problem with my OG Epic.. it took a while but I finally got it to read in ODIN
Click to expand...
Click to collapse
Odin can't recognize it because my computer doesn't even recognize it. I plug it in and go to device manager and there's no signs of it. Maybe it's the drivers, idk. I haven't even activated it to Sprint yet so I doubt that they help a "stranger"

Try a USB jig
Sent from my Samsung Galaxy S2

I heard usb jig only works if I can't already get into download mode.
Sent from the future.

[Q] Help Un-Soft-bricking SGH-i747M

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?

can't wipe phone, reboots about 5 seconds into wipe, help?

The title really says it all...I am trying to wipe my phone to put on wicked 9.1 and try some new kernels, but every time I go into recovery and tell it to do a factory reset/wipe, the phone goes on like it is gong to wipe but then about five seconds in, it just reboots. Hours right back into the normal boot procedure and boots up fine like I never told it to wipe.
still pretty new to all of this, I mean I got clockwork recovery on and have learned to flat kernels kitchens and roms, but that's about it. I've never had a problem like this before, but I can't figure out what to do to wipe my phone.
IHave also tried just installing the new room and telling the installer to wipe, but then it just reboots when it gets to that point.
Is there a different way to wipe the phone? I don't want to lose my personal data such s photos calender etc, I understand I'll lost sms longer normal but I back those up so that is ok
Any help for a kind of newbie?
on advance

Also have tried going to Mount/format partition on recovery and manually formatting the data partition...same thing phone just reboots after a couple seconds and acts like I did nothing at all to it
If I was too go to factory reset in the settings menu while the phone is booted up normally what would happen? It scares me cuz it looks like it would kill everything
Oh and I screwed up and accidentally deleted my nandroid backup...yea I'm dumb

Download goo manager.
Hit menu.
Choose "install open recovery script".
Verify it has identified your device correctly.
Let it download and install TWRP.
Reboot into recovery.
Make backup using TWRP.
???
Profit.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

re: rebooting issue
asaqwert said:
The title really says it all...I am trying to wipe my phone to put on wicked 9.1 and try some new kernels, but every time I go into recovery and tell it to do a factory reset/wipe, the phone goes on like it is gong to wipe but then about five seconds in, it just reboots. Hours right back into the normal boot procedure and boots up fine like I never told it to wipe.
still pretty new to all of this, I mean I got clockwork recovery on and have learned to flat kernels kitchens and roms, but that's about it. I've never had a problem like this before, but I can't figure out what to do to wipe my phone.
IHave also tried just installing the new room and telling the installer to wipe, but then it just reboots when it gets to that point.
Is there a different way to wipe the phone? I don't want to lose my personal data such s photos calender etc, I understand I'll lost sms longer normal but I back those up so that is ok
Any help for a kind of newbie?
on advance
Click to expand...
Click to collapse
Here is the best and most surest way to get your phone ready to flash the "Wicked 9.1" or any other custom rom.
(You made a good choice of wanting to flash the Wicked 9.1 rom, it's the best custom rom currently available for our phones.)
Since the recovery mode (wipe) is not functioning properly you will need to Odin flash the stock rooted rom
before flashing any of the custom roms.
By doing the following you will NOT loose any pictures, videos or emails
and you will not loose anything which is on the internal or external sdcard.
You will as you said loose sms UNLESS you go to the play store and download sms backup/restore app.
Here is a link for the SMS backup restore app: https://play.google.com/store/apps/...estore&feature=nav_result#?t=W251bGwsMSwyLDNd
If you already have a backup/restore app like Titanium backup I would advise to backup all your apps first.
That way you will be able to restore the backup/restore sms app but you will be able to restore all your other
apps too after flashing the wicked rom.
After you backed up the sms using this app and after you have flashed the wicked rom you will need to
re-download this backup/restore sms app from the play store in order to restore your sms after you have
flashed the wicked rom.
This step by step is the best, most reliable and cleanest way to restore your phone to a stock rooted T999
and will get the phone ready for the new custom wicked rom to be flashed without any further problems.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you purchased it except for the benefit of being rooted.
Download the stock-rooted T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download ODIN it's required for flashing the stock rooted firmware (a windows app) http://d-h.st/Q14
After it's downloaded extract Odin into the same folder you made containing the T999 TAR file.
Download the stock-rooted Odin flash firmware for the T999 Tmobile Galaxy S3
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!

Didn't work at all...I'm fact, now I can't even boot into recovery it just reboots after a few seconds at the teamwin screen....
Also before I did this last thing with goo manager, I tried fixing permissions and the same thing happened it just reboots a few seconds after telling it to fix permissions in recovery
I'm really worried...I can't even get into recovery and I'm scared I'm gong to have a broken phone here shortly
Even worse my phone is my only internet connection right now

Misterjunky said:
Here is the best and most surest way to get your phone ready to flash the "Wicked 9.1" or any other custom rom.
(You made a good choice of wanting to flash the Wicked 9.1 rom, it's the best custom rom currently available for our phones.)
Since the recovery mode (wipe) is not functioning properly you will need to Odin flash the stock rooted rom
before flashing any of the custom roms.
By doing the following you will NOT loose any pictures, videos or emails
and you will not loose anything which is on the internal or external sdcard.
You will as you said loose sms UNLESS you go to the play store and download sms backup/restore app.
Here is a link for the SMS backup restore app: https://play.google.com/store/apps/...estore&feature=nav_result#?t=W251bGwsMSwyLDNd
After you backed up the sms using this app and after you have flashed the wicked rom you will need to
re-download this backup/restore sms app from the play store in order to restore your sms after you have
flashed the wicked rom.
This step by step is the best, most reliable and cleanest way to restore your phone to a stock rooted T999
and will get the phone ready for the new custom wicked rom to be flashed without any further problems.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you purchased it except for the benefit of being rooted.
Download the stock-rooted T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download ODIN it's required for flashing the stock rooted firmware (a windows app) http://d-h.st/Q14
After it's downloaded extract Odin into the same folder you made containing the T999 TAR file.
Download the stock-rooted Odin flash firmware for the T999 Tmobile Galaxy S3
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!
Click to expand...
Click to collapse
thanks so much!!! by saying it didn't work at all, i meant the goo manager thing... i am just going to start trying what you've said here now...
thank you SO much, this is what forums should be about... thank you for not telling me to go search or stuff like that, cuz i didn't know what to search for or what i could even try at this point, and i don't want to risk ruining a phone i can't afford to replace!!
thanks again
will update on the results....

also what recovery is the best one currently? would you recommend the one that is installed by GooManager or should i go back to clockwork mod recovery? or the TWRP or whatever is it called?? just don't know enough about what is current... am a single daddy now and can't really afford that much time to muck about with my phone.... basically i take a night every couple of weeks to find out if there is a new ROM or Kernel that i could benefit from but i just can't seem to make/find the time to keep up to date on everything.....
thanks again!

re: flashing
asaqwert said:
also what recovery is the best one currently? would you recommend the one that is installed by GooManager or should i go back to clockwork mod recovery? or the TWRP or whatever is it called?? just don't know enough about what is current... am a single daddy now and can't really afford that much time to muck about with my phone.... basically i take a night every couple of weeks to find out if there is a new ROM or Kernel that i could benefit from but i just can't seem to make/find the time to keep up to date on everything.....
thanks again!
Click to expand...
Click to collapse
I have used both CWM and TWRP (goomanager) and TWRP for me is the best.
If I were you I would not mess with any kernels until you get a better understanding
about customizing your phone, flashing, adding mods, what kernels do and why many
people like to change the stock kernels to custom kernels.
I have tried all the custom kernels and I cannot see the purpose of doing so.
With custom kernels you can make the phone respond faster but then you
sacrifice battery life, if you want better battery life you can adjust these kernels
so they use less battery power but then you sacrifice the phone's responsiveness.
I think that the manufacturer of the phone got it just about right with the stock kernel.
A good balance between speed and battery consumption.
Good Luck!

OH MY GOD... what the hell do i do... i'm getting so choked here now...
tried ODIN, wouldn't work... it gave me the following output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
what do i do??? it won't let me do anything... i'm just freaking right out now...
whenever it tries to do anything with the data partition it seems to just force reboot.,..
any ideas? please help me here...

re: try this
asaqwert said:
OH MY GOD... what the hell do i do... i'm getting so choked here now...
tried ODIN, wouldn't work... it gave me the following output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
what do i do??? it won't let me do anything... i'm just freaking right out now...
whenever it tries to do anything with the data partition it seems to just force reboot.,..
any ideas? please help me here...
Click to expand...
Click to collapse
Try this, do the same thing you done before but instead of using the stock rooted firmware
try this one: http://www.androidfilehost.com/?fid=9390169635556426424
This is the 100% stock firmware WITHOUT root.
The firmware is identical to what all the T999 phones came with from Samsung.
If this flashes successfully you will need to ROOT the phone before you do anything else.
Right now your phone is in the same condition as it was before trying to flash the stock rooted firmware.
Good Luck.

sorry for the freak out post, i just actually AM freaking out.... when i was mucking about with ODIN i realized i had used it before with the SGS3 toolkit for snapdragon v2.1, so i figured maybe i could try to put a stock rom on that way, well all i could get on was a stock recovery, then i put on a CWM recovery using the toolkit and ODIN, and for whatever reason, that recovery will only read my external SD card and not my internal one, and will only let me flash off that... some how, and thankfully, i had a FreeGS3 7.1 rom on there that i was able to flash, as it wouldn't boot up at all after the failure with ODIN... now i got it booting into FreeGS3 7.1 but it is acting really odd... slower than anything, it's slower than my old HTC maple was, feels like an old phone on froyo or something....
so any other idaes? thanks for the help so far
p.s. about the kernels, i've had pretty good luck up until now with sticking with kernels by some of the really experienced devs, like morphic and faux123, and the biggest reason i want to muck about with them is so that i can undervolt my phone, and get a little longer battery life.... i can deal with a LITTLE bit of a loss of performance, as i rarely do much more than browse the web, text, email, and call on my phone, maybe read the news on the BBC app, and do other stuff like that, but no gaming ever, and don't watch much for video on it either, so i really can't tell the difference in speed too much if i have it set up for slightly better battery life
but at this point, i honestly just want it to work again! i just want to be able to wipe it and start from square one! i don't think i could even bring it back to the store for a warranty because they're going to obviously see that i had a different ROM on it than stock

Misterjunky said:
Try this, do the same thing you done before but instead of using the stock rooted firmware
try this one: http://www.androidfilehost.com/?fid=9390169635556426424
This is the 100% stock firmware WITHOUT root.
The firmware is identical to what all the T999 phones came with from Samsung.
If this flashes successfully you will need to ROOT the phone before you do anything else.
Right now your phone is in the same condition as it was before flashing the stock rooted firmware.
Good Luck.
Click to expand...
Click to collapse
before i do this, i'm just wondering if you have any idea why it might be acting this way? i just feel like i'm going to have the same kind of trouble i just had with this rom, as it was obviously having issues with wiping the data partition and/or another area.... i just don't want to muck about too much and end up with a brick... so any ideas why it is doing this and if there is just simply some sort of command i can use to force it to do a wipe, using ODIN or the toolkit, or something else? if so, i'd need some help getting it right, thats for sure
i also am using my phone to tether my computer, as we don't have internet at home for this month, so i really kind of need to know if something SHOULD work or if it is just a shot in the dark, beause if it is a shot in the dark and it fails and i can't get my phone booted again, then i can't even get on the net to post info and get more help.... i'll be screwed and i just realized that my boss wanted to call me in the morning, i thought he was calling friday morning not tomrw

asaqwert said:
before i do this, i'm just wondering if you have any idea why it might be acting this way? i just feel like i'm going to have the same kind of trouble i just had with this rom, as it was obviously having issues with wiping the data partition and/or another area.... i just don't want to muck about too much and end up with a brick... so any ideas why it is doing this and if there is just simply some sort of command i can use to force it to do a wipe, using ODIN or the toolkit, or something else? if so, i'd need some help getting it right, thats for sure
i also am using my phone to tether my computer, as we don't have internet at home for this month, so i really kind of need to know if something SHOULD work or if it is just a shot in the dark, beause if it is a shot in the dark and it fails and i can't get my phone booted again, then i can't even get on the net to post info and get more help.... i'll be screwed and i just realized that my boss wanted to call me in the morning, i thought he was calling friday morning not tomrw
Click to expand...
Click to collapse
The only thing I can think of right now is that you tried to flash some custom kernel or rom which
was not compatible with the phone if this is the case then that's what started the problem.
If the above is true then I would try to flash the STOCK kernel without trying to WIPE anything.
Here is the STOCK kernel you can flash in TWRP or CWM: http://dl.xda-developers.com/attach.../51821620/1/4/3/4/1/6/1/T999UVALH2-Kernel.zip
Try flashing this stock kernel first, if it does not help I would go ahead and ODIN flash the un-rooted stock firmware.
As long as you can get into download mode your phone is NOT bricked.
Good luck!

Did you try verifying the checksum?

First, yea checksum is all good
, that kernel won't download it just says error 410 - gone
other links?
,Honestly, I don't feel it is anything to do with the kernel...I think that something has changed some setting to do with the data partition or something
you do a factory reset/ wipe, what exactly does the phone wipe? Can I do this manually with adb or something? If so, how? Sorry to ask for this kind of help but I'm at my wits end, I'm honestly just about to lose it, the other reason I wanted to flash wicked 9.1 is that my phone was getting slow and unusable something was going on with it....I'm honestly almost in tears with this as I can't afford to buy anything right now and I need my phone to work for work, or I can't make ANY money, so right now I'm screwed. I've never had anything even similar to this happen before
Please help me get this back to working....as it is it is unusable and laggy to they point where I can't do much of anything....I'm actually at Tim Horton's on their Wi-Fi with my laptop trying to get it to work because my phone is so messed up

Factory reset wipes your data partition. And I guess some other things. What was it you tried to Odin? Was it stock UVDLJC? Try both Odin versions in my signature, as some people have had issues with the newer one.
I recommend trying that. Because if that doesn't work, my money is on hardware failure.

Aerowinder said:
Factory reset wipes your data partition. And I guess some other things. What was it you tried to Odin? Was it stock UVDLJC? Try both Odin versions in my signature, as some people have had issues with the newer one.
I recommend trying that. Because if that doesn't work, my money is on hardware failure.
Click to expand...
Click to collapse
Well I'm trying to flash basically anything that might help me be able to wipe my phone so that I can either go back to stock and warranty the phone if there are legit problems with the hardware, or what is more likely is that there is just some file that got corrupted and is forcing the phone to reboot when I try to wipe. In that car I just want to be able to wipe and install wicked 9.1.
Dos anyone have a working link to the stock kernel? The link provided above does not work
And are there any other ideas? I just find it hard to believe that there is a hardware failure when the phone has been working fine, just getting a little laggy, and honestly I just wanted to upgrade to the new wicked Rom....I just find it very hard to imagine that a hardware issue is causing me to not be able to wipe but I can still use the phone normally in every other way
Again, is there a way to manually wipe using adb ro some other program? If so how, and what exactly do I wipe and what do I leave alone? I've managed to copy everything I want to save over from my phone so I should be ok to format whatever I need to
Please help! And thanks again and thanks in advance
Oh and by ghee way Odin will let me flash a new recovery, it is only when I try to flash one of the two stock roms that were linked above that it errors out....I haven't tried anything else with Odin yet, not really sure how
I flash a normal Rom file with Odin? How so?

Aerowinder said:
Factory reset wipes your data partition. And I guess some other things. What was it you tried to Odin? Was it stock UVDLJC? Try both Odin versions in my signature, as some people have had issues with the newer one.
I recommend trying that. Because if that doesn't work, my money is on hardware failure.
Click to expand...
Click to collapse
oh and when i go to the link for the older version of odin that is in your sig, it says that it can't find it....any help there?

this is what i got with the Odin 1.85 that i got from your sig... i got it working, was something in my hosts file blocking access to the site... my bad there
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
any ideas?
also, on the phone screen itself, it says the following:
ODIN MODE
PRODUCT NAME: SGH-T999V
CUSTOM BINARY DOWNLOAD: Yes (5 Counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
SECURE CHECK FAIL: aboot
so any ideas what the crap is going on?

So do you have a t999 or a t999v?
You can access the proper t999v firmware from my signature.

Galaxy SGH-I747 on 4.2.2 ROOTED Softbricked after AT&T OTA

Had stock AT&T SGH-I747 at Android 4.2.2 rooted with chainfire working fine. Today an update installed automatically and now I'm dead.
At first, it would show the Samsung logo and maybe another, then just go black.
Now normal booting, or attempting to boot into recovery gives: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
If attempt to boot into download mode, it succeeds. But everything will end up with "FAIL!" in Odin and show "fused 3 > binary 0" on the phone. I've tried multiple Odins: v3.10.6, 3.09, 3.07 and multiple recoveries (Clockwork 6.0.4.7, etc.) and stock ROMS (UCALG1, UCDLK3).
Even Kies "Firmware Upgrade and Initialiasion" option, where you enter in SGH-I747 and the serial number will go through all the motions and then fail, with the same "fused" message showing on the phone.
Grendelin had the most similar situation (I can't post external links yet, but you can get to it at http:__androidforums.comthreads_at-t-gs3-at-t-issues-after-downloading-newest-update.860382_ by replacing _'s with /'s) as me but the difference is that he was able to flash a recovery image which led to further restoration.
Please help. If it's not possible to recover this, I would just like to get a couple years' worth of pictures from /sdcard/DCIM/*.

When you boot into download mode, do you see anything about warranty bit?
You could try and flash TWRP using Odin, then boot to TWRP and mount the data partition to see if you can copy the data from the phone to your computer.

audit13 said:
When you boot into download mode, do you see anything about warranty bit? You could try and flash TWRP using Odin, then boot to TWRP and mount the data partition to see if you can copy the data from the phone to your computer.
Click to expand...
Click to collapse
I tried TWRP (specifically twrp-2.8.7.0-d2att.img.tar) using Odin and it gave all the usual signals that it's working before the box turns red and it says "FAIL!" on it. Here's its log in case it's useful:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialization..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yes download mode does mention the waranty bit. Here's the full text:
Code:
ODIN MODE
PRODUCT NAME: SGH-I747
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 3

Are you using version 3.07 of Odin? Did you uncheck everythign except f.reset time before flashing?
What about flashing Philz Touch for the d2lte? I was suggesting TWRP because you may be able to re-flash a rooted nj1 system and boot img.
I asked about warranty bit to make sure that the phone was running a 4.3 or newer bootloader. As you may know, the 4.3 bootloader cannot be downgraded so you can't flash anything from sammobile.

Yes, 3.07, and there were only two things checked, "F. Reset Time" and "Auto Reboot". At your suggestion I unchecked the latter but it appeared to have no effect on the flashing success.
Can't get to philz's dev files at the moment since his page at goo.im is down.
I don't understand what is meant by 4.3 bootloader. Isn't 4.3 referring to the Android version? While Android lists the bootloader version in its properties, Android in principle shouldn't be concerned about what lower level, hardware specific bootloader brought it up, should it?
I really need my phone back

dreamluvr said:
Yes, 3.07, and there were only two things checked, "F. Reset Time" and "Auto Reboot". At your suggestion I unchecked the latter but it appeared to have no effect on the flashing success.
Can't get to philz's dev files at the moment since his page at goo.im is down.
I don't understand what is meant by 4.3 bootloader. Isn't 4.3 referring to the Android version? While Android lists the bootloader version in its properties, Android in principle shouldn't be concerned about what lower level, hardware specific bootloader brought it up, should it?
I really need my phone back
Click to expand...
Click to collapse
I really hate to tell you this but I don't think your going to get this fixed yourself. If Odin is failing like that your probably going to need a debricking service that can flash your emmc directly. If you can get a recovery back on then you'll be fine cause you can then flash firmware to repair the damage the OTA did. Keep trying I guess but ultimately you'll probably need the debricking service.
When bootloaders are refered to as 4.3 or 4.4.2 is just referring it to the OS version they came with in the OTA. And while on a pc this is true windows isn't dependent on the lower lever firmware, Android kinda is... least the OEM's have made it that way.

Most people say that if you can reach download mode then you're OK. I can't believe this ****ing phone is just going to sit here and reject everything that's sent to it. In some cases I'm sending it stock stuff.
It's bull**** that AT&T can just impose their updates like this. Yes I had modifications that probably interfered with their intended update, but they obviously exercised no caution, not checking that everything was in their expected state before overwriting.
I'm upset that I supported a gimped device, one that's cryptographically preventing user modifications when it's user paid for.
Is there no hope in simply making a disc image, mounting it, and recovering /sdcard/DCIM ?

I had a similar problem a week ago. I got this i747 and decided to wipe it using kies. I didn't know about the boot loader problem after the kitkat OTA upgrade. So I had a soft brick like you. I ran into the same problems using Odin to flash the twrp tar and various other images. What I decided to do was flash twrp multiple time using odin. But during one of the reboots I think I removed the cable and put it back (maybe even pulled the battery?) in time for odin to check and say it was successful. Then i had a semi-functional twrp to flash the rooted ucfnj1 image from the i747 dev forum. I still have root issues, but my phone works.

bump before I mail it off to unbrick service
looking for any ideas
short summary: canNOT boot into recovery, CAN boot into download, but Odin always fails and phone says "fused 3 > binary 0"
EDIT (Sept 8, 2015): I used mipick22's JTAG services on ebay and he fixed it. Good price, good communication, etc. Says he's a member on here but didn't give his username.

Stuck at "Galaxy Note II"?

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