Database Info

Bricked Jiayu G4T, Help Required

Hallo,
being new to this forum and also new to Android devices, please feel free to move my post into the correct section of the forum if I used the wrong one. The use of the search function is also not unknown to me, however I may not know all terms to be used (rookie) and english still is a foreign language for me.
Anyway, I have a serious problem with my brandnew Jiayu G4T phone and at least I need some help in sorting my thoughts and ideas after several days of browsing through the community.
What I know for sure:
Phone starts booting but stops on the third screen (1st: Jiayul ogo white, 2nd: Jiayu logo green falling in place, 3rd: Jiayu logo white fading).
I am able to boot into stock recovery and into factory mode (mostly chinese characters).
I have access to my phone by adb shell and can look into the directories.
The event occured after an overnight update with weird behavior of the phone (what happened is posted in the assumption section, it was still pretty early and I was clearly not fully awake.
I had the Xposed framework and XPrivacy installed and running. All other apps were pretty common.
In ADB my phone is listed as 0123456789ABCDEF (weird number)
What I do not know / Assumptions:
In /data I see plenty of files telling me that the data wipe from recovery was not successfull, the data belong to previously installed apps.
It seems that I was able to flash a new ROM, in system/app I do not see any of my previously installed apps. Superuser.apk is still present.
I also can access data however only after using su in shell.
I cannot delete the data using rm or wipe data being in [email protected] #, I have no idea why. Read only....
SP Flash tool told me that the flash of the new ROM was successful (red, pink, yellow progress bar followed by green circle). I think that is a good sign.
I also was able to apply ADB sideload for installing a new ROM and the phone told me I was successful. Not sure if this is true considering that my phone still is not booting.
After finding my phone in the morning mobile connections were both down, I think that an Android update was not successful and it might have happened that I restricted this very app with XPrivacy inadvertently.
The phone identifier seems to tell me that XPRivacy might still be active somewhere....
What I think about the next steps:
I think that getting rid of the old data might be the key for success, but I have no idea HOW....
Any thoughts from your side re highly appreciated,
Thomas

Tomcat117 said:
Hallo,
being new to this forum and also new to Android devices, please feel free to move my post into the correct section of the forum if I used the wrong one. The use of the search function is also not unknown to me, however I may not know all terms to be used (rookie) and english still is a foreign language for me.
Anyway, I have a serious problem with my brandnew Jiayu G4T phone and at least I need some help in sorting my thoughts and ideas after several days of browsing through the community.
What I know for sure:
Phone starts booting but stops on the third screen (1st: Jiayul ogo white, 2nd: Jiayu logo green falling in place, 3rd: Jiayu logo white fading).
I am able to boot into stock recovery and into factory mode (mostly chinese characters).
I have access to my phone by adb shell and can look into the directories.
The event occured after an overnight update with weird behavior of the phone (what happened is posted in the assumption section, it was still pretty early and I was clearly not fully awake.
I had the Xposed framework and XPrivacy installed and running. All other apps were pretty common.
In ADB my phone is listed as 0123456789ABCDEF (weird number)
What I do not know / Assumptions:
In /data I see plenty of files telling me that the data wipe from recovery was not successfull, the data belong to previously installed apps.
It seems that I was able to flash a new ROM, in system/app I do not see any of my previously installed apps. Superuser.apk is still present.
I also can access data however only after using su in shell.
I cannot delete the data using rm or wipe data being in [email protected] #, I have no idea why. Read only....
SP Flash tool told me that the flash of the new ROM was successful (red, pink, yellow progress bar followed by green circle). I think that is a good sign.
I also was able to apply ADB sideload for installing a new ROM and the phone told me I was successful. Not sure if this is true considering that my phone still is not booting.
After finding my phone in the morning mobile connections were both down, I think that an Android update was not successful and it might have happened that I restricted this very app with XPrivacy inadvertently.
The phone identifier seems to tell me that XPRivacy might still be active somewhere....
What I think about the next steps:
I think that getting rid of the old data might be the key for success, but I have no idea HOW....
Any thoughts from your side re highly appreciated,
Thomas
Click to expand...
Click to collapse
This is your solution right here (hopefully)
1) If you have not installed the drivers, download, unpack and install drivers http://uloz.to/xwWU1vKw/mtk6589-driver-zip.
2) Download and unpack Stock ROM http://www.ejiayu.com/en/News2-1-100.html.
3) Download and unpack FlashTools http://uloz.to/x6U5ZDKs/spflash3-1316-0-150-zip, and Click on Flash_tool.exe.
4) Click button "Scatter-loading" and select a the MT6589_Android_scatter_emmc.txt in ROM.
5) Turn off your phone and remove the battery!
6) Press F9 (or hit Download button) and connect your phone into the computer via USB data cable.
7) The process will start and a red progress bar will appear after color purple, yellow. And green circles display. Finish. You can now safely disconnect your phone and turn it on.

