good morning people had a problem with my x play, I tell them from the beginning ...
when it acquired the device had an edited rom resureccion remix 6.0, what we did was change clothing by a AOSP by sd card and installing by TWRP already had it installed, then wanting to return to 6.0 stock had a problem, the device after display the poster remains unlocked bootloader on a android doll and says erasing ... well not start and restarts automaticamnete.
and not only that, my pc with windows 7 recognizes the cell as an unknown device, having all the drivers installed and so can not flash it or get back to get another reovery and also install a rom, nose what else to try, I need help!
information of fastboot
Console. null
device is unlocked. Status code 3
Software status. modified
Related
Hello, yesterday installed installed a custom ROM Roma KF 2016 and before the installation does not detect my phone because I wanted to upload Odinie TWRP, but I found that it can have, and, although I had already loaded, I have uploaded the system, then decided to return to the 6.0.1 stock. Odin still does not detect so I decided to turn off the OEM unlock, I thought it might through it. Well, now it is the max lime because he sees it to me on WIN XP as .. Unknown device, 7 and 8.1 do not even hear the sound device is connected, and on the phone FRP Lock and even the recovery can not enter because everything after blocking, I might add that before Odin always seen it, and even how it happened to me that the FRP LOCK blocked my phone, I have uploaded a new and everything was ok. Please help, I'm without a phone. I tried to 4 PC and 3 cables. I have no idea what's going on.
Solved!
The problem started after running out of battery. I never touched the firmware before
The firmware is athene 7.0 NPJS25 93 14 18/3. The first thing i tried was installing another version of the rom but couldn't because the version installed wouldn't let me so i tried installing the same version following this thread
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Everything went well, the phone was detected by fastboot and all files were transferred without errors but the same problem persist.
Reading found out another possibles solutions like trying differents BlankFlash but always getting the "waiting device" because the phone is detected by the pc like "fastboot athene" instead of qualcomm. Tried installing the qualcomms drivers in two differents pc but the phone keep showing ass fastboot athene.
Another solution was unlocking the oem and trying downgrade but this impossible without enabling oem unlock, which i can't do since i can't enter to the system and activate the option
Any other possible solution?
Hi,
I'm not sure I'm posting in the right section but, I had a really bad experience upgrading to android 10. Really sluggish and slow... so I tried to downgrade to android 9 by using Lenovo's Rescue and Smart Assistant.
What I did, is to find the stock ROM for my model, and replace the files downloaded by the Rescue Assistant (which downloaded the latest firmware). The process went through, but now the device wont power on.
When I plug in the USB, windows makes a sound, the charging light comes on, but The rescue Assistant nor SP flash tool is able to flash the latest firmware.
Is it bricked for good?
Model : TB-XF606F
Hardware number : 60
Maybe your computer doesn't recognize your tablet. Did you ever try using sp flash tool with your tablet before? You can try reinstall or install a driver for your table if you haven't done it yet.
Well the tablet is recognized as the "mtk vcom..." in device manager. I guess it is the driver that the lenovo rescue app installed.
I have never used sp flash tool with my tablet, just the lenovo rescue.
I tried on 2 different pc and it is the same thing. I think the problem is that I can't turn off the tablet properly, even though, all I can see is a black screen.
I will try to drain the battery by keeping the power button pressed with some scotch tape. I don't know what I can do else.
Edit: I tried a few other times with flash tool using different setting for the connection (with battery and full speed) and nothnig happened. But now windows says it does not recognize my tablet.
did the same thing exactly. . bricked lenovo m10 fhd plus x600v after i flashed a downgrade version. dont try to downgrade this thing. i had already flashed it with 3 or 4 versions the same way , but when i chose to flash the oldest version available with the model , this tab got completly unresponsive , no feedback when try to boot into recovery, fastboot, or system . neither does it gets recognised in windows or anything - device manager dowsnt recognise this usb device ( in device manager properties comments it reads- USB\DEVICE_DESCRIPTOR_FAILURE). if you find a way to reflash the device please let us know. good luck .
Bricked mine after being completely running smoothly on Lineage, then was messing around trying to get gapps installed and jacked up the partitions. TWRP said no OS. Kept messing around and mistakenly locked the bootloader again with apparently an unverified boot partition. . I couldn't get SP Flash tool to work ever either. Pretty sure it's a door stop now.
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
McMeth said:
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
Click to expand...
Click to collapse
I've been reading around a little, it seems like it could be a recovery issue? try the official lineage recovery if you're not already. If you can get fastboot working at all try to reflash the stock rom and go from there.
I had a similar problem. Use a windows computer with the essential drivers (you can download from reddit) and use the official cable
DO NOT use the cable supplied with the Essential phone for data transfer, it is likely to brick your phone. Use a high quality one from a reputable manufacturer!
I bought a Motorola Moto C Plus a while ago so I can root it and play around with it. I tried to unlock the bootloader for a while on this phone but I just can't. Every guide I tried didn't work. From mfastboot to MTKClient.
mfastboot just gave "unknown command" when trying to get unlock data, and MTKClient couldn't detect a partition or something when trying to wipe.
Then I tried searching my serial number: ZW2224XFWW, but that gave no results. Not on Google nor on here. Can anybody help. I'm very new to the rooting scene.
EDIT: I have a Moto C Plus with 1GB RAM and 16GB internal storage
MTKClient works, download the live .iso file from https://github.com/bkerler/mtkclient
Boot from it, open a console and type:
pip3 install -r requirements.txt
First just follow the readme to unlock the bootloader and after that root with latest magisk. I just tested all that on a moto C, I don't have the exact model but it was the 8gb/1gb variant.
Something's going terribly wrong because now it hangs at 43.8% while flashing boot partition and i dont know why
(I'm scared...)
MarkPCExpert said:
Something's going terribly wrong because now it hangs at 43.8% while flashing boot partition and i dont know why
(I'm scared...)
Click to expand...
Click to collapse
After further investigation, this happens also at recovery and maybe also other partitions so now it is soft bricked
EDIT: it seems that the connection stops or something because after it fails flashing, i also cant do other operations. I NEED HELP!!!
EDIT 2: after trying the console instead of the gui, i discovered that it was never unlocked in the first place. It said "unknown seccfg partition header, aborting unlock"
You are going to know you have your bootloader unlocked if you see a white letters on black background message saying that the phone will boot in 5 seconds after turning it on. You can't flash anything with a locked bootlader.
THATS EXACTLY WHAT I'M GETTING!!! But still, i can't flash a single thing. and I dont know why. I tried to flash TWRP recovery to install a lineageos build but TWRP hangs at 88%. And the patched magisk thingy hung at 43.8%
Now the phone is kind of bricked.
EDIT: Maybe the hang is because i use USB 2 or the Live ISO on a not so good USB. I do use an upgraded Dell OptiPlex 3010 as my main machine. Or the hang is bcuz it failed to flash.
Reflash the original firmware and try again. If you did a backup just flash the original boot.bin
Welp. I am screwed. I forgot i was running a live USB so the entire backup is gone.
And the userdata was also empty for the most part.
Try this: https://www.motorola.com/us/rescue-and-smart-assistant/p
If that doesn't work see if you can find a stock firmware and flash with flash tool. https://androidfilehost.com/?fid=889964283620774903
I already tried that one, but when i plug it in, it doesnt do anything and I DONT KNOW WHY!
also im on vacation
UPDATE: im back from vacation and no replies, great...
BUT, ive chosen a mostly aosp based rom for the phone.