Database Users

[Q] hltetmo vs hltecan. Also question about bootloaders.

What is the difference between devices hltetmo and hltecan? I have a hltecan. Will we need CyanogenMod compiled for hltecan? I notice that recoveries have different versions for both devices. Also I am wondering about downgrading for 4.4 (when it comes) to 4.3. Is there a surefire way to upgrade and downgrade between 4.4 TW 4.4 CM and 4.3TW? I would not mind voiding my Knox counter. Just worried about being stuck or getting a brick for another 21 months on contract :silly:

jtl999 said:
What is the difference between devices hltetmo and hltecan? I have a hltecan. Will we need CyanogenMod compiled for hltecan? I notice that recoveries have different versions for both devices. Also I am wondering about downgrading for 4.4 (when it comes) to 4.3. Is there a surefire way to upgrade and downgrade between 4.4 TW 4.4 CM and 4.3TW? I would not mind voiding my Knox counter. Just worried about being stuck or getting a brick for another 21 months on contract :silly:
Click to expand...
Click to collapse
you cant downgrade if you want cm you have to stay on 4.3 for now

jaythenut said:
you cant downgrade if you want cm you have to stay on 4.3 for now
Click to expand...
Click to collapse
Sigh. I would do anything to be able to upgrade and downgrade between versions. Even Knox counter. If anyone finds something let me know

jtl999 said:
Sigh. I would do anything to be able to upgrade and downgrade between versions. Even Knox counter. If anyone finds something let me know
Click to expand...
Click to collapse
I played around a bit earlier... The only firmware you can upgrade to 4.4.2 and downgrade back to 4.3 is the mexican telco one for the n900w8, however I had some issues but will play some more tomorrow when I get time. As for KNOX, it's just one of them things we have to live with I'm afraid..
EDIT: I'm gonna mess with the bootloader and see, doubt it can be matched/mixed to work with the N9005 but what's the harm in trying.

radicalisto said:
I played around a bit earlier... The only firmware you can upgrade to 4.4.2 and downgrade back is the mexican telco one for the n900w8, however I had some issues but will play some more tomorrow when I get time. As for KNOX, it's just one of them things we have to live with I'm afraid..
Click to expand...
Click to collapse
Please try with Telus firmware please. Currently on MJ1

radicalisto said:
I played around a bit earlier... The only firmware you can upgrade to 4.4.2 and downgrade back to 4.3 is the mexican telco one for the n900w8, however I had some issues but will play some more tomorrow when I get time. As for KNOX, it's just one of them things we have to live with I'm afraid..
EDIT: I'm gonna mess with the bootloader and see, doubt it can be matched/mixed to work with the N9005 but what's the harm in trying.
Click to expand...
Click to collapse
The harm in trying is a hardbrick.

Well yes there is that, however I am not overly fussed about it, as most HB's can be revived. I am aware of all the risks, so will be my fault 100% if I brick myself.

I upgraded my note 3 yesterday to android 4.4 with cm 11, using the probam rom.
I noticed that it lacked the s pen features, so i downgraded back to stock rom.
Download a stock rom and flash it trough twrp
Sent from the Android beast: Galaxy Note 3

Rajito said:
I upgraded my note 3 yesterday to android 4.4 with cm 11, using the probam rom.
I noticed that it lacked the s pen features, so i downgraded back to stock rom.
Download a stock rom and flash it trough twrp
Sent from the Android beast: Galaxy Note 3
Click to expand...
Click to collapse
Flash a tar.md5 through twrp? What version of the stock rom?
Did you have the new bootloader?

Rajito said:
I upgraded my note 3 yesterday to android 4.4 with cm 11, using the probam rom.
I noticed that it lacked the s pen features, so i downgraded back to stock rom.
Download a stock rom and flash it trough twrp
Sent from the Android beast: Galaxy Note 3
Click to expand...
Click to collapse
CM is based on MJ/MK Bootloader. You could run Android 9.6 and it'd make no difference. It's all about the bootloader

radicalisto said:
CM is based on MJ/MK Bootloader. You could run Android 9.6 and it'd make no difference. It's all about the bootloader
Click to expand...
Click to collapse
Sorry. Can't understand exactly. What exactly means what versions you can run with a new bootloader?

