I believe I ended up bricking my device after trying to fix a battery issue I had with CM10.2, where my device wouldn't charge. I had no access to recovery, only download mode. Trying to flash stock with heimdall and odin, i find that for both, when it is trying to flash factoryfs, the device reboots, and is sent from download mode into the one with the exclamation mark (forced download mode?). If I try to flash with either one in that mode as well, it will simply reboot back into the same thing. If I try to access recovery, it will result in a bootloop from the battery meter to a black screen until I enter back into download mode. I have tried this with and without kies installed, and have reinstalled drivers using zadig. Is there any way I can fix this issue?
EDIT: Managed to flash back to stock, but I no longer have my efs, nor can i find my previous efs backup. I tried use the dummy efs and have also edited out a few things, but I am still missing my lock screen and power menu.
Related
I attempted to root my verizon sgh-i905. It partially succeeded however I don't have wifi. So, I tried to go into recovery to reapply the files. The two icons came up but when I tried to go into recovery, a blank page appeared and that was it. It is partially rooted because I also tried it with rom manager with the same results. Anyone got any ideas on how to overcome this problem? Actually, now after trying to update it with rom manager it won't boot up at all. The usb debugging has been unchecked as per instructions after odin. It will still go into downloading mode but odin doesn't see it because usb is unchecked. The only thing that comes up now is Samsung Galaxy tab 10.1 then screen goes blank.
Even though I couldn't get into usb debugging, I did get odin to reapply the tar so it would boot up. Rom manager still won't flash recovery and in download/ recovery the tab won't enter recovery. Is there a way to restore recovery?
EDIT: As I've now gotten Odin to flash again, and my device still won't boot, I'm really starting to think Andromeda's recovery has wiped something vital that isn't restored with a "regular" stock ROM image. PIT? EFS? Partitioning? Something like that? Odin successfully flashes the whole image tar (which I've previously used successfully), and the boot splash now correctly changes to the default Samsung one without triangle, but still the phone won't boot (as described in msg #3). So I'm now wondering if there's any way to a more aggressive restore (whence the topic title change)? Or am I barking up the wrong tree here?
----------
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Daniel Smedegaard Buus said:
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Click to expand...
Click to collapse
the reason for Dream and Andromeda not booting ur phone is that, if ur paranoid rom version was latest, then it comes with the new JB mali drivers for which only Dori v7.4 and siyah v5.0 are compatible
since u have already messed up too much with ur phone, u can try the 'KIES' option as the last resort to restore it back, since odin flash is not wrk'ng for u
Okay, so I tried installing Kies and connecting it. A variety of connection attempts, but it just won't connect to the device.
But, I'm making some progress! I've found that when I can get the phone to boot into the "Firmware upgrade encountered an issue." screen, I can get Odin to flash the stock Gingerbread image (still won't in download mode). And I then get a reboot with the regular Samsung boot splash (no yellow triangle) - except it never gets past it. After about a minute, it'll go black and then boot back up to the same splash screen and the same problem.
This is the exact same image I've used previously to revert the device to stock. So I was kinda hoping to see a normal clean. But unfortunately no donut. It reminds me of a computer I once bricked by screwing with its BIOS - it never got beyond POST and so I couldn't reflash it.
Is there something like a BIOS in this thing that could've gotten damaged in some way? And if so, is there any way to use Odin or another tool to fix that?
Cheers,
Daniel
Tried flashing a couple of matching CF kernels. I now get the green battery after the grey one, but still no boot.
All turned out the be the Shun Andromeda kernel re-introducing the hard brick bug. If you have the same issue, see my reply here for links to where you can get the custom PIT trick up and running.
I have an S3 GT-I9300 and about a week ago it started refusing to turn on. It was fully charged, and I'd get LED indicators for messages, emails etc, but none of the buttons would switch on the screen, neither would unplugging the cable. The only way to fix it was to remove the battery, and after removing it one time, it refused to boot, sticking at the Samsung logo screen. Recovery mode wouldn't work, I tried resetting to factory settings, and wiping the phone, but it kept sticking (I think at cache), and wouldn't boot whatever I did.
I tried to update the firmware through Kies, which just froze at 94% every time. I also tried Odin, which again froze about the same point. So I tried following this guide, but when the phone restarted it tried looking for files on an SD card (which I don't have), so no luck. I tried repartitioning, but it keeps failing and if I try to flash the phone it now fails with "there is no PIT partition". I can't remember at which point it started happening, but although I can still get into download mode, switching the phone on any other way gives me a glitched screen something like this.
Is there any way at all to fix this phone at this point?
@edwards87: I'm confused about your description: no recovery mode, but factory reset? A root tool for rescue?
If you can boot into download mode, download actual firmware and Odin from sammobile.com (all new, delete old stuff) and try to flash it.
rp158 said:
@edwards87: I'm confused about your description: no recovery mode, but factory reset? A root tool for rescue?
If you can boot into download mode, download actual firmware and Odin from sammobile.com (all new, delete old stuff) and try to flash it.
Click to expand...
Click to collapse
I can get into download mode (power + home + vol down), but can no longer get into recovery mode (power + home + vol up). When I could get into recovery mode right at the start, none of the recovery options did anything because it said there were missing files or directories.
I've tried several firmwares from sammobile through different versions of Odin and they all froze at the same place towards the end. Now none of them go anywhere because there's no PIT partition.
Then my next step would be a 3part-firmware +PIT-file.
rp158 said:
Then my next step would be a 3part-firmware +PIT-file.
Click to expand...
Click to collapse
Finally found a 3-part firmware but I get the same problem - repartition operation failed.
@edwards87: sounds like broken internal storage. Can't help you, sorry.
I need a pit file for galaxy s3 i9300 16GB please help me
I ran into a serious problem and now I do not know how to fix it. It turns out that I wanted to install a rom to my cell phone, since the stock I had was giving problems with the battery indicator, and I tried to calibrate it and even used others also following different steps to calibrate them, but always the same problem; Well, after root I found the problem that I could not install anything from the recovery mode of the cell phone, there was a problem that was disabled and could not from the sd, or internal, or adb or anything. Finally I decided to find an application to install twrp and flash the rom, downloaded flashify and I did.
When I went into recovery to flash the rom the cell phone did not change the logo with the message in a corner that is not the official recovery as always comes out when a custom is installed. And there it stays.
I can not turn it on normally, because each time I turn it on it goes directly to the logo with the message that it is not the original recovery, as if trying to access the recovery.
PS: I can not use odin, it does not recognize the cell phone when it is in odin mode, since all the drivers are installed and the kies, I reinstalled everything 3 times every time I tried it. And I can not enter odin mode, and the home button does not work, I used adb, but since it does not turn on, it does not recognize it either.
alberto1251 said:
I ran into a serious problem and now I do not know how to fix it. It turns out that I wanted to install a rom to my cell phone, since the stock I had was giving problems with the battery indicator, and I tried to calibrate it and even used others also following different steps to calibrate them, but always the same problem; Well, after root I found the problem that I could not install anything from the recovery mode of the cell phone, there was a problem that was disabled and could not from the sd, or internal, or adb or anything. Finally I decided to find an application to install twrp and flash the rom, downloaded flashify and I did.
When I went into recovery to flash the rom the cell phone did not change the logo with the message in a corner that is not the official recovery as always comes out when a custom is installed. And there it stays.
I can not turn it on normally, because each time I turn it on it goes directly to the logo with the message that it is not the original recovery, as if trying to access the recovery.
PS: I can not use odin, it does not recognize the cell phone when it is in odin mode, since all the drivers are installed and the kies, I reinstalled everything 3 times every time I tried it. And I can not enter odin mode, and the home button does not work, I used adb, but since it does not turn on, it does not recognize it either.
Click to expand...
Click to collapse
To enter in to the download mode you can use JIG USB which looks like this :
https://images-na.ssl-images-amazon.com/images/I/41MhETGCbBL.jpg
You can buy that jig USB on E-Bay
or you can use this tool but little Warning !!!
https://app.box.com/s/ktb9rzxde78lujqioh3rbmh6w39gedmm
File was scanned against viruses and it has some , maybe because like that he make your device in download mode.
https://www.virustotal.com/sr/file/...33ff7dceef468c2e8c325d79c7ad43fc8c1/analysis/
Here is video how to use .
https://www.youtube.com/watch?v=2er95HkiJbo
Good Luck
I'll try with the usb jig. Still don't know if buy the resistance and make one or just buy the jig. Then i will see if i can get for odin to detect the phone, using some kind of witchcraft or whatever hahahaha.
Thanks, I will set the thread as solved.
Good Luck
My phone is stuck in a bootloop. Here's what I've tried so far:
Booting into recovery mode, but it won't go into it, download mode does work though.
Flashing the latest 7.0 BTU using Odin, it is successful, but upon reboot the bootloop is back.
Flashing to another 7.0 BTU, same as above.
Flashing using AP + CP + CSC in Odin, same as above.
Flashing TWRP, it is successful, but again, on reboot the bootloop is back and it won't go into recovery mode, I have held down the buttons on the black screen, I've tried holding them whilst flashing, I've tried with auto boot and without it, nothing works. I've flashed TWRP about 10 times now trying different things.
Tried using ADB to get into recovery using TWRP, but ADB doesn't recognize any devices, probably because I don't have the USB mode enabled? Obviously I can't enable it as the phone is bricked.
Any suggestions?
This phone is so thin, it won't even make a good door stop at this point.
Sprinter55 said:
My phone is stuck in a bootloop. Here's what I've tried so far:
Booting into recovery mode, but it won't go into it, download mode does work though.
Flashing the latest 7.0 BTU using Odin, it is successful, but upon reboot the bootloop is back.
Flashing to another 7.0 BTU, same as above.
Flashing using AP + CP + CSC in Odin, same as above.
Flashing TWRP, it is successful, but again, on reboot the bootloop is back and it won't go into recovery mode, I have held down the buttons on the black screen, I've tried holding them whilst flashing, I've tried with auto boot and without it, nothing works. I've flashed TWRP about 10 times now trying different things.
Tried using ADB to get into recovery using TWRP, but ADB doesn't recognize any devices, probably because I don't have the USB mode enabled? Obviously I can't enable it as the phone is bricked.
Any suggestions?
This phone is so thin, it won't even make a good door stop at this point.
Click to expand...
Click to collapse
Try flashing philz recovery that worked for me to get recovery working !
Do you know what version and where from?
I tried a few versions but got the "Recovery is not seandroid enforcing" error on reboot.
I also tried recovery.tar from arter97 com (can't post the link) - Now it doesn't show the above error, and the Galaxy logo is showing without rebooting every 5 seconds. At least it's something different. Still can't boot into recovery mode though.
Here is a video that can fix the bootloop of Samsung Galaxy phone, maybe helpful with you.
https://www.youtube.com/watch?v=zXSHe3oorIM