Hello, guys and gals!
I think that I may have messed my only phone up too much. My phone is a Samsung Galaxy Grand 2 Duos SM-G7102 ms013g that was bought around 2014.
Some background info (very long, if you don't want to waste your time reading all this, skip all the grey parts until you reach "The Problem"):
It was originally owned by my mother. It all started when my local carrier decided back in around 2015 or 2016 that my Windows Mobile phone that was running Windows Mobile 6.0 until it hard bricked itself that their network is no longer compatible, I waited patiently until my mother had been gifted a completely new phone in 2019. This resulted in my mother giving me her old phone with my SIM card in.
In late 2020, I started using my phone for hanging out with my friends, but I also started charging it with the power brick that I have until I finished all my conversations each day. It was performant at the time.
When I started using Instagram, I realized that I couldn't post pictures, so I started investigating the app info and found that it's running a version which was released in 2018. The newer updates required running Android Lollipop or greater, so I installed custom ROMs that allowed me to run the latest version of Android. The last ROM that I flashed was Resurrection Remix Nougat.
Because I bought a Samsung Galaxy Tab S8 that came with Android 12 back in June 2021, I decided to update my phone to LineageOS 19.1 with Android 12L obtained from this thread: https://forum.xda-developers.com/t/rom-unofficial-ms013g-12-lineageos-19-1-stable.4516799/ on November 2022. Everything went fine until 2023 started.
The Problem
-----------
My phone was running Android 12 in a semi-stable fashion, with the following issues discovered:
- Taking very long to boot up because it was showing the Samsung logo for around 2-3 minutes
- Some of the UI is not running at 60 FPS, especially when scrolling down the notification bar
Now, it was suffering from a major problem, which made me have to update the time and the date each time my phone booted up. Upon reboot or a cold boot, the phone would reset its time and date to a date and time that I've installed Android 12 on back then. This resulted in my phone not connecting to WiFi until I set the date and the time back to today's date.
Thinking that it's from LineageOS 19.0, I proceeded to download LineageOS 18 Android 11 Go (https://forum.xda-developers.com/t/rom-android-11-go-ms013g-lineageos-18-1.4512867/) and TWRP 3.7.0-9 (https://forum.xda-developers.com/t/recovery-ms013g-twrp-3-7-0_9-0-for-ms013g.4514667/), fully understanding the warnings that may have come with both the threads. Then, I rebooted my device to recovery.
First, I ran a backup of my device, but I saw that everytime I make a complete backup off TWRP, the compressed size was actually bigger than the total size by around 40 MB. When that finished, I proceeded to install TWRP to the recovery partition by clicking on the Install Image button and selecting the TWRP image. I then rebooted into recovery again and saw that it's running the updated version.
I proceeded to wipe the device completely (dalvik, system, cache, data) except the external SD card that was holding the ROM files, which went fine. I then went ahead to install the Go version of the ROM as per the thread's direction that tols me not to flash Gapps as MicroG was already included, which made the ROM lighter.
When that finished, I rebooted the phone to find that it successfully booted to Android 11, with the setup wizard showing up. It even detected my SIM card that was inserted to my phone. All went fine until I tried to access the Aurora Store, and saw that it couldn't find any application, resulting in the store only showing "No available apps" or something like that.
Next, I proceeded to download the Windscribe VPN, and saw that while the browser was loading sites fast, the download was very slow. It said that it's going to take one hour, which I wasn't going to wait for because it was too late. All that despite having an 8 Mbps connection supported by the fiber optic and not the copper ADSL wires.
As a result, I thought that maybe it was the system, so I rebooted Android.
The date and the time reset again back to when I first installed Android 12 (November 2022), but now it showed me a completely new issue. I wasn't prompted for the SIM unlock code as it used to prompt me for each time I reboot. Even worse, when I opened my phone, it no longer detected my SIM card!
When I checked the system information, I saw that the IMEI numbers went to Unknown for both my SIM card slots. My SIM card was placed on the first SIM slot. I decided that enough was enough and rebooted my phone to the TWRP recovery.
I wiped everything again (dalvik, system, cache, data) and tried to restore the phone from backup, but at the end of restoring the system, the recovery turned itself off, flashed the black screen for a millisecond, then went back to the main home screen for the recovery. I tried again, but it's the same.
So, I decided to re-install the whole Android 12 ROM from scratch, but instead of installing Gapps, I installed MicroG. I then rebooted the phone to see that instead of booting up, it's now stuck in a reboot loop.
The Samsung logo showed up for around 2 minutes and then the LineageOS boot animation showed up. After another 2 minutes, I saw that the backlights turned on. However, it kept on instead of turning off. As a result, my phone kept trying to boot until the screen went darker and the backlight turned off. After few seconds, the phone rebooted and it kept doing this cycle.
I rebooted the phone to the recovery, thinking that it might have been a compatibility issue with the recovery that I've installed, to wipe everything again. I restored the earlier working recovery, and installed Android 12 and MicroG. I rebooted, but the problem still persisted.
I rebooted the phone again to the recovery, and, this time, I reinstalled Android 12 with the Gapps package made for Android 12L. I rebooted the phone to finally see the setup wizard, but when I clicked on Start, the "Factory data reset" popup appeared with "Rebooting" underneath it. This caused my phone to reboot continuously.
I rebooted the phone to recovery to reinstall the latest recovery available for my phone. I think I may have killed my phone's software while trying to restore the Android 12 software. The time was too late, so I left my phone in the recovery mode at 100% battery charge.
I did the factory reset, but when I rebooted the phone, the "Factory data reset" popup still didn't go away. This time, when I rebooted to recovery, it showed 4% battery.
Below shots in the attachments are trying to describe what I'm seeing in my phone, the /system partition, and the /system_root partition before and after wipes as I thought that the /system_root might be the cause.
https://imgur.com/OEHsRgh
https://imgur.com/1yoGdLt
https://imgur.com/eihrtwW
https://imgur.com/J7YWkct
https://imgur.com/tafl3CY
I currently restored the recovery partition to go back to the older TWRP that didn't have /system_root.
I can't afford to buy another phone, even the mid-range ones like the Samsung Galaxy A53 or the upcoming A54, because the prices in our country recently had a huge inflation. Also, this is my only phone because my last phone, Windows Mobile, hard bricked itself.
Despite my 10 years experience with dealing with Android tablets and phones, this is my first time experiencing a problem that I can't seem to fix. I'm at a loss as to what to do now, so any kind of help would be appreciated.
Also, what caused my phone to behave like this? Should I start over by flashing the latest stock Samsung firmware from Odin?
I finally managed to get out of the "Factory data reset" loop! Here's how.
When I had a chance to discover why this factory reset loop is occurring, I proceeded to reinstall the entire system with Android 12 LineageOS 19.1 using the older TWRP 3.2.3 recovery. I also restored the data partition from the backup that I made before installing LineageOS 18.1 Go. However, it didn't fix the problem, which is strange, considering that the data partition in the backup was supposed to be pristine.
I went ahead to spin up the terminal from within the TWRP recovery to find any possible variables in default.prop that caused this to happen, but I found nothing. Then, I looked at the hexdump of a fota partition (/dev/block/bootdevices/by-name/fota) and wrapped its output using the "more" command, and saw something I've never seen before. It said something along the lines of "prepareUserData failed for system user" and "recovery".
Confused, I went as far as to open the source code of Android as found in this link (https://cs.android.com/android/platform/superproject/+/master:frameworks/base/services/core/java/com/android/server/pm/UserDataPreparer.java;l=128?q="userdata failed"&ss=android/platform/superproject) and saw something about user data preparation, so I went to turning on the USB debugging using TWRP because Android won't let me in because of the "Factory data reset" loop by appending the following properties to the build.prop file:
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
My file already had the "persist.sys.usb.config=adb" line.
Upon rebooting to Android, I turned my old PC on and plugged my phone in to my PC. Then, I installed ADB using "sudo apt install adb" and executed the "adb devices" command to find that it found a device with "no permissions", so I added my device to my udev configuration. When I plugged my phone back in, I tested the command again, and saw "device".
I went ahead to test running Android again, and upon encountering the "Factory data reset" problem, I immediately took a snapshot of the Logcat of my device from my computer. When my phone rebooted to the recovery, I opened the text editor on my computer to look for potential problems. As I scrolled down, I saw the following:
Code:
11-09 09:56:17.500 245 257 E cutils : Failed to chmod(/data/media/0, 1528): Permission denied
11-09 09:56:17.500 245 257 E vold : Failed to prepare /data/media/0: Permission denied
Weird!
My phone was still in the recovery mode at the time. I rolled up my terminal emulator from my phone and checked the permission of the affected folder using "ls /data/media -l" and saw something that is beyond imagination. The user and group permissions for the "0" folder was set to "root"! I wrote the "chown -R media_rw:media_rw /data/media/" command thinking that it'll fix the factory reset loop. Upon rebooting, same issue occurred!
Thinking that I may have missed something, I proceeded to look for possible solutions to this debacle, until I found a viable solution. I captured the Logcat, looked for the error, and found this:
Code:
11-09 09:56:18.189 245 257 E cutils : Failed to chmod(/data/media/0, 1528): Permission denied
11-09 09:56:18.186 257 257 W Binder:245_3: type=1400 audit(0.0:112): avc: denied { setattr } for name="0" dev="mmcblk0p25" ino=129282 scontext=u:r:vold:s0 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=0
11-09 09:56:18.189 245 257 E vold : Failed to prepare /data/media/0: Permission denied
11-09 09:56:18.186 257 257 W Binder:245_3: type=1300 audit(0.0:112): arch=40000028 syscall=333 per=800008 success=no exit=-13 a0=ffffff9c a1=b24c88e0 a2=5f8 a3=0 items=1 ppid=1 ppcomm=init auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 exe="/system/bin/vold" subj=u:r:vold:s0 key=(null)
In my phone, I opened the terminal, and wrote the following commands:
Code:
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ';'
find /data/media/ -type f -exec chmod 664 {} ';'
restorecon -FR /data/media/
When I rebooted my phone, the "Factory reset" issue went away! My SIM is now seen by my phone! The only thing now is that I'll have to set all my applications up, as even Windscribe, Instagram, and all apps are now prompting me to provide login details or configure them. The phone still works smoothly, but still suffers from the date and the time problem.
I prefer to have the date and time problem fixed. Any advice?
Related
I had to restore a backup because my G1 was stuck on the G1 screen. I've done restore before and it all worked fine. This time, I got an error...
1. First, I am running CM5.0.8 with 1.0.7 recovery.
2. Went into recovery and tried nand restore and got the following error telling me to running recovery via console using 'nandroid-mobile.sh restore'
3. Went into console and ran it and got the following error:
error: unable to mount /data, aborting
I've tried to use a copy of my backup files that I had on my computer by moving it to the sd card and still get the same errors.
I'm a complete noob and seem to have messed things up trying to learn more!
Any help would be greatly appreciated.
Thanks
It sounds like you might be having a problem with the SD card, take it out and see if the phone boots up. SD cards die all the time and give you various symptoms. If that doesn't work, put 5.0.8 on the card and re-flash it. Sometimes my nandroid restore gives me a error if I have too many backups saved, I just have to mount SD card go to nandroid folder -> (device id) folder -> and there will be a folder for each back-up you have made, get rid of all but the last 2 and run it again. This always works for me.
Sounds more like something happened to the userdata partition.. otherwise the error would indicate /sdcard or a md5sum error. (Not sure what I've seen such things but they where entirely my fault.)
From fastboot screen try running 'fastboot erase system -w' from your computer, booting recovery and trying again.
Thank you for the replies.
I think I messed something up due to user error. I was playing with turning swap on and off via a script I had installed (a great script by a member steveo I think). I turned it on correctly by using swapon30 from the terminal but I didn't turn it off correctly (used swapoff instead of swap-off I think). When the blue led wouldnt turn off, I tried rebooting and got stuck on the G1 screen. (I really have no clue if that's where I messed up but that was what I was doing when it got stuck on reboot).
Anyway, I did a wipe/factory reset then it started up fine. I then went back into recovery and restored my last backup from last night which went fine as well. Only kind of weird thing I noticed was that I had to reinstall Google Maps from the market and now it's showing as installed in "system" whereas before it was showing as "internal".
When I did a factory reset and then ran a recovery, perhaps I needed to reflash the google apps that is part of the original CM5 install?
Appreciate the replies guys!
okay so after trying some other options i was able to solve this problem, here is the how to in case this has happened to anyone else. my original post is below the how to.
1.flash the sbf that returns your defy to stock eclair using a different T-Mobile sim, after it is done flashing you will seem to still have the problem, except it will say no sim emergency calls only.
2.power off the device and install your original sim from T-mobile.
3.reboot the device and you will not be prompted to setup motoblur, because you device is in soft brick limbo still, but you will have laggy touch responses, be patient with your device as you navigate to settings>privacy>factory reset and confirm. ( this process will take much longer than usual and the progress bar will not show any progress but it will shutdown and reboot as it normally would with a factory reset)
4. you will now be prompted to setup your motoblur account ( if you are not restart the steps until this happens, if it does not happen your device did not actually do a factory reset you will need to try again until it does ask you to setup blur, this is your sign from the moto gods that your device is no longer in softbrick limbo)
5. setup your blur account ( you will still have no recovery menu at this time so don't try and check or you will have to start back over at step one)
6. now navigate to settings>about phone> check for updates
7.download and install the update to froyo ( durring downloading you phone may shut off several times, however if you reboot it will automatically pick up the update where it left off as if your device never powered off to begin with)
8. once you have installed the update you device will be back to froyo stock and your recovery partition will no longer be bricked
9. enjoy your defy once again, and be more careful with your device in future ROOT mods and tweaks, cheers!
10. If this helped you recover your device please thank me for this solution.
okay so i am new to posting on XDA and i will try to organize my problem as best as possible, but i may need much guidance on if i am posting in the proper forum.
here are my details of my device and the problems i am facing with my device currently.
Motorola Defy
MB525
T-mobile US
stock Froyo rom 2.2.1 ROOTED overclocked with milestone overclock to 1224 mhz @ 85% voltage /V6 SUPERCHARGER SCRIPTS. MODDED BUILD.PROP TO REFLECT THE MAX HSUPA CATEGORY 34/MAX HSDPA CATEGORY 36/ GPRS CLASS 10/ HSXPA=2/RO.RIL.VIDEO_MODES=TRUE EVERYTHING ELSE IN BUILD.PROP WAS STOCK EXCEPT WHAT THE V6 SUPERCHARGER SCRIPTS CHANGES. I was running a custom bootscreen that i placed in the location of the old one using ES file explorer with root browsing rights, i had defy Recovery installed but only used it basically as a system restore app ( context of previous statement is relating to system restore if you were talking about a windows machine) used Avast anti virus as root installation w/antitheft installed used system tuner to manage startups down to core services or other services i did want to run at boot i.e. stuff like facebook and weather channel.
DEVICE WAS ALSO SUBSIDY UNLOCKED
SBF started with and reflashed to try to correct problems was JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.OR_JORDANTMO_PO22_HWp3_SERVICE1FF.sbf
****NOW TO THE PROBLEMS****
I was starting to think that maybe the v6 supercharger scripts were not really doing anything performance wise for me as it would disable my overclock settings at boot and i would have to manually invoke them after everything had requested its SU rights at boot. so i decided to get rid of the v6 supercharger scripts and all other softwares pertaining to managing and running the scripts, I decided the best way to do this was to do as i had always done in the past when wanting to re-tweak my phone and use the stock recovery to start fresh with 0 tweaks and only apply the ones i wanted after restoring to stock, when i used the stock recovery this time it didn't work, i booted the phone back up after wiping data/ factory data reset and to my surprise the recovery did nothing but delete the SU.apk the custom boot was still in tact, everything else listed above still in tact except for the phone was obviously throwing errors left and right because there was no SU for apps to request permissions from, so i reinstalled the SU.apk just to make sure i didn't have to deal with the device being slow while restarting the process of doing a full wipe. this time i used the DefySDrecovery.apk i mentioned above to do the same steps and while adding wiping the dalvik cache after wiping data and before invoking the recovery, it then gave me the same error i have always gotten when wiping the cache which is
e:\ cant mount cache partition
e:\ cant find /recovery/caller
e:\ cant find/recovery/cache
(this has never caused problems with the device once recovery was finished)
this time however I was only able to boot(loop) to the moto logo
so i reflashed The above mentioned SBF and the device booted normally i went through the entire setup like it was a new device with blur and google and it finished. when I got to the home screen it was frozen and would not respond to touch it also showed to have no cellular signal, i turned it of and back on and it made me go through blur and gmail setup again, went to home screen same thing frozen with no signal.
i reflashed the SBF again thinking maybe something went wrong as they do sometimes with RSD yet still finished and passed on everything
the above description repeated except for this time it responded to touch for the first few seconds before it froze completely ( oops! sorry one detail to add when i say it froze i mean froze like would respond to nothing, touch, hardware buttons, nothing) i had to pull the battery in both instances to try and start over, after many attempts of getting in the phone and trying to turn on usb debugging before it froze i finally was able to complete the finger olympics and get usb debugging turned on, i was able to root it using superoneclick so that i could have a look at the logcat in ADB. now in my experiences with ADB normally when you run a logcat command it will print to the screen for about two to three hundred lines and then slow down and only print one to six lines at a time as the server is calling actions when i ran a logcat on this device it runs two to three hundred lines slows down and then runs lines until you close the ADB window i let it run a logcat overnight and it was still running lines the next morning with no sign of stopping where you could freeze the window and read over all the crap it was calling to action, looking at the device durring this process i saw force close windows a few times saying the com.android.process has stopped but the home screen never crashed and the phone didn't do a random reboot. so to sum it all up ( so sorry for the lengthy explaination but i wanted you to have the whole problem fully explained in hopes you wouldn't have to ask for more detail)
it freezes and has no service with my T-mobile sim in it ( if i put my at&t sim in it has service but still freezes)
flashing a new SBF doesn't fix the problem as it should
and there is no way to enter the Recovery Menu now its gone, non existant, cant find it, cant fix it, i'm F***** right now Please help if you know how, and if i totally screwed the phone i'm cool with you saying so but it can still be in a respectful way i already feel like an idiot for not being able to correct this with all the knowledge i have of this phone, a negative attitude insinuated is not going to help me in either direction, thanks in advance for any help you may be able to provide.
Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.
Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.
I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.
Hello all,
I have a Nexus 6P, stock, rooted, with Xposed installed. The phone is completely functional for the better part of its life time since I bought it at release -probably first or second batch- (except for random reboots once daily on average, deemed by my investigation and exhausting all options to be a hardware issue or Xposed related).
Today, out of nowhere, the phone randomly rebooted itself and surprisingly it launched the "Android is starting..." dialogue which, if I'm not mistaken, optimize apps for ART. The battery was at 19% before it randomly rebooted, so when it started that optimize apps it went down to 0 (I assume) and it turned off. The charger wasn't connected correctly so that happened. Now the phone keeps restarting itself up to before it gives me the boot up decryption phase of the Data partition and reboots again. I assumed it can't decrypt Data for some reason, so I launched TWRP recovery to try and decrypt data and take a backup copy of my Titanium Backup folder on storage... Unfortunately, TWRP reports "failed to decrypt data" even though I'm 100% positive that the pattern is correct because I'm literally inputting it almost 10-20 times a day for the past two years...
Note: there seems to be a red blinking LED in the top left corner of the the phone. I never even knew this existed.
WHAT I WILL DO
I'll reflash everything system-wise.. I'm ok with that. I'll reflash the factory images, root it, install Xposed, no problem.
WHAT I NEED HELP WITH
I need to extract some folders from my phone storage, namely the Titanium Backup folder. I know the pattern protection of the encryption.
How do I go about doing this?
UPDATE:
Help is urgently needed now indeed: The phone doesn't even turn on to bootloader mode anymore now. It was able to, just half an hour ago. Now all I see it the red blinking LED.
UPDATE2: https://support.google.com/nexus/troubleshooter/3337561?hl=en-GB#ts=3337942
I'll try in 30 minutes.
Meanwhile, please help me with my original problem; extracting data.
I was thinking, if I boot into bootloader mode, can I use adb to pull any folder? If so, will that work in my case with decryption fails or Data partition doesn't seem to mount correctly?
Relevent:
Reviewing some other threads:
TWRP: 3.0.2-2
Bootloader: UNLOCKED
I did NOT upgrade to Android 7.0 nor was I planning to, until Xposed is available.
I did NOT flash anything **new** recently. However, Installed an Xposed module yesterday which caused a bootloop. I rebooted into TWRP, uninstalled Xposed, rebooted into system (which looped once, out of the ordinary) and I uninstalled that module, back to TWRP installed Xposed, and rebooted back into system. It worked for 12 hours and then what I wrote this post for happened as stated above.
UPDATE3:
15 minutes into charging... NOT EVEN A RED BLINKING LED ANYMORE.
Last? UPDATE:
Almost 1 and a half hour into charging and there is no longer ANYTHING. Is it hard-bricked now?
How the **** is this possible? I'm very much capable of solving any sof-brick but not a hard-brick...
Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck
KLit75 said:
Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck
Click to expand...
Click to collapse
I was indeed able to connect to a PC after I saw the problem (the bootloop essentially)... But I didn't at the time as I didn't have a plan of action as to how to get my data, so I turned it off. After sometime, I couldn't do anything with the phone... Not able to boot into bootloader, not recovery, the phone is essentially not turning on to anything, not even the splash screen; like a hard-brick. I'm not sure if this indeed is a hard brick as I've never seen any.. and don't currently know what to try next.
Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.
TnT_ said:
Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.
Click to expand...
Click to collapse
I honestly declared it hard-bricked.
Will Fastboot show any devices if the phone didn't show bootloader screen?
I'll try again today.
Update:
Didn't work.
check out my post
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
Hello,
I am trying to encrypt my Note 4.. In the years I have tried, I only successfully got it encrypted once.
Right now, I have installed Lineage 15.1. Going through settings, my phone reboots twice, and then boots back up normally.
same thing happens if I use vdc cryptfs enablecrypto inplace .......
Earlier I tried vdc cryptfs enablecrypto wipe It just shows the Lineage 'frown' with the circle going across, it did this for hours. Took the battery out, when I booted back up, it did the same thing, just the circle going across.. I restored my backup without wiping it, have lost WiFi now actually, it won't turn on. So I'll be wiping it again tonight
When I was running the Samsung OS, it would only encrypt if I wasn't rooted.. Which was a non-starter. The one time I got it to encrypt, I started from stock, encrypted, ran KingRoot, then the application that swaps KingRoot for SuperSU.. The next time, the application wasn't successful at removing KingRoot..
I was hoping with Lineage I would be able to encrypt the storage again.
What do I have to modify n Lineage to enable Android's 'forceencryption'? I see this flag discussed, but not where to actually set it... Am I missing something obvious?