Egbert
jimmys01 said:
This is your solution right here (hopefully)
Click to expand...
Click to collapse
This actually is a thread I found very early and unfortunately it was not working.
Honestly I assume that Isomehow lost root: How does this sound in the view of my observations and assumptions?
Thomas

[Q] Only position independent executables (PIE) are supported

Hello forums, I've got an annoying problem I've stumbled into. I wanted to download and install KBOX2 onto my OPO for the sake of being able to play gblorb files, I download the OneBox Package Manager that should do that automatically by executing a script in Terminal Emulator and instantly an error pops up as seen in the title of the thread, the whole PIE thing. Now, after extensive googling it seemed like a very early problem that eventually either got patched, or it was exclusive to early nexus models and fixed but some zip.
I have found no info on PIE in Lollipop 5.0 or 5.1, or for my OPO, outside of one website having an article on how to run python in the terminal - it had a subsection devoted to bypassing PIE, which included renaming your original linker to linker.old and then substituting in a patched linker in /system/bin/ that would avoid the whole PIE thing. The next problem I have stumbled into is that even after unlocking my boot, installing TWRP and rooting the device after a lot of hassle with drivers:
Whenever I would mount my /system for the sake of modifying the linker file, it would either keep trying indefinitely or fail promptly, after which I all of the sudden had no root access anymore, root checker showed I didn't have root anymore, and upon restarting my device it would be unable to boot into the OS, and instead boot into TWRP. After even more hassle I have some backups ready to easily mitigate all that but I simply cannot comprehend what the problem is. Seemingly I rooted the phone correctly yet when I want to execute a root action like changing something in /system/bin, it just unroots itself and bam. I have also tried doing all of the above through TWRP itself, mounting system, changing the files (successfully), and then unmounting it / leaving it mounted, it would still not be able to boot into the OS.

Bumping.

exactly the same.
i cant flash anything into /system/bin
i also want to patch linker file, to use SSHTunnel properly in Lollipop.
i use CyanogenOS (CM12S), and TWRP.
how to flash it?

Bumping once more. Does no one have this problem at all ?
I mean fine, PIE might not be common now, or the linker file I have might be the fix i need, but what about the system partition thing ?

[Q] Continuous Force Closes

I've recently started having problems after changing ROMs a couple of times.
I tried installing a new Rom (CM12.1) but it is still happening and I've installed a new GAPPS each time too so I guess the problem runs deeper than that.
The ROM runs fine for a bit but then all of a sudden I get a force close which constantly keeps coming up no matter how many times I press 'Ok'.
I've had a few different processes stop but the last two that spring to mind are 'process.android.phone', 'Swiftkey' and 'Google Play'.
I have to reboot but then end up stuck at the splash screen at boot. I then have to Power+Vol Down to go into recovery and then reboot system from there. It then runs through the App optimisation screen brfore restarting.
I've never touched kernels since I've been changing ROMs so whether thats the issue.
Any help with this would be great as otherwise this is the best Rom Ive used.
Thanks in advance

A logcat showing traces of these force closes would help