MJ7 is the bootloader that powers CM currently. You need a bootloader to be able to boot into the operating system. Like a key into the phone.
If you upgrade your bootloader to a newer version aka NA6 it locks the phone. Therefore anything that runs lower than NA6 aka MJ7 won't work.
Think of it like, you broke your door, you got a new door and tried to use the old key. It no long works.
Sent from my SM-N9005 using XDA Premium 4 mobile app

radicalisto said:
MJ7 is the bootloader that powers CM currently. You need a bootloader to be able to boot into the operating system. Like a key into the phone.
If you upgrade your bootloader to a newer version aka NA6 it locks the phone. Therefore anything that runs lower than NA6 aka MJ7 won't work.
Think of it like, you broke your door, you got a new door and tried to use the old key. It no long works.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I know how bootloaders work. Isn't there a way to omit bootloaders from Odin tar.md5 updates? Once I/Someone figures that out I'm golden staying with my old bootloader. Currently on MJ1.

jaythenut said:
you cant downgrade if you want cm you have to stay on 4.3 for now
Click to expand...
Click to collapse
hi, can you elaborate?
i always thought samsung doesn't let you downgrade to an older bootloader. but if you install CM (not samsung official updates) the bootloader doesn't get updated so you can downgrade in the future.
unless you upgrade to 4.4.2 official samsung ROM and update the bootloader, then you'll never be able to downgrade again?

jtl999 said:
Flash a tar.md5 through twrp? What version of the stock rom?
Did you have the new bootloader?
Click to expand...
Click to collapse
No, if you want to try out kitkat i recommend you to use a cyanogenmod based 4.4 like probam, it doesn't update your bootloader and you can just downgrade back to jellybean
Sent from the Android beast: Galaxy Note 3

S5 SafeStrap ROM Help...Can I use CM13?

Hi. Using a CID11 device w/ KINGROOT/SAFESTRAP
I know the bootloader is locked and all, but will I still be able to use CyanogenMod 13 ?
http://download.cyanogenmod.org/?device=kltevzw
I know this is a noob question as the S5 is pretty locked down now 'geocold' is helping the enemy, but is it still at all possible to use CM13 with this safe strap option on a CID11 device.
also is there any other ROMs I could use that are similar with any kind of custom kernel that helps preserve battery life like in the past or is that a no now since the bootloader is locked.
lastly will I loose root if I can do any of the above.
....
very new to the S5 please bare with me lol

meistfx said:
Hi. Using a CID11 device w/ KINGROOT/SAFESTRAP
I know the bootloader is locked and all, but will I still be able to use CyanogenMod 13 ?
http://download.cyanogenmod.org/?device=kltevzw
I know this is a noob question as the S5 is pretty locked down now 'geocold' is helping the enemy, but is it still at all possible to use CM13 with this safe strap option on a CID11 device.
also is there any other ROMs I could use that are similar with any kind of custom kernel that helps preserve battery life like in the past or is that a no now since the bootloader is locked.
lastly will I loose root if I can do any of the above.
....
very new to the S5 please bare with me lol
Click to expand...
Click to collapse
There is a thread on xda about flashing mm custom roms on bootloader locked s5 verizon so try that here is the thread
http://forum.xda-developers.com/ver...flash-custom-6-0-1-roms-locked-t3393943/page1
Sent from my SM-G900V using Tapatalk

[email protected] said:
There is a thread on xda about flashing mm custom roms on bootloader locked s5 verizon so try that here is the thread
http://forum.xda-developers.com/ver...flash-custom-6-0-1-roms-locked-t3393943/page1
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Hey thanks! I'm on 5.0 OK3 will this require me to prepare anything or just ez install threw safestrap touchwiz ? also will I loose my apks/data or do I need to do a back up of such things.

meistfx said:
Hey thanks! I'm on 5.0 OK3 will this require me to prepare anything or just ez install threw safestrap touchwiz ? also will I loose my apks/data or do I need to do a back up of such things.
Click to expand...
Click to collapse
You shouldn't lose any data but a backup is always wise
According to the thread you have to be on rooted PB1 firmware and use safestrap
The guide is specific so follow his guide exactly
I would do a back up in Samsung Smart Switch or Samsung kies 3 before you use or use safestrap backup whatever you prefer
Sent from my SM-G900V using Tapatalk

