Related
Dear All,
I'm in need of some urgent help. I have a S4 GT-I9500 which was running Kitkat stock 4.4.2 unrooted. I noticed the Lollipop update available OTA and so I downloaded and applied it. The installation went ok but after that the phone has just not worked. It comes to the homescreen, there comes an error stating that "An application needs and update" and below that "Requested by Google Play services". The homescreen appears on the screen for less than 5 seconds and it reboots. This goes on and on making the device really hot. There was a massive battery drain as well (from 90% to 30% within 30 mins)
Now the worst part is I hadn't even backed up any of my data. Although my photos are on my external SD, contacts are synced to google but there are some application specific data (whatsapp, few games progress, etc) that I would like to save.
Please help me out. At this point, I dont even care about the lollipop as long as I can get my phone back. I'm also open to rooting it, as my warranty period is over.
OK, I booted into recovery and wiped the cache partition too. No luck.
boogey_man said:
OK, I booted into recovery and wiped the cache partition too. No luck.
Click to expand...
Click to collapse
1. Wipe system, cache and cache partition (data no atm).
2. Reboot in DOWNLOAD MODE and flash via ODIN again Lollipop firmware. You will have to download it of Sammobile.com.
3. I hope this will work :highfive:
Joku1981 said:
1. Wipe system, cache and cache partition (data no atm).
2. Reboot in DOWNLOAD MODE and flash via ODIN again Lollipop firmware. You will have to download it of Sammobile.com.
3. I hope this will work :highfive:
Click to expand...
Click to collapse
Thanks for the reply.
But won't this erase all of the data (whatsapp, few games progress, etc) I want to save ?
boogey_man said:
Thanks for the reply.
But won't this erase all of the data (whatsapp, few games progress, etc) I want to save ?
Click to expand...
Click to collapse
Read the step 1.:
- You will have "Advanced Wipe" on your custom recovery. Click only for wipe system, cache and dalvick cache. In TWRP is:
Joku1981 said:
Read the step 1.:
- You will have "Advanced Wipe" on your custom recovery. Click only for wipe system, cache and dalvick cache. In TWRP is:
Click to expand...
Click to collapse
I haven't installed TWRP. I was only using inbuilt recovery (using volume-up, menu and power buttons) until now.
Please correct me if the below steps on installing TWRP are right:
- download latest twrp for s4 from here: http://www.teamw.in/project/twrp2/191
- flash TWRP to my phone using ODIN 3.09 (Download the above file and flash using Odin in the PDA tab.)
boogey_man said:
I haven't installed TWRP. I was only using inbuilt recovery (using volume-up, menu and power buttons) until now.
Please correct me if the below steps on installing TWRP are right:
- download latest twrp for s4 from here: http://www.teamw.in/project/twrp2/191
- flash TWRP to my phone using ODIN 3.09 (Download the above file and flash using Odin in the PDA tab.)
Click to expand...
Click to collapse
1. This will void you warranty: KNOX 0x1. You dont need care if you are out of warranty.
2. The steps are you following are corrects.
Thanks. I tried it but TWRP is just not getting installed. I flashed using ODIN 3.07 and PDA, but when in restart the phone into recovery mode, it goes back to the Samsung's stock recovery and doesn't have the TWRP. Any suggestions?
Use a different USB port, and don't use a hub. Also be sure you're using the original cable, have the drivers installed, and do not have Kies installed or running.
If necessary, find a later copy of Odin. 3.09 is apparently the standard although 3.10 exists.
Strephon Alkhalikoi said:
Use a different USB port, and don't use a hub. Also be sure you're using the original cable, have the drivers installed, and do not have Kies installed or running.
If necessary, find a later copy of Odin. 3.09 is apparently the standard although 3.10 exists.
Click to expand...
Click to collapse
Right....
Now I receive the below error in ODIN:
<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> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The COM port gets detected. Also, now the boot loop is gone and is replaced by "firmware upgrade encountered an issue" error.
Should I try downloading Kies now?
Kies wouldn't do you much good, as it would find Android 5.0.1 on your S4 and report that there was no update.
You may need to flash with a PIT file in order to correct this as your S4 after the Lollipop update may have had its partition information changed. If that doesn't work, you may have to bite the bullet and do a complete factory reset, which will cost you the data.
Strephon Alkhalikoi said:
Kies wouldn't do you much good, as it would find Android 5.0.1 on your S4 and report that there was no update.
You may need to flash with a PIT file in order to correct this as your S4 after the Lollipop update may have had its partition information changed. If that doesn't work, you may have to bite the bullet and do a complete factory reset, which will cost you the data.
Click to expand...
Click to collapse
Thanks.
Meanwhile, I've tried on another PC too, same issues. "Complete (Write) operation failed." error in ODIN there as well.
PIT file flashing is next on the list, I guess. Any pointers as to how should I start?
And BTW, I don't know how I can wipe complete data, as now there is no way to access the stock recovery. Pressing the "up+menu+power" just opens the "firmware upgrade encountered an issue" error. The boot loop doesn't happen any more. Its just a soft brick now.
Update: I've tried flashing recovery.img (from both CWM and TWRP) using Heimdall. Both were not helpful.
Code:
C:\Heimdall Suite>heimdall.exe flash --RECOVERY recovery.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
ERROR: Failed to retrieve config descriptor
Right...
So I was now able to flash stock 4.4.2 along with adonis.pit. This was a PASS! in Odin. However, still the device didn't boot. Stuck on the Samsung logo.
I did manage to flash CWM recovery on it and I'm now able to boot into recovery. I'll take the backup now and then try to wipe data and flash.
My frustrating first custom ROM attempt: Sought to upgrade my Tab4 (SM-T530NU) from stock KitKat to a LP 5.1 custom ROM. Studied xda-developers forum for hours. Did a full backup to G-drive with Helium Premium (from G-Play). Used ODIN to flash CF-Auto-Root. Used ODIN to flash TWRP 2.8.6.0 (openrecovery-twrp-2.8.6.0-matisse.tar) that I fetched from sub77's metal-build.de site. Booted into recovery and used TWRP to do a backup (Nandroid Backup?) of the Boot, System, and Data partititions to my "Micro SDcard". Used TWRP to do a "Factory Reset" -- wiping Data, Cache, and Dalvik. Then used TWRP to install CyanogenMod 12.1 (cm121_smt530_ArchiDroid_Ffo-891cc1d1bc.zip) and GApps (gapps-5.1-arm-2015-05-03-16-32-37.zip). It all seemed to go smoothly, but then I pressed TWRP's "Reboot" button ...
The reboot caused display of a message "KERNEL IS NOT SEANDROID. SET WARRANTY BIT: RECOVERY" and nothing more happened, so after about 15 minutes I powered off and powered into recovery mode. I did another Factory Reset and again flashed the CyanogenMod and GApps files, then wiped just the Cache and Dalvik Cache, and rebooted. The same static message (KERNEL IS NOT ...) appeared and this time I waited a full 30 minutes before giving up and powering off.
So I rebooted into TWRP recovery and restored my backup, then rebooted. After what initially appeared a normal startup, I received an endless stream of messages on a black screen "Unfortunately, [app] has stopped." I was stumped, but eventually found a tidbit on xda-developers that led me to use TWRP to wipe the Data partitition. That allowed my Tab4 to restart in what seemed a brand-new state. So I re-entered my wifi, Samsung, and Google passwords, e-address, etc. when prompted. Then re-installed Helium from G-Play and attempted to restore my Heluim backup files from my G-drive. I found that the process required that I re-install each app (about 20) from G-Play or the Samsung App site before Helium would restore associated data. Tedious, but it worked.
So I think my Tab4 is useable again, but I remain frustrated at my failures and struggles. What did I do wrong?
So I rebooted into TWRP recovery and restored my backup, then rebooted. After what initially appeared a normal startup, I received an endless stream of messages on a black screen "Unfortunately, [app] has stopped."
Click to expand...
Click to collapse
This is exactly what happens to my friend's s5 when i installed the wrong twrp. I would try to boot it into twrp. Instead i booted in to the normal system recovery (with the android and the exclamation mark) from there i had to do a factory reset that worked again. Now i am pretty sure that the black screen thing wasn't because of your twrp if you could boot into it tough that's just what my experience is
schafer49 said:
My frustrating first custom ROM attempt: Sought to upgrade my Tab4 (SM-T530NU) from stock KitKat to a LP 5.1 custom ROM. Studied xda-developers forum for hours. Did a full backup to G-drive with Helium Premium (from G-Play). Used ODIN to flash CF-Auto-Root. Used ODIN to flash TWRP 2.8.6.0 (openrecovery-twrp-2.8.6.0-matisse.tar) that I fetched from sub77's metal-build.de site. Booted into recovery and used TWRP to do a backup (Nandroid Backup?) of the Boot, System, and Data partititions to my "Micro SDcard". Used TWRP to do a "Factory Reset" -- wiping Data, Cache, and Dalvik. Then used TWRP to install CyanogenMod 12.1 (cm121_smt530_ArchiDroid_Ffo-891cc1d1bc.zip) and GApps (gapps-5.1-arm-2015-05-03-16-32-37.zip). It all seemed to go smoothly, but then I pressed TWRP's "Reboot" button ...
The reboot caused display of a message "KERNEL IS NOT SEANDROID. SET WARRANTY BIT: RECOVERY" and nothing more happened, so after about 15 minutes I powered off and powered into recovery mode. I did another Factory Reset and again flashed the CyanogenMod and GApps files, then wiped just the Cache and Dalvik Cache, and rebooted. The same static message (KERNEL IS NOT ...) appeared and this time I waited a full 30 minutes before giving up and powering off.
So I rebooted into TWRP recovery and restored my backup, then rebooted. After what initially appeared a normal startup, I received an endless stream of messages on a black screen "Unfortunately, [app] has stopped." I was stumped, but eventually found a tidbit on xda-developers that led me to use TWRP to wipe the Data partitition. That allowed my Tab4 to restart in what seemed a brand-new state. So I re-entered my wifi, Samsung, and Google passwords, e-address, etc. when prompted. Then re-installed Helium from G-Play and attempted to restore my Heluim backup files from my G-drive. I found that the process required that I re-install each app (about 20) from G-Play or the Samsung App site before Helium would restore associated data. Tedious, but it worked.
So I think my Tab4 is useable again, but I remain frustrated at my failures and struggles. What did I do wrong?
Click to expand...
Click to collapse
... upgrade from kitkat stock was wrong. You need to install lp stock first to get the bootloader updated.
The kernel is not ... msg can be ignored.
so get stock 5.0.2 and retry.
sub77 said:
... upgrade from kitkat stock was wrong. You need to install lp stock first to get the bootloader updated.
The kernel is not ... msg can be ignored.
so get stock 5.0.2 and retry.
Click to expand...
Click to collapse
Each time I attempted to flash the stock Lollipop 5.0.2 (T530XXU1BOD8_T530OXA1BOD8_HOME.tar.md5) I got the same error messages from ODIN (versions 3.07, 3.09, and 3.10):
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Q1: Do I first need to unroot my SM-T530NU, that I previously had rooted with CF-Auto-Root-matissewifi-matissewifizs-smt530.tar.md5?
Q2: Do I first need to find a way re-set KNOX to 0?
Q3: Anything else?
schafer49 said:
Each time I attempted to flash the stock Lollipop 5.0.2 (T530XXU1BOD8_T530OXA1BOD8_HOME.tar.md5) I got the same error messages from ODIN (versions 3.07, 3.09, and 3.10):
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Q1: Do I first need to unroot my SM-T530NU, that I previously had rooted with CF-Auto-Root-matissewifi-matissewifizs-smt530.tar.md5?
Q2: Do I first need to find a way re-set KNOX to 0?
Q3: Anything else?
Click to expand...
Click to collapse
You install stock firmware , which not for you . You T530NU . This firmware is for T530 .
I have a Samsung galaxy J5 (2016, SM-J510FN/DS) whose OS I carelessly deleted (while not having a backup nonetheless ) while fixing a boot loop issue. I managed to reinstall Android 6.0 (Marshmallow) from opengapps.org (Arm architecture, 6.0 Android, Full version). The install was successful (I used TWRP to reinstall from my SD card) but I am now stuck on the boot loop. The phone either stays stuck on the Samsung logo or boots into recovery. I have wiped the Davik cache and performed a factory reset with success but I am still getting stuck on this boot loop. I have reinstalled the OS a few times but it #1 fails on zip verification and #2 repeats the boot loop after zip verification is turned off. I have a feeling that this is probably the root of my problem, however, my tool box of solutions is spent. I respectfully ask for assistance from more knowledgeable individuals and offer my thanks in advance.
mrnice10033 said:
I have a Samsung galaxy J5 (2016, SM-J510FN/DS) whose OS I carelessly deleted (while not having a backup nonetheless ) while fixing a boot loop issue. I managed to reinstall Android 6.0 (Marshmallow) from opengapps.org (Arm architecture, 6.0 Android, Full version). The install was successful (I used TWRP to reinstall from my SD card) but I am now stuck on the boot loop. The phone either stays stuck on the Samsung logo or boots into recovery. I have wiped the Davik cache and performed a factory reset with success but I am still getting stuck on this boot loop. I have reinstalled the OS a few times but it #1 fails on zip verification and #2 repeats the boot loop after zip verification is turned off. I have a feeling that this is probably the root of my problem, however, my tool box of solutions is spent. I respectfully ask for assistance from more knowledgeable individuals and offer my thanks in advance.
Click to expand...
Click to collapse
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.
#Henkate said:
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.
Click to expand...
Click to collapse
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.
#Henkate said:
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.
Click to expand...
Click to collapse
unfortunatly, I've tried this multiple times and still cannot get it out of the boot loop. I'm not booting back into recovery but rather to the Samsung logo now.
Wizardlysense said:
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.
Click to expand...
Click to collapse
I've done this as well with no success.
And if you are not waiting for the necessary time you need to load the system? .. since after installing the stock you have to leave this in the samsung logo about 10 to 20 minutes at least
One thing to note is that you should be flashing AP, BL, CP, and CSC, and not the HOME package only (not sure if your variant has it in the first place!). Also, ensure that the "NAND Erase All" option is ticked before performing the flash.
thank you, I have not tried ticking nand flash before but I will try it.
Wizardlysense said:
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.
Click to expand...
Click to collapse
This is what I'm seeing on Odin
<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> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
I have switched from Odin 3.12 to 3.04 and tried different stock files but no success yet.
mrnice10033 said:
This is what I'm seeing on Odin
<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> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
I have switched from Odin 3.12 to 3.04 and tried different stock files but no success yet.
Click to expand...
Click to collapse
Are you sure you have got the correct files for your device? Usually, when it errors out at aboot.mbn it is because the files are for another device/variant. What's your device model? I will try downloading for you the stock files and see whether it is successful.
P.S. Just saw that you noted your device model in the OP. Sorry about that! Give me a moment and I will get the files for you!
https://drive.google.com/drive/folders/0B8346PsUO8X8cUE1QkZMOGI2SmM?usp=sharing
Try this!
Rizzed said:
Are you sure you have got the correct files for your device? Usually, when it errors out at aboot.mbn it is because the files are for another device/variant. What's your device model? I will try downloading for you the stock files and see whether it is successful.
P.S. Just saw that you noted your device model in the OP. Sorry about that! Give me a moment and I will get the files for you!
Click to expand...
Click to collapse
Thank you so much. I appreciate it.
Hello everyone ,first of im experienced noob in rooting , flashing etc. Done it couple times , know how it work, but mistakes were made...
at this point i feel like im dying so i'll try to be short becouse im sitting around 5 hours at desk and trying to make this brick to work,
So since like 5 months ago i flashed custom rom , flash working twrp , everything worked like a charm ,
today found out there is rom called "GoogleWIZ" , put it on sdcard , went twrp , format , advance wipe , everything but sd and internal , flash bootloader (Tried both later), flash rom , phone keeps restarting ,
repeat with different bootloader , same problem , updated twrp , same problem , tried different rom, same problem , tried stock firmware , wont boot stuck at loading , tried another different custom rom , same problem. 4 hours of god knows what i were doing , tried "GOOGLEWIZ" , got some status 7 error.
One thing i notice that while i was flashing roms , it said "mount failed to mound no such file or directory andorid" , something like that , just before it "Succed" in flashing ,
Smart Switch wont recognize phone so thats not option.
Its possible that i didnt enable OEM Unlock , it says in downloading mode , FAP LOCK : OFF , OEM LOCK: OFF
Still dont know how to revert. :/
Now i just want to have stock android firmware back , any rom would be good too , just to unbrick it
Going to sleep now dead tired , i have faith in any of you guys , realy need phone for work and i cant afford it to be stupid brick.
DefaultNoob said:
Hello everyone ,first of im experienced noob in rooting , flashing etc. Done it couple times , know how it work, but mistakes were made...
at this point i feel like im dying so i'll try to be short becouse im sitting around 5 hours at desk and trying to make this brick to work,
So since like 5 months ago i flashed custom rom , flash working twrp , everything worked like a charm ,
today found out there is rom called "GoogleWIZ" , put it on sdcard , went twrp , format , advance wipe , everything but sd and internal , flash bootloader (Tried both later), flash rom , phone keeps restarting ,
repeat with different bootloader , same problem , updated twrp , same problem , tried different rom, same problem , tried stock firmware , wont boot stuck at loading , tried another different custom rom , same problem. 4 hours of god knows what i were doing , tried "GOOGLEWIZ" , got some status 7 error.
One thing i notice that while i was flashing roms , it said "mount failed to mound no such file or directory andorid" , something like that , just before it "Succed" in flashing ,
Smart Switch wont recognize phone so thats not option.
Its possible that i didnt enable OEM Unlock , it says in downloading mode , FAP LOCK : OFF , OEM LOCK: OFF
Still dont know how to revert. :/
Now i just want to have stock android firmware back , any rom would be good too , just to unbrick it
Going to sleep now dead tired , i have faith in any of you guys , realy need phone for work and i cant afford it to be stupid brick.
Click to expand...
Click to collapse
flash stock rom then go to stock recovery wipe all.
ZenI717 said:
flash stock rom then go to stock recovery wipe all.
Click to expand...
Click to collapse
" Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 5906 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
"
ON PHONE -sv rev. check fail(bootloader) device: 3, binary: 1
DefaultNoob said:
" Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 5906 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
"
ON PHONE -sv rev. check fail(bootloader) device: 3, binary: 1
Click to expand...
Click to collapse
Flashing older firmware than whats on device
Your phone says that you want to flash an older firmware that the bootloader doesn‘t allow... so try to flash the latest firmware for your device and try again... reply back if it doesn‘t help.
I flashed newer firwmare , it passed , thanks god ,
but then phone booted , "checking system update" -----> ERROR
, i went to recovery , wipe all , now its same old boot loop but it try to load samsung logo then it shutsdown and boot again...
edit: formated data , going one more odin flash , will say results
edit: Results are that we got one more boot loop
DefaultNoob said:
I flashed newer firwmare , it passed , thanks god ,
but then phone booted , "checking system update" -----> ERROR
, i went to recovery , wipe all , now its same old boot loop but it try to load samsung logo then it shutsdown and boot again...
edit: formated data , going one more odin flash , will say results
edit: Results are that we got one more boot loop
Click to expand...
Click to collapse
try to use smart(forgot the name) to reflash...if it doesn't work try install twrp then flash stock firmware using twrp,flash magisk also...it it also do not work then the phone become an expensive paper...maybe you can try send to samsung but yeah idk if they willing to fix knox 0x1.
ZenI717 said:
try to use smart(forgot the name) to reflash...if it doesn't work try install twrp then flash stock firmware using twrp,flash magisk also...it it also do not work then the phone become an expensive paper...maybe you can try send to samsung but yeah idk if they willing to fix knox 0x1.
Click to expand...
Click to collapse
I think the problem you had while flashing the custom ROMs was the Data partition was in some format other than EXT2 and EXT4, what TWRP uses to recognize and write to the partition. A quick reformat under advanced wipe should've fixed the issue. Flashing the bootloader brings an other issue, since it won't allow for the flashing of anything under a set parameter.
I would suggest to try flashing the newest firmware for your device variant, without the BL tab. If that doesn't work, download the newest FW for your device, but instead of your region get BTU (I'm just assuming that isn't what you have). Again, load up AP, CP, CSC, but not BL.
If your ok with getting from SamMobile, here's a link to the BTU I suggest you to try. If not, look for the latest stock firmware for SM-G950F United Kingdom BTU.
I had a similar issue with my s7 edge not too long ago (last week), and this is how I resolved it. Please let me know if that did the trick!
Hi guys, I tried to factory reset my phone by flashing the latest firmware. These are the files that I used:
AP_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G935TUVSBCTA2_CP14916856_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar
CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
I am a noob and I accidentally flashed the HOME_CSC file in the USERDATA section but every other file was in its place. Then after the successful flash, the phone restarted and entered a boot loop with the galaxy s7 and t-mobile logo. Also, I could't boot into recovery. It shows " recovery booting..." and stays there. After that, I tried to flash several different firmware versions but I always get errors like "fw ver check failed" and stops flashing. I only managed to reflash the first firmware again with success but the phone still doesn't boot. Does anyone know what is causing the problem? Am I using wrong firmware? can anyone help on this?
regards
bassist82 said:
Hi guys, I tried to factory reset my phone by flashing the latest firmware. These are the files that I used:
AP_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G935TUVSBCTA2_CP14916856_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar
CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
I am a noob and I accidentally flashed the HOME_CSC file in the USERDATA section but every other file was in its place. Then after the successful flash, the phone restarted and entered a boot loop with the galaxy s7 and t-mobile logo. Also, I could't boot into recovery. It shows " recovery booting..." and stays there. After that, I tried to flash several different firmware versions but I always get errors like "fw ver check failed" and stops flashing. I only managed to reflash the first firmware again with success but the phone still doesn't boot. Does anyone know what is causing the problem? Am I using wrong firmware? can anyone help on this?
regards
Click to expand...
Click to collapse
What country are you in?
cooltt said:
What country are you in?
Click to expand...
Click to collapse
USA
bassist82 said:
USA
Click to expand...
Click to collapse
Oops! Very temperamental phone, the bootloader is locked.
You can only flash the same firmware that was on the device before you started but if not the latest G935T firmware should work.
p. s. Factory reset is an option in the settings menu, there's no need to flash new firmware.
cooltt said:
Oops! Very temperamental phone, the bootloader is locked.
You can only flash the same firmware that was on the device before you started but if not the latest G935T firmware should work.
p. s. Factory reset is an option in the settings menu, there's no need to flash new firmware.
Click to expand...
Click to collapse
I don't know what firmware the phone had installed before. What are my options now? I can't get into recovery menu, only download menu works. Tried already a bunch of different android 8.0 ROMs for g935t but Odin fails to install them. It only works with just one but it goes into boot loop.
bassist82 said:
I don't know what firmware the phone had installed before. What are my options now? I can't get into recovery menu, only download menu works. Tried already a bunch of different android 8.0 ROMs for g935t but Odin fails to install them. It only works with just one but it goes into boot loop.
Click to expand...
Click to collapse
If the phone is a T Mobile device you just need to install a T Mobile firmware from sammobile.
This is the latest for your device (and I'm assuming it is a G935 edge?)....
https://www.sammobile.com/samsung/g...e/SM-G935T/TMB/download/G935TUVSACSI1/297176/
Sammobile is a little slow for non premium members
cooltt said:
If the phone is a T Mobile device you just need to install a T Mobile firmware from sammobile.
This is the latest for your device (and I'm assuming it is a G935 edge?)....
https://www.sammobile.com/samsung/g...e/SM-G935T/TMB/download/G935TUVSACSI1/297176/
Sammobile is a little slow for non premium members
Click to expand...
Click to collapse
I already tried to flash this rom, I downloaded it from a faster source and fails to flash it.
<ID:0/007> Odin engine v(ID:3.1303)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 4575 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> emmc_appsboot.mbn
<ID:0/007> lksecapp.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
bassist82 said:
I already tried to flash this rom, I downloaded from a faster source and fails to flash it.
<ID:0/007> Odin engine v(ID:3.1303)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 4575 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> emmc_appsboot.mbn
<ID:0/007> lksecapp.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
Click to expand...
Click to collapse
Fail (auth) means your phone is not in download mode or the firmware file is not in the correct box in Odin.
I think you may be better reading a step by step guide on how to flash firmware.
If you manage to flash and get stuck in a bootloop do the following.
1. No matter what the phone is doing just press volume down+home+power (in that sequence)
2. When the screen goes black quickly move your finger to volume up while still pressing home + power. This will boot you into recovery menu.
3. Choose "wipe cache partition" then "reboot system now"
4. Allow phone to go through the first boot up, it could take 10 minutes just leave it until you get the welcome screen.
cooltt said:
Fail (auth) means your phone is not in download mode or the firmware file is not in the correct box in Odin.
I think you may be better reading a step by step guide on how to flash firmware.
If you manage to flash and get stuck in a bootloop do the following.
1. No matter what the phone is doing just press volume down+home+power (in that sequence)
2. When the screen goes black quickly move your finger to volume up while still pressing home + power. This will boot you into recovery menu.
3. Choose "wipe cache partition" then "reboot system now"
4. Allow phone to go through the first boot up, it could take 10 minutes just leave it until you get the welcome screen.
Click to expand...
Click to collapse
When I press volume down+home+power it gets me to a screen says "warning: a custom o/s can cause critical problems bla bla bla..." and underneath it shows these options: 1) Volume up: continue 2) Volume Down: Cancel (restart phone) 3) Home Button: Show Barcode. If I proceed with the 1st option it goes to download mode where I flash with odin. I tried also the combination volume up+home+power with the phone witched off and it shows the message "recovery booting..." on screen with blue text but then it shows the android icon and says" installing system update, then restarts and falls into boot loop again with the samsung logo.
bassist82 said:
When I press volume down+home+power it gets me to a screen says "warning: a custom o/s can cause critical problems bla bla bla..." and underneath it shows these options: 1) Volume up: continue 2) Volume Down: Cancel (restart phone) 3) Home Button: Show Barcode. If I proceed with the 1st option it goes to download mode where I flash with odin. I tried also the combination volume up+home+power with the phone witched off and it shows the message "recovery booting..." on screen with blue text but then it shows the android icon and says" installing system update, then restarts and falls into boot loop again with the samsung logo.
Click to expand...
Click to collapse
Yes that's fine, just keep trying to get it into recovery, it can take a few attempts for recovery to boot successfully.
The locked bootloader models are a nightmare unfortunately but there's lots of info on the forum about all the different issues and how to resolve.
Sometimes the only solution is to try flash the firmware which was there before you did anything to it eventhough there is a newer version.
cooltt said:
Yes that's fine, just keep trying to get it into recovery, it can take a few attempts for recovery to boot successfully.
The locked bootloader models are a nightmare unfortunately but there's lots of info on the forum about all the different issues and how to resolve.
Sometimes the only solution is to try flash the firmware which was there before you did anything to it eventhough there is a newer version.
Click to expand...
Click to collapse
I tried a lot of times already but it finally gets to a point that says "no command" with the android icon on top and if I press some times the volume up/down or home it finally gives some error messages and stuck there. It seems to me that the recovery menu is missing completely for some reason and the second problem is I don't remember which firmware version it had exactly before my attempt to flash another.
Anyone? Do I need a pit file to fix this problem?