Related
ATT Galaxy S3 SGH-I747
16 GB
Trying to root using Galaxy S3 Toolkit (Snapdragon):
http://forum.xda-developers.com/showthread.php?t=1746665
Chose option for ALLINONE (Flash Insecure Boot, CWM, Root Phone + Install Busy Box)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ran Odin (not 3.07 version, don't have exact version anymore). Flashed file, phone rebooted.
Goes directly to:
Samsung Galaxy S3 Logo and just stays there. (I never see just a Samsung Logo).
I can get into Download mode, but not recovery mode.
When I try to reflash via Odin (including stock ROMs), the upload hangs.
Here is the output from Odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.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> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
It will never go past NAND Write Start. The phone shows the Downloading screen, but as soon as it starts, the download bar goes to 100%. I have left it like this for a couple of hours and it never completes.
Searching around the forums, I see a number of other reports of people not being able to get in recovery mode, and not getting past "NAND Write Start!!" but I havent been able to find any solutions.
I did find the two posts below which had the same issue and a solution:
https://plus.google.com/u/0/115708174332375617872/posts/QhxJRcf4G6q
https://plus.google.com/115708174332375617872/posts/9x2Zy8BRfV3
Which involved using a PIT file and a 3 part firmware, but I havent been able to find the corresponding files for my device.
Does anyone have any suggestions on how I can get the phone working again? or get recovery mode working?
I would suggest using Odin 3.07 and follow this thread http://forum.xda-developers.com/showthread.php?t=1739426, it will have the the files you need, Once rooted then use snapdragon and select custom recovery from there
jeeper11 said:
I would suggest using Odin 3.07 and follow this thread http://forum.xda-developers.com/showthread.php?t=1739426, it will have the the files you need, Once rooted then use snapdragon and select custom recovery from there
Click to expand...
Click to collapse
Thanks. I did try that with 3.07, but the problem is that Odin gets stuck on "NAND Write Start!!".
All I can suggest is make sure NOTHING else is running while using Odin, try different usb ports, Heck, try deleting Odin the re-download it and the stock root file you need
jeeper11 said:
All I can suggest is make sure NOTHING else is running while using Odin, try different usb ports, Heck, try deleting Odin the re-download it and the stock root file you need
Click to expand...
Click to collapse
Thanks. I tried with multiple USB cables, and on multiple computers. Same issues each time.
The solution in the post above seems to suggest I need to Flash using a PIT file, but I cant find the appropriate file for my device.
root69_ATT_I747UCALG1.7z...<< is this the file you have?..
To be sure...download this file, put it on your desktop. Extract it to your desktop. Phone in DL mode, open odin. connect phone. click PDA button, search your desktop for the root69 file, click it once, then click open at the bottom of the dialogue box. hit start on Odin.
I just want to make sure your following the right steps and files
jeeper11 said:
root69_ATT_I747UCALG1.7z...<< is this the file you have?..
To be sure...download this file, put it on your desktop. Extract it to your desktop. Phone in DL mode, open odin. connect phone. click PDA button, search your desktop for the root69 file, click it once, then click open at the bottom of the dialogue box. hit start on Odin.
I just want to make sure your following the right steps and files
Click to expand...
Click to collapse
Thanks for helping me with this. Yes, I am doing exactly that, and still having the same issues. "Nand Write Start!!" which never finishes.
You need to find a recovery tar. Flash and should be done i was having the same issue with an i727
Sent from my SAMSUNG-SGH-T989 using xda premium
marcos600rr said:
You need to find a recovery tar. Flash and should be done i was having the same issue with an i727
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks. Same issue, "<ID:0/004> NAND Write Start!!". Basically, I can get into download mode, but nothing will flash from Odin. It just stops on Nand Write Start. Odin doesnt hang btw, if I disconnect the cable, then Ill get a failure message in odin. Otherwise, it will just stay in Nand Write Start forever (have left it running a couple of hours before).
I'm sure you do, but do you have all the drivers for your phone on your comp?
And somewhere on here is a thread on using Kies to restore to stock.
---------- Post added at 10:36 PM ---------- Previous post was at 10:27 PM ----------
here it is http://forum.xda-developers.com/showthread.php?t=1984717
jeeper11 said:
I'm sure you do, but do you have all the drivers for your phone on your comp?
And somewhere on here is a thread on using Kies to restore to stock.
---------- Post added at 10:36 PM ---------- Previous post was at 10:27 PM ----------
here it is http://forum.xda-developers.com/showthread.php?t=1984717
Click to expand...
Click to collapse
Yes. Drivers are installed. Have tried on two machines, one with kies, and one where I manually installed the drivers.
Have you tried both the older and newer stock roms on Odin?
I just want to help you figure this out,Or at least have someone else help us here lol
jeeper11 said:
Have you tried both the older and newer stock roms on Odin?
I just want to help you figure this out,Or at least have someone else help us here lol
Click to expand...
Click to collapse
Yeah, I have tried multiple versions. The issue seems to be that the roms dont actual begin to write. Looking at my original post, I did find someone with a similar problem and they had to do a flash using a 3 part / file firmware, and a PIT file to repartition the device. However, I cannot find the 3 part firmware for my device.
Ok , my last annoying question for you...you said you tried kies, was that for the drivers or did you try that restore method thru kies?
P.S i can't find the 3 file for your device either, maybe its just for the I9300
jeeper11 said:
Ok , my last annoying question for you...you said you tried kies, was that for the drivers or did you try that restore method thru kies?
P.S i can't find the 3 file for your device either, maybe its just for the I9300
Click to expand...
Click to collapse
That was for the drivers. I did launch kies with the phone in download mode, but kies cant connect to the device (although it does try).
Btw, thanks for the help with this.
mike
mesh2325 said:
That was for the drivers. I did launch kies with the phone in download mode, but kies cant connect to the device (although it does try).
Btw, thanks for the help with this.
mike
Click to expand...
Click to collapse
ok. I have made some progress and have been able to get it boot. My hunch that I had to repartition was correct.
First, I used the PIT file listed here:
http://forum.xda-developers.com/showpost.php?p=29130477&postcount=14
and used the 3 file firmware from here:
https://hotfile.com/dl/158814567/30ec3bc/GT-I9300_XEO_I9300XXALEF_I9300OXFALEA_I9300XXLEF.rar.html
This is not the correct one for my device, but my hunch was that it would Flash and repartition, and then I could flash the correct one on. (This appears to be the polish firmware). I can also once again get into recovery mode.
So, at this point, my phone is once again working, and now ill go back into odin and trying to install the correct firmware.
ok. Another quick update. Phone works fine not (and got it working in US English). Tried to install the firmware suggested by jeeper1 (root69_ATT_I747UCALG1.7z) but ran into the Nand Write Start!! issue again.
So, I have a working phone once again, although might not be running the exact firmware it should be. Still want to root, but need to recharge the phone first. Will keep posting updates as I get more info (in case anyone else runs into similar issues).
If anyone has any suggestions, let me know.
OK. Final update. I finally figured out the issue.
My phone is from AT&T US, and is listed on the box as SGH-I747. However, it is actually an international version (GT-19300). I noticed this when I realized there were multiple versions of the upgrade toolkit. Once I switched to the international version:
http://forum.xda-developers.com/showthread.php?t=1703488
the everything worked perfectly, and I was able to flash the roms.
So, perhaps AT&T sells multiple versions of the phone, once which works in US, and one which will also work internationally.
Basically, I was flashing the incorrect roms for my phone. Thanks for all of the help and input.
I'm having same issue
mesh2325 said:
ok. I have made some progress and have been able to get it boot. My hunch that I had to repartition was correct.
First, I used the PIT file listed here:
http://forum.xda-developers.com/showpost.php?p=29130477&postcount=14
and used the 3 file firmware from here:
https://hotfile.com/dl/158814567/30ec3bc/GT-I9300_XEO_I9300XXALEF_I9300OXFALEA_I9300XXLEF.rar.html
This is not the correct one for my device, but my hunch was that it would Flash and repartition, and then I could flash the correct one on. (This appears to be the polish firmware). I can also once again get into recovery mode.
So, at this point, my phone is once again working, and now ill go back into odin and trying to install the correct firmware.
Click to expand...
Click to collapse
I'm having this same problem right now as well, can you tell me step by step how you fixed this problem.
Thanks
hello fellas, i have Bell SGS 3, i used the all in one toolbox to load recovery and then using the recovery i flashed Avatar ROM, after flashing and using it for a few days I started receiving updates which I did and now I am stuck.
I lost recovery, I can not boot into recovery mode, I thought of flashing recovery again but the toolbox is asking for me to put the phone in debugging mode which I did and the toolbox doesn't go anywhere. It is stuck at "Waiting for USB debugging to be enabled" option and doesn't do anything. I thought I will use option available in toolbox to reflash the stock recovery back and go from there, still same, when it reaches the option for USB debugging to be enabled, it just doesn't go anywhere. I thought I will flash stock recovery through ODIN using the option available in toolbox, it does the same, stuck at waiting message.
Please help.
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?
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.
Looking back I cant recall ever updating this phone's OS or Baseband. But yet I read all over the place that Samsung and Sprint like to automatically update at random.
A few months back when 4.4.2 came out I noticed that my phone decided to automatically update itself and the moment it rebooted all hell broke loose. All the phone would do is boot showing the "Samsung" logo than the "Galaxy S3" logo right after. The phone would reboot itself right away than it would boot the exact same way, this time locking up on the "Galaxy S3" logo. The whole time also vibrating.
I am unable to boot into recovery mode, volume up + home button + power button. At the top left corner of the "Samsung" screen it shows "booting recovery" then immediately goes right to the "Galaxy S3" screen and reboots again.
I am able to boot to download mode, volume down + home button + power.
So far I have tried using ODIN's v3.09/3.07 to load stock firmware's for the original 4.0.4, 4.3, and just in case it actually updated 4.4.2. Every time I try to load them through ODIN I get...
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sbl2.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Write)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is where I'm stuck and at a loss. From what I have been reading all over XDA, as long as I can still boot to download mode I still have a chance. I am really crossing my fingers here because being a Disabled Veteran I can't afford the money to get a new phone outside of my current contract time. And there is no way the wife and I can share the Note 3, lol.
-Semper Fi
Try a different cable or port... Those are usually the biggest causes of Odin failures.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My ROM: WICKED X
bilgerryan said:
Try a different cable or port... Those are usually the biggest causes of Odin failures.
My ROM: WICKED X
Click to expand...
Click to collapse
AND DON'T TRY TO ODIN ANYTHING BUT 4.4.2!!!! YOU WILL BRICK YOUR PHONE COMPLETELY.
My ROM: WICKED X
Does the phone hard reset when in download mode too? If it does, your power button may be stuck D:
DirtTrash said:
So far I have tried using ODIN's v3.09/3.07 to load stock firmware's for the original 4.0.4, 4.3, and just in case it actually updated 4.4.2.
This is where I'm stuck and at a loss. From what I have been reading all over XDA, as long as I can still boot to download mode I still have a chance. I am really crossing my fingers here because being a Disabled Veteran I can't afford the money to get a new phone outside of my current contract time. And there is no way the wife and I can share the Note 3, lol.
-Semper Fi
Click to expand...
Click to collapse
@bilgerryan thank you for saying it lol he got really lucky that it didn't go through, if you can tell by what i quoted from this guy...he already tried to Odining lower than 4.4.2....he said he read all over XDA so he should have come across us saying don't flash below 4.4.2.....
No, the power button isn't stuck. And remember me stating that the phone had NEVER been rooted. And from what Samsung told me the phone hadn't been updated to 4.4.2 yet so that's why previous versions were attempted. They came to that conclusion from me telling them what the Download Mode screen showed.
ODIN MODE
PRODUCT NAME: SPH-L710
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOMM SECUREBOOT: ENABLE
And that's all that shows. Nothing about KNOX or any counters that they said would have appeared if the phone had been updated with, I think they said, 4.3 or 4.4.2. So, from the information I gathered from them is the phone supposedly has an older version still installed.
And thank you very much for chiming in bilgerryan . Your thoughts and concerns have been noted and are appreciated. And 6th_Hokage...if I had the links to where I read the many posts stating to try the other versions I'd post them here for you. The posts did reiterate what Samsung had stated regarding being able to attempt flashing multiple versions. BTW, these are all stock Samsung packages I'm using to flash via ODIN.
So, I was able to successfully install 4.1.2 last night and the phone booted up without any issues. The phone was back to the original state at which it was purchased, aside from not being 4.0.4. Then the strangest thing happened, I installed a few applications from the Play Store and the phone started acting up again. It rebooted twice on its own then went back to the home screen...odd. Then I noticed the phone tried automatically updating again, just like what originally happened last time. And now its back to the EXACT state it was. And again, attempts at reinstalling 4.1.2 were unsuccessful. Note, I am still able to success download mode.
Anything at all out there??
And please, save the thread a post if you're just going to reiterate something someone else already stated. And still, from what I'm reading here throughout XDA is that I'm now S.O.L. because I can still boot to Download Mode. Thanks in advance.
DirtTrash said:
And 6th_Hokage...if I had the links to where I read the many posts stating to try the other versions I'd post them here for you. The posts did reiterate what Samsung had stated regarding being able to attempt flashing multiple versions. BTW, these are all stock Samsung packages I'm using to flash via ODIN.
U do have the posts. On 11/29/13 jdelano reaponded to a very similar post fro u, with this advice...
"You'd only be taking a risk trying to ODIN 4.1.2 (MD4) to your phone at this point. If the 4.3 bootloader made it on, then trying that will totally brick your phone to the point that they have to replace it."
Doesn't matter if they're stock. Flash an older version over a newer version and u might be looking at a paperweight.
Are u running odin as admin?
Did u try different usb ports/cables like bilgerryan said? Personally i only use usb ports off the back of my pc (cause they're hard-wired to the mb).
Did u make sure that the drivers are all installed correctly? Did u try to update them or reinstall them?
Do u have kies on ur pc?
Did u check the md5 if ur download?
Understand ur frustration,but don't be dissing 6th_hokage. Ever. Goes out of his way to help people in the forums...
Sent from my SPH-L710, using Tapatalk 2 Cyan. ND8. Rooted and rom'd with WICKED-X (HELLS YA!)
Click to expand...
Click to collapse
No "dissing",, and thx for your post. Odd how like minds seem to think the same thing.
Yes, running ODIN as Admin
Tried every USB port after I read bilgerryan's post
All drivers are installed correctly on my system
I have tried it with and without KIES on my system
MD5 was checked and verified
Nothing wrong with my computer. Modified ASUS G75VW. And it helps that I'm a Computer/Network Engineer, so all my systems are always in pristine condition and up-to-date.
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