[email protected] said:
You shouldn't lose any data but a backup is always wise
According to the thread you have to be on rooted PB1 firmware and use safestrap
The guide is specific so follow his guide exactly
I would do a back up in Samsung Smart Switch or Samsung kies 3 before you use or use safestrap backup whatever you prefer
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Oh ok, yeah since I'm on OK3 will I need to do the whole KingRoot method again? or if I flash to PB1 from ODIN will I still keep root/safestrap/bb not sure how this all works just started using the S5 today.
Also once that is all done, and I'm on a rooted PB1 ... I'll be able to flash threw safestrap to a MM 6.0.1 ROM ? but when I do this wont I loose root? and I thought root not able to be obtained on MM 6.0.1 with CID11 devices? this is where it gets to be confusing for me, sorry for all the questions

meistfx said:
Oh ok, yeah since I'm on OK3 will I need to do the whole KingRoot method again? or if I flash to PB1 from ODIN will I still keep root/safestrap/bb not sure how this all works just started using the S5 today.
Also once that is all done, and I'm on a rooted PB1 ... I'll be able to flash threw safestrap to a MM 6.0.1 ROM ? but when I do this wont I loose root? and I thought root not able to be obtained on MM 6.0.1 with CID11 devices? this is where it gets to be confusing for me, sorry for all the questions
Click to expand...
Click to collapse
You will lose root if you go up to cm13 using this method
If you need root then the linked method above may not be for you
Sent from my SM-G900V using Tapatalk

[email protected] said:
You will lose root if you go up to cm13 using this method
If you need root then the linked method above may not be for you
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Yes I can not use android with out root lol, but thanks for showing me all this anyways its progress I guess, not sure if this handset was worth the money now knowing all this, but I'll stick with it.
I see no point in even bothering to run CM13 or any custom rom really with out the use of root. ehhhh anyway. Backing up my apk/data using a snazzy lil app called MyBackup Pro. for the migration.
Thanks for the help. Looks like I'll be staying on the 5.0 OK3 rom then since at least I have it rooted, and some kind of recovery even tho the whole safestrap touchwiz thing is not pleasing its better than nothing.

Downgrade required or not?

I am Official Nougat. Currently locked bootloader and stock. im thinking about installing a 6.0.1 custom rom. Do i need to downgrade first or can i install directly 6.0.1 rom from android N .
Thanks in advance

The rom itself will work,however fingerprint and camera might be borked.

syedhmed said:
The rom itself will work,however fingerprint and camera might be borked.
Click to expand...
Click to collapse
So should I downgrade first?

jeevan_cool said:
I am Official Nougat. Currently locked bootloader and stock. im thinking about installing a 6.0.1 custom rom. Do i need to downgrade first or can i install directly 6.0.1 rom from android N .
Thanks in advance
Click to expand...
Click to collapse
yaa its mandatory to downgrade to stock MM for all the features to work. later u can install custom roms based on MM

jeevan_cool said:
So should I downgrade first?
Click to expand...
Click to collapse
If you don't use the fp ,the rom will work fine without the downgrade.

Thank u everyone for the replies

OTA update when rooted

My phone is unlocked and rooted. It wants to download the OTA but I know that Motorola says on their site you will have problems with the OTA. Should I download it or Should I flash a ROM.

mongoose96 said:
My phone is unlocked and rooted. It wants to download the OTA but I know that Motorola says on their site you will have problems with the OTA. Should I download it or Should I flash a ROM.
Click to expand...
Click to collapse
You must be PURE stock to take an OTA update, or it will fail and bootloop... Flash a rom if you wish.

What i did was make a back up of everything just incase and then look up the ota version on your phone and get it in the rom section and look up twrp flashable OTAs and just flash it. you might lose root but its easy to get back if you flash magisk again.

You can found the right guide here:
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175

does anyone have fastboot stock rom?

siddhesh9146 said:
does anyone have fastboot stock rom?
Click to expand...
Click to collapse
Of the current version? lol, no, we wish... we are averaging 3-6 months behind OTA releases for full ROM images, if we get them at all. Moto does not officially provide them, so they have to be leaked somehow, and sources are completely dried up yet, but it's getting there. :/

Hi. Can I get Oreo Ota for mi xt1670 with rooted device but locked BL? I'm on stock everything. Thanks.

