Related
This is a [WARNING] Don't flash any other thing after you update Tmobile S5 to 5.1.1!
I have just flashed 5.1.1 and tried to flash CF-AUTOROOT / TWRP / CWM / ANY ROOT OR RECOVERY and I stucked at bootloop while the phone kept on ringing 4times at the T-mobile boot screen.
i think Samsung had changed something to prevent from install recovery or root on S5 in 5.1.1.
We should wait for someone to make 5.1.1 root.
The good news: You are able to downgrade from 5.1.1 to 5.0 or even 4.4 just by flashing previous firmwares using ODIN.
Without any problem. Full service, imei, SV, .... everything's fine.
Try wiping your caches in recovery. Same thing happened to me for 5.0
Sent from my SM-G900T using XDA Free mobile app
thienbrand said:
This is a [WARNING] Don't flash any other thing after you update Tmobile S5 to 5.1.1!
I have just flashed 5.1.1 and tried to flash CF-AUTOROOT / TWRP / CWM / ANY ROOT OR RECOVERY and I stucked at bootloop while the phone kept on ringing 4times at the T-mobile boot screen.
i think Samsung had changed something to prevent from install recovery or root on S5 in 5.1.1.
We should wait for someone to make 5.1.1 root.
Click to expand...
Click to collapse
Try doing what Kevin said. Otherwise reflash the update in Odin, download here or mega mirror.
After I installed Recovery or root, I do full wipe.
But remain the same.
Sent from my SM-G900T using XDA Free mobile app
Kevin or lingo, are you saying it works ok for you?
Sent from my SM-G900F using Tapatalk
A better question, are we able to downgrade after installation of this version?
I seen a screenshot of the S6 update screen and it showed that a downgrade would not be possible.
thienbrand said:
After I installed Recovery or root, I do full wipe.
But remain the same.
Click to expand...
Click to collapse
Try downloading the rom from the link I posted and flash it in odin, if you wan't to get out of bootloop.
pnut22r said:
Kevin or lingo, are you saying it works ok for you?
Click to expand...
Click to collapse
I haven't tried it, my S5 is 900F international. And I don't know the procedure for flashing T-Mobile roms on the 900F.
Maybe we can flash the rom but I'm pretty sure the bootloader and kernel is a no go.
The good news: You are able to downgrade from 5.1.1 to 5.0 or even 4.4 just by flashing previous firmwares using ODIN.
Without any problem. Full service, imei, SV, .... everything's fine.
thienbrand said:
The good news: You are able to downgrade from 5.1.1 to 5.0 or even 4.4 just by flashing previous firmwares using ODIN.
Without any problem. Full service, imei, SV, .... everything's fine.
Click to expand...
Click to collapse
This is good news, thanks!
thienbrand said:
This is a [WARNING] Don't flash any other thing after you update Tmobile S5 to 5.1.1!
I have just flashed 5.1.1 and tried to flash CF-AUTOROOT / TWRP / CWM / ANY ROOT OR RECOVERY and I stucked at bootloop while the phone kept on ringing 4times at the T-mobile boot screen.
i think Samsung had changed something to prevent from install recovery or root on S5 in 5.1.1.
We should wait for someone to make 5.1.1 root.
The good news: You are able to downgrade from 5.1.1 to 5.0 or even 4.4 just by flashing previous firmwares using ODIN.
Without any problem. Full service, imei, SV, .... everything's fine.
Click to expand...
Click to collapse
Try this, run cf auto root, let it reboot, yank the battery, reboot to dl mode and flash ONLY the stock recovery from the update and reboot
thienbrand said:
The good news: You are able to downgrade from 5.1.1 to 5.0 or even 4.4 just by flashing previous firmwares using ODIN.
Without any problem. Full service, imei, SV, .... everything's fine.
Click to expand...
Click to collapse
Add this to your op so people don't freak out lol
I'm sure we'll get a working root method for 5.1.1, iirc I read the S6 running 5.1.1 was easily rooted, even without tripping KNOX
Can anyone post some screenshot of this release? Thanks in andvance!
nfs11 said:
Can anyone post some screenshot of this release? Thanks in andvance!
Click to expand...
Click to collapse
Looks the same as 5.0
ShinySide said:
Looks the same as 5.0
Click to expand...
Click to collapse
Theme support?
ShinySide said:
Try this, run cf auto root, let it reboot, yank the battery, reboot to dl mode and flash ONLY the stock recovery from the update and reboot
Click to expand...
Click to collapse
We don't have the seperate recovery file.
nfs11 said:
Theme support?
Click to expand...
Click to collapse
No theme support. It's still a S6 exclusive.
thienbrand said:
We don't have the seperate recovery file.
Click to expand...
Click to collapse
It's in the tar. I tried it few minutes ago, still wouldn't boot
m_malyszko said:
No theme support. It's still a S6 exclusive.
Click to expand...
Click to collapse
I guess that will be exclusive for a limited time. I hope.
m_malyszko said:
No theme support. It's still a S6 exclusive.
Click to expand...
Click to collapse
That's disappointing, my excitement for 5.1.1 has just disappeared.
Hey Xda,
Today I present you a guide on how to
REVERT TO STOCK OR REFLASH firmware on the Asus Zenfone 2 Laser ZE5550KL.
This guide is applicable to both types of users ie who use TWRP and who don't use TWRP.After following this guide your phone will also be unrooted.
For TWRP Users
Here I give you links to two firmwares which you can directly flash via TWRP recovery.
Version:1.13.40.496
Link
Version:1.17.40.1234
Link
For Stock/Non-TWRP Users
The procedure is a little long here ==>
1. Download the official firmware from asus website.
2. Copy the firmware to the Micro-SD and rename the file (firmware) by one more(version).This renaming should be according to your current firmware version.If you have 17.something firmware and you download 16.something firmware then rename the 16.x.x file to some thing like 17.x.x For eg. if you have 1.17.40.763 then rename 16.x.x file to 1.17.40.764.
3. Reboot the phone.Android should automatically find the update file and offer to automatically update the software.Do it !!
4. Go to stock Recovery and wipe cache , dalvik cache and data.
5. Reboot device. Your phone will now be unrooted(if it was rooted before).
DONT FORGET TO PRESS THE THANKS BUTTON IF I HELPED YOU.
CREDITS
CREDITS
@abhishekr700
@LuK1337
@abhishekr700: You could atleast credit me for TWRP method. The zips you uploaded are obviously made using my guide.
LuK1337 said:
@abhishekr700: You could atleast credit me for TWRP method. The zips you uploaded are obviously made using my guide.
Click to expand...
Click to collapse
Yes ofcourse,
Would you provide me links to your guide? @LuK1337
abhishekr700 said:
Yes ofcourse,
Would you provide me links to your guide? @LuK1337
Click to expand...
Click to collapse
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482
is it applicable for asus_z00LD
kris12344 said:
is it applicable for asus_z00LD
Click to expand...
Click to collapse
Yes
Sent from my C2305 using Tapatalk
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Lololololololo
tmjm28 said:
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Click to expand...
Click to collapse
Lemme guess. You use that stupid custom kernel? That'd explain why About Phone says it's Z00LD.
Sent from my ASUS_Z00TD using XDA Labs
Does this work with zenfone500kl
LuK1337 said:
Lemme guess. You use that stupid custom kernel? That'd explain why About Phone says it's Z00LD.
Sent from my ASUS_Z00TD using XDA Labs
Click to expand...
Click to collapse
Well, I'll be damned. I was doing so much flashing at the time that I didn't put it together. Oh well. I've been back on the stock CM kernel for days and everything finally works as it should again.
Will flashing this stock ROM on TWRP replace my current TWRP recovery to stock recovery on boot?
Sent from my ASUS_Z00LD using Tapatalk
tmjm28 said:
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Click to expand...
Click to collapse
This issue has been fixed on V4.0of kernel .
Hope you like it.
HampTheToker said:
Lololololololo
Click to expand...
Click to collapse
This issue has been fixed on V4.0 .
Hope you like it.
mohamedelkholy said:
Does this work with zenfone500kl
Click to expand...
Click to collapse
Yes
HampTheToker said:
Well, I'll be damned. I was doing so much flashing at the time that I didn't put it together. Oh well. I've been back on the stock CM kernel for days and everything finally works as it should again.
Click to expand...
Click to collapse
This issue has been fixed on V4.0 .
Hope you like it.
kunalchitara said:
Will flashing this stock ROM on TWRP replace my current TWRP recovery to stock recovery on boot?
Nope !
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
Hi
May I know if the above worked for downgrading from Marshmallow 6.0.1 back to Lollipop 5.x.x ??
Thanks
Man, so how should I do if I wanna flash back to LP and upgrade to MM?
The TWRP won't be replace to stock you said above.
I'm now using TWRP and CM13
- Thanks!
jasonshao88 said:
Man, so how should I do if I wanna flash back to LP and upgrade to MM?
The TWRP won't be replace to stock you said above.
I'm now using TWRP and CM13 and stock LP firmware.
- Thanks!
Click to expand...
Click to collapse
How can you use cm13 and stock lp together?
This is for reverting to stock nothing else.
Sent from my C2305 using Tapatalk
.
will get updates again if i flash this? tnx
My friend I installed TWRP and accidently deleted all android system. . . Now only appears the TWRP .... How to do reinstall android 5.0 system ??
hi
I have rooted my ze550kl and unrooted it through su iam not able to install ota updates i have twrp i want removery twrp and install stock rom to get ota updates but i cant find recovery img for my firmware
Can u please provied recovery.img,boot.img,bootdriod.img files for ww.1.17.40.1234 firmware for my asus zenfone2 laser ze550kl
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
First flash this file and then Rom. That's right?? Or its other way around
karan khara said:
First flash this file and then Rom. That's right?? Or its other way around
Click to expand...
Click to collapse
If u have dm verity error on boot. Just flash it..
Wouldn't this procedure downgrade some performance on the device?
Giocarro said:
Wouldn't this procedure downgrade some performance on the device?
Click to expand...
Click to collapse
No..
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Nitesh13 said:
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Click to expand...
Click to collapse
Yes u can..
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
cool.boy said:
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
Click to expand...
Click to collapse
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
I have no DM verity error and I have cb9 firmware and rooted
Sent from my OnePlus 3 using XDA Labs
Why would you want to flash old firmware and modem, not made for this ROM, just to get rid of a pointless message?
Especially when there are other methods to fix this so called issue ...
Sent from my OnePlus 3 using Tapatalk
puschkin said:
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
Click to expand...
Click to collapse
Yes..
snippem said:
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
Click to expand...
Click to collapse
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
cesar.mk4 said:
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
Click to expand...
Click to collapse
dlhxr said:
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
Click to expand...
Click to collapse
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
cesar.mk4 said:
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
Click to expand...
Click to collapse
I never had that till now only after flash does not reboot.
In my opinion it is more a twrp incompatibility that will be resolved when N sources are out by oneplus
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
Don't even need to wait, just press the power button to skip it (same applies to first bootloader unlocked message).
Sent from my OnePlus 3 using Tapatalk
it's easily avoidable (but the phone will be decrypted)
after flashing ob9 successfully and booting to system, reboot to TWRP (.28) and wipe convert data to f2fs then wipe it, then wipe internal storage (back up your data to your pc 1st)...and that's it, if you want root, reboot back to TWRP and flash root, then roboot to system, dmverity will be gone, and the phone decrypted,
(this will work if you started with a clean ob9 install like sideloading, and you ended with a full stock ob9)
THIS IS FOR SAMSUNG GALAXY J7 METRO PCS VERSION. DO NOT FLASH ON OTHER VARIANTS.
If you have messed up your system while trying to root and need J700T1UVU3AQC3 firmware to recover, or if you just need to upgrade to the latest firmware, here is the official unmodified Rom:
Download link:
https://mega.nz/#!ltcgwYLZ!R0n3FyaDUCtY8yiMrppFpbxNaSHnjiSUZSMQiU_o-kk
1- The firmware is on Mega servers. Please use a PC to download. If you have to use your mobile device to download, use the Mega app or set your browser to "desktop".
2- The firmware files are zipped. They should be unzipped and flashed via Odin.
3- This version upgrades the bootloader version to 3 and therefore downgrading to previous versions becomes impossible. So if you are happy with your current firmware and you think you may change your mind after the upgrade, stay away from this.
3- Rooting this firmware is possible through flashing TWRP via Odin and then superSU via TWRP. As I am sure you are well aware, that process will trip your Knox flag and renders your warranty void.
4- As usual, I share this with you AS IS and I have no responsibility if it breaks your phone. USE IT AT YOUR OWN RISK.
twrp for j7
which version of twrp works
Drsmit3 said:
which version of twrp works
Click to expand...
Click to collapse
This is not for twrp. Please read the OP:
Quote:
2- The firmware files are zipped. They should be unzipped and flashed via Odin.
3- This version upgrades the bootloader version to 3 and therefore downgrading to previous versions becomes impossible.
I was having network problems..calls kept disconnecting and phone would freeze. I restored my twrp backup with no issues.
need root for this j700t or t1 qc3 , please help tnx
mr64fixit said:
need root for this j700t or t1 qc3 , please help tnx
Click to expand...
Click to collapse
Just download SuperSU, newest 2.82. flash via recovery, there u are rooted.
Are the TMo and Metro devices interchangeable yet? In other words a Tmo sim in a Metropcs phone and vice versa?
TabascoTX said:
Are the TMo and Metro devices interchangeable yet? In other words a Tmo sim in a Metropcs phone and vice versa?
Click to expand...
Click to collapse
Think u have to sim unlock it first.
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
Don't flash this firmware on a t mobile phone though.it will kill your modem and efs
Ok, not to sound like a noob,(I don't deal with Samsung's usually). What are ef's again?
TabascoTX said:
Ok, not to sound like a noob,(I don't deal with Samsung's usually). What are ef's again?
Click to expand...
Click to collapse
It's your encrypting file system.its where your imei is stored and other super important stuff and unique to your specific phone's serial number alone. And tethered to your carriers signal
fullofhell said:
It's your encrypting file system.its where your imei is stored and other super important stuff and unique to your specific phone's serial number alone. And tethered to your carriers signal
Click to expand...
Click to collapse
The EFS stuff really scares me when it comes to flashing. With that said. Where can i download the latest rom for metropcs. Sammobile only appears to have T-Mobile from the last time i checked. Does not hurt to have it at hand just in case.
Sent from my SM-J700T1 using Tapatalk
DroidJP said:
The EFS stuff really scares me when it comes to flashing. With that said. Where can i download the latest rom for metropcs. Sammobile only appears to have T-Mobile from the last time i checked. Does not hurt to have it at hand just in case.
Click to expand...
Click to collapse
Download updato app on play store. U can find all firmwares..or if u have any old firmwares laying around flash it and then take an OTA update then fomat and make a backup of it
fullofhell said:
Download updato app on play store. U can find all firmwares..or if u have any old firmwares laying around flash it and then take an OTA update then fomat and make a backup of it
Click to expand...
Click to collapse
No firmware at hand but updato, wow it identified my phone and found my firmware in matter of seconds. And to be sure. TMK is Metro correct?
Sent from my SM-J700T1 using Tapatalk
DroidJP said:
No firmware at hand but updato, wow it identified my phone and found my firmware in matter of seconds. And to be sure. TMK is Metro correct?
Click to expand...
Click to collapse
I'm not sure on that man look up some other firmwares for metro just to kinda compare..I don't want to steer u wrong. But updato saved me so much stress and time.
Yup, it's the correct one lol.
Sent from my SM-J700T1 using Tapatalk
Hey guys. Are any of you experiencing random reboots on the latest firmware? My phone randomly reboots for no reason. It has done this several times and the 2 times i can remember was 1. Phone rebooted when i was connecting to wifi. 2. It also did a reboot while in a middle of a game. What gives?
Sent from my SM-J700T1 using Tapatalk
The metro qc3 works nice in the T-Mobile and does not harm it any way, I did mine , no problem
Rooting is a problem with this security 3 since no TWRP is working with this version yet. But there is a eng root boot.img out which does the job, they charge 50 USD for this file.
mr64fixit said:
The metro qc3 works nice in the T-Mobile and does not harm it any way, I did mine , no problem
Rooting is a problem with this security 3 since no TWRP is working with this version yet. But there is a eng root boot.img out which does the job, they charge 50 USD for this file.
Click to expand...
Click to collapse
I have t mobile.i flashed this firmware once with flash fire, and then once with odin.lost my efs both times. I had someone send me the t mobile one and it was fine, I flashed the same twrp and it was like normal. I don't know if someone uploaded a different version of twrp or what, but the ones that have been on xda for the past 8 months do the job fine. I switch between the twrp for the j7, then the j700T specific twrp. I don't run stock, but all the roms I run with this twrp and all 3 kernels I use in development I also root through these recoveries.
@ Droid, what ROM are you running?
My Tmobile j700t qc3 had no issues when using j700t1 qc3 all was good. But twrp not working with qc3. Maybe yours was different firmware. But looking at other Samsung Tmobile and Metro pcs I never had an issue cross flashing them. Maybe you used not compatible firmware when you Lost efs , usually that happens when using lower bit or wrong modem file.
Sent from my SM-N930T using Tapatalk
mr_one said:
My Tmobile j700t qc3 had no issues when using j700t1 qc3 all was good. But twrp not working with qc3. Maybe yours was different firmware. But looking at other Samsung Tmobile and Metro pcs I never had an issue cross flashing them. Maybe you used not compatible firmware when you Lost efs , usually that happens when using lower bit or wrong modem file.
Click to expand...
Click to collapse
I used this very posts files...it's weird cuz the t mobile file is larger by a bit.maybe it is all weir
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