Hi,
So I got the i9506 and since I've played around with my i9100 for a couple of years rooted, I decided to root my i9506 too. Before doing so, the phone installed 4.3 via OTA. I've been unrooting i9100 over and over while installing custom ROMs and so forth.
But now as I was trying to root my i9506, a problem struck. As I was flashing the Philz FW, it failed and now I'm stuck with "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". Well that's a mighty good idea, but for some reason Kies does not recognize my phone. I googled and and some other people have this problem too and I'm yet to find a solution with Kies.
So I arrived to XDA, once again, and tried looking for a solution. Found this topic and already hoped that I was saved. But either my understanding of the whole thing isn't enough or it doesn't have the solution for me, I just couldn't get my phone fixed.
So now I'm stuck with the "Firmware encountered an issue..." screen and I don't have a way out. Could someone please help me out?
Any help is much appreciated!
PS: I'm from Finland.
I downloaded the stock roms 4.2.2 and 4.3 from sammobile and tried those as well, but no help.
Odin always fails when trying to flash something.
Tried with Odin 1.85 after multiple failed attempts with 3.09.
I always get this log, no matter what I pick as the bolded option:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUBML6_I9506NEEBML1_I9506XXUBMK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!
Click to expand...
Click to collapse
Do I need a PIT file and if so, is there a certain file I need or am I supposed to use a tool like PIT Magic?
My phone still says the following so I'm not sure my warranty is voided altogether:
Product name: GT-I9506
Current binary: Samsung Official
System status: Official
Knox kernel lock: 0x0
Knox warranty void: 0x0
Resolved.
I was using another microUSB cable to do the job, but after changing to new white cable that came with the phone, it passed! Now all's back to way it used to be before all the trouble. Even my phone name and all are intact.
I have a loop reboot problem with my Samsung Galaxy Tab 2 10.1 p5113.
Using Odin I tried to install all this recovery software, openrecovery-twrp-2.8.5.0-p5110 ; philz_touch_6.57.8-p5110.tar ; openrecovery-twrp-2.8.5.0-p5110.
In 3 cases, Odin install recovery software succesfully and then restart.
But after restart, allways return to stock recovery.
With the stock recovery can't install any ROM, what can I do???
Flash the latest Firmware .tar file with ODIN
Roby007 said:
I have a loop reboot problem with my Samsung Galaxy Tab 2 10.1 p5113.
Using Odin I tried to install all this recovery software, openrecovery-twrp-2.8.5.0-p5110 ; philz_touch_6.57.8-p5110.tar ; openrecovery-twrp-2.8.5.0-p5110.
In 3 cases, Odin install recovery software succesfully and then restart.
But after restart, allways return to stock recovery.
With the stock recovery can't install any ROM, what can I do???
Click to expand...
Click to collapse
Download the latest firmware for your Galaxy tab 2.
Use odin to Flash the file.
This is the method i always use whenever i get into some type of trouble. However in my case the open recovery or philz recovery method is useless. !!!
I download last ROM P5113UEBLH3_HOME.tar.md5
I tried to install with Odin, at middle of proccess, fail:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do?
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your specific device forum here (bookmark/subscribe this):
Samsung Galaxy Tab 2
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Galaxy Tab 2 Q&A, Help & Troubleshooting
Good luck!
Is tab rooted?
Not mentioned in op.
Without root flash will fall and you get stock recovery.
Pp.
Root?
Root, no was rooted.
Roby007 said:
Root, no was rooted.
Click to expand...
Click to collapse
Don't know what this means?
But check your root, it may be borked.
Use root checker from play store.
Pp.
Roby007 said:
I have a loop reboot problem with my Samsung Galaxy Tab 2 10.1 p5113.
Using Odin I tried to install all this recovery software, openrecovery-twrp-2.8.5.0-p5110 ; philz_touch_6.57.8-p5110.tar ; openrecovery-twrp-2.8.5.0-p5110.
In 3 cases, Odin install recovery software succesfully and then restart.
But after restart, allways return to stock recovery.
With the stock recovery can't install any ROM, what can I do???
Click to expand...
Click to collapse
I'm experiencing this exact issue, however it's with the LTE version of this tablet, model # SGH-I497.
It should be noted, starting with a stock tablet without root, I've TWRP'd + restored a "master image + rooted" backup on many of these same tablets in the past, all without any issues whatsoever.
The TWRP I'm using is an unofficial build by @tselling, filename recovery_twrp2.6.3.0_tselling.tar.md5 (can't remember which thread I found it in exactly)
Now, no matter what I do, I can't replace the Stock Recovery. Tried uninstalling and reinstalling the drivers (Samsung USB v1.5.14.0), disabled and re-enabled USB debugging, multiple flashes of the recovery.tar.md5 via Odin v1.85, different USB cables and USB ports on my computer, etc. I even tried a Factory Reset using the Stock Recovery, and doing everything again. This particular tablet has given me more trouble than the 10+ I've done in the past couple weeks.
Right now I'm just downloading this firmware from SamMobile, and I'll try the instructions listed at the bottom of that page. Will try using Odin 3.09 as instructed.
Here is the most recent Odin report I received after my latest attempt at flashing the recovery:
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery_twrp2.6.3.0_tselling.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Removed!!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
---------- Post added at 12:44 PM ---------- Previous post was at 11:47 AM ----------
So I tried flashing the stock firmware, no luck. This is the report I got from Odin:
Code:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I497VLAMJ2_I497XACAMJ2_I497VLAMJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sbl1.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If it helps, while in Odin Mode my tablet says that Qualcomm Secureboot is ENABLED. It also displays a "Secure Check Fail: sbl1" message after the flash failure.
Anybody have feedback/fixes for this?
I am unfortunately still stuck
Also of note, my previous successful attempts on these tablets never added to the flash counter, i.e. it always remained at 0.
I checked this morning on the tablet that's giving me so much trouble, and it counted each one of my 6 unsuccessful attempts.
I got TWRP to stick!
@Roby007
MAJOR UPDATE - after racking up a healthy 10 on my flash counter, I finally got TWRP to work!!!
My SGH-I497 has just been sitting on my desk since my original post, completely Stock Samsung and non-TWRP'd. Today, I decided that I would give it another shot.
What I did, step-by-step:
1. Settings > ensure that USB debugging is enabled > ensure that when using Minimal ADB and Fastboot that "adb devices" returns the Device ID > disconnect device's USB cable from PC.
2. Right click on Odin3 1.85.exe file > Run As Administrator > click PDA option and select twrp2.6.3.0.tar.md5 recovery file.
3. Power the device down > boot into Odin/Downloading Mode using Power + Volume Down buttons then Volume Up button to continue > reconnect device's USB to PC and ensure that device gets "Added" in Odin.
I repeated above process four times, each time with a slightly different iteration, detailed below:
Iteration #1 - USB Port 1 with Auto Reboot checked and F. Reset Time unchecked
Iteration #2 - USB Port 1 with both Auto Reboot and F. Reset Time checked
Iteration #3 - USB Port 2 with Auto Reboot checked and F. Reset Time unchecked
Iteration #4 - USB Port 2 with both Auto Reboot and F. Reset Time checked
Despite receiving no errors and Success/Pass messages each time, Iterations #1-3 did not work - I still had the Stock Recovery after each flash.
Iteration #4 however was successful, and I finally have TWRP on this device! I wasted no time in restoring my carefully-crafted master image.
I really hope this post helps you out - I know from firsthand experience how frustrating this can be.
(Apologies if I'm keeping this thread alive unnecessarily, however it's proving very useful for documenting my ongoing challenges with this TWRP-not-sticking issue. Hopefully someone else will find it useful as well.)
MAJOR UPDATE 2
I encountered the same "TWRP not replacing Stock Android Recovery" issue today, this time with a different device, a Samsung Galaxy Tab 2 10.1" tablet (model # GT-P5113, WiFi-only).
I tried the method that worked for me above, i.e. changing the checkbox options in Odin and switching USB ports/cables. 16 flashes later on the counter, and still no TWRP.
After doing some more research, I came across this post by @Android-Andi. Following the steps, especially numbers 9-14, resulted in a successful TWRP flash. I actually unchecked both Auto Reboot and F. Reset Time, waited 2-3 minutes after Odin's "Success/Pass" message, then disconnected the USB cable and booted directly into TWRP Recovery from there.
I also found this guide for the S4, although the steps that refer to Odin appear to be relevant for any Samsung device. Right after Step 7, there is instruction that follows a similar process outlined above, however with an added battery pull for good measure.
Heyy XDA,
Writing this post as I'm completely stumped on this one
Basically when I first got my S6 I rooted it and all, and everything was fine, I then unrooted it in order to update the OS to 5.1.1 which again all went fine.
This was about 4 days ago. Since this there hasn't been any issues what so ever, until this morning when the phone died. After charging it back up to 100% I switched it on and it just chilled in a bootloop.
From here I tried soft resetting the phone, but it stayed in the loop. I then tried clearing the cache, which again had no effect. I've also tried wiping the phone entirely and putting it back to factory which again did nothing to help and safemode didn't boot as it restarted as soon as the display lit up (baring in mind that the OS is completely stock and the phone is unrooted.)
After no avail with the phone, I decided to try rooting the phone, hoping that it would 'kick' it back to life as that's what Apple devices do... :good: , however after attempting to root the phone it just stayed on the samsung screen with the error 'recovery is not seandroid enforcing'.
Then I thought ... F*** ... and downloaded the 5.1.1 firmware for my current model (G920F, UK model, EE network) which I then tried to flash through ODIN v3.10.7, however I got the error of:
'<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)'
I've checked that this is the correct version, as well as checked the MD5 to ensure its not corrupted. Also I've tried restarting my PC and tried all 5 USB ports.
Anyone have any other ideas other than start moaning to Samsung and trick them into giving me a new phone??
Thanks in advance,
Dark :highfive:
If you don't have tripped knox, you definitively should bring it to warranty.
But I think, by installing root you tripped it already.
Now you have two options. The first is to bring it to warranty and 'pray' that they doen't discover the altered KNOX state.
The second is, you can search for a complete firmware with PIT file and everything.
I see that you understand how to flash phones, but I will again alert you an others that have the same problem and read that post: Be sure to select the PIT file which corresponds to your phone's size (32, 64, 128GB)
However, bring it first to warranty. If they doesn't want to repair, take second option which is PIT flashing. If that doesn't take efect either, you must bring it to repair, and unfortunately, pay to repair this phone.
Tried a different cable?
Samsung Galaxy S7 (SM-G930T) T-Mobile
Info on ODIN Download screen
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: On
WARRENTY VOID: 0x0
QUALCOMM SECUREBOOT: Enabled
RP SWREV: B4(2, 1, 1, 1, 1) K1 S3
SECURE DOWNLOAD: Enabled
I have referenced the guide I followed. GUIDE. I followed all the instructions. After root I used the Debloater and my phone was incredibly slow and inefficient. So, I used the fix V15. Yet again, slow, hot and a whole host of problems. So, I follow the unroot guide. I continued encounter this error on odin when attempting to unroot.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And this error on my phone:
Code:
SW RV CHECK FAIL: [system]Fused 3>Binary 1
After trying at least 4 different AP's
Code:
TMB-G930TUVS2APB8-20160317155535
TMB-G930TUVU2APC8-20160402115527
TMB-G930TUVU1APB6-20160310103828
TMB_G930TTMB4BQB1
I got frustrated and Held any button I could to get that stupid screen to go away. I was met with "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software. So, I go to do that. And the smart switch software does not support my phone. So, I boot into Recovery mode Wipe Cache, Wipe everything I can and try to reboot and I can only go from DOWNLOAD mode to recovery mode. I read somewhere on here that you can't Rollback firmware so I try the newest firmware and maybe that will work. I encounter no issues in ODIN and no issues on my phone Once my phone reboots it goes to the Samsung Galaxy S7 splash screen with the Unlocked lock and doesn't do anything past that. So I try to boot to recovery mode and that's when I get caught in a loop. My phone went from a flashing "Recovery booting" then if I tap a bunch of VOL UP/DN HOME and POWER combinations It will go to splash screen and flash the splash screen numerous times. I can now get it back to Download mode after messing around with it. But I have no idea what I need to do.
If I need to provide any more information let me know.
How Do I mark this as solved? I Used ODIN to update my bootloader to the newest version. then used the most current AP CP and CSC there is. It's booted up and installed. Now I'm just restoring and Going to restart to make sure everything is working correctly.
Hey guys, I've come into possesion of a Galaxy Note 5 that my cousins seemed to have messed with. A long while back I played with flashing firmware etc on my own phones so I assume that is what happened here. It attempts to start up, getting to the Note 5 splash screen then black screens, then splash screen and so on. I couldn't stop it without a hard reset (Volume down + Lock).
The phones details:
Samsung Galaxy Note 5 (was known working no more than a week ago) Product name: SM-N920I I saw version 6.0.1 somewhere in the menus, I believe this to be the current version of android available to Note 5 phones in Australia? I cant find the build number anywhere that I can access.
Has anyone got any clues? I'll include the ODIN screenshot and text from the phone in download mode. It may also be worth noting I can get into recovery mode, but not safe mode. I've tried wiping partitions etc, nothing there worked.
Download Mode pre failed flash:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N902I
CA_ TYPE: CA_3
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download : Enabled
KNOX WARRENTY VOID: 1 (0x0500)
RP SWREV: B:3 K:0 S:1
I gain "SECURE CHECK FAIL : (BOOTLOADER)" after the failed ODIN flash.
Recovery menu shows -
Android Recovery
MMB29K.N920IDVS3BQA3
samsung/nobleltedv/noblelte
6.0.1/MMB29K/N920IDVS3BQA3
user/release-keysAt the bottom -
Supported API: 3
dm-verity verification failed...
I can't post a screen shot of ODIN due to an inactive account, so I will copy paste that text here as well.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1205)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Like I said above, the phone was working fine last week, saw it myself at a family get together. He said something about not being able to play Mario Run, and I've heard there are issues with rooted devices with Mario Run so perhaps hes tried to unroot the device and messed up the process?
I'm fairly tech savvy, so I should be able to fix it. I just don't know where to really go from here thanks to lack of experience.
How screwed is this phone?
EDIT: I also just want to state that I couldn't find any info about the "SECURE CHECK FAIL : (BOOTLOADER)" message anywhere. A lot about aboot and other stuff, but no bootloader.