Hello all,
So, I've been doing some reading in regards to some problems I ran into when installing KK on my device (even though it's currently running CM11 nightly without any noticeable issues ) and I noticed that my device has something that for my understanding should not have worked: I'm still on the I747MVLDLK4 bootloader and was able of getting the latest CM11 nightly running without issues on the device.
Granted that the device's modem is updated to the latest version, but for what I've read that it should have never boot up onto any KK ROM. I've been able of getting SlimKat, AOKP and CM11 running on it, even though CM11 was the only one that didn't give me any FC's or any unwanted behavior. I must admit that getting any of these ROM installed required quite a bit of messing around in TWRP and had to do complete wipes between installing versions, but still, it worked. I also had JB 4.3 installed ( AOKP ) since around October/2013 and upgraded to KK about 1 month ago.
I have a couple of questions in regards to this:
- If the KK ROM's are not supposed to boot up on such an old bootloader, what did I do that would've overrun this?
- Since I'm still on I747MVLDLK4 bootloader, would I be able of downgrading to 4.1.1? ( I want to perform the device unlock for free, which only is available on that version)
I've added screenshots of the bootloader info on the console emulator and the system info...
Thanks in advance!
The 4.3 requirement is only for touchwiz kk roms.
Related
I'm unsure of what exactly is causing the problem but My T-Mo Galaxy Note 3(SM-900t. Hltetmo) is unable to successfully flash any custom roms. It's running the official 4.4.2 kitkat as well as the bootloader installed from kies 3. Currenty I have a beta version of twrp installed that works with the 4.4 bootloader and I've tried a few different roms with varying issues. Is it just not possible to flash custom roms on this official bootloader currently?
The roms I've tried flashing to name two are Tweaked and W03's Slim. I've only done clean installs and even cleaned out all of the SD card / internal before attempting but the roms either won't boot, and the phone just heats up or loop endlessly. I made a nandroid backup of my stock rooted which I have no problem going back to after each unsuccessful attempt but I've yet to figure out why. If anyone has any tips or advice it's much appreciated.
peanutsrule said:
I'm unsure of what exactly is causing the problem but My T-Mo Galaxy Note 3(SM-900t. Hltetmo) is unable to successfully flash any custom roms. It's running the official 4.4.2 kitkat as well as the bootloader installed from kies 3. Currenty I have a beta version of twrp installed that works with the 4.4 bootloader and I've tried a few different roms with varying issues. Is it just not possible to flash custom roms on this official bootloader currently?
The roms I've tried flashing to name two are Tweaked and W03's Slim. I've only done clean installs and even cleaned out all of the SD card / internal before attempting but the roms either won't boot, and the phone just heats up or loop endlessly. I made a nandroid backup of my stock rooted which I have no problem going back to after each unsuccessful attempt but I've yet to figure out why. If anyone has any tips or advice it's much appreciated.
Click to expand...
Click to collapse
Tweaked is 4.3 the ROMs are not interchangable
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
That would definitely explain it for tweaked, but Will's seems to be a kitkat 4.4.2 rom. I'm unable to get that one to work either when many seem to have no issue. Due to my post count I'm not able to directly ask in each of their threads so there's it's anything I can do I'm willing. I'll research if it's possible to downgrade back to 4.3 but from what I read already it doesn't look like it.
- Edit
After some research it looks like Will's is modded in some way to have kitkat's version with the 4.3 loader. So that would explain why I'm unable to flash that as well.
peanutsrule said:
That would definitely explain it for tweaked, but Will's seems to be a kitkat 4.4.2 rom. I'm unable to get that one to work either when many seem to have no issue. Due to my post count I'm not able to directly ask in each of their threads so there's it's anything I can do I'm willing. I'll research if it's possible to downgrade back to 4.3 but from what I read already it doesn't look like it.
- Edit
After some research it looks like Will's is modded in some way to have kitkat's version with the 4.3 loader. So that would explain why I'm unable to flash that as well.
Click to expand...
Click to collapse
They need different sections here for this. One for 4.3 another for 4.4.2.
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
nsaveer composed
It would probably help sort out things a lot better, yeah. Shame.. I didn't think an update could possibly go this bad but lesson learned. If anything.. I've had zero problems with kitkat it actually does run better and smoother but the locked down issues are unacceptable with Knox.
peanutsrule said:
It would probably help sort out things a lot better, yeah. Shame.. I didn't think an update could possibly go this bad but lesson learned. If anything.. I've had zero problems with kitkat it actually does run better and smoother but the locked down issues are unacceptable with Knox.
Click to expand...
Click to collapse
What lock down issue.
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
From what I understand once updated to the official 4.4.2 kitkat the updated bootloader in 4.4 makes it so you can't downgrade. It's much more locked down compared to the official 4.3 JB. As such I'm stuck on 4.4. From my research there's only one model of the note 3 that can downgrade and it's the W8 model.
So, I'm trying to install a custom recovery to flash a new ROM on this stock, UCUFNJ1 phone, but I'm concerned I might approach it wrong. Could I get a hand, 'fellas?
I inherited the phone, and have had pretty good success with the I747 in the past, installing TWRP and CM 10.2 on a few phones in the past for friends and family (I usually default to that one since, in my experience, it's been most stable). I've heard that there's a high rate of bricking when trying to install a custom recovery on AT&T i747 devices running 4.3+ bootloaders, so I'm trying to play it safe, since I've never worked with one that had anything newer than 4.2.1 installed on it.
I can't seem to find anything definitive on rooting this phone for the UCUFNJ1, but a lot of people trying to update to that bootloader from NE4. Interestingly, this device was running UCUFNE4 (I decided to check because I had a feeling the folks weren't going to heed my warning, "NOT TO TOUCH IT BEFORE YOU GIVE IT TO ME.") But when I got it back, I discovered they must have reset it and some kind of OTA was applied when they were using it.
For the record, this device is unrooted, and is running stock TW, and has no custom recovery.
I'm going to document my approach with this, as well: from what I can see, the information on rooting/unlocking this particular model is pretty scarce, and a lot of the methods are very outdated. Since this is a newer bootloader, I have a sinking feeling it's uncharted territory.
Here's what I'm dealing with now:
Android Version: 4.4.2
Baseband version: I747UCUFNJ1
Kernel Version:
¶3.4.0-1514807
¶][email protected] #1
¶Wed Oct 1 21:09:24 KST 2014
Build Number: KOT49h.i747UCUFNJ1
SE for Android Status:
¶]Enforcing
¶SEPF_SAMSUNG-SGH-I747_4.4.2_0016
¶Wed Oct 01 21:09:13 2014
This is what the phone was running before they accepted the OTA:
Android Version: 4.4.2
Baseband version: I747UCUFNE4
Kernel Version:
¶3.4.0-1514807
¶[email protected] #1
¶Mon May 19 21:00:05 KST 2014
Build Number: KOT49H.i747UCUFNE4
SE for Android Status:
¶Enforcing
¶SEPF_SAMSUNG-SGH-I747_4.4.2_0016
¶Mon May 19 20:59:50 2014
I suggest flashing Philz Touch via Odin from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Make sure you download the tar.md5 file.
Copy a custom ROM to an SD card, boot into recovery, backup your existing ROM, wipe cache, Dalvik, data, system, and flash the custom ROM.
Is there any significant difference from using Philz versus TWRP or CWM? Can anybody report success with this configuration? I wouldn't want to brick this device, since if I do, it's back to my ancient Motorola Atrix 4G and I do not want that to happen, haha.
Additionally, will I have any trouble installing ROMs of earlier Android versions? For instance, I've had a good experience with CM 10.2 on all the GS3s I've installed it on, but since I'm running the UCUFNJ1 bootloader for 4.4.x devices, would I run the risk of bricking the phone by trying to install anything other than a Kitkat ROM? (If it just fails to install, I'm no stranger to that, I'm just trying to cover my bases here.)
Thanks.
I had issues with TWRP on my s3 and Note 3 so I switched to Philz.
Philz is actually based on CWM with a touch interface.
Older ROMs should work properly on updated bootloaders and modems. Newer ROMs may not be fully functional on older bootloaders and modems.
Feel free to wait for others to chime in. I understand your hesitation. I would not want a brick on my hands either
You do not need root to install a custom recovery and flash ROMs.
ok, chymeing in then. have had just opposite experience. lol. on mj2 had no problem flashing new roms. updated bootloader/modem to NE4 (KK), and get fail error older CM builds (cm10/10.2,etc.) but was taught by docholiday that on older roms you just edit the updater script to include the new bootloader version and bam! flashes just fine.
p.s. thanks for all your good advice/help audit13, would have drown many times without.:thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Alright, I'm going to give this a go on Thursday or Friday, thanks for the help--
--I'll be sure to post the procedure and results.
It's been a while since I flashed a rom. I thought I would play around with some ROM's today, but I'm getting overwhelmed by the contradictory information out there, regarding bootloaders,wifi patches, kernel flashes etc. Not that it's misinformation, but I just don't know if it's implied that the bootloader on the install instructions have been updated to 4.1.2 or higher before moving forward with flash.
I'm on a rooted T-mo/T889 Galaxy Note 2 with stock 4.1.1 and UVALL4. I flashed TWRP on it a few months ago, when I was looking into installing DN3 rom.
It seems to me that the instructions for installing DN4 (which is what I'm looking at today) might assume my device is updated to latest firmware.
So I'm wondering where to start. Do I need to update bootloader, or can I just move forward with electronteam's install instructions flash DN4 with addon patch? Or even more broader terms, can I flash a 4.4.4 + rom from a 4.1.1 firmware?
lyinelriche said:
It's been a while since I flashed a rom. I thought I would play around with some ROM's today, but I'm getting overwhelmed by the contradictory information out there, regarding bootloaders,wifi patches, kernel flashes etc. Not that it's misinformation, but I just don't know if it's implied that the bootloader on the install instructions have been updated to 4.1.2 or higher before moving forward with flash.
I'm on a rooted T-mo/T889 Galaxy Note 2 with stock 4.1.1 and UVALL4. I flashed TWRP on it a few months ago, when I was looking into installing DN3 rom.
It seems to me that the instructions for installing DN4 (which is what I'm looking at today) might assume my device is updated to latest firmware.
So I'm wondering where to start. Do I need to update bootloader, or can I just move forward with electronteam's install instructions flash DN4 with addon patch? Or even more broader terms, can I flash a 4.4.4 + rom from a 4.1.1 firmware?
Click to expand...
Click to collapse
You're good to go with DN4... just flash Dn4 and addon. The only thing is, Dn4 has issues with GPS. So, if you need/use this often, you may want to stick with DN3. Oh yeah, update your TWRP to newest (2.8.5.0) since it's been a few months since you installed it. And after you get it set up, update to the newest Agni kernel... http://forum.xda-developers.com/showthread.php?t=2602053
Thanks.
I went ahead with DN4, and sure enough, I have no GPS.
A more troubling issue I'm having is that my data/phone signal just randomly gone. I live in a city with LTE , and have no coverage issues here. Sometimes a restart will remedy it, but only for a short while. I'm going to flash this Latest Agni, Maybe that will fix it. EDIT: Nope, still happening. Changing Network Mode back and forth between LTE and WCDMA/GSM seems to be easier than rebooting though.
So...it's been about 6 months now since first tried to gather the in for I needed in order to get my device back to date.
.When I first got te device...it did an ODA, and I ODINed a root in and installed TWRP.
So I'm essentially on build --info posted below via screenshot-- and am trying to install the New Iron ROM. I've received messages from people whobsaid that I need to flash the boot loader before I can go from stock 5.0.2 to the latest IronROM/Ironkernel.....and I've seen messages that I then purpose of flashing a boot loader for people trying to get on a particular ROM, is so that "they ***can get*** the 5.0.2 boot loader-- if you're on 5.02....you can install 5.0.2 Roms freely...as long as you have the 5.02 boot loader (which you must have because you're running 5.0.2.) The reason this boot loader mess is such a big deal is because some people want to install custom LOLLIPOP ROMs, when they have only Evey installed Kit Kat ROMs. So the first time you flash a lollipop FROM you have to flash the botloader....but once you do that you can flash everything from lollipop and up (because the new lollipopband marshmallow builds use the stock code from lollipop at the moment).
I'm a competitive hearthstone player ad access to a computer and Odin is far away right now.....so if I could do this all through tarp.....or just unfreeze the update app, let it update, and reroot, if possible.....and then I could just flash what I wanted...but I'm notbsure whose right. Most of Tue devices I've handled all my rom flashing through TWRP, with no care I the world for what baseband I had. It was never an issue.
I've posted a screenshot of the build I'm on below (am using a custom kernel for sound boost)....
Would like to install this --
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
So....I'm on a 5.02 FROM. A stock one. Is it a different build than the one that FROM is based on? It looks like it. But should have the right boot loader! Right? In this case... I can just wipe/flash with tarp! No odin /boot loader futzing about needed. And I can use the other some too right? The CM or Pad Man ones? Because they're using the 5.02 code from Samsung for our device to get those build working?
/facepalm.. .
Or.....if every time a new from based on a new 5.0.2 build comes out, I have to odin a new boot loader so that I can now install roms made from a different base...even though what really mattersnis that I have a 5.02 boot loader already....
I though that the version number was what mattered. IF 6.0 came out tomorrow and everyone started making roms based upon the stock 6.0 code, id have to get the same version number boot loader as they had in the source material.
Conflicting messages >.<
I'm on a Completely stock, rooted 5.02 ROM. U1BOCC
The from I want to install appears to be 5.02 based on BOJJ.
What do I do now?
Hello!
I have a friend who is fed up with Lollipop, downgraded to KitKat and is still having issues, so now he wants to downgrade the Note 3 back to Android 4.3 (Jelly Bean), but the ODIN process keeps failing. I've read around that downgrading the bootloader (to a version prior to the KitKat update) would bypass the "Must be a KitKat ROM" check and allow his device to be downgraded to the older firmware, so my question for you guys is could you please provide me (or at the very least) point me in the right direction so I can successfully complete this for him? If it's absolutely NOT possible, please let me know, but based on my reading around on XDA, I'm pretty sure it's possible once you downgrade the bootloader to one which doesn't include those checks.
Thanks.
You cannot load a 4.3 bootloader over a KK or LP bootloader.
Your only option is to flash a custom ROM based on JB, but at this point in time I highly doubt that any links to JB are still functional. As stated above, you cannot load a 4.3 bootloader once you've updated to LL.
What are the so fed up with on 5.0? Mine has been a dream especially with all the recent little updates. Buttery smooth, and no issues at all. Maybe a full factory reset, or even a factory reset, and ODIN flash of it again? Sorry to hear about the problems.