Develop Bugs

[Q] Unable to flash custom roms

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.

[Q] ATT S3 Upgrade to 4.4

I am not very much familiar with all intricacies of Android system but i have played around rooting and putting customer firmwares on few devices.
I have AT&T Galaxy S3 with following detals:
Baseband: I747UCUEMJB
Version: 4.3
I had the device rooted in the past but recently un-rooted it and reset the flash counter as well and did factory reset. Did all that since i wanted to use ISIS and couldn't make it work on a rooted S3. Seems it used to work before till they updated ISIS app to patch it.
Now AT&T got 4.4 update and my phone detects it, downloads it but while installing fails at 32%. I have seen many threads where people faced similar issues due to their phones being rooted. Seems something on my phone didn't reset to default.
I found one post which mentions that i can download UCUEMJB_to_UCUFNE4_Firmware_update.zip and load it to phone using TWRP. As i understand, this will update the baseband but android version still remains at 4.3 (?). Is that the path i should be looking for or i am shooting in wrong direction? I want to stay on default firmware since i like to use ISIS till they keep running those cashback promos
Would appreciate some feedback.

Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.

DocHoliday77 said:
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
Click to expand...
Click to collapse
Thanks for the reply.
Just to confirm so that i don't mess up, i will apply the following(is modem same as firmware?) and then try OTA.
I747UCUEMJB: modem_CWM_I747UCUEMJB.zip

No. The modem is only one part of the firmware. Firmware includes bootloaders, kernel, system, modem and more.

HardBricked i747 after UCUFNE4

I've got a different issue here. I was running SlimKat 4.4.4 with BMS kernel on my d2att. I was on the CUEMJB Bootloader and Modem, so I thought that I can directly flash the rom. First, what I did was flash UCUEMJB_to_UCUFNE4_Firmware_update.zip. It flashed perfectly till the end. Then I flash the I747UCUFNE4_Stock_Rooted_Deodex_3-31-15.zip, which had an error that I had forgotten. It apparently is caused by my BMS kernel, so I went on and reinstall SlimKat 4.4.4 to remove the kernel. It flashed perfectly, but when I rebooted my phone, it did not power on. I was thinking, what's inside the UCUEMJB_to_UCUFNE4_Firmware_update.zip, are they the bootloaders and modem for CUFNE4 ? If so, is my phone dead like all the others who flashed 4.4.2 modem over 4.3 ? Please, I need my phone bad.

Did you follow this thread: http://forum.xda-developers.com/showthread.php?t=2789917 ?
Since you were already on the mjb bootloader, you flashed the UCUEMJB_to_UCUFNE4_Firmware_update.zip file? Any errors when flashing this?
Before installing NE4 firmware, did you do a full wipe as instructed in step 3 of the thread I linked?

audit13 said:
Did you follow this thread: http://forum.xda-developers.com/showthread.php?t=2789917 ?
Since you were already on the mjb bootloader, you flashed the UCUEMJB_to_UCUFNE4_Firmware_update.zip file? Any errors when flashing this?
Before installing NE4 firmware, did you do a full wipe as instructed in step 3 of the thread I linked?
Click to expand...
Click to collapse
Hey yeah. No errors occurred when I flashed it. The only I have gotten was from the OTA update zip itself. I can't remember what it is, but it prevented me from updating my phone to UCUFNE4. So I reinstalled Slimkat and booted properly but at the time I've rebooted, it's all dead.

And also, yes. That is the post that I've followed. I checked if my bootloader and modem are CUEMJB, and they are. So I figured that the firmware update should've not ruin it.
NOTE : I am running on a debrick card UCUEMJB if that helps with the information. I can't seem to boot off the eMMC itself, so I always kept the SD card on the slot. That, until it died.

I really think that my bootloader is messed up because of the UCUEMJB_to_UCUFNE4_Firmware_update.zip. I think it borked my bootloader, that's why I can't use any debrick images to recover it. Please, help. I'm short on funds, and losing this phone is a big cut on my budget.

