So, I hope I'm not completely bricked. I was using LGNPST to flash a stock ROM, and at 85%, the phone rebooted and is now in a bootloop that ends in "Security Error". I cannot get to Download Mode either, nor is it seen by ADB (obviously). Can anyone help?
Related
Hi,
My problem started a couple days ago. I had my Samsung Galaxy S2 (I9100) charging overnight and when I woke up it was off. When I turned it back on it was stuck in a boot loop. I could not access recovery mode (although it would enter recovery mode and then drop out) but I could enter download mode. It was running a stock ROM and I had never played around with flashing before.
After leaving it for about a day without power nothing had changed so I started reading up about recovering from soft-brick and possibly the NAND read-write corruption at the guide on XDA here http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771
The guide is a bit old now so some links are broken which made it more difficult for me to figure out what I had to do. Particularly with what file should be going where.
I ended up downloading the same ROM that i think was already on my phone from samfirmware and tried to flash it using Odin (various versions) without success. I tried to flash just the kernel using heimdall which now stops me from even entering recovery mode. I tried to flash everything in the ROM from samfirmware using heimdall but it got stuck on the second file (cache) at 62%, the first file was the bootloader which it said was successful. However now I don’t even get the Samsung logo anymore. I only get "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I still have download mode so I have hope.
I haven’t tried repartitioning yet, is that my next step? Can someone give me instructions on how to determine what the problem is and what I should or shouldn’t be flashing? I’m not against going to a completely new ROM like cyanogen mod either. I need some help from people who have more experience with this.
Thanks for your help, I should be around to answer questions.
Same thing happened to me
Hi, almost the same thing happened to me - except that I was running Cyanogenmod 10 custom rom and I'm not being able to go into recovery mode, but I can go into download mode.
So far I've only managed to worsen things while trying to use odin to write a recovery kernel, so I had a bad firmware upgrade and now instead of powering up to Samsung logo it goes into the "Firmware upgrade encountered an issue" screen. But I'm still able to boot into download mode.
Did you manage to fix your phone? If so, how did you do it?
Dear XDA Members,
My P765 now is on Bootloop, it wont load the OS. Before it happened, the phone was fine with CM 10.2 and CWM Custom. I try to flash again an TWRP which can only use to flash CM 11 Unofficial. After i flash the recovery, it went normal. I restarted the phone, and the phone was working. I copy the CM 11 then i try to flash it by entering the recovery again, but the method just open the fastboot page, not the TWRP. and now the phone bootloop on LG logo. I try hard restart, and it couldnt work. i try to flash again the KDZ but the KDZ updater said my phone not recognized. Does anyone knows what should i do to fix my phone? :crying: Thanks before.
BR,
CR
HELP!!
Even my LG-p765 is stuck in boot loop... actulally ringing boot.
But for me it happened during flashing recovery for the 1st time (i used tool tip for doing it).:crying:
Now my phone shows LG logo (just for a second) and restarts. This keeps happening unless i pull out the battery.
Please post, if anyone know how to recover from this the ringing boot.
If you can manage to get into fastboot and flash uboot and xloader, then connect the phone on software upgrade mode, it should connect. Although there is a catch, THIS WILL RELOCK YOUR BOOTLOADER.
No, it won't. If he install kdz by normal usb cable (not 910k), he will still have unlocked bootloader.
My phone is MDK and used to have TWRP recovery. I was flashing a rom (EMPTY GALAXY) via TWRP and on the reboot it got in the bootloop. The symptoms are:
Can't boot into recovery, simply goes into BOOTING RECOVERY loop
Won;t even start without a cable, I put a charged battery and didn't want to start with just battery.
I reflashed the emergency MDK image via Odin with success, but still can't make the past BOOTING RECOVERY loop. I tried with PIT and without PIT file.
The only thing I can get into is the download mode
Kies 3 says says unsupported phone, while Kies2 keeps trying to connect
Kinda running out of options
I'm working with SGH-337 completely stock and it appears to be soft-bricked. It's stuck in a boot loop, and doesn't get past the Samsung logo and then a black screen before a reboot. It's not "USB debugging enabled". I can access Recovery and Download. I downloaded the firmware from sammobile.com and got an error "nandwrite failed (Auth)" in Odin. I then found a different firmware from a blog online that works, after I get a PASS with that one I'm still in a boot loop after clear a cache\wipe data. I tried it with a PIT file attached. Still in a boot loop. What else can I try? I heard something about a boot loader, where do I get that and how would I flash it. Is it possibly a hardware issue? Please help!
I have been trying for the past 2 days to search for a fix, but I have had no luck. I rooted my phone yesterday and tried to flash custom recovery but when the phone restarted i had the message "recovery is not seandroid enforcing" and just stuck there.
I have tried odin with lots of different stock firmwares and i keep getting different errors, mainly "NAND Write Start, Failed"
Also, i can't boot into recovery as it doesn't turn off, it is always stuck in download mode or in the boot loop.
I am all out of ideas and have no idea how else to fix it
Anyone have any ideas, im still at it and cant figure out a solution
NathanEvanss said:
Anyone have any ideas, im still at it and cant figure out a solution
Click to expand...
Click to collapse
Have you sorted this mate? I can help