UPDATE: I was able to fix my phone by flashing a stock ROM via Odin, which failed, but it wiped out CWM, so I could access the default recovery, it then successfully wipe my cache in seconds. After that, I was able to follow the custom ROM instructions properly and I am now using the custom ROM!
Random Pieces of Information:
Phone: SGH-T989D
SD Card: 8GB
Carrier: Koodo
Backups: CWM v6.0.1 Backup, ROM Toolbox (Version unknown) App & Data Backup
After browsing for a bit, I finally decided to take a shot at flashing a custom ROM to my phone. I decided to try AOKP http://forum.xda-developers.com/showthread.php?t=1828728&page=430 I downloaded all the files, and started copying them over, but had to leave for around 30 minutes, when I came back, I got ahead of myself and went straight into flashing the ROM without flashing the rest of the listed things, or wiping the data. Immediately after I started the flash, I realized I had done wrong, but I figured pulling the battery would only be worse, so I left it to finish, then rebooted, hoping for some strange reason, it would be fine. It showed my custom boot animation that I had installed on the Koodo stock ROM via ROM Toolbox (Which hadn't worked until then), but after that it just went black. I waited for ~15 minutes and after that, I pulled the battery since I figured it wasn't going to do anything.
In hopes of recovering, I went back into CWM and went to restore, it went through everything until it hit "Restoring cache...", after waiting for 30 minutes, I pulled the battery and went back into CWM to try and wipe the data, it has now froze on "Formatting /cache...". I have now stopped doing anything to it and came here for help.
I realize that around 90% of the things I did were really stupid, but I'm a very independent person who doesn't like getting help for anyone. Now I've hit the point of desperation, since I definitely don't have the cash for a new phone, not even an old school flip phone.
So, I have turned to this forum, ready to follow instructions to the letter, in hopes of fixing my phone. My primary goal is to get my phone functional without paying a penny, so if that means covering my tracks and making it look like I never did anything to void my warrenty, instructions to do that would be great, so I can get it repaired via Koodo. If it possible to get it back to factory defaults and lose every piece of data I had, that would be wonderful too. All I want is a working phone again, so if someone could guide me by posting instructions on how to fix it, or a link to a thread that would help me, that would be great too.
I found this thread, but I am not familiar with what exactly "SoftBricking" is, and whether my situation is refered as such, so if the linked to thread would apply to me, a quick post saying so would be great too. I just don't want to do anything without someone with some sort of experience to advise me, so I can avoid further failure and damage.
EDIT: I decided to try and see if I could at least get into Download Mode, as described by the SoftBricked guide. So here's what I did:
Removed and inserted battery.
I downloaded the listed drivers, ran them, it told me they were already installed and asked me if I wanted to install them anyway, I said yes, just to be safe.
I then held down Vol+ and Vol- and plugged it in. At first, I saw a large grey battery with a spinning circle in it, and felt a vibration, then it went black. Shortly after, it was a smaller battery icon, that was pure white, it then went black again. Windows said it was installing the driver. After a little bit of waiting, it said it failed to install the driver.
I don't know what to do now.
EDIT2: When I try to power on the device without holding any volume keys, it shows me the picture that tells me my device name, then the Koodo loading screen, then starts the default Samsung Boot Animation, but freezes half way, makes a whining sound, then stops and reboots again.
EDIT3: I booted into ClockwordMod Recovery, and mounted my phone, and I am able to view the files on it via my PC, if that means anything.
Just start over with the flashing instructions.
Since you're on CWM:
Flash the super wipe zip
Flash Rom of choice
Flash cache wipe zip
Reboot and let sit for 10 mins
Reboot and go.
If all else fails, find the thread for how to unroot with Odin. It's in the general section (not a sticky).
Edit: here you go http://forum.xda-developers.com/showthread.php?t=1514434
You weren't getting into download mode last time you tried. With your phone off and your battery inserted, hold both volume buttons while plugging in the usb until you see a green android dude.
Sent from my SGH-T989 using xda premium
Corosus said:
Random Pieces of Information:
Phone: SGH-T989D
SD Card: 8GB
Carrier: Koodo
Backups: CWM v6.0.1 Backup, ROM Toolbox (Version unknown) App & Data Backup
After browsing for a bit, I finally decided to take a shot at flashing a custom ROM to my phone. I decided to try AOKP http://forum.xda-developers.com/showthread.php?t=1828728&page=430 I downloaded all the files, and started copying them over, but had to leave for around 30 minutes, when I came back, I got ahead of myself and went straight into flashing the ROM without flashing the rest of the listed things, or wiping the data. Immediately after I started the flash, I realized I had done wrong, but I figured pulling the battery would only be worse, so I left it to finish, then rebooted, hoping for some strange reason, it would be fine. It showed my custom boot animation that I had installed on the Koodo stock ROM via ROM Toolbox (Which hadn't worked until then), but after that it just went black. I waited for ~15 minutes and after that, I pulled the battery since I figured it wasn't going to do anything.
In hopes of recovering, I went back into CWM and went to restore, it went through everything until it hit "Restoring cache...", after waiting for 30 minutes, I pulled the battery and went back into CWM to try and wipe the data, it has now froze on "Formatting /cache...". I have now stopped doing anything to it and came here for help.
I realize that around 90% of the things I did were really stupid, but I'm a very independent person who doesn't like getting help for anyone. Now I've hit the point of desperation, since I definitely don't have the cash for a new phone, not even an old school flip phone.
So, I have turned to this forum, ready to follow instructions to the letter, in hopes of fixing my phone. My primary goal is to get my phone functional without paying a penny, so if that means covering my tracks and making it look like I never did anything to void my warrenty, instructions to do that would be great, so I can get it repaired via Koodo. If it possible to get it back to factory defaults and lose every piece of data I had, that would be wonderful too. All I want is a working phone again, so if someone could guide me by posting instructions on how to fix it, or a link to a thread that would help me, that would be great too.
I found this thread, but I am not familiar with what exactly "SoftBricking" is, and whether my situation is refered as such, so if the linked to thread would apply to me, a quick post saying so would be great too. I just don't want to do anything without someone with some sort of experience to advise me, so I can avoid further failure and damage.
EDIT: I decided to try and see if I could at least get into Download Mode, as described by the SoftBricked guide. So here's what I did:
Removed and inserted battery.
I downloaded the listed drivers, ran them, it told me they were already installed and asked me if I wanted to install them anyway, I said yes, just to be safe.
I then held down Vol+ and Vol- and plugged it in. At first, I saw a large grey battery with a spinning circle in it, and felt a vibration, then it went black. Shortly after, it was a smaller battery icon, that was pure white, it then went black again. Windows said it was installing the driver. After a little bit of waiting, it said it failed to install the driver.
I don't know what to do now.
EDIT2: When I try to power on the device without holding any volume keys, it shows me the picture that tells me my device name, then the Koodo loading screen, then starts the default Samsung Boot Animation, but freezes half way, makes a whining sound, then stops and reboots again.
EDIT3: I booted into ClockwordMod Recovery, and mounted my phone, and I am able to view the files on it via my PC, if that means anything.
Click to expand...
Click to collapse
I assume you didnt flash TDJ super wipe? what you got is a softbrick the linked you have is fine, but i fixed mine by flashing the same recovery you used when you rooted your phone. and then make sure you wipe everything even use supewipe. then restore with nandroid backup. One thing though you sound like you didnt root the phone with your computer as you dont have your proper drivers. check here http://forum.xda-developers.com/showthread.php?t=1513359 and here http://forum.xda-developers.com/showthread.php?t=1650908 it may help you. You can also find the odin koodo rom and go all stock. remember when you see the yellow brick on odin it means it recognize your phone
by the way some recoveries seems to hang on me too even the one we use to root. thats why I let rom manager to flash my recovery
How long is DARKSIDE supposed to take? It seems that the loading bar hasn't moved in a really long time. Just like when I was using the built-in CWM wipe, it is freezing on the cache.
Corosus said:
How long is DARKSIDE supposed to take? It seems that the loading bar hasn't moved in a really long time. Just like when I was using the built-in CWM wipe, it is freezing on the cache.
Click to expand...
Click to collapse
5mins
Sent from my SGH-T989 using xda app-developers app
After giving up on getting the cache to wipe, since that's clearly not working, I remembered that the first time I got to Download Mode was by holding one volume button and pressing the power button. This worked for me, so I was able to open Odin and try to flash the stock that way, unfortunately, it failed. This is the output:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T989UVLE1_T989TMBLE1_T989UVLE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<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.ext4
<ID:0/005> amss.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
TDJ doesnt take 5 minutes to flash. On the odin side you may have a corrupt file, try downloading it again or just flash the recovery you used to root. and they on recovery wipe everything and restore to a nandroid backup
I have a Sprint Note 4 that supposedly had a custom ROM installed on but I believe the digitizer is broken. Nothing shows up on the display. I booted into DOWNLOAD MODE using Home Power and volume down and flashedN910PVPU1ANK2_N910PSPT1ANK2_SPR then N910PVPU1ANIE_N910PSPT1ANIE_SPR via ODIN It sounds like its stuck in a boot loop after both flashes, but ODIN says PASSED when it finishes. Since I can't access the screen, how can i get this flashed back to a stock rom? Any help would be greatly appreciated.
I'm confused; why flash two stock tars? Did you let the phone boot after flashing the first stock tar?
I'd suggest a factory reset in recovery, power down, Odin the factory tar of your choice and let it auto boot. You should see the phone boot into into recovery briefly on the auto boot when flashing stock tar in Odin, then fully boot. If not seeing the brief recovery, start over and try again.
I recall a YouTube video on a digitizer issue that may have been resolved. The guy had a dead spot on the digitizer. I think it only suggests a possible fix in a follow-up video the user posted. But maybe the stock tar will fix it.
why flash two stock tars?
After flashing the the first one, it just kept rebooting. That was last night. Today I flashed the older one. I'm trying install ADB on my Windows 7 desktop to enter recovery.
So you can't do power down, volume up, home plus power to get to recovery?
The stock kernel won't allow adb access; permission denied when booted. Haven't tried adb on a boot loop; don't know if it lets you in or not.
Did you check the md5 for match prior to Odin? Maybe bad download?
Have you tried Odin without the sdcard installed. Bad user data or root directory data bad?
You could Odin the TWRP tar recovery and wipe everything but recovery and boot partition. Then Odin the stock tar after a power down.
Be careful not to select repartition during Odin. There was a PIT file posted but AFAIK, no one has shared a successful experience using the repartition with PIT file. Anyone correct me if I'm wrong and post a link to correct PIT file to use. Please.
samep said:
So you can't do power down, volume up, home plus power to get to recovery?
The stock kernel won't allow adb access; permission denied when booted. Haven't tried adb on a boot loop; don't know if it lets you in or not.
Did you check the md5 for match prior to Odin? Maybe bad download?
Have you tried Odin without the sdcard installed. Bad user data or root directory data bad?
You could Odin the TWRP tar recovery and wipe everything but recovery and boot partition. Then Odin the stock tar after a power down.
Be careful not to select repartition during Odin. There was a PIT file posted but AFAIK, no one has shared a successful experience using the repartition with PIT file. Anyone correct me if I'm wrong and post a link to correct PIT file to use. Please.
Click to expand...
Click to collapse
I tried without SD card and I didn't check repartition in ODIN. The md5 matched on both.
Did you try the suggestion of using TWRP to wipe partitions prior to stock tar? Look next to last paragraph of previous post.
Only other advice I can think of ATM is that the stock tars are so large, it takes a few moments to verify once selected. I leave my phone USB disconnected until Odin has verified the tar selected. Then I plug the USB and make sure I have the COM pop-up prior to start. If not, disconnect and reconnect the USB until COM is displayed. Not sure but I think there were some posters that didn't really flash the stock tar in Odin.
samep said:
Did you try the suggestion of using TWRP to wipe partitions prior to stock tar? Look next to last paragraph of previous post.
Only other advice I can think of ATM is that the stock tars are so large, it takes a few moments to verify once selected. I leave my phone USB disconnected until Odin has verified the tar selected. Then I plug the USB and make sure I have the COM pop-up prior to start. If not, disconnect and reconnect the USB until COM is displayed. Not sure but I think there were some posters that didn't really flash the stock tar in Odin.
Click to expand...
Click to collapse
How can I use TWRP without the screen?
thanks
Sorry but I got focused on the boot loop issue and lost focus on the screen issue.
No screen has me wondering how you know you're in download mode to flash Odin tar?
Starting over, I've never used kies but there was a similar problem in this thread I found with Google.
www.androidpit.com/forum/606685/phone-no-os-or-cwm-or-download-mode-please-help
Scroll down to post 10 for instructions.
Anyone else have experience or suggestion to share? Please jump in.
samep said:
Sorry but I got focused on the boot loop issue and lost focus on the screen issue.
No screen has me wondering how you know you're in download mode to flash Odin tar?
Starting over, I've never used kies but there was a similar problem in this thread I found with Google.
www.androidpit.com/forum/606685/phone-no-os-or-cwm-or-download-mode-please-help
Scroll down to post 10 for instructions.
Anyone else have experience or suggestion to share? Please jump in.
Click to expand...
Click to collapse
I went by feel....and the fact that Odin said COM connected. and PASSED
kevg77 said:
I went by feel....and the fact that Odin said COM connected. and PASSED
Click to expand...
Click to collapse
So you pulled the battery, pressed and held volume down, home and power buttons until it vibrated, waited to make sure it wasn't just booting, when satisfied, you pressed volume up; right?
I'd say that is a sufficient feel.
If the Odin or kies update won't take and screen is dead; with no adb access, who would know what's on the phone unless it's just not playing the right boot tone when it keeps rebooting? Problem?
I think that may be enough to take your phone back to point of sale and ask for replacement without worrying about root voiding warranty?
Did you try the Kies update?
I am familiar with the Note 3, thats how I was able to get it into Download mode by feel. I tried KIES and it said that my device is not supported. Im using the latest version of KIES. I know I'm running into an issue with the usb driver recognizing...Im on Windows 10 technical preview. thinking about trying it on an old Win7 laptop.. thanks for the advice
Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?
Try to flash newest rom via odin using pit file.
What is the Odin error message? What file fails to flash? Is Odin able to pick up the partition information from the phone?
audit13 said:
What is the Odin error message? What file fails to flash? Is Odin able to pick up the partition information from the phone?
Click to expand...
Click to collapse
Hi audit13's Avatar. Thanks for your reply.
The file i downloaded from samsung. The offical rom N7100XXUFNL1
Below is what shows in the measage window.
<OSM>N7100XXUFN1_N7100EURFNG1_N7100XXUFNG1
<OSM>Chaecking MD5 finished successfully..
<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>Set PIT file
<ID:0/005>DO NOT TURN OFF TARGET!!
<ID:0/005>Can't open the specific file.. (Line: 1876)
<OSM>All threads completed. (Succeed 0 / failed 1)
I dont understand the 3rd question... how do u check that?
zett89 said:
Try to flash newest rom via odin using pit file.
Click to expand...
Click to collapse
Thanks for your reply. Not sure how to that?
You're using the latest rom from sammobile.com? If you are, you're unzipping it to have a tar.md5 file? Looks like you may not need a pit file as Odin is able to read the pit information from the phone.
audit13 said:
You're using the latest rom from sammobile.com? If you are, you're unzipping it to have a tar.md5 file? Looks like you may not need a pit file as Odin is able to read the pit information from the phone.
Click to expand...
Click to collapse
What should i do then. Could you walk through it as im a bit of a novice...
You may not need a pit file as Odin looks like it can read the information from the phone. Try flashing the stock ROM from Sammobile.com.
If the ROM doesn't flash, try different USB cables and USB ports.
download newer version of Odin HERE
and uncheck repartition.
yaro666 said:
download newer version of Odin HERE
and uncheck repartition.
Click to expand...
Click to collapse
Will do. I will keep you posted...
So for the last week my note 2 would just do random reboots like once or twice a day, then started to do few times a day and now it goes to Samsung note 2 screen and sits there. I popped out the battery and went into recovery mode cleared the cache tho sure did nothing.
The phone has never been modified or rooted in anyway. I've owned since new. Is there a fix for this? Sorry I'm a newb. If the phone is toast I do have insurance on it so not worried about that. Just wanna know if I can either fix or if not can I get the data off it somehow?
I've included a pic of the screen...
Thanks!
Try flashing a stock ROM via Odin.
I have the same exact issue. It happened randomly. No root. Stock ROM. I tried flashing stock rom via odin but it fails.
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
Anything I flash fails with nand write. I'm about to lose hope :S
Are you using the original Samsung USB cable? Tried different USB cables and USB ports? Post the complete Odin log?
If the phone is no longer usable is it possible to recover my data at least?