I need some help....I was on the last version of Knox Raid and decided to flash to Dynamic Kat. I installed the latest version of SafeStrap and tried to get into recover mode after re-boot...no splash screen...then I remember there was a folder called "togetsafestrap" where I went into Odin and installed the BL and AP files there...it installed successfully and now I get a boot loop. I am still able to get into download mode but tried flashing to stock version MI9 using Odin...but it failed. Help?
Ok...I got everything fixed.
Went here and followed the steps.
http://forum.xda-developers.com/showpost.php?p=51572044&postcount=2&nocache=1&z=1683958484791219
Related
so i have been running Paranoid android for a while, and wanted to try this out:
http://forum.xda-developers.com/showthread.php?t=2051904
flashed the latest cm10.1 kernel, and then formated cache, dalvic, battery stats, etc.
then i managed to reboot before i had flashed the new rom and got stuck in bootloop. could not access CWM any more
after this i downloaded odin after a few forum reads, and flashed different versions of CWM to see if i could get back in to flash the rom.
the latest one i have in it is this:
http://fs1.d-h.st/download/00033/pQK/GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar
as it was recommended in some un-brick thread. still no access to CWM
after this i flashed a stock rom, as i could not find any .md5 or .tar roms to use with odin, and i got at least a samsung logo on hte screen, before i got back to boot screen and was stuck there again.
CWM still not working, or showing up in any way.
out of obvious options i now tried flashing the pit file trough odin from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
and after this the samsung boot logo did not show up anymore. only boot loop
i am now going to try and download the older ginger bread rom and flash it trough odin, but i got no idea if it will make any difference.
otherwise phone goes to download mode just fine, and i got working drivers in windows trough kies.
im quite new to this, and dont really know what would work from here. ill end up hard bricking the phone if i don't get some help, and the trash can will be my n7000 next home.
any advice is welcome
--------------------------------------------------------------------
EDIT:
flashing official rom again after the pit file acrually gave me a working phone again. also i now got 50 gb of drop box storrage for free, so thats nice
Hi everyone.
I followed the instructions regarding the use of Safestrap to upgrade to 5.0 and keep root. Detailed here http://forum.xda-developers.com/att...w-to-update-to-g900aoca-5-0-keeproot-t3076803 However, I did not flash this file " G900A_OC4_Stock_Partitions_wOA1_BL" I had downloaded a previous file called " G900A_OC4_Stock_Partitions" which I assume did not have the OA1 BL in it.
After I completed those steps, the phone was stuck at the Samsung Galaxy S5 splash screen. I then flashed the stock NCE ROM to start over but now the phone is stuck in a boot loop. I tried wiping the system through the stock recovery but no good. I can still access Download Mode and Recovery. I didn't get any errors when flashing the files via Odin. Any ideas? Thanks.
Here's what I have tried:
Flashed NG3 kernel
Flashed OA1 kernel
Flashed OC4 kernel
Applied NCE to NG3 update via ext-sdcard
Nothing is working...
Hello, I wanted to install the new android update from AT&T however I couldn't since my phone was rooted. I attempted to unroot by flashing a stock ROM via Odin 3.10 the flash was successful but now it won't boot past the samsung logo. The screen goes black and the blue LED stays lit at the top.
I am able to get into download mode and recovery mode. I've tried wiping cache and factory reset. I've tried re-flashing and it still gets stuck. I'm wondering if there's any way I can just flash a custom android 5.0 rom since it doesn't seem to want to go back to stock. I've read a few guides but they all require safestrap and I can't put that on my phone.
I flash the AP, CSC, and CP with no BL and it still won't work.
Flashed the downgrade to NCE, worked perfectly.
"Recovery is NOT SEANDROID ENFORCING" after CF-Odin rooting N910T3 run on M6.01
Just got a US Cellular Galaxy Note 4 phone. Did a factory reset and it run perfectly on T Mobile N910T3 Marshmallow 6.01 (stock). Must have been rooted before, but flashed back to stock firmware and unrooted. So I want to get it rooted again.
Without realizing the difference of rooting androids running on Marshmallow and previous versions, I downloaded the latest specific CF-Odin tool for N910T3, run it to root it. Quickly, Odin showed the green "Pass!" But the phone got stuck immediately after that when it proceeded to reboot with this error:
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
And the Galaxy Note 4 logo.
I removed the battery, waited for many minutes or a day. Power it on or boot to Recovery Mode always get to the above same error, so I cannot wipe data or do factory reset, as some suggested.
From above error screen, hold Volume down+Power+Home, I can easily get to the Download Mode. So I downloaded N910T3UVS2EPE2 (not the latest N910T3UVS2EPG2, as it's too slow from Samsung), but failed to flash it with Odin (3.11.1 or 3.10.6) with or without PC's Antivirus Off. And on the phone I got:
SW REV CHEKC FAIL : [aboot]Fused 2 . Binary 1
[1]eMMC write fail: ABOOT
Wonder if I can flash TWRP with Odin in such a state? Besides, I forgot and didn't install USB drivers for Galaxy Note 4. Could this be the problem? I have USB drivers for Note 2, and it seems the PC communicate normally with this Note 4.
Appreciate very much for any help!
Having the same issue. Can't even get the phone to flash the pit file or the stock software it fails every time.
Think the phone is Toast.
***Update***
Had to do some weird stuff to get it booted and running stock un rooted again. I ODIN flashed TWRP booted into recovery and formatted DATA, then I ODIN flashed the GP2 PIT file along with the newest version of the CF Auto Root at the same time (For some reason this is the only way the PIT flash would not fail, Then I ODIN flashed the [email protected] stock firmware, and it finally booted again. After not being able to boot for 2 weeks. Device is running the setup now.
Update:
I was too scare to take any actions on the phone for almost a week! However, yesterday I only flashed TWRP with Odin and it automatically rebooted back to normal!! Everything seems to be working perfectly again! The only exception when I boot it to recovery mode to TWRP, I still see a flash of the following error message before TWRP:
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Some how TWRP can pass the bootloop.
With TWRP I was able to root the phone, thanks to Rootmygalaxy.net, and did some backups.
Wonder if I can get rid of that error message by wiping Cache/data...?
You will get an error on that screen; kernel error or not seandroid enforcing error because it is not Samsung stock being used. There's no getting g around the warning that I'm aware of and it doesn't cause a difference on the phone running stock modified or just going all out and running any other rom.
ODIN MODE
PRODUCT NAME: SM-G925A
CURRENT BINARY: SAMSUNG OFFICAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
SECURE DOWNLOAD: ENABLED
KNOX WARRANTY VOID: 0 (0X0000)
AP SWREV: B: 4 K: 3 S: 3
Good evening,
First time poster long time reader/browser. Before posting this message I have read all other posts/threads in an attempt to fix this issue. Long story short I busted my old Samsung Galaxy S6 Edge SM-G925A AT&T and bought this one used online. The seller never mentioned it was bricked as all pictures posted of it showed it operating and at least booting up. When I received phone I turned it on and it is stuck in a boot loop. I have tried to boot in recovery mode by pressing VOL UP+HOME+POWER button and it does nothing. I am only able to boot into download mode. I have attempted to flash multiple stock firmwares which 3 have been successful and passed in ODIN, however once they pass and the phone reboots it is still stuck in a boot loop. I have been successful in flashing the below firmwares. I do not know anything about the phone besides the IMEI number, S/N, SKU and manufactured date. I do not know what firmware was on the phone originally and do not know what was flashed on phone when I received it (I'm assuming phone was flashed or rooted before due to the above stating SYSTEM STATUS: CUSTOM) Am I stuck with a bricked phone? I've attempted flashes with PIT Files, w/o PIT FILES, with just the AP file, with all 4 BL, AP, CP and CSC files and each time it gets in a bootloop. Can someone please assist me? I've read that sometimes all is needed is to wipe the cache in recovery mode and that would clear bootloop, but I cannot get into recovery mode. Any suggestions. Again, below are what I've flashed successfully but continues to bootloop. Thank you all in advance.
G925AUCS5DPJ1--SUCCESSFUL ODIN FLASH-STILL BOOTLOOP
G925AUCU3BO12--SUCCESSFUL ODIN FLASH-STILL BOOTLOOP
G925AATT3BOJ7--SUCCESSFUL ODIN FLASH-STILL BOOTLOOP
I will say after flashing the DPJ1 files I can no longer flash the BL file for either of the 2 firmwares below it (the AP, CP and CSC files all still flash successful).
I'm just about to give up and shell out the money and buy new phone. Was just hoping someone on here could provide me some advice, some sort of miracle file or a way I can odin flash a tar/md5 file that will wipe my cache/system cache like it would as if you did it in recovery mode.
OH! Also Samsung Smart-Switch will not recognize the phone. I'm able to input the model name and S/N in the emergency software initialization but as soon as I input the S/N and click ok it immediately crashes and closes out Smart-Switch. Thanks Guys!
Paul
You need to find a Marshmallow odin file. The phone has most like;y already been updated to Marshmallow in the past. Once on MM, you cant go back to Lollipop which is what those 3 files you listed are.
Edit, NM....that PJ1 file is marshmallow. Try taking it to Best Buy and having them reflash it with the latest MM file.
Thank you, I will try that. I have tried taking to AT&T but they wouldn't help at all. They said since I'm not AT&T customer then I'd have to go thru Samsung. I'm aggravated. I've been working on this off and on for 3 months now. Thanks again for the reply. I've read a lot of people saying after wiping cache partition and rebooting it fixed bootloop after successful flash.
You said I could go back to Lollipop. If I use anything other than the 3 files I listed Odin will fail with various,
Secure Check fail message. Do you know if anyone has created a Odin file that will successfully wipe the cache partition like it would via system recovery?
Thanks again for the reply.
Any updates on this ? I'm having the same issue with my G925I.
why don't you try to flash the DPK5 update from ODIN in the nougat update thread. that's the latest ODIN file I think
saketkutta said:
why don't you try to flash the DPK5 update from ODIN in the nougat update thread. that's the latest ODIN file I think
Click to expand...
Click to collapse
No matter what I flash , it's always stuck on the s6 edge logo.. And I can't enter any recovery be it stock or custom recovery. All I can do is enter download mode and flash official ROMs but none seem to work.
Thats some unfortunate situation. I don't know what to do. If official roms don't boot then it's permanent brick I think. Any senior devs know what to do?
Sent from my SAMSUNG-SM-T337A using Tapatalk
I am suffering from the similar fate,, its a friend mobile whose stuck on Samsung logo, he tried to fix it with Kies and Smart Switch and it did not workout for him.
The phone does not boot into recovery. I tried flashing G925AUCU1AOCE and G925AUCU3BOJ7 stock firmwares but no luck.
I successfully flashed G925AUCU6EQCF but it is still stuck on Samsung Logo
Any help or suggestion would be welcome
edit 3rd: Ok now I have managed to flash G925AUCS5DPJ1, still it won't boot into recovery and it is looping to Samsung logo
Same for me ... The recovery is not accessible and the phone reboots in a loop, Smart Switch tell me that the S / N does not match the phone model ...