Hello,
I tried to root this device with cf-autoroot and Odin 3.07 yesterday. But it just didn't do anything. After felt 20mins I cancled the process with no good result :/
Now I'm getting the message:
"firmware upgrade encountered an issue. please select recovery mode in kies & try again."
-I tried it via Kies, but it needs some code I don't have.
-I downloaded stock Rom 4.4.2 and flashed it via Odin 3.09 but no success.
Odin just won't let me flash anything. I don't know why.
-While flashing Kies is off, drivers are installed (it's Added! In Odin) and it's not the first time I'm doing this. I have no idea. I tried different usb-ports. No success. First time I face this problem.
Now I read about Pit file, but I have no clue.
Every help is much appreciated.
Thank you so much
Red
I guess the code is under your battery
Okaay. I will give it a try. Next time! The problems solution was to flash a custom recovery first.
redplate said:
Hello,
I tried to root this device with cf-autoroot and Odin 3.07 yesterday. But it just didn't do anything. After felt 20mins I cancled the process with no good result :/
Now I'm getting the message:
"firmware upgrade encountered an issue. please select recovery mode in kies & try again."
-I tried it via Kies, but it needs some code I don't have.
-I downloaded stock Rom 4.4.2 and flashed it via Odin 3.09 but no success.
Odin just won't let me flash anything. I don't know why.
-While flashing Kies is off, drivers are installed (it's Added! In Odin) and it's not the first time I'm doing this. I have no idea. I tried different usb-ports. No success. First time I face this problem.
Now I read about Pit file, but I have no clue.
Every help is much appreciated.
Thank you so much
Red
Click to expand...
Click to collapse
The latest FW in Sammobile starting from Hungary till Bulgary they fail at hidden file in Odin, you need to flash custom recovery to solve that issue....
@Muhammad Rihawi, Also having the same problem. Somehow, i thought the solution ws flashing a pit file... Let us know if flashing a custom recovery sorts out the problem for ya..
Inimaga said:
@Muhammad Rihawi, Also having the same problem. Somehow, i thought the solution ws flashing a pit file... Let us know if flashing a custom recovery sorts out the problem for ya..
Click to expand...
Click to collapse
Yes Pit file will solve it but we don't have it...
you can flash root or custom recovery, either of both will work.
From two days i just flash bulgari FW then chanfire Root via odin and its works
Muhammad Rihawi said:
Yes Pit file will solve it but we don't have it...
you can flash root or custom recovery, either of both will work.
From two days i just flash bulgari FW then chanfire Root via odin and its works
Click to expand...
Click to collapse
I don't get it, after flashing the stock Firmware, which failed at hidden. The status bar on the phone stopped and seemed to freeze... I flashed the cf-auto root but it failed... then removed the battery, rebooted into download mode and reflashed the cf-auto root then in odin i saw passed but when the phone rebooted, it was stuck on the bootscreen. After waiting endlessly, removed the battery and tried to enter the recovery mode but it simply wouldnt go there.... Did i miss anything???
Inimaga said:
I don't get it, after flashing the stock Firmware, which failed at hidden. The status bar on the phone stopped and seemed to freeze... I flashed the cf-auto root but it failed... then removed the battery, rebooted into download mode and reflashed the cf-auto root then in odin i saw passed but when the phone rebooted, it was stuck on the bootscreen. After waiting endlessly, removed the battery and tried to enter the recovery mode but it simply wouldnt go there.... Did i miss anything???
Click to expand...
Click to collapse
flash the FW via odin after its failed at hidden file just remove the cable and the battery, re enter the battery and run to download mode straight connect the cable flash custom recovery or cf-auto root after it's success just remove the cable and the device will restart and boot...
in odin keep everything unticked just auto restart ticked.
Life Saver!!! it worked!!! thank you!
Inimaga said:
Life Saver!!! it worked!!! thank you!
Click to expand...
Click to collapse
you are welcome
Related
I've been trying to fix the wifi issues after installing WanamLite v4.2.
I've tried flashing with Odin the MJ5 bootloader (supplied from Wanam) with no success. Also, I've tried flashing the wifi fix supplied from Dr.Ketan, again with no success. In one of those attempts flashing failed, as indicated by Odin. Now all I get is this warning: "firmware upgrade encountered an issue. please select recovery mode in kies & try again."
Can't do anything else, no recovery and no download mode. Help?! :/
EDIT: Actually, I can get into download mode after all...
paps79 said:
I've been trying to fix the wifi issues after installing WanamLite v4.2.
I've tried flashing with Odin the MJ5 bootloader (supplied from Wanam) with no success. Also, I've tried flashing the wifi fix supplied from Dr.Ketan, again with no success. In one of those attempts flashing failed, as indicated by Odin. Now all I get is this warning: "firmware upgrade encountered an issue. please select recovery mode in kies & try again."
Can't do anything else, no recovery and no download mode. Help?! :/
EDIT: Actually, I can get into download mode after all...
Click to expand...
Click to collapse
If you can access download mode Then you can stop panicking.
It maybe that you need to flash a stock rom. First though I would make sure that all the usb drivers on you pc are correct. Personally I used odin 3.04 when I flashed Dr ketan wifi patch but i believe 3.09 is whats mostly used.
---------- Post added at 04:08 PM ---------- Previous post was at 04:05 PM ----------
First you could go to Phil recovery (Link in my sig) and download the appropriate file to flash via odin whilst your in download mode. After there you should be able to flash a rom through recovery as normal but as I say I'd be uninstalling the usb drivers and refreshing them
tonylee000 said:
If you can access download mode Then you can stop panicking.
It maybe that you need to flash a stock rom. First though I would make sure that all the usb drivers on you pc are correct. Personally I used odin 3.04 when I flashed Dr ketan wifi patch but i believe 3.09 is whats mostly used.
---------- Post added at 04:08 PM ---------- Previous post was at 04:05 PM ----------
First you could go to Phil recovery (Link in my sig) and download the appropriate file to flash via odin whilst your in download mode. After there you should be able to flash a rom through recovery as normal but as I say I'd be uninstalling the usb drivers and refreshing them
Click to expand...
Click to collapse
Thanks Tony, I'll give it a try.
paps79 said:
Thanks Tony, I'll give it a try.
Click to expand...
Click to collapse
How is it going? This is why i avoid ODIN at all costs.....i completely destroyed a galaxy player 5.0 in odin once.....now only use it too root my phone and that's it. Recovery is 1000 times more efficient & safer
paps79 said:
I've been trying to fix the wifi issues after installing WanamLite v4.2.
I've tried flashing with Odin the MJ5 bootloader (supplied from Wanam) with no success. Also, I've tried flashing the wifi fix supplied from Dr.Ketan, again with no success. In one of those attempts flashing failed, as indicated by Odin. Now all I get is this warning: "firmware upgrade encountered an issue. please select recovery mode in kies & try again."
Can't do anything else, no recovery and no download mode. Help?! :/
EDIT: Actually, I can get into download mode after all...
Click to expand...
Click to collapse
well i had the same problem tried going back to stock from dn3 just flashed the recovery and everything good here now
Mashed_Potatoes said:
How is it going? This is why i avoid ODIN at all costs.....i completely destroyed a galaxy player 5.0 in odin once.....now only use it too root my phone and that's it. Recovery is 1000 times more efficient & safer
Click to expand...
Click to collapse
I've always used odin with absolute fear lol as you say - only when there's no other option ie rooting etc. But I didn't see any other option now I want 4.3. I used odin 3.04. I made sure the usb driver had installed correctly and i used the wifi patch by Dr ketan on the pda tab and it all worked out fine
Great that all is fine in the end. Please mark your post as [SOLVED]. Will help others.
Sent from my GT-N7100 using Tapatalk
Mashed_Potatoes said:
How is it going? This is why i avoid ODIN at all costs.....i completely destroyed a galaxy player 5.0 in odin once.....now only use it too root my phone and that's it. Recovery is 1000 times more efficient & safer
Click to expand...
Click to collapse
I've just flashed PhilZ Touch recovery as per instructions and then it rebooted normally into Wanamlite. Thanks again Tony!
Now onto the wifi issues. Is wifi supposed to be completely disabled...as it is now, I can see networks but I can't connect.
Should I just flash again Dr.Ketan's wifi patch?
Also, I get this message from the notification panel.
"SE for android has been disabled. Restart your device to restore your security settings." Ideas?
paps79 said:
I've just flashed PhilZ Touch recovery as per instructions and then it rebooted normally into Wanamlite. Thanks again Tony!
Now onto the wifi issues. Is wifi supposed to be completely disabled...as it is now, I can see networks but I can't connect.
Should I just flash again Dr.Ketan's wifi patch?
Also, I get this message from the notification panel.
"SE for android has been disabled. Restart your device to restore your security settings." Ideas?
Click to expand...
Click to collapse
You should try to flash the Hurricane ROM, it's running on the newest 4.3 JB, the MK4 build. Wi-Fi works perfectly, no need to patch anything.
Finally...after flashing the MJ9 modem and then the MJ5 bootloader with no success, the remedy was to just reinstall the rom. Wifi is now fixed!
Thanks for the support guys.
EDIT: double post
paps79 said:
I've been trying to fix the wifi issues after installing WanamLite v4.2.
I've tried flashing with Odin the MJ5 bootloader (supplied from Wanam) with no success. Also, I've tried flashing the wifi fix supplied from Dr.Ketan, again with no success. In one of those attempts flashing failed, as indicated by Odin. Now all I get is this warning: "firmware upgrade encountered an issue. please select recovery mode in kies & try again."
Can't do anything else, no recovery and no download mode. Help?! :/
EDIT: Actually, I can get into download mode after all...
Click to expand...
Click to collapse
Flash stock rom from odin.
You can get these from sammobile.
After trying to update to kit kat my note 2 will not get past the "note 2" splash screen. What sucks even worse is that I can't get into recovery to install a new rom. I've been searching tons of threads and whatnot across XDA and other websites but nothing has worked.
What I've tried:
-Flashing TWRP, CWM, Philz recoveries. Odin says they succeeded but I still can't get to any of them.
-Flashing srock roms downloaded from multiple sources. When I try this I get an error in odin, usually fails right after sboot.bin
-Using other versions of Odin, different usb's, etc. Same stuff happens no matter what.
-Kies, but it won't connect and says device is unsupported.
-Android toolkit, but i couldn't really do much with it in this state
-I even tried re-partitioning with some t0lte pit file. This really didn't change anything.
-I found an "mk4_recovery.tar" file in a thread on here. That finished and succeeded, but I still can't get anywhere, However I did notice that this changed the "current binary" on my phone from "custom" to "official samsung binary." I'm not sure if that is important or not.
I feel like I am running out of options and my phone is hard-bricked. You guys are my last hope and I'm hoping there's something you guys can help me with!! If you have anything I can try please let me know!!!
SCAND1UM said:
After trying to update to kit kat my note 2 will not get past the "note 2" splash screen. What sucks even worse is that I can't get into recovery to install a new rom. I've been searching tons of threads and whatnot across XDA and other websites but nothing has worked.
What I've tried:
-Flashing TWRP, CWM, Philz recoveries. Odin says they succeeded but I still can't get to any of them.
-Flashing srock roms downloaded from multiple sources. When I try this I get an error in odin, usually fails right after sboot.bin
-Using other versions of Odin, different usb's, etc. Same stuff happens no matter what.
-Kies, but it won't connect and says device is unsupported.
-Android toolkit, but i couldn't really do much with it in this state
-I even tried re-partitioning with some t0lte pit file. This really didn't change anything.
-I found an "mk4_recovery.tar" file in a thread on here. That finished and succeeded, but I still can't get anywhere, However I did notice that this changed the "current binary" on my phone from "custom" to "official samsung binary." I'm not sure if that is important or not.
I feel like I am running out of options and my phone is hard-bricked. You guys are my last hope and I'm hoping there's something you guys can help me with!! If you have anything I can try please let me know!!!
Click to expand...
Click to collapse
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.
michael85tx said:
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
Click to expand...
Click to collapse
What a nightmare!
I odined back to stock MK4, did the 4.4.2 OTA last night. Then did the CF Auto Root via odin, installed custom recovery. The phone is currently on pageplus network. I started messing around, did the GSM Mod, then tried the international and domestic sim unlock procedures. The result was not satisfying, so I tried flashing different modems. Eventually CDMA works, but GSM not. So I made a huge mistake by attempting to downgrade from NE2. And of course failed. Now the phone can't register on either CDMA or GSM.
So once I flash M2 Stock with Count Reset, I can play with the 4.4.2 OTA zip again to get a 100% 4.4.2 system?
michael85tx said:
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.
Click to expand...
Click to collapse
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!
SCAND1UM said:
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!
Click to expand...
Click to collapse
I did the procedure everything went well but is there any way to update lastest firmware kitkat as i tried to and keep having to do the same procedure to unbrick it? thanks
brooklynman2020 said:
I did the procedure everything went well but is there any way to update lastest firmware kitkat as i tried to and keep having to do the same procedure to unbrick it? thanks
Click to expand...
Click to collapse
The best way to do the upgrade (since you know how to get your phone back if it happens again) is to just simply use Odin now to flash the 4.4.2 tar file thanks to "garwynn" for taking the time in making it.
http://forum.xda-developers.com/showthread.php?t=2780984
since most of my links don't work after I post lol I'm giving the download too. I tried uploading it but the file size is too big to post. So I hope this link works let me know and I'll re-upload it and post another link if the link stops working. 4.4.2 stock rom .tar
---------- Post added at 03:05 AM ---------- Previous post was at 02:55 AM ----------
lilila said:
What a nightmare!
I odined back to stock MK4, did the 4.4.2 OTA last night. Then did the CF Auto Root via odin, installed custom recovery. The phone is currently on pageplus network. I started messing around, did the GSM Mod, then tried the international and domestic sim unlock procedures. The result was not satisfying, so I tried flashing different modems. Eventually CDMA works, but GSM not. So I made a huge mistake by attempting to downgrade from NE2. And of course failed. Now the phone can't register on either CDMA or GSM.
So once I flash M2 Stock with Count Reset, I can play with the 4.4.2 OTA zip again to get a 100% 4.4.2 system?
Click to expand...
Click to collapse
sorry for the late reply but yes you can. I have gone back and forth trying to decide which 4.4.2 works best for service and style. lol right now I'm on 4.4.2 stock rooted (took FOREVER to get rooted I think it just finally clicked in I had given up). but there's already a .tar file for 4.4.2 you can just flash the .tar file and you have a OTA STOCK (unrooted) version of 4.4.2 for SPRINT only. It's the easiest way to get your phone back to working if it' soft bricked or just won't load recovery.
...NOTE... you can UPGRADE flash your bootloader (i.e. ... M2 .. MK4 ...N2) from Odin. You just CAN NOT downgrade firmware via Odin if you're going to go back to 4.1/4.2/4.3 versions. You will 99% of the time get "failed" at write to sboot .. for recovery I recommend Philz as it clears your cache and such when you flash roms and gapps and such for you.
---------- Post added at 03:10 AM ---------- Previous post was at 03:05 AM ----------
SCAND1UM said:
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!
Click to expand...
Click to collapse
You're welcome lol when it happened to me I wanted to punch a wall or something because I couldn't make a call to help me and there was no way Sprint would have helped me. It took me 8 hours to find it that day lol I had almost started giving up hope
You may already know this, but you also want to read up and see what versions of odin people are having success with. As well as what custom recoverys (and versions) seem to be working.
I used Odin v3.09 with no problems. Heard that others had success with v3.07
Flashed and running Philz custom recovery v6.0.4.5
I flashed update-supersu-v1.94.zip (originally flashed cwm-supersu-v0.94.zip, which DID NOT work). Supersu is a little buggy. On both the note2 and s3, after install apk would fc. Went to play store and updated supersu, supersu will then work (even "partially" disables knox for you)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
You may already know this, but you also want to read up and see what versions of odin people are having success with. As well as what custom recoverys (and versions) seem to be working.
I used Odin v3.09 with no problems. Heard that others had success with v3.07
Flashed and running Philz custom recovery v6.0.4.5
I flashed update-supersu-v1.94.zip (originally flashed cwm-supersu-v0.94.zip, which DID NOT work). Supersu is a little buggy. On both the note2 and s3, after install apk would fc. Went to play store and updated supersu, supersu will then work (even "partially" disables knox for you)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Yeah that's true I use Odin 3.09 Philz Recovery (latest version if that doesn't work the 6.07.09 has had some good success) and SU v1.93 is the one I have.
Stuck with 4.4.2 OTA
michael85tx said:
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.
Click to expand...
Click to collapse
Followed this procedure after accepting OTA and couldn't get chainfire autoroot to work. This worked flawlessly for me and I'm flashing again !!!!
lewisyiv said:
Followed this procedure after accepting OTA and couldn't get chainfire autoroot to work. This worked flawlessly for me and I'm flashing again !!!!
Click to expand...
Click to collapse
Where is the fix file for download? I cant flash the tar file, all time show fail in odin, I was try with firmware 4.4.2, 4.2, 4.1.2 and nothing my note 2 enter in download mode but not in recovery mode, alwais is in bootloop in logo... maybe I have brick?
vegitamaster66 said:
Where is the fix file for download? I cant flash the tar file, all time show fail in odin, I was try with firmware 4.4.2, 4.2, 4.1.2 and nothing my note 2 enter in download mode but not in recovery mode, alwais is in bootloop in logo... maybe I have brick?
Click to expand...
Click to collapse
Two post above you or in the quote above you has the link for fix. You need to follow the first link (xda thread link) and it will take you to my post that has the upload.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Second post in this thread helped me immensely. Thank you!
I broke my note 2 that I had rooted and was running rwilco's mostly stock rom on.
Got another note 2 off craigslist and decided I should root it too for speed and for tethering. Tried the liquid smooth rom and it failed leaving me with no ROM.
Every ROM I tried failed until I found this thread and used Odin to flash "ALL_SPT_L900VPUCNE2_L900SPTCNE2_1561791_REV04_user_low_ship.tar.md5" that was linked.
So phone is now running 4.4.2 can I safely try again to load a custom ROM?
What do I need to do to make sure I don't have the same problem?
I'm not really savvy with this stuff but I can follow destructions
does any of the above steps wipe internal data?
Hi all, I'm hoping someone can help, but I'm not too optimistic. I have a SGH-M919 (T-Mobile Galaxy S4) that had a tripped KNOX bootloader and I had been installing custom ROMs on it. I wanted to ODIN back to stock, but it has caused all kinds of problems.
I was using ODIN v3.09 to ODIN the NB4 complete .tar file from Sammobile under the "AP" section with only Auto Reboot and F. Reset Time checked. It got what looked like about 95% complete and then showed FAILED. It gets to a point where it will say:
"Complete(Write) operation failed"
Upon rebooting, the phone says "Firmware upgrade ecountered an issue. Please select recovery mode in Kies & try again."
The phone will go into Download mode still but it will not go into Recovery mode.
After the above combination failed, I've tried using ODIN v.3.07 and v1.85, different official and unofficial firmwares (NB4, MK2, Fenny's NB4), tried various USB ports on my computer, and even tried another computer. Each time ODIN fails, and sometimes much earlier in the process.
I also tried installing using Kies after all of the above failed, but Kies will not recognize the phone at all.
Is it dead, or does anyone know of something else I can try? Upon my searching, most recommendations to "brick" problems seems to just be to ODIN like I did above =/.
Thank you for any help!
Have you tried flashing recovery and then booting right away to it?
serio22 said:
Have you tried flashing recovery and then booting right away to it?
Click to expand...
Click to collapse
I was able to flash a recovery, which is good news. The one I had on hand was Philz, which I could go straight into. Now I have a problem with /data not being able to mount, and no ROM I install from recovery seems to boot, even a full nandroid backup... Any ideas from there?
UPDATE: I flashed TWRP 2.5.0.2 and was able to format /Data, reinstalled a ROM, and it booted!! Thanks so much!!
Mralexander006 said:
UPDATE: I flashed TWRP 2.5.0.2 and was able to format /Data, reinstalled a ROM, and it booted!! Thanks so much!!
Click to expand...
Click to collapse
Good! That's what I was gonna suggest
Mralexander006 said:
I was able to flash a recovery, which is good news. The one I had on hand was Philz, which I could go straight into. Now I have a problem with /data not being able to mount, and no ROM I install from recovery seems to boot, even a full nandroid backup... Any ideas from there?
UPDATE: I flashed TWRP 2.5.0.2 and was able to format /Data, reinstalled a ROM, and it booted!! Thanks so much!!
Click to expand...
Click to collapse
Hi. I'm having the same issue here. Can you please elaborate on what you did exactly? Thanks
hyperenigma said:
Hi. I'm having the same issue here. Can you please elaborate on what you did exactly? Thanks
Click to expand...
Click to collapse
ive read forums and trying different things for 6+ hours and was having no luck.
i read that someone took it to a best buy where they have a samsung kiosk because they can reflash the firmware.
i took it there but they were unable to reflash it.
they had the same problems i was having.
i literally just tried odin again and it worked.
i think mayb them hooking it up to their computer did something to it which then allowed me to get it to work.
if that doesnt work you can also send it back to samsung to have it reflashed,
both are FREE of charge. ( most people dont know that.
best of luck to you.
Hey sorry, have been swamped with work. Did you ever get it working or still need help?
Using ODIN to flash a complete ROM would always fail, bit have you tried flashing just TWRP recovery? For me that worked, and from there I could reformat the /data folder, and flash a new ROM in recovery. Never was able to use Odin for a full ROM but that method was good enough.
Can someone please help? I have followed the instructions and have rooted my T900, but now everytime I try to install a custom recovery, TWRP, it doesn't work. I've flashed it a couple times and every time I try to boot into recovery it just goes to standard Android recovery KOT49H.T900UEUANK1. My KNOX has been tripped, is that causing a problem? Any and all help is greatly appreciated in this matter.
travazz said:
Can someone please help? I have followed the instructions and have rooted my T900, but now everytime I try to install a custom recovery, TWRP, it doesn't work. I've flashed it a couple times and every time I try to boot into recovery it just goes to standard Android recovery KOT49H.T900UEUANK1. My KNOX has been tripped, is that causing a problem? Any and all help is greatly appreciated in this matter.
Click to expand...
Click to collapse
Did you flash via odin or an app? Knox being tripped shouldnt matter.
To fix the problem when flashing in odin, just untick autoreboot in odin and reboot manually.
Which instructions did you follow?
travazz said:
Can someone please help? I have followed the instructions and have rooted my T900, but now everytime I try to install a custom recovery, TWRP, it doesn't work. I've flashed it a couple times and every time I try to boot into recovery it just goes to standard Android recovery KOT49H.T900UEUANK1. My KNOX has been tripped, is that causing a problem? Any and all help is greatly appreciated in this matter.
Click to expand...
Click to collapse
I have attempted rooting several times with Odin 3.07 & 3.09 using the CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5 file but it always fails after the first step. Which instructions did you follow? Any help would be appreciated.
DUHAsianSKILLZ said:
Did you flash via odin or an app? Knox being tripped shouldnt matter.
To fix the problem when flashing in odin, just untick autoreboot in odin and reboot manually.
Click to expand...
Click to collapse
Just tried that and it is still not working. I can root and keep root, every time I reset or try to lpad custom recovery it just hangs at the Samsung screen. Any other suggestions?
travazz said:
Just tried that and it is still not working. I can root and keep root, every time I reset or try to lpad custom recovery it just hangs at the Samsung screen. Any other suggestions?
Click to expand...
Click to collapse
try flashing the TWRP 2.8.0.x.tar file in odin. should work. i had a problem where TWRP 2.8.5.x would not work on my tab pro 12.2. after installing TWRP 2.8.0.x fixed the problem.
jvilla785 said:
try flashing the TWRP 2.8.0.x.tar file in odin. should work. i had a problem where TWRP 2.8.5.x would not work on my tab pro 12.2. after installing TWRP 2.8.0.x fixed the problem.
Click to expand...
Click to collapse
Thank you jvilla785! That's what was going wrong, I now have custom recovery. Thanks man
Adding my thanks
thought my tab was done for...installedthe suggested twrp 2.8.0.x.tar file from techerrata and I'm back where I started- which is not where I want to be but a working tablet is better than a dead tablet- even if it is a Samsung
angelamibrahim said:
thought my tab was done for...installedthe suggested twrp 2.8.0.x.tar file from techerrata and I'm back where I started- which is not where I want to be but a working tablet is better than a dead tablet- even if it is a Samsung
Click to expand...
Click to collapse
check this post
Hi, I've digged through much of xda and not found a satisfying answer. My phone boots into download, is detected by odin (7,8,9,12 all ok), and whatever I do, odin says it was successfull. I tried flashing the stock ROM, the official ROM with 4.4.2, pit file, all in vain. Before crashing my s4 was running cm13 with twrp3.0.2-1. When turning phone on, it just displays "Samsung GalaxyS4 mini / GT-I9195 label on black screen, with "set warranty bit: kernel" in upper left corner. Download mode boots ok, but recovery - twrp 3.0.2-1 logo is displayed for about 8 seconds, and then phone reboots to "normal" mode - displaying the logo.
It would be great if some of you had an idea of what to do as I've been trying on my own for 3 weeks now and nothing changed for better.
As there are people looking at this thread, it would be great to hear from you! I still did not succeed in flashing anything, twrp screen shows for 8sec and then phone reboots to normal, which is samsung splash screen. I'm using samsung drivers, have tried different usb ports, used different computers, still nothing.
Did you try 4 files firmware?
http://firmware.smartphonewp.com/download-samsung-galaxy-s4-mini-gt-i9195-full-firmware-4-files/
Hi,
Unfortunately I can't help you here, but I have a similar problem and it might be related to yours. I have also have a Samsung S4 mini GT-i9195 LTE. Originally with Android 4.4.2 but lately with no OS at all. And I can't figure out how to get one back. What happened, chronologically and (very) detailed:
I rooted my phone with KingoRoot, which worked fine as far as I can tell. When I didn't like the KingoSuperUser-App I installed SuperSU. But it failed to work, apparently because of Knox or something like that. I later wanted to flash my phone with a LineageOS ROM (lineage-14.1-20170505-nightly-serranoltexx-signed.zip) and therefore I wanted to install TWRP as custom recovery. As the usual way with Odin seemed a bit complicated to me at the time, I decided to install the "TWRP Manager" App, which went well. But as soon as I tried to install my ROM with it, it asked if my bootloader was unlocked. So, after searching the internet about that and it said that Samsung phones usually have an unlocked bootloader and only have to be rooted, I went on with installing the LineageOS ROM using the TWRP Manager. Mind you, I am not talking about the custom recovery that you have to boot in to by pressing Vol-Up+Home+On/Off-Button, I am talking about the app that you can download and just needs root permissions to do the same stuff. I had downloaded the ROM-zip onto my SDcard before and wanted to flash it from there.. Now, when I let the app go on, the screen just went blank. And this might be the moment I overreacted. I panicked and tried to start my phone again. But it only went as far as the Samsung logo and didn't go further and I had to pull the battery to turn it off. I then tried to boot into recovery mode by pressing Vol-up+home+On with no result, I then tried with Vol-down+home+On and found Download mode with:
Code:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1 -> this one might have been 0x0 the first time
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
After some research I downloaded Odin3 (v3.12.5) and managed to flash TWRP (2.6.3.0) onto my phone. And I found the ROM-zip file, but it would not let me unpack and flash it and it didn't help to uncheck the "Zip file signature verification." When I tried to flash I always got the same error massage:
Code:
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/external_sd/lineage-14.
Checking for MD5 file...
Skipping MD5 check: no MD5 file foun
Warning: No file_contexts
Target: 1493971678
detected filesystem ext4 for /dev/bl
Can't install this package on top of
E: Error executing updater binary in
Error flashing zip '/external_sd/lin
Updating partition details...
And it gives a "failed" response. Now, I tried moving the zip to internal_sd and flashing with no better result. I also tried to flash a stock ROM which I downloaded from Sammobile.com. This didn't work either. The adb push method and the sideload didn't work out either.
Interestingly, when I go to "Reboot" -> "Power Off" to turn the phone off I get a dialog:
No OS installed! Are you sure you wish to power off?
-> "Swipe to power off"
-> then comes the next dialog:
Install SuperSU?
Your device does not appear to be rooted.
Install SuperSU now?
This will root your device.
-> "Swipe to install."
Which had no effect at all but to inform me that my phone apparently isn't rooted after all. I therefore downloaded the S4Mini_RootKit_v2.zip and tried flashing it, which was successful. But I still got the same dialog when powering off and I couldn't install the zip files either.
That's where I am now and I really don't know what to try or do next. As I could flash TWRP onto my phone, shouldn't it also be possible to flash an OS?
I hope this was a precise enough description. If someone has any further question, please ask.
@albaCross @desolate_sorrow
Try an factory reset with the recovery.
Download a multiple Firmware from Sammy with PIT.file
Boot into Download mode.
Download Odin 3.07 or 3.09 not newer
Flash all Files with Pit.file
Reboot.
bierma32 said:
@albaCross @desolate_sorrow
Try an factory reset with the recovery.
Download a multiple Firmware from Sammy with PIT.file
Boot into Download mode.
Download Odin 3.07 or 3.09 not newer
Flash all Files with Pit.file
Reboot.
Click to expand...
Click to collapse
I posted this thread precisely because my recovery DOES NOT work. No option for factory reset. It just reboots after ~8 secs of twrp 3.0.2-1 screen. Flashed with ODIN 3.09, official intern. ROM from sammobile into AP and drive. google. com /file/d /0Bx2R0nz6jh17bllKenctWnVsWkE/edit <-- this PIT file. Also tried this pit with different versions of twrp - 2.6, 3.0, 3.1 - still no change at all, no recovery booting
@desolate_sorrow
But you are not tried a multiple ROM with PIT.file.
You flashed only a Single File ROM under AP.
On the multiple ROM you can extract the CSC File and than you have the PIT.
Pit you can only flash with Odin and a ROM.
bierma32 said:
@albaCross @desolate_sorrow
Try an factory reset with the recovery.
Download a multiple Firmware from Sammy with PIT.file
Boot into Download mode.
Download Odin 3.07 or 3.09 not newer
Flash all Files with Pit.file
Reboot.
Click to expand...
Click to collapse
Perfect! Worked like a charm for me! While factory reset itself did nothing to improve the phone, the other stuff worked. I flashed my phone with the .tar.md5 file I extracted from the .zip file (from sammobile.com) using Odin 3.09 and my phone works again, thank you soo much!
I then rooted it again and flashed LineageOS (lineage-14.1-20170505-nightly-serranoltexx-signed.zip) onto it. It worked but during the first startup I got the error massage "Setup wizard keeps stopping". I then tried the newest (20170519) version and got the same error again. Any Idea how I might repair this?
About the pit. file: what exactly is the difference between this multiple pit file, a "usual" pit file and the .tar.md5 file I used?
On a multiple ROM file is all separately, Bootloader, Phone , Modem and CSC file.
The PIT file is the partion File of the RAM. You can extract this seperat from the CSC file.
To the issue the the gapps. Try an older Version or flash first the LOS and setup WiFi.
Than flash Opengapps with wipe cache and dalvik than normally works the wizard.
bierma32 said:
@desolate_sorrow
But you are not tried a multiple ROM with PIT.file.
You flashed only a Single File ROM under AP.
On the multiple ROM you can extract the CSC File and than you have the PIT.
Pit you can only flash with Odin and a ROM.
Click to expand...
Click to collapse
i got the same problem, that the recovery is not working, flashing a multiple rom with pit doesn't help (neither recovery nor rom is working).
but i guess the main problem is, that i got a REV02 phone and I only can find REV01 firmware (e.g. this one here: http://firmware.smartphonewp.com/download-samsung-galaxy-s4-mini-gt-i9195-full-firmware-4-files/)
are there any REV02 firmwares out there, which maybe can help? or does anyone (@bierma32, @albaCross or @desolate_sorrow) got any other ideas?
bierma32 said:
To the issue the the gapps. Try an older Version or flash first the LOS and setup WiFi.
Than flash Opengapps with wipe cache and dalvik than normally works the wizard.
Click to expand...
Click to collapse
Thanks for replying. I tried flashing the LOS ROM and booting without gapps. According to TWRP it was successful. But when I booted for the first time I got similar error messages as before "[any app name] stopped running". Just with several names and all of them one after the other. Most of them appear to be named something like .android.com with different pre- and suffixes.
I then tried a more actual version of LOS with a similar result (same error message, similar names). After several times I decided to go back to my previously created TWRP backup (of the stock ROM with root access and several of the more annoying apps removed, also I had checked all partitions when backing up): I did a custom recovery and recovered my backup file and it seemed to work, TWRP said "success". On booting I again had the now so familiar error messages on the screen. Same happened when I flashed the stock ROM and recovered my backup after that, or at least tried. While TWRP still said it was a success it would not get past the screen where you choose your language.
After this I gave up and went back to the stock ROM and "rebuilt" my old phone. Maybe my phone just doesn't like anything but the stock ROM, so I should probably just stick to it.
But, just out of curiosity, what exactly is the problem with the phone if neither custom ROMs nor system backups work on it properly?
1of16 said:
i got a REV02 phone and I only can find REV01 firmware
Click to expand...
Click to collapse
this was me just 2 days ago!
i was on lineage os 7.1.1 with TWRP and was stuck wanting to go back to stock.
i flashed many many roms and they all failed in ODIN.
Eventually i found a Netherlands ROM that did not fail on the REV02 check - might be worth a go!
my thread
good luck!
Hello,
I own s4 mini gt i 9192
i have rooted it with kingroot when it was in a stock firmware, then i have decided to install lolipop rom with twrp with superuser in it, everything gone smooth i have used my phone over 3 months, one morning i woke up, the battery level was 43 %, i have set it in the charger returned back after 30 minutes and have seen that it only got 3% energy, pulled out the battery and inserted back, charged the phone for a while in a turned off mode, and powered it one, strangely it started but showed some kind of upgrading panel on the main screen than immediately it turned off and started to restart again and again, i have booted it in recovery mode, wiped the cache restarted the phone, main screen turned on to enter my password but in a seconds it went black again, opened it up in twrp recovery mode, went into advanced settings and wiped something in there(i can not exactly remember the name of the thing i have wiped but there was an option to wipe it in twrp advanced settings, it warned me "that my phone would not start correctly but anyway i have done it") after it's wipe phone started with s4 mini logo, and restarted like this over and over again, in recovery mode it only shows twrp logo no options panel to access to internal or external sd card, neither wipe or factory just nothing but twrp logo. I have flashed the 4 files recovery pack, (pit, ap,csc and etc,) but same it is never helped, i have used multiple recoveries, and the original stock rom from sammobile, but it has nor cure, i am a newbie on tech and xda please if you could help me, i have tried to post it to xda forms but i did not find a button to post a thread, thanks.