First time poster, hi to all and thanks in advance for any help you can provide.
My LG G5 H850 is some what in a bricked state, after a bad kdz update, my fault of course. It seems to have wiped all partitions.
The phone will only boot to fastboot, there is no recovery or download mode. Using the vol – and power, vol + and inserting the cable still sends me to fast boot.
I have the kdz, extracted that, extracted the dz. The bootloader is in an unlocked state.
When trying to flash the laf with fastboot flash laf laf.img the message I get is
Sending 'laf' (33448 KB) OKAY [ 0.819s]
Writing 'laf' FAILED (remote: 'cannot flash this partition in unlocked state')
fastboot: error: Command failed
Locking the bootloader gives a message FAILED (remote: 'device is locked. Cannot flash images')
adb commands don’t work error: no devices/emulators found
LGUP can’t see the device, there is no handset connected, please connect a handset(s).
I’ve looked at every post I can find regarding this be it about the LG or other devices and can’t get anything working.
Is there anything else I could try or some way to flash this partition to get to download mode?
As you can tell I’m a noob on this.
{
"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"
}
You're not a noob, at least when it comes to troubleshooting, so kudos for that.
Have you tried following this guide?
totalnoob34 said:
You're not a noob, at least when it comes to troubleshooting, so kudos for that.
Have you tried following this guide?
Click to expand...
Click to collapse
Thanks for the reply, I have looked at this but unfortunately, I can’t get the phone into download mode for the pc to detect it.
When I “Hold Vol+ and connect to PC while it was powered off” download mode flashes for a split second then straight back into fastboot.
I’m thinking if I can get the laf to flash I might be able to get into this, I have seen on other posts about “Shorting JTAG Pins” but most of those are for older LG models, can’t find anything about this regarding the G5.
Drewlandsupri said:
Thanks for the reply, I have looked at this but unfortunately, I can’t get the phone into download mode for the pc to detect it.
When I “Hold Vol+ and connect to PC while it was powered off” download mode flashes for a split second then straight back into fastboot.
I’m thinking if I can get the laf to flash I might be able to get into this, I have seen on other posts about “Shorting JTAG Pins” but most of those are for older LG models, can’t find anything about this regarding the G5.
Click to expand...
Click to collapse
Hmm, that may work, but I have no first hand experience on it unfortunately. JTAG pins usually exist on any model, but they may not be accessible to the user.
Related
So I decided to go ahead and flash Lollipop to my Nexus 7 once I saw the factory image was out. All was going well, bootloader unlocked, and initiated the flash-all script, but then disaster. My cable moved ever so slightly and my tablet became disconnected after the flash process had wiped the previous version and the recovery. I get the bootloader just fine, fastboot communicates just fine for device check (fastboot devices returns a serial number), but adb does not. To make matters worse, I can't boot into recovery.
I've tried just about everything seemingly. Neither toolkit or manual command line work has worked so far. Both return:
FAILED (command write failed (invalid argument)))
then tries to send the bootloader, same response
then:
Rebooting into bootloader...
FAILED (command write failed (unknown error)))
sending 'boot' (5146 KB)
FAILED (command write failed (no such device or address)))
And now I'm at a loss. What did I do to goof this badly?
Update:
Rebooted PC, changed cable (desperate measures), tried flash-all after fastboot devices listed the serial number. Got as far as sending bootloader and then I got:
FAILED (data transfer failure (too many links)))
rebooting into bootloader...
FAILED (command write failed (Unknown error)))
Archive does not contain 'boot.sig'
error: memory full
HELP!
Every solution seems to involve the ADB in some way.. I just want to mention with the lack of functioning OS on the tablet, I have no adb capabilities which had led me to wonder what exactly happened...
WRX97 said:
Every solution seems to involve the ADB in some way.. I just want to mention with the lack of functioning OS on the tablet, I have no adb capabilities which had led me to wonder what exactly happened...
Click to expand...
Click to collapse
You're obviously not looking at any revelant guides. adb does not work except in custom recoveries or booted into the OS. It does not and never will work while in bootloader/fastboot mode. You should just skip the flash-all and run the commands in bootloader manually.
I've tried flashing individually to no avail. When I try anything, whether it be flashing new stuff on, erasing anything, its all met command write errors either for invalid arguments or unknown errors
Is my tablet a write off at this point? No one seems to have any advice...
WRX97 said:
Is my tablet a write off at this point? No one seems to have any advice...
Click to expand...
Click to collapse
Well without knowing what commands you are using and the errors you are receiving, it's hard to give more advice.
{
"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 comes from attempting a flash
No one has any suggestions for the above error messages?
Seems like maybe the fastboot drivers aren't working? Can you do fastboot devices and get a response?
Fastboot devices gets a response
Fastboot devices returns the device serial number, which makes me wonder what the true problem is.. Corrupted boot loader?
Hello there,
My brother had a Redmi note 4X from last 2-3 years. One fine morning it decided to die and wouldn't start. So i took it upon myself to revive it (as i have the experience with Roms, flashing etc.).
First i tried the usual solutions i.e, MiFlash, but i came to know the bootloader is locked. Then i switched to EDL mode (Testpoint) and successfully flashed the Fastboot Rom (MIUI 8, MIUI10) but the phone wouldn't start, stuck on MI logo or bootloop.
Then i searched here and came across QFIL tool. First i got Sahara errors, searched for the solutions and came to know that you have to press the Download button ASAP after you connect EDL mode. Solved the Sahara error, Rom started to flash but suddenly it showed ' Process Failed: Attempted to divide by zero '.
Tried again, same error. Now whenever i process reaches to flash my ' Userdata.img ', it shows Attempted to divide by zero error. Everything else works fine, the drivers are good, the files are good, tried different fastboot roms, but when it comes to flash userdata.img, it shows error and fails.
while it gets successfully flasheflashed in MiFlash (but bootloop).
Now it doesnt seem to have any solution left (i couldnt find). so i have resorted to post it here.
It would be a great help if anything helpful is posted here.
Regards.
Have you choosen "clean all" during MiFlash?
If not use clean all option.
Remember also to put ROM in short named catalog inside of systemroot drive like that:
{
"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"
}
have tried everything, it flashes in MiFlash but with bootloop.
And in QFIL, it flashes with userdata.img error.
nothing else works.
cybercracker` said:
have tried everything, it flashes in MiFlash but with bootloop.
And in QFIL, it flashes with userdata.img error.
nothing else works.
Click to expand...
Click to collapse
It's hardware problem, probably emmc broken
zoel.fahmi said:
It's hardware problem, probably emmc broken
Click to expand...
Click to collapse
so no chance of getting it sorted out ?
cybercracker` said:
so no chance of getting it sorted out ?
Click to expand...
Click to collapse
You can, if you can find another emmc or a note 4x with broken screen selling for parts
cybercracker` said:
have tried everything, it flashes in MiFlash but with bootloop.
And in QFIL, it flashes with userdata.img error.
nothing else works.
Click to expand...
Click to collapse
Use QPST version 2.7.438.3 (Google it), anything below and you get userdata write error
Hey I'm new to this forum and Android Tablets in general. I have received a Vodafone Smart Tab 4G, which doesn't boot up. It's an old Tablet and it hasn't been used in a couple years. I want to see if I can make it boot up and test whether it's still usable for minor tasks. I thought I'd try to install an update using an SD card, but it's surprisingly impossible to find anything from an official source. The service menu does say "KTU84P release-keys" which seems to suggest that it has Android 4.4.4 installed.
What I've tried so far:
1: Go into the service menu and do a factory reset.
2. Try to find an update file to install through SD card method (to no avail)
3. Put some alleged stock roms onto an SD card and try to use the update function (fails on the verification step)
4. Installed ADB & Unsigned Mediatek Vcom Drivers on Windows 10. ADB has no connection to the Tablet.
5. Downloaded and tried SmartTab4G_Recovery_KK_benjaminwan to no avail. It gets stuck at "waiting for device".
6. Downloaded SP Flash tool, but failed to find a ROM for the Smart Tab 4G with a scatter file.
7. Out of desperation I tried to flash it with a Smart Tab 3G Rom which had a scatter file, but when I press download nothing happens.
My current understanding is that the standard service menu isn't meant to be used to flash the firmware. If I had an official update file I might have had some success, but I couldn't find one. All the other attempts involving a connection to my Windows 10 PC failed, which seems to indicate that I might be using bad drivers. I'm honestly at my wits' end and I don't understand why this is any more complicated than going to the manufacturers website, finding my device, downloading the most recent system software and flashing it through the service menu. Hope someone can help me out with this one.
Update: Tried a different computer. Partial success. Device manager actually recognized an Android device this time. I installed the usb driver and the recovery batch actually didn't get stuck on "waiting for device" this time. That's great news, although I didn't get much further. Here's what I got:
{
"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"
}
Thread can be closed. I got it after all with the help of the available information. Turns out the recovery.bat was a dead end. Not sure why it didn't work for me with the batch. I tried the approach explained here with cmd and it worked fine.
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
Once I was in the cwm everything went smoothly since verification was disabled and I could install a custom rom. This probably took me way longer than it should've, but at least it's working now.
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.
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 ?