mortadelax said:
Hi. Can I get Oreo Ota for mi xt1670 with rooted device but locked BL? I'm on stock everything. Thanks.
Click to expand...
Click to collapse
You can't be rooted with a locked bootloader so your question is obsolete.
You can apply to OTA with an unlocked bootloader.
You can't if you're rooted or changed anything else in /system or /vendor.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
You can't be rooted with a locked bootloader so your question is obsolete.
You can apply to OTA with an unlocked bootloader.
You can't if you're rooted or changed anything else in /system or /vendor.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply. Very clear! Please I need more help. The thing is...I don't want the oreo ota right now. This is my mother's phone so I don't want any problem. Nougat is just fine for now. So I need to stop the upgrade notification spam. I believe I must unlock BL, then root, then freeze the upgrader app. Is that correct? I can't force stop the app. That's for now.
I've read bad reviews about oreo battery drain and other stuff. That's why I'm trying to avoid it.
If someday I want it, maybe will install some rom.
Thanks bro.
EDIT. Does this make sense? Or should I stay stock everything and take the ota/ignore the spam everyday?
EDIT 2. Another question. What happen if I take the oreo ota, and i don't like it. Can I unlock BL, root, install some nougat rom, as a pseudo downgrade?

mortadelax said:
Thanks for the reply. Very clear! Please I need more help. The thing is...I don't want the oreo ota right now. This is my mother's phone so I don't want any problem. Nougat is just fine for now. So I need to stop the upgrade notification spam. I believe I must unlock BL, then root, then freeze the upgrader app. Is that correct? I can't force stop the app. That's for now.
I've read bad reviews about oreo battery drain and other stuff. That's why I'm trying to avoid it.
If someday I want it, maybe will install some rom.
Thanks bro.
EDIT. Does this make sense? Or should I stay stock everything and take the ota/ignore the spam everyday?
EDIT 2. Another question. What happen if I take the oreo ota, and i don't like it. Can I unlock BL, root, install some nougat rom, as a pseudo downgrade?
Click to expand...
Click to collapse
Oreo ist absolutely fine, no problems with it.
I haven't heard of any issues like increased battery drain, for me nothing changed at all regarding battery and the rest is also working flawlessly.
It would be a lot of action to unlock and root the device just to stop the updater service.
If you don't have any other plans that need root privileges I recommend just taking the OTA (s).
If you want to run another ROM later you can always unlock the bootloader, install TWRP, root the device and install any kind of custom ROM, Nougat, Oreo or Pie. There are also TWRP flashable stock firmwares which make it easy to move between different stock versions.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
If you want to run another ROM later you can always unlock the bootloader, install TWRP, root the device and install any kind of custom ROM, Nougat, Oreo or Pie. There are also TWRP flashable stock firmwares which make it easy to move between different stock versions.
Click to expand...
Click to collapse
That's good. A pseudo downgrade is possible. Thanks man. I'll think about it. And yes, the root privileges is just for stopping the updater.
Cheers
EDIT. Man, are you sure about this? Taking the Oreo Ota, and in the future unlock BL, root and install whatever rom?

mortadelax said:
That's good. A pseudo downgrade is possible. Thanks man. I'll think about it. And yes, the root privileges is just for stopping the updater.
Cheers
EDIT. Man, are you sure about this? Taking the Oreo Ota, and in the future unlock BL, root and install whatever rom?
Click to expand...
Click to collapse
Yes I am.
Just check some of the custom ROM threads, there are some that need stock Nougat as base but the most of them need Oreo. For custom ROMs there are no up/downgrading problems, that's only the case for stock firmwares.
And as said above, there are TWRP flashable stock builds that doesn't have these problems too and will bring you to whatever stock firmware you want, not just pseudo. (Here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482 )
So if you're on stock Oreo after unlocking the bootloader and flashing TWRP all options are open for you. Just don't forget to make a full nandroid backup incl. EFS and persist before you flash anything.
Sent from my Moto G5 Plus using XDA Labs

Custom ROM to latest stock?

I have a US XT1687 on LineageOS (2017-09-19 build), and I would like to flash the latest stock firmware (which I believe is the April NPNS25.137-93-10 update), while also continuing to receive future OTA updates
The fastboot stock firmware thread was closed.
I found these files https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ but I don't see the 93-10 update.
Can I flash the 93-4 update from that site via fastboot and then get the 93-10 update via OTA?
Thanks!

