Im loosing my signal sometime and its freezing... :/
Is there any way without unlocking bootloader?
Because unlocking bootloader will void my warranty :crying:
Rohitxperia said:
Im loosing my signal sometime and its freezing... :/
Is there any way without unlocking bootloader?
Because unlocking bootloader will void my warranty :crying:
Click to expand...
Click to collapse
Hi, unfortunatley I don't think it is possible at the current point in time as the 4.4.4 update comes with a brand new partition table (On the GPE anyway but both are practicly stock), however your issues may be fixable.
When I upgraded my Moto G (4.3 to 4.4) it caused lots of wierd issues, I just backed up my data, factory reset it and it worked like clockwork. I just don't think they have got upgrading perfected yet on any O/S or phone
Not sure how it is with a locked BL.
But i was able to run 442 on a 444 gpt.bin.
mokkami said:
Not sure how it is with a locked BL.
But i was able to run 442 on a 444 gpt.bin.
Click to expand...
Click to collapse
It depends but on the GPE people have had issues with the partition table
Before ranting at me for asking a question that was already answered, I know there is multiple threads of people asking how to do this.
So I've heard that there is an UNSAFE way of downgrading from 4.4.4 to 4.4.2 on a LOCKED bootloader. I'm willing to take the risk of trying the method for SCIENCE! If someone were to PM me the method of doing the downgrade, I will record what happens and report back.
I'm aware of the risks that come along with this. (Soft brick, hard brick), and I'm willing to take them.
Device:
Moto G XT1028 VZW
Just skip flashing bootloader (motoboot.img) and partition table (gpt.bin), it worked fine in my phone some time ago. Don't blame me if something bad happens to yours, you're the only responsible.
Did you do this with a locked bootloader on 4.4.4? And same device? (Confirming before attempting)
ryanguy426 said:
Did you do this with a locked bootloader on 4.4.4? And same device? (Confirming before attempting)
Click to expand...
Click to collapse
Nope, XT1032 unlocked.
Ah, well I have a locked bootloader on xt1028. Hence why I wanted to confirm first. (Updated op with info regarding locked bl)
ryanguy426 said:
Ah, well I have a locked bootloader on xt1028. Hence why I wanted to confirm first. (Updated op with info regarding locked bl)
Click to expand...
Click to collapse
I have this problem too. I deployed and my mother updated my phone. Thanks, mom.
The new bootloader won't allow older versions to be flashed. But you knew that already.
We're stuck unless an exploit is found. It's too bad, I was so excited to learn about SunShine working on 4.4.2.
If we had a temp root for 4.4.4 I'd test sunshine for y'all, even at the risk of my bootloader
ryanguy426 said:
If we had a temp root for 4.4.4 I'd test sunshine for y'all, even at the risk of my bootloader
Click to expand...
Click to collapse
You and I are both on the same boat, Same phone/carrier & same firmware.
I've been trying to get temp root as well to try out the sunshine apk but it seems
that information on this particular model is very scarce.
That's partly because it's (correct me if I'm wrong) just a rebranded Boost handset for Verizon, so it's not technically an actual variant.
Also the bootloader is like trying to move a 9001 pound rock with your body. It's not going anywhere.
Extosis said:
You and I are both on the same boat, Same phone/carrier & same firmware.
I've been trying to get temp root as well to try out the sunshine apk but it seems
that information on this particular model is very scarce.
Click to expand...
Click to collapse
I am also on this boat:crying:
Please get off my boat. I'm getting claustrophobic
Dear all,
I'm experiencing the infamous screen flickering after I downgraded from 5.0.2 to 4.4.4. Phone (Moto G XT1032) is working fine and the flickering goes away after switching the screen off and on again.
However, after a thorough search through these forums with no answer to my question, I was wondering whether anyone came up yet with a more permanent solution to tackle this problem?
I read it has something to do with the bootloader. While downgrading, I didn't flash the 4.4.4 bootloader (as told) because it could cause a hard brick of my phone. So my second question is; can anyone explain to me why the phone probably hard bricks when you try to downgrade the bootloader? Is there no workaround for this?
Thanks in advance!
Anyone?
I could flash the 4.4.4 bootloader fine when I downgraded. I believe it is required to receive the OTA update (could be wrong). The flickering is most likely caused by the 5.0.2 bootloader. So if you do want to try downgrading it that'll likely fix the problem
I want to update everything except leave the bootloader on 7.1. Will this work?
LoliSmith said:
I want to update everything except leave the bootloader on 7.1. Will this work?
Click to expand...
Click to collapse
I don't believe that will work. Why do you want to do that? 7.1.1 won't relock it if that is what you are worried about....as long as you are already unlocked.
TonikJDK said:
I don't believe that will work..
Click to expand...
Click to collapse
I think I will try it.
TonikJDK said:
Why do you want to do that?
Click to expand...
Click to collapse
I want to be able to lock and unlock if I need to.
LoliSmith said:
I think I will try it.
I want to be able to lock and unlock if I need to.
Click to expand...
Click to collapse
Once you are unlocked it does not matter what version you are on you can lock and unlock all you want. I advise strongly against relocking. You very well might brick yourself. Has happened to a fair number of people already. Also remember unlocking or relocking will wipe your phone.
TonikJDK said:
Once you are unlocked it does not matter what version you are on you can lock and unlock all you want.
Click to expand...
Click to collapse
http://theroot.ninja/depixel8.html
"DO NOT RELOCK YOUR BOOTLOADER, unless you have restored it back to 100% stock and are sure you won't want it unlocked again."
TonikJDK said:
O I advise strongly against relocking. You very well might brick yourself. Has happened to a fair number of people already.
Click to expand...
Click to collapse
Were they still on 7.1 bootloader? Or had they upgraded to 7.1.1 bootloader?
LoliSmith said:
Were they still on 7.1 bootloader? Or had they upgraded to 7.1.1 bootloader?
Click to expand...
Click to collapse
Don't know, didn't pay that much attention.
TonikJDK said:
Don't know, didn't pay that much attention.
Click to expand...
Click to collapse
My guess is they upgraded to the 7.1.1 bootloader and that caused the issues relocking.
LoliSmith said:
My guess is they upgraded to the 7.1.1 bootloader and that caused the issues relocking.
Click to expand...
Click to collapse
It has nothing at all to do with the bootloader.
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
It has nothing at all to do with the bootloader.
Click to expand...
Click to collapse
So what does it have to do with then?
LoliSmith said:
So what does it have to do with then?
Click to expand...
Click to collapse
No one knows for sure. Well some must know but they're not saying. Maybe imei. Depixel8 used an exploit which was closed in a November update. The bootloader versions are exactly the same for the Verizon and Google devices as are the system images.
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
Depixel8 used an exploit which was closed in a November update. The bootloader versions are exactly the same for the Verizon and Google devices as are the system images.
Click to expand...
Click to collapse
Right but if I stay on 7.1 bootloader, then it doesn't matter.
I am on 7.1. still. I want the bootloader to stay on 7.1. I think people who experienced problems relocking had upgraded their bootloader to 7.1.1.
LoliSmith said:
Right but if I stay on 7.1 bootloader, then it doesn't matter.
I am on 7.1. still. I want the bootloader to stay on 7.1. I think people who experienced problems relocking had upgraded their bootloader to 7.1.1.
Click to expand...
Click to collapse
There has been posts about problems relocking before 7.1. Bottom line is if you have a Verizon Pixel, you don't want to do it unless you are completely stock. Regardless of the version of your bootloader. Why would you want to lock it again anyway? Under the context you are using here, it makes no sense. Keep an old bootloader so you can lock and unlock at your choosing. I can see reasons for relocking it but i can't see any reason why you'd want to unlock, then relock, then unlock, etc. Leave it unlocked and enjoy the benefits. I'm not really sure what it is you're wanting here. As has been said before, once unlocked, you'll remain unlocked. Regardless of any update with an updated bootloader. Once unlocked, the only way for you to end up with a locked bootloader is if you issue the necessary fastboot commands. Leave it unlocked. Enjoy. Just my two cents worth.
bobby janow said:
No one knows for sure. Well some must know but they're not saying. Maybe imei. Depixel8 used an exploit which was closed in a November update. The bootloader versions are exactly the same for the Verizon and Google devices as are the system images.
Click to expand...
Click to collapse
There's actually a total of 5 bootloaders
robocuff said:
Bottom line is if you have a Verizon Pixel, you don't want to do it unless you are completely stock.
Click to expand...
Click to collapse
I would never try to relock without being completely stock.
robocuff said:
Why would you want to lock it again anyway?
Click to expand...
Click to collapse
More secure.
LoliSmith said:
I would never try to relock without being completely stock.
More secure.
Click to expand...
Click to collapse
I can't argue with that but how much security are losing by staying on that version and not installing the monthly updates? They are mostly security related updates. Seems to me you'd be trading one security issue for a whole bunch more. That said, if you stay on 7.1 you should be able to lock it and unlock it again in the future if that's what you want to do.
robocuff said:
I can't argue with that but how much security are losing by staying on that version and not installing the monthly updates?
Click to expand...
Click to collapse
As long as they are released as flashable files, I can flash them. But if not then yeah, I am missing out on those.
robocuff said:
That said, if you stay on 7.1 you should be able to lock it and unlock it again in the future if that's what you want to do.
Click to expand...
Click to collapse
Yes, that is what I want to do. The only thing I am not sure on is if I flash everything else, will the phone work with an older bootloader version. It always worked with my motorola and nexus phones but of course, that doesn't mean it will work with a Pixel.
With motorola I did have to keep the partition table consistent with the bootloader version and that could create a problem if the system partition of later versions was larger.
I plan on staying on Nougat with this phone so it shouldn't be a problem.
LoliSmith said:
As long as they are released as flashable files, I can flash them. But if not then yeah, I am missing out on those.
Yes, that is what I want to do. The only thing I am not sure on is if I flash everything else, will the phone work with an older bootloader version. It always worked with my motorola and nexus phones but of course, that doesn't mean it will work with a Pixel.
With motorola I did have to keep the partition table consistent with the bootloader version and that could create a problem if the system partition of later versions was larger.
I plan on staying on Nougat with this phone so it shouldn't be a problem.
Click to expand...
Click to collapse
I don't really know what to tell you about it. The bootloader may work fine but who's to say the vulnerability that depixel8 exploits is in the bootloader? It could be software related, it could be hardware related. I really have no idea. Also, I did a bit of searching about this and from what I read, it sounds as if it might not be possible to unlock it again if you've already taken the security patch that patched the exploit. I could be wrong but it sounds as if that may be the case. Look, at the last paragraph of this article . From what that says, it sounds as though it isn't possible to unlock even on an older version of Nougat once you've taken that security patch. If that's the case, it would seem the the exploit must have targeted something at a very low level. Something other than the OS or the bootloader.
Also, even if you can do what you want to do, I don't know if you can install the updates without installing the one that patches the exploit. I really have no idea. I've seen it said that they are cumulative and in order to install the newest updates, you have to install all the previous ones first. I really have no idea if that is correct or not but if it were me, I'd tread lightly on this one unless you're willing to risk the possibility of not being able to unlock it again. These are just some of my thoughts about it all. I don't have the answers to my thoughts but if it were me, I wouldn't lock it again without knowing for sure it can be unlocked again.
robocuff said:
I could be wrong but it sounds as if that may be the case. Look, at the last paragraph of this article . From what that says, it sounds as though it isn't possible to unlock even on an older version of Nougat once you've taken that security patch.
Click to expand...
Click to collapse
Right because it updated both the bootloader and the kernel. I would only be updating the kernel, not the bootloader. And I am assuming that as long as the bootloader is on 7.1, I can downgrade the kernel, system, etc. as long as the files are signed.
robocuff said:
If that's the case, it would seem the the exploit must have targeted something at a very low level. Something other than the OS or the bootloader.
Click to expand...
Click to collapse
I am not going to ever take any OTAs. Presumably aboot.img is the bootloader but I am not sure what bootlocker.img and keymaster.img are so I would need to research that further. Do you know what they are?
robocuff said:
I've seen it said that they are cumulative and in order to install the newest updates, you have to install all the previous ones first.
Click to expand...
Click to collapse
Are you talking about flashing or taking OTAs?
robocuff said:
I really have no idea if that is correct or not but if it were me, I'd tread lightly on this one unless you're willing to risk the possibility of not being able to unlock it again. These are just some of my thoughts about it all. I don't have the answers to my thoughts but if it were me, I wouldn't lock it again without knowing for sure it can be unlocked again.
Click to expand...
Click to collapse
Thanks. I am OK with not being able to unlock again.
LoliSmith said:
keymaster.img
Click to expand...
Click to collapse
Yeah, definitely won't be updating that:
https://source.android.com/security/keystore/
Hi all, currently running my pixel 2 on latest Dec security patch. 8.1. However due to bug in bootloader (66) unable to unlock the device. I can RMA but still want to know is there any way to revert back OTA update ?
I tried using OTA side load from Recovery but its giving me error saying current timestamp is newer than OTA so failing.
Any tweak to downgrade ?
rohanhole said:
Hi all, currently running my pixel 2 on latest Dec security patch. 8.1. However due to bug in bootloader (66) unable to unlock the device. I can RMA but still want to know is there any way to revert back OTA update ?
I tried using OTA side load from Recovery but its giving me error saying current timestamp is newer than OTA so failing.
Any tweak to downgrade ?
Click to expand...
Click to collapse
As far as i know u cant downgrade. Regarding the bug in bootloader unlocking, that has been solved. Restore factory your device and you should be able to unlock bootloader.
infamousvincci said:
As far as i know u cant downgrade. Regarding the bug in bootloader unlocking, that has been solved. Restore factory your device and you should be able to unlock bootloader.
Click to expand...
Click to collapse
I tried but facing issue. Its toggling but at the time of flashing fastboot command its saying locked.
I doubt something broke in 66 version of bootloader. That's why wanted to be on previous version to check the solution
rohanhole said:
I tried but facing issue. Its toggling but at the time of flashing fastboot command its saying locked.
I doubt something broke in 66 version of bootloader. That's why wanted to be on previous version to check the solution
Click to expand...
Click to collapse
What command are u running? And what is the error that shows
infamousvincci said:
What command are u running? And what is the error that shows
Click to expand...
Click to collapse
Described in https://issuetracker.google.com/issues/68897739#comment119
Read last comments ! You will realise.
rohanhole said:
Described in https://issuetracker.google.com/issues/68897739#comment119
Read last comments ! You will realise.
Click to expand...
Click to collapse
Prolly yeah. But i was able to unlock bootloader on 2 pixel 2 phones running 8.1. mine and my fiance. Prolly weird and rare bug