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.
Galaxy Note 4 Acquisition Day is rapidly approaching, but first I need to do some housekeeping... like get my AT&T S3 unlocked so I can keep using it after switching to T-Mobile. I'm currently running CM11 [d2lte] w/MJ2 bootloader, CM kernel, and TeamWin recovery. As far as I know, the phone has to be running a stock(-ish) ROM in order to use the unlock code from AT&T.
Paranoia point: I had a HELL of a time reflashing from a pre-rooted Knox-disabled 4.3 ROM to CM11... literally, I spent a day and a half trying desperate, semi-random things over and over again until it the flash seemed to finally "catch" and work. I have a hunch my problems might have been eMMC-related. For obvious reasons, I'd like to be better prepared this time around & I'm open to suggestions for specific semi-stock ROMs to try.
More concerns: I know you can't downgrade from stock 4.4 to stock 4.3... but can you downgrade from CM11-4.4 to stock-derived 4.3?
I'd very, very much like to keep the phone un-Knox'ed, so I can have my cake (keeping it rootable & reflashable without permanent consequences) while eating it too (preserving my ability to flash it to official Samsung 4.4 someday in full Knox glory, just in case I end up needing a Knox-capable wifi device for company email purposes someday). If push came to shove, I guess I could deal with Knox'ing it now since I'm getting my new phone in another week or three, but I'd really rather avoid burning the Knox bridge behind me if I can avoid it.
For unlocking, most stock based roms will work. As long as it has the stock dialer.
Im not completely sure about MJ2 firmware, but I believe you are still free to flash older versions. If this is confirmed, you can flash 4.1.1 firmware and unlock for free. Then from there update to MJB or NE4.
Once there though, if you trip the warranty bit you can never use knox. So if you want to preserve that ability, dont go above MJ2. (Not sure if it has the warranty bit.)
As for roms, if youre on at least MJ2 or newer, you can flash any rom you want. Old or new. Its just the base firmware that cannot be downgraded once on MJB or newer.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hello,
I just bought my first Galaxy device (had a CDMA LG for a while, and I have a Nexus Tablet), and I am looking at how to get this new phone set up right. I bought my i747 retail, so I was unable to unlock it. However, now I'm struggling with finding the right method for upgrading, rooting, etc. I know nothing about knox or any of these Samsung intricacies. Could someone please give me a little guidance on how to go about getting to the OS and status that I'm looking for? This is what I've done so far:
Came unrooted with 4.1.2 stock rom
Unlocked using legit unlock code
Tried OTA updates, but none were available (must be because of unlock)
Rooted w/ ODIN using 4.1.1 file based of MrRobinson method. (http://forum.xda-developers.com/showthread.php?t=1739426)
Now I keep getting popups like process. ... .acore,media, etc. stopped.
I'm looking to ideally get a custom recovery (either CWM or TWRP, whichever is better) and either kitkat Touchwiz or possibly kitkat nexus stock (I read somewhere that it was possible). Also, i just bought it, and have the code still, so I don't mind deleting everything if needed. Regardless, I'd like the ability to get it back to pure stock with no flash counter (I have a manufacturer's warranty I want to use if need be).
Could someone please just give me a little guidance? I'm pretty capable with rooting, etc., so you'd only need to lead me to other threads, etc. that will take me where I want to go. Thank you very much.
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
audit13 said:
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
Click to expand...
Click to collapse
Well, the bad news is I already flashed using MrRobinson's instructions, and now my phone is barely workable, as things like process.android.media and Touchwiz keep crashing. I was able to install the info app though, and my bootloader is listed as I747UCDLK3. Thanks again though, and let me know what else you need from me.
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
audit13 said:
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
Click to expand...
Click to collapse
Thank you, but wouldn't OTA updates install Knox, which would basically void my warranty if I tried to flash anything after that? And, I've checked for OTA updates twice, once on 4.1.2 and on 4.1.1, and both times it said my software was up to date.
I spoke with StoneyJSG about my situation, and he suggested that I go to stock 4.1, root w/ saferoot, then flash a kitkat custom rom without Knox through TWRP. That way, I could use triangle away and flash stock unrooted if I needed to send it in.
Although, I'm not sure if I should do that, as I thought I read that you need to update the radio and bootloader first before you can install a custom kitkat rom from jelly bean, but I'm still not entirely sure how that works.
The most recent release of many custom ROMs will not work but you may not have a signal without an updated modem and you should not be running updated modems on an older bootloader. Doing this could brick your phone.
With a rooted system, OTA updates will not work.
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
jateed said:
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
Click to expand...
Click to collapse
What is your cell service? If not AT&T, you will never get OTA.
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
audit13 said:
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
Click to expand...
Click to collapse
Well, I have an AT&T model which I unlocked and will be putting on Cricket at the end of the week (when my plan month is set to end). Right now there's no SIM in it, and I've been doing everything over wifi. I looked up whether the carrier had something to do with the OTAs, and I was told that Samsung sent the updates out, not AT&T, so I figured that the carrier info was irrelevant. I now wonder what my options are.
Can I manually flash 4.3 stock without tripping the knox warranty void?
Does Towelroot/Xposed framework trip the Knox void flag?
If I can update to 4.3/4.4 and root without tripping the knox flag, I might just manually update and just run towelroot and xposed to modify my OS the best I can until my warranty runs out.
If I can't root it at all once I'm on 4.3+, then I'll just sit on 4.1.1 for a few months until I can't stand it anymore and just void the warranty anyway.
Thanks again everyone. This whole knox/binary counter thing is not something I dealt with on my CDMA LG or Nexus, so I was totally in the dark about how it all worked. This is also my first GSM phone, so all those intricacies are new to me too. Once I know about manually flashing stock and running towelroot/xposed, I think I'll be in good shape.
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
audit13 said:
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
Click to expand...
Click to collapse
Excellent. If I did flash stock, i would just use ODIN, then factory reset to wipe the caches. And that's good to know about the KK rom, as I would probably update straight to 4.4 if at all (I've read a lot of bad things about 4.3 on the S3), but not if it means I cannot root safely and cleanly.
I'll check out the custom roms for 4.1.1. I know that flashing the rom and/or a custom recovery will trip the binary counter, but I can just use triangle away to clean that up. Do you know if there is a list of custom 4.1.1/4.1.2 roms somewhere, or do I need to scour the older threads here?
Thank you very much audit13 (thanks to StoneyJSG and pre4speed as well). You have been immensely helpful and really brought me up to speed on everything surrounding S3 customization. Needless to say it's way more complicated than what I've dealt with from LG and Google/Asus. (I mean, i could root my nexus with a single click using Wugfresh's toolkit)
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
audit13 said:
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
Click to expand...
Click to collapse
Oh, so what other way can you flash a stock rom, if not through ODIN or a custom recovery? Regardless, it seems as though I really should not dive into 4.3+ until I'm ready to concede that my warranty is over. There are just too many potential pitfalls and headaches.
On the lighter side, I've found a few 4.1.2 based custom roms that have some promise. I'm going to post them here in case anyone has opinions on them, or if someone else in my situation sees this thread and wants to go custom 4.1 too:
Hyperdrive RLS16
http://forum.xda-developers.com/showthread.php?t=2176793
Slim Bean-d2
http://forum.xda-developers.com/showthread.php?t=1865262
Jedi Academy
http://www.teamandroid.com/2013/12/...oid-412-jedi-academy-jelly-bean-custom-rom/2/
Jelly ‘Beans’
http://www.teamandroid.com/2013/04/...ndroid-412-att-galaxy-s3-sgh-i747-custom-rom/
I was also torn when I got my s3 that was running 4.1.2. I downgraded to 4.1.1, sim unlocked the phone, used it on stock 4.1.2 for about a week to make sure everything was working, hardware wise, upgraded to stock 4.4.2, installed a custom recovery and a custom ROM. I wasn't too concerned about the warranty since I got the phone as a free upgrade and had no intention of using the s3 as my daily phone. I kept it as a backup until my niece needed and phone and then it went to her. It's been over a year and there are still no problems with the phone.
Hello,
I'm a noob but usually try to fix this kind of issues on my own, looking at the boards, following tutorials, learning, but this time I think I'm not able to find a solution on my own so I'm asking for advice here.
Some time ago I installed cyanogenmod 10.1 on my Note 2 LTE and was happy with it for some month, than last week I tried to upgrade to cm12.1 It worked but there where some issues and bugs, mainly I wasn't able to swap internal/external sd cards.
So I decided to go back to latest available stock rom 4.4.2 from sammobile.
Here is where the problem starts. The stock 4.4.2 resulter in a bootloop, tried cache/dalvik/factory reset, flash again, whipe again.. nothing.
The phone is not able to get past the white label "Samsung Note 2 gt-n7105" screen. It goes black than the white label again and again.
It doesn't even get to the Samsung animated logo.
Ok bottloop, no problem, try to flash again something else.
I tried different Custom roms, different kernels, different flashing methods. I can flash anything with no problem but every time a get a bootloop.
During the various attempts knox fired, but I don't care. I don't know if this could be the cause.
Actually the only firmware that works is the original oldest STOCK 4.1.2, every other stock firmware past that or any custom rom is bootlooping the same way. To fix I only can reinstall stock 4.1.2 with odin.
I really need any advice or hint.
At the moment my goal is to get at least to stock 4.3 but I cant.........
Thanks!
When you first bought your phone, did it come with Knox?
ErnestChia said:
When you first bought your phone, did it come with Knox?
Click to expand...
Click to collapse
nope it doesn't existed before, but now I can see it when I boot in download mode "knox warranty void:1"
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/showthread.php?t=2088809/[URL]
From what you've described, I think the Stock ROM 4.4.2 from Sammobile contained a bootloader update. So when you flashed this ROM, it updated your bootloader from the non-Knox version to the Knox version.
I am very unfamiliar with the technical details of Knox, but I think the new Knox bootloader is causing your bootloop problem.
However, I don't know why 4.1.2 works when everything else doesn't work!
Can you check the Stock ROM 4.4.2, and see whether it really contains a bootloader update?
mysuperdonghae said:
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/sho...can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
misthero said:
I think so, there is a boot.im, anyway I also discovered that I can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
Since a boot.img is present, it means that it would flash your boot partition. So now we know for sure that when you attempted to flash the Stock ROM 4.4.2, your bootloader was changed to the Knox version.
So the lesson here is: before you flash anything via ODIN, always check to see if there is a bootloader update. Usually you don't want to be changing the bootloader on your phone.
***
So now there are 2 possible ways to reach your goal:
1) Keep your new bootloader and see whether you can get Stock 4.3 or Stock 4.4.2 running on your phone
2) Try to restore your old bootloader
As I said earlier, I'm not familiar with the technical details of Knox, so I'm not sure how to get Stock 4.3 or Stock 4.4.2 running on your phone when your Knox indicator is already 0x1. You need someone else to help you.
And you can only restore your old bootloader if you happen to have made a copy of your boot partition before you flashed the Stock ROM 4.4.2. Even if you did have a copy of your original boot partition, I'm not confident with helping you to restore your old bootloader. You need someone else to help you in this case too.
Conclusion: I don't think I can help you to solve your problem I'm sorry. Hopefully someone else who is more of a pro than me will come along to help you out.
Good luck!
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.