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?)
Related
Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?
I used Nexus Root Toolkit when I got semi-bricked.
Use erase Command on flashboot for data and system then do flash_all again
As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?
hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.
hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.
Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Is it a carrier model or a play store
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-ca-bootloader-t3494615
This.
chapelfreak said:
Is it a carrier model or a play store
Click to expand...
Click to collapse
Google store
ASimpleSock said:
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-ca-bootloader-t3494615
This.
Click to expand...
Click to collapse
I see the thread but it doesnt seem like theres a fix in it
tryfont said:
I see the thread but it doesnt seem like theres a fix in it
Click to expand...
Click to collapse
There probably isn't, if you've altered system and relock and toggle OEM unlocking off in dev. options you get bricked.
tryfont said:
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Click to expand...
Click to collapse
Did you try:
fastboot flashing unlock
Since you only relocked, you unlikely toggled "OEM unlock"?!
If it fails, I think you are SOL. Maybe someone with a proper solution will chime in. Otherwise, you have to RMA your device...
Good luck...
5.1 said:
Did you try:
fastboot flashing unlock
Since you only relocked, you unlikely toggled "OEM unlock"?!
If it fails, I think you are SOL. Maybe someone with a proper solution will chime in. Otherwise, you have to RMA your device...
Good luck...
Click to expand...
Click to collapse
It just says waiting for device and hangs there... I don't think it recognizes the phone
EDIT: IT WORKED!!!!!
It wouldnt recognize it and I ran fastboot continue and it just hanged there but I went into the bootloader mode and for like a quarter of a second it recognized it and forced it to boot
tryfont said:
It just says waiting for device and hangs there... I don't think it recognizes the phone
Click to expand...
Click to collapse
Open device manager in windows. Plug your phone and see how is your phone recognized.?!
5.1 said:
Open device manager in windows. Plug your phone and see how is your phone recognized.?!
Click to expand...
Click to collapse
Im on mac but its good now I edited my comment above. Only question is how to I completely clean the OS so I can relock bootloader without running into the same problem
This is whats happening to me- https://goo.gl/photos/2kv9Xo3HM3Mqn8AQ9
tryfont said:
Im on mac but its good now I edited my comment above. Only question is how to I completely clean the OS so I can relock bootloader without running into the same problem
Click to expand...
Click to collapse
Hey... Go into recovery and perform a factory reset.
Reboot bootloader and flash stock firmware. You could flash both slots to be sure your device is completely clean.
I wrote a how-to for someone having another issue. You.can follow this:
https://forum.xda-developers.com/showpost.php?p=71849370&postcount=28
When you are finished with flashing, reboot to be sure your system boot properly and your phone works as it should...
From here you can reboot into bootloader and issue:
fastboot flashing lock
If It was me I'd leave it unlocked though... Or at least OEM unlock enabled and ADB debugging ON. Since Google tend to release messed up OTA, you can always unlock the bootloader if needed.
But if you wish you can also disable the OEM unlock.
Good luck...
5.1 said:
Hey... Go into recovery and perform a factory reset.
Reboot bootloader and flash stock firmware. You could flash both slots to be sure your device is completely clean.
I wrote a how-to for someone having another issue. You.can follow this:
https://forum.xda-developers.com/showpost.php?p=71849370&postcount=28
When you are finished with flashing, reboot to be sure your system boot properly and your phone works as it should...
From here you can reboot into bootloader and issue:
fastboot flashing lock
If It was me I'd leave it unlocked though... Or at least OEM unlock enabled and ADB debugging ON. Since Google tend to release messed up OTA, you can always unlock the bootloader if needed.
But if you wish you can also disable the OEM unlock.
Good luck...
Click to expand...
Click to collapse
I'm pretty inexperienced with this kind of stuff and so you might have to explain it a bit further than what that link says. I did fastboot reboot bootloader in terminal but it can't find my device. Also I couldnt get into recovery when it was bricked so I probably still can't
tryfont said:
I'm pretty inexperienced with this kind of stuff and so you might have to explain it a bit further than what that link says. I did fastboot reboot bootloader in terminal but it can't find my device
Click to expand...
Click to collapse
Hey...
You boot into bootloader when the Device is powered off
Just like in your video: with power + volume down
You can see infos regarding:
Bootloader
Radio
S/N
DRAM
Boot-slot=
Etc...
This is the bootloader :good:
From here, unzip the google image you have downloaded, open the folder and from here run the flash-all script. Let your device reboot. Power it down, boot into bootloader again with power + volume down. Change active slot as I described in the link I gave you previously. Run the same flash-all again... Done!
Just for safety, remove your Google account before you continue. You'll add it again later...
Good luck...
5.1 said:
Hey...
You boot into bootloader when the Device is powered off
Just like in your video: with power + volume down
You can see infos regarding:
Bootloader
Radio
S/N
DRAM
Boot-slot=
Etc...
This is the bootloader :good:
From here, unzip the google image you have downloaded, open the folder and from here run the flash-all script. Let your device reboot. Power it down, boot into bootloader again with power + volume down. Change active slot as I described in the link I gave you previously. Run the same flash-all again... Done!
Just for safety, remove your Google account before you continue. You'll add it again later...
Good luck...
Click to expand...
Click to collapse
Alright thank you so much its doing the flashing right now. I really appreciate you helping...I was worried I'd have to get a replacement through google. Have a great day lad
tryfont said:
Alright thank you so much its doing the flashing right now. I really appreciate you helping...I was worried I'd have to get a replacement through google. Have a great day lad
Click to expand...
Click to collapse
Hey... Flash both slots... Just to be sure both are clean and nothing problematic remains on your device before locking your bootloader!
It could brick installing an OTA or whatever. Better restart 100% clean. :good:
Cheers...
Just flash the flash-all, relock and call it a day. Then you'll be fully stock and locked. I would however recommend rebooting once before locking to make sure its all good.
tryfont said:
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Click to expand...
Click to collapse
Hey man I have the same problem you can try calling Google support they can send you a replacement if you still have a warranty
my warranty has expired so I'm on my own
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.
This Is For those Who Stuck At Android 9 In WW Roms With ZS660KL Model
This Method Will Use Raw Firmware so there is risks if you do something wrong and maybe data loss so always backupBootloader Must Be Unlocked
How To Flash Raw Rom:1-Bootloader Must be Unlocked! (To change fingerprint to ww and relock the bootloader to get OTA) If you are already on WW fingerprint this step aint needed or you want to stay on cn fingerprint just skip)
2-Install adb and fastboot
3-Download and extract the raw version you want i will give some below
4- reboot the phone to fastboot mode and connect it to the pc Use Side Port
5-in the raw firmware folder double click flashall_AFT.cmd This will take sometime and no progress will be shown so all you have to do is to wait till the phone reboot or get black screen if you got black screen just hold vol down and power button for some seconds
6-if your Fingerprint is cn Change it to WW With root explorer you can find posta about this step by step (skip this if you are already on WW Fingerprint)
Downloads:
Android 10:
https://drive.google.com/file/d/1NQI7SyCfPkBA15dVAim2yhEWD_6p0Kta/view
Android 9:
https://drive.google.com/file/d/16uIlYvFuXDEoRmtosqUwgVgM7aMdhaOp/view
Credits:
the custom droid site for the raw Firmwares
Some info:
After this method You will get ota updates if you relock bootloader
or you can install update zips from asus if you want to keep bootloader unlocked :silly:
You don't need to unlock the bootloader to flash the raw firmware. That is stupid to say you do..
joluke said:
You don't need to unlock the bootloader to flash the raw firmware. That is stupid to say you do..
Click to expand...
Click to collapse
The way you say stupid is stupid however mine didn't got flashed just rebooted when tried to flash the raw and couldn't update in system updates or zip files however having some respect ain't bad for your health.
shahram Ali said:
The way you say stupid is stupid however mine didn't got flashed just rebooted when tried to flash the raw and couldn't update in system updates or zip files however having some respect ain't bad for your health.
Click to expand...
Click to collapse
First of all, I just said it was a stupid thing to say because you don't need to unlock the bootloader and you must use the side USB c port to flash via fastboot. Second: learn to interpret proper English because I didn't offend anyone. End of conversation
joluke said:
First of all, I just said it was a stupid thing to say because you don't need to unlock the bootloader and you must use the side USB c port to flash via fastboot. Second: learn to interpret proper English because I didn't offend anyone. End of conversation
Click to expand...
Click to collapse
I mentioned the side port i don't write a paragraph about the phone as homework short and easy fix is the point there is nothing missing in the post so your reply wasn't necessary mate keep it cool :good:
How do I lock the bootloader after this?
I have some apps that wont work, whit the message "This app is not supported in rooted devices, please restore your device"
Thanks
Ricardo55467 said:
How do I lock the bootloader after this?
I have some apps that wont work, whit the message "This app is not supported in rooted devices, please restore your device"
Thanks
Click to expand...
Click to collapse
You will need to enter an command in fastboot mode but be aware backup every necessary things
If you didn't rooted or touched boot.img just use this command in fastboot and the bootloader will be locked again
fastboot oem asus-csc_lk
shahram Ali said:
You will need to enter an command in fastboot mode but be aware backup every necessary things
If you didn't rooted or touched boot.img just use this command in fastboot and the bootloader will be locked again
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .
Ricardo55467 said:
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .
Click to expand...
Click to collapse
You'll need to flash stock boot img if your rom version (to remove root) before locking bootloader
Ricardo55467 said:
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .
Click to expand...
Click to collapse
Just reflash stock boot.img and you can use the command
Accidently hit the "clean all and lock" bat, it did the job...now it's absolutely kicked me out. Loads fastboot only, can't do anything. Bootloader now locked yet again, error states "can't erase lock state" nothing I do will get this thing working....i'm in tears
poco f3 is my phone.
What rom did you have before
CraigUK87 said:
Accidently hit the "clean all and lock" bat, it did the job...now it's absolutely kicked me out. Loads fastboot only, can't do anything. Bootloader now locked yet again, error states "can't erase lock state" nothing I do will get this thing working....i'm in tears
poco f3 is my phone.
Click to expand...
Click to collapse
Read warranty policy:
https://www.mi.com/uk/service/warranty?v=1#warrant
Maybe you can have free repair.
zaki789 said:
What rom did you have before
Click to expand...
Click to collapse
Elite OS. Was unlocked.
Does anyone have EDL access that would be willing to save me?
I gess u used MiFlash tool if u locked ur bootloader (clear all and lock), so I guess again that u flashed an stock rom (since MiFlash tool works with fastboot stock rom only). That means that ur not on Elit ROM anymore but in a stock ROM. If u can access fastboot as u claimed, try to unlock ur bootloader again....maybe a miracle is happen and it will work without bonding ur account to ur phone In this stage, u can not mess up ur phone more, so give it a try
Try to unlock bootloader again. It should be possible if you unlocked bootloader before.
It doens't work, it asks me to do the old adb, i can't get in the phone to enable unlock.
but yes, i did...rookie mistake, poxy thing shouldn't even be there and now Im more screwed than ever
What did you flashed with miflash?Stock rom?
When the phone starts at the POCO logo do you have the little lock at the top of the screen locked ?
hexisg said:
What did you flashed with miflash?Stock rom?
Click to expand...
Click to collapse
Yep, was going back to stock. I really don't know what to do. Some guy is offerign to fix for £25...but...just seems fishy and I have 0 in my bank
"couldn't unlock" please add your acc in MIUI settings > Dev Ops > Mi unlock.
This is the error I get.
CraigUK87 said:
Yep, was going back to stock. I really don't know what to do. Some guy is offerign to fix for £25...but...just seems fishy and I have 0 in my bank
Click to expand...
Click to collapse
You can try this guy https://xiaomi.eu/community/threads/bricked-mi-8-edl-flashing-problem.58984/#post-582694
Personally didn't contact him, so you have to risk it to verify, and high chance to charge you some repair fee.
If you think everyone who offers EDL but request payment is fishy, then your only choice is Xiaomi repair center.
In your state, chances for EDL access free of charge is extremely low, even non-exist.
If you want free of charge, then try Xiaomi repair center. There's chance for free repair, that is, if your device meet the warranty coverage policy.
CraigUK87 said:
"couldn't unlock" please add your acc in MIUI settings > Dev Ops > Mi unlock.
This is the error I get.
Click to expand...
Click to collapse
fixed? i have a fix use xiaomi adb fastboot tools for bl unlock its unoffical but still works im also like by mis i pressed clean all and lock whille insstalling redmi k40 rom in my mi 11x so my phone booted only to fastboot so i just clicked on unlock my phone got unlockdd before data getting erased it went to fastboot then i check fastboot oem device-info then it said bootloader unlock true then just flash your stock stock rom thats all
Have you ever heard of XiaoMiTool V2? I saw some posts that it is a tool for bricked devices but I dont know for sure.
Renatoskie said:
Have you ever heard of XiaoMiTool V2? I saw some posts that it is a tool for bricked devices but I dont know for sure.
Click to expand...
Click to collapse
idk
I had a similar issue with a Motorola. I tried this, so no promises...but generally I think it's "hot booting" the boot image. I ran the command:
fastboot -b flash boot boot.img
It returned some output like "downloading..." and something else. Of course, locate and put your matching boot.img file in your fastboot directory before flashing. Afterwards, my phone booted into the system like nothing was wrong. I suppose it didn't make it to flashing the system partition? which left it bootable?
Please, corrections, I'm uh, new <----.
notquitecurious said:
I had a similar issue with a Motorola. I tried this, so no promises...but generally I think it's "hot booting" the boot image. I ran the command:
fastboot -b flash boot boot.img
It returned some output like "downloading..." and something else. Of course, locate and put your matching boot.img file in your fastboot directory before flashing. Afterwards, my phone booted into the system like nothing was wrong. I suppose it didn't make it to flashing the system partition? which left it bootable?
Please, corrections, I'm uh, new <----.
Click to expand...
Click to collapse
You cant flash anything via adb if your bl is locked -_-
If you have an f3 and flashed a fastboot rom you shouldn’t get any issue!! There is a little tool to switch to edl from fastboot , but even having access to that you need a verified mi account to flash or pay someone , its around 25$ had the same issu 7 months ago i can provide you the contact of a legit guy who did for me
I think you have to first put your phone in edl mode by opening the case (melt the glue using a hair dryer) and shorting 2 pins. You should start worrying about edl credentials after you have done that.
bouyhy01 said:
You cant flash anything via adb if your bl is locked -_-
Click to expand...
Click to collapse
Yes, apparently you can. My bootloader was locked when I input that command. The phone then booted into the normal system. You have to have a matching boot image though.