Database Info

Need a Microsoft Surface RT Recovery

Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.

adam_4049 said:
Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.
Click to expand...
Click to collapse
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.

C-Lang said:
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.
Click to expand...
Click to collapse
i did do a search and nothing has been able to help me so far. i also did read that it is device specific but have also read it has worked for some people. unfortunatley in australia we do no have any microsoft stores so its not that easy to just take it somewhere.
I feel like there are files missing from c drive. Almost like it started to do a restore then stopped halfway. In which I have never been able to get it to that stage for that to be the case.
I did some reading and was able to find the recover partition and tried to run the install.wim file from which I understand to basically be the “OS”. When I try to run it it says “no such interface supported”
From what I understand there is just no way to do a fresh install on these things regardless of what the problem is which is disappointing on Microsoft’s behalf.

C-Lang said:
And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you.
Click to expand...
Click to collapse
No. Those recovery images are device-type specific. Not device-specific. You can safely take one WIM file from the recovery partition of your device and use it to recover a different device of the identical model.
adam_4049
I see that you were able to start a restore process and it fails in the middle.
You may try the following: boot into the command line mode and format the boot partition (probably drive C: ). This would fix the disk errors if they are present, but you'll lose everything. Use diskpart tool to find the disk letter. Be careful with diskpart - do not delete partitions or issue "clean" command.
Then assign the letter to recovery partition with diskpart (say, R: ), then expand WIM file from the recovery partition with the command like this:
Code:
Dism /apply-image /imagefile:R:\RecoveryImage\install.wim /index:1 /ApplyDir:c:\
R:\RecoveryImage\install.wim - a path to install.wim on the recovery partition.
More info: http://technet.microsoft.com/en-us/library/hh824910.aspx - you need only "Dism /apply-image" part, bcdboot is unnecessary. Lets hope that "apply-image" option is present on RT.
This would forcibly expand the WIM file to your disk C:. Or at least you'll be able to see why it fails.
This may help. Or may completely brick the device and you'll need to go to service. So use it on your own risk. And you should be familiar with the command line - so don't ask how to use diskpart.
I had a problem with the recovery process when I've played with BCD and added a boot from VHD option. Had to delete that extra boot setting - and then recovery went fine. But I assume that you have not played with BCD.

Yeah, looks like people dont use search, what you want is a nice useful soul that creates a USB recovery from his EN-UK Surface_RT and puts it up on Copy, or Dropbox or something like that...

Moto G XT1040 LTE- Bricked, Have Fastboot And CWM

Persistent bricking of a Moto G XT1040 LTE
I'm happy to PayPal $20 to anyone who figures this one out...
One day it was working, and then - it froze and went to the loading screen and stayed there. I've unlocked and rooted and used for months with no issue. I've tried everything I can find to fix my Moto G LTE gen-1 XT1040, and I'm at my wits end.
It works, in the sense that I can load fastboot, and I can load CWM (I cannot load any version of TWRP), but I can't get into an operating system. I've tried flashing the stock OEM, I've tried flashing lolipop, slimkat, cyanogenmod - no luck with anything. It does not load into recovery (stock, CWM or TWRP) but can load CWM with "fastboot boot cwm.img" (fastboot flash boot cwm.img then booting into recovery fails).
It looks like some parts of the cyanogenmod flashing stuck, but since then nothing else seems to do anything. Also, the system partition seems to be "raw" when I try to use it - I can't delete my user data (things have persisted despite wiping commands from fastboot and in adb and in CWM). It looks as though anything I'm trying isn't "sticking". I've tried to be as detailed as possible with screenshots.
Maybe: corrupted system partition? somehow things are "locked"? should be hardbricked and then reinstalled as device driver? hardware issue?
All images / screenshots / logs with details are here: imgur.com/a/dQQGD
Any suggestions, tips, advice on this one? Your help would be very appreciated.

Sounds like the emmc corruption (making phone read-only) that possibly affects many phones. There are certainly numerous cases of this happening with Moto G - so many infact that I have looked into getting ROMs to boot via OTG-USB drives. There appears to be many 'solutions' if you search around, but I know of no single case where someone has fixed the problem. Replacing Motherboard is of course an option.

lost101 said:
Sounds like the emmc corruption (making phone read-only) that possibly affects many phones. There are certainly numerous cases of this happening with Moto G - so many infact that I have looked into getting ROMs to boot via OTG-USB drives. There appears to be many 'solutions' if you search around, but I know of no single case where someone has fixed the problem. Replacing Motherboard is of course an option.
Click to expand...
Click to collapse
Hmm.. Thanks for your reply. In another thread user liveroy posted "The eMMC is not corrupted or defunct, you just got the fs on those positions destroyed, therefore they are not formatted now, thus being RAW. If you still have custom recovery installed, try formatting /system, /data and flash CM12."
Any way to follow-up on that? Is there a way to do the formatting from adb?
I'm OK with replacing the motherboard, if that's needed. No idea where to find this particular part though.
Tried "mount -o rw,remount -t yaffs2 /system" got "mount: can't find /system in /proc/mounts"