I believe it depends on what bootloader version you were on before. If you were on 93-4 or earlier, then theoretically you should be fine. If you were on the 93-10 version of the bootloader and attempted to flash to the 93-4 stock rom, and then take an OTA from there, you are very likely going to hard-brick your device.
There are a lot of active threads about flashing back to stock and losing IMEI and enhanced LTE, so I wouldn't risk it. Out of curiosity why would you want to flash back to stock Nougat? IMO the camera is worse and you're rolling back to an older OS.

dunderball said:
I believe it depends on what bootloader version you were on before. If you were on 93-4 or earlier, then theoretically you should be fine. If you were on the 93-10 version of the bootloader and attempted to flash to the 93-4 stock rom, and then take an OTA from there, you are very likely going to hard-brick your device.
There are a lot of active threads about flashing back to stock and losing IMEI and enhanced LTE, so I wouldn't risk it. Out of curiosity why would you want to flash back to stock Nougat? IMO the camera is worse and you're rolling back to an older OS.
Click to expand...
Click to collapse
I'm actually still on Nougat. The last time I flashed a new ROM was back in September (the LineageOS build I'm using is from 2017-09-19). So my bootloader is likely whatever the latest one was around that time.
From what I read, it seemed like people were losing their IMEI and VoLTE after flashing 8.1 custom ROMs, which I haven't done, so I figured I was safe. Maybe I'm misunderstanding?

Yousie642 said:
I'm actually still on Nougat. The last time I flashed a new ROM was back in September (the LineageOS build I'm using is from 2017-09-19). So my bootloader is likely whatever the latest one was around that time.
From what I read, it seemed like people were losing their IMEI and VoLTE after flashing 8.1 custom ROMs, which I haven't done, so I figured I was safe. Maybe I'm misunderstanding?
Click to expand...
Click to collapse
Ah I wasn't aware that you were on a nougat version of LOS. I would still back up all partitions just in case.

dunderball said:
Ah I wasn't aware that you were on a nougat version of LOS. I would still back up all partitions just in case.
Click to expand...
Click to collapse
Is that different from doing a NAND backup in TWRP?

Yousie642 said:
Is that different from doing a NAND backup in TWRP?
Click to expand...
Click to collapse
Nope it's the same.

Yousie642 said:
I have a US XT1687 on LineageOS (2017-09-19 build), and I would like to flash the latest stock firmware (which I believe is the April NPNS25.137-93-10 update), while also continuing to receive future OTA updates
The fastboot stock firmware thread was closed.
I found these files https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ but I don't see the 93-10 update.
Can I flash the 93-4 update from that site via fastboot and then get the 93-10 update via OTA?
Thanks!
Click to expand...
Click to collapse
Here's a mirror of the 93-10 firmware, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud but not everyone was able to download it from there.
If you changed to a custom rom in September 2017 you should have been on August security patch which is the firmware NPNS25.137-33-11.
But you should be good to go with 93-10.
As written above make sure to have a full nandroid, especially of EFS.
Sent from my Moto G5 Plus using XDA Labs

dunderball said:
Nope it's the same.
Click to expand...
Click to collapse
Wolfcity said:
Here's a mirror of the 93-10 firmware, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud but not everyone was able to download it from there.
If you changed to a custom rom in September 2017 you should have been on August security patch which is the firmware NPNS25.137-33-11.
But you should be good to go with 93-10.
As written above make sure to have a full nandroid, especially of EFS.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks dudes! I actually found my old adb folder and saw I had the files for NPN25.137-83 extracted there, so I'm pretty sure that's what I'm on. Seems like it still won't be an issue though.
What I am worried about now is losing VoLTE if I ever decide to go back to a custom ROM. Though, from what I understand, as long as I have an EFS backup, I can fix it. Is that right?

Yep you should be fine. I didn't have issues when going from stock to custom. Still -- I'd try out an Oreo rom before jumping back to stock.

dunderball said:
Yep you should be fine. I didn't have issues when going from stock to custom. Still -- I'd try out an Oreo rom before jumping back to stock.
Click to expand...
Click to collapse
Y'know, it didn't actually occur to me, and this may be a silly question, but now I'm wondering if there's actually any need to run a stock firmware update before going to newer custom ROMs? The reason I ask is because this was a thing with my Nexus 5x. Newer LineageOS builds sometimes needed a bootloader and radio update.