I've had a Note 4 for quite a while now. I've run various ROM's on it and have not really had issues. Until recently. I upgraded from TEKXodus UR5 to UR7.0. Since then the phone has been unstable. I went back and the only thing I can think of is I'm running COG2 baseband, which is not what TekHD recommends. So off to flash a new baseband - but the damn phone wont do it. Download mode has "Secure Download = Enabled" and nothing will flash from Odin. I can still get into TWRP and flash ROM's no problem. Since discovering the issue it looked like I needed to check an option for OEM Unlock. But when I do, it does not stay checked. Google says this is a feature to stop people without access to the phone from using ADB or odin to break in. But its doing an excellent job of keeping me out too. Any ideas on how I can get my bootloader unlocked?
If you have TWRP installed... you definitely don't have a locked bootloader. My phone has the "Secure Download: Enable" on the Odin screen also, and I haven't had a problem with flashing any stock Odin files. My guess is that you're using the wrong files for the wring operating system, corrupted files or outdated Odin.
Sent from my SM-N910T using Tapatalk
Related
Hey folks. I basically just want Gingerbread on my phone, but I'm having issues doing it through Kies as it won't recognize the current firmware when I connect.
I'm not able to flash to JF6 in Odin OneClick without getting an ATT boot screen and nothing more.
Apparently I need to have JF6 in order to get Kies to recognize the phone. I'd like to get this done today (Been two weeks without full function), and I'm thinking I just want to flash to a good rom that runs 2.3.
Is there anything I can do to flash to something other than I896UXJL1-stock or I896UXJI2 TORONTO? These flash well, but are not what I was looking for. Again, I'm going to need something that doesn't require JF6, or another method to get JF6 on without getting stuck at the ATT screen.
Any flash with Odin does not require you to be on a prerequisite firmware, it will flash over whatever you're running.
Go to the Dev section, find a gingerbread firmware with bootloaders included, put phone in download mode and flash.
Full List of Necessary Files for Successful Flash
Okay, I've been browsing around, trying to find something suitable, but now it would seem that I'm not able to flash anything except for the OneClick method which gives me that ATT screen.
I read somewhere that later editions of the Captivate may not work out well with certain Odin flashes. I think my phone is 1038?
I'm hoping that someone might be good enough to show me how to get this thing to flash to what Samsung sent to Rogers from the factory, or at least to a point that I can successfully flash to 2.3. Right now I'm stuck.
Thanks in advance for any help.
Okay, I'm back to UXJL1, using Odin 1.81, and I also found a OneClick that reportedly switches out the bootloaders for GB bootloaders. I tried it, and it did give me an ATT screen, followed by a normal boot and I was back to having apps like Titanium crashing on boot, which is beyond annoying to figure out.
My biggest issue is that I think I have a decent grasp of what's involved in this process, but I don't know which file is compliant with which. I seem to always use 512 for the partition, but I see some variations in that. I also don't know what to do about the bootloader situation except the one tool I mentioned above.
Basically I could either use what I have, go back to Firefly, or keep trying this GB upgrade. I'd rather keep trying but I also need a phone.
I have a ton of different firmware files at my disposal and can download whatever else I need if mentioned, I also have a few different versions of Odin, and OneClick. I downloaded Odin OneClick 2.xx for rooting purposes and it seemed to work with a flash I did today.
Again, thanks for any help.
As for bootloaders. If the 1 click doesn't work, or you don't know if your phone likes 1 clicks I've attached a pda.tar and a odin in a rar that contains just GB bootloaders. This isn't my work I downloaded from somewhere in xda, I just can't remember where so I can't link. All credit to whoever created it. I can't speak specifics for I896 but random FC's usually means a bad flash. Try downloading again or another odin rom. Sorry I can't be any more help.
I'm not quite sure if people still visit these threads, but I'll give it a shot. My friend gave me his old captivate i897 because he got a new phone. He is on AT&T, while I am on T-mobile. So I looked up how to unlock this phone, and it said that I needed to root. I looked up how to do this in the seemingly thousands of different ways. It was running gingerbread, and the only working program I could find to do this was gingerbreak. I ran it, and it seemed like it was going to work. I then ran the unlocking software, and it would not let me do so because of a supposed bad root. Following this, I researched some more, and found that other unlocks work on froyo. I then tried to revert the phone to froyo using odin. This worked, except the phone then believed that it was a i9000 instead of a 897. I realize that I must have used the wrong program. The phone itself worked fine, but it registered as a 9000. For some reason, I then continued my quest to unlock/ re root. I ended up trying to use heimdall one-click. It could not find my device. I then turned to a stock flash thing. I tried cognition 5, which involved frugu or something. Anyway, the phone has the noise/lines running across when i turn it on. It will enter download mode. Have I bricked it? If not, is there anything that I can do?
Not bricked. Is the first screen the white at&t world phone one or the black one that says gt-i9000? If the latter, hold volume down only and plug in USB to get download mode.
Also, the garbled screen is from trying to use a gingerbread kernel with old bootloaders.
Sent from my SGH-I777 using xda premium
Get into download mode and use one of these GB 2.3.5 i897ucKK4 one clicks with bootloaders...here...http://forum.xda-developers.com/showthread.php?p=18370912.
Then use the regular Odin to flash the KK4 Corn Kernel v7.0A to get a compatible kernel with CWM Recovery included. And as a bonus, within that recovery u can get Root...here is the kernel thread...http://forum.xda-developers.com/showthread.php?p=18233847
Afterwards proceed how u wish as far as flashing other Roms.
(Another Root method here...[Utility] KK4 Easy Root)
Sent from my SGH-I897 using xda premium
Was trying to unroot my phone and restore to factory... decided to go with the Odin 1-click 4.2.2 found here:
http://forum.xda-developers.com/showthread.php?t=2629093
I'm using a mac and running the Odin 1-click (top subsection of OP in above link) through VMWare on Windows 7. It runs through the entire thing and says it pushed all the files and stuff and completed, but every time says succed 0 failed 1. I've downloaded the file several times from different locations, and run it about 15 times now.
Phone info-
IMIE: 356554053791865
SN: R31D81E817A
MODEL: SGH-I537
SKU: 6145A
16GB
FCC ID: A3LSGH1537
I also tried to use regular Odin software (pretty much every version of it) through VMWare to push the 4.3 files (found on the second to last subsection of OP on above link) individually - those never even get past Check MD5, just locks up there.
I also attempted to push the same individual files through JOdin3 on my MAC, but I don't have a PIT and JOdin3 is unable to pull it from my phone (probably because it's stuck in a soft brick state - can boot to download, but when powering on normally or booting to recovery I get the warning about failed firmware upgrade and to try to fix in Kies - which I can't.
Before I had 4.2.2 with MF3, rooted with the activeroot one click root from the website which you browse to on your phone.
I think you tried flashing ml2 4.4.2. If thats the case you have the locked 4.4.2 bootloader and you can not go back to 4.2.2, or atleast I could not.. you have to flash everything except BL in odin to 4.3 and go from there.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
I took it to Best Buy at the Samsung station and they flashed it back with the stock ROM - then upgraded it to 4.4.2 KitKat cause they were feeling froggy. Free of charge plus the chick was super flirty.
I was wondering if anyone had flashed back to that factory dump someone had put up I saw it floating around here somewhere...
I have flashed stock multiple times, but I didn't use Odin since the same stock firmware is available through Kies and it flashes it pretty much the same way and flawlessly.
I used Odin for other files but since the bootloaders are locked and encrypted I received an error message in red font in the download mode screen, and then Odin was disconnected. Knox counter did not advance in my case, but I did consider the possibility before flashing.
Kies, on the other hand, asks for the phone model and the serial number and then it lets you flash it. I'm assuming it might be generating md5 encryptions based on the phone model and serial number and then phone checks to match those before flashing. (Not sure!)
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Hey guys,
I've done my custom rom well and it all was working fine, and I restared right after it started and then my phone has stopped at Samsung Galaxy Note 8, and in Red Text up it says:
Only Official Released Binaries are allowed to be flashed.
Is there any solution with my situation?
Your help would be appreciated guys
Ziezo said:
Hey guys,
I've done my custom rom well and it all was working fine, and I restared right after it started and then my phone has stopped at Samsung Galaxy Note 8, and in Red Text up it says:
Only Official Released Binaries are allowed to be flashed.
Is there any solution with my situation?
Your help would be appreciated guys
Click to expand...
Click to collapse
The only way to fix that is by flashing stock filmware with Odin. Just make sure to download the same filmware or newer than what is on the phone as you can't flash older filmware and you would just get an error. You can use "Frija" for PC to download the filmware at a decent speed, just Google "Frija XDA"
Did you flash a rom and this happened? Or did you just flash TWRP and reboot?
The ' Only Official Released Binaries are allowed to be flashed ' error is due to bootloader not being fully unlocked.
As @stonedpsycho has said flash firmware to fix.
Is it related to RMM ? https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
stonedpsycho said:
The only way to fix that is by flashing stock filmware with Odin. Just make sure to download the same filmware or newer than what is on the phone as you can't flash older filmware and you would just get an error. You can use "Frija" for PC to download the filmware at a decent speed, just Google "Frija XDA"
Did you flash a rom and this happened? Or did you just flash TWRP and reboot?
Click to expand...
Click to collapse
I'll try the "Frija XDA" and see what I can get, because I got tired of keep downloading STOCK ROM at low speed and then stopped!!
and I got this message after flashing the ROM, I flashed it the first time and it was very good, but I wanted to remove some unwanted apps, then I flashed it again, OK! This time it works fine too and when it started and before making any setups (Google account, WIFI, etc) I restarted my phone to flash some additional Add-On's but I got this message and I'm stock here untill now.
Ziezo said:
I'll try the "Frija XDA" and see what I can get, because I got tired of keep downloading STOCK ROM at low speed and then stopped!!
and I got this message after flashing the ROM, I flashed it the first time and it was very good, but I wanted to remove some unwanted apps, then I flashed it again, OK! This time it works fine too and when it started and before making any setups (Google account, WIFI, etc) I restarted my phone to flash some additional Add-On's but I got this message and I'm stock here untill now.
Click to expand...
Click to collapse
Very strange that this happened after flashing a rom as the RMM state should be patched (This should only be an issue when wanting to root stock filmware and not flash a rom). Post the link to the Lightrom you are using and I will have a look on the thread as maybe you missed something or there may be others who encountered the same problem with someone offering a solution.
stonedpsycho said:
Very strange that this happened after flashing a rom as the RMM state should be patched (This should only be an issue when wanting to root stock filmware and not flash a rom). Post the link to the Lightrom you are using and I will have a look on the thread as maybe you missed something or there may be others who encountered the same problem with someone offering a solution.
Click to expand...
Click to collapse
This is the LightRom I used, always I'm following the instructions and my work always goes the right, except this time, I may did something wrong.
And by the way, I have formatted Data before doing the 1st flash and the 2nd flash.
stonedpsycho said:
The only way to fix that is by flashing stock filmware with Odin. Just make sure to download the same filmware or newer than what is on the phone as you can't flash older filmware and you would just get an error. You can use "Frija" for PC to download the filmware at a decent speed, just Google "Frija XDA"
Did you flash a rom and this happened? Or did you just flash TWRP and reboot?
Click to expand...
Click to collapse
Flashed the Stock rom and it worked, thank you guys @LR7875 @spawnlives @stonedpsycho
The RMM and/or KG state has been around since oero. Flashing stock firmware will reactive this state. To modify your phone this state has to change.
So you will need
Oem unlocked in developers menu
In download mode
RMM - normal or dissapeared
KG - checking
Then you start to flash non samsung signed firmware. ie: twrp,root,custom roms etc.
Read the post quoted above for rmm state bypass
KG state there is no zip to bypass so it has to be in checking mode and will generally stay that way until flashing stock firmware again.