Aquous said:
A logcat showing traces of these force closes would help
Click to expand...
Click to collapse
I didnt do one on account of me not having a clue what the hell one was
Luckily my friend Google does know what the hell one was.
I've attached a couple of log files created around the time of the unpleasantries which hopefully might shed some light.

This one attached might be better, this was taken after I sorted out my Root Access again so might have more info.
Regards

Looks like a resources issue. Are you running any custom CM10 theme? What happens if you install such a theme providing an icon pack?

Aquous said:
Looks like a resources issue. Are you running any custom CM10 theme? What happens if you install such a theme providing an icon pack?
Click to expand...
Click to collapse
Hi, thanks for your reply. I havent been near any other custom themes. I've had this problem over a couple of Roms too.
I've tried to generate a catlog to get some error messages around the time its happening but I keep getting constant force close boxes which stop me doing anything (for a couple of different processes). The only way to stop them is to reboot but then the logs stop and reset when it boots so I cant get the info.
I've had to reboot about three times today and each time it has had to optimize the apps for some reason.
I've tried to get a catlog through ADB but I cant run the Android SDK as I need to install the JDK which keeps giving me 'Error 1500' on the install (even though I am most definately not already trying to install it).
Thanks for your help so far though and taking the time to read through the previous log.
Every solution I try just seems to create more problems
I've managed to attach a text file of all the error files its had since it started up (they are all in the space of about 10mins)

I'm not seeing any force closes in there. In your previous log, I saw these lines:
Code:
07-15 18:24:07.919 W/ResourceType(2356): No package identifier when getting value for resource number 0x00000000
07-15 18:24:07.919 W/PackageManager(2356): Failure retrieving resources for [insert any package here basically]: Resource ID #0x0
which led me to identify resources (i.e. icons, drawables, etc) as your culprit.
What we need to do with that information, I wouldn't know. Ask the rom dev, I suppose?

