[Q] Cannot fix bootloop for SGH-T889V - T-Mobile Samsung Galaxy Note II

I bought a slightly used Samsung Note 2 Sgh-t889V [Canada Moblicity , I think] phone with a bootloop problem [person tried to root with jedi and messed up,tried to correct, messed up again, gave up!!] which I thought I could maybe try to fix, but no luck.
Things I have done so far
files I downloaded
- T889VVLALJ4_T889VYVLALJ4_T889VVLALJ4_HOME.tar [stock rom, I hope! downloaded a couple different times]
- Odin3v185
-Did the vol down,home button,power button,then vol up to get downloading screen
says top left corner
ODIN MODE
PRODUCT NAME:SGH-T889V_NA_VTR
CUSTOM BINARY DOWNLOAD: Yes (34 COUNTS) [[[[ Big problem right here!!!!!!!!!!!]]]]]
CURRENT BINARY: Samsung Official
SYSTEM STAUS: Custom
I opened up Odin, checked off PDA and Load file-T889VVLALJ4_T889VYVLALJ4_T889VVLALJ4_HOME.tar [only auto reboot checked in opitions] avg 5 to 6 mins later
Odin does it's thing, goes to reboot phone,
reboots [passes in ODIN] [first thing shows up on screen SAMSUNG [nothing else], then makes sound and then that swish blue picture comes up and goes back to SAMSUNG[stays for a few seconds and then repeats over and over again]
I pulled the battery, go into
Android system recovery <3a>
-wipe data/factory reset
-press reboot system now
Goes into the loop again same thing SAMSUNG,swish,SAMSUNG and repeats [nothing else]
I have tried a couple different times/different usb ports, different samsung usb cable, same results[ From a look of things the previous owner tried multi times doing something also]
Is there anything else I can try or is this like done like dinner[I hope not]
Any help would be greatly appreciated

ruffneck30 said:
I bought a slightly used Samsung Note 2 Sgh-t889V [Canada Moblicity , I think] phone with a bootloop problem [person tried to root with jedi and messed up,tried to correct, messed up again, gave up!!] which I thought I could maybe try to fix, but no luck.
Things I have done so far
files I downloaded
- T889VVLALJ4_T889VYVLALJ4_T889VVLALJ4_HOME.tar [stock rom, I hope! downloaded a couple different times]
- Odin3v185
-Did the vol down,home button,power button,then vol up to get downloading screen
says top left corner
ODIN MODE
PRODUCT NAME:SGH-T889V_NA_VTR
CUSTOM BINARY DOWNLOAD: Yes (34 COUNTS) [[[[ Big problem right here!!!!!!!!!!!]]]]]
CURRENT BINARY: Samsung Official
SYSTEM STAUS: Custom
I opened up Odin, checked off PDA and Load file-T889VVLALJ4_T889VYVLALJ4_T889VVLALJ4_HOME.tar [only auto reboot checked in opitions] avg 5 to 6 mins later
Odin does it's thing, goes to reboot phone,
reboots [passes in ODIN] [first thing shows up on screen SAMSUNG [nothing else], then makes sound and then that swish blue picture comes up and goes back to SAMSUNG[stays for a few seconds and then repeats over and over again]
I pulled the battery, go into
Android system recovery <3a>
-wipe data/factory reset
-press reboot system now
Goes into the loop again same thing SAMSUNG,swish,SAMSUNG and repeats [nothing else]
I have tried a couple different times/different usb ports, different samsung usb cable, same results[ From a look of things the previous owner tried multi times doing something also]
Is there anything else I can try or is this like done like dinner[I hope not]
Any help would be greatly appreciated
Click to expand...
Click to collapse
I'm having the same problem. I got the thing to finally boot by flashing the modem from the Rogers/AT&T Note II (SGH-I317M I believe). That got rid of the bootloops but then I had no IMEI and wasn't capable of making called. Try flashing the I317M modem and hopefully your bootloops will go away.
Let me know if you come across a solution, since I need it too

That seems like a Videotron device... any updates on this please?

Related

Black Screen after Rom Flash with Odin

Where to start... So I Flashed a stock rom "M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar" with Odin to my M919 3 times with the same result.
Used Odin 307 with PDA and only Auto Reboot checked each time. Flash went fine completed successfully with Pass each time. Unfortunately that's where the
success ended. The phone rebooted with the TMobile Logo and Samsung logos flashing on screen and immediately went "Samsung is Upgrading 155 applications."
After this process it rebooted once again Flashing the TMobile and Samsung logos. Once booted, the phone screen is black with no icons. At the very top of the
screen, I have a battery icon, the time, 4 bars despite having no sim card in and that little eye icon. At the bottom, the back and menu buttons light up when
touched. The phone is recognized by windows and does allow me to browse the file folders. On the off chance that my file was corrupted somehow, I downloaded it
from a second source the 2nd and 3rd times I flashed it. Now I'm stuck. Nothing I do changes this condition.
Please Help!
** After several attempts I managed to get the phone into recovery mode. Unfortunately the phone Is still having issues. The TouchWiz is back and all the icons, it goes through the setup process but it's unable to turn wifi on and it doesn't seem to see my sim card. Aside from a hardware failure of some type, I don't know what this could be.
insomni said:
Where to start... So I Flashed a stock rom "M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar" with Odin to my M919 3 times with the same result.
Used Odin 307 with PDA and only Auto Reboot checked each time. Flash went fine completed successfully with Pass each time. Unfortunately that's where the
success ended. The phone rebooted with the TMobile Logo and Samsung logos flashing on screen and immediately went "Samsung is Upgrading 155 applications."
After this process it rebooted once again Flashing the TMobile and Samsung logos. Once booted, the phone screen is black with no icons. At the very top of the
screen, I have a battery icon, the time, 4 bars despite having no sim card in and that little eye icon. At the bottom, the back and menu buttons light up when
touched. The phone is recognized by windows and does allow me to browse the file folders. On the off chance that my file was corrupted somehow, I downloaded it
from a second source the 2nd and 3rd times I flashed it. Now I'm stuck. Nothing I do changes this condition.
Please Help!
** After several attempts I managed to get the phone into recovery mode. Unfortunately the phone Is still having issues. The TouchWiz is back and all the icons, it goes through the setup process but it's unable to turn wifi on and it doesn't seem to see my sim card. Aside from a hardware failure of some type, I don't know what this could be.
Click to expand...
Click to collapse
I sent you a PM that may or may not help. Let me know.
re: error fixes
DarkMenace said:
I sent you a PM that may or may not help. Let me know.
Click to expand...
Click to collapse
Have you tried going into recovery and doing a "Factory Reset" and reboot, it might fix the problem.
Also if it does not fix all the problems you can try to boot the phone up just to get into the SETTINGS
screen, then goto settings>accounts tab>backup and reset> and select "Factory data reset" then
reboot the phone if it does not reboot on it's own.
Good luck!

Issue trying to update to 4.3

(Originally posted this in the wrong forum, so I am reposting here.)
I have the Galaxy Note II with T-Mobile.
Some background: It was running Android 4.1.2. I rooted my phone once, about two weeks ago, just so I could take an image of it in case of an update issue. (I think the software was called nandroid.) Once I took the backup, I unrooted it again.
Since then, doing the Software Update check under settings never returned any results. It would just keep checking until I clicked cancel.
Anyway, when T-Mobile released the 4.3 update Monday morning, I tried updating to it using the Kies software on my PC (by connecting it through the USB cable). It got up to about 60% installation and then just hung for over an hour. So I unplugged the phone, re-plugged it back in, and then attempted the emergency firmware recovery through Kies. It went through this and got upto 76% installation and then just hung again for another hour. I again unplugged it to re-try the emergency recovery again, but every time I connected the phone, Kies would not detect it again. I re-seated the battery, rebooted my computer, uninstalled and reinstalled Kies, but Kies would not detect my phone again.
I am/was running the stock rom, but my phone won't even boot into it's normal screen. Any time I turn it again, i see the screen--"there were errors during firmware upgrade. try emergency recovery in Kies."
I can't even figure out a way to get to a screen where I can install the image I took using Nandroid a few weeks ago.
Any help or advice anyone can provide would be extremely appreciated!
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Double0EK said:
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Click to expand...
Click to collapse
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
diggeryo said:
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
Click to expand...
Click to collapse
Try installing SuperSU from Playstore
It has an option of doing a FULL UNROOT
I am sure that will help.
If not then install Rom Manager from PS
Through RomManager reboot in Recovery
1.) Wipe device 3x times
2.) Wipe cache 3x times
3.) Under advance you will Find Dalvik Cache -- wipe that 3x times
[MENTION=522570 [MENTION=1065870 [user=1879310]@@@@[/user][/MENTION]@@[/MENTION]@@
But more importantly why would you want 4.3 stock anyway?
Install TWRP Recovery or ClockWorkMod recovery and install/Flash CM1 (Cyagonemod) or any other custom roms 4.4.x kitkat
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Just do this un root with chain fire root away app.
Then use triangle away app.
Then find 4.1.2 MB1 stock Odin tar. The complete package .
Odin to stock .
Reboot and then update via Ota.
You have to un root first and also have to triangle away which removes flash counter in Odin.
System modified status will not allow Ota.
That's the best suggestion I have
Sent from my SGH-T889 using xda app-developers app
diggeryo said:
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Click to expand...
Click to collapse
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Sent from my SGH-T889 using XDA Premium 4 mobile app
wolfpack612 said:
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Click to expand...
Click to collapse
I have. It brings me to the same screen with the Samsung Galaxy Note II text on the black background and just stays there.
So, in summary, I can get into download mode (vol down+home+power), but it seems nothing else.
Try factory settings the phone through stock recovery and then check your phone status. It should say 'normal' but if it says 'modified,' download Triangle away and run the tracking setting (it'll make your phone say normal so you can download the OTA). Given you're on tmobile and your phone is the T889 model, check for software updates and install the OTA. Your phone will take a bit and will probably be stuck on the T-Mobile 4G boot screen for several minutes (it's normal). This should work.

Not your Usual Boot Loop

Hi Guys hoping someone can help me out.
One of my friends who should know better decided to try and flash a custom rom to his N7105 trouble is he used a n7100 twrp which apparently installed and then tried to flash a n7100 rom .
Now his phone is stuck in a boot loop, it sometimes gets as far as the animated boot logo with the blue led pulsing depending on what I last did to it lol. I can get into both download and recovery and the power button isn't stuck.
I don't know what stock version the phone was one when he started messing with it and he is vague about everything HE tried to do to fix it before I got my hands on it. Its entirely possible it was on 4.1.2 to start off with and he's tried to go straight to lollipop does the 7105 need to update in increments? or could he have put a n7100 bootloader on somehow but flashing stock via Odin should fix that right?
I have a memory of people having this sort of problem years ago with HTC and it ended up being a mismatch between the modem and baseband versions or something like that, thoughts?
Here's what I've tried
Odin flash CF-Auto root as it restores stock recovery at least now the PC detects it as t0lte not t03g
1) Recovery wipe data and cache - now only gets as far as the initial samsung galaxy note II screen
2) Odin flashing a 4.1.2 rom from sammobile - no go "unsupported" so has a knox bootloader
3) Odin flashing a 4.3 rom from sammobile - hangs on animated boot logo with the blue led pulsing
tried 1 again same result
4) Odin flashing a 4.4.2 rom from sammobile - hangs on animated boot logo with the blue led pulsing
tried 1 again same result
5) Install firmware via Kies - hangs on animated boot logo with the blue led pulsing
tried 1 again same result
Odin Flash proper version of twrp 2.8.7.0
6)Fix permissions in TWRP - says sucessfull but also has "E: unable to mount data" etc back to the initial galaxy note II screen
7) Flash custom rom via twrp - hangs on animated boot logo with the blue led pulsing
tried 1 again same result
I'm running out of ideas and patience with this thing does anyone have any other ideas for me to try?
After leaving the phone for a while to prevent me from smashing it into a million bits with the biggest hammer I could find I got it working tonight.
Charged the phone up I had to disconnect and reconnect a few times as it said it was 100% on the full screen battery picture then in recovery it said 18% or something
I re-flashed N7105XXUFNL2_N7105H3GFOD1_H3G from sammobile using Odin 1.85 along with the PIT file from this thread checking re-partition (I used a pit file otherwise I'd leave this alone), Auto Reboot, F.Reset time and Phone Bootloader update. This seemed to take longer than previous flashes.
Flashed TWRP 2.8.7.0
formatted Data in TWRP (the advanced one where you have to type yes to confirm). Previously Data was unmountable so I assume the long flash fixed something there.
Wiped cache in TWRP
and rebooted and waited ages and it came to life

Galaxy Note 2: Stuck In Bootloop

NoteII Randomly stuck in a bootloop with no access to recovery
I looked for two days around the web for fixes to this, tried flashing everything from roms (if i understand it correctly it's like a phone OS), through custom recoveries (the things that show up after the up/home/power button combo) and even a kernel. I know that I honestly shouldn't have done that without the full knowledge of what I did, but at 3AM I didn't think much. I think i even tried using PIT, but it got stuck and didn't go through.
Okay, specifics:
One day I pick up my phone and notice the big white letters - " (...) note II" etc, standard bootloop. Kinda surprising since I didn't do anything to the phone, but It had some problems before like deleting like 4-5 apps randomly once, or an icon or two disappearing. I tried the obvious method of recovery mode and clearing caches and such, but it didn't work:
after the button combination it briefly showed the "teamwin" blue logo of my recovery i used to have for like 2 years, and then it goes black, and the white letters show up again. Only the download mode shows up. Odin detects the phone and when i flashed a stock rom and some recoveries on it, odin said they "passed", but no change ensued, the recovery still showed teamwin's, even after flashing clockwork recovery, or whatever it's called. I basically accomplished nothing, and I need to know what to do specifically to fix the phone, without bricking it even more. can you guys point me in the right direction, or maybe try to diagnose the problem? Thanks.
-no recovery
-recovery flashing doesn't change anything
-download mode works, odin detects the phone
I've got the impression that you're trying to make two steps in one. I suggest to flash firmware through Odin, reboot, setup and then make wipes and factory reset in stock recovery. Then flash the custom recovery through Odin and all should be fine again.
Reminder: Don't flash firmware beneath your current bootloader version.

Debrick process: can't enter Recovery mode

Hello everyone,
My phone (S4 mini GT-I9195) decided all of a sudden to stop working. I couldn't boot it, charge it, nothing but a black screen. After some research on the world wide web, I came to the conclusion that it might be "bricked", as the cool kids call it. I came upon a guide on this website that seemed promising: https://forum.xda-developers.com/showthread.php?t=2600869
I followed the instructions, found a debrick.img corresponding to my GT-I9195, put it on a sd card and managed to boot the phone.
Next was entering Download mode and flash with a stock firmware via Odin (v3.09). I used a 4.4.2 firmware I found on Sammobile (I9195XXUCNK4_I9195QXZCOA1_XEF) corresponding to my region and phone.
Everything went fine with Odin, I waited until it said "PASS!" and rebooted the phone.
The next step was to enter Recovery mode, and that's where I have a problem. I use the combination "Volume up + Home + Power" to enter it, it vibrates once, shows me the Samsung logo (+ model) with "Recovery booting...." written in blue on the top left corner, I release all the buttons, and after a few seconds, it goes to a black screen, it vibrates twice and reboot on the Samsung logo, but without the "Recovery booting..." message on top left corner. After that, it enters a bootloop that only ends when I remove the battery.
So, I can never enter the recovery mode (I tried multiple times, with different methods, such as releasing only the power button, but to no avail) and cannot complete the debrick guide. I tried different stock firmwares but always with the same result.
Did I do something wrong? What can I do differently to enter recovery mode? Should I prepare the funeral for my phone?
Thank you in advance for your answers.
You should try flashing cwm with odin, then formating your system partition, if you can externally put a rom on your memory card then do so, after that install that rom on your phone, if that doesn't work then try flashing your stock firmware after you had done everything...Of course I don't know if any of this will work because I haven't run into a issue like this before, though one time my recovery was blocked and flashing cwm on it fixed it, instead of flashing stock firmware I went for cyanogenmod (now lineage os) so it might work for you, who knows.
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
paupiette said:
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
Click to expand...
Click to collapse
I have TWRP on my mini. When I first flashed TWRP (3.0.2.1) via Odin, I had to manually boot into recovery by holding VolUp+Home+Power as soon as I see PASS!, BEFORE the phone automatically reboots.
I have to try this a couple times to get TWRP to stick. From what I read, if you let the phone boot automatically after flashing from Odin, it will automatically overwrite the new flash with stock Samsung recover (which is bad in your case.) So you have to interrupt this by a manual reboot before the phone does its thing. If you are successful, you should boot directly into TWRP on the manual reboot. From then on TWRP will overwrite the stock recovery and you will be good to go.
I find the timing of this manual reboot a bit tricky on the phone. Do it too soon, and the TWRP was not flashed, a second too late, and the phone boots to stock. I had to try that a few times to get it right. Basically, be ready with the buttons and press it the instant you see PASS! So maybe you can try flashing TWRP again before giving up.
I have encountered the same problems today. After waking up, my phone (S4 Mini) told me an update (17 MB) was available. Happy about still getting updates, I started the process and the telephone rebooted. When returning ten minutes later it was all dark and wouldn't respond to any button combination. After working through a lot of threads and forums, trying to fix the problem, I managed to get a debrick image for the phone as well as the right firmware from Sammobile (which is astonishingly the same one that paupiette uses, though I'm from Germany, but the phone seems to have a French regional code).
At first I wasn't able to get to the Download Mode, instead my phone always told me this while denying my attempts to flash it:
BOOTE RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY..
WRITE 139008 sectors..
FLASH WRITE FAILURE
ddi: mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RPSWREV: 2
WRITE PROTECTION: Enable
Nothing seemed to work and some other topics on different forums blamed the internal flash chip (eMMC) to be the cause for all the trouble. I gave up on my phone, loosening the skrews on the back to get a look on the board. Before ripping apart the last bits, I tried to start the Download Mode one more time, so I put in the battery and hold the three buttons. Et voilĂ  - the phone came up with that white booting screen. It was looping this process over and over as paupiette had allready described. I managed to start the Download Mode and flash with Odin3 (v3.12). A green "PASS!" told be, it worked until it began to enter the loop of rebooting again unable to enter the Recovery Menu.
So close but yet so far away from what I want.
Any new ideas or suggestions?

Categories

Resources