Hi, i am new to rooting and modding and i want to get away the warning message on my oneplus5t that remember me everrytime i turn it on i have a unlocked bootloader.
Is there a way to do it? I want to change also the boot animation becouse is cool but with this message is horrible, i want to remove it before changing the boot animation.
Can someone help me to find a solution? I searched and i found is not removable yet i just wanted to make sure is 100% impossible to do it
I know, it's horrible but impossible to remove ...
asnachan said:
Hi, i am new to rooting and modding and i want to get away the warning message on my oneplus5t that remember me everrytime i turn it on i have a unlocked bootloader.
Is there a way to do it? I want to change also the boot animation becouse is cool but with this message is horrible, i want to remove it before changing the boot animation.
Can someone help me to find a solution? I searched and i found is not removable yet i just wanted to make sure is 100% impossible to do it
Click to expand...
Click to collapse
You should use the Questions & Answers section. This is for original development only
There is no way as the bootloader is locked down. There was some guy claiming to be able to do this but it was just a hoax or a developer not knowing enough on this topic.
For the bootanimation there should be a bootanimation.zip in /system/media. That needs to be replaced.
Thanks and sorry if i putted this topic here
I will have always this **** when i boot it up so, damn oneplus
Silvio Scarani said:
I know, it's horrible but impossible to remove ...
Click to expand...
Click to collapse
un altro italiano
Macusercom said:
You should use the Questions & Answers section. This is for original development only
There is no way as the bootloader is locked down. There was some guy claiming to be able to do this but it was just a hoax or a developer not knowing enough on this topic.
For the bootanimation there should be a bootanimation.zip in /system/media. That needs to be replaced.
Click to expand...
Click to collapse
What are you talking about, at the top of the site it says;
xda-developers > OnePlus 5T > OnePlus 5T Questions & Answers.
I just got the OnePlus 5T, my understanding is it's the same on this phone as some others, the boot loader message is low level, more like in the boot image, and the bootanimation.zip is just the splash images.
DoR3M3 said:
What are you talking about, at the top of the site it says;
xda-developers > OnePlus 5T > OnePlus 5T Questions & Answers.
I just got the OnePlus 5T, my understanding is it's the same on this phone as some others, the boot loader message is low level, more like in the boot image, and the bootanimation.zip is just the splash images.
Click to expand...
Click to collapse
It was moved to this section by a mod.
Macusercom said:
It was moved to this section by a mod.
Click to expand...
Click to collapse
Ahh my bad...
You have to sign boot.img and recovery.img to remove the warning.
I have managed to eliminate it by signing those two images.
In my oneplus 5 and 5t I have twrp installed and with rom lineageos without warning.
Who wants to try to send me your boot and recovery and return it for you to try.
Remember that you have to close the bootloader whereby the phone will be wipe
Process:
fastboot oem unlock
unlock bootloader
You have to go back to fastboot mode
fastboot flash boot boot.img
fastboot recovery recovery_name.img
fastboot oem lock
Wuala
It can be done in any rom from firmware 5.1.5
superatmel said:
You have to sign boot.img and recovery.img to remove the warning.
I have managed to eliminate it by signing those two images.
In my oneplus 5 and 5t I have twrp installed and with rom lineageos without warning.
Who wants to try to send me your boot and recovery and return it for you to try.
Remember that you have to close the bootloader whereby the phone will be wipe
Process:
fastboot oem unlock
unlock bootloader
You have to go back to fastboot mode
fastboot flash boot boot.img
fastboot recovery recovery_name.img
fastboot oem lock
Wuala
It can be done in any rom from firmware 5.1.5
Click to expand...
Click to collapse
Although the above procedure may work, I wouldn't suggest locking the bootloader after making changes like this.
xocomaox said:
Although the above procedure may work, I wouldn't suggest locking the bootloader after making changes like this.
Click to expand...
Click to collapse
Because no, you avoid the annoying message, you enjoy your own kernel and the recovery you want, do you mean that you are going to send some malicious files?
I've been with Android for many years to get my reputation for it. : =
---------- Post added at 09:13 PM ---------- Previous post was at 09:12 PM ----------
[ro.boot.verifiedbootstate]: [green]
[ro.boot.veritymode]: [enforcing]
[ro.bootimage.build.date]: [Fri Sep 28 02:08:12 CEST 2018]
[ro.bootimage.build.date.utc]: [1538093292]
[ro.bootimage.build.fingerprint]: [OnePlus/OnePlus5T/OnePlus5T:8.1.0/OPM1.171019.011/1808081927:user/release-keys]
[ro.bootloader]: [unknown]
[ro.bootmode]: [normal]
[ro.build.date.utc]: [1538093292]
[ro.build.description]: [OnePlus5T-user 8.1.0 OPM1.171019.011 1808081927 release-keys]
[ro.build.display.id]: [superteam_dumpling-userdebug 8.1.0 OPM6.171019.030.K1 b8192e9518 test-keys]
[ro.build.expect.firmware]: [5.1.5]
[ro.build.expect.modem]: [2018-08-08 20:13:31]
[ro.build.fingerprint]: [OnePlus/OnePlus5T/OnePlus5T:8.1.0/OPM1.171019.011/1808081927:user/release-keys]
[ro.build.flavor]: [superteam_dumpling-userdebug]
[ro.build.host]: [Asus-Rog]
[ro.build.id]: [OPM6.171019.030.K1]
[ro.build.product]: [OnePlus5T]
[ro.build.selinux]: [0]
[ro.build.selinux.enforce]: [0]
[ro.build.tags]: [test-keys]
[ro.build.type]: [userdebug]
[ro.build.user]: [superatmel]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [b8192e9518]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.release]: [8.1.0]
[ro.build.version.sdk]: [27]
[ro.build.version.security_patch]: [2018-09-05]
---------- Post added at 09:27 PM ---------- Previous post was at 09:13 PM ----------
In this post it is asked how to eliminate the warning in the boot, I have offered to help to remove it nothing more, since in my terminals it eliminates it.
No words are needed
https://www.youtube.com/watch?v=Bzfd-dKgpes&feature=youtu.be
superatmel said:
No words are needed
https://www.youtube.com/watch?v=Bzfd-dKgpes&feature=youtu.be
Click to expand...
Click to collapse
You're locking the bootloader...
3:58 in Video; fastboot oem lock.
Not exactly the solution people are looking for.
DoR3M3 said:
You're locking the bootloader...
3:58 in Video; fastboot oem lock.
Not exactly the solution people are looking for.
Click to expand...
Click to collapse
Of course, that's the idea of locking the bootloader again to avoid the message.
Try locking it with a boot.img or recovery that is not signed to see what happens
my getprop
[ro.boot.verifiedbootstate]: [green]
bootloader locked+boot signed NO WARNING MESSAGE
[ro.boot.verifiedbootstate]: [orange]
bootloader unlocked+boot unsigned WARNING MESSAGE
[ro.boot.verifiedbootstate]: [red]
bootloader locked+boot unsigned SYSTEM CORRUPT, NOT BOOT
So you need to have the bootloader unlocked if you have already put any rom, any boot or any recovery on your phone?
The bootloader can not be edited but to avoid the warning message if boots and recoverys can be signed
superatmel said:
No words are needed
https://www.youtube.com/watch?v=Bzfd-dKgpes&feature=youtu.be
Click to expand...
Click to collapse
superatmel said:
Of course, that's the idea of locking the bootloader again to avoid the message.
Try locking it with a boot.img or recovery that is not signed to see what happens
my getprop
[ro.boot.verifiedbootstate]: [green]
bootloader locked+boot signed NO WARNING MESSAGE
[ro.boot.verifiedbootstate]: [orange]
bootloader unlocked+boot unsigned WARNING MESSAGE
[ro.boot.verifiedbootstate]: [red]
bootloader locked+boot unsigned SYSTEM CORRUPT, NOT BOOT
So you need to have the bootloader unlocked if you have already put any rom, any boot or any recovery on your phone?
The bootloader can not be edited but to avoid the warning message if boots and recoverys can be signed
Click to expand...
Click to collapse
I understand these things, but are you asking, or telling?
People want to keep the bootloader unlocked to hack on their phones, and locking it defeats this purpose.
The post is about trying to keep the bootloader unlocked and remove the message, but as I mentioned before, it's my understanding it's deep within the bootloader process, not an easy thing to get at, hack away. Also it seems, because of some Google Policy it's pushing on the phone manufacturers to have, as a requirement to their agreement with Google, at least it's what I've come to understand.
DoR3M3 said:
I understand these things, but are you asking, or telling?
People want to keep the bootloader unlocked to hack on their phones, and locking it defeats this purpose.
The post is about trying to keep the bootloader unlocked and remove the message, but as I mentioned before, it's my understanding it's deep within the bootloader process, not an easy thing to get at, hack away. Also it seems, because of some Google Policy it's pushing on the phone manufacturers to have, as a requirement to their agreement with Google, at least it's what I've come to understand.
Click to expand...
Click to collapse
I am saying.
But people do not need to have the bootloader unlocked to hack their phones. In fact I do not want to be hacked, but I do want to modify my boots to add things to the system. and also get not having the message at the start of the system
An example that for example I want
I would like to have the kernel blur but if I put it I have the warning message.
Solution:
I sign the blur kernel, I install it I close the bootloader and I have the kernel working and I do not have a warning message
Does not it help you to autopirate your phone?
---------- Post added at 01:32 AM ---------- Previous post was at 01:28 AM ----------
I could now have oxygen os 5.1.5 or higher with modified kernel, recovery twrp, add xposed modules and closed bootloader.
It's not useful?
superatmel said:
I am saying.
But people do not need to have the bootloader unlocked to hack their phones. In fact I do not want to be hacked, but I do want to modify my boots to add things to the system. and also get not having the message at the start of the system
An example that for example I want
I would like to have the kernel blur but if I put it I have the warning message.
Solution:
I sign the blur kernel, I install it I close the bootloader and I have the kernel working and I do not have a warning message
Does not it help you to autopirate your phone?
---------- Post added at 01:32 AM ---------- Previous post was at 01:28 AM ----------
I could now have oxygen os 5.1.5 or higher with modified kernel, recovery twrp, add xposed modules and closed bootloader.
It's not useful?
Click to expand...
Click to collapse
Well, it's always been my understanding, that if someone is always tinkering, playing with their phone, constantly flashing roms, kernels, etc., then keeping the bootloader unlocked is simpler.
I personally just got the OnePlus 5T, so I don't know if it's doing something different here over other devices, where you can simply lock it on a custom rom and have it boot ok.
It's suppose to be from my understanding that some devices you can lock it, and everything works ok, and other devices, where if you lock it, it wipes all data and encrypts it over, then the rom boots up all wiped, and I'm talking Internal Storage all gone, everything wiped, not a situation good. Locking bootloader on some devices means, loose all data.
So the safest route amongst all devices is to simply leave it unclocked, and getting hacked by someone with an unlocked bootloader, isn't very likely to happen.
DoR3M3 said:
Well, it's always been my understanding, that if someone is always tinkering, playing with their phone, constantly flashing roms, kernels, etc., then keeping the bootloader unlocked is simpler.
I personally just got the OnePlus 5T, so I don't know if it's doing something different here over other devices, where you can simply lock it on a custom rom and have it boot ok.
It's suppose to be from my understanding that some devices you can lock it, and everything works ok, and other devices, where if you lock it, it wipes all data and encrypts it over, then the rom boots up all wiped, and I'm talking Internal Storage all gone, everything wiped, not a situation good. Locking bootloader on some devices means, loose all data.
So the safest route amongst all devices is to simply leave it unclocked, and getting hacked by someone with an unlocked bootloader, isn't very likely to happen.
Click to expand...
Click to collapse
Sorry but I think you do not understand.
Your unlocked bootloader phone is vulnerable since it is ready for any option.
Mine to have it closed my data is safe because if someone opens it is completely deleted.
My phone with a oneplus recovery stock signed by me and a custom boot plus system modifications and closed bootloader is completely safe.
superatmel said:
Sorry but I think you do not understand.
Your unlocked bootloader phone is vulnerable since it is ready for any option.
Mine to have it closed my data is safe because if someone opens it is completely deleted.
My phone with a oneplus recovery stock signed by me and a custom boot plus system modifications and closed bootloader is completely safe.
Click to expand...
Click to collapse
Sorry for any misunderstanding, I understand about the bootloader.
My mistake, I wasn't paying attention that you signed your own image. Did you sign both the recovery and boot?
Now you signed the images, but you locked the bootloader and it's my understanding that if signed, you could get rid of the message and still leave it unlocked. So with your signed images, can you leave it unlocked and the message is gone?
DoR3M3 said:
Sorry for any misunderstanding, I understand about the bootloader.
My mistake, I wasn't paying attention that you signed your own image. Did you sign both the recovery and boot?
Now you signed the images, but you locked the bootloader and it's my understanding that if signed, you could get rid of the message and still leave it unlocked. So with your signed images, can you leave it unlocked and the message is gone?
Click to expand...
Click to collapse
Exactly, now you understand it. I sign boot.img and recovery.img and with that I can close the bootloader and the message disappears. That's what you see in the video.
Install twrp signed by me, lineageos latest version, extract by boot.img and sign it, so at the end of the whole I integrate the boot.img and then I close the bootloader
I have put lineageos to put something, but I create my own systems
Related
update
i had buy sunshine and make s-off
and removed the tampered and the phone now show its Locked
now i need to unroot it ,, i have to flash stock firmware right ?! with stock recovery
Then I suppose at this post I can ask why make a new post if you already asked this question in another thread You're spamming now...
fastboot oem lock
That's the command to lock bootloader. If it's for warranty purposes it probably doesn't make a huge differences seeing as you're S-ON.
What does it say in bootloader "Software status: Modified" ? Then they already know you messed around with things.
It'll say "Relocked" and not "Locked" so there again, they'll know you messed with the phone already.
To go back to stock 100% for warranty purposes you would have needed S-OFF to achieve that. As it is now the only thing you can do is restore stock ROM, stock recovery and use the code fastboot oem lock to lock the bootloader but that won't prevent them from seeing that you unlocked it previously anyways.
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
BerndM14 said:
Then I suppose at this post I can ask why make a new post if you already asked this question in another thread You're spamming now...
fastboot oem lock
That's the command to lock bootloader. If it's for warranty purposes it probably doesn't make a huge differences seeing as you're S-ON.
What does it say in bootloader "Software status: Modified" ? Then they already know you messed around with things.
It'll say "Relocked" and not "Locked" so there again, they'll know you messed with the phone already.
To go back to stock 100% for warranty purposes you would have needed S-OFF to achieve that. As it is now the only thing you can do is restore stock ROM, stock recovery and use the code fastboot oem lock to lock the bootloader but that won't prevent them from seeing that you unlocked it previously anyways.
Click to expand...
Click to collapse
Oh and remove your IMEI from your post as that is personal information.
BerndM14 said:
Then I suppose at this post I can ask why make a new post if you already asked this question in another thread You're spamming now...
fastboot oem lock
That's the command to lock bootloader. If it's for warranty purposes it probably doesn't make a huge differences seeing as you're S-ON.
What does it say in bootloader "Software status: Modified" ? Then they already know you messed around with things.
It'll say "Relocked" and not "Locked" so there again, they'll know you messed with the phone already.
To go back to stock 100% for warranty purposes you would have needed S-OFF to achieve that. As it is now the only thing you can do is restore stock ROM, stock recovery and use the code fastboot oem lock to lock the bootloader but that won't prevent them from seeing that you unlocked it previously anyways.
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
Oh and remove your IMEI from your post as that is personal information.
Click to expand...
Click to collapse
I didnt want to spam on the other thread
So i opend a new thread
And thx for notice me on the imei
So first i need to make s/off
And then flashing stock sense and stock recovery
I will try to do the soff first
BerndM14 said:
Then I suppose at this post I can ask why make a new post if you already asked this question in another thread You're spamming now...
fastboot oem lock
That's the command to lock bootloader. If it's for warranty purposes it probably doesn't make a huge differences seeing as you're S-ON.
What does it say in bootloader "Software status: Modified" ? Then they already know you messed around with things.
It'll say "Relocked" and not "Locked" so there again, they'll know you messed with the phone already.
To go back to stock 100% for warranty purposes you would have needed S-OFF to achieve that. As it is now the only thing you can do is restore stock ROM, stock recovery and use the code fastboot oem lock to lock the bootloader but that won't prevent them from seeing that you unlocked it previously anyways.
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
Oh and remove your IMEI from your post as that is personal information.
Click to expand...
Click to collapse
I just sent my phone back to HTC and I got a "illegal software" notice. I had everything stock except for SOFF. Do you think that was the case?
sparxx4 said:
I didnt want to spam on the other thread
So i opend a new thread
And thx for notice me on the imei
So first i need to make s/off
And then flashing stock sense and stock recovery
I will try to do the soff first
Click to expand...
Click to collapse
You should also take your serial no off of that getvar. Just sayin....
BerndM14 said:
Then I suppose at this post I can ask why make a new post if you already asked this question in another thread You're spamming now...
fastboot oem lock
That's the command to lock bootloader. If it's for warranty purposes it probably doesn't make a huge differences seeing as you're S-ON.
What does it say in bootloader "Software status: Modified" ? Then they already know you messed around with things.
It'll say "Relocked" and not "Locked" so there again, they'll know you messed with the phone already.
To go back to stock 100% for warranty purposes you would have needed S-OFF to achieve that. As it is now the only thing you can do is restore stock ROM, stock recovery and use the code fastboot oem lock to lock the bootloader but that won't prevent them from seeing that you unlocked it previously anyways.
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
Oh and remove your IMEI from your post as that is personal information.
Click to expand...
Click to collapse
so you say there is no way to avoid that they cant see my bootloader was unlocked ?!
Ota update stops a 1/4 of the way and i get a triangle with an exclamation point.
How can I fix this issue. I was using custom Rom but flashed back to stock for update. Only problem is the update won't go thru. Even when I try flashing with command prompt it gives error parsing 24 something like that. I'm starting to believe I jacked my phone all up any help will help. Hopefully someone out there has the solution to my problem. I also uninstall supersu thanks ahead of time
njdevil1146 said:
How can I fix this issue. I was using custom Rom but flashed back to stock for update. Only problem is the update won't go thru. Even when I try flashing with command prompt it gives error parsing 24 something like that. I'm starting to believe I jacked my phone all up any help will help. Hopefully someone out there has the solution to my problem. I also uninstall supersu thanks ahead of time
Click to expand...
Click to collapse
Did you go back to your stock recovery as well? You'll need to.
But the problem is probably a modified system partition. Do you have Xposed installed on your phone? If you do, uninstall all of the modules with Xposed, then uninstall the framework as well to be safe.
Also, you uninstalled SuperSU? Did you use it to unroot first?
Ota update stops a 1/4 of the way and i get a triangle with an exclamation point.
xunholyx said:
Did you go back to your stock recovery as well? You'll need to.
But the problem is probably a modified system partition. Do you have Xposed installed on your phone? If you do, uninstall all of the modules with Xposed, then uninstall the framework as well to be safe.
Also, you uninstalled SuperSU? Did you use it to unroot first?
Click to expand...
Click to collapse
I did unroot with supersu first then uninstall it then I flashed the stock recovery. I never installed xposed. I do agree it has to be a modified partition . How do I go about figuring out if that's the issue. Thanks in advance
njdevil1146 said:
I did unroot with supersu first then uninstall it then I flashed the stock recovery. I never installed xposed. I do agree it has to be a modified partition . How do I go about figuring out if that's the issue. Thanks in advance
Click to expand...
Click to collapse
Flash a custom ROM. It will re-write the system partition.
njdevil1146 said:
I did unroot with supersu first then uninstall it then I flashed the stock recovery. I never installed xposed. I do agree it has to be a modified partition . How do I go about figuring out if that's the issue. Thanks in advance
Click to expand...
Click to collapse
Just hold Volume UP or Volume DOWN (Can't remember which one, I think it's Volume UP) and Tap the Power button to get to the log screen of the recovery "installer" to see what error it reports.
If it's a missing file replace it, if it's a file with "unexpected contents" i.e Changes made to it, put back the original.
How i can install a working stock recovery ?
Where i need to look to know what recovery working with my phone
sparxx4 said:
How i can install a working stock recovery ?
Where i need to look to know what recovery working with my phone
Click to expand...
Click to collapse
You can find your stock recovery here. Search for the one that matches your firmware version and flash it.
BerndM14 said:
Just hold Volume UP or Volume DOWN (Can't remember which one, I think it's Volume UP) and Tap the Power button to get to the log screen of the recovery "installer" to see what error it reports.
If it's a missing file replace it, if it's a file with "unexpected contents" i.e Changes made to it, put back the original.
Click to expand...
Click to collapse
Do I do that on the recovery screen after it fails or when phone is off. How do I go about changing it the file that is. Or placing one if missing. I got unexpected contents a8293.ko
njdevil1146 said:
Do I do that on the recovery screen after it fails or when phone is off. How do I go about changing it the file that is. Or placing one if missing. I got unexpected contents a8293.ko
Click to expand...
Click to collapse
That's a kernel issue. Try flashing back your devices stock boot.img(Contains stock Kernel then). Else just try to restore a nandroid backup for your device.
BerndM14 said:
That's a kernel issue. Try flashing back your devices stock boot.img(Contains stock Kernel then). Else just try to restore a nandroid backup for your device.
Click to expand...
Click to collapse
thats what i did restore a nandroid backup from here idk what to do i give up thanks anyway much appreciated
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
What are you talking about? Before unlocking have you checked OEM unlocking from Developer tools? After this you need to flash Twrp, boot into it directly from bootloader and flash SUPERSU. That should be the minimal steps in order to keep the custom recovery in place.
HaiKaiDo said:
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
Click to expand...
Click to collapse
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
You do need some knowledge so take a look at the howto conversation http://forum.xda-developers.com/showthread.php?t=3206930
, this is my go to tool since my Nexus 4 http://forum.xda-developers.com/showthread.php?t=3258492
Darke5tShad0w said:
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
Click to expand...
Click to collapse
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
HaiKaiDo said:
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
Click to expand...
Click to collapse
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
wtoj34 said:
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
HaiKaiDo said:
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
Click to expand...
Click to collapse
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
wtoj34 said:
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
Click to expand...
Click to collapse
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Well i went and redid everything the same way I did the first time and it worked! I must done something stupid the first time. Guess this thread was for nothing! xD Thanks for clarifying some things for me though guys.
HaiKaiDo said:
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Click to expand...
Click to collapse
Disabling encryption does give you a speed increase. It may or may not be noticeable for your use but the majority can see the difference.
So you have to decide between security and a snappier phone.
Just remember to back all your data up as this requires wiping your data and possibly a clean flash and either switching from the stock rom to another rom(Most have the forced encryption disabled) or when on stock rom either flash another kernel or flash supersu in systemless mode.
Hotspot need it Help! Nexus 5x
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Varsismaname said:
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Click to expand...
Click to collapse
You need to go and start your own thread in the q&a section, its not polite to high jack someone else's.
Hello, I am completely new so I apologize if this is the wrong place.
I wanted to be able to lock my bootloader but still use cyanogenmod, specifically, only allow roms that I have compiled myself and signed with my cert to work on my phone. I unpacked the stock recovery.img, and made the necessary changes to the ramdisk to replace the stock OnePlus key with my own. I then was then able to confirm that only my signed zips could be sideloaded, both official CM and OxygenOS zips failed - just as I wanted.
The issue is then that this only worked with an unlocked bootloader. When I locked it, the OP3 entered a boot cycle, with a strange graphical glitch appearing then the screen going black, again and again. I could then no longer boot to either recovery or cyanogenmod, nor could I unlock fastboot. This amazing guide got my phone working again.
I now have three questions. What prevented my phone booting after I locked it, how does the unbrick tool work, and is there anything I can alter, like certifications or hashes, lower down in the boot sequence to allow only my signed images to work (using the previous tool. I am unsure what QLoader is, some form of serial interface to the 820 to write to the storage chip?).
Thanks for any advice you can offer!
Update: I have unpacked boot.img provided in the unbrick tool. I cannot find any keys to modify in /res but I have found a file called "verify_keys". Does anyone know what I need to change in boot.img to allow my self-signed recovery and os to boot? Thanks
UPDATE 2:
From reading some Android notes it appears that instead of replacing the OEM key, you can also just use fastboot to flash keystores for self-signed recovery and roms. This still allows OEM signed images to run, but is certainly a step in the right direction. I have run into an issue with building a correct keystore. I can use keytool and import my previous certs, but "fastboot flash keystore examplename.keystore" fails. I saw "fastboot flash ssd keystore.dat" used, and it works with my current dot keystore file, but then after locking it fails to boot. I'm going to see how I can convert my .keystore to a .dat.
I've been meaning to ask this same question for a while now also, so I'm eager to see the response. I suspect the official OnePlus forums might be a good place to ask as well, since they are visited by engineers from OnePlus. For anyone else who's curious as to what's being discussed and better the understand the risks of an unlocked bootloader (and how to mitigate them), there's a brief article here as well as a paper.
It is always suggested that never re-lock the bootloader until there is valid reason to do it
JumboMan said:
It is always suggested that never re-lock the bootloader until there is valid reason to do it
Click to expand...
Click to collapse
Have you read any of the attached links in my last post? There are valid reasons for doing so.
Just to pose an oversimplified hypothetical, imagine going through immigration/customs in Saudi Arabia (or maybe even the U.S.) with a Android device that has an unlocked bootloader. The officer examines your possesions, then takes your laptop and phone into a back room. Your phone is powered down and encrypted so it's not like they can do anything, right? Wrong. They plug it into a forensics device and flash a surreptitious malware app onto /system before returning it back to you. Then, the next time you turn on your phone your encryption keys and all your data, all your communications are secretly transmitted. You never have a clue... With a locked bootloader and appropriate precautions, that would never be possible.
Update 3:
I am now following the official Android guide for creating a keystore. They show how to create a "keystore.img" not .dat, bu the error I got when trying "fastboot flash keystore ..." said something along the lines of the keystore not being a valid image. Hopefully this will work. After I get this working, I will move on to removing or damaging the OEM key, hence not even allowing OnePlus images to be sideloaded.
JumboMan said:
It is always suggested that never re-lock the bootloader until there is valid reason to do it
Click to expand...
Click to collapse
I do have a valid reason - security. An unlocked bootloader means any code can be flashed to my device. Even with encryption it is vulnerable to cold boot attacks, it makes it easier to bruteforce, and pulling encryption keys from memory.
chocol4te said:
I do have a valid reason - security. An unlocked bootloader means any code can be flashed to my device. Even with encryption it is vulnerable to cold boot attacks, it makes it easier to bruteforce, and pulling encryption keys from memory.
Click to expand...
Click to collapse
sir prefer not rooting and staying on stock ROM with locked bootloader.
emptyragnarok said:
sir prefer not rooting and staying on stock ROM with locked bootloader.
Click to expand...
Click to collapse
Look, I'm sorry, I don't need any more useless comments saying the solution to my problem is to not do anything like on every other forum I've tried. I am perfectly aware of how to lock the bootloader with a stock rom, but I don't want to use the stock rom. I want to use custom roms. From what I have done so far it appears to be possible, so don't tell me it's not, at least without a good reason.
In addition, the stock method isn't even the most secure the phone can be. OnePlus can still sign any code and run it on my device and hence requires my trust in a third party that I am unwilling to give. I only want my own code to run.
Update 4:
Using the unbrick utility, I have updated the MD5 partition with the checksums of my modified boot and recovery partitions. Unfortunately, I am now getting a checksum failed error, with both the MD5 and recovery partitions highlighted in red. So I was wrong about the checksum being compared with hashes in the MD5 partition. Does anyone know where the lowest level checksums are stored? Hopefully if I can change that, then locking the bootloader will be no issue.
chocol4te said:
Update 4:
Using the unbrick utility, I have updated the MD5 partition with the checksums of my modified boot and recovery partitions. Unfortunately, I am now getting a checksum failed error, with both the MD5 and recovery partitions highlighted in red. So I was wrong about the checksum being compared with hashes in the MD5 partition. Does anyone know where the lowest level checksums are stored? Hopefully if I can change that, then locking the bootloader will be no issue.
Click to expand...
Click to collapse
Bro I am not a prolike you but I understand your vision now,... and I am with you in that.... Open Source stuff and ANdroid as an Open source impify that only... We should have our custom code for locking and unlocking our bootloader so we can have the full control over our device.... If not and the guy that said that you can lock the bootloader with the stock rom didn't get that .. even with stock rom and recovery anyone can have the access of the phone by just unlocking the boot loader and that is simple. SO I GOT YOUR VISION AND I AM WITH YOU I WILL TRY TO UNDERSTAND THE LOCKING SYSTEM OF THE BOOT-LOADER AND I WILL TRY TO FIND THE LOCATION OF LOWER LEVEL CHECKSLUMS... WE will try and try untill we succeed.... I AM WITH YOU BRO!!!!!
indroider said:
Bro I am not a prolike you but I understand your vision now,... and I am with you in that.... Open Source stuff and ANdroid as an Open source impify that only... We should have our custom code for locking and unlocking our bootloader so we can have the full control over our device.... If not and the guy that said that you can lock the bootloader with the stock rom didn't get that .. even with stock rom and recovery anyone can have the access of the phone by just unlocking the boot loader and that is simple. SO I GOT YOUR VISION AND I AM WITH YOU I WILL TRY TO UNDERSTAND THE LOCKING SYSTEM OF THE BOOT-LOADER AND I WILL TRY TO FIND THE LOCATION OF LOWER LEVEL CHECKSLUMS... WE will try and try untill we succeed.... I AM WITH YOU BRO!!!!!
Click to expand...
Click to collapse
Thanks! I'm glad to hear it!
chocol4te said:
Thanks! I'm glad to hear it!
Click to expand...
Click to collapse
You're most welcome bro.
Did I just witness a major bro-down?
Awsome thread, I'd also like to put my OP3 in a state where only ROMs I signed my self will run...
Any further development??
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
indieross said:
Did I just witness a major bro-down?
Click to expand...
Click to collapse
Whats a bro down?
Sent from my Pixel XL using XDA-Developers mobile app
indroider said:
Any further development??
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Whats a bro down?
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry, other stuff came up. I am still very interested in getting this to work, but I am really stuck if I can't understand why the MD5 verification error occurs when I use Loader to flash the modified images. I looked at CopperheadOS, and in their documentation they show how to re-lock the bootloader with a custom ROM. Here is the shell script they use to upload the OS.
Code:
fastboot flash bootloader bootloader-bullhead-bhz11f.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-bullhead-m8994f-2.6.33.2.14.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-bullhead-nbd90z.zip
As you can see they flash two images, boot loader and radio, then update the main ROM. Then apparently it boots fine and the bootloader is OEM locked inside the OS. This was for the Nexus 5X, but I want to find out if a similar process is possible on the OP3.
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
chocol4te said:
Sorry, other stuff came up. I am still very interested in getting this to work, but I am really stuck if I can't understand why the MD5 verification error occurs when I use Loader to flash the modified images. I looked at CopperheadOS, and in their documentation they show how to re-lock the bootloader with a custom ROM. Here is the shell script they use to upload the OS.
As you can see they flash two images, boot loader and radio, then update the main ROM. Then apparently it boots fine and the bootloader is OEM locked inside the OS. This was for the Nexus 5X, but I want to find out if a similar process is possible on the OP3.
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
Click to expand...
Click to collapse
Ok.. Great to hear... Let me if you need any help.. I m here
chocol4te said:
Sorry, other stuff came up. I am still very interested in getting this to work ... ...
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
Click to expand...
Click to collapse
This sounds exactly like what I was looking for. Have you been able to progress? Do you think that the bootloader and the radio are somehow linked in the boot verification sequence?
---------- Post added at 05:51 AM ---------- Previous post was at 05:43 AM ----------
chocol4te said:
UPDATE 2:
From reading some Android notes it appears that instead of replacing the OEM key, you can also just use fastboot to flash keystores for self-signed recovery and roms. This still allows OEM signed images to run, but is certainly a step in the right direction. I have run into an issue with building a correct keystore. I can use keytool and import my previous certs, but "fastboot flash keystore examplename.keystore" fails. I saw "fastboot flash ssd keystore.dat" used, and it works with my current dot keystore file, but then after locking it fails to boot. I'm going to see how I can convert my .keystore to a .dat.
Click to expand...
Click to collapse
Have you read this: https://mjg59.dreamwidth.org/31765.html
Update: The guys at Razer are just about as clueless as a retail phone carrier. They told me to do the exact same thing, the factory reset and all that, but they don't know what they're doing.
So FYI: IF YOU'RE BOOTLOADER IS LOCKED AND YOUR OS WON'T START, YOU'RE SCREWED.
Okay so I rooted the phone on Oreo, the second to last update, and tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again.
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it.
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader.
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------
Dashaquavius said:
Okay so I rooted the phone on Oreo, the second to last update, sand tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again..
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it..
Click to expand...
Click to collapse
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Roxas598 said:
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader
Click to expand...
Click to collapse
iliais347 said:
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
Click to expand...
Click to collapse
waiflih said:
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Click to expand...
Click to collapse
1. I didn't flash TWRP with the bootloader in the locked state, it was while it was unlocked.
2. Out of desperation, after flashing the stock images multiple times (while it says errors and maximum download reached and stuff) I re-locked the bootloader with the command thinking it would finally at least boot into the OS, to no avail.
3. Factory images didn't flash without some kind of error.
4. I'm unable to run any kind of commands, it says it's not allowed.
5. I've flashed multiple times, flashed the previous updates and the latest updates, and there's always some kind of error or it's not allowed.
I'm just gonna contact Razer. Apparently, I can't flash anything if the bootloader is locked? And the phone won't even boot into the OS to let me tick the option? I think I'm screwed.
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
waiflih said:
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
Click to expand...
Click to collapse
It says flashing is not allowed for everything.
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
waiflih said:
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
Click to expand...
Click to collapse
I just got off with Razer support, they're just gonna send me a new one.
And apparently, absolutely NO OTG support!
Let this thread serve as a warning..
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
parky169 said:
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
Click to expand...
Click to collapse
Interesting. I sent 2 phones with speaker issues and they offered a replacement for both and gave me shipping labela.
Moto G7 Play bootloader unlock issues - "bad key", not OTA, no way to roll back?
My plan was to unlock the bootloader before configuring the new phone - just in case I might need it later, then use the phone as out-of-box. I unlocked the bootloader for the new Moto G7 Play, following the official procedure via the Motorola Accounts page, resulting in:
- Fastboot page shows: "flashing unlocked"
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
- I could not try TWRP, as there is no TWRP for the G7 Play yet (so not sure if flashing would work)
My concerns now are that I will not be able to update the phone, and that the "bad key" issue might cause other problems.
So my plan would be to roll back and lock the phone again, to use it as out-of-box (not worrying about warranty loss that might already have happened - I did accept these terms). However, that does not work, too:
- Locking bootloader requires factory images, which are not available for the G7 Play
- Locking bootloader with fastboot OEM lock will not work without complete images
Any suggestions how bring the phone back to normal? I am disappointed by Motorola, as they officially offer the unlock procedure - which then does not produce the expected outcome, breaks updating, and provides no way to go back? Mind you, I did not apply any "hacks", nothing but the official Motorola unlocking steps.
Thanks for advice
I have the same problem and i cannot fix it.
I tried to get advice from Motorola support - but replies are very generic, referring to the bootloader unlock page (we obviously found that) or to the Motorola Forum (where the answer isn't). Will now just live with the unlocked phone and hope for the opportunity to OTA / update in a while
CoffeeMachineSwitch said:
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
Click to expand...
Click to collapse
Unlocking any Motorola bootloader will cause the bootscreen to display "Bad Key". This is normal. It is a warning that the bootloader has been unlocked and the phone may not be "safe". Once you root a Motorola phone, it will display "N/A" instead of "Bad Key". Again, this is normal behavior. There are image makers that can replace the "splash" image and "hide" the "N/A", but since this phone doesn't have TWRP yet, you'll have to live with it for now.
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
mn1968 said:
Unlocking any
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
Click to expand...
Click to collapse
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
CoffeeMachineSwitch said:
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
Click to expand...
Click to collapse
That would be an unfortunate change if true. Prior devices could be unlocked and still get OTA updates. They won't install if certain changes are made but still get notified of updates.
You still can install full ROM using fastboot commands and regain root by patching boot.img from updated ROM
I did it on both G6 and G7
Where did you get the ROM images from. I understand there are no officials?
CoffeeMachineSwitch said:
Where did you get the ROM images from. I understand there are no officials?
Click to expand...
Click to collapse
Have you tried the LMSA tool? It's a tool you download from Motorola. There is a discussion here about it. It has a rescue button with which, I understand that you can download stock images directly from Motorola, but I haven't used it myself.
umbrisle said:
Have you tried the LMSA tool? ....
Click to expand...
Click to collapse
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
CoffeeMachineSwitch said:
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
Click to expand...
Click to collapse
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Should've read the thread here before i go buy g7 play, not my phone get softbricked.
Unblocked bootloader successfully following the official doc but failed to install magisk by copying the wrong build number of boot.img of OTA from here mirrors.lolinet.com/firmware/moto
now my g7 says
Code:
failed to load kernel, no Bootable A/B slot,
Failed to book Linux
falling back to fastboot.
I downloaded `RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC` which i think this is the right build number when i see error like
Code:
river/retail corrupted
(can't remember exactly, but it's RETAIL not RETUS)
and make my own version of fastboot command stemming from servicefile.xml, still with unlucky.
there is no recovery.img and google has limited resource to make g7 play back to stock orm, i'd like to see if community has any idea or i have to give it to moto to fix it.
========================update=================================
update: i finally get the correct stock ORM which is exactly matching my build number "XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" i was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict, "second time rooting in my life".
not i has flash all of the original orm into my phone then fastboot reboot works, it give me the original error like
Android Recovery
motorola/channel_retail/channel9/PPY29.105-36/d7abeuser/release-keys
Use volum up/down and power
can't load Android system. Your data may be corrupt.
If you continue to get this message, you may need to perform a factory data
reset and erase all user data stored on this device
=====
Try again
Factory data reset
Click to expand...
Click to collapse
now i need to figure out what to do next
===============update=========
lol, turns out just press Factory data reset will bring the brick back to life!!!!!
just want to post my process for anyone having my issue.
the key point to find the correct build number
umbrisle said:
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Click to expand...
Click to collapse
.
The G6 Play is really slow, at least the Boost one. I was kind of sorry I bought one to put on Sprint's free unlimited plan. At least Sprint unlocked it for me after 60 days.
Give the G7Play some time, it just came out.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
gedster314 said:
.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
Click to expand...
Click to collapse
Yeah, but there is inconsistency in Motorolas communication, they actively offer the option to unlock the bootloader (with T&C and all) incl. a link to a rollback feature. Which then does not work. So in a scenario where a developer buys the device because it actively offers this features, they dont get what they paid for. Mind you, we are not discussing hacking a device here or jailbraking - we are discussing features that Motorola actively promotes with a dedicated webpage.
wallace_mu said:
was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict
Click to expand...
Click to collapse
You completely missed the wrong code name "river" in RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC it is for another device, while "channel" is the right one
Where did you get the correct Rom from? Thanks
I don't own Moto G7 Play and can not confirm, however this one worked for wallace_mu
wallace_mu said:
XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
realsine said:
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
Click to expand...
Click to collapse
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
CoffeeMachineSwitch said:
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
Click to expand...
Click to collapse
Hello,
I'm glad to read that I could help.
I have "my" image of 'https :// mirrors.lolinet.com/firmware/moto/channel/official/RETEU/'. There are also some others - just have a look. And please remove the spaces around '://'. I'm currently not allowed to post (external) links, so this way.
* Every 'LOCK' deletes all data and the system is "clean" again.
* The same applies (unfortunately) to EVERY 'UNLOCK'.
I don't care at the moment because I haven't set up my smartphone yet. But it's not nice.
Best regards