I heard that the i747m users recovered theirs by pulling out the 128mb file. So if any of you i747 users running at the NE4 version could just pull out the bootloader partition, that would be great. enewman's debrick doesn't seem to work for me.

The bootloader for the i747 and i747m are not compatible even though they phones appear to have the same hardware.
So the phone does not boot at all with the mjb debrick image?

audit13 said:
The bootloader for the i747 and i747m are not compatible even though they phones appear to have the same hardware.
So the phone does not boot at all with the mjb debrick image?
Click to expand...
Click to collapse
It does not. Not even with the 4.4.2 debrick image. Help

If it used to boot with the debrick image and it doesnt boot now, a jtag service may be the only way to revive it.

May I just know what happened to my phone before it had gone bananas? A little information might help. Also, Im planning to buy a board for T999. Will it fit with the I747 chassis ?

I really don't know what happened to cause this problem with your phone. When flashing a phone, there is always an element of risk. I have pooched a few phones in my life too. I even damaged a couple of sim slots by using sim adapters too.
When your phone was able to boot with the debrick image, you could have tried reflashing the mjb bootloader and modem but it's a moot point now.

URGEN: Trying to go from CM11 to any TW firmware to use unlock code

Hello, it's been a long time since I messed with this but I'm smart. I'm also in a rush (unfortunately) to find a TW-based firmware that I can flash to from CM11.
The end goal is to use the unlock code I just purchased, but that won't work because I'm on CM11, I assume.
I'm knee deep in information, half of which I understand, half of which I think I barely understand.
What information do you need to help me?
From what I understand, being on a 4.4.4 CM 11 I must have a firmware that is at least android 4.3 or higher, is that correct?
If so, what other specs do I need to ensure I don't brick the phone from having the wrong bootloader, modem, ect from being incompatible?
Effectively, I'm tyring to find firmware to get back to any TW-based firmware from CM11 android 4.4.4. (Also somewhat unsure if it needs to be just TW based or 100% stock)

politelyowned said:
Hello, it's been a long time since I messed with this but I'm smart. I'm also in a rush (unfortunately) to find a TW-based firmware that I can flash to from CM11.
The end goal is to use the unlock code I just purchased, but that won't work because I'm on CM11, I assume.
I'm knee deep in information, half of which I understand, half of which I think I barely understand.
What information do you need to help me?
From what I understand, being on a 4.4.4 CM 11 I must have a firmware that is at least android 4.3 or higher, is that correct?
If so, what other specs do I need to ensure I don't brick the phone from having the wrong bootloader, modem, ect from being incompatible?
Effectively, I'm tyring to find firmware to get back to any TW-based firmware from CM11 android 4.4.4. (Also somewhat unsure if it needs to be just TW based or 100% stock)
Click to expand...
Click to collapse
The first thing I would recommend is to verify your bootloader and modem version. There is a playstore app, Phone Info *Samsung*, by vndnguyen that will do this. Or you can use the terminal emulator that is in CM roms and find out with these two commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
All I have seen indicates you will need to be on a stock rom with a stock dialer to use the code. You may even need to unroot before using (I am not sure about root/unroot.) Before recommending any stock rom source, are you using an i747 or an i747M?

dawgdoc said:
The first thing I would recommend is to verify your bootloader and modem version. There is a playstore app, Phone Info *Samsung*, by vndnguyen that will do this. Or you can use the terminal emulator that is in CM roms and find out with these two commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
All I have seen indicates you will need to be on a stock rom with a stock dialer to use the code. You may even need to unroot before using (I am not sure about root/unroot.) Before recommending any stock rom source, are you using an i747 or an i747M?
Click to expand...
Click to collapse
I know that it is an I747. I will comment again when I have the info for bootloader and modem.
So lets assume we find a rom that is; i747 gs3 stock rom and stock dialer; meets android version requirements (which I would love to have confirmed, based on the OP); compatible bootloader and modem; and is rooted, and the unlock code doesn't work. If we assume the unlock failed because it is rooted, is there a way to unroot the phone that doesn't require flashing a different, unrooted, to spec, rom? That is something that I truly don't understand what is happening.
Is there a wiki, or a list, or somewhere I can go to learn more about bootloaders and modems? I don't understand how they play into the overall configuration; such as how they may be X or Y when I'm running CM11, instead of being mandatory for a given configuration. I guess that question is, what prerequisites determine the bootloader and modem options that one may be and can be running or that one can flash successfully.

