Related
Is it possible to have some custom ROMs for ZenFone 2 ZE500CL in future? Somebody hear me? Someone? People?
RusLion__ said:
Is it possible to have some custom ROMs for ZenFone 2 ZE500CL in future? Somebody hear me? Someone? People?
Click to expand...
Click to collapse
Currently trying to find devs to help me out with this, I have a bit of an Idea of what I'm doing but need help with making sure I've got the right build flags and toolchains to make a bootable aosp rom for this device.
AlexBodewig said:
Currently trying to find devs to help me out with this, I have a bit of an Idea of what I'm doing but need help with making sure I've got the right build flags and toolchains to make a bootable aosp rom for this device.
Click to expand...
Click to collapse
What about custom recovery? Do you have TWRP or CWM for our phone?
Right now its tethered, but I'm working on a safestrap to counter the lack of unlocked bootloader.
I would cry...in a good way, if you could get this phone safestrapped.
Also... How are some people unlocking there bootloaders with the Asus unlock tool, mine won't unlock. I've had 2 of these phones, both the same. No unlock.
Sent from my zf2e[ze500cl] using Tapatalk
robot_head said:
I would cry...in a good way, if you could get this phone safestrapped.
Also... How are some people unlocking there bootloaders with the Asus unlock tool, mine won't unlock. I've had 2 of these phones, both the same. No unlock.
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
I think it might be because technically the ZF2e and the ZE500CL are not the same phone. I mean they have the same processor, screen, and body, but the ZF2e is locked to AT&T, which might be blocking the bootloader unlock.
cmendonc2 said:
I think it might be because technically the ZF2e and the ZE500CL are not the same phone. I mean they have the same processor, screen, and body, but the ZF2e is locked to AT&T, which might be blocking the bootloader unlock.
Click to expand...
Click to collapse
It could also be a lack of space on the internal storage but it's more likely that it won't unlock because of the serial number indicating that it is a zf2e and not the ze500cl.
RusLion__ said:
Is it possible to have some custom ROMs for ZenFone 2 ZE500CL in future? Somebody hear me? Someone? People?
Click to expand...
Click to collapse
I've cracked down this bad boy at last, Got unlocked bootloader and a fully working TWRP 2.8.7.0, Will make a thread soon....
Ze500cl has bootloader unlocked, what about att version zf2e?
Sent from my zf2e[ze500cl] using Tapatalk
robot_head said:
Ze500cl has bootloader unlocked, what about att version zf2e?
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
I don't know if it's possible to unlock the ZF2E bootloader. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-ze500cl-unlock-app-t3257815 ( I used this app to unlock my 500CL)
@NerdyNerd9000 any news on Roms. I had a horrible time with the updater script. I have a rom, basically a zip file with a system folder and meta-inf
Sent from my zf2e[ze500cl] using Tapatalk
robot_head said:
@NerdyNerd9000 any news on Roms. I had a horrible time with the updater script. I have a rom, basically a zip file with a system folder and meta-inf
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
I've ported boot and recovery from zenfone5 successfully , but I need help flashing the system folder.
@muhammad_fatah could you post your work. I've tried zipME, android script creator, kitchen, but nothing i do can create a working updater script to flash anything. AND most zips won't flash, like certain themed apps, mods, almost nothing will flash except super su and xposed
Sent from my zf2e[ze500cl] using Tapatalk
robot_head said:
@muhammad_fatah could you post your work. I've tried zipME, android script creator, kitchen, but nothing i do can create a working updater script to flash anything. AND most zips won't flash, like certain themed apps, mods, almost nothing will flash except super su and xposed
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
I don't know if this might help (the second guide, flash full ROM):
forum.xda-developers.com/zenfone2/general/how-to-flash-ota-rom-twrp-t3209545
I know how to flash, its this raggedy little phone controlled by att.
Sent from my zf2e[ze500cl] using Tapatalk
robot_head said:
@muhammad_fatah could you post your work. I've tried zipME, android script creator, kitchen, but nothing i do can create a working updater script to flash anything. AND most zips won't flash, like certain themed apps, mods, almost nothing will flash except super su and xposed
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
Same sh*t bro. I tried every single way of making a working updater-script. Gives binary error every time. I'll post my work as soon as I get free time.
---------- Post added at 06:41 PM ---------- Previous post was at 06:16 PM ----------
robot_head said:
@muhammad_fatah could you post your work. I've tried zipME, android script creator, kitchen, but nothing i do can create a working updater script to flash anything. AND most zips won't flash, like certain themed apps, mods, almost nothing will flash except super su and xposed
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
Porting, flashing won't help. Need to compile CM ROM from source. Do you have the device and vendor tree of our phone? Kernel source is already there , need device and vendor tree to get started porting cm.
I do not, and with my locked bootloader (att) i can't flash another kernel. So any rom i flash has to be based off stock, or so heavily modded it looks like cm. ??
Sent from my zf2e[ze500cl] using Tapatalk
AlexBodewig said:
Right now its tethered, but I'm working on a safestrap to counter the lack of unlocked bootloader.
Click to expand...
Click to collapse
UNLOCK USING ASUS UNLOCK Tool
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ZE500CL_UnlockTool_0909.apk
jbetro said:
UNLOCK USING ASUS UNLOCK Tool
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ZE500CL_UnlockTool_0909.apk
Click to expand...
Click to collapse
This method doesn't work for some. Particularly those with the Zenfone 2E variant.
Correct, this is the 2e (economy) version from att, anything att nowadays is unlockable, i even bought a samsung s5 before i knew that, you can't even root that phone, so needless to say, att users have to sit on the bench while everyone else gets to ride the rides
Sent from my zf2e[ze500cl] using Tapatalk
So i recently updated to the new mhc19l version on my nexus 6p (this is not android N, just the latest android update for the 6p). I did it via the flashfire method following this youtube video: https://www.youtube.com/watch?v=cvs0JQswTWw&feature=youtu.be
I dont have multirom so i didnt do the stuff it mentioned about that. At first I thought I was successful and everything was working great. I reflashed xposed to the latest version, and updated my elemental X kernal too.
But now when I do anything with the camera the phone gets really weird. Post reboot the camera preview will work only once. If I take a photo it crashes. And every time I try to do anything with the camera involved the thing will crash and not even load preview anymore. That includes 3rd party apps like snap chat. Also I can't edit quick setting tiles in system ui as it tells me system ui tuner has crashed, but that i can live with. The camera issues I can not live with.
None of that happens with my rooted 6p on the same build. I think you need to look at xposed, the kernel changes and all the other jiggerypokery you've done. I'd do begin by reflashing the factory image and do this manually either using Heisenberg's extremely clear guide, or by the flash-all.bat command that google supplies in the factory build. Then you can check camera, flash recovery (again, using Heisenberg's guide, it takes but a couple of commands), then root, add xposed, kernels and all that special sauce. Do it step by step, then you'll know when something goes wrong and only have to fix that.
Thank you for your help. I'll check that out. Do you think it may be because I updated from a pretty old build? (808L) I skipped a few updates and went right to the latest one, could that cause any problems?
Not really. I think it's because you've done too much using a tool and without checking things after each step. Stop using tools like flashfire when you don't understand what they do and get yourself up to speed with using the commands. After that, you'll spot where things have gone wrong and be able to fix or troubleshoot it within the community. No one can help you when it's an issue that could caused by one or more of a hundred things you've tinkered with.
It's not hard and worth the little bit of busy work and brain thought. You'll enjoy it!
Yea I like to tinker and stuff. It's just the customizations with dashclock and stuff that I don't want to lose. But I did app backups so hopefully I won't.
Something probably went wrong during the flash process. I highly doubt xposed or kernel modifications are to blame. I keep 12 xposed modules running at all times with kylo kernel which I have heavily modified with EX kernel app. Read Heisenberg's guide and learn to flash images properly and you should be good to go.
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You can't flash anything with a locked bl. Locking the BL is nothing but trouble if you like to tinker.
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
dirtyuzbek said:
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
Click to expand...
Click to collapse
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Any Advice ?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
naruto.ninjakid said:
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
Click to expand...
Click to collapse
Look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Deception isn't necessary anymore, as long as you use the latest TWRP you should have no problems.
did it flash the vendor?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
and313 said:
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Heisenberg said:
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Click to expand...
Click to collapse
Right... I did not think that the first step (enable bootloader unlock from dev options) is actually necessary.
Sent from my Nexus 6P using Tapatalk
About a year ago, I tried installing a custom ROM for my ASUS ZenFone 5 (A500CG). I went through all the shenanigans of doing so (rooting, flashing, unlocking the bootloader). After succeeding in installing the ROM, I discovered the so-called "FREEZING BUG" of the Z5 wherein if you tried to unlock the bootloader, the phone would freeze/hang then reboot invariably. I didn't really like the ROM anyway, so I went back to my stock KitKat, also thinking that it would fix the "freezing". After the return, my Z5 still experiences the bug (FREEZING). With a bit of research, I found out that unlocking the Z5's bootloader is the culprit. I went to re-lock it, and as if nothing happened, it was fixed! No more freezing!
And today, I heard of CyanogenMod 13.1. I knew the Z5 would not be blessed with the new Android 6.0 update along with its 1st-Generation siblings. So I thought, "Meh. I'll give the custom ROM a shot." And I indeed liked CM 13.1. I wanted to keep it, but because I had to unlock my bootloader to get it to work, I'm back with the old, dreaded freezing bug.
Sorry for the long story, but my question is this:
Is it possible to keep the CyanogenMod with a locked bootloader? If so, how?
And if not, is there any way at all to fix the "FREEZING" problem of the Z5 whenever you try to unlock its bootloader?
Any help is appreciated!
cnswico said:
About a year ago, I tried installing a custom ROM for my ASUS ZenFone 5 (A500CG). I went through all the shenanigans of doing so (rooting, flashing, unlocking the bootloader). After succeeding in installing the ROM, I discovered the so-called "FREEZING BUG" of the Z5 wherein if you tried to unlock the bootloader, the phone would freeze/hang then reboot invariably. I didn't really like the ROM anyway, so I went back to my stock KitKat, also thinking that it would fix the "freezing". After the return, my Z5 still experiences the bug (FREEZING). With a bit of research, I found out that unlocking the Z5's bootloader is the culprit. I went to re-lock it, and as if nothing happened, it was fixed! No more freezing!
And today, I heard of CyanogenMod 13.1. I knew the Z5 would not be blessed with the new Android 6.0 update along with its 1st-Generation siblings. So I thought, "Meh. I'll give the custom ROM a shot." And I indeed liked CM 13.1. I wanted to keep it, but because I had to unlock my bootloader to get it to work, I'm back with the old, dreaded freezing bug.
Sorry for the long story, but my question is this:
Is it possible to keep the CyanogenMod with a locked bootloader? If so, how?
And if not, is there any way at all to fix the "FREEZING" problem of the Z5 whenever you try to unlock its bootloader?
Any help is appreciated!
Click to expand...
Click to collapse
Yes you can relock it Flash android M and after lock bootloader. http://forum.xda-developers.com/android/help/root-zenfone-5bootloader-unlock-recovery-t2896589
swiczak said:
Yes you can relock it Flash android M and after lock bootloader. http://forum.xda-developers.com/android/help/root-zenfone-5bootloader-unlock-recovery-t2896589
Click to expand...
Click to collapse
It is a false information.
Custom kernel for CM13 (or any Marshmallow custom rom) does not has a signature. (kernel by Asus has it)
So locked bootloader stop booting due to it.
Ok. I guess a custom ROM really just can't work with a locked bootloader. However, is there really even a way to fix the ZenFone 5's "freezing" problem even with the bootloader unlocked?:crying:
cnswico said:
Ok. I guess a custom ROM really just can't work with a locked bootloader. However, is there really even a way to fix the ZenFone 5's "freezing" problem even with the bootloader unlocked?:crying:
Click to expand...
Click to collapse
Unfortunately, for now, you can't, either you get the freeze bug or the camera bug when you unlock the bootloader on some ZF5s.
jephimax said:
Unfortunately, for now, you can't, either you get the freeze bug or the camera bug when you unlock the bootloader on some ZF5s.
Click to expand...
Click to collapse
Damn ASUS wouldn't give the Z5 the 6.0 update. Perhaps they want you to get a new phone? I really needed the new 6.0 stuff.
Anyway, thanks for the heads-up!
cnswico said:
Damn ASUS wouldn't give the Z5 the 6.0 update. Perhaps they want you to get a new phone? I really needed the new 6.0 stuff.
Anyway, thanks for the heads-up!
Click to expand...
Click to collapse
Actually if i get a new phone it won't be another Asus. They need to know
There's no fully solution for unlocking bootloader and they are not giving the private sources for signing kernels, or unlocking bootloader properly, or about GPS/FM bug.
If you want to get these features work proper only Asus can provide this things.
U can try AOSP 5.0.2
Sent from my ASUS_T00F using XDA-Developers mobile app
adhit_barker said:
U can try AOSP 5.0.2
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
No good, bruh. I need a 6.0 ROM. Or if you can suggest a way to use an SD card as adopted storage for non-Marshmallow firmwares.
Sent from my ASUS_T00J using XDA-Developers mobile app
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Unless you are on the totally stock system then I wouldn't lock your bootloader.
vjyrdy said:
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Click to expand...
Click to collapse
Technically i believe you could and would still be rooted, but I've always seen it advised NOT to lock your bootloader again until you are on 100% stock (right now your boot.img isn't stock since it's patched for root).
mrcooter said:
Technically i believe you could and would still be rooted, but I've always seen it advised NOT to lock your bootloader again until you are on 100% stock (right now your boot.img isn't stock since it's patched for root).
Click to expand...
Click to collapse
So you mean I would not be able to re-lock bootloader even if I had installed Nougat, isn't it?
thats because we are using tampered boot.img. Is it possible in-future we can use original boot.img ?
vjyrdy said:
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Click to expand...
Click to collapse
If you relock your bootloader with anything other than a factory image you will brick your device.
vjyrdy said:
So you mean I would not be able to re-lock bootloader even if I had installed Nougat, isn't it?
thats because we are using tampered boot.img. Is it possible in-future we can use original boot.img ?
Click to expand...
Click to collapse
If you modify your device, bottom line, you should leave it unlocked so you can fix things or go back to stock if needed, otherwise you could turn it into a paper weight. Even if root is done without modifying the boot.img, I would still keep it unlocked as there are usually still system changes.
mrcooter said:
If you modify your device, bottom line, you should leave it unlocked so you can fix things or go back to stock if needed, otherwise you could turn it into a paper weight. Even if root is done without modifying the boot.img, I would still keep it unlocked as there are usually still system changes.
Click to expand...
Click to collapse
This.
With a modified system or other partition, you risk a brick.
If anything goes wrong, once the bootloader is locked you can't fix it.
DO NOT LOCK THE BOOTLOADER ON ANY PHONE IF ROOTED!!!!!
See this thread:
https://forum.xda-developers.com/essential-phone/help/bricked-essential-phone-t3714809
When I boot my k20 plus I get "cannot verify corruption. Lock your boot loader" it sticks there until I press power. How do I get rid of that without locking bootloader?
zlost1 said:
When I boot my k20 plus I get "cannot verify corruption. Lock your boot loader" it sticks there until I press power. How do I get rid of that without locking bootloader?
Click to expand...
Click to collapse
K20+?? You are in the wrong thread sir. Please search for your phones XDA forum and ask in the rooting thread there. This is the essential ph-1 forum. Good luck!
Sent from my PH-1 using XDA Labs
swiftbones74 said:
K20+?? You are in the wrong thread sir. Please search for your phones XDA forum and ask in the rooting thread there. This is the essential ph-1 forum. Good luck!
Click to expand...
Click to collapse
Doesn't really matter what phone. If. It were a rocket with a string attached the question would have the. Same answer.
zlost1 said:
Doesn't really matter what phone. If. It were a rocket with a string attached the question would have the. Same answer.
Click to expand...
Click to collapse
This ain't the rocket and thread forum or the whatever dumb other thing forum so it really doesn't matter what the answer is.
Sent from my PH-1 using XDA Labs
I don't see anything about a phone type in the original question. Only that he asks about locking the boot loader.
zlost1 said:
I don't see anything about a phone type in the original question. Only that he asks about locking the boot loader.
Click to expand...
Click to collapse
Lol you are in the wrong thread genius. I don't know who "he" is but assume you are referring to the OP and in that case "He" doesn't need to mention anything about any specific phone because he is already posting in the right place. The question you asked about your k-whatever phone will most certainly be different for every phone. Good luck and who knows maybe a forum moderator can help you?
Sent from my PH-1 using XDA Labs
Also this. https://forum.xda-developers.com/lg-k20-plus/help
MOD EDIT
You are one trippy person ? if you really feel the need to post about your LG phone in the mata thread go right ahead buddy.
Sent from my PH-1 using XDA Labs
MOD EDIT
It's worth noting that the Essential PH-1 uses an A/B partition system so any advice given here would not be helpful in the slightest for devices that don't have the same file system. Quickly doing a search of your phone reveals it's not an A/B partitioned system so following advice here could potentially lead to you actually destroying your phone.
could you lock the BL once rooted if in fastboot mode it lists device tampering = false?
Wonderful reply
tech_head said:
This.
With a modified system or other partition, you risk a brick.
If anything goes wrong, once the bootloader is locked you can't fix it.
DO NOT LOCK THE BOOTLOADER ON ANY PHONE IF ROOTED!!!!!
See this thread:
https://forum.xda-developers.com/essential-phone/help/bricked-essential-phone-t3714809
Click to expand...
Click to collapse
Thanks, this reply should be pinned to the top of the thread. It is crucial information for our dear noobies
swiftbones74 said:
Lol you are in the wrong thread genius. I don't know who "he" is but assume you are referring to the OP and in that case "He" doesn't need to mention anything about any specific phone because he is already posting in the right place. The question you asked about your k-whatever phone will most certainly be different for every phone. Good luck and who knows maybe a forum moderator can help you?
Sent from my PH-1 using XDA Labs
Also this. https://forum.xda-developers.com/lg-k20-plus/help
Click to expand...
Click to collapse
Just an opinion, but...there are rules for posting in forums that Dev's, no matter how over worked and underpaid/appreciated should follow as well. Teach by example not proxy. Applaud the calm gentleman who responded with eloquent grammar and poise.
NaterTots said:
Unless you are on the totally stock system then I wouldn't lock your bootloader.
Click to expand...
Click to collapse
If you patched boot.img (Android 11 stock) with magisk and then lock bootloader... Will that be possible since it's stock rom or it altered because of the boot.img patch?
rossrosh007 said:
If you patched boot.img (Android 11 stock) with magisk and then lock bootloader... Will that be possible since it's stock rom or it altered because of the boot.img patch?
Click to expand...
Click to collapse
I don't know.
I just flashed latest Nougat and wiped my device. I am trying to find out how to re-lock BL. It seems that Fastboot oem lock doesn't work. Anyone know the function to use?
Ascertion said:
I just flashed latest Nougat and wiped my device. I am trying to find out how to re-lock BL. It seems that Fastboot oem lock doesn't work. Anyone know the function to use?
Click to expand...
Click to collapse
Don't do it...
Leave it unlocked... You're just inviting issues you can't fix...
Sent from my PH-1 using Tapatalk
rignfool said:
Don't do it...
Leave it unlocked... You're just inviting issues you can't fix...
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I am trying to sell it. If I leave bootloader unlocked, it may deter buyers. Are you saying relocking bootloader when it's 100% stock doesn't work? Why?
Ascertion said:
I am trying to sell it. If I leave bootloader unlocked, it may deter buyers. Are you saying relocking bootloader when it's 100% stock doesn't work? Why?
Click to expand...
Click to collapse
If you are truly 100% stock... Then sure... Lock away...
I'm not going to spell it out... For fear of the stupid...
But substitute 'flashing' for 'oem'...
Sent from my PH-1 using Tapatalk
rignfool said:
If you are truly 100% stock... Then sure... Lock away...
I'm not going to spell it out... For fear of the stupid...
But substitute 'flashing' for 'oem'...
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
thanks very much. This worked and device is not bricked! :good:
Ascertion said:
thanks very much. This worked and device is not bricked! :good:
Click to expand...
Click to collapse
If you just flashed Oreo, then it is beta.
Typically you don't lock the boot loader with beta software running.
If something goes wrong, and it can, you potentially won't be able to flash a downgrade.
I understand your reasoning, but it's normally a bad idea.
Although, essential doesn't instruct you to unlock the bootloader to install the Oreo beta builds.
I side loaded mine through the stock recovery and only unlocked a few weeks afterwards.
tech_head said:
If you just flashed Oreo, then it is beta.
Typically you don't lock the boot loader with beta software running.
If something goes wrong, and it can, you potentially won't be able to flash a downgrade.
I understand your reasoning, but it's normally a bad idea.
Click to expand...
Click to collapse
It's all good. I restored to Nougat before I re-locked. :good: