Hi guys
Please help me to solve my problem. I tried several methods but unfortunately it was not solved. Does anyone have a suitable solution?
My Phone Rog phone 5 ww ver bootloader Locked
Jamshid66 said:
Hi guys
Please help me to solve my problem. I tried several methods but unfortunately it was not solved. Does anyone have a suitable solution?
My Phone Rog phone 5 ww ver bootloader Locked
Click to expand...
Click to collapse
What is the specific problem you are trying to fix?
twistedumbrella said:
What is the specific problem you are trying to fix?
Click to expand...
Click to collapse
My phone (Rog phone 5) turned off and didn’t turn on!!
After connecting to PC, it enters to EDL Mode and doesn’t exit from it!!
Help me that how can exit it from EDL Mode and use my phone again!?
Jamshid66 said:
My phone (Rog phone 5) turned off and didn’t turn on!!
After connecting to PC, it enters to EDL Mode and doesn’t exit from it!!
Help me that how can exit it from EDL Mode and use my phone again!?
Click to expand...
Click to collapse
What were you doing when it started? Did you unlock the bootloader? Was it rooted? Did you flash something?
twistedumbrella said:
What were you doing when it started? Did you unlock the bootloader? Was it rooted? Did you flash something?
Click to expand...
Click to collapse
It went to this state when the mobile phone was finished charging
Jamshid66 said:
It went to this state when the mobile phone was finished charging
Click to expand...
Click to collapse
It's a completely stock phone? You've never unlocked the bootloader or tried to flash anything?
If that's the case, you'd be far better off contacting Asus about it. It is well within the year warranty and you may require a special cable to flash it correctly yourself. It sounds like it may be defective, so even recovering it could only be temporary.
Contact Us | ASUS
twistedumbrella said:
It's a completely stock phone? You've never unlocked the bootloader or tried to flash anything?
If that's the case, you'd be far better off contacting Asus about it. It is well within the year warranty and you may require a special cable to flash it correctly yourself. It sounds like it may be defective, so even recovering it could only be temporary.
Contact Us | ASUS
Click to expand...
Click to collapse
I talked to the support department but did not answer
Is there a way I can do it?
I feel my bootloader is broken
Jamshid66 said:
I talked to the support department but did not answer
Is there a way I can do it?
I feel my bootloader is broken
Click to expand...
Click to collapse
Probably need a deep flash cable, I believe it's called
twistedumbrella said:
Probably need a deep flash cable, I believe it's called
Click to expand...
Click to collapse
It says they are updating the page. You probably won't hear back over the weekend and they take a couple days to reply normally. It is the safest way to restore the phone, though.
Making cables and using software that doesn't come directly from Asus for restoring from a brick is risky. It's a last resort when they say they won't help.
twistedumbrella said:
It says they are updating the page. You probably won't hear back over the weekend and they take a couple days to reply normally. It is the safest way to restore the phone, though.
Making cables and using software that doesn't come directly from Asus for restoring from a brick is risky. It's a last resort when they say they won't help.
Click to expand...
Click to collapse
If I want to do it myself, what do you suggest because I got the phone from another country, I do not think the warranty is included
Jamshid66 said:
If I want to do it myself, what do you suggest because I got the phone from another country, I do not think the warranty is included
Click to expand...
Click to collapse
I suggest looking at how they did it on the ROG Phone 3 and then seeing what, if any, of that has a matching ROG Phone 5 version. This phone is only a couple months old, so there isn't a whole lot of public research yet.
twistedumbrella said:
I suggest looking at how they did it on the ROG Phone 3 and then seeing what, if any, of that has a matching ROG Phone 5 version. This phone is only a couple months old, so there isn't a whole lot of public research yet.
Click to expand...
Click to collapse
Do you mean that I have to use files that referse to Rog phone 3 ?
Jamshid66 said:
Do you mean that I have to use files that referse to Rog phone 3 ?
Click to expand...
Click to collapse
No. That will break the phone much worse.
twistedumbrella said:
No. That will break the phone much worse.
Click to expand...
Click to collapse
So we have to wait for more files For ROG 5
Jamshid66 said:
So we have to wait for more files For ROG 5
Click to expand...
Click to collapse
I honestly don't know. Hopefully someone else will come along that can help.
twistedumbrella said:
I honestly don't know. Hopefully someone else will come along that can help.
Click to expand...
Click to collapse
what is your suggestion?
Jamshid66 said:
what is your suggestion?
Click to expand...
Click to collapse
Wait to hear back from Asus
twistedumbrella said:
Wait to hear back from Asus
Click to expand...
Click to collapse
I speak with a warranty, unfortunately my request was rejected
Jamshid66 said:
I speak with a warranty, unfortunately my request was rejected
Click to expand...
Click to collapse
If the device is under warranty and this happened without you altering anything I don't understand how they can reject it
If the device is only stuck in EDL mode but no hardware damage and has a working bootloader you can try (entirely at own risk):
1 - Make (or buy) a deep flash cable and see if you can snap it out of EDL mode by activating it a few times while the device is connected. (Chances are slim but it does work sometimes).
2 - Disconnect and re-connect the battery pack from the mainboard. The battery connector of ROG 5 is located on the right side between the north battery and the mainboard when looked from the back. You need to remove the top part of the motherboard for access to it. It's not a huge operation but requires some basic tools and some phone adhesive for closing the backcase again. Some cooling paste is also useful to repaste the heat conducting parts before closing it again (optional).
However, if the device doesn't have a working boot and/or it's really damaged then all above is useless.
Related
http://www.fotosik.pl/pokaz_obrazek/pelny/7ebe08a2b2e135ea.html
http://forum.android.com.pl/attachment.php?attachmentid=95985&d=1413954853
http://forum.android.com.pl/attachment.php?attachmentid=95987&d=1413958300
http://www.fotosik.pl/pokaz_obrazek/pelny/d08020e375678c25.html
please help. Do RMA repair motherboard? is a way to repair this phone? can lock the bootloader and clean templar flag through fastboot??
Link 2 and 3 don't work.
Please write full description of problem here. Do not link to external sources as we probably wont read them
I see from link 1 you're using Wugfresh to flash stock. Most of us discourage use of toolkits, particularly when flashign stock is so easy.
Please click the link in my signature and read 2 threads. The adb and fastboot thread and the return to stock thread.
If you get the same error doing things properly, your NAND is fried and needs to be sent for repair. That is usually what "write failure" means. However since you are using toolkit, I cannot say that the error is genuine or not... So please use fastboot to flash stock
http://www.fotosik.pl/pokaz_obrazek/pelny/6ffdde1cca5a3865.html
up
tuningsea said:
http://www.fotosik.pl/pokaz_obrazek/pelny/6ffdde1cca5a3865.html
up
Click to expand...
Click to collapse
Unfortunately, it looks like the emmc is toast. You'll need to send it in for repairs. Contact Google if you've bought from the playstore. Bought from a retailer? Contact LG.
Good Luck!
I bought the LG. If I have unlocked bootloader + root means that for the repairs I have to pay?
Did you flash something recently? Because EMMC failure can be if you flash something not for your device (e.g kernel,rom and etc) or did got wet or fallen down? Or it's just happened out of sudden?
It happened suddenly, even I do not know how. I used a flashlight for 30 minutes the phone is restarted and died. I can enter fastboot mode only
tuningsea said:
I bought the LG. If I have unlocked bootloader + root means that for the repairs I have to pay?
Click to expand...
Click to collapse
If your warranty falls under LG, you might need to pay up since the bootloader is unlocked. Try to lock the bootloader and reset the tamper flag if you can.
Follow the last part of this tutorial:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
"fastboot boot path / to / TWRP.img" and stands on the logo teamwin. nothing can be done
http://www.fotosik.pl/pokaz_obrazek/pelny/ac67c81c2b162108.html
Motherboard die? whether it is for sure the motherboard?
tuningsea said:
http://www.fotosik.pl/pokaz_obrazek/pelny/ac67c81c2b162108.html
Motherboard die? whether it is for sure the motherboard?
Click to expand...
Click to collapse
You cannot write the bootloader, which means teh device (NAND Chip) that you are writing to is likely failed. This is in turn attached to the motherboard, so yes - probably needs a new Motherboard. Probably.
GOD
tuningsea said:
It happened suddenly, even I do not know how. I used a flashlight for 30 minutes the phone is restarted and died. I can enter fastboot mode only
Click to expand...
Click to collapse
How hot was the phone when it happened? I'm wondering if it has anything to do with the phones overheating (for some reason, like too high thermal throttling - remember the Xbox RROD)?
http://forum.xda-developers.com/google-nexus-5/help/stuck-google-boot-screen-fix-flashing-t2910842
Look at my thread
AndreIrawan97 said:
http://forum.xda-developers.com/google-nexus-5/help/stuck-google-boot-screen-fix-flashing-t2910842
Look at my thread
Click to expand...
Click to collapse
I do not think you have read THIS thread.
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
Hi all,
My Pixel bricked a few months back & was still under warranty. It was replaced & I've just today received the original bricked phone back to my surprise.
When plugged in via USB it shows as Qualcomm HS-USB QDLoader 9008
QFIL detects it but I can't find any .xml, .mbn, .hex files to flash it with.
Can i copy anything of the working phone (exact same model), to my laptop to then revive the bricked phone?
Thanks in advance for your advice...
Any luck with this? My girlfriend's Pixel is stuck in this mode as well. I can't find these files anywhere on the net. She's starting to get a little cranky.....please help!
Unfortunately the files you are looking for are not available. The have not been released
shagbag913 said:
Unfortunately the files you are looking for are not available. The have not been released
Click to expand...
Click to collapse
Thanks for the reply. How and when do these files usually get released? Do you advise I keep the device in hopes that I will be able to revive it in the near future?
Thanks!
Melnutz said:
Thanks for the reply. How and when do these files usually get released? Do you advise I keep the device in hopes that I will be able to revive it in the near future?
Thanks!
Click to expand...
Click to collapse
I wouldn't advise keeping it. They honestly will probably never be released, sadly.
Adventur0us said:
Hi all,
My Pixel bricked a few months back & was still under warranty. It was replaced & I've just today received the original bricked phone back to my surprise.
When plugged in via USB it shows as Qualcomm HS-USB QDLoader 9008
QFIL detects it but I can't find any .xml, .mbn, .hex files to flash it with.
Can i copy anything of the working phone (exact same model), to my laptop to then revive the bricked phone?
Thanks in advance for your advice...
Click to expand...
Click to collapse
Melnutz said:
Any luck with this? My girlfriend's Pixel is stuck in this mode as well. I can't find these files anywhere on the net. She's starting to get a little cranky.....please help!
Click to expand...
Click to collapse
shagbag913 said:
Unfortunately the files you are looking for are not available. The have not been released
Click to expand...
Click to collapse
Melnutz said:
Thanks for the reply. How and when do these files usually get released? Do you advise I keep the device in hopes that I will be able to revive it in the near future?
Thanks!
Click to expand...
Click to collapse
shagbag913 said:
I wouldn't advise keeping it. They honestly will probably never be released, sadly.
Click to expand...
Click to collapse
Wrong! I just did it!
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Follow that guide but with the files provided here https://forum.xda-developers.com/pixel/help/fix-google-pixel-help-noob-t3790470
(https://dl.google.com/dl/android/aosp/sailfish-opm4.171019.016.b1-factory-68c3a77d.zip)
All you need is a working bootloader, thank God. This just saved my ass.
Creed14 said:
Wrong! I just did it!
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Follow that guide but with the files provided here https://forum.xda-developers.com/pixel/help/fix-google-pixel-help-noob-t3790470
(https://dl.google.com/dl/android/aosp/sailfish-opm4.171019.016.b1-factory-68c3a77d.zip)
All you need is a working bootloader, thank God. This just saved my ass.
Click to expand...
Click to collapse
Your right, IF you have a working bootloader. The op does not.
I was having this same issue. Currently running crDroid and selected the Reboot Recovery option from the advanced Power Menu. It turned off but didn't come back on. Tried booting into the bootloader but got nothing. Plugged it into my PC and saw the same device description then realized I probably had a hard brick. I was about to give up when I decided to just hold the power button alone and after about 20 seconds it booted normally. Looks like I dodged a bullet.
shagbag913 said:
I wouldn't advise keeping it. They honestly will probably never be released, sadly.
Click to expand...
Click to collapse
Is there a way to pull it off a working Pixel? I have two 128GBs Pixels with the exact that were running the exact same setup (Unlocked BL with LOS15.1)
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
vlc_marcos said:
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
Click to expand...
Click to collapse
No duplicated thread are permitted
Please help us to keep the forums neat
Thanks
vlc_marcos said:
I downloaded the wrong Firmware for the Pixel 5
Click to expand...
Click to collapse
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
l7777 said:
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
Click to expand...
Click to collapse
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
vlc_marcos said:
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
Click to expand...
Click to collapse
when its plugged into a computer does the computer see it at all?
thewraith420 said:
when its plugged into a computer does the computer see it at all?
Click to expand...
Click to collapse
not at all is there some kind of hard unbrick??
vlc_marcos said:
not at all is there some kind of hard unbrick??
Click to expand...
Click to collapse
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
thewraith420 said:
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
Click to expand...
Click to collapse
Mine bricked about a month ago and Google suggested uBreakiFix. They tried to do a force flash on it but it didn't work. They ended up replacing the motherboard which fixed it, but now my proximity sensor is always on. I don't know if they can fix that or if it will require another motherboard.
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
p_a_r_s_a7 said:
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
Click to expand...
Click to collapse
Did you use any special way to even turn on the phone or reach the bootloader?
vlc_marcos said:
Did you use any special way to even turn on the phone or reach the bootloader?
Click to expand...
Click to collapse
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
p_a_r_s_a7 said:
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
Click to expand...
Click to collapse
how did you end up with it like that with bootloader locked? what caused it?
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
But you could reach fastboot right?
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
speo said:
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
Click to expand...
Click to collapse
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
speo said:
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
Click to expand...
Click to collapse
I send back to Google, i couldn't fix it
Cj719 said:
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
Click to expand...
Click to collapse
thank you anyway, it was a little light on the horizon at least ;-)
p_a_r_s_a7 said:
I send back to Google, i couldn't fix it
Click to expand...
Click to collapse
have you been charged ?
Mine is from another dealer, will see..
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