Database Info

[Q] The hardest rescue

Hi everyone!
Just a little question, as I'm facing this situation right here:
is there a way to revive a phone that doesn't boot, nor lets me access recovery mode or fastboot or bootloader?

UltimateGoblin said:
Hi everyone!
Just a little question, as I'm facing this situation right here:
is there a way to revive a phone that doesn't boot, nor lets me access recovery mode or fastboot or bootloader?
Click to expand...
Click to collapse
Which phone are you talking about?

I'm talking about the Alcatel V860. It's absolutely an uncommon model, that's the reason why I'm speaking in general.

UltimateGoblin said:
I'm talking about the Alcatel V860. It's absolutely an uncommon model, that's the reason why I'm speaking in general.
Click to expand...
Click to collapse
Please ask specific questions as its related to the phone model. I'm not hopefully about it. You can get it serviced by "bootloader repair" Should be about 40$.
Some of the more common phones can be unbricked on your own.

LS.xD said:
Please ask specific questions as its related to the phone model. I'm not hopefully about it. You can get it serviced by "bootloader repair" Should be about 40$.
Some of the more common phones can be unbricked on your own.
Click to expand...
Click to collapse
I've already posted here, but I received only one answer, so I decided to speak more general just to know if it is theoretically possible to rescue a phone in the situation I described.
Anyway, do you think that there is no way that the pc can communicate with a phone that doesn't even reach the bootloader?

Ok, I'll ask a different question: the phone I'm talking about ended up this bad while flashing an official OTA.
How is that possible?
I thought there was no possible way that an OTA messed with the bootloader, or the recovery... or fastboot! Doesn anyone know what could possibly have gone wrong during the update?

