Hi. Looking for help with my strange situation. Namely, I made some photos/videos on vacations using Z5C and while trying to transfer all my data to PC (99%) system just hanged and after that, forgot most of the data, so only 33% left on internal memory. I recovered this amonut, but trying to "undelete" those which have been lost got real dragons. No recovery software couldn't do that. One said, I need to root my system to do it as I did such operations on PC. So I tried and failed - now only recovery mode works (sometimes) and the Android is not waking any more.
Please, give me a hint what way is better to recover my data. Communication with PC is now not available - only in fastboot mode. No recovery programs see my phone. Recovery mode shows no deleted (lost) files, but the whole system is visible. How to connect/recover that data? Is it possible to do it via fastboot? I didn't load any new files and didn't make any modifications to not overwrite potentially hidden files on the storage.
The system not working because I fastbooted something accidently (wrong kerner) - this maybe the reason. Recovery didn't work as well, but it sometimes starts.
PyeR said:
Hi. Looking for help with my strange situation. Namely, I made some photos/videos on vacations using Z5C and while trying to transfer all my data to PC (99%) system just hanged and after that, forgot most of the data, so only 33% left on internal memory. I recovered this amonut, but trying to "undelete" those which have been lost got real dragons. No recovery software couldn't do that. One said, I need to root my system to do it as I did such operations on PC. So I tried and failed - now only recovery mode works (sometimes) and the Android is not waking any more.
Please, give me a hint what way is better to recover my data. Communication with PC is now not available - only in fastboot mode. No recovery programs see my phone. Recovery mode shows no deleted (lost) files, but the whole system is visible. How to connect/recover that data? Is it possible to do it via fastboot? I didn't load any new files and didn't make any modifications to not overwrite potentially hidden files on the storage.
The system not working because I fastbooted something accidently (wrong kerner) - this maybe the reason. Recovery didn't work as well, but it sometimes starts.
Click to expand...
Click to collapse
Hello and good morning, @PyeR
Welcome to XDA. I hope you'll always find and get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Related
Hi there,
I am stuck in a unique situation where my Android phone is acting strangely. It appears that all apps lost internet and/or SD card storage permissions. From the phone no app can read/write/access storage or internet. I can still use adb to look at the SD card (both internal and external) on the phone, I can install a package using adb, I can pull files using adb, but I can't write or delete any files using adb.
I wonder if there is a way to regain those permissions by using adb? Sending some package and execute some commands to force Android to reload the platform.xml? Does it have anything to do with KNOX on the device somehow getting into the way? When I put the phone in Download Mode I still see KNOX not being tripped (0x0).
The Android version is 4.4.2.
P.S. Forgive me if this post seems to be out of place. I was posting similar questions in the specific phone forum but I got little success there. So I decided to post the question here in the generic Android area, hopefully it is the right place where there are many more developers who have experience with Android in general can help.
Thanks
After installing a Magisk module my OS just died, or rather, everything is black but unrelated things such as the widget I have on my lockscreen and the power menu are still visible, I still see me taking screenshots too. But the rest of the OS is black and doesnt seem to respond to gestures. Im able to boot into TWRP too. getting to the point, I want to get my stuff off of it and putting it into my new phone but Im unsure how to proceed. TWRP to PC backup doesnt help cuz, well, yknow. Neither does just dumping the files over a cable, although that seems to be Windows´ fault. Any ideas?
_Unknown? said:
After installing a Magisk module my OS just died, or rather, everything is black but unrelated things such as the widget I have on my lockscreen and the power menu are still visible, I still see me taking screenshots too. But the rest of the OS is black and doesnt seem to respond to gestures. Im able to boot into TWRP too. getting to the point, I want to get my stuff off of it and putting it into my new phone but Im unsure how to proceed. TWRP to PC backup doesnt help cuz, well, yknow. Neither does just dumping the files over a cable, although that seems to be Windows´ fault. Any ideas?
Click to expand...
Click to collapse
@_Unknown?
Please read the guidances that are stuck on top of every forum prior to your next posting like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
Oswald Boelcke said:
@_Unknown?
Please read the guidances that are stuck on top of every forum prior to your next posting like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
Click to expand...
Click to collapse
oh Im so sorry, thanks for doing that!
Serious hackers ensure that the door to Android OS always is open before they start hacking Android OS.
This is done by
either
enabling USB Debugging ( AKA ADB ) on Android device - take note that ADB always gets started by device's bootloader when device gets powered on
or
installing LAN Drive ( a SMB server & client ) on Android device what allows one turn the Android device into a Windows PC's network drive.
Both allows one to dump / transfer files located on Android device to Windows PC.
If Android device supports OTG then you also can access Android's user-data when connected by an USB-C-cable.
Hey there!
I wanted to install chroot on my rooted phone [24gb available space + sdcard with 26gb available space]. It didn't work using the "Download latest" button so I downloaded the kalifs-full.tar.gz and put it in internal storage myself, which was working fine. When I got to select the metapackages I selected all of them because I wanted to install everything. After that, it just listed all the metapackages I selected in the Status menu, then it just kinda stops. I rebooted my phone but it says that chroot isn't installed. I also tried waiting for half an hour but nothing really changed. I have tried re-doing it cuppa times but again, nothing changed. The picture below shows the state where it has left off at. I installed the Kali NetHunter module using magisk v24.1
-Greetings
okok1 said:
Hey there!
I wanted to install chroot on my rooted phone [24gb available space + sdcard with 26gb available space]. It didn't work using the "Download latest" button so I downloaded the kalifs-full.tar.gz and put it in internal storage myself, which was working fine. When I got to select the metapackages I selected all of them because I wanted to install everything. After that, it just listed all the metapackages I selected in the Status menu, then it just kinda stops. I rebooted my phone but it says that chroot isn't installed. I also tried waiting for half an hour but nothing really changed. I have tried re-doing it cuppa times but again, nothing changed. The picture below shows the state where it has left off at. I installed the Kali NetHunter module using magisk v24.1
-Greetings
Click to expand...
Click to collapse
@okok1
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Android Q&A. Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
I just found out myself.
1. Installing everything is about 55-60gb which my phone has not enough space for
2. The download I used didn't work, the official one from github worked
I've seen the Recovery System class in Android SDK or API (however it is called) and I thought about modifying its System Partition without touching the Bootloader to unlock or flashing the TWRP Image. I did not test it out yet on my device (my device is Huawei Honor 9X), but I think that it is a cool idea to modify its content on the System Partition.
What I already know is that it is required to have a so-called signed OTA package, but I am unsure if this requires the system OTA certificates from /system/etc/security/otacerts.zip or the self-signed package. Since my device settings do not support installing packages from the storage (it is because of the dload folder), I would need to have a hand coded app (what I really like) to install these packages myself.
Another problem could arise: the Bootloader may check for the files, which, for example, an app that came from nowhere or a patched libc.so file via its checks (since my phone does not have A/B partitioning, I think it does that). From what I already read somewhere is that any Recovery trusts any package that is signed, but I didn't trust that and searched the Internet, where I literally didn't find anything useful to that. I hit another dead end, but that didn't stop me from doing so.
Since my computer already dual-boots Ubuntu and Windows 11, I could mount any system.img file and check file-per-file if it may modify the system's behavior, but I am anxious about that because I already bricked several phones in the past that I don't want to watch another one getting either soft-bricked or hard-bricked.
So to come into conclusion: is it possible to modify any file on the System without unlocking the bootloader or flashing a custom recovery, or is this required to do so before modifying on the System partition? I am not ready to flash Magisk onto my phone nor flash the TWRP because there are no official image(s) for my device.
BeChris100 said:
I've seen the Recovery System class in Android SDK or API (however it is called) and I thought about modifying its System Partition without touching the Bootloader to unlock or flashing the TWRP Image. I did not test it out yet on my device (my device is Huawei Honor 9X), but I think that it is a cool idea to modify its content on the System Partition.
What I already know is that it is required to have a so-called signed OTA package, but I am unsure if this requires the system OTA certificates from /system/etc/security/otacerts.zip or the self-signed package. Since my device settings do not support installing packages from the storage (it is because of the dload folder), I would need to have a hand coded app (what I really like) to install these packages myself.
Another problem could arise: the Bootloader may check for the files, which, for example, an app that came from nowhere or a patched libc.so file via its checks (since my phone does not have A/B partitioning, I think it does that). From what I already read somewhere is that any Recovery trusts any package that is signed, but I didn't trust that and searched the Internet, where I literally didn't find anything useful to that. I hit another dead end, but that didn't stop me from doing so.
Since my computer already dual-boots Ubuntu and Windows 11, I could mount any system.img file and check file-per-file if it may modify the system's behavior, but I am anxious about that because I already bricked several phones in the past that I don't want to watch another one getting either soft-bricked or hard-bricked.
So to come into conclusion: is it possible to modify any file on the System without unlocking the bootloader or flashing a custom recovery, or is this required to do so before modifying on the System partition? I am not ready to flash Magisk onto my phone nor flash the TWRP because there are no official image(s) for my device.
Click to expand...
Click to collapse
@BeChris100
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Android Q&A.
Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
I have a HTC Desire 650 running android 6 and I am trying to root it and also keep the original recovery.
I have found this thread: https://forum.xda-developers.com/t/root-htc-desire-650.3713325/ and apparently someone built a twrp for it. Doesn't that need a root in the first place to extract the kernel source?
Anyway, are there any apps or known vulnerabilities that would allow me to root the phone or at least extract the recovery image?
The problem is that I couldn't find any stock rom images or anything else for this phone. I was only able to unlock the bootloader.
Dan Ti said:
I have a HTC Desire 650 running android 6 and I am trying to root it and also keep the original recovery.
I have found this thread: https://forum.xda-developers.com/t/root-htc-desire-650.3713325/ and apparently someone built a twrp for it. Doesn't that need a root in the first place to extract the kernel source?
Anyway, are there any apps or known vulnerabilities that would allow me to root the phone or at least extract the recovery image?
The problem is that I couldn't find any stock rom images or anything else for this phone. I was only able to unlock the bootloader.
Click to expand...
Click to collapse
Hello and good morning, @Dan Ti
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Only to clarify things:
1. Recovery is a small and independent operating system that is set up in its own partition in many Android smartphones and tablets.
The "Recovery mode" is useful for you if you want to access the Android system of your smartphone or tablet beyond the conventional settings.
Since the recovery system is on its own partition next to the actual operating system and is thus intact even after a virus attack, it is often used for system repair.
2. Android's bootloader is a program that is responsible forbooting Android device.
3. Rooting is how you get complete access to everything in the Android OS, and those elevated permissions allow you to change it all. Root, at least the way I'm understanding it, is the superuser.
When you root your Android, you're simply adding a standard Linux function that was removed by OEM. A small file called su is placed in the system and given permissions so that another user can run it. It stands for Switch User, and if you run the file without any other parameters, it switches your credentials and permissions from a normal user to that of the superuser. You are then in complete control and can add anything, remove anything, and access functions on your phone or tablet that you couldn't reach before. This is pretty important and something you should think about before you begin.
To root Android OS it's neither necessary to unlock devices bootloader nor to install TWRP: this is an obviously not eradicable old nurse's tale!