My phone was rooted using Kingo Root, I flashed SlimKat rom, when I tried using Odin to flash back to stock, it bricked, it doesn't boot, it goes directly to "Firmware Upgrade Encountered an issue. Please Select recovery mode in Kies & try again"
I tried using Kies, it won't detect it, I had two techns who tried legally they can't do anything obviously, it won't even boot into recovery bootloader.
Is my phone really dead?
WOOO. Thank you XDA, all I had to do was flash a custom recovery again, and it booted no issues,
Odin probably tried to downgrade your bootloader. If you were on a bootloader at or beyond MJB that is probably what bricked your phone.
You might be able to bring it back with a debrick image. Debrick images are usually specific to your bootloader, so if you know what firmware you were running prior to this it would be helpful.
You'll need an external SD card to stand in for your internal storage until you get things synced back up, and you'll have to do some very specific formatting and image writing to that external SD.
Search the forums for debrick image and you should find some helpful threads. I've never had to do this myself, but I have heard some success stories. Good luck.
If you see the upgrade firmware screen, your phone is not totally bricked.
Can you get into download mode? If you can, just flash a custom recovery, flash the latest cm10.2, verify your boot loader, and post back here.
audit13 said:
If you see the upgrade firmware screen, your phone is not totally bricked.
Can you get into download mode? If you can, just flash a custom recovery, flash the latest cm10.2, verify your boot loader, and post back here.
Click to expand...
Click to collapse
I can go into downloading mode, I flashed CWMS3ATTrecovery before thats what was on it.
Copy the most recent cm10.2 to an external SD card.
Use Odin to flash the most recent tar.md5 from Philz for the d2lte from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
After flashing Odin, boot to recovery and flash cm10.2 so you can get your phone running and determine the bootloader on your phone.
Related
Hi all,
I have a soft-bricked GS3 that I can't revive even after using odin 3.09. Hope you guys can help.
My encrypted phone was running CM10.1.3 and I decided to update it to CM10.2 using sideload. That didn't go well and I was stuck with the CM bootloop.
So after several tries with sideloading I decided to use odin to turn it back to stock. I tried both the stock LG1 and LK3 and both went thru the flash without issues but after the phone reboots it asks for the encrypted storage password. After the password entry it's stuck at the samsung logo bootloop. (p.s. LG1 recognized my encryption p/w but LK3 didn't)
I had flashed using odin on an encrypted phone before and I don't think the encryption stays after the odin flash. Am I missing something like flashing the bootloader together with the .tar file? I tried searching and google but can't seem to find an answer.
Any suggestions? Thanks!!!
gowenf said:
Hi all,
I have a soft-bricked GS3 that I can't revive even after using odin 3.09. Hope you guys can help.
My encrypted phone was running CM10.1.3 and I decided to update it to CM10.2 using sideload. That didn't go well and I was stuck with the CM bootloop.
So after several tries with sideloading I decided to use odin to turn it back to stock. I tried both the stock LG1 and LK3 and both went thru the flash without issues but after the phone reboots it asks for the encrypted storage password. After the password entry it's stuck at the samsung logo bootloop. (p.s. LG1 recognized my encryption p/w but LK3 didn't)
I had flashed using odin on an encrypted phone before and I don't think the encryption stays after the odin flash. Am I missing something like flashing the bootloader together with the .tar file? I tried searching and google but can't seem to find an answer.
Any suggestions? Thanks!!!
Click to expand...
Click to collapse
Can you try booting into recovery and doing a hard wipe/factory reset? If you flashed a stock *.tar file via Odin, it should deliver a complete stock system with all partitions updated. There shouldn't be need to flash a bootloader separately.
Larry2999 said:
Can you try booting into recovery and doing a hard wipe/factory reset? If you flashed a stock *.tar file via Odin, it should deliver a complete stock system with all partitions updated. There shouldn't be need to flash a bootloader separately.
Click to expand...
Click to collapse
Got it. Thanks!! I kept thinking that I couldn't use the recovery because CWM does not see the encrypted partition and therefore cannot do a hard wipe. I totally forgot that after odin I was back to stock recovery and therefore could do the wipe. Thanks again!!
I tried to factory format my phone through TWRP, then when I tried to restart again, it never comes back.
I still have access to TWRP, but when I install zip files I downloaded, it always failed. I tried to use Odin, it failed to flash an image in.
Plz help me.
Many thanks.
Gambinohe said:
I tried to factory format my phone through TWRP, then when I tried to restart again, it never comes back.
I still have access to TWRP, but when I install zip files I downloaded, it always failed. I tried to use Odin, it failed to flash an image in.
Plz help me.
Many thanks.
Click to expand...
Click to collapse
What format option did you select in TWRP and hope you didn't accidently remove your OS? The device could fail to boot if you don't have an OS installed. You may be able to flash a complete stock restore image via TWRP. Would you recall what Android version you were on before the brick? Also what is your phone model and carrier?
Larry2999 said:
What format option did you select in TWRP and hope you didn't accidently remove your OS? The device could fail to boot if you don't have an OS installed. You may be able to flash a complete stock restore image via TWRP. Would you recall what Android version you were on before the brick? Also what is your phone model and carrier?
Click to expand...
Click to collapse
Mine was ATT S3 I747 with Android 4.3 system. I did wipe my OS during recovery. That caused the whole problem. Then I use TWRP to flash a system and a kernel in. I was unable to flash bootloader and modem in; I did not know what is the problem. The weird thing is that I successfully start my phone and used it for a while. When I rebooted it, it dies again. I tried to install the some boot update in this January. It never works again. Any advise?
Gambinohe said:
Mine was ATT S3 I747 with Android 4.3 system. I did wipe my OS during recovery. That caused the whole problem. Then I use TWRP to flash a system and a kernel in. I was unable to flash bootloader and modem in; I did not know what is the problem. The weird thing is that I successfully start my phone and used it for a while. When I rebooted it, it dies again. I tried to install the some boot update in this January. It never works again. Any advise?
Click to expand...
Click to collapse
You can try flashing a complete stock system to get your phone back to working condition. Since you already had 4.3, flashing zips often fails if there is a bootloader incompatibility. The stock restore should do it. Please go to the following thread ....
http://forum.xda-developers.com/showthread.php?t=2658486
Download the stock restore zip to your PC. Use another device or something to load it to a (micro) SD card. Insert the card into your phone. Boot into recovery mode and flash from TWRP. When done, wipe your cache/dalvik and reboot to system. Let's know if this works for you.
My non-rooted GT-N7100 didn't want to boot after a longer period without battery charge. After fully charging, i got this screen: dropbox dot com/s/jy8sirmpgp6zm7h/20140823_214100.jpg
Later, i got the "firmware upgrade encountered an issue"-message. I tried to flash the latest stock ROM (via ODIN, from sammobile, checked MD5) but I get a fail when writing system.img.
So I decided to flash a custom recovery (twrp v2.8.0.1) (and trip knox..) to flash via an OTG-cable, but this also doesn't work.
TWRP tells me there is "no OS installed" when trying to reboot.
What am I doing wrong?
Wensjong said:
My non-rooted GT-N7100 didn't want to boot after a longer period without battery charge. After fully charging, i got this screen: dropbox dot com/s/jy8sirmpgp6zm7h/20140823_214100.jpg
Later, i got the "firmware upgrade encountered an issue"-message. I tried to flash the latest stock ROM (via ODIN, from sammobile, checked MD5) but I get a fail when writing system.img.
So I decided to flash a custom recovery (twrp v2.8.0.1) (and trip knox..) to flash via an OTG-cable, but this also doesn't work.
TWRP tells me there is "no OS installed" when trying to reboot.
What am I doing wrong?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1922461
try the steps under "3. Odin Instructions for the Samsung Galaxy S III "based" devices".
TWRP recovery should not be an issue if you rooted your phone before installing it. But, if you somehow have messed it up, try getting the firmware from Sammobile and flash it using odin. That should also replace your recovery to stock.
Hope this helps.
Cheers
I can flash a bootloader, recovery, pit-file, .. I'm using the right cable/drivers/.. It's just impossible to flash system.img to that partition. Twrp/philz/cwmrecovery give me an error when trying to wipe. Is it possible that that partition is corrupt?
I've tried a few stock roms and different custom/pre-rooted roms. None are flashable via odin (1.85, 3.07, 3.09), via adb sideload or USB-stick. I can't mount micro SD cards.
The phone was 4.3 when problems started; does anyone know where i can find the latest universal 4.3 stock rom? Sammobile only shows 4.4 and up..
Bricked?
Try twrp 2.7.2.1. and see if it works.
im sorry if this has been asked before. i was very hesitant to post but ive been trying to resolve this issue for 2 days and browsing and reading as much as i can with minimal results. i am trying to update to 4.4 from 4.2.2. i initially had a hard brick but was able to restore life with the img file but am stuck there. it boots into paranoidkangdroid sometimes (which is the rom i used before it hard bricked but not the one on the img file i created...weird i think). i think the more reading i do the more confused i get. im not sure if i have to flash to stock to get the ota, or whether i can just flash a 4.4 rom. im not sure what other information i should provide. thanks for any help and again, sorry if this is inappropriate.
Does your phone boot into download mode? If it does, flash a custom recovery and custom ROM to at least get your phone into a working state.
audit13 said:
Does your phone boot into download mode? If it does, flash a custom recovery and custom ROM to at least get your phone into a working state.
Click to expand...
Click to collapse
i am able to boot into twrp no problem
audit13 said:
Does your phone boot into download mode? If it does, flash a custom recovery and custom ROM to at least get your phone into a working state.
Click to expand...
Click to collapse
i was finally able to get some where!
i used this method to restore my phone to 4.3
http://forum.xda-developers.com/showthread.php?t=2658486
what steps do i have to take now to update to 4.4 and flash a custom rom?
do i first need to flash a 4.4 bootloader?
Personally, I prefer cwm over twrp.
Just copy a custom ROM to your external SD card, boot into recovery, wipe cache, dalvik, data, system, install ROM, reboot.
Depending on the ROM you install, you may have to update your bootloader and modem.
No O/S - can only boot into download mode
I've got an interesting one. I was prepping my phone for selling, decided to clear out all the memory. Somehow I must have deleted more than I meant to b/c when I restarted the phone, it just hangs on the Samsung screen. I can get into download mode, but not into recovery and nothing ever loads. I tried at least one version of installing CWM but it doesnt look like I can boot into recovery even after the Odin install appears ok. Before the crash, I was running a modded 4.4.2 rom with the bootloader and other things that come with it. Is there anything I can do to get this thing up and running again?
Thanks!
I suggest you flash a custom recovery and CM10.2 to at least get the phone up and running so you can confirm the bootloader and modem on the phone before flashing anything. Flashing the wrong bootloader, modem, or bootloader/modem combintaion could hard brick the phone.
audit13 said:
I suggest you flash a custom recovery and CM10.2 to at least get the phone up and running so you can confirm the bootloader and modem on the phone before flashing anything. Flashing the wrong bootloader, modem, or bootloader/modem combintaion could hard brick the phone.
Click to expand...
Click to collapse
Thanks. I'm positive I was running 4.4.2 on the phone before I decided to turn it into a paperweight
Flashing a custom recovery would be the goal, problem is that I can't find a recovery that I can flash. I've tried the latest version of PhilZ Touch recovery and that doesnt seem to work. ODIN shows it as a good install but when I restart the phone, I can't get into recovery. So was hoping for some direction on a different way of going about it. Basically, had 4.4.2, now I can only get into Download mode...
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Open Odin, connect phone, uncheck everything except f.reset time. Flash Philz. When you see reset in the status windows, remove USB cable, pull battery, replace battery, boot into recovery, flash ROM.
There are different versions of the 4..4.2 so it is best to determine the exact bootloader.