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. 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?
{
"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"
}
Thanks in advance
From what it looks like, you've encrypted your phone. That explains the password on startup and the unmounted system.
If you don't know your encryption password, you have a bit of a problem on your hands.
From what I know, there's no way to hack into or change your phone when it's encrypted.
Turtle_Cookies said:
From what it looks like, you've encrypted your phone. That explains the password on startup and the unmounted system.
If you don't know your encryption password, you have a bit of a problem on your hands.
From what I know, there's no way to hack into or change your phone when it's encrypted.
Click to expand...
Click to collapse
In first, thank you on reply ,Turtle_Cookies.
If the phone is encrypted, it should be possible to reset it to factory settings. The user data is encrypted, so it would delete them and set to the default settings, and that should recover the phone. On the other hand, I can access to certain directories by ADB (like etc,sys), but can't change it. Am I right?
Same Issue
Did you found solution to this?
Related
About the phone:
1. I dont know the exact phone model, but it is Cloudfone Ice plus. There is a phone called Cloudefone Ice (Huwawei u8500) but i dont know if mine has another name.
2. It looks like this,
h++p://cdn2.sulitstatic.com/images/2012/0926/222830332_22162996997ba02ceb979675b8093b33516b3b725d6504ce0.jpg
3. Adroid version 2.2.1
4. Detected as "Globe Phone" in Google Play Market. *Globe is a carrier in our country.
The Problem:
When I turn it on, the android logo appears, and stays like that forever.
Cause:
After I tried to install a custom ROM using update.zip in recovery mode, the process got aborted in the last part of the installation.
5. I'm not sure if it's fully rooted, I have superuser but when I tried Root Checker before, it's not.
Other info,
I already tried to boot in recovery mode(it's the only mode that I get into now), I wiped data and cache/factory reset.(still stuck on boot screen)
I tried to install other Roms(update.zip), but all gets aborted in the beginning
I tried to download an update.app file in a dload folder in the root of sd card(firmware for huwawei)- I can't go to update firmware.I can only go to recovery mode.
I tried adb, I can use adb devices, it shows MT(serial number)
adb shell shows adb shell exec '/system/bin/sh' failed: no such file or directory exists
superboot cant detect the device.
I boot the device using power button+volume up,
when I use power+volume down, android logo appears and "Factory Mode" in the lower left (then It stays there forever, whatever button i press)
These are the infos that I can give, please help, I'm looking for fixes since yesterday from google and forums but no luck, nothing works so I decided to post my own.
image
{
"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"
}
Click to expand...
Click to collapse
no spaces in link
Hi!
I picked up a Mate 8 from a local service provider and would love to flash a new ROM to get rid of the ugly stock one, but I am stuck when trying to flash anything from TWRP.
The phone boots fine, I unlocked the bootloader, and has TWRP Mate 8 version...I can't locate any files from the internal storage though. I understand this is due to the system being encrypted. I cant seem to get around that though. I tried the format data option, hit yes, then go back but that obviously has deleted what I had stored (the SU zip). I can't mount the SD either afterwards, to load it in recovery.
I tried using the Italian knife tool, and used the Root option, and option 3, but get an error: error: cannot load '.\rec\boot.img
I am not a pro on this so it might be something farely stupid. I would love if anyone could help me with 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"
}
--------------------------------
Edit:
I was able to solve myself. It was a rookie mistake. Perhaps the internal storage is encrypted, however I was able to flash SU using TWRP by inserting an external SD, which I had not done before. I was able to view contents from that location and did not need to use the Italian knife tool.
Hi there I am using iBall KitKat mobile is rooted but i am unable delete system apps and can't use link2sd showing error mount structure needs cleaning can anyone help
aceslivelong said:
Hi there I am using iBall KitKat mobile is rooted but i am unable delete system apps and can't use link2sd showing error mount structure needs cleaning can anyone help
Click to expand...
Click to collapse
Are you using SuperSU ??
To delete system apps, download system app uninstaller from play store and grand it superuser permission.
Hello guys,
I'm new here, I've read a lot about your different topics and I'm admirative for some level god members with their answers :good: :laugh:
Indeed I'm a dev, but for websites so it's a bit different with phones for me, and I will try to explain as detailed as I can.
I have a samsung SM G965F, bought in Poland (I work here for the moment); And indeed tried to root it for private purposes.
I followed a tutorial; I was on Pie 9 (****tiest ever update for me); from there OEM in DEV tools was activated, and the TWRP was installed.
the phone wasn't root, but I had the TWRP options (when push Volume up+bixby+lock) so thought I'm on the good way, but only after, and there is my mistake, I understood by reading something that I should make faster an operation when enabled the OEM (before it start to delete all my infos) that I should switch to recovery mode (or installation) and if not there was a story with 7 days to wait.
So the phone was just reseted with only memory card datas not deleted, and the phone was working, just the OEM always disabled, and when you select to enable it it says "ok we reboot the phone you will loose all your files etcc..." and anyway after many attempts, it says always the same after the reboots, and never is enabled after. So I tried to install a new rom, and then I thought I had a problem, in the installation it was written "Secure Check Fail : PIT".
So I tried to found the right rom, with the number "6" inside as per this screen :
{
"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"
}
Then the Secure Check Fail : PIT dissapeared and now its just Fail in Odin.
Also, I tried to reboot normally but it says that there was an error and I need to reinstall with smart view or smart touch, I don't really remember, so I just reinstalled the first TWRP and now the screen of my phone is looping on Samsung, and rebooting.
I'm lost, I spent from 3pm to 4 am yesterday in the internet to found a solution, so my final option is write to ask your help guys.
Hope you can help me, thank you in advance
PS: Sorry for the big picture, there is no acceptance unfortunately for resizing codes, or maybe I just still don't have access to this option cuz I have less than 10 messages, if need delete it or explain me if you need pictures, I did it 10 min ago, even if there is not a lot to do because i'm limited with my phone now
Hello!
How to unmount an old android 4.4.2 data partition?
Update: phone model if that makes any difference is Sony Xperia E1 dual
Not sure where to put this question, so I guess a general??
I have no knowledge of linux, android. But I got a programming background on windows systems and web.
I want to unmount an old android 4.4.2 data partition to run file system check because after deleting some files in data directory I am unable to write anything.
Could anyone please help me to get an idea how to do this? I searched the threads but they are more about flashing, TWRP and so on. Would not a simple file system check be enough in this case? As I noticed possibly it might be some sort of inode error? So checkdisk or something should fix it, shouldn't it?
I tried clearing the cache, it helped, but after few hours could not write anything again.
Now even the cache cleaning does not help.
{
"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"
}
It's always a good idea to set filepointer to begin of filesystem if you mount / unmount a partition: doing so you'll never run into error "Device or resource busy"
xXx yYy said:
It's always a good idea to set filepointer to begin of filesystem if you mount / unmount a partition: doing so you'll never run into error "Device or resource busy"
Click to expand...
Click to collapse
thanks for the tip!
However, I am a noob in linux/android, and the mount was done by android or KINGO rooter. So should I something like restart in recovery mode? Update:
Code:
adb reboot recovery
-> just rebooted to the regular interface
Update: phone is Sony Xperia E1 dual
I thought fixing a disk would be something like very basic task, like one liner or one parameter I did not add...
The mounting is just a way how I think I might solve the problem. That might be absolutely wrong way, not sure, now trying to move in the darkness by intuition only ...
Main problem: can not write anything with free space avaliable. Appeared since I deleted some files from /data using adb and rm command.
I also tried all the devices, but none of them was checked with two types of error:
Hi smart kind pilgrims and jedis,
this antique was working the other day, but if the password was ever known it's long forgotten
(Started saying enter Android password, so trying to reset)
Have read others have had success elsewhere, when googling product name for firmware nothing crops up. Not sure if it's a pixel (dual boot, currently no win login options available)
P806 mentioned on back, on access recovery the product name is
inet_alc5651_32
& Only the serial is known
When selecting recovery mode, I got the droid on his back with front panel open and
When I hold all buttons to power on (vol up+down) I get fastboot waiting for command- do you plug in usb before booting then control from pc?
or Is this another brick for the landfill?
Thanks for any suggestions or pointers!
Yes, Android may ask for a password at boot for security reasons. This is to ensure that only authorized users can access the device and its data. If you have set up a password or PIN for your device, you will be prompted to enter it when you turn on your device. If you don't want to enter a password every time you boot your device, you can disable this feature in your device's settings app
{
"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"
}
If you can't access this app then to remove the password you have to perform a Factory Reset - what in turn will wipe all user-data and all user-apps ever installed, too.
BTW:
A Factory Reset never produces an error like "no valid installer medium found".
The error message "E: No valid installer medium found" typically indicates that the Android Recovery system is unable to find a valid installation medium, such as a ROM or firmware file, to install on your device. This could be due to a number of reasons, such as a corrupted or incomplete installation file, a faulty SD card or USB drive, or an issue with the recovery system itself.