UltimateGoblin said:
Ok, I'll ask a different question: the phone I'm talking about ended up this bad while flashing an official OTA.
How is that possible?
I thought there was no possible way that an OTA messed with the bootloader, or the recovery... or fastboot! Doesn anyone know what could possibly have gone wrong during the update?
Click to expand...
Click to collapse
Actually, it seems like your phone is bricked, there are some methods to unbrick some phones but I don't know if they would work for you, just try to do a Google search how to unbrick a bricked phone, and it might return with some useful stuff, try everything that's possible, because nothing worst can happen over a brick(except it can blast in your hand if you connect a high voltage in place of battery)(lol, it won't happen! )
Hit Thanks if I helped sent from my SM-T211

Already done that, I'm giving up if my pc cannot communicate with the phone.
At this point I'd only like to know how could an OTA corrupt the bootloader.

UltimateGoblin said:
Already done that, I'm giving up if my pc cannot communicate with the phone.
At this point I'd only like to know how could an OTA corrupt the bootloader.
Click to expand...
Click to collapse
Only thing you can do now is, go to store(from where you buy your phone, act dumb and tell them that this won't turn on, they might replace your phone!
Hit Thanks if I helped sent from my SM-T211

Thanks. Anyone else?

UltimateGoblin said:
Thanks. Anyone else?
Click to expand...
Click to collapse
So, what exactly you did?
Hit Thanks if I helped sent from my SM-T211

It wasn't me, it was my cousin, who flashed an OTA which apparently corrupted all the layers of the OS. I believe him, but I find it incredibly difficult to happen, so I wanted to know if that could really happen.

UltimateGoblin said:
It wasn't me, it was my cousin, who flashed an OTA which apparently corrupted all the layers of the OS. I believe him, but I find it incredibly difficult to happen, so I wanted to know if that could really happen.
Click to expand...
Click to collapse
What do you mean by ota corrupting all layers of os?
I never heard of it.
Hit Thanks if I helped sent from my SM-T211

It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.

UltimateGoblin said:
It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.
Click to expand...
Click to collapse
Try smart phone flash tool(on pc), I recently came across a thread in which author said he have a hard bricked xolo phone and it don't boot to anything, but responds to SP Flash tool. Give it a try, if might work.
I don't have it's link, Google it
Hit Thanks if I helped sent from my SM-T211

UltimateGoblin said:
It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.
Click to expand...
Click to collapse
Did that worked?
Sent from my SM-T211 using xda app-developers app

What rom should I flash to get extra Languages?

I've got the Canadian Virgin Mobile Moto G, and I recently unlocked the carrier. I am going to unlock to bootloader to flash a rom with more languages, specifically Portuguese.. What rom should I use, I'm looking for the original Moto G software.

Zehmistah said:
I've got the Canadian Virgin Mobile Moto G, and I recently unlocked the carrier. I am going to unlock to bootloader to flash a rom with more languages, specifically Portuguese.. What rom should I use, I'm looking for the original Moto G software.
Click to expand...
Click to collapse
I'm running CM11 and a quick look the phone tells me that it have Portuguese for brazil and portugal, alternatively try any latin american stock rom: http://sbf.droid-developers.org/phone.php?device=14

Z-WolF said:
I'm running CM11 and a quick look the phone tells me that it have Portuguese for brazil and portugal, alternatively try any latin american stock rom: http://sbf.droid-developers.org/phone.php?device=14
Click to expand...
Click to collapse
Oh man, thank you for the link, I just might use that. Just a refresher, to flash It I would first unlock the bootloader, flash a new recovery, wipe, and then flash the new rom?

Zehmistah said:
Oh man, thank you for the link, I just might use that. Just a refresher, to flash It I would first unlock the bootloader, flash a new recovery, wipe, and then flash the new rom?
Click to expand...
Click to collapse
yep, but you don't need to flash a custom recovery for a Stock ROM.

Z-WolF said:
yep, but you don't need to flash a custom recovery for a Stock ROM.
Click to expand...
Click to collapse
Thank you!!! and one more question, the new rom should still be capable of getting OTA updates from whatever carrier's rom I flashed, correct?

Zehmistah said:
Thank you!!! and one more question, the new rom should still be capable of getting OTA updates from whatever carrier's rom I flashed, correct?
Click to expand...
Click to collapse
****. I think I ****ed up. http://forum.xda-developers.com/showthread.php?t=2727965

Zehmistah said:
****. I think I ****ed up. http://forum.xda-developers.com/showthread.php?t=2727965
Click to expand...
Click to collapse
Zehmistah said:
Okay so I unlocked my bootloader for my Moto G, and when It rebooted it said android was updating apps and then all the processes stopped working. It booted into the android startup but I couldn't get any processes running so it wouldnt work. I tried to reboot and now android doesn't even boot up. Should I flash a custom recovery right now and then wipe??? I haven't done anything to the phone other than carrier unlock and bootloader unlock. please help
Should I try this? http://forum.xda-developers.com/showthread.php?t=2542219 , or is it too risky right now? I'm planning to restore it to another stock firmware anyways.
Click to expand...
Click to collapse
First, don't panic.
Second, explain how do you unlock the bootloader, did you use this?
Third, what does the bootloader screen (Power+VolDown) says in the second to last line before the first break (LOCKED/UNLOCKED).
Fourth, if it says UNLOCKED, try to flash the ROM using this, otherwise try to unlock the bootloader again with the link i posted in the second point.
And don't worry as long as you can enter fastboot mode (bootloader) you can fix everything, and nothing of the things you are doing affects fastboot mode.

They all want money.
Sent from my GT-N7105 using xda app-developers app

Perry2547 said:
They all want money.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Can you elaborate?

You can add more languages without a custom ROM using MoreLocale 2.

Z-WolF said:
First, don't panic.
Second, explain how do you unlock the bootloader, did you use this?
Third, what does the bootloader screen (Power+VolDown) says in the second to last line before the first break (LOCKED/UNLOCKED).
Fourth, if it says UNLOCKED, try to flash the ROM using this, otherwise try to unlock the bootloader again with the link i posted in the second point.
And don't worry as long as you can enter fastboot mode (bootloader) you can fix everything, and nothing of the things you are doing affects fastboot mode.
Click to expand...
Click to collapse
I used that webstie to unlock the bootloader, and when I went to fastboot it did say UNLOCKED status code: 3.
I left it plugged into my PC last night because It wouldn't turn off, and I think it wasn't charging because now it's off and won't turn on. I'm going to plug it into a wall charger and wait a few to check if it's on.
After that, I'll try the method you said.
EDIT: Seems like charging doesn't work either, weird... because it said it was connecting to my PC last night in Fastboot

Zehmistah said:
I used that webstie to unlock the bootloader, and when I went to fastboot it did say UNLOCKED status code: 3.
I left it plugged into my PC last night because It wouldn't turn off, and I think it wasn't charging because now it's off and won't turn on. I'm going to plug it into a wall charger and wait a few to check if it's on.
After that, I'll try the method you said.
EDIT: Seems like charging doesn't work either, weird... because it said it was connecting to my PC last night in Fastboot
Click to expand...
Click to collapse
That's weird, doing the steps in that page don't make changes big enough in the phone to make something like that happen.
What does it says in the line below UNLOCKED, USB CONNECTED or CONNECT USB DATA CABLE while you had it connected to your pc/wall?
Why don't you try to use another cable?

Z-WolF said:
That's weird, doing the steps in that page don't make changes big enough in the phone to make something like that happen.
What does it says in the line below UNLOCKED, USB CONNECTED or CONNECT USB DATA CABLE while you had it connected to your pc/wall?
Why don't you try to use another cable?
Click to expand...
Click to collapse
I don't remember what it said.
I've tried a few different wall chargers and cables. They seem to charge my other phones but not this one. I'm going to wait an hour and then maybe put it in the freezer for a few minutes

Zehmistah said:
I don't remember what it said.
I've tried a few different wall chargers and cables. They seem to charge my other phones but not this one. I'm going to wait an hour and then maybe put it in the freezer for a few minutes
Click to expand...
Click to collapse
That's a... unorthodox approach, but reading around it just might work.
I can only recommend you to put it in a sealed container and having a rice bag at hand afterwards, just in case.
Now if you can get it to fastboot mode, try to restore a backup (if you did one) or flash a ROM, im assuming that if you can connect a cable and send commands to fastboot it is charging the phone. BTW at this point if you can send commands and are tired trying to fix it, you can execute
Code:
fastboot oem lock
and you can claim the warranty, that behaviour is not normal, maybe something in the hardware side broke but until we test it more we can't be sure.
Now while we wait in for the phone to become a popsicle, can you detail how you unlocked it?

Z-WolF said:
That's a... unorthodox approach, but reading around it just might work.
I can only recommend you to put it in a sealed container and having a rice bag at hand afterwards, just in case.
Now if you can get it to fastboot mode, try to restore a backup (if you did one) or flash a ROM, im assuming that if you can connect a cable and send commands to fastboot it is charging the phone. BTW at this point if you can send commands and are tired trying to fix it, you can execute
Code:
fastboot oem lock
and you can claim the warranty, that behaviour is not normal, maybe something in the hardware side broke but until we test it more we can't be sure.
Now while we wait in for the phone to become a popsicle, can you detail how you unlocked it?
Click to expand...
Click to collapse
Ok, so I bought the phone and got it carrier unlocked, then yesterday I decided to flash a new rom to get the languages so I went to https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Unlocked the bootloader and when the phone was about to restart from cmd it said "FAILED" but rebooted anyways. It went into fastboot again and ti said it was Unlocked, when I selected Normal Reboot, it started up with the bootloader logo and continued on normally. It was then that it displayed the android startup page (Where you select language, sign into google, connect to wifi etc.) like I haven't used the phone before. Shortly after a popup came and said " Android is updating # of apps out of 137", once that was over every single process on the phone crashed.
Now I'm where I am now.
One more thing, I booted it into recovery before I unlocked the bootloader, accidently. Do you think it maybe could've wiped the original OS on the device?

Zehmistah said:
Ok, so I bought the phone and got it carrier unlocked, then yesterday I decided to flash a new rom to get the languages so I went to https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Unlocked the bootloader and when the phone was about to restart from cmd it said "FAILED" but rebooted anyways. It went into fastboot again and ti said it was Unlocked, when I selected Normal Reboot, it started up with the bootloader logo and continued on normally. It was then that it displayed the android startup page (Where you select language, sign into google, connect to wifi etc.) like I haven't used the phone before. Shortly after a popup came and said " Android is updating # of apps out of 137", once that was over every single process on the phone crashed.
Now I'm where I am now.
One more thing, I booted it into recovery before I unlocked the bootloader, accidently. Do you think it maybe could've wiped the original OS on the device?
Click to expand...
Click to collapse
As far as i know, you can't wipe the system with a stock recovery and with a "blank" OS your phone still connects to PC.
i forgotted this existed, at this point you can't lose anything in trying it. i dont recomend the bootloader bricker part for your case.

Z-WolF said:
As far as i know, you can't wipe the system with a stock recovery and with a "blank" OS your phone still connects to PC.
i forgotted this existed, at this point you can't lose anything in trying it. i dont recomend the bootloader bricker part for your case.
Click to expand...
Click to collapse
The phone isnt't being detected when I plug it in.
I've read that leaving the phone 24 hours untouched could also help the battery. I'm going to try that\
EDIT: GOT IT TO TURN ON!!!

Ok, so I got it working. The thread you told me first helped!! It works fine now with the Brazilian software. Thank you very much, you're a life saver.
Now... I've got another moto G to do the same to

Zehmistah said:
Ok, so I got it working. The thread you told me first helped!! It works fine now with the Brazilian software. Thank you very much, you're a life saver.
Now... I've got another moto G to do the same to
Click to expand...
Click to collapse
You had me worried there, i though it was a goner. in the end everything turned out okay.
Happy to be of service.

fastboot erase all --> no IMEI (unsolvable atm)

Hello,
so... yep, I did "fastboot erase all" :cyclops:.
But if I boot into bootloader I can still get my imei with "fastboot getvar imei", though the rom doesn't recognize it. Nope, not even that anymore.
Is it just corrupted or something? Can I still "unbrick" my phone?
(I'll try to flash the stock firmware, but it'll take a while to download) did not work so far.
Stuff I tried:
-Flashing stock firmware
-Edit #550(IMEI) with QPST
Thanks in advance!

Ralmo said:
Hello,
so... yep, I did "fastboot erase all" :cyclops:.
But if I boot into bootloader I can still get my imei with "fastboot getvar imei", though the rom doesn't recognize it. Nope, not even that anymore.
Is it just corrupted or something? Can I still "unbrick" my phone?
(I'll try to flash the stock firmware, but it'll take a while to download) did not work so far.
Thanks in advance!
Click to expand...
Click to collapse
If your imei displayed in fastboot mode then you might have a chance to reflash pure stock including recovery and reflash the bootloader. If that doesn't work I am sorry my friend, at this point in time it cannot be recovered.

skyguy126 said:
If your imei displayed in fastboot mode then you might have a chance to reflash pure stock including recovery and reflash the bootloader. If that doesn't work I am sorry my friend, at this point in time it cannot be recovered.
Click to expand...
Click to collapse
It was displayed... then i flashed stock firmware and did other stuff (didn't get it to work). Now it is not displayed in fastboot. I do get a signal occasionally, so that's "good" i guess.
I'll buy a new one and use this one for testing and might try to fix it when somebody has come up with something. It's not that expensive afterall and I was actually planning on buying a 2. Gen or a 2014 version :3

Ralmo said:
It was displayed... then i flashed stock firmware and did other stuff (didn't get it to work). Now it is not displayed in fastboot. I do get a signal occasionally, so that's "good" i guess.
I'll buy a new one and use this one for testing and might try to fix it when somebody has come up with something. It's not that expensive afterall and I was actually planning on buying a 2. Gen or a 2014 version :3
Click to expand...
Click to collapse
If you are going to use the old one for testing would you mind giving this a try: http://forum.xda-developers.com/showthread.php?p=57054884
[MOD][SCRIPT] Get More Storage by Reloacting Dalvik Cache!

sure
skyguy126 said:
If you are going to use the old one for testing would you mind giving this a try: http://forum.xda-developers.com/showthread.php?p=57054884
[MOD][SCRIPT] Get More Storage by Reloacting Dalvik Cache!
Click to expand...
Click to collapse
Sure, why not? Well, I'll try it in a few days since I'm quite busy (school/work).

Ralmo said:
Sure, why not? Well, I'll try it in a few days since I'm quite busy (school/work).
Click to expand...
Click to collapse
Thanks!

I don't have a computer here in front of me, but if I remember correctly it should be possible to restore/set your IMEI using CDMA workshop if you are able to get your MSL

elrod16 said:
I don't have a computer here in front of me, but if I remember correctly it should be possible to restore/set your IMEI using CDMA workshop if you are able to get your MSL
Click to expand...
Click to collapse
I already ordered a 2. Gen Moto, but I could return it. Would be nice if you could show me how to do that (I already tried a bit with qpst, but it didn't work and i lost my motivation ^^). Link maybe?
The problem is that I can't really mess with my phone, I need it and I'd rather know how to fix it than try for hours and hours and not be able to use it :/ That's why I just gave up

HELP!!!!!! Locked bootloader after flashing a kernel and it doesn't want to boot

Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!

Colday96 said:
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Click to expand...
Click to collapse
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.

phaino00 said:
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
Click to expand...
Click to collapse
I bought the phone on ebay. Could i still get a RMA replacement ?

Colday96 said:
I bought the phone on ebay. Could i still get a RMA replacement ?
Click to expand...
Click to collapse
I don't believe so since you're not the original owner. However, it doesn't hurt to try.

If you bl locked the phone w modified software ur boned. I believe that RMA availability is transferrable from owner to owner, however, I also believe that they will refuse to RMA a phone which technically broke because AVB is doing its job properly. You can try but I'd say your chances are slim. Sorry mate. Also future reference: if you don't have any reason in particular to relock your phone, just don't. You'll save yourself the hassle of having to do it again and it wiping the phone everytime any software thing goes wrong or anytime u want to upgrade custom ROM or kernel or anything of the sort. This goes for any phone not just those with android verified boot.

phaino00 said:
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
Click to expand...
Click to collapse
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?

Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Assume they will.

Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Yes they will know but they have proprietary software to forcefully unlock/reformat the phone properly if they so choose to actually accept the phone

This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?

Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Click to expand...
Click to collapse
You can still sell it for around 150 for parts on ebay

Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400
Click to expand...
Click to collapse
Can't you restore using the stock zips from google?

Poebat said:
Can't you restore using the stock zips from google?
Click to expand...
Click to collapse
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail

Nandolkz said:
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Click to expand...
Click to collapse
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?

Poebat said:
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Click to expand...
Click to collapse
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...

Nandolkz said:
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Click to expand...
Click to collapse
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat

Poebat said:
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Click to expand...
Click to collapse
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?

Colday96 said:
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Click to expand...
Click to collapse
He doesn't have a working OS so I doubt it

Here is what is happening to me... Any ideason how to fix it? ?

Nandolkz said:
Here is what is happening to me... Any ideason how to fix it? ?
Click to expand...
Click to collapse
Try flashing the stock rom with fastboot

Poebat said:
Try flashing the stock rom with fastboot
Click to expand...
Click to collapse
Here

Question Hard brick

Hello good to all,
It turns out that I have the device with a hard brick and I can't find a solution to repair it, I've been looking for a similar thread, but nothing. It won't let me in, it's not fastboot, not in recovery or anything, and if I turn it on normally I get: The current image have been destroyed...
How I got to this situation, was after rooting the device with a tutorial here, which worked perfectly for me. It was later when I had the great idea of closing the bootloader with the rooted device, and since then it gives me this error.

Suishida22 said:
when I had the great idea of closing the bootloader with the rooted device
Click to expand...
Click to collapse
And you want us to do what. You ruined your own device and now you have to live with it.

cykalala said:
And you want us to do what. You ruined your own device and now you have to live with it.
Click to expand...
Click to collapse
I don't want you to do anything, just let you know if there is any way to recover it, because on my own I can't find anything

Suishida22 said:
I don't want you to do anything, just let you know if there is any way to recover it, because on my own I can't find anything
Click to expand...
Click to collapse
you need to use msmtool, it is paid, remote service cost 8-10 usd

SrCDA said:
you need to use msmtool, it is paid, remote service cost 8-10 usd
Click to expand...
Click to collapse
Thanks mate, could you explain me a little how it works and how to get this program? I don't mind paying if it gets fixed.

Suishida22 said:
Thanks mate, could you explain me a little how it works and how to get this program? I don't mind paying if it gets fixed.
Click to expand...
Click to collapse
1)Just go to service center , if phone is in warranty , they will just flash the device with STOCK ROM using msm tool (best )
2)however they might even replace motherboard for no reason but that will also fix the device (time taking)
3) last option is to use paid msm flashing services costs from 5to 10$ USD , you can find them by Google search (risky)

I had about the same problems, my GT Neo 2 does not load fastboot further. The cyclical startup process is repeated.
Stupidly, I understand now, I decided to wipe data in TWRP recovery
This is what it looks like - youtube
I tried to install custom recovery from this topic, all stages passed without problems, but at the end after rebooting fastboot loops
Have you solved this problem, if so, in what way?

udp
installing this method
but root I couldn't get here
I tried to unlock twrp using the magic installation, but the problem described above appeared

I think I have the same problem as others. Realme appears and restarts continuously. It does not go into fastboot because the boot loader is blocked. What can I do?

SrCDA said:
you need to use msmtool, it is paid, remote service cost 8-10 usd
Click to expand...
Click to collapse
Do you run that service?

My phone bootloops and is able to boot into stock recovery, any chance to revive?

S1611 said:
My phone bootloops and is able to boot into stock recovery, any chance to revive?
Click to expand...
Click to collapse
yes

SrCDA said:
yes
Click to expand...
Click to collapse
How?

S1611 said:
How?
Click to expand...
Click to collapse
do you have telegram?

SrCDA said:
do you have telegram?
Click to expand...
Click to collapse
yes