Hello, first post here and I am hoping you guys will be able to help me.
I have here a SII that will only access download mode. I have tried re-flashing it several times with various Odin flashable files all of which returned a "Pass" but still would not allow me to pass the first "Samsung" screen. The files I have flashed include Clockworkmod, TWRP, and the stock UMCD8 firmware with and without pit file.
Is there any other option left short of replacing the motherboard?
You should be able to boot the phone after performing a wipe data/factory reset from within recovery. To enter recovery, hold all three buttons (vol+ vol- & pwr) continuously until the boot screen appears the second time, then release all three. You can perform a wipe data/factory reset from stock 3e recovery, or from a custom recovery, depending on which you have, it doesn't matter. That being said, you success will depend perhaps on what you flashed. I am assuming by ClockworkMod and TWRP you mean I-777 kernels containing those recoveries, as the I-777 does not have a separate recovery because the recovery is built into the kernel. If the kernel version does not match the system version (UCMD8 is Jelly Bean) then the phone would not boot even after a reset. But you could flash the full I777UCMD8 again, and then it should boot. If you have additional questions or issues, let us know.
creepyncrawly said:
You should be able to boot the phone after performing a wipe data/factory reset from within recovery. To enter recovery, hold all three buttons (vol+ vol- & pwr) continuously until the boot screen appears the second time, then release all three. You can perform a wipe data/factory reset from stock 3e recovery, or from a custom recovery, depending on which you have, it doesn't matter. That being said, you success will depend perhaps on what you flashed. I am assuming by ClockworkMod and TWRP you mean I-777 kernels containing those recoveries, as the I-777 does not have a separate recovery because the recovery is built into the kernel. If the kernel version does not match the system version (UCMD8 is Jelly Bean) then the phone would not boot even after a reset. But you could flash the full I777UCMD8 again, and then it should boot. If you have additional questions or issues, let us know.
Click to expand...
Click to collapse
Retried flashing the I77UCMD8 using odin 1.83 but it still wont boot. I also realized that when I try to access recovery it doesn't actually shut down, but gives me a black screen from which it will reboot if left for approximately five minutes. Is there anyway to get access to adb, like perhaps flashing a. insecure bootloader or something?
Berthfield said:
Retried flashing the I77UCMD8 using odin 1.83 but it still wont boot. I also realized that when I try to access recovery it doesn't actually shut down, but gives me a black screen from which it will reboot if left for approximately five minutes. Is there anyway to get access to adb, like perhaps flashing a. insecure bootloader or something?
Click to expand...
Click to collapse
Since you get a pass in Odin when you flash the full UCMD8 distribution, you should be able to get into recovery. Pull the battery for at least 30 seconds, then put the battery back into the phone and hold all three buttons continuously until you see the Samsung logo appear, the screen to go black, the Samsung logo appear a second time, and the screen to go black a second time, then release all three buttons.
If this does not boot the phone into recovery mode, then please describe in detail in your next post exactly what happens when you follow this procedure.
And, if the phone will not boot into recovery, then I will need additional information in order to troubleshoot the issue further. You have not given much information about the phone. What is the history of the phone before the problem manifested? Has this been your phone since new, or did you get it from another user? What was it running before the problem. Exactly what happened when the phone stopped working. Are you an individual trying to get his personal phone going, or a business trying to fix a phone to sell? Give me as much information as you can possibly think of.
creepyncrawly said:
...
Click to expand...
Click to collapse
On a side note, very honored to have issued your 3,001 'thanks'. I swear you should have triple that amount, due to the quality and depth of help you've given to the community - and continue to do so.
creepyncrawly said:
Since you get a pass in Odin when you flash the full UCMD8 distribution, you should be able to get into recovery. Pull the battery for at least 30 seconds, then put the battery back into the phone and hold all three buttons continuously until you see the Samsung logo appear, the screen to go black, the Samsung logo appear a second time, and the screen to go black a second time, then release all three buttons.
If this does not boot the phone into recovery mode, then please describe in detail in your next post exactly what happens when you follow this procedure.
And, if the phone will not boot into recovery, then I will need additional information in order to troubleshoot the issue further. You have not given much information about the phone. What is the history of the phone before the problem manifested? Has this been your phone since new, or did you get it from another user? What was it running before the problem. Exactly what happened when the phone stopped working. Are you an individual trying to get his personal phone going, or a business trying to fix a phone to sell? Give me as much information as you can possibly think of.
Click to expand...
Click to collapse
Okay. I am a student who repairs phones part-time, I am not new to the android platform or to the galaxy line however this is the first I am experiencing this particular problem.
This phone is a unlocked and refurbished device that was purchased recently by my cousin. He claims he was just installing an app when it shut down and refused to boot back up. I initially took it with the intentions of wiping the data and returning it, however I was unable to access the recovery menu.
As I had no idea what rom was on it before, other than the fact that it was a samsung original, I proceeded to trying to flash various recoveries hoping that one would load from which I could install a custom rom. Failing that I then went on to flashing the I777UCKH7 firmware which also failed to boot and/or access recovery. Unsure what to do next I then attempted to flash the I777UCMD8 firmware which also did not boot. I then made a second attempt at flashing the I777UCKH7 firmware and .pit file from your download repository which also failed to boot.
All were loaded using Odin versions 1.82, 1.83 or 1.85 (Mostly 1.85). They all returned a "Pass" status but would be stuck on the "Samsung" screen when they rebooted. It was at this point having run out of ideas that I made the O.P.
I have also tried leaving the battery out and then following your instructions for recovery, when I do so I get a black screen. If i leave it in that screen for some time (approximately 5 mins) it will reboot and again be stuck on the "Samsung" screen.
We appreciate that you aren't new to the android platform or to the galaxy-line. Regarding the i777, you are in good company, and if we know NOTHING about any other device, we know the i777 very well. We're here to help.
You mentioned that you flashed several recoveries to the device. For future reference, the recovery for the i777 is packaged with the kernel, and is not installed separately. Even the often-troublesome temporary flash-recoveries that can be found, are actually a kernel/recovery combination. The s959g (straight talk's s2) has the same partition layout as the i9100 and i777 (and several other s2's), and DOES use a separate partition for recovery.
The fact that desktop ODIN indicates PASS when the flash is complete tells us that all of the factory nand images flashed successfully (including boot). It is very common that the device needs to have the factory data reset even after the factory images have been installed via desktop ODIN, but of course that requires access to recovery. If after a successful factory flash, the vol+ & vol- & power button held-concurrently-until-recovery (<--while NOT plugged into a USB port) truly doesn't get you to recovery, then that would be a new one for me as well; all other signs (as you have stated them) point to a correctly functioning device.
I'm hesitant to point you to flash a custom kernel;
there's some unnamed part of the procedure affecting the process, and flashing another boot image won't be helpful
-or-
there's a hardware failure, and flashing another boot image won't be helpful
-or-
you're using an incorrect method to get to recovery, and flashing another boot image won't be helpful
If you want to try it anyway, custom_kernel_twrp_v2.7.1.0.tar file via desktop odin might be worth a try.
^^this will trip the flash counter
^^this will install any custom firmware, but will not boot anything below android 4.4.x
I apologize for the hijack @creepyncrawly
Berthfield said:
Okay. I am a student who repairs phones part-time, I am not new to the android platform or to the galaxy line however this is the first I am experiencing this particular problem.
This phone is a unlocked and refurbished device that was purchased recently by my cousin. He claims he was just installing an app when it shut down and refused to boot back up. I initially took it with the intentions of wiping the data and returning it, however I was unable to access the recovery menu.
As I had no idea what rom was on it before, other than the fact that it was a samsung original, I proceeded to trying to flash various recoveries hoping that one would load from which I could install a custom rom. Failing that I then went on to flashing the I777UCKH7 firmware which also failed to boot and/or access recovery. Unsure what to do next I then attempted to flash the I777UCMD8 firmware which also did not boot. I then made a second attempt at flashing the I777UCKH7 firmware and .pit file from your download repository which also failed to boot.
All were loaded using Odin versions 1.82, 1.83 or 1.85 (Mostly 1.85). They all returned a "Pass" status but would be stuck on the "Samsung" screen when they rebooted. It was at this point having run out of ideas that I made the O.P.
I have also tried leaving the battery out and then following your instructions for recovery, when I do so I get a black screen. If i leave it in that screen for some time (approximately 5 mins) it will reboot and again be stuck on the "Samsung" screen.
Click to expand...
Click to collapse
cyril279 said:
I apologize for the hijack creepyncrawly
Click to expand...
Click to collapse
On the contrary, your input is valuable and desired.
@Berthfield,
If there was actual nand damage in any partition that was flashed, you would not get a pass in Odin, as far as I know. Since you are unable to boot into any recovery, this indicates a problem with the nand memory, possibly a corruption issue. Please try the following (you might try accessing recovery after each step, and if you get to it, perform a wipe data/factory reset):
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
I was away from home for a bit and so was unable to work with the phone. I have followed the instructions given above but I am still unable to boot.
I was using the "I777UCKH7-REV02-home-low-CL503881.tar.md5" file downloaded from the download repository, is this the right file or is there another Gingerbread flash that wold be better to use?
I am really puzzled at what exactly is happening with this phone.
Yes, that is correct. That is the original stock gingerbread from when the phone was first released.
I agree that it is a puzzle. Just to be sure, you followed the directions exactly? I'm not sure why, but the sequence will clear nand read/write corruption. You might try once again with the SBL -> Siyah Kernel -> Full Gingerbread, just to make sure.
1) Flash the SBL by itself and pull the battery.
2) Flash the Siyah kernel by itself and pull the battery.
3) Flash the full Gingerbread stock and pull the battery.
4) Enter recovery and perform a wipe data/factory reset.
5) Reboot.
creepyncrawly said:
Yes, that is correct. That is the original stock gingerbread from when the phone was first released.
I agree that it is a puzzle. Just to be sure, you followed the directions exactly? I'm not sure why, but the sequence will clear nand read/write corruption. You might try once again with the SBL -> Siyah Kernel -> Full Gingerbread, just to make sure.
1) Flash the SBL by itself and pull the battery.
2) Flash the Siyah kernel by itself and pull the battery.
3) Flash the full Gingerbread stock and pull the battery.
4) Enter recovery and perform a wipe data/factory reset.
5) Reboot.
Click to expand...
Click to collapse
Did the above and it is still a no go.
I have come to realize that the phone seems to think it is in recovery mode when I attempt to enter it as if it is plugged in while on the black screen it doesn't display the charging animation. This occurs regardless of the kernel/recovery combo that is on the phone and while in that state it is also not detected by the computer. To rule out possible problems I have also attempted the flash on a different computer with a different cable and it is still the same.
I remember reading about the ICS hard-brick bug and that it was possible to brick the phone is a large enough file was written to memory. Is it possible that this could be my problem or would Odin return a error if the chip was damaged? Also I am not sure if this matters but I find it odd that after flashing the Siyah kernel and CWM the phone still hasn't tripped its custom binary counter.
Berthfield said:
Did the above and it is still a no go.
I have come to realize that the phone seems to think it is in recovery mode when I attempt to enter it as if it is plugged in while on the black screen it doesn't display the charging animation. This occurs regardless of the kernel/recovery combo that is on the phone and while in that state it is also not detected by the computer. To rule out possible problems I have also attempted the flash on a different computer with a different cable and it is still the same.
I remember reading about the ICS hard-brick bug and that it was possible to brick the phone is a large enough file was written to memory. Is it possible that this could be my problem or would Odin return a error if the chip was damaged? Also I am not sure if this matters but I find it odd that after flashing the Siyah kernel and CWM the phone still hasn't tripped its custom binary counter.
Click to expand...
Click to collapse
Evidently, this situation is beyond my experience.
My understanding is that if emmc memory is damaged within a given partition, then Odin will not be able to successfully flash that partition. While I don't know exactly how Odin functions, I believe there are checks within the flashing sequence for each partition. So as stated before, it is assumed that if you get a pass in Odin, there is not emmc damage, at least not within the various partitions that Odin flashes.
There was one case I remember with the emmc super brick bug where the phone would boot, but would not function correctly. Evidently in that case, a small portion of the emmc memory was damaged. The usual symptom of that bug was a hard brick.
The charging issue could be hardware or it could be a failing or failed battery. Have you tried another battery?
Flashing the Siyah kernel and not tripping the flash counter is more than a little odd. The code that governs that behavior is in the secondary boot loader as far as I know, and you have reflashed that. Please bear in mind that anything I say is speculation, but this issue give me a lot of reasons to think it is a failed hardware issue.
Related
Hi there,
My phone is a Samsung Galaxy SII GT-I9100 with the OS version ICS 4.0.4
Basically I read about my OS version having the superbrick bug in the kernel, and in order to root I needed to install a custom recovery partition (CWM) and then install custom ROMS, so I went ahead and downloaded CWM and then transferred the .tar over to my device with Odin, and Odin said all went well and it passed, next I went to root it with SuperOneClick (v2.2), so I fired that up and hit root, and all was well or so it seemed, SuperOneClick told me I had SU access, so I thought all had worked. I then started in recovery mode just to see if CWM was there and working correctly, however it was just the normal android one, no CWM - although it said Current Binary: Custom and Custom Binary Download: Yes (1 count). I quickly realised it had not rooted successfully when root checker told me it wasn't rooted, and CWM was missing and also that my video playback/camera screens weren't functioning properly - they were just black screens. So I hooked my phone back up to my PC and went to SuperOneClick and hit Unroot hoping all would be well, then when my phone started up again it gets stuck at the boot animation of the big 'S'.
So now I am stuck, I don't have CWM installed to perform a reset, and I don't think I can flash ROM's to my device directly in case it 'superbricks' due to the kernel bug, so I don't know whether I can just flash the stock ICS ROM back on
I am seriously annoyed with this, what can I do?
Any help is seriously appreciated
Thanks alot
Try finding your recovery menu (probably volume up+power from off) and wiping cache. If not, then try factory reset, also from stock recovery. If not, then i'd say you're gonna have to flash stock ICS. No help in your device's thread Q&a? My question is why was the CWM in .tar form? Usually it is an image..
Also, no help in SuperOneClick thread?
bodh said:
Try finding your recovery menu (probably volume up+power from off) and wiping cache. If not, then try factory reset, also from stock recovery. If not, then i'd say you're gonna have to flash stock ICS. No help in your device's thread Q&a? My question is why was the CWM in .tar form? Usually it is an image..
Also, no help in SuperOneClick thread?
Click to expand...
Click to collapse
How do I wipe cache with the recovery menu? It is just the standard android recovery with "Volume up: Continue to download mode" or "Volume down: Cancel (restart phone)". Also would I be able to try and flash CWM again with a different file, and if it works I could perform a stock reset sort of thing? Could you link me to a reputable CWM file that will work so I can just shove the .tar in Odin and hit start. And I can't flash ICS as there is a high probability I have the superbrick bug
EDIT: The CWM Restore file for download for the SGSII here www (dot) clockworkmod (dot) com/rommanager are not in even in the correct format for flashing with Odin, what do I do??
Some recoveries allow a cache wipe, while others don't.. Recovery menu [if you've looked up how to access it on your particular device] most certainly should have a factory reset option as well, so im thinking you haven't found its menu.. Again, cwm should be in img format. .tar sounds like someone else's backup. If your inexperienced with what you're gonna need to do to fix your phone, i'd definitely say a warranty claim. I know someone that got a brand new sgsii just a week before her warranty ran out, due to the same issue.
And i've never used odin..look up a guy named samersh72 on the forum, and his threads.
Hi, so I've been flashing for a while now on my phone and my friend wanted to root his phone so i agreed to help him out. After flashing multiple files in order to get cwm recovery and just get everything working, the phone started to act up.
Here are the problems:
Phone can boot into stock recovery but i cant flash anything from it
i wiped data/factory reset many times.
i tried to install the cwm kernal by applying update from sd card (I followed the install custom recovery instructions from here: http://wiki.cyanogenmod.org/w/Install_CM_for_i777) but when into recovery to flash, 2 red signs come up saying "E: Failed to verify whole-file signature" and "E: signature verificatoin failed" after this is just aborts the process
i tried download mode, but none of my computers recocgnize the phone (2 computers) i have tried all usb ports, reinstalling usb drivers, different usb ports many times but all have failed
if i try to boot, the phone just stays stuck on the Samsung galaxy s2 logo (no triangle? even though its rooted)
my only option is to hang out in recovery, i have a bunch of files saved to an external sd card but i cannot access that from stock recovery
any help would be appreciated, Thanks
You can not install any unsigned files with stock 3e recovery, as you have discovered. That is normal behavior.
I don't know why performing a wipe data/factory reset from 3e recovery does not clear the phone to boot normally. It should. But since it won't...
You will need to get the phone recognized by a computer, and then flash with Odin, or you could try flashing with Heimdall command line. I would suggest that you flash the full stock plus root I777UCKH7 (2.3.4), and then when it boots normally into the system, install Mobile Odin Lite or Mobile Odin Pro, and use that to flash a custom kernel. You can find the stock firmware in the Download Repository, and the basic directions in my guide, both of which are linked in my signature.
creepyncrawly said:
You can not install any unsigned files with stock 3e recovery, as you have discovered. That is normal behavior.
I don't know why performing a wipe data/factory reset from 3e recovery does not clear the phone to boot normally. It should. But since it won't...
You will need to get the phone recognized by a computer, and then flash with Odin, or you could try flashing with Heimdall command line. I would suggest that you flash the full stock plus root I777UCKH7 (2.3.4), and then when it boots normally into the system, install Mobile Odin Lite or Mobile Odin Pro, and use that to flash a custom kernel. You can find the stock firmware in the Download Repository, and the basic directions in my guide, both of which are linked in my signature.
Click to expand...
Click to collapse
The hardest part about this is getting my computers to recognize the phone
i guess i shouldve mentioned this earlier, i attempted to flash in Odin but it was stuck on zImage so i unplugged it
before i flashed in odin, i used to be able to boot into the phone like touchwiz and whatnot, now it just gets stuck on the samsung galaxy s ii boot logo
This is now [Solved}! thanks for the help creepyncrawly! i figured it out after doing some more reasearch online. apparently, youre not supposed to use the charger wire that came with the device since samsung doesnt want to waste their time on creating a good enough cable for this kind of stuff. so i grabbed some random cable that i found in my house, hooked it up and BAM! both of my computers were able to detect my phone just finished flashing bone stock on the phone thanks
I noticed in your post that you tried everything but another cable. But I'm glad you got it working. I had the same problem before too. Cables are finicky little things.
Sent from my SGH-I777 using xda app-developers app
Hi folks, mid last week I woke up to a non responsive Galaxy S2. It's been happily running stock Vodafone ICS for over a year, and somehow spontaneously went soft brick on me. Gets stuck at logo screen or goes into boot loop.
Download mode is accessible. I can flash through Odin (1.85 and 3.09) and it reports success. I have successfully put CWM (various versions) on it can can boot into them fine.
Recovery mode is also accessible and appears to be working fine. I can access external SD card no problem.
Attempting to flash through zip from external SD aborts with Mode 7, reporting bad zip or unable to read source file. I have tried removing asserts from install script (educated myself to the risks and made sure the ROM was correct!!) and multiple versions of CM (10.1.3 stable, 10.2 nightly) and multiple versions of CWM recovery (6.0.2.9 is what I've been using mostly, as recommended by CM guide)
Tried running GS2ROMNukeV2.12.zip which reported successful wipe, then attempted zip install from SD with same result (aborted mode 7). Repeated wipe and attempted stock (I9100TDVLSK_I9100THUTLSD_I9100TDVLS3_HOME.tar) from flash through Odin. Reported success, phone booted into recover and applied KOR CSC successfully, then reboot and still stuck at logo screen/boot loop.
I have attempted the fix in http://forum.xda-developers.com/showthread.php?t=1449771 as best I could wish the resources I could find, but it's hard to follow to the letter with the links broken!!!
I have not tried repartition with PIT as I'm not sure where to get an appropriate PIT file. Advice on this appreciated!
I want to make this clear because people seem to not want to believe it: I did not soft brick my phone flashing it. My best theory at this point is some kind of memory corruption or hardware failure that's causing a boot loop. Any help or suggestions would be appreciated. This week I will probably take it in to a repair shop and hope for the best, but tomorrow is a public holiday and I've got nothing to lose by trying any more suggestions.
Kaine said:
Mode 7
Click to expand...
Click to collapse
If memory serves me right this is due to an old version of Recovery, i had the same thing, updated recovery and it flashed zip fine. just as you know. :fingers-crossed:
Current status: BOOT LOOP, NO WORKING RECOVERY
I'm working on a friend's Photon, trying to get it back to stock. It got the 2.3.5 OTA update ages ago and therefore has a locked bootloader.
I have tried many things. Do not tell me to search the forum; I have spent many hours doing exactly that.
The phone starts booting, shows the U.S. Cellular animation from the Electrify due to the performing the first of the six tasks outlined in several places, including here: http://forum.xda-developers.com/showpost.php?p=30654255&postcount=5
It then reboots before getting to a home screen. The next logical step would be to boot to recovery and do a factory reset. However, starting recovery (hold volume down, down until recovery, up) results in the yellow exclamation point sign and android icon and then it freezes. I suspect, but am not sure, that the phone had CWM on it at some point. I'm not sure if the Electrify sbf also re-installs stock recovery?
I can get into fastboot, but the two recovery images I attempt to flash result in "failed to process command flash:recovery error(0x180002)". I have also flashed 2.3.5_45.4.13ota_unbrick.sbf in an attempted to get a working recovery, but that just goes back to the boot loop at the end of flashing.
I can't continue with the 6-step unbrick process because the phone won't boot up all of the way to allow me to root it and install the bootstrap apk. I can't wipe the phone because recovery doesn't work.
What I need:
a fastboot-able stock recovery image file, to ensure that I have the correct recovery. There were links to this at one time, but they are all either rotted or the OP flounced and nuked his posts containing them.
Apparently the yellow exclamation point sign means that stock recovery is installed. However, it never presents a menu or any text, just the image, so something else is wrong. Of course, there are no useful error messages, either, just the image.
No amount of RSDLite appears to be helping. Is there a way to force a factory reset from fastboot or RSDlite instead?
To answer my own question:
fastboot erase userdata does a factory reset.
If anybody else sees this while trying to do the 6-step 2.3.5 stock reinstall, if you get hosed after step 1, that's how you fix it.
I have been flashing the stock 4.1.2 firmware, in odin 3.07, and it keeps bootlooping. First it displays the samsung logo with sound, and then the samsung logo without the sound for the whole time. In odin 3.14, when i try flashing the stock firmware, it says fail. How do i fix this?
Did you use a four-file firmware?
ze7zez said:
Did you use a four-file firmware?
Click to expand...
Click to collapse
Yes, but the firmware i am trying to flash has no bootloader file. (I always used to flash it and it worked)
I am fixing one now.
The partition layout is weird because it had AOSP/Cyanogen etc
Luckily I found a bunch of old sh.t to flash on it
- Odin 3.07
- service files - original pit, bootloader, recovery
- custom files from XDA developers such as custom pit files, TWRPs, and AndroidOS v7+ zips
I flashed a "4 file" repair firmware with Odin 3.07 and in Recovery stage, it errored out with
E:Error in /cache/recovery/sec_csc.zip
(Status 7)
So in the same Recovery I switched to install update from adb
adb sideload I9100XWLSW_I9100XXMS2_I9100XEULS5_HOME.tar.md5
However this time the error was Signature verification failed.
So I started Factory Reset and it's stuck at Formatting /data
OMG LOL
Removed battery let it cool, put new battery in.
Asked evil GPT just pasted my previous post and it gave me the following:
Partition Layout: The i9100 has a unique partition layout that includes several partitions for different purposes. The main partitions are:
PDA: This partition contains the firmware and is the primary partition that gets updated during the flashing process.
Phone: This partition contains the baseband firmware and other radio-related files.
CSC: This partition contains the carrier-specific customizations and settings for the device.
EFS: This partition contains the device's IMEI number and other important data related to the device's radio and network functions.
Cache: This partition contains temporary files used by the device, such as app data and system files.
System: This partition contains the Android operating system and other system files.
Security Protections: The i9100 includes several security protections to prevent unauthorized access and tampering. These protections include:
Bootloader: The bootloader is the first piece of software that runs when the device is powered on. It verifies the signature of the firmware before allowing it to be loaded, preventing unauthorized firmware from running on the device.
Knox Security: The Knox security platform provides enhanced security features, such as secure boot and real-time kernel protection, to prevent unauthorized access to the device's data and functions.
Secure Boot: Secure Boot verifies the signature of the firmware and the bootloader to ensure that only authorized firmware is loaded.
Encryption: The i9100 supports full device encryption to protect data stored on the device.
Remote Lock/Wipe: In case of loss or theft, the device can be remotely locked or wiped to prevent unauthorized access to the data.
Overall, the i9100 has a robust partition layout and security protections to ensure the integrity and security of the device and its data.
Try flashing a different firmware file using Odin 3.07: If the firmware file you initially flashed is causing issues, try flashing a different one. Make sure the firmware file you download is compatible with your device and has been verified by other users.
Check the partition layout: If the partition layout is causing issues, you may need to manually adjust it using a tool like Odin. Make sure you have a backup of your existing partition layout before making any changes.
Verify the integrity of your firmware files: If you are getting signature verification errors, it may be due to a corrupted or incomplete firmware file. Make sure to download the firmware files from a reputable source and verify their integrity before attempting to flash them.
Wipe the cache partition: If you are encountering issues in recovery mode, try wiping the cache partition. This can often resolve issues with installing or updating firmware.
Use a different recovery: If the default recovery is causing issues, try using a custom recovery like TWRP. This can often provide more advanced features and better support for installing custom firmware.
Ah, the i9100, a classic device. When it comes to fixing a softbrick issue, the first thing to try is to boot the device into recovery mode and wipe the cache partition. If that doesn't work, you may need to try flashing a custom recovery like TWRP and then flashing a new firmware file. Just make sure to download the firmware file from a trusted source and verify its integrity before flashing. If all else fails, you can always try performing a factory reset, but be aware that this will erase all data on the device. And if all THAT fails, well, you might just have to accept that your i9100 is a goner. But hey, at least you can still use it as a paperweight or a doorstop, am I right? Haha, just kidding (sort of).
- Here my prompt was I asked about what to do when the phone is at Samsung logo and the bottom buttons are lit.
If your device is stuck at the Samsung logo after performing a factory reset, you may need to try a few things to get it back up and running. Here are a few suggestions:
Boot into recovery mode and wipe the cache partition again: Sometimes a factory reset can leave behind some residual data that can cause issues. Wiping the cache partition again may help to resolve this.
Try a different firmware file: If the firmware file you flashed initially is causing issues, you may need to try a different one. Make sure to download the firmware file from a trusted source and verify its integrity before flashing.
Flash a custom recovery like TWRP: If you haven't already, try flashing a custom recovery like TWRP. This can sometimes provide better support for installing custom firmware.
Re-flash the firmware file: If all else fails, you may need to re-flash the firmware file using Odin. Make sure to follow the instructions carefully and verify the integrity of the firmware file before flashing.
Hopefully one of these suggestions will help to resolve the issue you're experiencing with your i9100.
Click to expand...
Click to collapse
So the fix was to clear cache and replace battery it seems.
WOW the factory software 4.1.2 is goergeous!!! Why can't all phones and tablest be made so well ?!
It's a conspiracy brothers.
I tried to install LineageOS 19 and now my phone is stuck in bootloop after I tried installing the old PIT file to get back to LOS16 which was working. My phone does not respond to any of the combinations, either for recovery or download mode.
Anything that can be done?
Try again the key combos but maybe get more specific key combos from somewhere. It also matter from what mode the key combo is used, from some modes you need to first hold some combo to "turnoff" then keep/change holding a combo to enter recovery etc.
Sometimes it matters what cable is in the phone and what battery and when exactly.
Take out the battery and cable and try again
Power off your device completely.
Press and hold the Volume Down key, Home button, and Power button simultaneously.
Once the phone vibrates and the Samsung logo appears, release the Power button while still holding the Volume Down and Home buttons.
Continue to hold the Volume Down and Home buttons until you see a warning screen with a yellow triangle icon.
Press the Volume Up button to enter download mode.
You should now see a screen displaying "Downloading..." with a green Android icon. This indicates that you have successfully entered download mode. From here, you can use a tool like Odin to flash new firmware and hopefully fix the boot loop issue.
eventually you can enter some mode by testpoint probably
I tried everything and unfortunately seems I will have to resort to jig.
Could be the buttons have waterdamage corrosion and hence the symptoms ? You can try reverse the corrosion with chemicals however it's a multi-step process because after each chemical there are cleaning agents to prevent the further corrosion from the previous step.
Pressing multiple times hard also helps with corrosion sometimes.