politelyowned said:
I know that it is an I747. I will comment again when I have the info for bootloader and modem.
So lets assume we find a rom that is; i747 gs3 stock rom and stock dialer; meets android version requirements (which I would love to have confirmed, based on the OP); compatible bootloader and modem; and is rooted, and the unlock code doesn't work. If we assume the unlock failed because it is rooted, is there a way to unroot the phone that doesn't require flashing a different, unrooted, to spec, rom? That is something that I truly don't understand what is happening.
Is there a wiki, or a list, or somewhere I can go to learn more about bootloaders and modems? I don't understand how they play into the overall configuration; such as how they may be X or Y when I'm running CM11, instead of being mandatory for a given configuration. I guess that question is, what prerequisites determine the bootloader and modem options that one may be and can be running or that one can flash successfully.
Click to expand...
Click to collapse
Some of the stock ROMs will remove root, that would be one way to resolve the issue. If you flash a stock image that is rooted, and it is rooted with SuperSu you can use the options in the SuperSu app to either temporarily unroot or to completely remove root.
I don't recall seeing a specific source for info about what bootloader / modem is needed in each situation. Most is accumulated knowledge from reading many posts and threads.
There are variations on what is correct, it all depends on the specifics of a device's status. For example, CM 11 would run on 4.3 bootloaders and modems up until about September of a year ago (or was that two years ago), since then you need to be on 4.4.2 bootloaders and modems. I think the same held true for AOSP based roms. I don't recall seeing where any of the 5.x.x roms have run on 4.3 bootloaders and modems. (Well, I think the devices run but have signal and data issues - both 4.4.x and 5.x.x roms.)
Generally you will see it said that the 4.4.2 Touchwiz based custom roms must be on 4.4.2 bootloaders and modems. In truth there were a number of such roms that would run with the 4.3 bootloader and modem IF one of a few specific kernels were flashed just after the rom was flashed.

I need 4.1.1 firmware for Koodo i-317M

Hello guys,
For some reason, my phone shows that my SIM is locked ( I was on RR 6.0). I need to flash the 4.1.1 firmware for Koodo to unlock the SIM.
Can anyone send me a link for this firmware?
Thank you!

You don't need Koodo to unlock the sim. Just flash the stock LJ2 firmware with Odin and use the dialler menu to permanently network unlock the phone.
https://forum.xda-developers.com/showthread.php?t=2014982
Maybe this will work: http://rapidgator.net/file/0207e341...yos.com/samsung-galaxy-note-2-stock-firmware/

I know it's been a long time, but did this procedure actually WORK? AFAIK, Koodo Note 2s never came with less than KitKat, and we all know that Samsung has blocked downgrading though its bootloader starting then.
The reason I ask is I'm looking for a spare phone for mine as a backup and can't seem to find one on which I can load my Jellybean 4.1.2 CM based phone image.

Well this an interesting post, I have a similar problem, I have 2 exact Note 2 phones one with custom firmware (4.1.1) one without, I would like to copy/clone the stock firmware to my other (as I somehow managed to delete the stock firmware on it)
Now I have made a backup with TWRP and copied it to the other phone but TWRP refuses to install it, it tries to install and gets most of the way but at the very end I get the 255 error "install failed"
Why can't I copy/ install this backup?
Do I need to to use some other recovery software or make a backup some other way.
Thanks

