Hello
While using the tablet, several errors were displayed continuously on the screen. I do not remember exactly what the text of the errors was.
The error was almost identical to the name of the system files that had a problem with them.
Clicking on each error quickly displayed the next error. As long as the system hangs up, I have to reset the tablet.
When the tablet was reset, the system did not go up and it was constantly reset. After 3 or 4 times the reset enters the Recovery Mode.
The following errors are displayed in the Recovery Mode:
Mount Cache (Invalid Argument)
I run the Wipe Cache Partition and the problem did not fix.
I did Factory Reset, but it was not successful.
I installed the Phone Flash Tool and used the following rom:
http://gsm-firmware.com/index.php?a=downloads&b=file&id=20427
But when it comes to executing the "oem start_partitioning" command, it timeout. The device will reset and the error will be displayed below:
EFILINUX ERROR [start_boot_logic: 431] No valid target found. Fallbacking to MDS.
So i tried to follow the strategy written here:
https://forums.lenovo.com/t5/Lenovo...ollipop-5-0/m-p/2204562/highlight/true#M27284
I downloaded the IntelAndroid-FBRL-07-24-2015 program and I run Part 2 / T4.
I have downloaded the TWRP backup file but I do not know what should I install.
So if the solution outlined above is correct, help me do the rest. If I have to do something else, I'd be happy to guide me.
No one can help me?
Related
While booting into recovery and trying to flash a new radio on pa 4.5 I ran into an error message in recovery that said E:Unable to mount '/cache'.
I tried to flash various different ROMs and even a different recovery but I still ended up getting the same message that it was unable to mount cache. I tried to manually mount cache in TWRP but it wouldn't let me, finally I tried a factory reset but that failed as well with the same error message.
Next I tried to go into fastboot and flash a new recovery, but I got an error message saying "FAILED <remote flash write failure>". I then tried to format cache through fastboot but that failed as well.
Lastly I tried LGNPST in order to return to stock but I got an error at 85% in LGNPST and still got it even though I tried on 3 different computers running both Windows 7 & 8.
I have contacted LG and they told me to mail the phone in for repairs, is that my only option now, or is there an other way to fix this and not have to pay LG to do it?
Thanks in advance to anyone that can help me sort this out.
Same problem here
Same situation here any solution plz help me
Hello to everyone.
I have phone LG g pro 2 D838 made in Korea, that has strange symptoms. When it boots, appear screen with keyboard and input box with text ''Enter PIN/password to decrypt 30/30 attempts remaining". After I entered some code, it shows "29/30 attempts remaining, and no matter how many times wrong code is entered, still remains 29/30. First of all I did factory reset., but nothing happened. Download mode working, and I try to flash latest stock rom 10f, but nothing happened. Then I try stock roms 10a, 10b and 10d, but still nothing. Next to the download mode, I have a recovery mode, in which there is no menu. In this mode, it is possible to access phone with ADB, but everything is read only, and system is not mounted. I can list folder contents, but I can't push or pull, and when i try to use shell, I get a message " -exec '/system/bin/sh' failed: No such file or directory", because system partition is not mounted. ADB Remount generate error " remount failed: Success ". I forgot to mention that every time when i try to flash stock rom, in box on phone display was written, in red letters, 'ROOTED'. I guess that unroot is not succeeded . Also suppose that possible solution is to flash some custom rom with recovery, but i can do that only if I have it in KDZ format. Does anyone know how to make a custom rom in KDZ format, or someone already has it? Does anyone know some other solution? Does anyone know how to bypass CryptKeeper.java?
Hi,
I have a Pioneer XDP-100R (hi-res music player) running android 5.1. I tried to root with SuperSU. At the end it asked to reboot my device. Now it's stuck on the android boot logo.
I can access the recovery menu (next track + power). A message is displayed: "E:Can't open /dev/block/platform/msm_sdcc.1/by_name/misc (permission denied)".
If I choose Wipe Data/factory reset, I get:
-- Wiping data...
Formatting /data...
Formatting /cache...
Data wipe complete.
"E:Can't open /dev/block/platform/msm_sdcc.1/by_name/misc (permission denied)".
I get pretty much the same when I try to "wipe cache partition".
None of the two actually make a difference.
Previous track + power is supposed to get me to the fastboot menu but it's stuck on the linux logo.
I had made a backup with adb beforehands but I can't restore it. adb won't see my device unless I select the option "apply updates from adb", but in that case, the only command it accepts is adb sideload.
I have not installed a custom recovery as my device is too rare. I never managed to find a stock rom or custom rom for my device so I can't even flash another one.
Has anyone any clue?
-- edit
I couldn't find any solution anywhere. I had to return it...
Thanks heaps
You could have some useful informations on forums or the page http :// xdp-100r.tk
I still have the device running if anybody needs files or tips.
theofruitrouge said:
You could have some useful informations on forums or the page http :// xdp-100r.tk
I still have the device running if anybody needs files or tips.
Click to expand...
Click to collapse
i have one hang logo. do you have file unbrick
mitsumi72 said:
i have one hang logo. do you have file unbrick
Click to expand...
Click to collapse
What exactly do you need ?
i need file system read from qfil. do you have telegram acc ?
Hi guys. After several attempts to unbrick my stratos 2 I now suspect 2 filesystem is corrupted for good because nothing works and I'm still stuck at the logo screen. Anyways, as a last resort, I decided to seek the opinion and knowledge from people who have more experience.
I tried the simpler methods trying to access the bootloader through adb but the command 'adb shell reboot bootloader' didn't work because there was no '/system/bin/sh'. I think it tells something about the filesystem, maybe. I even ran 'adb ls /system/bin' but there's nothing there.
After that I found a method to enter fastboot using the device buttons and etc. Before that I also unlocked the bootloader. 'fastboot getvar all' shows 'unlocked: yes'.
Than I tried the following:
First I tried the method described in this post:
https://forum.xda-developers.com/t/...e-installer-2-3-13-0-amazfit-stratos.3764636/
Everything worked during the process, but after boot the device I'm still stuck at the logo screen.
After that I tried the method describes in this post (deep flash):
https://forum.xda-developers.com/t/...-stratos-3-verge-deep-flash-tutorial.3908237/
Again, the process ran smoothly, the images where written but again, after rebooting, still stuck at logo screen.
After both procedures I executed 'adb shell' but still getting a message telling me there's no /system/bin/sh. Looks like nothing happened after the procedures.
So I don't know what else I can do or even if there is something else to do.
Any thoughts?
UPDATE:
I almost got it to work after trying method 1 another time. I passed the logo screen, the initialization process even got to the end and I was able to pair with the smartphone, but it was VERY slow, with several little hangs during the process. Some error occurred too that caused the device to reboot.
After that it was still too slow and I rebooted again. Guess what: stuck in logo screen again. So it's pretty clear to me that this is a storage corruption, but I still want a second opinion.
iranmarcius said:
Hi guys. After several attempts to unbrick my stratos 2 I now suspect 2 filesystem is corrupted for good because nothing works and I'm still stuck at the logo screen. Anyways, as a last resort, I decided to seek the opinion and knowledge from people who have more experience.
I tried the simpler methods trying to access the bootloader through adb but the command 'adb shell reboot bootloader' didn't work because there was no '/system/bin/sh'. I think it tells something about the filesystem, maybe. I even ran 'adb ls /system/bin' but there's nothing there.
After that I found a method to enter fastboot using the device buttons and etc. Before that I also unlocked the bootloader. 'fastboot getvar all' shows 'unlocked: yes'.
Than I tried the following:
First I tried the method described in this post:
https://forum.xda-developers.com/t/...e-installer-2-3-13-0-amazfit-stratos.3764636/
Everything worked during the process, but after boot the device I'm still stuck at the logo screen.
After that I tried the method describes in this post (deep flash):
https://forum.xda-developers.com/t/...-stratos-3-verge-deep-flash-tutorial.3908237/
Again, the process ran smoothly, the images where written but again, after rebooting, still stuck at logo screen.
After both procedures I executed 'adb shell' but still getting a message telling me there's no /system/bin/sh. Looks like nothing happened after the procedures.
So I don't know what else I can do or even if there is something else to do.
Any thoughts?
UPDATE:
I almost got it to work after trying method 1 another time. I passed the logo screen, the initialization process even got to the end and I was able to pair with the smartphone, but it was VERY slow, with several little hangs during the process. Some error occurred too that caused the device to reboot.
After that it was still too slow and I rebooted again. Guess what: stuck in logo screen again. So it's pretty clear to me that this is a storage corruption, but I still want a second opinion.
Click to expand...
Click to collapse
If you get the watch booting and passing the initial A logo, reboot into fastboot before the system crashes and do a factory reset in fastboot
fastboot erase cache
fastboot erase data
And let's see if that fixes something.
Hi, thanks for the answer.
I already did that. I even erased system partition, but unfortunately it didn't work either.
Giving more information, after erasing the partitions I did a test: I rebooted the device (right after fastboot erase) and executed 'adb ls /' to see if something changed, but apparently not. There was still several directories and files, like nothing was erased.
Should I try to format these partitions maybe? Either way, I'm still stuck in the A logo. At least I didn't kill the device completely (yet).
Saratoga79 said:
If you get the watch booting and passing the initial A logo, reboot into fastboot before the system crashes and do a factory reset in fastboot
fastboot erase cache
fastboot erase data
And let's see if that fixes something.
Click to expand...
Click to collapse
UPDATE:
I erased cache and data partitions again and rebooted the device. After that I was able to get to the QR code screen. I even was able to enter 'adb shell' and execute a 'top' command to see what was happening during the initialization process.
But after it got to the QR code screen the device rebooted by itself and I got stuck in the A screen again.
So I erase the partitions one more time, reboot the device but there was no way I get passed the A logo screen.
When I execute 'adb ls /system/' there are no files.
iranmarcius said:
Hi, thanks for the answer.
I already did that. I even erased system partition, but unfortunately it didn't work either.
Giving more information, after erasing the partitions I did a test: I rebooted the device (right after fastboot erase) and executed 'adb ls /' to see if something changed, but apparently not. There was still several directories and files, like nothing was erased.
Should I try to format these partitions maybe? Either way, I'm still stuck in the A logo. At least I didn't kill the device completely (yet).
Click to expand...
Click to collapse
After several attempts, erasing data and cache partitions the device is working again.
Looks like after erasing partitions and rebooting it was necessary to wait a long time until all process in the device did their jobs, including app optimization, with can take several minutes, but sometimes with no feedback on the screen.
I'm still trying to figure out a way to check partitions for erros, maybe using e2fsck, but when i try to do it, even using -b option, I got a message that I must have RW access to the partition or be root.
Anyone can help me on that?
Continuing the saga, I rebooted the device using a rooted image and from that I was able to check the partitions using e2fsck -n. The results:
e2fsck 1.42.9 (28-Dec-2013)
Warning! /dev/block/platform/jzmmc_v1.2.0/by-name/data is in use.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (545541, counted=616333).
Fix? no
Free inodes count wrong (172802, counted=172856).
Fix? no
/dev/block/platform/jzmmc_v1.2.0/by-name/data: 1086/173888 files (6.3% non-contiguous), 148731/694272 blocks
So /data partition has some errors but I couldn't fix it because it's reported busy. Maybe some processes are using it, but I don't know which ones. The best that occurred me is that if I kill those processes I can fix the partition errors. don't know if this is the correct way to do it.
iranmarcius said:
After several attempts, erasing data and cache partitions the device is working again.
Looks like after erasing partitions and rebooting it was necessary to wait a long time until all process in the device did their jobs, including app optimization, with can take several minutes, but sometimes with no feedback on the screen.
I'm still trying to figure out a way to check partitions for erros, maybe using e2fsck, but when i try to do it, even using -b option, I got a message that I must have RW access to the partition or be root.
Anyone can help me on that?
Click to expand...
Click to collapse
Hi all,
Well, operator error is definitely at fault here... I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and obviously ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Hi, would anyone like to weigh in on this issue?