Anyone know how to fix a boot loop issue? Looks like my smartphone decided to go into a boot loop. My Realme GT2 Pro isn't seen by my PC in this state.
Soft-brick or hard-brick? Can you access the bootloader? Do you have ABD drivers on your PC?
I don't know the difference between a soft brick and hard brick. It starts to boot and recycles. I can manage only to get into this strange recovery mode. I tried all 3 options you see on the screen and there is no difference.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://imgur.com/DE0nePX
It's soft-bricked... it's easy to fix... But do you flashed the phone or just started bootlooping all of nothing?
It just started this yesterday for no reason. I was deleting some apps I don't use when it started.
How can I fix this when the device can't be seen by the PC?
Since you said that tried all three options from Recovery mode means that there's no more data to recover... So, just re-flash the phone... You'll need the ADB drivers for the PC to recognize the phone on bootloader...
I managed to get the phone into a condition where it is recognized by a qualcomm QDLoader. Where do I go from here?
This is EDL mode... This is for severe cases, which is not yours, for now... Is your phone unlocked?
I think the phone is unlocked right now
No fastboot available so how do I flash an image in EDL mode?
Are you sure you doesn't have access to bootloader? Start the phone with the power button + volume down...
Anyway, in EDL mode you can flash your phone with QFIL, but it's very buggy... Or with MSM Download Tool, which is flawless, but the problem is getting access to this software... That was my problem until today as you can see here...
MSM Downloaf Tool for realme GT 2 Pro
Does anyone know how to access this tool? This is ridiculous, realme has no useful tool to flash their phones and the one that is useful are impossible to access... The only one that I have access was one patched for some especific Oppo phone...
forum.xda-developers.com
I guess I'm willing to pay to have this resolved or return for a refund
I paid a small fee and this was resolved
robert3892 said:
I paid a small fee and this was resolved
Click to expand...
Click to collapse
the solution is change slot
aaronisaacm said:
the solution is change slot
Click to expand...
Click to collapse
Change slot?
Related
Hey,
I recently got a cheap, slightly used chinese version Nokia N1. But because without the Google Services its pretty much useless to me, I want to root it and install a custom ROM.
I followed 2 tutorials:
https://forum.xda-developers.com/nokia-n1/help/nokia-n1-root-t3125771
and
https://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
But I always get stuck on the part with the Recovery Launcher.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To give some background, here are the steps I did:
Because fastboot and the launcher won't see my device if its in MTP or PTP, I disabled both. That seems to work fine.
I "unlocked" oem in the developer settings and also allowed USB debugging.
I started the Recovery Launcher with admin privileges and used option T4.
It boots into recovery mode, but I just get errors all over the place bacause the device is still locked. So i just typed "fastboot oem unlock". Then T4 again.
Thats where this error occurs. From what I read, this should put me into a CWM recovery session. But it doesn't. It just stays in the fastboot mode window.
I'm pretty new to this android modding thing, so don't expect to much knowledge from me.
with much thanks
~David
Bump
I really hope bumps are allowed here
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
nuzzydev said:
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
Click to expand...
Click to collapse
The thing is, there are no other solutions out there I really know about. I searched google up and down and got no real result.
I think my problem is that my android version isn't 5.0.x, like almost every english tutorial suggests. It is 5.1.1.
oh God... my fault sorry
Hello,
i'm new in the forum, i have problem with Meizu M6 Note M721H because i have installed twrp recovery with app crack (3.2.1) and next i have deleted SO (flyme firmware) and i have cleaned the phone, after i have updated twrp to 3.2.2-0 version and after reboot, after 1-2 seconds of meizu logo the screen becomes black and the twrp doesn't start....and i haven't firmware installed...fastboot mode working but i haven't permissions because bootloader is locked and secured. I can't use well QFIL.exe and after after I Have entered the files in the program and start download, i have the issue: "Download Fail: Switch to EDL FailFailed to Switch to Emergency Download mode". I tried everything, could you help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe this can help you to fix that error.
https://geekofia.wordpress.com/2017/10/12/download-failswitch-to-edl-failfirehose-fail-fixed/
MatteoGhost07 said:
Hello,
i'm new in the forum, i have problem with Meizu M6 Note M721H because i have installed twrp recovery with app crack (3.2.1) and next i have deleted SO (flyme firmware) and i have cleaned the phone, after i have updated twrp to 3.2.2-0 version and after reboot, after 1-2 seconds of meizu logo the screen becomes black and the twrp doesn't start....and i haven't firmware installed...fastboot mode working but i haven't permissions because bootloader is locked and secured. I can't use well QFIL.exe and after after I Have entered the files in the program and start download, i have the issue: "Download Fail: Switch to EDL FailFailed to Switch to Emergency Download mode". I tried everything, could you help me?
Click to expand...
Click to collapse
what do you mean you deleted "SO"?
if i understand correctly you replaced stock recovery with twrp but it can not load because your bootloader is locked.
i am not very well familiar with qfill but you are having wrong port open "900E" . you need to enable "9008".
try if this trick works https://www.youtube.com/watch?v=fOpZsUQwOrY
fortunately i have the same problem, same phone, unfortunately you need to open it up, as i understand there are some circuits you need to shortcircuit to load the fastboot, looking into this now, will post updates
And how did someone solve a black screen problem after TWRP botting? I have the same problem and I can not deal with it; /
master2007 said:
And how did someone solve a black screen problem after TWRP botting? I have the same problem and I can not deal with it; /
Click to expand...
Click to collapse
hold down the power button for 20 seconds?
Assuming you still have an the Android OS installed.
Unbrick Meizu M6 note
Hello, why don't you try to flash it with qfil rom?
Device is a pretty much new LG V30 from verizon, running android 8.
I have done pretty much nothing with the device yet. No root, no tinkering, nothing. I accidentally accepted the software update request it showed me today, which I didn't want. I shut the device down but everytime I would turn it on it would start the update progress.
The only other option I had was booting into recovery, so I did that. I was presented with the following options:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I went with factory reset. After that the phone won't boot anymore, and all I see is this screen:
What can I do now?
Again: No root. No unlocked bootloader. Nothing. I used LG's "require password on boot" feature though, which I assume is equal to android's full disk encryption. (?)
I talked to LG already since it's under warrenty (got it literally last week) - LG however told me the warrenty is void because there is a small crack on the back of the phone. WTF? Is that even true? I didn't drop the phone. I don't even know where the crack comes from. It's small. Shouldn't the warrenty cover that TOO instead of voiding the warrenty for everything else? Like jesus christ all I want is LG to fix my software why does a crack on the back matter?
From what I see my only option is to access fastboot and re-flash the ROM? The thing is: How do I access fastboot on this phone? Power and Vol- brings me into recovery (stock) everytime. Are there flashable images for the V30?
No one knows what I should try or what I could look into? This doesn't sound like it could be something overly complex to me.
Issue still persists. I had a talk with verzion at their store and they said I'd have to pay a $149 deductible. So what can I do now?
I'm assuming flashing a ROM via fastboot. Two questions:
1) Where can I get the ROM from?
2) How can I access fastboot on this phone? The method suggested everywhere puts me in LG's stock recovery, not in fastboot.
So I have this phone Xiaomi Redmi 10X, and I wanted to put Pixel Experience 11.0 in it, after seeing this thread on GitHub.
To my surprise, following steps on that link was not that easy!
I flashed MIUI 22.1.19 manually (not in the correct way), and I ended up with a hard bricked phone.
Yesterday, while Googling about that, I managed to run into a tool called MTKClient v2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it solved my problem, by flashing original firmware and got it correctly working with the default MIUI 13 system.
BUT, that wasnt enough for me, because I still wanted to put Pixel Experience in it since I like it so much and think it is so sexy!!! So I, without knowing what I was doing, erased all the partitions in my phone with that tool.
Now, I cant get it to connect to that tool to work or connect with my device. On the cmd behind though, I do get some hope after seeing that device is still recognized in some way, but that's all there is to it, it doesnt go further, only "Phone detected: Reading model info".
I've tried to wait and keep both volume buttons pressed at the same time, but to no avail.
Since this, I've tried several tools but none is working to reset my partition table to original state, since I think that's my problem.
Any idea how to fix it?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
No. What is that?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
Even if it connects, it shows no partitions to write over.
What it needs, is to first restore the erased partitions, I think, and then writing (flashing) the firmware into it.
Appreciate anyone who can help! I was tooling around trying to unlock my AT&T locked SD1 but was basically unable to get it working. So I decided to undo everything with a factory reset and relock the bootloader...and that's when I bricked my device.
I am unable to go past the bootloader screen and unable to either Start the device or enter Recovery Mode.
Not sure how else to proceed.
So, is the bootloader currently locked?
Does fastboot flashing unlock work?
Renate said:
So, is the bootloader currently locked?
Does fastboot flashing unlock work?
Click to expand...
Click to collapse
Unfortunately, no. Adb is no longer recognising the device and I'm stuck in boot select screen unable to even Start or enter Recovery Mode.
Bootloader is currently locked.
Not that it does a lot of good, but you can see fastboot?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what I see.
I think you are out of luck until the firehose programer for the DUO out. I got the same device like this. Maybe boot.img is broken for the device, or recovery partition got messed up. Basically the device have to restore from the ground up.
Sadly MSFT does not provide a restore solution other than the recovery image which the device have to enter the recovery mode at least.
JimmyRespawn said:
I think you are out of luck until the firehose programer for the DUO out. I got the same device like this. Maybe boot.img is broken for the device, or recovery partition got messed up. Basically the device have to restore from the ground up.
Sadly MSFT does not provide a restore solution other than the recovery image which the device have to enter the recovery mode at least.
Click to expand...
Click to collapse
I was worried you'd say something like that. Down in the dumps.
May be this can help you?
https://www.reddit.com/r/surfaceduo/comments/wn5joi
Sharkam said:
May be this can help you?
https://www.reddit.com/r/surfaceduo/comments/wn5joi
Click to expand...
Click to collapse
What in the name of all things holy?! Man, I'm gonna have to look deep into this and figure it out. Problem is, I am not nearly as smart as that guy which is itself gonna be a huge challenge. That said, I do have all the patched imgs on my desktop...so perhaps there is a way back. IF I can figure out the process as laid out here.
Thanks for this pal at least it helps.
im here with you i need bootimg from 2022.823.41 ota went threw now stuck.. im on the duo 2
This is the duo 1 forum.
There is a duo 2 forum, but it is less active.
did u tryed
`fastboot reboot recovery`
yes .. it just falls back to bl .. I need the boot.img from 2022.823.41 update . I tried to capture the link but it flashed before I told it.
this is the duo2 btw
Me too I have the same issue. Did you found how to fix it ?