Hi,
A couple of week ago my rooted xperia x compact with lineage os turned off for low battery, and after rebooting the sim wasn't recognized any more. This already happened once, but I managed to resolve with *#*#4636#*#* code, setting the preferred network type to GSM only and rebooting.
This time however this solution didn't work and since then I've tried to do everithing I could, including flashing stock rom with flashtool, flashing again twrp and lineage os from scratch and lastly I tried to resolve erasing modemst1 & 2 (following this https://nerdschalk.com/fix-empty-im...-from-bootloader-mode-using-fastboot-commands), using fastboot, adb and twrp terminal.
Fastboot always says permission denied, I don't know why, while both adb and twrp after the command dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 say
dd: /dev/block/bootdevice/by-name/modemst1: No space left on device
3073+0 records in
3072+0 records out
1572864 bytes transferred in 0.032 secs (49152000 bytes/sec)
without resolving the issue. As little as i know about this things this should be a command that delete this files, so I don't understand this output and I don't really know what to do anymore.
I really like this phone and I would really like to avoid to change it since it seems to be a solvable problem.
Thx in advance for your help (as far as I can see it seems to be an analogous problem as this one https://forum.xda-developers.com/t/...hereafter-cell-radio-permanently-off.3875722/)
Related
So I think I've bricked my G2 while updating with the latest update. Was rooted on stock ROM. Tried to install TWRP recovery but could never get into so, didn't think I had it installed. Installed VooDoo and took the update.
Well, my phone is stuck in a black screen. The LG logo comes on but I can't go anywhere from here. Can go into factory reset but it keeps coming back to the black screen. I've read all the forums and tried flash tool, fastboot, adb.... but no luck. My comp (Win 8) won't recognize the device and I get bunch of Local disks when I plug into USB.
I'm at a loss, total loss. I would really appreciate any help that I can get. Just want to get in hard drive and save some photos if I can't save the phone. Thanks!
try to install the drivers in a windows 7 pc and do it again!!
fixing the black screen boot
google and install koush's universal adb driver.
once you have adb..shell into device
adb shell
then
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
you should be able to boot your phone now
as far as your recovery and root i dont know, this isnt my solution i dont know exactly who found it, but i watched autoprime talk a user thru this and booting up after in the #lg-g2 irc channel and thought i would put it here to help some folks.
any thanks or beer money should be directed to him or whomever he points to lol
good luck
I have the lg g2 from at&t and yesterday i went from cm10.2 back to the stock backup i had for the g2 and received the OTA update. I didnt think much of it and downloaded it, now i am stuck on the endless loop ending in the TWRP screen, I have about 3 back ups but every time i try to restore it it just ends up back in the recovery screen. I've tried to do what i've found on the forum as far as using terminal command from twrp , but all i get is a list of folders, i tried using adb but because of the phone being in it's current state the drivers wont install correctly on the computer, so it doesnt register. Pretty stuck right now and dont know what else to try or do , any help will be appreciated. thank you
Look this
forum.xda-developers.com/showthread.php?t=2451696
I cant do that method because option 1 , adb cant communicate with my phone due to the drivers not being able to install correctly and i tried option 2 but i dont see where to enter the command in terminal command , all i see is a directory of folders
In Twrp,go in Terminal and Press Select
Write this line:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
And go - finish
Here again accurately described
dd[space]if=/dev/zero[space]of=/dev/block/platform/msm_sdcc.1/by-name/fota
[Space] stands for space bar
I can't thank you enough for taking the time to help me out with this, thank you and forgive my ignorance with the whole terminal thing i am still new at all of this .
The LG G2 is rooted then I got an update on my phone that asked me if I want to do it and then I accidently did that.
What happend I'm stuck in Teamwin recovery with no rom and no backup and nothing left on the phone everything is erased.
When I try to do a the button thing with volume down and power button I get in to some reset but that won't work as well.
I hope someone have had the same problem or have a solution for it. Please guys help me if no one can help me with that I have to ask you if it's possible to send it to a certified LG workshop and get it fixed thru the warranty.
JoKeRWiLD said:
The LG G2 is rooted then I got an update on my phone that asked me if I want to do it and then I accidently did that.
What happend I'm stuck in Teamwin recovery with no rom and no backup and nothing left on the phone everything is erased.
When I try to do a the button thing with volume down and power button I get in to some reset but that won't work as well.
I hope someone have had the same problem or have a solution for it. Please guys help me if no one can help me with that I have to ask you if it's possible to send it to a certified LG workshop and get it fixed thru the warranty.
Click to expand...
Click to collapse
ok if you have adb access on the pc then try the following commands(if you don't know what this is then skip this part)-
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
if you have twrp 2.6.3.3 or later than go to the terminal app inside twrp and type the following-
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
if that one doesn't work you can aso try-
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
and if the above does not work then you are going to have to flash back to stock using the following guide http://forum.xda-developers.com/showthread.php?t=2432476
If you can get in to TWRP, you should be able to plug in and send a rom to it over USB (I think TWRP has this ability, but I have not used it). Alternatively you could use ADB to push some files to it also. Anywhos, once you have a rom it sounds like you should be able to flash away and be good to go unless I missed something in your OP
I've tried everything and it won´t work. I need to know how to send a rom in to a phone thru usb, but I have another problem the computer recognize a product "g2" but when I plugg it in I can't find it, the drivers that I installed can't find it as well. Please somebody help
Hi guys,
the phone is from my sister and it got hit by some tool from her (ex-) husband. The screen has been hit on the left side with destroying the battery too. So I have NO display, NO Touch. Latest Android (I think 7.0.1) is installed. The phone has never been tampered with and all is stock.
Because of all the photos from kids and cat she asked me to rescue the photos from it - and then the fun began.
Of course I bought a used A3 2016, but the display showed just static crap. A new display spare part did the same ...
The mainboard seems to be working ok - I am with Apple Phones only because my employer tells me to
It is for almost a year now, and I cant get to the photos.
So far I've read that I should root the device so I could access the filesystem to just simply save the jpgs. Of course no USB-debugging enabled the phone is locked with a patternlock ...
Problems so far: I cant get the phone into Download-Mode - it seems to bee booting through and after 30-40 secs my PC recognizes the device as it should, but the file folder is empty.
I can get into recovey-mode, and there I'm stuck. I can use "get update by adb" and adb shows me, that the phone is in sideload-mode but any upload ends with an error at 0% ...
Total factory reset could be an option, because I think I can recover most of the files from internal storage, right?
So I decided to ask the PROs and ask for help and/or ideas here ...
Thanks for reading !
How would you recover the files if you factory-reset the device? Are they not saved in standard locations? If yes, a factory reset will remove all normal user-files.
Are you able to get into an ADB shell from recovery mode? ("adb shell" command)
If you can get a shell, you could navigate to the directories and download ("adb pull <file>") the files to your PC.
I believe you could get a shell from TWRP. If you can flash the recovery with TWRP and boot into it directly via console (unfortunately I don't have a command handy), then you might be able to access the shell, too. (Take this with a grain of salt, but it's better to try it before doing a factory reset.)
Do you know if the storage has been encrypted? If so, then forget everything I wrote.
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!