Database Develop

Remove "this build is for development purposes only screen"

Hi was wondering if it is possible to remove the red writing on the One on the bootscreen that says this build is for development purposes only?
As i am doing a part exchange with the Galaxy note 2
Kind regards Anthony

mimicuk said:
Hi was wondering if it is possible to remove the red writing on the One on the bootscreen that says this build is for development purposes only?
As i am doing a part exchange with the Galaxy note 2
Kind regards Anthony
Click to expand...
Click to collapse
I don't have a dev model. Is that what comes from the factory, or did you flash a custom ROM?

stevedebi said:
I don't have a dev model. Is that what comes from the factory, or did you flash a custom ROM?
Click to expand...
Click to collapse
Happens on all builds when you flash a custom recovery/rom

MacHackz said:
Happens on all builds when you flash a custom recovery/rom
Click to expand...
Click to collapse
Thanks. I'm on stock right now, but considering flashing later. I appreciate the information.

It happens when anything is tampered from stock, the only way to get rid of it is a Modded hboot which requires s-off
Sent from my HTC One using Tapatalk 2

How long do you think before s-off is available?

mimicuk said:
How long do you think before s-off is available?
Click to expand...
Click to collapse
No clue, I have no insight if anyone is working on it.
Sent from my HTC One using Tapatalk 2

Regardless if you remov the sign, your boot loader will still signify that its been tampered with.
Sent from my HTC One using xda premium

Will flashing a custom boot animation remove this? or does the screen appear before the boot logo?

superchilpil said:
It happens when anything is tampered from stock, the only way to get rid of it is a Modded hboot which requires s-off
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
dnydny said:
Will flashing a custom boot animation remove this? or does the screen appear before the boot logo?
Click to expand...
Click to collapse
Please read above
Sent from my HTC One using Tapatalk 2

dnydny said:
Will flashing a custom boot animation remove this? or does the screen appear before the boot logo?
Click to expand...
Click to collapse
boot logo is different from the animated screen as you boot. you cannot change the boot logo without s-off. if you try flashing a new logo image, your device will not boot. i've already tried. had to reload rom.
s-off will be ready when it's ready.

Flash a stock kernel. By saying stock I mean the one HTC provides and compiles. After flashing it the message should be gone.
The sole reason why it's showing up is because kernel devs here repack the kernel with the parameter
console=ttyHSL0,115200,n8 androidboot.hardware=m7 user_debug=31
Click to expand...
Click to collapse
Which came from earlier builds which were not for retail devices.

I haven't installed a custom rom or kernel and get this message.

if you want to pay for s-off mobiletechvideos.com has achieved s-off on the htc one. i dont know if they added the service yet though
---------- Post added at 07:36 AM ---------- Previous post was at 07:35 AM ----------
biffsmash said:
I haven't installed a custom rom or kernel and get this message.
Click to expand...
Click to collapse
did you unlock the bootloader and root?

xdracco said:
boot logo is different from the animated screen as you boot. you cannot change the boot logo without s-off. if you try flashing a new logo image, your device will not boot. i've already tried. had to reload rom.
s-off will be ready when it's ready.
Click to expand...
Click to collapse
how do u remove the text with S-off? can teach? i am s-off now, thanks

FxJohnnyEng said:
how do u remove the text with S-off? can teach? i am s-off now, thanks
Click to expand...
Click to collapse
Use a modified hboot/firmware without this red warning.

Sprint Moto X

Hey Guys! Finally able to bring my Moto X home and start messing around!
So this is my first Motorola device and my head is spinning with all these root/unlocking bootloader threads.
So can anyone explain to me some of the stuff I'm going to need to know, seeing how this is my first Motorola device?
Which root method is the latest?
What is the newest OTA?
How do I unlock my bootloader?
Not a noob by any means. One explanation and I'll have it down.
Thank you in advance!!

To unlock the bootloader go here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root it: unlock the bootloader, flash TWRP with fastboot, boot directly into TWRP, reboot from TWRP, it will ask if you want to root, swipe to root, finish rebooting, enjoy root.
I believe the above will work with the newest update. I wouldnt know though, im on Verizon.

mentose457 said:
To unlock the bootloader go here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root it: unlock the bootloader, flash TWRP with fastboot, boot directly into TWRP, reboot from TWRP, it will ask if you want to root, swipe to root, finish rebooting, enjoy root.
I believe the above will work with the newest update. I wouldnt know though, im on Verizon.
Click to expand...
Click to collapse
Awesome. Thanks for the quick response!
Can anyone confirm that?

