Picked up an S3 from someone that I have no idea what they had done to it. Its possible it was flashed with the i9300 noobness. No idea.
It does not boot to any screen. HOWEVER, i can power it up into download mode.
So I tried reflashing some stock images for T-mobile, And it does not boot no matter what I do. It will power up into download mode only.
Recovery mode tries. Itll come up Recovery Booting... for a quick second then go away. But it never comes up. Tried letting go of the buttons at the blue text, etc.. no dice.
I tried erasing NVRAM on the factory image flash and it didnt change anything on the recovery either. tried flashing CWM to recovery, same deal.
Normal boot I get nothing. just a vibrate and black screen. no logos.
Download mode shows this:
ODIN MODE
Product Name: SBG-T999
Custom Binary Download: (Yes) 5
Current Binary: Custom
System Status: Official
Qualcomm Secureboot Enable
It did say Binary Official before I reflashed a kernel or some sorts for tmobile to see if it would boot. same thing.
Any ideas?
Only thing I havent tried is bootchain, and I cannot find the bootchains for T-mobile. I also havent tried reparitioning as I cant find any info or PIT files for this device.
I think its screwed up partitions. I flashed the 4.0.4 ROM onto the device, even used the correct PIT.
Samsung logo will show now for a quick second and shuts down. Try recovery mode, Same thing but shows the blue text with samsung logo. Then shuts down.
I have no way to log the kernel to find out where the fault lies but I bet its messed up partitions.
Does it need jtagged? Reason why I ask is it still goes in download mode, but the PIT didnt help. Neither did nand erase on factory ROM.
Did you ever see it run? Kinda sounds like the internal memory is bad.
Sent from my SGH-T999 using xda premium
Recently, I was just playing games on my Tab then suddenly it froze and reboots. It was then stuck at 'samsung galaxy tab 3', not the samsung logo. Even if I restarted my Tab or charged it, it always get stuck at that 'samsung galaxy tab 3' logo.
The problem is: I can't access Recovery mode, all I can do is go to download mode.
I tried to flash any roms available here on xda via odin, still no luck. I even tried to flash the stock firmware. After it successfully finished flashing, still no luck.
What I have noticed after flashing the latest stock firmware:
1. download mode - System status was still on custom
2.download mode - RP SWREV: A1 shows up!
Still can't access Recovery mode.
Any help would gladly appreciated..
Flash a new recovery over Odin, this should fix the Access to the recovery
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
Alright, so I had my Samsung Galaxy Tab 3 7.0 (SM-T210R) rooted and had a custom recovery and ROM flashed. (TWRP and RocketTab respectively.) Nothing was wrong, everything worked fine, and then the battery died. I didn't plug it up immediately because I didn't really have a need to, but when I did this afternoon, it was stuck in a boot loop, infinitely repeating the Samsung Galaxy Tab 3 splash screen. So I tried to go into recovery mode and back it up, but I couldn't. Recovery mode would not open, even during the boot loop while charging. (I think it was charging anyway.) I can get it to go into download mode fine, but it will not go into recovery mode no matter what I do. Before starting trying pretty much anything I could find that looked reputable, download mode said:
ODIN MODE
PRODUCT NAME: SM-T210R
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
HW REV: 0x5
After trying to flash the stock rom and recovery, it says:
ODIN MODE
PRODUCT NAME: SM-T210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
And I am still unable to get into recovery, and it is still stuck in the boot loop any time I plug it up. I should also mention, that no button combinations or even just the power button do ANYTHING when the tablet is off, but I know the battery is ok because if I plug it up, get it into download mode, and then unplug it it's fine. It's just during the boot loop.
I'm honestly just lost. Can anyone please help?
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?