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.
Related
I just tried to flash a ROM and it ended up strangly. As a disclaimer: this is not a "MY PHONE IS BROKEN PLZ HELP ME!" post. I managed to get around this somehow, but I want to realize what technically happened in order to deepen my knowlage about the Android boot process. I come from a background of a Linux PC developer, but I didn't develop anything for Android yet.
So this is the boot process as I understand it, please correct me where I'm wrong:
When you turn on the device, the first thing that happens is that the CPU executes the Radio. The Radio allows the software to preform basic communication with the hardware, and is similar to the PC's BIOS. The Radio can be replaced, but if replaced with a problematic Radio, there's nothing you can do with home equipment to restore it (meaning a full brick).
Once loaded, the Radio executes the boot loader from the flash memory. The boot loader is like GRUB on a PC Linux system. It is the one that traps magic keys like "Volume up + Home" and decides, whether to boot the ROM, the recovery console or just "boot itself".
Both the ROM and the recovery software reside in differents partitions, and the bootloader chooses which partition to boot from.
In normal boot, the bootloader chooses to load the Linux kernel from the system partition and pass the execution to it. The Linux kernel loads Java, which loads the launcher, etc etc...
As I understand, a normal boot process doesn't involve the recovery software at all, and each ROM comes with its own custom-compiled Linux kernel.
The recovery software is like another operating system, which allows you replace the operating system in the system partition (AKA the ROM). Is the recovery software based on the Linux kernel too, or is it an independed software written in C/Assembly? If it is based on the Linux kernel, does it share a kernel with the ROM, or does it have its own version of the Linux kernel?
Now, this is what happened when I tried to flash Cyanogenmod 10 into a Galaxy S device running Cyanogenmod 7. I booted into recovery, backed up and wiped. To my understanding, backup means creating images of the system and data partition, storing these image files in the SD card and sign them with MD5.
When I tried to install the ROM, it warned me that my current partition layout won't fit to the new ROM, and I need to install again to confirm.
Now, when installing an OS in a PC, you can alter the partitions because the OS installation runs from a CD or a DOK, but if the recovery software runs from the disk too, how can it alter the partition table?
Anyways, once I confirmed, the phoned crashed and entered a boot loop. As I understood, flashing a ROM doesn't do anything to the recovery partition, so in any case I can always boot back to recovery and restore the backup. I was probably wrong, because when I tried to boot into recovery I found out that I have a different recovery software (The previous one had the Clockwork icon and a black background, and the new one had gray background and the Android Logo. I tried to restore the backup using the new recovery software but it failed, complaining that it can't format the system partition and that there's a problem with "MTD" (What's that?). I tried to reformat the system partition from the recovery software, but doing so caused it just to return to the main recovery screen without preforming anything or complaining about errors. Same thing when I tried to preform factory reset.
After some failed attemps, what I tried is to flash the old CM7 ROM, not from a backup, but from a clean zip. The recovery console claimed that it succeeded, but it did it too fast to be true, and there were almost no prompts beside the one that says that it succeeded.
I tried to restart, and got into a boot-loop again. This time, however, in each boot I could see my prevoius Clockwork recovery software for a second before the phone restarted again. I booted again into recovery mode to find my previous old recovery software. I tried to restore the backup and it succeeded. Now, I don't really understand what happened:
1. How come flashing ROMs changed the recovery software? I though that I zip containing a ROM contains only a ROM (A Linux kernel, Java JVM etc etc...), not a recovery software.
2. After I tried to flash CM7 back I could see the recovery screen in the boot-loop. Why did I see that screen if I didn't choose explicitly to boot into recovery?
3. How can the recovery software change the partition layout of the memory that it resides on by itself?
4. How come that the previous recovery software managed to restore that backup? As I understood, I ruined the partition layout, so what magic did the old recovery software that the new one couldn't do?
Thanks for the help
r.darwish said:
I just tried to flash a ROM and it ended up strangly. As a disclaimer: this is not a "MY PHONE IS BROKEN PLZ HELP ME!" post. I managed to get around this somehow, but I want to realize what technically happened in order to deepen my knowlage about the Android boot process. I come from a background of a Linux PC developer, but I didn't develop anything for Android yet.
So this is the boot process as I understand it, please correct me where I'm wrong:
When you turn on the device, the first thing that happens is that the CPU executes the Radio. The Radio allows the software to preform basic communication with the hardware, and is similar to the PC's BIOS. The Radio can be replaced, but if replaced with a problematic Radio, there's nothing you can do with home equipment to restore it (meaning a full brick).
Once loaded, the Radio executes the boot loader from the flash memory. The boot loader is like GRUB on a PC Linux system. It is the one that traps magic keys like "Volume up + Home" and decides, whether to boot the ROM, the recovery console or just "boot itself".
Both the ROM and the recovery software reside in differents partitions, and the bootloader chooses which partition to boot from.
In normal boot, the bootloader chooses to load the Linux kernel from the system partition and pass the execution to it. The Linux kernel loads Java, which loads the launcher, etc etc...
As I understand, a normal boot process doesn't involve the recovery software at all, and each ROM comes with its own custom-compiled Linux kernel.
The recovery software is like another operating system, which allows you replace the operating system in the system partition (AKA the ROM). Is the recovery software based on the Linux kernel too, or is it an independed software written in C/Assembly? If it is based on the Linux kernel, does it share a kernel with the ROM, or does it have its own version of the Linux kernel?
Now, this is what happened when I tried to flash Cyanogenmod 10 into a Galaxy S device running Cyanogenmod 7. I booted into recovery, backed up and wiped. To my understanding, backup means creating images of the system and data partition, storing these image files in the SD card and sign them with MD5.
When I tried to install the ROM, it warned me that my current partition layout won't fit to the new ROM, and I need to install again to confirm.
Now, when installing an OS in a PC, you can alter the partitions because the OS installation runs from a CD or a DOK, but if the recovery software runs from the disk too, how can it alter the partition table?
Anyways, once I confirmed, the phoned crashed and entered a boot loop. As I understood, flashing a ROM doesn't do anything to the recovery partition, so in any case I can always boot back to recovery and restore the backup. I was probably wrong, because when I tried to boot into recovery I found out that I have a different recovery software (The previous one had the Clockwork icon and a black background, and the new one had gray background and the Android Logo. I tried to restore the backup using the new recovery software but it failed, complaining that it can't format the system partition and that there's a problem with "MTD" (What's that?). I tried to reformat the system partition from the recovery software, but doing so caused it just to return to the main recovery screen without preforming anything or complaining about errors. Same thing when I tried to preform factory reset.
After some failed attemps, what I tried is to flash the old CM7 ROM, not from a backup, but from a clean zip. The recovery console claimed that it succeeded, but it did it too fast to be true, and there were almost no prompts beside the one that says that it succeeded.
I tried to restart, and got into a boot-loop again. This time, however, in each boot I could see my prevoius Clockwork recovery software for a second before the phone restarted again. I booted again into recovery mode to find my previous old recovery software. I tried to restore the backup and it succeeded. Now, I don't really understand what happened:
1. How come flashing ROMs changed the recovery software? I though that I zip containing a ROM contains only a ROM (A Linux kernel, Java JVM etc etc...), not a recovery software.
2. After I tried to flash CM7 back I could see the recovery screen in the boot-loop. Why did I see that screen if I didn't choose explicitly to boot into recovery?
3. How can the recovery software change the partition layout of the memory that it resides on by itself?
4. How come that the previous recovery software managed to restore that backup? As I understood, I ruined the partition layout, so what magic did the old recovery software that the new one couldn't do?
Thanks for the help
Click to expand...
Click to collapse
1.A recovery could have been packaged in the zip (i use zips to install recoveries too).
2.Im not sure about this but it could be that your bootloader got messed up and didn know what to load.
3.I think this is possible since recovery loads itself into ram and works from there allowing the partition to be changed.
4. I don't know about this one
Also the recovery has it's own kernel it doesn't share it with the rom one(ex. if touch doesnt work in a rom due to its kernel it can work in recovery)
Sent from my LG-P350 using xda premium
nerot said:
1.A recovery could have been packaged in the zip (i use zips to install recoveries too).
2.Im not sure about this but it could be that your bootloader got messed up and didn know what to load.
3.I think this is possible since recovery loads itself into ram and works from there allowing the partition to be changed.
4. I don't know about this one
Also the recovery has it's own kernel it doesn't share it with the rom one(ex. if touch doesnt work in a rom due to its kernel it can work in recovery)
Sent from my LG-P350 using xda premium
Click to expand...
Click to collapse
Thank you for the answer
Maybe someone can confirm if Cyanogenmod is shipped with a recovery software?
r.darwish said:
Thank you for the answer
Maybe someone can confirm if Cyanogenmod is shipped with a recovery software?
Click to expand...
Click to collapse
Official builds do not contain the recovery.
Sent from my LG-P350 using xda premium
oneovo establish
I used official builds for both 10 and 7.
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.
I'd say I'm above average when it comes to rooting and installing ROMS, but this one has be stumped. It may just be that I simply need to flash the stock ROM and try again, but here's my dilemma.
I successfully installed the correct version of TWRP for my tablet, as was I able to root it, but Xposed posed an issue. Upon flashing Wanam's custome Xposed zip, I am got the dreaded "Encryption Failed" screen. Assuming that Wanam's custom Xposed zip is what I need, because I'm using a Samsung device, what might I have done wrong? I have now formatted and wiped everything and am back to the setting up the device run through, but TWRP is still installed. If I do need to flash the stock ROM (firmware), I can't because I have not found it when searching here or Google.
If anyone has successfully installed TWRP, rooted, and installed Xposed on this tablet, I beg of your assistance. Also, a link to the stock firmware would be amazing.
EDIT: I will add that after I was able to get back to setting up the tablet and no longer facing the "Encryption" boot loop, as well as flashing Wanam's Xposed uninstall zip, I no longer have root and flashing the Chainfire SuperSU does not give root, but brings back the "Encryption" boot loop.
EDIT 2: I have found the stock firmware for this tablet. I found it on two file hosts. One is the well-known RapidGator. The other is an obscure (to me anyway) filehost called Alfafile. I am downloading it from Alfafile because RapidGator makes you pay for their premium service to download a file this large (1.6 GB), but the speed is awful to say the least. Once I download it, I want to share it. Where could I upload this that it would be available to everyone without paying a premium price, a site we are allowed to link on here??
Success... at last!
I did download the correct stock ROM (including boot.img, recovery.img and system.img). It was found as XAR-T580UEU1APG1-20160905144918.zip located HERE. This is the correct stock ROM for this device.
Before trying any of these steps, make sure you have installed the latest Samsung drivers. It may take a few minutes during some of these steps for the drivers to install. If at any point during these steps Windows has a notification that it is installing drivers, stop and wait until the drivers are finished installing. I noticed that a "Gadget Serial" installed when I connected my tablet to Odin in Download Mode. If that happens it's fine, let the drivers install before moving forward. Also it should be noted that this was performed using a PC with Windows 7 Professional.
COME WITH ME ON MY JOURNEY TO FREEDOM!
1. Boot in stock recovery
Hold Volume Up button + Home button + Power button
-OR-
Power off, wait for battery charge screen to come up, the hold Volume Up button + Home button + Power button
2. Wipe data & Factory reset
Press the Volume Down button until wipe data/factory reset is selected (highlighted/colored), then press the Power button, on the following screen use the Volume Up button or Volume Down button to select Yes and then press the Power button, once your screen is back on the main screen where you started, continue to step 3
3. Boot to Download Mode from stock recovery (do not boot to Android OS)
Press and hold Volume Down button + Home button + Power button
4. Odin, prep for flash and connect tablet (latest version, v3.12 at the time of this posting)
Open Odin and click options, then uncheck Auto reboot, and finally plugin your the USB cable into your tablet and PC. Once Odin recognizes your tablet, the far left box under ID:COM will turn blue and the Log tab will say "Added!!"
5. Flash TWRP custom recovery (twrp-3.0.2-0-gtaxlwifi.img.tar)
Click the AP button and find where you saved the TWRP zip.
Once the box next to AP is checked, click Start, if successful the Log will say "Successful 1 / Fail 0".
If this was successful, move on to step 6. Note that you don't have to unplug your tablet from the PC, just close Odin.
6. Boot to TWRP recovery (do not boot to Android OS). This step can be a tricky one and requires good timing. It is important to do these steps quickly.
From Download Mode, press and hold the Volume Down button + Home button + Power button (the Download Mode combo) until the screen goes black, then immediately press and hold the Volume Up button + Home button + Power button (the Recovery mode combo). You must switch from the Download Mode button combo to the Recovery Mode button combo before the Galaxy Tab boot screen appears. If you're too slow, you will have to go back to flash the stock ROM back to the tablet and start back at step 1.
Once in Recovery Mode, swipe the bar at the bottom of the screen, tap mount, and verify that the box next to Data is checked. Once that is verified, you can flash the SuperSU (SR4-SuperSU-v2.78-SR4-20161115184928.zip).
If you had not already copied it to your tablet, you can do this now since Windows should recognize it and allow you to copy the zip file to the table. You can also copy it to the external SD card if you have one and flash from there.
Once you have the SuperSU on your tablet, tap install from the main TWRP screen and then find it (you may have to search the folders), tap on it, and then tap install. If you are wanting to flash Xposed (xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip), or the boot image patcher (no-verity-no-encrypt_ashyx.zip), do not check the reboot box. Just swipe and flash SuperSU. Once done, go back and select the Xposed zip and flash. Once it is finished, go ahead and reboot, unless you also want to flash the boot image patcher to remove encryption. If you do, install, flash, and then reboot system.
NOTE: If you are going to flash all 3 (SuperSU, boot image patcher, and Xposed) do them in that order.
7. Confirm your work
Once Android is booted, check the SuperSu app and you'll verify you're rooted. Go ahead and reboot into TWRP recovery and you're Data partion is mounted and unencrypted. Now go ahead and install Xposed Installer (XposedInstaller_3.1.1.apk) and you're ready to download and use Xposed modules.
I followed these steps and have my Samsung Galaxy Tab A 10.1 (2016) (Model SM-T580NZWAXAR) rooted, unencrypted (data partition mounts in TWRP recovery), and Xposed framework installed flawlessly with no boot loops, no lost Data partition, no Encryption errors, and no hassel. All credit for the mentioned files and part of the steps to achieve this go to those that the credit is due. My contribtion is merely my journey and this 5 times tested, yes, I completely wiped and formatted my entire device and did this method 4 more times after I had success before writing this, to help others that might be frustrated for days as I was.
:victory:FREEDOM!!:victory:
Thanks for this, I'll be looking to root my tab after the holidays.....:fingers-crossed:
Hello!
Would someone be so kind and explain the following sentence to me:
tpsped said:
If you're too slow, you will have to go back to flash the stock ROM back to the tablet and start back at step 1.
Click to expand...
Click to collapse
Why should it be necessary to flash the whole ROM again?
I know that many ROMs reset the recovery to default, if TWRP hasn't patched the system, but then it should be enough to flash the custom recovery again.
DЯΦ[email protected]П said:
Hello!
Would someone be so kind and explain the following sentence to me:
Why should it be necessary to flash the whole ROM again?
I know that many ROMs reset the recovery to default, if TWRP hasn't patched the system, but then it should be enough to flash the custom recovery again.
Click to expand...
Click to collapse
When flashing the custom recovery, your Data will be unencrypted until you boot to Android OS.
In order to have an unencrypted Data partition, you have to follow these instructions in this order. If you are too slow and boot into the Android OS, you have missed the step and Data will become encrypted. Going back to Stock will once again reset the Data partition to unencrypted in order to properly make it permanently unencrypted.
Anyone unencrypted Data partition is needed in order to flash SuperSU, Xposed, the unencrypted method, or anything else in TWRP. The only exception may be flashing from external sd.
Anyone can correct me if I'm wrong, but I believe this should answer your question.
Wow thank you worked so well best of all guides
tpsped said:
Going back to Stock will once again reset the Data partition to unencrypted in order to properly make it permanently unencrypted.
Click to expand...
Click to collapse
To achieve this it is sufficient to format data partition in TWRP before flashing files, see https://forum.xda-developers.com/ga...ifi-galaxy-t3437666/post68154208#post68154208
ThemGo said:
To achieve this it is sufficient to format data partition in TWRP before flashing files, see https://forum.xda-developers.com/ga...ifi-galaxy-t3437666/post68154208#post68154208
Click to expand...
Click to collapse
Thanks for the info. I do welcome improvements to my instructions. I want to emphasize that these steps were the steps I took and that I figured out these steps on my own because there were no other instructions available that I could find. I'm always learning and growing!
tpsped said:
I'm always learning and growing!
Click to expand...
Click to collapse
Me too, I think everyone should :highfive:
Thank you for your guide, I like the clear steps.
Just woke up to see my phone on the Samsung Galaxy i9300 logo.
(I had just flashed LineageOS the previous day)
I was able to get into recovery CWM but nothing could mount, so I tried TWRP. Same thing. Couldn't sideload too (because you couldn't sideload to anywhere duh).
Tried flashing stock rom and repartitioning. Failed. And now the phone says Firmware upgrade failed etc instead of the logo.
Can't get into recovery anymore.
Can get into odin mode, but Odin doesn't recognize the phone.
SDS?
EDIT:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
You can still flash a stock ROM when you see the "upgrade failed" screen.
Did you try using different USB cables and ports to flash the stock ROM? Tried using Odin 3.07 with and without a pit file?
If you can get to download mode try another cable and install the pc drivers while the phone is connected in download mode or install kies for your operating system, stop the processes and try again.
Make sure your stock firmware is the correct one for your device/region/variant and that the md5 hash matches.
The problem you are having is caused by a borked recovery. It is very possible that the partition is corrupt, inevitably causing the death of your phone.
Beamed in by telepathy
Odin 3.07 / 3.09 and Heimdall don't recognize the phone.
The usb cable seems fine considering I used to flash the day before and if I remove the battery the phone is still on while connected to the usb cable.
I already ordered a new phone but if I can get this one fixed that'd be great. The new phone may come with a usb cable so I will try that.
I guess I was stupid enough to flash TWRP and SuperSU on top of LineageOS.
EDIT:
Before getting to this point I was able to flash stock rom while the Firmware upgrade has failed... logo showed. However I can't flash stock rom because the phone can't mount anything, not even /system. So it fails as soon as it tries to write something.
New usb cable - couldn't flash but was detected by odin.
Deleted hidden.img from the stock rom and now it flashes!
Let's hope it works.
Update: it did not.
After flashing it booted to recovery, said something about missing sd card and a countdown to 20s. After that was over it went to the recovery menu and I got a bunch of the same errors: couldn't mount /system /cache (no such file or folder found).
I put back my sdcard but I couldn't get to recovery, also, instead of the samsung galaxy logo I got a white screen. I could still get to download mode, and get recognized by odin and heimdall, but can't flash anymore ANYTHING.
Either There's no PIT file or stuck at Get pit for mapping if I do include one.
I've tried 3 different versions of odin.
I've tried heimdall under windows and linux with root without success (Either couldn't set up interface or there's no pit file).
I'm gonna try 1.85 odin tommorow. I lost all hope at this point. ****ed up my partitions.
RIP I9300.
Idk if that may work but you may have a go to just try flashing stock rom with a box. Gsm service points shouldn't take much for it
KayleMaster said:
Update: it did not.
After flashing it booted to recovery, said something about missing sd card and a countdown to 20s. After that was over it went to the recovery menu and I got a bunch of the same errors: couldn't mount /system /cache (no such file or folder found).
I put back my sdcard but I couldn't get to recovery, also, instead of the samsung galaxy logo I got a white screen. I could still get to download mode, and get recognized by odin and heimdall, but can't flash anymore ANYTHING.
Either There's no PIT file or stuck at Get pit for mapping if I do include one.
I've tried 3 different versions of odin.
I've tried heimdall under windows and linux with root without success (Either couldn't set up interface or there's no pit file).
I'm gonna try 1.85 odin tommorow. I lost all hope at this point. ****ed up my partitions.
RIP I9300.
Click to expand...
Click to collapse
Your emmc Nand Flash chip died. I had same problem with my n7100 last month. Had to change motherboard.
I took it to a service center. The told me the screen was dead because of the white screen. It was white cus corrupted BL or something, but definitely not the screen, considering you can go into download mode and you can clearly see it's functioning.
I laughed all the way through the front door.
Correct the screen is not the issue. The nand will be borked.
Beamed in by telepathy
TL; DR - explanation of issue; can you sideload TWRP via ADB?
I have a busted Galaxy S6 that won’t allow me access to do anything easier or more practical. My first thought was to root the phone to get inside that way, pull off the stuff I (well, really my mom - this is hers) want, and be done with it.
I originally tried flashing OJ9. This was successful but the phone became stuck in a boot loop. I tried to flash stock firmware but got a few different Odin error messages depending on the fixes I tried:
- first NAND write start (complete operation failed), this was when trying to flash TWRP
- then one suggesting there was a PIT issue - I don’t remember the exact message but it’s written down. This was when flashing stock ROM
- then back to the NAND crap when I tried to flash TWRP again.
We tried a factory reset, thinking it might be tricked into letting us in that way (I tried to flash the stock ROM again after that too). We have wiped the cache.
The most we can do is get it to the stock recovery screen. My thought now is to try to sideload TWRP through ADB, since the only time my computer recognizes the phone as a device is during this part. Is this even possible? I can’t find zip files for TWRP.