Related
Hi,
Apparently, I'm misunderstanding something. I'm trying to root my 2XL. I have unlocked the phone successfully, I believe. I have the notification screen at bootup. When I get to the task of flashing a factory image, I get the Failed notification, "FAILED (remote: Flashing is not allowed for Critical Partitions)". This occurs after ... writing 'bootloader_b'.
I was able to get Magisk installed but only 14.0 and I don't have root.
I haven't rooted anything in over 5 years so most of this stuff is pretty foreign.
Any advice would be welcome.
fastboot flashing unlock
then
fastboot flashing unlock_critical
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?
slingblade01 said:
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?
Click to expand...
Click to collapse
Unlock critical first then flash 8.1. Make a backup because this will wipe user data.
I am already unlocked and flashed 8.0 manually. I went to flash 8.1 today and got the OPs error. Are you saying that fastboot flashing unlock_critical will also wipe data? Damn that sucks if true.
SirVilhelm said:
I am already unlocked and flashed 8.0 manually. I went to flash 8.1 today and got the OPs error. Are you saying that fastboot flashing unlock_critical will also wipe data? Damn that sucks if true.
Click to expand...
Click to collapse
Oh yeah! It's definitely true. Unfortunately
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Thx you saved my life <3
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I get an error saying "device already unlocked" but it still won't let me flash my bootloader... (Hope you're still active here...)
clarkcant said:
I get an error saying "device already unlocked" but it still won't let me flash my bootloader... (Hope you're still active here...)
Click to expand...
Click to collapse
Are you on Pie or Oreo? Is your platform-tools up to date? Have you tried different USB A to USB C cables and ports?
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Thanks man u saved my life. btw im not using a pixel, im in a xiaomi a3 but it worked!!
It doesnt work ....Help me to unlock critical
sadatkabir55 said:
It doesnt work ....Help me to unlock critical
Click to expand...
Click to collapse
Without details from you, we can't help you. For example, are you on the latest update? What else did you try? What worked for you and what didn't? Seriously, we can't read your mind. We can't see your phone. We can't perform miracles. It's a bit tiresome to have to ask you for things you should have already provided so we CAN help you.
Since you haven't given any details for anyone to go on, all I can tell you is that depending on the version of Android you are running, the "unlock critical" command may no longer be required, in which case you will get a message when executing the command.
I did not notice this was the forum dedicated to Pixel devices, sorry. I re-did my message in the Oneplus Nord dedicated forum regarding my issue that, however, seems to be the same as the one people encountered here.
Here is the link if anyone feels like helping me : https://forum.xda-developers.com/t/...itions-need-assistance-details-below.4274551/
slingblade01 said:
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?
Click to expand...
Click to collapse
yeah he was like in 1 min
I have oneplus 8 5g IN2017. I was flashing the global rom.I unlocked the bootloader. but fastboot flashing unlock is taking too long. It just keep running and did'nt finish. Please guide. I am so tired of this.
Also Device is stuck in bootloader.
Khateeb2110 said:
I have oneplus 8 5g IN2017. I was flashing the global rom.I unlocked the bootloader. but fastboot flashing unlock is taking too long. It just keep running and did'nt finish. Please guide. I am so tired of this.
Click to expand...
Click to collapse
You'll need to read about your own phone. This thread is about the Pixel 2 XL. Different manufacturers tend to have different ways to unlock the bootloader.
Also, people who follow this thread are unlikely to know about OnePlus. Find a OnePlus-thread to ask for help.
So I flashed 3 ROMS from openkirin.net,
1. LOS
2. Carbon OS
3. RR Os
Everything is fine except the camera apps there. All three Roms have apps that just click normal pics whenever i switch to portrait mode (I must add they contain stock emui camera app) the apps just hangs.
Does anybody have a solution to this to take portrait mode photos on custom roms.
Or any camera ( can be third party ) that can allow me to do so.
Thanks in advance ?
MeChiku said:
So I flashed 3 ROMS from openkirin.net,
1. LOS
2. Carbon OS
3. RR Os
Everything is fine except the camera apps there. All three Roms have apps that just click normal pics whenever i switch to portrait mode (I must add they contain stock emui camera app) the apps just hangs.
Does anybody have a solution to this to take portrait mode photos on custom roms.
Or any camera ( can be third party ) that can allow me to do so.
Thanks in advance ?
Click to expand...
Click to collapse
Name any custom ROM. They're Camera are just bare bones. Having stock camera port is great actually. We can't really complain about camera since we don't have Gcam mod available for kirin devices.
Username.php said:
Name any custom ROM. They're Camera are just bare bones. Having stock camera port is great actually. We can't really complain about camera since we don't have Gcam mod available for kirin devices.
Click to expand...
Click to collapse
Am not complaining dude i was asking for a solution
MeChiku said:
So I flashed 3 ROMS from openkirin.net,
1. LOS
2. Carbon OS
3. RR Os
Everything is fine except the camera apps there. All three Roms have apps that just click normal pics whenever i switch to portrait mode (I must add they contain stock emui camera app) the apps just hangs.
Does anybody have a solution to this to take portrait mode photos on custom roms.
Or any camera ( can be third party ) that can allow me to do so.
Thanks in advance ?
Click to expand...
Click to collapse
Bro i too flashed lineage os beta 4 in honor 7x. But it has too many bugs. How to get back to stock oreo rom.. please help me bro
krishnapenn said:
Bro i too flashed lineage os beta 4 in honor 7x. But it has too many bugs. How to get back to stock oreo rom.. please help me bro
Click to expand...
Click to collapse
Do you even check the "Honor 7x Guides, News, & Discussion" forums lmao???
https://forum.xda-developers.com/honor-7x/how-to/getting-to-stock-emui-super-easily-t3804722
crayonicle said:
Do you even check the "Honor 7x Guides, News, & Discussion" forums lmao???
https://forum.xda-developers.com/honor-7x/how-to/getting-to-stock-emui-super-easily-t3804722
Click to expand...
Click to collapse
No need sir, I've already rolled back successfully to stock oreo Tom. BTW thank you for responding
krishnapenn said:
No need sir, I've already rolled back successfully to stock oreo Tom. BTW thank you for responding
Click to expand...
Click to collapse
Glad to hear that :good:
crayonicle said:
Glad to hear that :good:
Click to expand...
Click to collapse
Sir can you tell me how to relock the bootloader
krishnapenn said:
Sir can you tell me how to relock the bootloader
Click to expand...
Click to collapse
Follow this procedure:
Dr.Anshuman said:
if you have unlocked your bootloader status and you want your original 'Locked' status instead of 'ReLocked' status, follow the procedure.
1. fastboot reboot bootloader
2. fastboot oem relock UnlockCode this will ReLock your bootloader
3. switch on your phone, go to developer menu and Uncheck the OEM unlocking
4. Reboot your phone, done , your Phone status is now "Locked" , FRP is also Locked , you can check it in fastboot mode
5. if you want to unloack FRP, then just go to developer menu and Allow oem unloack, this will turn off FRP but bootloader status remains "LOCKED" , it doesn't change to ReLocked.
Enjoy
Click to expand...
Click to collapse
crayonicle said:
Follow this procedure:
Click to expand...
Click to collapse
After I entered relock command then it rolocked the bootloader and then it factory reset itself and reboot itself. When I went to disable the oem unlocking. It already got disabled. After that I went to check fastboot mode whether everything is unlocked. But it showing the 'relocked' but not 'locked' status. Anything to do sir???
krishnapenn said:
After I entered relock command then it rolocked the bootloader and then it factory reset itself and reboot itself. When I went to disable the oem unlocking. It already got disabled. After that I went to check fastboot mode whether everything is unlocked. But it showing the 'relocked' but not 'locked' status. Anything to do sir???
Click to expand...
Click to collapse
Disable "OEM unlocking" in developer options.
crayonicle said:
Disable "OEM unlocking" in developer options.
Click to expand...
Click to collapse
But it already disabled sir
krishnapenn said:
But it already disabled sir
Click to expand...
Click to collapse
Then bootloader should show "Locked" not "relocked"
crayonicle said:
Then bootloader should show "Locked" not "relocked"
Click to expand...
Click to collapse
It is saying 'bootloader relocked, FRP locked
krishnapenn said:
It is saying 'bootloader relocked, FRP locked
Click to expand...
Click to collapse
I've been searching around the internet, there is no way to make it say "locked"
sorry
crayonicle said:
I've been searching around the internet, there is no way to make it say "locked"
sorry
Click to expand...
Click to collapse
That's ok sir!!! No problem
krishnapenn said:
After I entered relock command then it rolocked the bootloader and then it factory reset itself and reboot itself. When I went to disable the oem unlocking. It already got disabled. After that I went to check fastboot mode whether everything is unlocked. But it showing the 'relocked' but not 'locked' status. Anything to do sir???
Click to expand...
Click to collapse
are you on oreo?
on oreo, if BL is unlocked, developer oem unlocking option will freeze to "oem unlocking Allowed" so this procedure is not useful.
by the way, if you have untouched stock rom, then OTA updates will come even on unlock bootloader and
you can claim warranty with ReLocked status.
Is there no easy way to relock the bootloader without using the MSM Tool (which I've never done)? I relocked it in the normal way, fastboot oem lock, but that resulted in a "device is corrupt and will not boot" error. I unlocked it and it's fine, but... I want to re-lock it.
dmarden said:
Is there no easy way to relock the bootloader without using the MSM Tool (which I've never done)? I relocked it in the normal way, fastboot oem lock, but that resulted in a "device is corrupt and will not boot" error. I unlocked it and it's fine, but... I want to re-lock it.
Click to expand...
Click to collapse
On OOS? Run a full local upgrade to whatever your current version is and try again
Yeah, it was just running stock firmware... Ok, so full local upgrade and try fastboot oem lock again?
Worth a try I guess, thanks!!!
The local update is running now, hope it works since the MSM Tool gives me a "failed to start" "because of a side by side configuration" error... lol. Sheesh, never experienced trouble relocking a device before.
dmarden said:
Yeah, it was just running stock firmware... Ok, so full local upgrade and try fastboot oem lock again?
Worth a try I guess, thanks!!!
Click to expand...
Click to collapse
Just factory reset once and then lock from fastboot > fastboot OEM lock > Select Yes to confirm and the device will lock the bootloader and reboot into OS
No dice... same error... what the heck?!
Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.
null0seven said:
Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.
Click to expand...
Click to collapse
It wouldn't let me install the downgrade APK (maybe because it is not on A12), but I am downloading the downgrade/rollback package and will try it.
null0seven said:
Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.
Click to expand...
Click to collapse
No dice... I presume because it's an older version it needs that APK.
Ok... this is resolved, even if I don't know how. I literally just tried it a third time and it worked. *shrug*
Thanks to those that responded.
dmarden said:
Ok... this is resolved, even if I don't know how. I literally just tried it a third time and it worked. *shrug*
Thanks to those that responded.
Click to expand...
Click to collapse
This is how I always did it
Hello, i unlocked the bootloader of my motorola one action. And i installed lineage 18.1 official, but i want to lock the bootloader again. i tried locking the bootloader using this help thread https://forum.xda-developers.com/t/...-2019-ask-any-question-noob-friendly.4010875/ but it din't work. Can somewone help me?
raphaelgamer981 said:
Hello, i unlocked the bootloader of my motorola one action. And i installed lineage 18.1 official, but i want to lock the bootloader again. i tried locking the bootloader using this help thread https://forum.xda-developers.com/t/...-2019-ask-any-question-noob-friendly.4010875/ but it din't work. Can somewone help me?
Click to expand...
Click to collapse
NEVER lock a phone with custom firmware installed. This usually leads to bootloops.
georg3_ said:
NEVER lock a phone with custom firmware installed. This usually leads to bootloops.
Click to expand...
Click to collapse
No, I Didn't try to lock the bootloader with a custom firmware.
raphaelgamer981 said:
No, I Didn't try to lock the bootloader with a custom firmware.
Click to expand...
Click to collapse
What are the steps you took before relocking the bootloader?
In my experience, relocking the bootloader should be the last thing you do, after you've got a working/bootable stock ROM.
arsradu said:
What are the steps you took before relocking the bootloader? In my experience, relocking the bootloader should be the last thing you do, after you've got a working/bootable stock ROM.
Click to expand...
Click to collapse
So, after i installed the latest stock rom, the device worked normally, but after waiting a while for the oem lock option appear in development options, it din´t show up. so i just gave up and installed lineage 19.1 but if i can i want to lock the bootloader again.
Raphael, I think you might have quoted my post twice, but didn't add an actual answer. Or maybe I'm super blind and I can't see it.
arsradu said:
Raphael, I think you might have quoted my post twice, but didn't add an actual answer. Or maybe I'm super blind and I can't see it.
Click to expand...
Click to collapse
ohh sorry, i tried replying to your post in my ipad 3 and it din´t show up any caracters.
raphaelgamer981 said:
So, after i installed the latest stock rom, the device worked normally, but after waiting a while for the oem lock option appear in development options, it din´t show up. so i just gave up and installed lineage 19.1 but if i can i want to lock the bootloader again.
Click to expand...
Click to collapse
So, the OEM lock/unlock thing comes with a pretty big caveat, and you need to be aware of it: loss of data.
Every time you lock or unlock your bootloader, a wipe data is triggered.
Now, for as far as I know, to lock the bootloader, you need two things:
1. Stock ROM. Don't do this on a custom ROM!
2. following command, in Terminal/Cmd Prompt
fastboot oem lock
Of course, you need to be in fastboot mode, so if you're not, and if you're booted and connected via USB (USB debugging needs to be ON and RSA fingerprinting accepted), do:
adb devices
It should display your device here. This is just to make sure ADB is working properly.
adb reboot bootloader
At this point, the phone should reboot into bootloader, so now you can do the lock command
fastboot oem lock
Data should be erased and, in case it doesn't automatically boot up, you can reboot the phone.
Don't worry about the OEM unlocking option in Developer Options. You just make sure the stock ROM is functional before attempting to relock the bootloader.
arsradu said:
So, the OEM lock/unlock thing comes with a pretty big caveat, and you need to be aware of it: loss of data.
Every time you lock or unlock your bootloader, a wipe data is triggered.
Now, for as far as I know, to lock the bootloader, you need two things:
1. Stock ROM. Don't do this on a custom ROM!
2. following command, in Terminal/Cmd Prompt
fastboot oem lock
Of course, you need to be in fastboot mode, so if you're not, and if you're booted and connected via USB (USB debugging needs to be ON and RSA fingerprinting accepted), do:
adb devices
It should display your device here. This is just to make sure ADB is working properly.
adb reboot bootloader
At this point, the phone should reboot into bootloader, so now you can do the lock command
fastboot oem lock
Data should be erased and, in case it doesn't automatically boot up, you can reboot the phone.
Don't worry about the OEM unlocking option in Developer Options. You just make sure the stock ROM is functional before attempting to relock the bootloader.
Click to expand...
Click to collapse
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
raphaelgamer981 said:
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
Click to expand...
Click to collapse
raphaelgamer981 said:
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
Click to expand...
Click to collapse
But why do you say it didn't work? Do you get an error at any point during the process?
arsradu said:
But why do you say it didn't work? Do you get an error at any point during the process?
Click to expand...
Click to collapse
no, i run the command and it asks for changing the oem lock setting in developer options, i reboot the phone and run through the setup process. Then when i enable developer options and check the oem lock option, it is greyed out.
Is it greyed out in the on or off position? Can you attach a screenshot? I don't remember the operations sequence... But I think the option was automatically switched back to the original position (off) when you lock the bootloader. I could be wrong though. So...when you run the "fastboot oem lock" command, it asks you to....what?
Set the option to on or off? Some screenshots from both the PC, with the message, and the developer options might help to clarify this.
arsradu said:
Is it greyed out in the on or off position? Can you attach a screenshot? I don't remember the operations sequence... But I think the option was automatically switched back to the original position (off) when you lock the bootloader. I could be wrong though. So...when you run the "fastboot oem lock" command, it asks you to....what?
Set the option to on or off? Some screenshots from both the PC, with the message, and the developer options might help to clarify this.
Click to expand...
Click to collapse
it is greyed in the on position, i can´t add a screenshot because i am in lineage 19.1 with root and the option shows up,when i run the command in cmd, it says to me to check the oem lock option in developer options
raphaelgamer981 said:
it is greyed in the on position, i can´t add a screenshot because i am in lineage 19.1 with root and the option shows up,when i run the command in cmd, it says to me to check the oem lock option in developer options
Click to expand...
Click to collapse
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
ok thanks for your help!
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
hello, so i want to lock the bootloader again, how do i install the stock rom back?
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
so after running the fastboot oem lock command, it asked this in the cmd
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.080s]
finished. total time: 0.080s
when i rebooted the phone, it showed the screen saying that the bootloader was unlocked. also i had to re run the command because it was going to erase my phone but that din´t happend, after going to developer options the option was still greyed out.
The last 3 days i've tried some roms from here.first i've unlocked the bootloader in developer menu,then from fastboot with the unlock key provided by motorola website,i've tried different rom,didnt like that i cannot use bank apps.so i went for locking.full reset,adb enable,reboot bootloader,full flash stock rom (last one from Motorola),reboot to check,adb enable, reboot bootloader,run command " fastboot oem lock " once ,it asked for confirmation due to data loss,then run command " fastboot oem lock " once more,then reboot to os.everything went ok,device dont show that was unlocked
ROOT RED MAGIC 8 PRO V3.18Your device must be bootloader unlocked
To unlock bootloader enable oem unlock in developer options and usb debugging
Then type the command: adb reboot bootloader
Or access fastboot with hardware key: Power + volume down
Once in fastboot type the following command to unlock:
fastboot flashing unlock
fastboot flashing unlock_critical"
Access fastboot then type the command:
fastboot flash init_boot_a magisk_patched-25200_3.18UN.img
fastboot reboot
Done
You check if the correct active slot is a, if it is b just change the command a with b
Only use for V3.18 version I have not tested other versions
Note: Absolutely do not patch the boot file, you will have a continuous boot error
Root Done
The backups with just ommiting the B slots is 12.7 gb so i cant personally help you with that. Have you tried flashing the OTA's boot.img (might even try boot_a.img) and init_boot.img while slot A is selected? Not the magisk modded files either.
mcfizzlestag said:
The backups with just ommiting the B slots is 12.7 gb so i cant personally help you with that. Have you tried flashing the OTA's boot.img (might even try boot_a.img) and init_boot.img while slot A is selected? Not the magisk modded files either.
Click to expand...
Click to collapse
i flashed those 2 files but still can't boot the phone, go to logo then turn off the screen, can only go to fastboot and recovery, i sideload 47% it gives error
If you are rooted, please help me, I will send you coffee donate, please help me, full backup
I Pm'd you the backups now that i am at home, hopefully they help
Im at a stand still with this. I have already fastboot flashing unlock_critical as you can see in which it states Device already unlocked but whether I am in bootloader and fastboot I get Flashing is not allowed in a lock state. Any help from some else that ran into this or has knowledge on it?
Thanks
Update. Fixed the issue. Add the step of "fastboot flashing unlock" before "fastboot flashing unlock_critical"
If You can flash a GSI, It'd be a decisive factor in getting people to buy this phone. The company should be paying you to do this, but they're probably too greedy to make a bigger profit
I've successfully flashed a few A13 GSIs but screen lock is a still a problem and so far calls and messaging doesn't work normally.
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Muriyata said:
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Click to expand...
Click to collapse
yes, you can return warranty
Muriyata said:
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Click to expand...
Click to collapse
Well once you unlock bootloader it clearly says warranty: void in fastboot so it probably is very easy to detect
edzchen said:
Well once you unlock bootloader it clearly says warranty: void in fastboot so it probably is very easy to detect
Click to expand...
Click to collapse
In that case, why op said that the warranty can still be returned after relocking the bootloader?
As you see, it is very connfusing... Some guys say yes, some others not. :s
edzchen said:
I've successfully flashed a few A13 GSIs but screen lock is a still a problem and so far calls and messaging doesn't work normally.
Click to expand...
Click to collapse
Could you please tell me the steps to flash A13 GSI roms. Thanks.
[email protected] said:
Could you please tell me the steps to flash A13 GSI roms. Thanks.
Click to expand...
Click to collapse
Unlock bootloader
Reboot into fastboot
Flash system with the GSI.img
Mr.PvT said:
i flashed those 2 files but still can't boot the phone, go to logo then turn off the screen, can only go to fastboot and recovery, i sideload 47% it gives error
If you are rooted, please help me, I will send you coffee donate, please help me, full backup
Click to expand...
Click to collapse
I have the same problem with my phone. Could you please tell me if you know find the solution to this. Thanks.
[email protected] said:
I have the same problem with my phone. Could you please tell me if you know find the solution to this. Thanks.
Click to expand...
Click to collapse
inbox me
Mr.PvT said:
inbox me
Click to expand...
Click to collapse
How can I inbox you?
Oh no... Can this be fixed?
Stusick said:
View attachment 5862143View attachment 5862145View attachment 5862147
Click to expand...
Click to collapse
Did you follow the instructions correctly, this error may have you flashed the wrong boot file, right?
Mr.PvT said:
Did you follow the instructions correctly, this error may have you flashed the wrong boot file, right?
Click to expand...
Click to collapse
Yes, I unlocked the bootloader first.
Then I flash boot and an error occurred.
Did I get a brick or is there hope?)