Old faithful said:
I know it's been a long time, but did this procedure actually WORK? AFAIK, Koodo Note 2s never came with less than KitKat, and we all know that Samsung has blocked downgrading though its bootloader starting then.
The reason I ask is I'm looking for a spare phone for mine as a backup and can't seem to find one on which I can load my Jellybean 4.1.2 CM based phone image.
Click to expand...
Click to collapse
The note 2 sgh-i317m was used by Telus, Rogers, and Bell.
This downgrade method works. I've used it to network unlock four note 2 models.
The stock 4.1.1 firmware from sammobile.com did not contain a bootloader file which allowed me to flash it using Odin on a phone running a stock 4.4.2 rom.

audit13 said:
The note 2 sgh-i317m was used by Telus, Rogers, and Bell.
This downgrade method works. I've used it to network unlock four note 2 models.
The stock 4.1.1 firmware from sammobile.com did not contain a bootloader file which allowed me to flash it using Odin on a phone running a stock 4.4.2 rom.
Click to expand...
Click to collapse
Man, if this really works it's going to solve all my problems. Are you saying you can flash the 4.1.x ROM on top of the the 4.4.2 bootloader (presumably one could deselect the bootloader from the 4.1.x ROM if it was included - sorry I'm quite rusty at this, haven't used Odin in years), so that the phone may be running ICS or JB despite having a 4.4.2 encrypted (locked) bootloader?
The idea is being able to load Clockworkmod recovery and from it, the rooted 4.1.2 backup on my external sd card...
Sorry if it's been asked before and if I may be confused - Thing is, I haven't done this type of tweaking in 5 years

I could flash a stock 4.1.1 ROM from sammobile.com on top of a stock 4.4.2 ROM because the stock 4.1.1 ROM didn't contain a bootloader. I did this to use the menu method to network unlock the sgh-i317m; however, the phone cannot stay on a stock 4.1.1 ROM with a 4.4.2 bootloader because the phone cannot connect to a cellular network with this 4.1.1 ROM/4.4.2 bootloader combination. After I unlocked the phone, I either re-flashed a stock 4.4.2 ROM or a new custom ROM.
The bootloader on the Canadian Note 2 was never locked the way it was with some USA carriers.

audit13 said:
The bootloader on the Canadian Note 2 was never locked the way it was with some USA carriers.
Click to expand...
Click to collapse
Are you saying the Koodo/Rogers.... 4.4.2 Note 2 bootloader is NOT locked on our phones, ergo, that I could downgrade to 4.1.1 including its bootloader successfully?! If so I'm set, I could purchase a used one on kijiji and simply reload my old Bell based ROM backup on it I simply look for a way to load my 5 year old Rooted ROM onto a newer version of the phone. I have on it apps that won't run on 4.4.2 that I sorely miss on my tablet (which runs 4.4.4)

The bootloader is not locked which allows for the installation of TWRP and cwm but it cannot be downgraded.

audit13 said:
The bootloader is not locked which allows for the installation of TWRP and cwm but it cannot be downgraded.
Click to expand...
Click to collapse
In other words it does allow for installing the 4.1.1 ROM for unlocking the phone, but it can't can't actually be used with the 4.1.1 ROM... What if I simply reinstalled the 4.4.2 modem, wouldn't that work?
I now I'm asking quite a lot - but in my case if I haven't been able to find a used phone that hadn't been at some point 'upgraded' and consequently became shackled (I've been looking for over a year now) in which case I might as well mourn it and move on to a new phone and start the fight for freedom all over again Honestly, I've grown tired of having to fight for the basic right of ownership against the relentless push for slavery that is the general trend in technology, to force people away from freedom of using the software they prefer and force them into a system where they must follow the dictates of corporate giants so perfectly exemplified by the cell phone, computer and browser based service industry.
Like Frederick Douglass famously said "Power concedes nothing without a demand. It never had and never will"... In other words if you want freedom and true control, you MUST FIGHT the providers and the manufacturers whose prime interest is to keep you enslaved

Installing the 4.4.2 modem will install but the stock 4.1.1 dialer doesn't work with a 4.4.2 modem and 4.4.2 bootloader from what I recall. It's been a long time since I had a note 2.