So I got the bootloader unlocked and I'm going to flash TWRP now.
Just a quick question, has anyone been able to get rid of the development warning text in the beginning of the boot when unlocking bootloader?

eyeisdasteve said:
So I got the bootloader unlocked and I'm going to flash TWRP now.
Just a quick question, has anyone been able to get rid of the development warning text in the beginning of the boot when unlocking bootloader?
Click to expand...
Click to collapse
There is a thread in the general section on your to do it.
Sent from my Moto X.

mentose457 said:
There is a thread in the general section on your to do it.
Sent from my Moto X.
Click to expand...
Click to collapse
Do you know the name of the thread? I looked and couldn't find it.
:good::good:

Search for "change boot logo".
Sent from my Moto X.
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=2445150
Sent from my Moto X.

mentose457 said:
Search for "change boot logo".
Sent from my Moto X.
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=2445150
Sent from my Moto X.
Click to expand...
Click to collapse
Perfect. I was looking for the wrong thin that's why!! Thank you again!! :laugh:

[Q] Locked bootloader, bootloop... brick?

Hi all! Im not a motorola user of any sorts, but a friend of mine, who's not a great english speaker and doesn't have an xda account, bricked, or at least so it seems, his Moto X 2014 (xt1097).
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader...
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.

ad astra said:
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
Click to expand...
Click to collapse
This is only true if he upgraded to 5.1, which it sounds like he did.
ad astra said:
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader.
Click to expand...
Click to collapse
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
ad astra said:
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
Click to expand...
Click to collapse
You in fact cannot flash a ROM with a locked bootloader.
ad astra said:
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.
Click to expand...
Click to collapse
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?

JulesJam said:
This is only true if he upgraded to 5.1, which it sounds like he did.
Click to expand...
Click to collapse
Yep, that's exactly the case.
JulesJam said:
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
Click to expand...
Click to collapse
If i'm not mistaken it was the other way around. He tried to update to 5.1 (I believe that the zip was form a different vendor).
JulesJam said:
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
Click to expand...
Click to collapse
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
JulesJam said:
You in fact cannot flash a ROM with a locked bootloader.
Click to expand...
Click to collapse
I understand what you mean, I meant that you can flash updates from sdcard with stock recovery.
JulesJam said:
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?
Click to expand...
Click to collapse
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one. So.. we didn't check that. What's the difference between both? Now he managed to flash (with unlocked bootloader) the 5.1 rom and his bootloader version shows 60.16.
On the other hand, the phone's argentinian made. The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0.
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Anyway, I think this thread will be of general interest so I'll continue to provide info on the case.

ad astra said:
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
Click to expand...
Click to collapse
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
ad astra said:
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one.
Click to expand...
Click to collapse
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
ad astra said:
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Click to expand...
Click to collapse
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
ad astra said:
the 5.1 rom and his bootloader version shows 60.16.
Click to expand...
Click to collapse
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.

JulesJam said:
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.
Click to expand...
Click to collapse
But how? His bootloader was locked, and we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work. We even edited the .xml file and tried the nokia flashing tool, which also resulted in a failed attempt.
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
2) adb sideload.
3) vendor flash tool (like Odin, and nokias RDS or something like that).

ad astra said:
The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0. .
Click to expand...
Click to collapse
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
ad astra said:
But how?
Click to expand...
Click to collapse
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
ad astra said:
But how? His bootloader was locked,
Click to expand...
Click to collapse
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
ad astra said:
we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work.
Click to expand...
Click to collapse
You don't do it through recovery - you do it through bootloader mode.

JulesJam said:
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
You don't do it through recovery - you do it through bootloader mode.
Click to expand...
Click to collapse
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Thanks for the info! And also thanks for the tip on the motorola deivce manager upgrade thing. The LG suite does the same thing and so I keep my stock image safely stored.

ad astra said:
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
Click to expand...
Click to collapse
Yes, this works. You don't need an unlocked bootloader to do it, but you do need mfastboot if the image file you have is a single image file. If you have the system already broken down into chunks, you can use regular fastboot.
ad astra said:
3) vendor flash tool (like Odin, and nokias RDS or something like that).
Click to expand...
Click to collapse
The one you want for a Moto X is the Motorola tool - RSDLite. RSDLite has mfastboot as a part of it.
You needed mfastboot to flash a single file system.img. Regular fastboot from the SDK won't work. mfastboot is motorola's version of fastboot.
Regular fastboot can only flash chunks of system. I think they have to be 256MB or less in size.
---------- Post added at 12:44 AM ---------- Previous post was at 12:41 AM ----------
ad astra said:
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Click to expand...
Click to collapse
I was trying to help you, but you didn't post back.

