Yesterday updated to Android 10 and all were ok until I decided to fix the broken fp.. With stock recovery i tried through adb to lock bootloader. That's it.. Now phone only vibrate every 2 secs with Realme logo appeared and disappeared. I can't enter on recovery or bootloader. I tried all button combinations with no luck. I think that the only solution is to visit a technical center. :crying:
The CN version is like this. Fingerprint can be used to unlock the BL lock phone. However, C7 should pay special attention to the fact that root and fingerprints cannot coexist. It should be officially added verification. Fingerprints are disabled when root is detected. It is said that the official detection of root is not very accurate. After all, magisk is still very powerful, everything is normal when entering the system, and C7 does not need a patch to close magisk core mode like C6. C7 safetyNet checks are also true. So how does the official know? Because the current magisk solution uses boot.img, that is to say, as long as it is not the original boot, the fingerprint will be disabled.
******** The above is only a personal guess.
Goddamn Similar Issue
Realme should've shared this important information about being stuck at bootloop when locking bootloader. Fed up of trying all the button and still no response. Had to wait for the service centre to be opened. Don't know when this will be fixed. XDA developers. you're the only one who'd be having any solution to this milisecond boot loop on realme x2 pro.. Didn't flashed any rom, just tried perfectly all step to lock bootloader. I hope xda developers guys might've the solution to this. Also unable to boot to fastboot nor to any recovery mode.
Had no issues on C23 with locking BL with stock recovery.
First thing I did was resetting the phone and then locking BL.
tidschi said:
Had no issues on C23 with locking BL with stock recovery.
First thing I did was resetting the phone and then locking BL.
Click to expand...
Click to collapse
Any help on what I can do to turn on my device??
EdoKai's Realme X2 Pro said:
Realme should've shared this important information about being stuck at bootloop when locking bootloader. Fed up of trying all the button and still no response. Had to wait for the service centre to be opened. Don't know when this will be fixed. XDA developers. you're the only one who'd be having any solution to this milisecond boot loop on realme x2 pro.. Didn't flashed any rom, just tried perfectly all step to lock bootloader. I hope xda developers guys might've the solution to this. Also unable to boot to fastboot nor to any recovery mode.
Click to expand...
Click to collapse
Did you contact realme Service Center What did they say ? i Have the exact same issue please help
Only realme service centre can help you.
Related
Hi all, I've an italian Nokia 7 Plus TA-1055 single SIM.
I was on Oreo 8.1, unlocked bootloader, tried many GSI roms for tests and then I wanted to came back to stock rom for some phone call problems.
In order to do it, during my tests, I did a big mistake, I relocked again the bootloader with fastboot oem lock command without having stock boot, but one with TWRP inside instead :crying:
Now, at every boot, phone shows me a message like this: "Your device is corrupt. it can't be trusted and will not boot[...] the device will shutdown in 30 seconds[...]".
Now, I can boot in download mode, but I cannot flash or boot anything via fastboot, in order to unlock again, and even "nb0 tools FIH Mobile" could not help me (like many others, stucked at "Reflashing service boot" or similar).
Now, what can I do?
Thanks for who wants to help me, every help is appreciated
death_jax said:
Hi all, I've an italian Nokia 7 Plus TA-1055 single SIM.
I was on Oreo 8.1, unlocked bootloader, tried many GSI roms for tests and then I wanted to came back to stock rom for some phone call problems.
In order to do it, during my tests, I did a big mistake, I relocked again the bootloader with fastboot oem lock command without having stock boot, but one with TWRP inside instead :crying:
Now, at every boot, phone shows me a message like this: "Your device is corrupt. it can't be trusted and will not boot[...] the device will shutdown in 30 seconds[...]".
Now, I can boot in download mode, but I cannot flash or boot anything via fastboot, in order to unlock again, and even "nb0 tools FIH Mobile" could not help me (like many others, stucked at "Reflashing service boot" or similar).
Now, what can I do?
Thanks for who wants to help me, every help is appreciated
Click to expand...
Click to collapse
Hi. U can't use any tools without unlocking bootloader in my knowledge. Me also faced same issue some months ago. I did same mistake as urs. Finally i give it to Service Centre. Got a replacement with warranty. I told them a different fake story
Rajeev said:
Hi. U can't use any tools without unlocking bootloader in my knowledge. Me also faced same issue some months ago. I did same mistake as urs. Finally i give it to Service Centre. Got a replacement with warranty. I told them a different fake story
Click to expand...
Click to collapse
The "failed update" story do you think that may be right?
death_jax said:
The "failed update" story do you think that may be right?
Click to expand...
Click to collapse
Absolutely
Thanks to all, this thread can be closed, I solved with the help of hikari_calyx
Hi everyone, some weeks ago I converted my A2 in 6X because I wanted to test MIUI. Yesterday, dealing with an update my phone get into a bootloop. Well, I used MiFlash to fix it but I selected "flash and lock" (yes, I know, I'm stupid).
The main thing is that I'm in a Chinese ROM with lock bootloader and when I try to unlock it I get error 86023.
I dont know what to do. I've thought about test point to flash Xiaomi.eu but I'm not sure bcause the bootloader is locked.
Someone with a posibble solution? Thanks
Welcome to the Club
Same thing happened to me.
You can now choose between China Developer or Stable.
I tried many progs and tutorials to unlock the bootloader but no way.
If you need GooglePlayStore, CalenderSync and ContactsSync:
https://androidfilehost.com/?fid=818070582850489460
I'm now on stable V10.3.6.0.PDCCNXM and all is working quite well.
rafamb281 said:
Hi everyone, some weeks ago I converted my A2 in 6X because I wanted to test MIUI. Yesterday, dealing with an update my phone get into a bootloop. Well, I used MiFlash to fix it but I selected "flash and lock" (yes, I know, I'm stupid).
The main thing is that I'm in a Chinese ROM with lock bootloader and when I try to unlock it I get error 86023.
I dont know what to do. I've thought about test point to flash Xiaomi.eu but I'm not sure bcause the bootloader is locked.
Someone with a posibble solution? Thanks
Click to expand...
Click to collapse
It didn't happened to me for myself, but I just asked this question to get better knowledge about bootloader stuffs:
As I understood the current problem is this:
You need to unlock your bootloader again, there is just (as much as I know) 2 ways to approach, which both of them will not help you:
1. Unlocking as a A2 : but your device is not a A2 anymore, so the device will not be unlocked by this method.
2. Unlocking as a 6x : but this one won't be successful either since the dedicated unlocking program asks for a real 6X device with a registered IMEI number by factory, which in your case is NOT.
So, you will be left just with the options that need no Unlocked Bootloader, as mentioned above, like Chinese Stable versions. ( That in my opinion it does NOT sound awful. )
(BTW, every day comes with new procedures, maybe you can find a new method to unlocked the bootloader again, there was times that many expertise told, after stucking in ARB4 trap, you just need to find a suitable Trash for your device!, but now we all know that there is plenty new ways to deal with it).
sz.hatef said:
It didn't happened to me for myself, but I just asked this question to get better knowledge about bootloader stuffs:
As I understood the current problem is this:
You need to unlock your bootloader again, there is just (as much as I know) 2 ways to approach, which both of them will not help you:
1. Unlocking as a A2 : but your device is not a A2 anymore, so the device will not be unlocked by this method.
2. Unlocking as a 6x : but this one won't be successful either since the dedicated unlocking program asks for a real 6X device with a registered IMEI number by factory, which in your case is NOT.
So, you will be left just with the options that need no Unlocked Bootloader, as mentioned above, like Chinese Stable versions. ( That in my opinion it does NOT sound awful. )
(BTW, every day comes with new procedures, maybe you can find a new method to unlocked the bootloader again, there was times that many expertise told, after stucking in ARB4 trap, you just need to find a suitable Trash for your device!, but now we all know that there is plenty new ways to deal with it).
Click to expand...
Click to collapse
not the imei, it asks for 6x serial number which device is a2. you have to find someone who has authorized mi account to unlock this device. it is only way for now
q0kHaN said:
not the imei, it asks for 6x serial number which device is a2. you have to find someone who has authorized mi account to unlock this device. it is only way for now
Click to expand...
Click to collapse
And how I can find someone with one?
rafamb281 said:
And how I can find someone with one?
Click to expand...
Click to collapse
Authorized Customer Services, or a friend who works there
It is very possible that they can restore your phone (and as well your bootloader) as what it was in factory.
sz.hatef said:
Authorized Customer Services, or a friend who works there
It is very possible that they can restore your phone (and as well your bootloader) as what it was in factory.
Click to expand...
Click to collapse
R u talking about contact with Xiaomi? Or another service?
I tried it here http://unlock-unbrick.com/, but they also couldnt help me.
rafamb281 said:
R u talking about contact with Xiaomi? Or another service?
Click to expand...
Click to collapse
Yes, exactly.
Hello my friends, i managed to unlock the bootloader of my converted A2/6X.
I tried several times to switch from stable china to developer china but from 9.8.15 to 9.9.3 no one worked.
After installing one of the developer roms, the phone only shows the boot screen for 2 seconds and turns off, with charger it boots endlessly or shows the green battery symbol after some minutes.
One thing that works, is using a rubber band to fix "Vol+" and connect phone via usb or charger, mostly after 5-10 minutes it will enter the "Miui-Recovery", then you can start "Mi-Assistent" in the "Miui-Recovery" and flash back the stable china, so luckily no need of EDL.
After flashing the last 9.9.3 rom and the phone was all screwed up, again. I tried the original "miflash_unlock-en-2.2.624.14" and it worked.
I have done this "thousand" times before with all available unlock tools I found but never succeeded before.
Download: miflash_unlock-en-2.2.624.14
https://xiaomifirmware.com/downloads/download-mi-unlock-2-2-624-14-windows/
https://androidfilehost.com/?fid=889764386195916630
Now I tried to boot into recovery “fastboot boot twrp_wayne.img” but it didn't work, because the phone reboots or turns off after 2 seconds.
So I flashed the china stable via fastboot (worked), let it boot up, no setup, reboot to enter fastboot and flashed successful the orangefox-twrp.
Hope somebody can also unlock his bootloader or maybe it was just luck.
puxxi2004 said:
Hello my friends, i managed to unlock the bootloader of my converted A2/6X.
I tried several times to switch from stable china to developer china but from 9.8.15 to 9.9.3 no one worked.
After installing one of the developer roms, the phone only shows the boot screen for 2 seconds and turns off, with charger it boots endlessly or shows the green battery symbol after some minutes.
One thing that works, is using a rubber band to fix "Vol+" and connect phone via usb or charger, mostly after 5-10 minutes it will enter the "Miui-Recovery", then you can start "Mi-Assistent" in the "Miui-Recovery" and flash back the stable china, so luckily no need of EDL.
After flashing the last 9.9.3 rom and the phone was all screwed up, again. I tried the original "miflash_unlock-en-2.2.624.14" and it worked.
I have done this "thousand" times before with all available unlock tools I found but never succeeded before.
Download: miflash_unlock-en-2.2.624.14
https://xiaomifirmware.com/downloads/download-mi-unlock-2-2-624-14-windows/
https://androidfilehost.com/?fid=889764386195916630
Now I tried to boot into recovery “fastboot boot twrp_wayne.img” but it didn't work, because the phone reboots or turns off after 2 seconds.
So I flashed the china stable via fastboot (worked), let it boot up, no setup, reboot to enter fastboot and flashed successful the orangefox-twrp.
Hope somebody can also unlock his bootloader or maybe it was just luck.
Click to expand...
Click to collapse
Amazing Dude. [emoji108][emoji108][emoji108][emoji108][emoji108] Congratulations.
Hello friends I'm new to this community so if anything wrong about posting i apologize in advance. I have a problem with my device Realme x2 pro , im not able to boot my phone into fastboot mode using realme in-depth test app.
What i see is when i tap on apply or start option inside the app , my phone reboots and the fastboot logo comes only for 1-2 sec and then vanishes , and my phone boots into system or android interface..
I need help with this (unlocking bootloader) as iam fed up with stock os that realme provides ..
RahulKumar_213 said:
Hello friends I'm new to this community so if anything wrong about posting i apologize in advance. I have a problem with my device Realme x2 pro , im not able to boot my phone into fastboot mode using realme in-depth test app.
What i see is when i tap on apply or start option inside the app , my phone reboots and the fastboot logo comes only for 1-2 sec and then vanishes , and my phone boots into system or android interface..
I need help with this (unlocking bootloader) as iam fed up with stock os that realme provides ..
Click to expand...
Click to collapse
Hello brother, as i know the only solution so far is to replace the motherboard, If you are still in the warranty period, hurry to the nearest RealmeCenter and blame the update, to get a free repair.
...
If you find a better solution you will be a hero to many people
edit: Some of us are stuck like you but without imei so no wifi/sim
a.saed said:
Hello brother, as i know the only solution so far is to replace the motherboard, If you are still in the warranty period, hurry to the nearest RealmeCenter and blame the update, to get a free repair.
...
If you find a better solution you will be a hero to many people
edit: Some of us are stuck like you but without imei so no wifi/sim
Click to expand...
Click to collapse
Me too, but i have imei, sim, wifi work ok
but i cant open fastboot mode
My phone suddenly get stucked into Redmi boot logo, cannot access system recovery but can access fastboot menu.
The problem is I hadn't enabled OEM unlock and developer options before. All the methods that I found so far requires bootloader unlock for that I also don't have MI account . What might be my next move? Thank you.
its hard to say what we can|t do with a still locked bootloader. if going to an authorized service center is out of reach, all we can do is try i guess. id still suggest going there if you can easily access your google account.
there are a few threads that say we can flash a still locked bl, but im not so sure.
Flash stock ROM/Recovery, lock bootloader?
Is there any guide on how I can complete return phone to stock and lock bootloader? Thank you.
forum.xda-developers.com
official stock roms can be hard to find on their site, heres an easier to navigate 1.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
gl
With EDL mode? I'm in a similar situation, a friend's mother forced a shutdown during a firmware update and destroyed the system that way. Of course the bootloader is blocked. I find it extremely stupid of Xiaomi to rely on a working system to give you the chance to unlock the bootoader but I guess that's how you sell some extra phones.
So far I've taken out the rear cover and the plastic that goes on top of the motherboard, unplugged the battery and with an arduino cable and some fiddeling shorted the "boot" pins while connecting the USB cable. Seems to be working given that MiFlash has changed the locked bootloader error for "indice fuera de limites" or in English "index out of limits error". I guess I don't have the right ROM so I'm downloading another one, but I'm struggilng to find the correct original fastboot ROM. The first one I've downloaded from Mi Community, the second one is from xiaomifirmwareupdater, but is gonna take forever to download. And I mean... F-O-R-E-V-E-R
Jaki1122 said:
With EDL mode?
...
Click to expand...
Click to collapse
gl with that, as only authorized people can properly flash from there. while i havent used EDL, there are some trusty people who can help us out (ive seen it in tg groups)
a site did say maybe using another version can help, who knows it might do the trick
https://c.mi.com/thread-2027947-1-0.html
also seems weird how goolag hasnt fixed half flashing from destroying, last time i had that happen was '12
Foreword: My time with Vivo has come to an end. After flashing a wrong devicecfg and accidentally rebooting my device it is now in a hard bricked state.
Vivo has locked down EDL, there is absolutely no way to flash or backup anything in EDL mode without the official Tools (namely Vivo AFTool 5.9.80).
Vivo India refers me to Vivo Germany - Vivo Germany has outsourced its customer support to bulgaria.
The people on the other side of the line know absolutely nothing about the technical aspect and refuse to put me through to anyone with any kind of knowhow.
Due to their anti consumer and anti repair attitudes I will not buy another Vivo phone.
With this out of the way: You might end up like me with a hard brick. Or without signal.
Even if this will not save you from a hard brick I can not stress this enough: Make a BACKUP! And backup your data. This will wipe your phone.
This process is IRREVERSIBLE unless you have a split ROM of the chinese Firmware or your own Backup.
THIS or BL UNLOCK will break your portrait mode. No more bokeh, neither in Origin OS nor FunTouch.
Do NOT flash fsg, modemst1 and modemst2. They are commented out in the COMMANDS file.
You do this at your own risk. As said before this might brick your device.
Unlock your Bootloader
Backup your Partitions
Download my Flash Folder and Extract it: Android File Host
Open 01COMMANDS.txt and read the instructions
Open a command shell in the same folder that you can find 01COMMANDS.txt in
Run the given commands in blocks or one after the other
If you do not have signal after flashing you might have to erase modemst1 and modemst2 partitions, so that they get replaced by the backup in fsg.
A magisk flashed boot.img and adb-modded recovery is included so you can flash it after booting up FunTouch once and backup all your partitions again.
Thanks again to @Pervokur for helping me along the way. There is definitely an easier method that involves less risky flash operations.
My phone died on the cross while I was trying to figure it out, so maybe someone else will pick up the torch.
I will not be able to offer any kind of support.
RIP @Killuminati91's Vivo, who died for the cause.
Sorry to hear that, man, you were so close to what looked like an easy switch between ROMs.
I know you said you were no developer but you are still a leap ahead of most of us here. Long do we miss the good old days where ROMs, kernels and pure innovation shortly followed our much-wanted phone when flashing a few ROMs a week was normal.
Thanks for all your help, perhaps one day there will be a way to recover your phone.
Many thanks, may I relock the bootloader when i finished change to Global rom?
amos0609 said:
Many thanks, may I relock the bootloader when i finished change to Global rom?
Click to expand...
Click to collapse
Same question
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
how did you relock the bootloader, does the portrait mode work again?
does any one change the origin os /ocean into funtouch？
version？ how to relock after it can switch to funtouch？
by the way, I saw the post on the taiwan vivo phone of fb
the second hand goods, it wrote he change the origin os into funtouch
and he sell this service , it charge 2000 nt dollars in taiwan.
maybe someone can save your phone.
Killuminati91
I think the only problem that keeps the phone from being recognized as official FunTouch is dm-verity.
In theory both phone versions have the same exact hardware.
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
stevenkh168 said:
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
Click to expand...
Click to collapse
Message?
silence360 said:
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
Click to expand...
Click to collapse
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Killuminati91 said:
Message?
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Click to expand...
Click to collapse
did you try using the OriginOS's camera app on FuntouchOS ? I find it when u use the front facing camera, the portrait mode still work. In the other hand, the back camera is not working in portrait mode. I follow your guide and using the FuntouchOS about 2 days. Everything works fine, except the portrait mode and the AOD. Cant use it anymore.
Oh I see, now that is weird that the portrait mode is not working. So even if you switch not all functionality has returned. Thanks for the explanation. Hopefully someone can continue your work, and find a solution for a seamless transition.
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
hope to see some good news from you sir.
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
Update us...
have you been able to solve it?
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
NHQ Thang said:
how did you relock the bootloader, does the portrait mode work again?
Click to expand...
Click to collapse
same question
adkana4310 said:
Update us...
have you been able to solve it?
Click to expand...
Click to collapse
If u asking me so no im still on the same cant flash
redwatch99 said:
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Click to expand...
Click to collapse
Someone who can help me solve it ?