Aquous said:
I'm not seeing any force closes in there. In your previous log, I saw these lines:
Code:
07-15 18:24:07.919 W/ResourceType(2356): No package identifier when getting value for resource number 0x00000000
07-15 18:24:07.919 W/PackageManager(2356): Failure retrieving resources for [insert any package here basically]: Resource ID #0x0
which led me to identify resources (i.e. icons, drawables, etc) as your culprit.
What we need to do with that information, I wouldn't know. Ask the rom dev, I suppose?
Click to expand...
Click to collapse
Well I'm assuming their force closes. I get a white box popping up that says 'unfortunately XXXXX has closed' and when I click 'ok' the box goes away but either comes straight back or another similar one pops up. Its Trebuchet quite a lot.
I can't do anything then, if I try to get to LogCat that closes too and I can't really do anything until I reboot.
Its happened over 3 different Roms so dont think theres much the Rom compiler (is that what they're called, lol) can do.
I'm am probably going to have to see if I can get a Log through ADB, if I can remember how to use it, when I have time.
Cheers

I've managed to connect the tablet through ADB and managed to get some errors taken at the time I started getting all the 'Unfortunately XXXXX has closed [ok]' boxes kept coming up.
All the error messages attached came up in the space of a few seconds.

Ahh, now this is interesting. The main cause of your problem is that your filesystem is remounted read-only, which Play Store Services doesn't like.
As to why this is going on I can only guess, but it's possible that it's due to filesystem corruption. Can you try running fsck from recovery?

Aquous said:
Ahh, now this is interesting. The main cause of your problem is that your filesystem is remounted read-only, which Play Store Services doesn't like.
As to why this is going on I can only guess, but it's possible that it's due to filesystem corruption. Can you try running fsck from recovery?
Click to expand...
Click to collapse
Hi,
Thanks for looking through them errors.
To be honest I haven't heard of fsck. Is it something I can pick up fairly simply or am I more likely to do more damage? I've done a few searches and it looks a bit difficult and couldn't really find any threads that sounded similar to what I might need.
Thanks again
Update : I've gone into recovery and found files in /system/bin called fsck.exfat and fsck.f2fs is it a case of running a command through terminal command in recovery from this directory?

Fsck is the linux file system checker. The binary is named e2fsck. I think the command should be:
Code:
e2fsck -pv /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS
This will try to automatically fix any errors (be sure to note whether there are any). If it complains about unexpected inconsistencies, you'll need to remove the 'p' argument to prevent it from trying to do any automatic fixing.
Note: the whole point of this command is to check and, if needed, modify low-level filesystem structures, so there is a risk of data loss on your DATAFS (i.e. /data) partition.
Be sure to note if there are any errors. If there are, we need to investigate where those are coming from. If not, something else is causing your fs to remount readonly (because THAT is ultimately what is triggering your system to flip out).
(Apologies for the delay, it's been a busy week)

Aquous said:
Fsck is the linux file system checker. The binary is named e2fsck. I think the command should be:
Code:
e2fsck -pv /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS
This will try to automatically fix any errors (be sure to note whether there are any). If it complains about unexpected inconsistencies, you'll need to remove the 'p' argument to prevent it from trying to do any automatic fixing.
Note: the whole point of this command is to check and, if needed, modify low-level filesystem structures, so there is a risk of data loss on your DATAFS (i.e. /data) partition.
Be sure to note if there are any errors. If there are, we need to investigate where those are coming from. If not, something else is causing your fs to remount readonly (because THAT is ultimately what is triggering your system to flip out).
(Apologies for the delay, it's been a busy week)
Click to expand...
Click to collapse
Hi,
No worries mate, I wasn't sure if what I said didn't make sense thats why there were no replies
The problem seems to be a lot better now but I've still had it a couple of times over the last two days.
I've tried to run the command above but with no joy. I'm still only learning the basics of ADB so still having some trouble.
I wasn't sure exactly where to run the commands from through the SDK so just went to the Terminal Command in Recovery and after navigating to the system/bin folder tried that command but it came up with the following:
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS is in use
esfsck: cannot continue, aborting
I apologise if some of what I am doing seems nonsense but I am trying to pick up what I can by myself from various sketchy threads to avoid being a 'tell me what to do cos I can't be bothered looking myself' person. I dont know if this is doing more harm then good
Thanks again in advance for your help.

You cannot check a filesystem while it is in use. Solution: boot to recovery (sorry, I should have specified), then make sure your data partition is not mounted (in CWM it isn't by default, which is good). Then it should be able to run.
(so: boot tablet to recovery, on computer run 'adb shell', in adb shell copy/paste the actual fsck command)

Aquous said:
You cannot check a filesystem while it is in use. Solution: boot to recovery (sorry, I should have specified), then make sure your data partition is not mounted (in CWM it isn't by default, which is good). Then it should be able to run.
(so: boot tablet to recovery, on computer run 'adb shell', in adb shell copy/paste the actual fsck command)
Click to expand...
Click to collapse
For some reason I cannot get my PC to pickup the tablet in a command window when in TWRP so I was unable to run through ADB. 'ADB Devices just did not show anything.
In the end I did it all on my tablet in TWRP through the 'Command Terminal'. I navigated to the necessary folder (the one with fsck.exfat and fsck.f2fs in - /system/bin) through the Command Terminal and after typing the command in I got the following:
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS clean, 9086/791520 files, 694414/3160055 blocks
Is that good?

It means that your emmc is fine and that there's a different reason why you're getting force closes. Can you post a dmesg next time it happens?

Aquous said:
It means that your emmc is fine and that there's a different reason why you're getting force closes. Can you post a dmesg next time it happens?
Click to expand...
Click to collapse
Hi, yea sure. I could use a bit of guidance with exactly how to do that though. I take it that is something I would have to run through ADB from my PC before I reset my tablet? Step by step instructions would be appreciated a lot (as has your extensive help already, creep creep ).

Boot to normal android. Wait until you start getting force closes. Stick your tab into your computer, run 'adb shell', then run 'dmesg'. If it says permission denied, run 'su' first and then run 'dmesg' again. Post the output.

Aquous said:
Boot to normal android. Wait until you start getting force closes. Stick your tab into your computer, run 'adb shell', then run 'dmesg'. If it says permission denied, run 'su' first and then run 'dmesg' again. Post the output.
Click to expand...
Click to collapse
Right, first thing this morning I had some errors, so I've managed to paste the results of a dmesg into the log file attached.
Cheers!

Hmmmm, now this is interesting. It looks like random services are failing to load - they are immediately exiting after being restarted. This is basically the same problem as with your apps force closing - something at the lower layers is causing everything to crash immediately upon launch.
Yet you're able to run basic programs (e.g. adb, dmesg) just fine, meaning that it's not likely to be a hardware issue.
What happens if in adb shell you run su and then 'stop' followed by 'start'? What should happen: when you run 'stop', the whole system freezes, and when you run 'start', you see your boot logo and android starts booting up again. Is this indeed what happens in this case, or do you get a bootloop? If so, post another logcat when you're stuck in the loop; you can get out of it by simply entering 'reboot' in your still-open adb shell.

How to debug data related bootloop?

begonia (Xiaomi Redmi Note 8 Pro), MIUI 11.0.6.0
I had an unfortunate series of events that resulted in a booloop. Basically:
- Magisk suddenly stopped working one day, after 1.5 year of no issues. I did nothing related to it recently, except just using root functionalities in e.g. Tasker
- I flashed newer Magik 23 and also updated TWRP fom 3.3.1 to 3.5.2
- everything worked fine up until one restart, which resulted in TWRP encryption problems. Right before restart I'm pretty sure I installed Viper4android. I could still get into system with a workaround of TWRP's "Decrypt user" hanging into button reboot, but Magisk/root wasn't working anymore
- so I thought reflashing Magisk and dm-verity/forceencrypt would help, but here's where the bootloops started. During the flash attempts I saw some partition mounting errors since the device was decrypted, so maybe that caused some data issues?
I tried now:
- downgrading TWRP to 3.3.1 - decryption works fine in it and I can flash problemlessly from it, however, doesn't help with bootloop. Reflashing Magisk/dm-verity zips from it also didn't help
- flashing recovery ROM (the same MIUI I had - 11.0.6.0) changed nothing
- flashing fastboot ROM in MiFlash with "save user data" option changed nothing, except I guess confirming the issue is with data
- last thing I tried was flashing uninstall.zip for Magisk since that removed its data folders, which I thought may have got corruped, also to no avail
I know it would probably get fixed with data wipe, but I need the data - I have hundreds of apps with lots of configuration for permissions, notiications, etc. and my recent backups from few months ago vanished because SD card got lost. I have a TWRP 3.3.1 backup of the data now, too bad I didn't do it before updating Magisk/TWRP - lesson learned... So the question is - what can I still do to further debug and fix this without losing data?
I read that reading these logs may also help with debugging, but not sure what to look for.
Kernel log (/proc/lastkmsg): https://pastebin.com/T2xBBRvi - some error looking lines at the end, but non-comprehensible. Can I use them somehow futher?
dmesg log: https://ghostbin.com/paste/vyBDk - don't really see anything here, but it's quite long and not sure what to look for
logcat: https://ghostbin.com/paste/PSh7f - lots of "avc" errors
Please help

Bump. Any help would be appreciated

Plug in the USB cable with the phone powered off. Then issue the commands
Code:
adb devices
adb wait-for-device
adb logcat
from your Windows CMD or Linux terminal: it will hang waiting for the device to come on-line, now power up the phone. The logcat should start scrolling off then.

While it's turned off:
Code:
$ adb devices
List of devices attached
mfaajbdu5s79pfhy unauthorized
If you `adb wait-for-device`, the cmd just waits and you can't enter next command.
`adb logcat`, if I skip the above, waits for device itself, but nothing happens, it just restarts to TWRP and the commands still hang. I can use logcat while in recovery though, that's what I did above

Ok, so I just went ahead and tried the following, too:
- made sure the TWRP data backup can get restored, just in case
- wiped data through TWRP, still the same (re)bootloop into TWRP. I tried both factory reset and advanced wipe with Dalvik/Data/ntenal Storage/Cache.
- so I tried reflashing 11.0.6.0 using MiFlash with that erasing data. That at least worked and phone boots after doing this, but unfotunately not what I'm looking it
- I then tried to get TWRP 3.3.1 back. I got into that and the usual rooting steps were invalid - recovery_fromboot ile was not present in system_root/system. Maybe that's not just present in downloadable ROMs? No clue, but doing the rest of required rooting steps - Magisk 23 install -> Close AVB (TWRP action) -> Remove dmverity (TWRP action) resulted this time in infinite type of bootloop, not sure why, waited for over 30 minutes
- so I reset into TWRP and tried flashing the dmverity zip that's from xda. And this is definitely what caused previous (re)bootloop as after flashing that its more or less the same time length before boot stops and restarts into TWRP. Now, weirdly, while installing this there was an error this time, saying that nvdata cannot be mounted
So I guess the problem before was with mounting nvdata? I see it's something related to phone's IMEI. How does it work exactly, is it somehow related to /data partition? Why wouldn't it mount? Why does it work with pure standard flashed ROM? Is it supposed to be empty when you look at it with TWRP's file manager? Could be something else but this is my only clue right now...
EDIT: oh, you can mount it in TWRP and that works fine, it's not empty. Not sure why that install scipt suddenly stated claiming it can't be mounted, by the end of log, though.

Completely no insights?

I'm coming back to the topic after almost 1 year on old backup phone because I got depressed by this incident and couldn't continue working on it. The old one is like 6 years old, it has abysmal battery life, it ran out of space and I can't install certain apps on older Android, I'm also missing a lot of the set up that I had and which was pretty convoluted - with Tasker and lots of other heavily configured apps. Which slows me down each day.
I can bring the new phone into usable state anytime, a matter of less than hour and reflashing the soft completely, however, setting it up initially took me one year of almost daily changes, many of which can't be retraced as my Titanium backup is old for some reason and there were a bunch of root related changes.
So any sort of help as to how I could potentially recover it with the data would be really appreciated.

And bump

Let's try a bump again

And one more hopeful bump. I'm even willing to pay/donate for any useful insight that will lead to progress with this as my old backup phone is becoming unusable and I don't want to start setting up this one from scratch again.

One last bump before trying in a new topic.
TLDR: what's the best way to debug a bootloop? Do the logs above help or is there something else?

Destroy666x said:
I'm coming back to the topic after almost 1 year on old backup phone because I got depressed by this incident and couldn't continue working on it. The old one is like 6 years old, it has abysmal battery life, it ran out of space and I can't install certain apps on older Android, I'm also missing a lot of the set up that I had and which was pretty convoluted - with Tasker and lots of other heavily configured apps. Which slows me down each day.
I can bring the new phone into usable state anytime, a matter of less than hour and reflashing the soft completely, however, setting it up initially took me one year of almost daily changes, many of which can't be retraced as my Titanium backup is old for some reason and there were a bunch of root related changes.
So any sort of help as to how I could potentially recover it with the data would be really appreciated.
Click to expand...
Click to collapse
Titanium backup is now broken, at least the recovery is now broken. You also are not allowed to start duplicate threads.

Titanium backup doesn't really help me anyways. And ok, I guess I'll keep bumping it then...

Can you access fastboot?

Recovering files from a boot looped Pixel 4a

Recently updated my Pixel 4a and have run into an issue that causes a strange boot loop to a screen that states "Cannot load Android system. Your Data may be corrupt." and prompts to either factory data reset or try booting again. What's strange is that when attempting to boot it again, it is able to load into the device and I have normal access to the phone for about 30-60 seconds before it restarts and prompts a factory reset again.
My main issue is that I need to backup/upload about 900 photos to google photos that were not saved. So far the phone has been rebooting, connecting to wifi and uploading about 0-3 items to google photos per boot until it restarts. Eventually I may be able to secure all my photos this way but I want to know if there is a more efficient method to do this.
Things to know:
Bootloader is locked (can't unlock due to wipe) -> cannot use custom recovery/ flash twrp
USB debugging is enabled and I have sideloaded the latest OTA (sunfish) via ADB sideload in recovery mode but the boot loop has not resolved.
I can successfully use ADB pull /sdcard/DCIM/Camera for only up to 60 seconds until it force restarts. When I attempt to pull again on the next boot, it will pull the same files because it is copying and not moving them.
Does anyone have a solution to this rather than to just factory reset or continuously rebooting? It is frustrating because I still have access to the phone's files but only for about less than a minute. I have scavenged reddit threads, forums, and google for some way to do this but to no avail. (Also is there a way to use the stock recovery's "mount /system" option?)

It's not very elegant, but I could totally imagine a script that listed the files and then copied a few at a time, waiting for the phone to reboot before continuing...
I have a python script that uses adb to "sync" a directory on the phone with a directory on the PC, but it's doing a push, not a pull.

a1291762 said:
I have a python script that uses adb to "sync" a directory on the phone with a directory on the PC, but it's doing a push, not a pull.
Click to expand...
Click to collapse
I modified my script a bit to pull instead of pushing, it's ... awfully rough (eg. you have to manually create a Camera directory to store the files it copies) but it seemed to work in principle. It might be enough for you, or it might serve as a base for a better solution. No doubt it'll need a few mods anyway, especially if you're on Windows (in which case ls won't work).
You might also try booting into safe mode, in case that stops the phone from rebooting? https://www.androidauthority.com/how-to-enter-safe-mode-android-801476/

a1291762 said:
I modified my script a bit to pull instead of pushing, it's ... awfully rough (eg. you have to manually create a Camera directory to store the files it copies) but it seemed to work in principle. It might be enough for you, or it might serve as a base for a better solution. No doubt it'll need a few mods anyway, especially if you're on Windows (in which case ls won't work).
You might also try booting into safe mode, in case that stops the phone from rebooting? https://www.androidauthority.com/how-to-enter-safe-mode-android-801476/
Click to expand...
Click to collapse
Thank you for the reply! I am on Windows and I am not too script savvy out of writing a few simple AHK actions so I am not entirely sure how to proceed with what you have there.
Booting into safe mode did not work unfortunately. Seems the time until restart was the same as well.

Expressionize said:
Thank you for the reply! I am on Windows and I am not too script savvy out of writing a few simple AHK actions so I am not entirely sure how to proceed with what you have there.
Click to expand...
Click to collapse
I do have a windows PC for gaming so I'll fire it up and see if I can make it work there.

a1291762 said:
I do have a windows PC for gaming so I'll fire it up and see if I can make it work there.
Click to expand...
Click to collapse
I was able to brute force the process and finally made my way through the photos. There was one lucky boot that allowed normal access for about 3 minutes and that was enough time for adb pull to completely grab what I needed. I appreciate your time and help.
I guess it still doesn't solve the issue if someone else runs into my similar situation though, but it seems like a rare enough problem.

Expressionize said:
I was able to brute force the process and finally made my way through the photos. There was one lucky boot that allowed normal access for about 3 minutes and that was enough time for adb pull to completely grab what I needed. I appreciate your time and help.
Click to expand...
Click to collapse
No worries. I'm glad you got your photos.
I had to go out, but I got back and literally just finished updating the script so it runs on Windows and is a bit smarter (eg. waiting for the phone to come back when it goes away). I'll attach it here in the event someone else finds it useful
There's a few variables at the top to configure it. It needs python and adb but shouldn't need anything else.
python3 fetch_files.txt
It's got a .txt extension instead of the more typical .py because XDA won't let me upload a .py file.