JulesJam said:
I was trying to help you, but you didn't post back.
Click to expand...
Click to collapse
Dont get me wrong. You did help me (thats why i left u a thanks) :good: My friend just went and did his thing on his own. I probably live in a different time zone, and my work doesn't allow me to be online the whole day. It was really late when I posted, I wasn't expecting a reply on the fly so I went to sleep. I continued this thread just because of curiosity.
On a side note, my friend checked his phone and, it seem'd alright, closed box and all. He worked a time at Motorola so he knows what was getting into. It seems the whole mess happened because of a forum post which indicated that he was flashing a soak test rom, when it was actually a final release (or something like that). This last, ended up messing up his system.

The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.

Steve-x said:
The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.
Click to expand...
Click to collapse
Agreed. Very poor judgement on behalf of my friend. Lesson learnt I guess, now he's bootloader is unlocked and he managed to flash 5.1 as previously intended.
It seems that the guy who posted the soak mistakenly posted the wrong file and caused a lot of problems for a lot of people... but, nevertheless u cant trust everything to go right... so that's my friends own fault for not unlocking, backing up and investigating enough.

i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?

Lussardi said:
i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?
Click to expand...
Click to collapse
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk

AGISCI said:
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works

Lussardi said:
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works
Click to expand...
Click to collapse
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk

AGISCI said:
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I do not know ... a customer came in for repair, so do not know the reason why he stayed so.

HELP: I've lost OEM Unlock

Need help badly:
I Lost OEM unlock option when I installed a custom rom. I have waited for 7 days and the option wouldnt appear in the settings. I believe if I reboot this, Id be stuck in binary blah blah and Id be back in stock rom again and be jailed for 7 days.
Im currently rooted. Ive read an article about DrKetan OEM patch. Can I be able to install that without using TWRP? Like the app Flashify or Flashfire?
Any insights please?
Thanks

I wish to restore my TWRP backup but I cant get to TWRP as I believe id be stuck in " only official binary blah blah"

I first unlocked the boot loader but didn't worked than I was unable to find the one unlock option again in developer mode even after reflashing the firmware.
In the Odin mode it is written oem lock off
Can somebody guide me how to show that option again

sangreal327 said:
Need help badly:
I Lost OEM unlock option when I installed a custom rom. I have waited for 7 days and the option wouldnt appear in the settings. I believe if I reboot this, Id be stuck in binary blah blah and Id be back in stock rom again and be jailed for 7 days.
Im currently rooted. Ive read an article about DrKetan OEM patch. Can I be able to install that without using TWRP? Like the app Flashify or Flashfire?
Any insights please?
Thanks
Click to expand...
Click to collapse
Some roms hide the OEM unlock option to avoid accidentally switching it and then locking you out ie only official binaries. Search in the thread of the rom you are using to see if that is the case.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Malikzeeshanarif said:
I first unlocked the boot loader but didn't worked than I was unable to find the one unlock option again in developer mode even after reflashing the firmware.
In the Odin mode it is written oem lock off
Can somebody guide me how to show that option again
Click to expand...
Click to collapse
Try using this great guide
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/

stonedpsycho said:
Some roms hide the OEM unlock option to avoid accidentally switching it and then locking you out ie only official binaries. Search in the thread of the rom you are using to see if that is the case.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Try using this great guide
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Click to expand...
Click to collapse
Does installing a new firmware Will replace the one unlock or not

Official TWRP for Moto One Power & Lineage 16 Alpha

https://twrp.me/motorola/motorolamotoonepower.html

__NOT TESTED YET__
testing version of lineage 16: https://androidfilehost.com/?w=files&flid=283156
HOW TO FLASH:
boot twrp with fastboot: http://build.twrp.me/twrp-3.2.3-1-chef.img
SUPPPPPERRRR IMPORTANNNNTTTTTTTTT flash copy-partitions-AB.zip (if you don't device will brick) : https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
flash lineage
reboot
find more info in moto x4 lineage thread : https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
STOCK FIRMWARES to restore back to stock : https://mirrors.lolinet.com/firmware/moto/chef/
report bugs to me with logcat

Hey, thanks a ton for the ROM but how to unlock the bootloader?
And also, we do not have the device yet. It is supposed to go on sale on 5th October!

Hello guys is that possible get china version P30 Note and install One power firmware on it? thanks.

ITMASTER said:
Hello guys is that possible get china version P30 Note and install One power firmware on it? thanks.
Click to expand...
Click to collapse
Possibly "Yes", if the hardware is same, firmware will install, (I dont know about the modem firmware though). But no OTA for you.
You can give it a try...

Ok I will get an chinese version soon. Then we can see. it has an model number XT1942-1. whats the one power model number??

ITMASTER said:
Ok I will get an chinese version soon. Then we can see. it has an model number XT1942-1. whats the one power model number??
Click to expand...
Click to collapse
I will try to find it for you if possible now, but I will buy the device on 5th of October. Hoping to help you more once I get my hands on!
All I know that the device name is "chef" and/or "chef_sprout".

smyaknti said:
I will try to find it for you if possible now, but I will buy the device on 5th of October. Hoping to help you more once I get my hands on!
All I know that the device name is "chef" and/or "chef_sprout".
Click to expand...
Click to collapse
Thanks bro )) I will have my device on hands not soon then Oct 20 so we can see.

