Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Zeuszoos said:
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Click to expand...
Click to collapse
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Zeuszoos said:
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Click to expand...
Click to collapse
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
There is an MM ROM that is Rooted and has TWRP built in, but I don't know if it would Flash over this with Odin or not
I am also considering trying the entire KK T2 ROM again to go down to KK and then Flashing that MM ROM.
It has both Odexed & DeOdexed. If I remember right, DeOdexed is the better choice, right?
Thanks for all your time and help!
Dave
Hi,
You know what's sad, is that if I could somehow Roog it without TWRP, then I could use the way awesome "Flashify" app to try to get TWRP on this phone! <lol>
Dave
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Zeuszoos said:
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Click to expand...
Click to collapse
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
dottyparent said:
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
Click to expand...
Click to collapse
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Zeuszoos said:
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Click to expand...
Click to collapse
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
No, I'm sorry, but you have to give me the answer.
All seriousness aside, I depreciate all your effort.
I can only think of one thing left to try... Go to Sammy's site and get the Lollipop 5.1.1 ROM and see what happens. It can't hurt to try, right?
I'll let ya know what happens and thank you again!
Happy Thanksgiving!
Dave
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Zeuszoos said:
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Click to expand...
Click to collapse
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
ShaDisNX255 said:
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
Click to expand...
Click to collapse
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
That's because I have a n910t not a t3
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
I upgraded from LL. The device was running 5.0.1 and now has 6.0.1
dottyparent said:
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Click to expand...
Click to collapse
Thank you for looking! I found out what it is.
It's "Factory Reset Protection" (FRP)
What it does, is keep someone else from Factory Resseting your phone if they steal it. When they reset it, during setup, they have to type in the last Google Email and Password that the phone used, before they can set up theirs.
After reading that, I remembered having to put my Google Info in at two separate points and seeing it telling me to "Verify", but I was just blowing right through setup, not reading all of the small print. I mean hey, I had no idea that even existed and was just annoyed that I had to type the same thing twice!
It will only be found on phones that already have Lollipop and up on them out of the box and probably not all of them yet. And you don't have to worry about downloadable ROMS, so those who have phones that started with KitKat, or even early versions of Marshmallow 6.0 or 6.0.1 would not have seen this happen to them. Even those who updated to the same version of Mm that my phone has won't, if they started with KK or an older MM and then updated to it.
Again, this is something that your phone would have "Out of the Box" and the phone (not all) would have at least L on it.
Just FYI, it's not just Samsung, either.
Just FYI, I have confirmed this info. It is a fact.
Once I have an easy to do, working fix, hopefully without having to perform a Factory Reset, I will "Create A Thread" and as normal for me, write clear and easy, step by step (not leaving any out) instructions on how to "Unlock FRP" and then come back here and post a link to the thread. Hopefully this week.
This phone will not beat me!!!
TTYL
Dave
Related
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
Oh god are you on the US version (SGH-I537)? If you're on the international version (I9295) ignore this post but otherwise, you need to read and take in my short rant. Trust me I wish this weren't the case, but it is, and it's important:
The Galaxy S4 Active i537 has a locked bootloader. There is no way around this, no ifs ands or buts. You simply cannot flash custom ROMs or recoveries. That's it, end of story as far as CM, CWM, AOSP and such things are concerned. That being said there is a sort of recovery called SafeStrap which you can use to make nandroid backups, flash mods and STOCK-BASED roms, but it's not a true custom recovery in the sense that we had been used to, because of this locked bootloader nightmare.
OK so I think you're gonna want to check out this thread. It's all about how to install any firmware from download mode, I think you're gonna have to go with NE3 or NH3.
Let me reiterate. NO CUSTOM ROMS. NO CWM. No Paranoid, no cyanogenmod, no AOSP, no crossing go before going directly to jail. Sorry for the stupid joke but seriously, you have got to keep your phone on stock-based roms (of which there are unfortunately few).
Firmware download links
timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
What phone do you have (i537 or i9295) and what version of firmware were you on?
Devo7v said:
What phone do you have (i537 or i9295) and what version of firmware were you on?
Click to expand...
Click to collapse
i537 and second to last, I537UCUCNE3
Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?
Web browser login, edit, advanced.
Add "solved" to title?
same problem with my i537, need help
timmytron said:
Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?
Click to expand...
Click to collapse
Need help, having the same problem
baddhabbitz88 said:
Need help, having the same problem
Click to expand...
Click to collapse
Have you used ODIN before?
i537 Stuck in download mode
timmytron said:
Have you used ODIN before?
Click to expand...
Click to collapse
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?
baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Did you get my PM?
timmytron said:
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?
Click to expand...
Click to collapse
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
Well AT&T decided to completely lock us out on this particular version on this particular phone. At least we have *ROOT*.
baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.
Devo7v said:
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.
Click to expand...
Click to collapse
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
timmytron said:
Did you get my PM?
Click to expand...
Click to collapse
yeah I got it thanks but it didn't work still digging
baddhabbitz88 said:
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
yeah I got it thanks but it didn't work still digging
Click to expand...
Click to collapse
Always check the stickies.
http://forum.xda-developers.com/showthread.php?t=2892445
Q&A for Bootstack (KK and L) for L90
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Bootstack (KK and L) for L90. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
what can we do with bootstack ?
leandro_sousa said:
what can we do with bootstack ?
Click to expand...
Click to collapse
Bootstack is a bunch of files deep inside the phone. They are responsible for turning device ON and OFF, having SIM card support or download mode for flashing .kdz systems.
If you want to use stock KitKat or any customROM (KK or L) you need KitKat bootstack.
If you want to use stock Lollipop you need Lollipop bootstack.
Hi,
At the moment I'm running stock lollipop on a d405N. The Phone is also rooted, and i've unlocked bootloader and flashed TWRP 2.8.6.0.
After flashing your KK bootstack, can I immediately flash a custom Lollipop rom and Gapps, and if so will my waveband work?????
grey heron said:
Hi,
At the moment I'm running stock lollipop on a d405N. The Phone is also rooted, and i've unlocked bootloader and flashed TWRP 2.8.6.0.
After flashing your KK bootstack, can I immediately flash a custom Lollipop rom and Gapps, and if so will my waveband work?????
Click to expand...
Click to collapse
Yes. That's exactly for what bootstacks are made for.
If you will have any problems after using those files, let me know.
Also I would appreciate information if it worked so I could mark it as stable.
Xemidra said:
Yes. That's exactly for what bootstacks are made for.
If you will have any problems after using those files, let me know.
Also I would appreciate information if it worked so I could mark it as stable.
Click to expand...
Click to collapse
Thanks for your quick reply,
I see i made an error, it should be baseband not waveband
A few more questions though, before flashing your bootstack should I do a clean wipe?
Also, captivate king says: quote: Flash this after flashing my ROM, and you should be good to go, does the order in which I flash matter or not????
Thanks in advance,
grey heron said:
Thanks for your quick reply,
I see i made an error, it should be baseband not waveband
A few more questions though, before flashing your bootstack should I do a clean wipe?
Also, captivate king says: quote: Flash this after flashing my ROM, and you should be good to go, does the order in which I flash matter or not????
Thanks in advance,
Click to expand...
Click to collapse
I figured out that you meant baseband
It's not necessary to do a wipe. Changing bootstack does not affect /system, /data and /cache partitions, but if you'll have problems with your customROM you should of course start with a wipe.
There is no order in which you should flash your bootstack and ROM. I firstly flashed bootstack (while being on stock Lollipop) and restarted my phone to see if it worked. I had no SIM support so I knew that my flash was successful. Then I flashed CM.
One more important thing is that you cannot restart you phone if flashing bootstack fail. Also it's recommended to flash bootstack before you boot your customROM for the first time to eliminate any possible bugs caused by wrong baseband file.
If you have any more questions feel free to ask them.
Xemidra said:
I figured out that you meant baseband
It's not necessary to a wipe. Changing bootstack does not affect /system, /data and /cache partitions, but if you'll have problems with your customROM you should of course start with a wipe.
There is no order in which you should flash your bootstack and ROM. I firstly flashed bootstack (while being on stock Lollipop) and restarted my phone to see if it worked. I had no SIM support so I knew that my flash was successful. Then I flashed CM.
One more important thing is that you cannot restart you phone if flashing bootstack fail. Also it's recommended to flash bootstack before you boot your customROM for the first time to eliminate any possible bugs caused by wrong baseband file.
If you have any more questions feel free to ask them.
Click to expand...
Click to collapse
Hi again,
both bootstacks for D405N worked for me, no more problems with baseband and wifi, :good:so thanks again.
I was just wondering, why all the files in the bootstack? Wouldn't just changing the modem be sufficient? I know i'm showing my ignorance, but just when I think I've figured things out, I get back to square one
grey heron said:
Hi again,
both bootstacks for D405N worked for me, no more problems with baseband and wifi, :good:so thanks again.
I was just wondering, why all the files in the bootstack? Wouldn't just changing the modem be sufficient? I know i'm showing my ignorance, but just when I think I've figured things out, I get back to square one
Click to expand...
Click to collapse
It's for compatibility reasons. To make sure that everything is working fine I changed all files. It's less secure but more effective.
Hi Xemidra and everyone else.
I have used this for about 12-14 times now, going from stock LP to custom ROM and back, and as far as I Know it's working without any problems.
It's a great timesaver, but wouldn't it be better that ROMs have LP as a base instead of KK, so that using bootstacks or other or reflashing KK wouldn't be needed?
Is it something that a ROM chef could do?? Or is this a CM thing???
Another thought, the modem file used. I've read somewhere that its not just the variant, but that different regions, countries etc. can have different (optimal) modem files, ie what would work great for me in Holland, might be unacceptable for someone in say Brazil??? Anybody know more about this??? I've tried searching for this article again, but couldn't find it. I use google, anybody know a better search engine for these type of querries?
grey heron said:
It's a great timesaver, but wouldn't it be better that ROMs have LP as a base instead of KK, so that using bootstacks or other or reflashing KK wouldn't be needed?
Click to expand...
Click to collapse
Yes, it would be. You need to contact you ROM developer about this. I can't do anything about that.
Which bootstacks did you use ?
Another thought, the modem file used. I've read somewhere that its not just the variant, but that different regions, countries etc. can have different (optimal) modem files, ie what would work great for me in Holland, might be unacceptable for someone in say Brazil???
Click to expand...
Click to collapse
Maybe. I haven't head anything about that. No one complaint about quality of calls etc. I believe that different bootstacks for different variants are enough. Countrys from which I use the .kdz file to create bootstack are random.
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
http://forum.xda-developers.com/lg-l90/general/guide-guide-to-unlocking-bootloader-l90-t2852917
---------- Post added at 11:45 AM ---------- Previous post was at 11:28 AM ----------
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
Hi,
Am on a d405N myself, but I would stick to the same version aboot as your firmware: D410 v20a fw >>>> D410_v20a_patched_aboot. Stick with what works.
I wouldn't use just any aboot version. It might work, but why take the chance?
If you can't find the D410_v20a_patched_aboot, consider upgrading your fw to v20b first. Firmware is a bit easier to find.
It would be even better to flash a d410 v10 kdz, aand use a d410 v10 aboot. This way you wouldn't have to worry about using bootstacks.
Hope this helps, and stop spamming.
Odd Report
I'm here to thank you so much for putting all this information togetther, although it's possitive... my report should be a little odd, I want to report that BOOTSTACK_v1.4_D405N-10F helped me get my D400HN's (yes, D400HN) sim card running with Temasek's CM12... just in case someone is looking for an answer like this...
Thanks a lot!
dnuuk said:
I'm here to thank you so much for putting all this information togetther, although it's possitive... my report should be a little odd, I want to report that BOOTSTACK_v1.4_D405N-10F helped me get my D400HN's (yes, D400HN) sim card running with Temasek's CM12... just in case someone is looking for an answer like this...
Thanks a lot!
Click to expand...
Click to collapse
Your phone will from now present itself as D405n.
Because you seem like a nice guy I made a bootstack especially for you and you variant (D400hn).
It's not tested and it may be faulty. If you want to go ahead and download it. From what I read your variant has an unlocked bootloader so I included the stock one.
Xemidra said:
Your phone will from now present itself as D405n.
Because you seem like a nice guy I made a bootstack especially for you and you variant (D400hn).
It's not tested and it may be faulty. If you want to go ahead and download it. From what I read your variant has an unlocked bootloader so I included the stock one.
Click to expand...
Click to collapse
Awww! How nice and kind of you!!
I'll download it right away and give it a try tonight as soon as I get home... just a quick question... should I just flash it over the custom ROM I'm already using? or should I do a clean flash? If it's of any use, Im running CM12 Temasek Build.
Anyway, thanks a zillion for being so kind and dedicated, as well as for the patient for noob users like me :silly:
Hope you're well
dnuuk said:
Awww! How nice and kind of you!!
I'll download it right away and give it a try tonight as soon as I get home... just a quick question... should I just flash it over the custom ROM I'm already using? or should I do a clean flash? If it's of any use, Im running CM12 Temasek Build.
Anyway, thanks a zillion for being so kind and dedicated, as well as for the patient for noob users like me :silly:
Hope you're well
Click to expand...
Click to collapse
It shouldn't have any impact on your ROM but if you'll have any trouble then do the wipe.
Let me know if it worked for you.
Xemidra said:
It shouldn't have any impact on your ROM but if you'll have any trouble then do the wipe.
Let me know if it worked for you.
Click to expand...
Click to collapse
Well bad news... couldn't wait to get home and flashed it already dear @Xemidra, as soon as boot starts i get a nasty error that says Error: Boot certification verify, secure booting error. Cause: boot certification verify (and about 6 times de number "520")... And it turns off automatically three seconds after showing that screen, if I try Vol Down + Power, release and push the same combination again (as trying to get in Recovery Mode, TWRP in my case) the numbers changed to a 4 digit number (something like 5340 or so), tried three more times to enter recovery mode and I get the factory reset confirmation but as soon as I accept on YES the phone turns off completely and won't turn back or respond (unless I take the battery off and put it back on)
Any ideas on how to come back to life? KDZ? I had a lot of issues with KDZ before, couldn't get the LG software to recognize my phone at all
Any suggestion would be greatly appreciated, thanks
dnuuk said:
Well bad news... couldn't wait to get home and flashed it already dear @Xemidra, as soon as boot starts i get a nasty error that says Error: Boot certification verify, secure booting error. Cause: boot certification verify (and about 6 times de number "520")... And it turns off automatically three seconds after showing that screen, if I try Vol Down + Power, release and push the same combination again (as trying to get in Recovery Mode, TWRP in my case) the numbers changed to a 4 digit number (something like 5340 or so), tried three more times to enter recovery mode and I get the factory reset confirmation but as soon as I accept on YES the phone turns off completely and won't turn back or respond (unless I take the battery off and put it back on)
Any ideas on how to come back to life? KDZ? I had a lot of issues with KDZ before, couldn't get the LG software to recognize my phone at all
Any suggestion would be greatly appreciated, thanks
Click to expand...
Click to collapse
I can get to Download mode, but it only says ROOTED (In red) and an user number i.e. USER B47, but LG Flash Tool won't recognize the phone (the drivers are fine, the computer does recognize the phone, not LG Flash tool 2014
Any aditional ideas or should I just forget I had a phone?
dnuuk said:
I can get to Download mode, but it only says ROOTED (In red) and an user number i.e. USER B47, but LG Flash Tool won't recognize the phone (the drivers are fine, the computer does recognize the phone, not LG Flash tool 2014
Any aditional ideas or should I just forget I had a phone?
Click to expand...
Click to collapse
Try to use LG Mobile Support Tool ? It always worked for me. Make sure you really have all the drivers installed.
It will flash the original .kdz meant for your phone.
Sorry for all the trouble I guess that the bootloader was locked ? or it needed to be unlocked using oem-unlocked feature.
Hey guys!
I finally decided to update my z1 compact to 5.1.1
Currently I'm on 4.4.4 (.0.157 firmware); it's rooted thanks to a guide found on this forum that let me to not unlock my bootloader (but sincerely I don't remember which one was since it's passed about one 1 year :cyclops: )
I have to say that I've NOT backuped my DRM keys yet (bc I'm very very lazy :angel: )
Now, what should I do in order to experience new Lollipop thrill on my device but still keeping root and bootloader locked on it? Can I update directly with new official firmware using Flashtool (and then root it) or os there some pre-rooted firmware that can be suitable with my case?
Sorry guys, I wrote in wrong section. I reported the thread to moderator already. I'm waiting for the shifting. I'm really sorry
Have a look at this thread --> PRF Creator
Basically, download the Lollipop firmware, and create a pre-rooted, flashable zip file that you can flash from your existing recovery.
If you look in the forums, some users will probably have uploaded a pre-rooted lollipop zip for you to try if you don't feel comfortable trying to do it yourself.
Hope that helps
MickieH said:
Have a look at this thread --> PRF Creator
Basically, download the Lollipop firmware, and create a pre-rooted, flashable zip file that you can flash from your existing recovery.
If you look in the forums, some users will probably have uploaded a pre-rooted lollipop zip for you to try if you don't feel comfortable trying to do it yourself.
Hope that helps
Click to expand...
Click to collapse
Could this be a solution for the c6916 American z1s as well?
Helgaiden said:
Could this be a solution for the c6916 American z1s as well?
Click to expand...
Click to collapse
Hiya,
It should work with any firmware really.
I've used it for my Z1, and my Z3, and used UK, CE1, and CE5 firmwares with no problems at all.
If you need any help, let me know.
MickieH said:
Hiya,
It should work with any firmware really.
I've used it for my Z1, and my Z3, and used UK, CE1, and CE5 firmwares with no problems at all.
If you need any help, let me know.
Click to expand...
Click to collapse
Even with a locked bootloader?
Helgaiden said:
Even with a locked bootloader?
Click to expand...
Click to collapse
Yes. They're only stock roms. They still have stock kernels.
You only need to unlock the bootloader if you want to run a custom kernel, like Cyanogenmod, or any other custom rom that doesn't use a stock Kernel.
All of my phones still have locked bootloaders.
All PRF does (very cleverly) is inject root and recovery into a stock ROM. The only reason the output file is a zip file is because we can't create ftf files ourselves. Those are signed by Sony. All you do is install the zip from an already existing recovery, so your phone must be rooted, with recovery already.
MickieH said:
Yes. They're only stock roms. They still have stock kernels.
You only need to unlock the bootloader if you want to run a custom kernel, like Cyanogenmod, or any other custom rom that doesn't use a stock Kernel.
All of my phones still have locked bootloaders.
All PRF does (very cleverly) is inject root and recovery into a stock ROM. The only reason the output file is a zip file is because we can't create ftf files ourselves. Those are signed by Sony. All you do is install the zip from an already existing recovery, so your phone must be rooted, with recovery already.
Click to expand...
Click to collapse
I don't think recovery exists for the z1s c6916, but I do have root. What options are there for that?
Helgaiden said:
I don't think recovery exists for the z1s c6916, but I do have root. What options are there for that?
Click to expand...
Click to collapse
XZ Dual Recovery should work on the C6916 according to NUT.
I don't see why it wouldn't, it's still a Z1
It's in the compatibility list here,
http://forum.xda-developers.com/showthread.php?t=2647487
Have you ever tried it?
MickieH said:
XZ Dual Recovery should work on the C6916 according to NUT.
I don't see why it wouldn't, it's still a Z1
It's in the compatibility list here,
http://forum.xda-developers.com/showthread.php?t=2647487
Have you ever tried it?
Click to expand...
Click to collapse
I have not. Thus far the bootloader has not been unlockable so I haven't really tried doing much, or anyone else for that matter.
Helgaiden said:
I have not. Thus far the bootloader has not been unlockable so I haven't really tried doing much, or anyone else for that matter.
Click to expand...
Click to collapse
You don't need an unlocked bootloader for nuts xz dual recovery.
The only thing you need is root, because you need permission to write to your phones system partition.
motorazrv3 said:
You don't need an unlocked bootloader for nuts xz dual recovery.
The only thing you need is root, because you need permission to write to your phones system partition.
Click to expand...
Click to collapse
So then I wonder if anyone has used this method to flash a newer 5.1.1 factory image from a regular z1 onto the US tmo Z1s...
Helgaiden said:
So then I wonder if anyone has used this method to flash a newer 5.1.1 factory image from a regular z1 onto the US tmo Z1s...
Click to expand...
Click to collapse
I don't know but I think not. Because the phones hardware isn't the same on all z1 types, you get the risk that something is not working or you are bricking your phone. That's the reason we have the different phone models like 6902, 6903,....
That's right. You can flash NUT's recovery on locked bootloader devices, that is what it was designed for, and the reason it's called 'lockeddualrecovery' :good:
If you flash a different model numbers firmware, then the modem is likely to be wrong for your carrier. If you look at some of the rom threads you'll see a lot of the Z1 C6903 roms contain patches for the C6902 also, which I'm assuming is the C6902's correct modem.
I don't know if you could flash another models on yours, but exclude the modem, thus retaining your own.
If you want to remain on stock, then I would highly recommend downloading your own model firmware from XperiFirm, SuperSU, and lockeddualrecovery for the Z1, then run it through PRF Creator. That way you'll end up with the correct firmware (and thus modem) which would be pre-rooted, with locked dual recovery.
Which firmware do you want to have? The latest for the US TM that I can see is
1277-0679 USA T-mobile US 14.5.B.0.247
---------- Post added at 03:57 PM ---------- Previous post was at 03:34 PM ----------
I wonder if we could create a pre-rooted zip from the unbranded UK 14.6.A.1.236 by not including the modem whilst creating the zip.
If you flash a zip containing that firmware, but not the UK modem, it would leave the most up to date modem that you already have, so connectivity should not be lost.
When running PRF Creator, there is a tick box to include the modem or not.
I'm just thinking out loud here, as it seems to be a similar issue to the C6902 patches on C6903 firmares.
I'm no developer, so I could be wrong.
MickieH said:
That's right. You can flash NUT's recovery on locked bootloader devices, that is what it was designed for, and the reason it's called 'lockeddualrecovery' :good:
If you flash a different model numbers firmware, then the modem is likely to be wrong for your carrier. If you look at some of the rom threads you'll see a lot of the Z1 C6903 roms contain patches for the C6902 also, which I'm assuming is the C6902's correct modem.
I don't know if you could flash another models on yours, but exclude the modem, thus retaining your own.
If you want to remain on stock, then I would highly recommend downloading your own model firmware from XperiFirm, SuperSU, and lockeddualrecovery for the Z1, then run it through PRF Creator. That way you'll end up with the correct firmware (and thus modem) which would be pre-rooted, with locked dual recovery.
Which firmware do you want to have? The latest for the US TM that I can see is
1277-0679 USA T-mobile US 14.5.B.0.247
---------- Post added at 03:57 PM ---------- Previous post was at 03:34 PM ----------
I wonder if we could create a pre-rooted zip from the unbranded UK 14.6.A.1.236 by not including the modem whilst creating the zip.
If you flash a zip containing that firmware, but not the UK modem, it would leave the most up to date modem that you already have, so connectivity should not be lost.
When running PRF Creator, there is a tick box to include the modem or not.
I'm just thinking out loud here, as it seems to be a similar issue to the C6902 patches on C6903 firmares.
I'm no developer, so I could be wrong.
Click to expand...
Click to collapse
I like where you're going with this. Hopefully a dev chimes in.
I just want to be off the broken memory leak firmware the z1s c6916 got stuck with. It gets absolutely crippling at times.
Helgaiden said:
I like where you're going with this. Hopefully a dev chimes in.
I just want to be off the broken memory leak firmware the z1s c6916 got stuck with. It gets absolutely crippling at times.
Click to expand...
Click to collapse
Same here buddy, same here.
Sent from my C6916 using XDA Free mobile app
Right, well, first things first.
To install recovery, download this --> Z1 Locked Dual Recovery 2.8.21 by NUT
This is the installer which you can run from your PC.
Make sure you have unknown sources ticked in your security settings, and USB debugging turned on in Developer options for it to work.
I use that one as I haven't tried the new combined installer/flashable recovery yet, and I know this one works fine on my Z1.
You could always download and use the newer combined one from NUT's download page if you wish, it's here --> Combined installer and flashable package
It's up to you on that.
Extract the zip file, then connect your phone to your PC while it's turned on, and double click the 'install.bat' and follow the on screen prompts. You will find that it will test reboot into recovery once it's finished anyway, if I remember correctly.
Once you have installed it, I would boot into recovery. You can press volume up or down when you turn your phone on, and it vibrates, or look for the NDR Utils app in your app drawer which is great for getting into recovery.
I like to use TWRP myself.
I'd create a backup once you're in recovery then at least you won't have to worry too much if anything does go wrong later.
Make sure you have a copy of the backup on an external SD card I would recommend.
That solves that problem.
Now, the newest firmware I have on my Z1 I have used PRF Creator, and created a zip file of it without including the modem files.
If you open the zip and look inside you will see the amss modem files, which are usually in the root directory, are missing.
This pre-rooted zip is C6903_Customized UK_1276-0875_14.6.A.1.236_R6D but without the modem files.
The zip can be downloaded here --> 14.6.A.1.236 For C6916 TM - UK Unbranded firmware with NO MODEM FILES
Be warned anyone downloading this that IT DOES NOT CONTAIN ANY MODEM FILES.
If you flash this in recovery, it will leave your current modem as is.
Now I can't guarantee that this will work, but you will have a working recovery anyway, so if it does go pear shaped, you can always restore that, and you'll be good.
PRF Zips will not wipe your userdata either, so anything on your internal memory will not be wiped.
While I find this good for minor OS version jumps, like 5.02 to 5.1.1, I do not recommend it for jumping different versions, i.e Lollipop back to KitKat for example. For something like that, I would personally prefer a full wipe.
Anyway, get the recovery installed and working, and once you're happy that you know how to use it, go ahead and flash the zip and see how you go.
If you do try it, and it works, great, just check your connectivity, mobile data, 2G, 3G, LTE, to make sure it's working ok.
If it doesn't work, I'm really sorry to have wasted your time, but you should be fine with a backup ready to fix any problems. Hopefully someone more knowledgeable will be along with a fix.
Anyway, good luck :good:
MickieH said:
Right, well, first things first.
To install recovery, download this --> Z1 Locked Dual Recovery 2.8.21 by NUT
This is the installer which you can run from your PC.
Make sure you have unknown sources ticked in your security settings, and USB debugging turned on in Developer options for it to work.
I use that one as I haven't tried the new combined installer/flashable recovery yet, and I know this one works fine on my Z1.
You could always download and use the newer combined one from NUT's download page if you wish, it's here --> Combined installer and flashable package
It's up to you on that.
Extract the zip file, then connect your phone to your PC while it's turned on, and double click the 'install.bat' and follow the on screen prompts. You will find that it will test reboot into recovery once it's finished anyway, if I remember correctly.
Once you have installed it, I would boot into recovery. You can press volume up or down when you turn your phone on, and it vibrates, or look for the NDR Utils app in your app drawer which is great for getting into recovery.
I like to use TWRP myself.
I'd create a backup once you're in recovery then at least you won't have to worry too much if anything does go wrong later.
Make sure you have a copy of the backup on an external SD card I would recommend.
That solves that problem.
Now, the newest firmware I have on my Z1 I have used PRF Creator, and created a zip file of it without including the modem files.
If you open the zip and look inside you will see the amss modem files, which are usually in the root directory, are missing.
This pre-rooted zip is C6903_Customized UK_1276-0875_14.6.A.1.236_R6D but without the modem files.
The zip can be downloaded here --> 14.6.A.1.236 For C6916 TM - UK Unbranded firmware with NO MODEM FILES
Be warned anyone downloading this that IT DOES NOT CONTAIN ANY MODEM FILES.
If you flash this in recovery, it will leave your current modem as is.
Now I can't guarantee that this will work, but you will have a working recovery anyway, so if it does go pear shaped, you can always restore that, and you'll be good.
PRF Zips will not wipe your userdata either, so anything on your internal memory will not be wiped.
While I find this good for minor OS version jumps, like 5.02 to 5.1.1, I do not recommend it for jumping different versions, i.e Lollipop back to KitKat for example. For something like that, I would personally prefer a full wipe.
Anyway, get the recovery installed and working, and once you're happy that you know how to use it, go ahead and flash the zip and see how you go.
If you do try it, and it works, great, just check your connectivity, mobile data, 2G, 3G, LTE, to make sure it's working ok.
If it doesn't work, I'm really sorry to have wasted your time, but you should be fine with a backup ready to fix any problems. Hopefully someone more knowledgeable will be along with a fix.
Anyway, good luck :good:
Click to expand...
Click to collapse
i tried to do a clean install and wiped the data, dalvik cache, internal memory (zip file was on external SD), and cache then flashed the zip. After complete, I pressed "reboot." Screen went black and now the LED blinks orange. If I hold the power button, I feel the phone vibrate but nothing happens. Damnit.
edit: got fastboot and flashmode working again and I'm flashing stock 4.4.4. Maybe I'll try this method again to make sure I didn't mess something up along the way.
edit 2: after restoring stock 4.4.4 , re-rooting, re-doing the nuts recovery, then reflashing the the above zip...same problem. No hope for us on the c6916. I'll go back to 4.4.4 that ran better than 5.0.2 and just deal with the SD card issues in KK. Maybe i'll root it to fix that though..
So I just found out that Android auto still require lollipop or better. DAMNIT. Just when I'm happy by moving back to 4.4.4 i find out that to use a feature of the vehicle I'm getting soon, I need to go back to the broken ass 5.0.2 lollipop firmware us Z1s owners are stuck with.
There has to be a solution to get us to 5.1. There just has to be. Any ideas?
What would happen if we tried creating a 5.1.1 pre-rooted zip for the tmobile z1s without the kernel and without the modem. I assume 5.1.1 would just not boot with the outdated kernel for 5.0.2, but it might still be worth trying, right?
Anybody get it yet? Supposedly went official yesterday. About 300MB.
I unlocked your mum's bootloader.
It just arrived, and it was about 300MB. IT rebooted into TWRP, which just sat there. I rebooted, and then Andorid complained that the update didn't work. Well, duh!
That said, now I would like to know what I should have done or should do in the future. Any thoughts?
Mine just arrived
What's new?
Just found a story about it here - it is indeed the July update:
http://www.tmonews.com/2016/08/t-mobile-galaxy-note-4-note-edge-july-security-update/
Links in that article will eventually point you to here, where the update can be downloaded manually and installed via Samsung Smart Switch.
https://support.t-mobile.com/docs/DOC-16486#update_download
Since I am rooted I am actually not sure what to do, and would appreciate some advice.
300 mb is a big update. If you are rooted you will need to flash the new firmware in Odin. But you may want to hold off. I am note sure it adds any new features and will probably make your device incompatible with any ROMs that are currently available.
ShrekOpher said:
300 mb is a big update. If you are rooted you will need to flash the new firmware in Odin. But you may want to hold off. I am note sure it adds any new features and will probably make your device incompatible with any ROMs that are currently available.
Click to expand...
Click to collapse
Thanks - sound advice.
So, where should I be looking on my Note 4 for the 300 MB download that happened earlier this morning, so I can delete it or copy/move it off for later?
I just got it but waiting to see if there are any bugs or negative effects. I'm not rooted so there's no way to go back.
Sent from my SM-N910T3 using Tapatalk
Still looking and haven't found any clues for changelog, not even security update. Anybody?
I unlocked your mum's bootloader.
Yep...trying to figure out how to avoid the update too.
I'm stick rooted with XPosed, Beastmode kernel, and a few other mods.
I just did the update, and I can confirm that TWRP, root, and xposed all work.
I don't know about compatibility with custom roms though.
ninjanick999 said:
I just did the update, and I can confirm that TWRP, root, and xposed all work.
I don't know about compatibility with custom toms though.
Click to expand...
Click to collapse
OK, so how did you install it?
To shut the System Update tool up, I had to freeze it in Titanium Backup.
wernst said:
OK, so how did you install it?
To shut the System Update tool up, I had to freeze it in Titanium Backup.
Click to expand...
Click to collapse
You can flash it with odin. The file is the all in one home odin file The file is floading around somewhere....Might look in Overdrives OP That might be where i saw it...
KennyLG123 said:
You can flash it with odin. The file is the all in one home odin file The file is floading around somewhere....Might look in Overdrives OP That might be where i saw it...
Click to expand...
Click to collapse
Yeah, if you can't find the update. You can just install the latest firmware you can find with odin, then update from settings.
Hi Folks,
I have no idea what "update from settings" means. Also, no idea where to start looking for the update - heck, I don't even know what to Google to find it. Thoughts?
wernst said:
Hi Folks,
I have no idea what "update from settings" means. Also, no idea where to start looking for the update - heck, I don't even know what to Google to find it. Thoughts?
Click to expand...
Click to collapse
From your device click settings look for about device click then at the top you will see (download updates manually) If you are rooted or removed any system apps dont go that route, the update will fail.. You then would just need the update file to flash with odin.. Might look in overdrives op.
What is overdrives op?
wernst said:
What is overdrives op?
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...-maximum-ovrdrive-6-0-1-mm-beta-4-13-t3358326 Here.. you will see the link it a all in one (home) odin file just flash in ap or pda slot depending on which odin you use..
I believe this is the AFH Linky for the new firmware also fwiw: https://www.androidfilehost.com/?fid=24588212152306227
So just to be clear, Overdrive is a MM-based T-Mobile ROM, basically just debloated and with some minor tweaks.
As a convenience, he has linked to "N910T Stock Odin Full EPG2 Firmware File," which we can flash using TWRP onto an otherwise stock+rooted MM 6.0.1.
I got this right?
wernst said:
So just to be clear, Overdrive is a MM-based T-Mobile ROM, basically just debloated and with some minor tweaks.
As a convenience, he has linked to "N910T Stock Odin Full EPG2 Firmware File," which we can flash using TWRP onto an otherwise stock+rooted MM 6.0.1.
I got this right?
Click to expand...
Click to collapse
The PG2 file he has a link to is stock. That thread is for his pe3 custom though. I haven't made my rounds through note 4 thread yet. I maintain another android site and all the devices in my sig are active. I'm never on the same thread everyday....lol
---------- Post added at 02:35 PM ---------- Previous post was at 02:31 PM ----------
glensta said:
I believe this is the AFH Linky for the new firmware also fwiw: https://www.androidfilehost.com/?fid=24588212152306227
Click to expand...
Click to collapse
I'm starting to see more links pop up now. Thanks I 'm not even going to try this one out i'm staying on pe3 for awhile...
I woke up and my phone had a message saying it was ready to update to N910TUVS2EQE2. Has anybody updated and rooted this fw yet?
I also recieved the update, I won't update for that reason. But the notification is annoying.
It's been forever since I had rooted my phone, finally updated, then had this update and installed it while it was still unrooted. But now I want to root the phone, so no one has tried it yet? Only thing I've noticed with this version is it seemed to have tried to keep a connection via wifi instead of bluetooth to my watch, which lead both of them to have some serious battery drain.
Now that I've set it back to bluetooth, let's see how well it does. The watch (Gear S2 Classic 3G) had to be charged twice in one day, it was terrible.
Unless T-Mobile has suddenly reversed a long-standing policy and locked the bootloader on a previously unlocked device (something I have not ever heard of for any device), you can still flash TWRP recovery from Odin and then flash SuperSU from recovery, which does not modify the system partition. This should just be a minor security update for Marshmallow and not an update to Nougat, which would have much bigger compatibility consequences but which should still be rootable by the above method.
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Would be great if we could get a nougat release.
ElMadre said:
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Click to expand...
Click to collapse
So let me see if I understood what you said, you installed the EQE2 and flashed TWRP, rooted it, then installed another ROM over it?
It is annoying as F!!!!! Every 6 hrs or so it nags the F!!!! outa you!
m4f1050 said:
So let me see if I understood what you said, you installed the EQE2 and flashed TWRP, rooted it, then installed another ROM over it?
Click to expand...
Click to collapse
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
ElMadre said:
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
Click to expand...
Click to collapse
Ok thanks.
t-mobile SM-910T
ElMadre said:
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
Click to expand...
Click to collapse
where could I get the QE2 file?
Lsanc1170 said:
where could I get the QE2 file?
Click to expand...
Click to collapse
Not going to say what others say all the time, but I searched for it. (I Googled it.) If you want to easily root it and already have TWRP recovery, go to this post:
https://forum.xda-developers.com/note-4-tmobile/development/roms-10-29-2014-t2922618
If you want the ODIN version, go to this link:
https://samsunggalaxyrom.com/2017/0...sm-n910t-n910tuvs2eqe2-marshmallow-6-0-1.html
ElMadre said:
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Click to expand...
Click to collapse
what is Smores Rom? what MM base does it use and what are it's features?
slaapliedje said:
It's been forever since I had rooted my phone, finally updated, then had this update and installed it while it was still unrooted. But now I want to root the phone, so no one has tried it yet? Only thing I've noticed with this version is it seemed to have tried to keep a connection via wifi instead of bluetooth to my watch, which lead both of them to have some serious battery drain.
Now that I've set it back to bluetooth, let's see how well it does. The watch (Gear S2 Classic 3G) had to be charged twice in one day, it was terrible.
Click to expand...
Click to collapse
The Gear watch battery drain problem likely isn't related to the phone update.
We've had the same problem with the Gear S3. After weeks of running fine, my S3 would do the same thing. We've been having to hard reset the watch to fix the problem.
anyone getting better or worse signal with the QE2? .... feedback?
I've looked everywhere in the threads and can't find an answer, hope you all can help.
N910T, Android 6.0.1, N910TUVS2EQE2. Everything I try and flash anything I get E: Footer Is Wrong and E: Signature verification failed. Tried Odin. Tried ADB. Tried to flash from ZIP. I unlocked the phone with the code from TMO but can't get past the loader to flash anything. Happy to provide futher details but any help would be very appreciated.
jnyfive said:
I've looked everywhere in the threads and can't find an answer, hope you all can help.
N910T, Android 6.0.1, N910TUVS2EQE2. Everything I try and flash anything I get E: Footer Is Wrong and E: Signature verification failed. Tried Odin. Tried ADB. Tried to flash from ZIP. I unlocked the phone with the code from TMO but can't get past the loader to flash anything. Happy to provide futher details but any help would be very appreciated.
Click to expand...
Click to collapse
It was the USB cable. Tried different cable and port. Tada.
f4phantomii said:
The Gear watch battery drain problem likely isn't related to the phone update.
We've had the same problem with the Gear S3. After weeks of running fine, my S3 would do the same thing. We've been having to hard reset the watch to fix the problem.
Click to expand...
Click to collapse
That did seem to help, and oddly enough one of the watch faces I'd bought that wouldn't install now installs and works fine.
jnyfive said:
It was the USB cable. Tried different cable and port. Tada.
Click to expand...
Click to collapse
Follow up. I'm able to flash TWRP. Made a backup but when I try to flash a new ROM I get error 6, error 7, or zip file errors in TWRP. When I try to flash ROM in Odin it crashes. Ideas? Is the build the issue?
Sent from my SM-G955U using Tapatalk
jnyfive said:
Follow up. I'm able to flash TWRP. Made a backup but when I try to flash a new ROM I get error 6, error 7, or zip file errors in TWRP. When I try to flash ROM in Odin it crashes. Ideas? Is the build the issue?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
what file and file name are you trying to flash and what model phone do u have and what current loaded firmware do you have?
XeoNoX said:
what file and file name are you trying to flash and what model phone do u have and what current loaded firmware do you have?
Click to expand...
Click to collapse
TMO Note 4, baseband version N910TUVS2EQE2, tried lineage-14.1-20170725-UNOFFICIAL-trltetmo.zip and RR-N-v5.8.2-20170303-trltexx-Official.zip
Sent from my SM-G955U using Tapatalk