Related
DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
INTRODUCTION
This thread is mainly intended for devs (pro devs don't really belong here because they're pro and this thread is useless), for someone who need help to continue the work for Nova and fix the bugs on Pie (not many left). I'll help as long as you can speak English xD (no google translate because it can cause misunderstandings). However, don't expect me to spend the same time into this as i''ve did when i've had the phone. Yes, i no longer have the phone (it's still dead) and if you're not up to date with that, then you can read the announcement here and i've mentioned that i've got a new phone here. On top of this, i can't build anymore because i can't sign up on Google Cloud Platform anymore. I've wrote about this here at the hidden content (below as a side note).
Users can also help with doing researches, testing things and logs.
I don't know if i'll consider to continue working on it myself alone without the phone. I'd need at least to be able to build and then i'd need people to test new builds / flashable zips. At some point i might consider that because i'm missing this phone and the community xD.
SOURCES
Device: https://github.com/skinzor/android_device_huawei_hwcan/tree/lineage-16.0-last
Vendor: https://github.com/skinzor/proprietary_vendor_huawei/tree/lineage-16.0-last
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
Click to expand...
Click to collapse
There's two branches:
1) lineage-16.0: those ones were used when i've booted Pie the first time. Remember that i've wrote about it here? Those ones were updated from mido's ones.
2) lineage-16.0-last. those ones are the last ones and updated, which i've used in my last build. Those ones were continued from previous branch and updated from tissot ones which were / are updated by another dev (not the same dev as on mido). I recommend to continue with this branch, but it's up to you. You might not be able to get a successful or bootable build anymore with lineage-16.0 branch anyway because lineage's sources were updated since then.
I've used mido's trees as reference for lineage 14 and 15 trees too. You can figure that yourself if you check mido's trees and then Nova's ones, as i've cherry-picked the commits. Why did i use mido's trees? Because:
1) It has the same qcom chipset as Nova.
2) It is a popular phone.
3) A good dev was working on it.
4) It has official lineage support.
Now you might ask why i haven't did myself everything from scratch. Well, as a newbie dev, it would've been much harder and would've took much more time. Also, i'd say that there's no point at all to do something from scratch when it was already done unless you want to go the "hard" way, assuming you have time and want to learn more. I've still learnt a lot since i've started.
There are "universal" commits which are about fixes / improvements that can be related to e.g. the android version or the qcom chipset and those commits are usually found in many device trees, so you just cherry-pick them. A good example would be this commit: hwcan: Use mke2fs to create ext4 images.
FIXING THE BUGS OF LINEAGE 16 / PIE
I assume that you've used lineage-16.0-last branch as i've recommended. I no longer remember what bugs had my last build, but i think that the bluetooth was working, while it wasn't working in the build made from old lineage-16.0 branch. However, i remember that it had a new bug and as far as i remember, it was the RIL, but the baseband was showing up. I think i've tried to fix it and i've got it working (i remember that it was about the blobs), but i don't remember how. As of typing now, i've looked into the logcat which i still have and i've seen this:
Code:
F linker : CANNOT LINK EXECUTABLE "/vendor/bin/tftp_server": library "liboemaids_vendor.so" not found
That kind of error is self explanatory: the blob / lib is missing. After i've seen this, i've remembered that it's a new blob which got added in the original commit and which i've cherry-picked here. I didn't include that blob for a reason, but i don't remember that reason lol (it's not that i've forgot it, but i've skipped it for a reason). I remember that back then i've added the blob manually after i've seen the error, but i don't remember if that's what fixed the RIL, so you can try that and let me know.
As i've said already, i don't remember what bugs had that build besides the RIL, so you can try it and let me know.
At the introduction i've mentioned that i can help. I'll help only here on XDA in this thread because it may help other people too if they're having the same error / problem and after all, it's nice to have a thread like this in my opinion.
You can attach the log or paste it to gist github, pastebin, del.dog or any pasting website, but don't paste it in the XDA post because it just sucks.
Click to expand...
Click to collapse
DOWNLOADS
MEDIAFIRE | ANDROIDFILEHOST
As i've recommended to use lineage-16.0-last branch to build / continue the development, i also recommend to flash that build.
The build from lineage-16.0 branch folder doesn't boot. Back then, when i've seen that it doesn't boot and took a look at the logcat, i've tried the graphic blobs from the tree of zenfone 3 and that one was using them from nokia 7 plus (based on the commit). I had two zips in my PC and i've uploaded both. The first one created is graphic_pie_blobs_zenfone3_nokia_7_plus.zip and the second one sdm_blobs_zenfone3_nokia7_plus.zip, so you flash them in that order. As i've mentioned in that post in which i've said that i've booted Pie, there is some lag / glitches while scrolling, due the display / graphic blobs.
ENDING
As i've promised, i've pushed the tree sources and uploaded my first and last build. The reason i'm willing to help in fixing the bugs is because i'm missing this phone and this community here on XDA (as i've expected xD). It was fun and thanks to this phone and y`all for your support and kind words, i've learnt so many things in this journey. That's simply unforgettable for me.
Hopefully someone will jump on and continue the development further. I'll be here to help.
XDA:DevDB Information
[DEV][9.0] LineageOS 16, ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
ROM OS Version: 9.x Pie
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Testing
Created 2019-01-02
Last Updated 2019-01-05
Reserved
Reserved
Thank you for all the hard work you put into this. I would try to follow the leads, but for me this phone is dead now. I had hoped it would be something, but naw, just a hunk of something. Maybe someone can pick it up and go with it, encouraged everyone to try. If you are thinking about it Robert @#Henkate will help you. Great person, and this phone got me to know him so boom, good phone.
Maybe this should be in off topic thread, but I will post here.
Thank you for the great work that you have done. You gave us nougat, oreo, almost a pie. LineageOS 15.1 is the best firmware I have ever used. EmUi far behind. Thanks again a lot. Pie is full of bugs (I have already tried), counted a huge list of 10 items, but I think it's time to relax. You gave nova a second life and for that I am grateful to you. I found out that you are switching to another phone. Good luck in developing it, you are a good developer, the main thing is to believe in yourself!
Hi enkate... does wifi calling work on 16 ?
thanks
virusdunil said:
Hi enkate... does wifi calling work on 16 ?
thanks
Click to expand...
Click to collapse
He has no way to check. Maybe someone who has flashed it could test.
wow！thx a lot，I will try it now！
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Alee.se said:
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Click to expand...
Click to collapse
With the first build go two files, except for the firmware, responsible for the display. Flash them after flash lineage 16 last build and everything will work
Logcats
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Vinnom said:
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Click to expand...
Click to collapse
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Disable out sim card
AssasinAkindinov said:
Disable out sim card
Click to expand...
Click to collapse
ye, phone in airmode workrd normally,
AssasinAkindinov said:
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Click to expand...
Click to collapse
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Sorry guys, no mean to be rude here, but this thread is for development purposes. My point in posting was to give a logcat and receive help to try and fix the bugs I found. I know that when possible, #Henkate gonna take a look and give some directions, so work can be done. So, if you wanna test and see if the rom works for you, that's fine, but provide logs, please. It's good to have other logs and be able to compare if the bugs are the same and I think it can help development a lot (no need to flood with logs either, be reasonable).
Unbrick no screen.
To repair the phone (when there is more image) it must start in fastboot mode and then flash boot image) wait for the phone to go off or remove the battery. When it is off plug the usb cable c on your huawei nova and the phone will show that the phone is charging. Now you can reflash another rom but not lineage os 16. Sorry i use google translation
Android 9 with jdi screen
Android 9 with jdi screen
Amazing near.
As it is known, custom firmware was not friends with the jdi screens.
And here came LOS16 on Android 9. Read reviews that it is now not usable even on smartphones with "normal" screens, what can we say about JDI
But from the realization that he had bought a new phone and having a lot of time, the thought crept in to try to put a fresh custom for total disappointment in his smartphone and quiet use of the new.
However, not everything is so simple. After the first launch, the screen began to flicker well, I thought everything had arrived, now it will get dark and the sensor will fail. Cured with just one reboot. more of this did not happen.
Sim cards did not pull out (I have 2 of them), some wrote that because of them there were some problems crashing and rebooting the system (I don’t have that)
After a night out, the interface began to respond with a delay of 0.5 seconds. (It was cured by a complete reboot) ..
Quickstep launcher is often closed with an error
The camera does not remove the drain, installed from the playlist of the market works without comments.
The navigation bar disappeared after a telephone conversation, when the interlocutor first completed the call (It was decided to reboot)
Vkontakte application crashes, but I use Kate Mobile, it flies with a bang.
YouTube crashes
The sound from the conversational dynamics is quiet, I think you can fix it in the mixer_paths but this is not exactly
Waiting for the moment until the screen fails.
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
R0mi4 said:
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
Click to expand...
Click to collapse
Ты все посты будешь переводить и сюда кидать?) (It is joke)
Hello all,
I present to you my new and updated guide on unlocking your Redmi note 8 bootloader.
Warning: any changes you choose to make are your responsibility, I'm not to be held accountable of any damaged or bricked phones and dead SD cards, you choose to make modifications to your device and these modifications can brick you device.
For the last time if you don't know what you're doing I advise you to learn about bootloader unlocking .
That said, let's begin:
You might not know but Xiaomi doesn't require you to apply for unlocking you bootloader anymore which is why I'm making this guide.
On another note remember that this process will wipe all data from your phone
And be careful charge your battery to a sufficient degree (about 80%) to avoid you device shutting down in the middle of that process that would be a shame really and proceed step by step to insure that you haven't missed on anything
Ok, here we go:
1. Enable developer options
2. Enable "OEM unlocking" & "usb debugging"
3.Login in to your Xiaomi account from within your phone and make sure the account is linked to your phone (it is located in additional settings -> developer settings -> Mi unlock status (it should say added successfully)
4. Download the Xiaomi unlock tool to your computer: https://en.miui.com/unlock/download_en.html
5 .Reboot your phone to fastboot mode ( by pressing volume + power ) on boot
6.Connect your phone to your PC and launch the Mi unlock tool (while in fastboot mode)
7. Login from within the app with your credentials
8.After that follow the instructions the program tells you
Remember this process is very long lasting it could take up to 720 hours to unlock the bootloader ! You can still use your phone in that period of time
For more info, here is the source I took all of is info from: https://c.mi.com/thread-1635834-1-1.html
If there is anything I missed or got wrong please feel free to correct me on anything regarding this procedure
Goodbye !
I successfully unlocked my device following the method above and it took me 6 days of waiting but it was worth it
sm-T116 said:
Remember this process is very long lasting it could take up too 720 hours to unlock the bootloader ! make sure you're not using your phone in that period of time
Click to expand...
Click to collapse
I don't think that is what they advise, you must be using your phone in a normal conditions since the 7 days waiting time is made to prevent bulk rebranding (localization changes)
RAR1991 said:
I don't think that is what they advise, you must be using your phone in a normal conditions since the 7 days waiting time is made to prevent bulk rebranding (localization changes)
Click to expand...
Click to collapse
I wasn't aware of that ! thanks for the feedback
I will correct the post
This essentially the same as what's posted here: https://forum.xda-developers.com/re...de-unlocking-bootloader-twrp-rooting-t4031831
sm-T116 said:
You might not know but Xiaomi doesn't require you to apply for unlocking you bootloader anymore which is why I'm making this guide.
Click to expand...
Click to collapse
Well the whole guide is....let's say misleading....but I won't blame you coz you read the source post on that mi community....actually you're still required to apply for permission to unlock bootloader...but....only if you have a new mi account...if you have an old mi account from which you already applied for permission once doesn't matter 2 years ago or 5 years ago, you won't be needing any more permission for that account...but for new accounts you still gotta apply for permission.
the_weird_aquarian said:
Well the whole guide is....let's say misleading....but I won't blame you coz you read the source post on that mi community....actually you're still required to apply for permission to unlock bootloader...but....only if you have a new mi account...if you have an old mi account from which you already applied for permission once doesn't matter 2 years ago or 5 years ago, you won't be needing any more permission for that account...but for new accounts you still gotta apply for permission.
Click to expand...
Click to collapse
Hello, thanks for your feedback, that said, with all the respect, I think you might be wrong because I've read in multiple sources that xiaomi doesn't require the unlocking permission anymore simply because their webiste doesn't display any info about unlock permission and it just prompts to log in to your xiaomi account and that's all.
However I've done some research and all I could find is articles which state that it's not required anymore.
Here is one of the sources I read: https://c.mi.com/thread-1857937-1-1.html
If you would please further clarify the process so that I could better understand.
Thank you !
* Disclaimer: I've only tested this on a G998B/DS Exynos S21 Ultra 5G, knox tripped and rooted with Magisk *
* DO NOT TRY ON ANY VARIANT OTHER THAN G998B/DS Exynos S21 Ultra 5G, I will be no responsible if you do *
* If it works for you on other variants, please report it so I can add it to the post, thanks *
As we all know, Samsung phones render a large, ugly disclaimers on the initials bootscreens/bootlogo when booting the phone, after it has been bootloader-unlocked (e.g. to root it via Magisk, to install TWRP, etc.)
Flashing this tweaked up_param partition on Odin will restore back a nice, clean bootscreen that won't scare the hell out of you every time you turn it on
How to install
1. Open Odin 3.14
2. Select the attached clean_bootlogo.tar into the BL box (you can use any slot, really, but suggesting BL here as a best practice)
3. Start flashing
4. Enjoy!
If you like this, leave your or thanks!
Hello there, firstly, I would like to thank you for your hard work into coming up with this, and yes it works great on my S21 Ultra Exynos G99B/DS.
I would love to suggest a feature/addon: Remove the press power button to continue text. (If it is possible)
Also just to point out, this post would get so much more attention if it was under "How To Guides" instead of "Development".
Anyways thanks you so much for your hard work
DaGalaxySheep said:
Hello there, firstly, I would like to thank you for your hard work into coming up with this, and yes it works great on my S21 Ultra Exynos G99B/DS.
I would love to suggest a feature/addon: Remove the press power button to continue text. (If it is possible)
Also just to point out, this post would get so much more attention if it was under "How To Guides" instead of "Development".
Anyways thanks you so much for your hard work
Click to expand...
Click to collapse
I intentionally left the "press the power button..." text on the screen, because once the bootloader is unlocked, and the phone takes you thru these screens, it will wait those ~8 seconds on that screen, unless you press the pwr button. So leaving there, lets the end user know they can skip it and get the system booted up faster.
However, I'll upload another version without the label
Works a treat bud! Thanks!
Thank you so much
rodrigofd said:
I intentionally left the "press the power button..." text on the screen, because once the bootloader is unlocked, and the phone takes you thru these screens, it will wait those ~8 seconds on that screen, unless you press the pwr button. So leaving there, lets the end user know they can skip it and get the system booted up faster.
However, I'll upload another version without the label
Click to expand...
Click to collapse
Hi has the version without the label been posted?
AAAAAA help me By mistake i flash it to SM-G996B/DS
My phone cant boot now, PC cant detect it.
It is possible to charge it but its drain battery continuously
So can I somehow recover my hard bricked s21+?
rodrigofd said:
* Disclaimer: I've only tested this on a G998B/DS Exynos S21 Ultra 5G, knox tripped and rooted with Magisk *
* DO NOT TRY ON ANY VARIANT OTHER THAN G998B/DS Exynos S21 Ultra 5G, I will be no responsible if you do *
* If it works for you on other variants, please report it so I can add it to the post, thanks *
As we all know, Samsung phones render a large, ugly disclaimers on the initials bootscreens/bootlogo when booting the phone, after it has been bootloader-unlocked (e.g. to root it via Magisk, to install TWRP, etc.)
Flashing this tweaked up_param partition on Odin will restore back a nice, clean bootscreen that won't scare the hell out of you every time you turn it on
How to install
1. Open Odin 3.14
2. Select the attached clean_bootlogo.tar into the BL box (you can use any slot, really, but suggesting BL here as a best practice)
3. Start flashing
4. Enjoy!
If you like this, leave your or thanks!
Click to expand...
Click to collapse
Hey buddy thank you so much for creating this... It is really scary indeed every time we boot to see that fear mongering screen.
I also wanted to ask if you have created the version without the "press the power button screen". Although I am not sure if it possible to bypass that 8 second screen.
Thank you and I hope you are well!
Ziomus said:
AAAAAA help me By mistake i flash it to SM-G996B/DS
My phone cant boot now, PC cant detect it.
It is possible to charge it but its drain battery continuously
So can I somehow recover my hard bricked s21+?
Click to expand...
Click to collapse
Did you manage to overcome it and fix your phone?
Yep, i send it to warranty. It is back to me with new motherboard, also new backplate without imei number on it.
Haha phone was knox 0x0 with new mobo
Just for one Day XD
So this file break hardware in other models xddd
Whole repair took 9 days.
Ziomus said:
Yep, i send it to warranty. It is back to me with new motherboard, also new backplate without imei number on it.
Haha phone was knox 0x0 with new mobo
Just for one Day XD
So this file break hardware in other models xddd
Whole repair took 9 days.
Click to expand...
Click to collapse
Well i'm glad it all worked out bud
I do know how to fix these warning images...
Is it okay to do it like this:
Edit param.bin (or up_param.bin)
Compress the bin file to a .img file instead of .tar file and flash it in TWRP, not Odin
TESTED!, THIS PARAM FILE WORKS NICELY ON ALL GALAXY S20 SERIES TOO.
Is there a similar fix available for the regular S21 G991B
mrao said:
Is there a similar fix available for the regular S21 G991B
Click to expand...
Click to collapse
You should ask that in a thread there... The dev. of this mod here has disappeared from the face of XDA for a long time now, and no one else will answer here unfortunately.
Is it possible to customize the boot logo? (e.g. place own one instead "Samsung Galaxy")
Ziomus said:
Yep, i send it to warranty. It is back to me with new motherboard, also new backplate without imei number on it.
Haha phone was knox 0x0 with new mobo
Just for one Day XD
So this file break hardware in other models xddd
Whole repair took 9 days.
Click to expand...
Click to collapse
Here the same .. flashing seems be fine but directly after reboot black screen of death …. Buttons doesn’t react on any combination seems is death lol … also Samsung smart switch doesn’t see the phone anymore no change too reflash it back …
Samsung s21 send back for warranty 4 days old lol
MichelH1973 said:
Here the same .. flashing seems be fine but directly after reboot black screen of death …. Buttons doesn’t react on any combination seems is death lol … also Samsung smart switch doesn’t see the phone anymore no change too reflash it back …
Samsung s21 send back for warranty 4 days old lol
Click to expand...
Click to collapse
Strange, could you post all the steps of what you did to reach a brick?
It must be something wrong you did at some point and it went sideways, or you just missed something?
babyboy3265 said:
Strange, could you post all the steps of what you did to reach a brick?
It must be something wrong you did at some point and it went sideways, or you just missed something?
Click to expand...
Click to collapse
I downloaded this tar file , reboot my phone in download mode insert in BL slot the tar file start enable reboot boem phone was death … really nothing more
How hard would it be to port this to the G998U?
MichelH1973 said:
I downloaded this tar file , reboot my phone in download mode insert in BL slot the tar file start enable reboot boem phone was death … really nothing more
Click to expand...
Click to collapse
So you had you bootloader unlocked, you were rooted and etc?
Greetins to all. Am a young enthusiast of tech and am a newbie here. So I got a note 9 from a friend but I think it has already been tempered with, cause I can't receive updates. So I decided to install a recent custom rom but can't find the oem unlock option in the developer menu... if it has been tempered with in anyway(rooting or custom rom), can I still install twrp ? So i can install a new custom rom ?
Model : SM-N960F exynos 9810
Base-Band version : N960NKOU3ETF2
Thank you
Take a look at this
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
VHFG22 said:
Take a look at this
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for this
i think this has something to do with theft protection. I got rid of it after connecting the phone to wifi. I assume it need to ensure that the device was reset properly, using your samsung account.
After connecting to wifi the OEM unlock switch, also was visible in the developer options.
Hi, let's see how to unlock the bootloader of the S23
Indeed you have to unlock it in order to root the phone or install TWRP and custom roms in the future
Before that some warnings :
THIS WILL ERASE YOUR DATAS (APP, FILES, PHOTOS), SO MAKE A BACK UP NOW
(so i recommand doing this just after getting the phone)
This might break the OTA updates, and might brake your warranty
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you don't know what you are doing
* before doing all this! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Ok, now, let's go :
1st step (on the phone) :
Go to settings -> About Phone -> Software Information -> Tap several times on Build Number to activate Developper Options
Go back (2 times) to glabal Settings -> Developer Options -> Tick OEM Unlocking ON and USB debugging ON
2nd step :
Power off your S23
Press volume Up AND Down together and at the same time plug the phone into your PC (powered on) with USB cable
Now you will get a warning message. Release the volume keys
Long press volume UP until you see another warning message asking you to confirm you want to unlock the bootloader
Again, this will factory reset your S23 and erase all your files !!!
Press volume UP 1 time to confirm, and let the device do it's things
Here you go your S23 will reboot, factory reseted and unlocked !
If you want to install TWRP i recommand doing that NOW because you will need to factory reset your phone again
You can install TWRP following this GUIDE (only for Galaxy S23 S911B) thanks to @afaneh92 and flash magisk from recovery to root your S23
And/Or you can root your device without TWRP by patching the boot img with magisk and flashing it with Odin i think. I will put a link if i find a guide
Give it a thanks if this helped you
fozzy056 said:
Hi, let's see how to unlock the bootloader of the S23
Indeed you have to unlock it in order to root the phone or install TWRP and custom roms in the future
Before that some warnings :
THIS WILL ERASE YOUR DATAS (APP, FILES, PHOTOS), SO MAKE A BACK UP NOW
(so i recommand doing this just after getting the phone)
This might break the OTA updates, and might brake your warranty
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you don't know what you are doing
* before doing all this! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Ok, now, let's go :
1st step (on the phone) :
Go to settings -> About Phone -> Software Information -> Tap several times on Build Number to activate Developper Options
Go back (2 times) to glabal Settings -> Developer Options -> Tick OEM Unlocking ON and USB debugging ON
2nd step :
Power off your S23
Press volume Up AND Down together and at the same time plug the phone into your PC (powered on) with USB cable
Now you will get a warning message. Release the volume keys
Long press volume UP until you see another warning message asking you to confirm you want to unlock the bootloader
Again, this will factory reset your S23 and erase all your files !!!
Press volume UP 1 time to confirm, and let the device do it's things
Here you go your S23 will reboot, factory reseted and unlocked !
If you want to install TWRP i recommand doing that NOW because you will need to factory reset your phone again
You can install TWRP following this GUIDE (only for Galaxy S23 S911B) thanks to @afaneh92 and flash magisk from recovery to root your S23
And/Or you can root your device without TWRP by patching the boot img with magisk and flashing it with Odin i think. I will put a link if i find a guide
Give it a thanks if this helped you
Click to expand...
Click to collapse
Sorry, but i think that a step is missing, here there is another step:
"Bypass Vault Keeper on Galaxy S23/S23 Plus/S23 Ultra
You must notify the Vault Keeper that you unlocked the device bootloader.
So, connect your phone to the internet connection.
Here, go to settings and enable the Developer option, as mentioned at the start.
Make sure to check that OEM unlocking toggle is enabled.
That’s it."
I'm not sure why but OEM Unlocking doesn't show up under developer options.
omerc10696 said:
I'm not sure why but OEM Unlocking doesn't show up under developer options.
Click to expand...
Click to collapse
Some variants cannot have unlocked bootloader. At least I read that..
Still will trip knox efuse right?
punkmonkey1984 said:
Still will trip knox efuse right?
Click to expand...
Click to collapse
Yes
pesa44 said:
Some variants cannot have unlocked bootloader. At least I read that..
Click to expand...
Click to collapse
Damn i hope not, I bought mine from google fi, I've read a few posts about it being locked until you've had your phone for 10 days or something like that, hasn't happened to me though even though I've had the phone since 2/17
omerc10696 said:
Damn i hope not, I bought mine from google fi, I've read a few posts about it being locked until you've had your phone for 10 days or something like that, hasn't happened to me though even though I've had the phone since 2/17
Click to expand...
Click to collapse
I bought mine from google fi too, I dont think its locked at all since the model U1 means factory unlocked. BTW are you able to use esim?
A warning i think should be added talking about the irreversible damage unlocking your boot-loader does like in the rooting post.
bipindr123 said:
A warning i think should be added talking about the irreversible damage unlocking your boot-loader does like in the rooting post.
Click to expand...
Click to collapse
I'm still unable to unlock bootloader, reading up on it apparently the chances of it being unlocked is slim. I was able to use esim, but had some trouble at first, I was trying to set my phone up while I was out of the house and it wouldn't activate, when I got home and was able to connect to wifi it activated with no trouble
omerc10696 said:
I'm still unable to unlock bootloader, reading up on it apparently the chances of it being unlocked is slim. I was able to use esim, but had some trouble at first, I was trying to set my phone up while I was out of the house and it wouldn't activate, when I got home and was able to connect to wifi it activated with no trouble
Click to expand...
Click to collapse
Some models cannot be unlocked.
You can't unlock bootloader on US models. No roots for US models
pesa44 said:
Some variants cannot have unlocked bootloader. At least I read that..
Click to expand...
Click to collapse
Like....no matter what? I can't find anything of how to get the option of OEM to enable
fozzy056 said:
Hi, let's see how to unlock the bootloader of the S23
Indeed you have to unlock it in order to root the phone or install TWRP and custom roms in the future
Before that some warnings :
THIS WILL ERASE YOUR DATAS (APP, FILES, PHOTOS), SO MAKE A BACK UP NOW
(so i recommand doing this just after getting the phone)
This might break the OTA updates, and might brake your warranty
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you don't know what you are doing
* before doing all this! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Ok, now, let's go :
1st step (on the phone) :
Go to settings -> About Phone -> Software Information -> Tap several times on Build Number to activate Developper Options
Go back (2 times) to glabal Settings -> Developer Options -> Tick OEM Unlocking ON and USB debugging ON
2nd step :
Power off your S23
Press volume Up AND Down together and at the same time plug the phone into your PC (powered on) with USB cable
Now you will get a warning message. Release the volume keys
Long press volume UP until you see another warning message asking you to confirm you want to unlock the bootloader
Again, this will factory reset your S23 and erase all your files !!!
Press volume UP 1 time to confirm, and let the device do it's things
Here you go your S23 will reboot, factory reseted and unlocked !
If you want to install TWRP i recommand doing that NOW because you will need to factory reset your phone again
You can install TWRP following this GUIDE (only for Galaxy S23 S911B) thanks to @afaneh92 and flash magisk from recovery to root your S23
And/Or you can root your device without TWRP by patching the boot img with magisk and flashing it with Odin i think. I will put a link if i find a guide
Give it a thanks if this helped you
Click to expand...
Click to collapse
So I was reading and it say there no bootloader for my model is there another safe way of