canwond said:
Hmm.. Thanks for your reply. In another thread user liveroy posted "The eMMC is not corrupted or defunct, you just got the fs on those positions destroyed, therefore they are not formatted now, thus being RAW. If you still have custom recovery installed, try formatting /system, /data and flash CM12."
Any way to follow-up on that? Is there a way to do the formatting from adb?
I'm OK with replacing the motherboard, if that's needed. No idea where to find this particular part though.
Tried "mount -o rw,remount -t yaffs2 /system" got "mount: can't find /system in /proc/mounts"
Click to expand...
Click to collapse
I was under the impression the appearance of partitions being 'raw' was just another symptom of corruption. I gave some ideas to try regarding formatting in the later posts of this thread.
Look for an XT1040 with broken screen, but still functional; as a cheap way to get a motherboard.

[Completed] Elephone P6000 - dead emmc or a partition/filesystem problem that can be fixed?

I have a serious problem with my Elephone P6000 (MTK6732). Following a freeze, it seems my internal storage got corrupted. After a few attempts at fixing the issue by wiping and formatting in recovery, I resorted to a clean flash through SPFT. SPFT looks like it's working, but I suspect it's not actually writing anything, because:
- the format part of the operation is way too quick
- I am not injecting a custom recovery in the scatter file, but my custom recovery remains functional on the phone
- nothing changes in terms of normally booting the phone (i.e. it doesn't)
I have some I/O errors in dmesg, and I very well understand this could simply be a case of hardware failure that no amount of hacking can fix, but I read this is not always the case so I am still giving it a shot.
I also tried using parted via adb, but the changes I make don't seem to persist. I can still mount and unmount /cache and /system and their contents don't appear to be damaged. I wanted to give SP Multiport Flash a shot, but it complains about the COM port and I can't figure out how to set it properly.
Is there anything left to try or should I assume it's indeed a hardware problem? SPFT not working really concerns me. Would a nandroid backup help? I think I made one a few months ago and I am looking for it on my PC but I haven't found it yet. For clarity, I can still boot into Fastboot and CWM, I can still use a shell via ADB and SP Flash Tool still talks to the phone.

Forgive me fot bumping this but it would be great to get some help.

Hi,
You've asked in the correct section: http://forum.xda-developers.com/android/general/p6000-thread-bug-fixes-faq-info-t3028845
so I'll close this thread.

TWRP backups

So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:

mark7807 said:
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
Click to expand...
Click to collapse
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.

exad said:
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
Click to expand...
Click to collapse
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.

mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.

mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
RC1 and backup system image, vendor image, data and boot.

robocuff said:
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
Click to expand...
Click to collapse
TheBurgh said:
RC1 and backup system image, vendor image, data and boot.
Click to expand...
Click to collapse
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!

mark7807 said:
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
Click to expand...
Click to collapse
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?

mark7807 said:
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
Click to expand...
Click to collapse
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.

TheBurgh said:
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
Click to expand...
Click to collapse
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??

mark7807 said:
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
Click to expand...
Click to collapse
Not that I am aware of. Mine is rooted and backups have been smooth sailing.

I recently attempted creating a nandroid backup via TWRP on my rooted Pixel and I'm consistently getting an error: 'cannot create [path]\backup file" message from TWRP. Is there a permission issue that I've overlooked here or does anyone have any thoughts as to why my rooted Pixel would be denying TWRP authority to create the backup?
Thanks

What version of twrp ?
I only use rc1, never seen this.

Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.

pstgh said:
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
Click to expand...
Click to collapse
When you boot into TWRP did it ask for your unlock PIN? If it doesn't/didn't, either keep rebooting into recovery or turn the phone off and go back into recovery until TWRP does ask for your encryption PIN. Sometimes TWRP doesn't ask, and without the PIN being entered, it can't write to the internal storage.
If you click "Install" in TWRP and see a bunch of gobbledygook it's because the internal storage is still encrypted so TWRP can't do anything with it.
You could probably use USB OTG through the USB-C connector, though, to do a backup to it, if you need to.

Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks

pstgh said:
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
Click to expand...
Click to collapse
I can't confirm since I've yet to do a successful backup but... Flashify Pro version looks like an option???
also
Anyone know when TWRP 3.1.0-0 will be out for Pixel? Looks like it addresses boot slots which off first glance seems like quite a fundamental feature no?

Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.

pstgh said:
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
Click to expand...
Click to collapse
Root Explorer does have support for Google Drive. In Root Explorer touch the plus sign in the lower right corner and in the menu that opens choose Google Drive tab.

Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.

pstgh said:
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
Click to expand...
Click to collapse
It sounds like you've got the right idea. Cut will move the files, copy will do just that. You choose one of the two and browse to the Google Drive tab, find the folder you want to use and then use the little clipboard thing to transfer the files to that folder. If that's what you're doing, the only thing I can think of right off the top of my head would be that you don't have enough space left on Google Drive for the size of the files you're trying to transfer. Try a picture or something and see if it takes that. If so, I'd suspect lack of Drive space is the reason it fails.

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?