I have ls998 and it was flashed to us998 version but it started reload. Then I decided flash it to AS998 via partition dl. near 65 percent phone say that battery is empty and shut down. Now I don't have download mode, it just load to bootloader unlock menu and that's all. I must say that phone is NOT ROOTED and OEM unlock option not enabled (
Can someone help me in my situation?
{
"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://forum.xda-developers.com/picture.php?albumid=15191&pictureid=58180
https://forum.xda-developers.com/picture.php?albumid=15191&pictureid=58179
You can try to extract KDZ file to images, then use fastboot to flash the necessary images separately.
通过我的 LG-US998 上的 Tapatalk发言
lilila said:
You can try to extract KDZ file to images, then use fastboot to flash the necessary images separately.
通过我的 LG-US998 上的 Tapatalk发言
Click to expand...
Click to collapse
Have you tried to do it yourself?
Last time I spend about 14 hours and have no success but it was another LG phone. When all was done I have "sahara not responding" and "sahara server error".
I haven't tried it on the v30 yet, but flashing the files using fastboot is common practice for many phones that have full fastboot commands (like moto x pure).
If you only have fastboot, you can try and flash only the laf partition using fastboot and see if you can get dl mode working and then use it to restore the phone.
LAF may need to match whatever rom version aboot is running though.
Can you get into fastboot?
If you wiped out aboot, i think your phone is a brick.
SOLVED
My phone now working well. The solution cost 35 bucks. One man remotely repair it )))) Second day i am going happy and smiling. If your phone is brick but qualcomm 9008 is working, he will repair it
Yellow_man said:
SOLVED
My phone now working well. The solution cost 35 bucks. One man remotely repair it )))) Second day i am going happy and smiling. If your phone is brick but qualcomm 9008 is working, he will repair it
Click to expand...
Click to collapse
Yes he did the same for me and flashed "modified" AS998 firmware and my battery life is absolutely insane now. I got over 7h screen on time with 10% battery remaining yesterday. Very pleased.
Yellow_man said:
SOLVED
My phone now working well. The solution cost 35 bucks. One man remotely repair it )))) Second day i am going happy and smiling. If your phone is brick but qualcomm 9008 is working, he will repair it
Click to expand...
Click to collapse
What did he do? I'm having the same problem. I live in India. I recently flashed pie instead of oreo while I was on Pie itself by mistake.
Please tell me what he did
Related
So about a week ago I was doing stuff on my PC. I take my Redmi 5 Plus (at the time with Pixel Experience installed) and I see that the screen is completely black.
Try to reboot, nothing. Vibration, Black screen for like 5 seconds, repeat.
Try to boot into TWRP, nothing. Fastboot, still that damned black screen.
I decided to reinstall the stock firmware, and I do it through the test point method. The software takes like 40 minutes to do so, but in the end it says "Success!".
Nothing, black screen.
So, I write this post to try and find a solution, or at least now what could have happened as since then I bought the Huawei P20 Lite. It could still be usefull though.
Thanks in advance and good day
@apd911
The time that MiFlash Tool spends to flash a rom in edl mode is aproximately 13 minutes.
Try flashing the firmware that came pre-installed.
You mentioned that you can´t enter to recovery nor fastboot mode before to reinstall the rom stock but after that now you can enter to recovery stock or fastboot?
SubwayChamp said:
@apd911
The time that MiFlash Tool spends to flash a rom in edl mode is aproximately 13 minutes.
Try flashing the firmware that came pre-installed.
You mentioned that you can´t enter to recovery nor fastboot mode before to reinstall the rom stock but after that now you can enter to recovery stock or fastboot?
Click to expand...
Click to collapse
No, same thing, black screen for five seconds then reboot, even in fastboot and recovery
apd911 said:
No, same thing, black screen for five seconds then reboot, even in fastboot and recovery
Click to expand...
Click to collapse
I flashed many roms in edl mode. here you have two possible situations; if your emmc is damaged pc will detect device and will listed how it´s showed in the screenshot attached but the flash won´t be succesfull not even will start, and second if device it´s not detected in the same way that in the picture then it´s not flashing correctly.
{
"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"
}
Can you attach some screenshot?
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?
Hello, so I decided to try an root this junky phone I have which is a moxee m2160. I followed a guide on youtube, I unlocked the bootloader, then got magisk. I then created the patched-magisk.img then used my computer & fastboot to flash it too the device. I was pretty sure I had gotten it until I rebooted it an it booted back too the bootloader. I'll upload pics of my screen to show you where Im stuck. Am I able to fix the phone with my pc somehow? I probably should've gathered more info before I did it. Thanks for any answers in advance.
{
"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 the name
e..
Is there anything I can do through adb or fastboot to fix it?
whisper42000 said:
Is there anything I can do through adb or fastboot to fix it?
Click to expand...
Click to collapse
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Something like this part I forgot the part with the empty vbmeta or from stock. Search. Good luck more I don't can help. I read it only somewhere
I've done the same thing to this phone every option on that screen doesn't do anything just reboots to the same screen. Does anyone out there have this phone and have the stock ROM or anything at all that would help restore this phone. I found out it is made by KonnectOne it is a government assistance phone from Assurance Wireless and that is pretty much all I can come up with. Any assistance at all would help a noob like myself, learning as I go. Thanks.
Specs for this devices are here https://phonedady.com/moxee-m2160
Greetings members. The support team over at KonnectOne has granted my request for factory firmware for this smartphone. I am presently in the process of establishing a secure file transfer protocol with support to download the package. I will have it later this week if any members are in need of it
I have the stock Firmware.. just got it today. Who needs it
dexscam37 said:
I have the stock Firmware.. just got it today. Who needs it
Click to expand...
Click to collapse
It's been officially released by the manufacturer, after weeks of haggling with KonnectONE's office of general counsel. Here's the link.
File on MEGA
mega.nz
I have three earlier builds as well if anybody needs them.
Now to go root my moxee
What about a twrp ?
Viva La Android said:
I have three earlier builds as well if anybody needs them.
Click to expand...
Click to collapse
how to i flash the stock firmware???
dexscam37 said:
how to i flash the stock firmware???
Click to expand...
Click to collapse
QFIL (Qualcomm Flash Image Loader)
Download Qualcomm Flash Image Loader (QFIL) - Qualcomm Tool
Download Qualcomm Flash Image Loader (QFIL) to flash stock firmware on Qualcomm based Smartphone and Tablets easily in few clicks.
androidmtk.com
You will find a how-to guide in the link I sent. You will need to install the Qualcomm EDL drivers and boot your phone into EDL mode in order to use QFIL. To boot into EDL, hold volume up and down simultaneously while connecting your phone and PC.
I will be posting a full QFIL guide this weekend.
Yo guys & gals,
Out of nowhere, the tablet started randomly restarting itself. It's not possible to use it anymore as the reboots occur pretty much a moment (at most) after the system boots up (sometimes even earlier).
What I tried so far:
1. Reflashing stock FW (it was never unlocked before, always original from Sammy; I also tried firmware from a different country). I did that a couple of times already.
2. Flashed with Nand Erase and Re-Partition (with the dedicated PIT of course).
The tablet is in mint condition, never dropped, and barely used. The battery is at least in very good condition.
And this is what I get when I enter the bootloader recovery mode:
{
"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"
}
Is it salvable or kaputt? What else can I try?
PS The device doesn't reboot while in download or recovery mode if it helps.
@Umpal Does it give any hints on NAND error when entering download mode?
Saw that once on a different device of mine.
Mine shows attached info.
What do you call a good condition for the battery?
Had devices on which even 50% capacity left led to reboots untill I replaced the battery.
Tried to pull a syslog?
Btw. what you call bootloader is actually the stock recovery.
The bootloader itself is afaik not directly accessible.
@bmwdroid No, no errors in download mode (see attached).
Battery
OK, I can only assume it's in good condition but my assumption is based on the use until the very last moment — the battery was holding great and there were no issues with the charge. Granted, I can't test it now under the system to confirm that but I can leave it on in the recovery or download mode for a very long time (but for the record I didn't measure the exact time). If it was faulty I bet it would power down or restart in those modes too.
Tried to pull a syslog?
Click to expand...
Click to collapse
No. I've been out of the device "flashing business" for a long time so I need a hint on how to get it.
Umpal said:
@bmwdroid No, no errors in download mode (see attached).
Click to expand...
Click to collapse
imho there is a remarkable difference to mine:
KG Status: Prenormal
Did you search for that?
Umpal said:
.....
No. I've been out of the device "flashing business" for a long time so I need a hint on how to get it.
Click to expand...
Click to collapse
As your device is unrooted (or isn't it?) I don't know either exactly.
ADB might help but I don't know the commands right now.
something like "pull log" or so.
There're somewhere in XDA
imho there is a remarkable difference to mine:
KG Status: Prenormal
Did you search for that?
Click to expand...
Click to collapse
Indeed, I didn't think it might be different from the normal status. And the Internet has some results for this topic. I'll investigate. Thanks @bmwdroid
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 ?