smyaknti said:
Hey, thanks a ton for the ROM but how to unlock the bootloader?
And also, we do not have the device yet. It is supposed to go on sale on 5th October!
Click to expand...
Click to collapse
just run the command on adb in fastboot mode
_fastboot oem unlock_

Bristow Xavier said:
just run the command on adb in fastboot mode
_fastboot oem unlock_
Click to expand...
Click to collapse
But the last motorola device I unlocked required a key to unlock the bootloader, which was exclusively tied to my device and my motorola account. They have strict warranty regulations refarding unlocking. How is it different this time?

smyaknti said:
But the last motorola device I unlocked required a key to unlock the bootloader, which was exclusively tied to my device and my motorola account. They have strict warranty regulations refarding unlocking. How is it different this time?
Click to expand...
Click to collapse
since it's an Andoid One device...:laugh:

Bristow Xavier said:
since it's an Andoid One device...:laugh:
Click to expand...
Click to collapse
Erm, okay. Lets see. I didn't find proper evidence on how it was supposed to be done in the moto x4 android one variant. Can you provide any thread or site having the guide? ?

erfanoabdi said:
__NOT TESTED YET__
testing version of lineage 16: https://androidfilehost.com/?w=files&flid=283156
HOW TO FLASH:
boot twrp with fastboot
SUPPPPPERRRR IMPORTANNNNTTTTTTTTT flash copy-partitions-AB.zip (if you don't device will brick) : https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
flash lineage
reboot
find more info in moto x4 lineage thread : https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
STOCK FIRMWARES to restore back to stock : https://mirrors.lolinet.com/firmware/moto/chef/
report bugs to me with logcat
Click to expand...
Click to collapse
i was really surprised and happy to learn that you are actually the official maintainer of Lineage OS for payton, so i was curious if
you're going to buy this device and develop roms.
I've avoided Moto devices past year because the specs and high price which reflected on the development(in the price range i could afford), it wasn't much. but this device has really good specs so i hope developers like you get on board so noobs like me will have better functioning roms.

does unlocking the bl erase user data?

Deleted

SOMEONE PLEASE HELP ME OUT
i unlocked boot loader and flashed twrp
but somehow i could not boot into it with hardware key combos, but adb commands
i could boot into my system then, but to fix the twrp problem i flashed twrp again from twrp
now the phone boots into twrp with hardware keys but not to the system anymore
even if i press reboot to system from twrp, it still reboots into twrp the next boot

For further queries and help, development join here
t.me/MotoOnePower

funeralfog said:
SOMEONE PLEASE HELP ME OUT
i unlocked boot loader and flashed twrp
but somehow i could not boot into it with hardware key combos, but adb commands
i could boot into my system then, but to fix the twrp problem i flashed twrp again from twrp
now the phone boots into twrp with hardware keys but not to the system anymore
even if i press reboot to system from twrp, it still reboots into twrp the next boot
Click to expand...
Click to collapse
In twrp , reboot menu choose Power Off option & and try On ur ph hope its work for you

funeralfog said:
SOMEONE PLEASE HELP ME OUT
i unlocked boot loader and flashed twrp
but somehow i could not boot into it with hardware key combos, but adb commands
i could boot into my system then, but to fix the twrp problem i flashed twrp again from twrp
now the phone boots into twrp with hardware keys but not to the system anymore
even if i press reboot to system from twrp, it still reboots into twrp the next boot
Click to expand...
Click to collapse
You're on the One Power or P30 Note?

mitu725 said:
In twrp , reboot menu choose Power Off option & and try On ur ph hope its work for you
Click to expand...
Click to collapse
Didn't
---------- Post added at 05:46 AM ---------- Previous post was at 05:46 AM ----------
smyaknti said:
You're on the One Power or P30 Note?
Click to expand...
Click to collapse
One power