Hello friends, my problem is that i can't boot and i can't enter recovery mode. I can enter download mode with jig or with vol + and - with usb cable, i can install fresh firmware but after reboot the phone shows samsung logo, then a progress bar, when the progress bar gets to the end the phone gets stuck with a black screen.
i tried to flash a recovery-clockwork-touch-6.0.3.1-hercules recovery with sucess but i can not enter recovery mode or boot up the phone, and after the reboot i get the black screen described above.
Please help!!
Did you use Odin to flash stock firmware? Did it work??
Yes, i can use Odin to flash a 4.1.2 stock firmware sucessfully, but after reboot it doesn't boot, get stuck after samsung logo.
i was on stock firmware when the phone stop responding and shut it self down.
I upgraded my phone to a 4.4.4 nightly rom from the 4.4.2 stock german rom and the phone will no longer be seen in odin
it also keeps going into download mode, this is without even asking me to press volume up to continue..but even though it is in download mode odin on pc doesnt pick it up.
any help please
thanks
also
the phone will not shut down, I can boot into the nightly rom but not always...a lot of the time it will stay in download mode
if i do get into the nightly rom and choose shut down it just starts back up again and goes into download mode
odin does not see this phone in download mode
my pc does not see this phone when i am in the nightly rom
can someone please help
thanks
I have recently bricked my Note N5120, when trying to flash kitkat. Odin not detecting it, unless i drain the battery to 0% till the screen is flickering or off. I power up with USB then Odin will detect the download mode. With this, I am able to flash any file with Odin.
As for my case, just not able to recover corrupted partitions or hidden folders (?), i am looking for a Odin PIT file now. Wonder if anyone is able to extract it.
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
Hey everyone looking for some help with my friends 32gb s6. He rooted the device last year with no custom recovery (googled and does not remember the site), installed rooted apps and the device was working fine. months later he decided to unroot and go back to stock. Everything was working fine until last week when out of the blue the device went into a boot loop. I told him at take a crack at it and see if i can help. The device does not go into recovery but it does go into download mode. The device does not power down and the battery eventually dies after many many boot loops. I tried to flash BOL1 as he told me that he was on 5.1.1, via odin (3.10.7)and it failed to flash. I was able to get a PIT file from within here:http://forum.xda-developers.com/sprint-galaxy-s6/help/help-galaxy-s6-sm-g920p-t3287963 so this is what i have noticed. If i flash the PIT file and reboot, the device goes into recovery. I then did a full wipe and cleared cache but the device keeps going into the boot loop. I see the samsung logo, then the green android screen and thats it as the device boot loops. I attempted to flash BOJ7 but it failed to flash. The way i can get a TAR file to flash is to flash the PIT file and then the TAR file but the device keeps going into the boot loop. I was able to flash both BOL1 and BOJ7 but experience the same results. I had the most success with BOJ7 after flashing twice but i had to place the device into download mode for me to flash a second time. The device made it past the first samsung screen, i saw the sammy splash screen and then it went into update 1 of 9.....made it to update 3 and then wham back to boot loop. That is as far as i got once I have also noticed that when i flash a TAR file when the device reboots i see the android screen loading the OS and it makes it about a quarter before it says "Erasing" and then the device goes into the boot loop. I have tried various BOL1 and BOJ7 files from the sammobile site and from within what i have found here at XDA but still no luck. I am not sure what else i can do which is why i am asking for help from you fine folks Any help is greatly appreciated.
****Resolved*****
flashed PIT and BOJ7 file from last update here http://forum.xda-developers.com/sprint-galaxy-s6/help/help-galaxy-s6-sm-g920p-t3287963 device still boot looped. I let it sit for a while and then just flashed BOJ7 again without the PIT. Let it boot loop again until BAM began to load. In all prob took about 20 mins of just letting it do its thing, who knew....
Did you try recover it via Smart Switch?
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?