So my Swift was struggling to run and kept rebooting on me- I downloaded an app for pokemon go I probably should not have. What i decided after a week of frustration, was to do a factory reset of the phone. But now my phone wont let me finish the install- it lets me get as far as setting up a Cyanogen account, but whatever I do it tells me there is a 'communication error' with the server, suggests changing the WiFi connection and check my SIM us properly installed. It will not let me go past that screen. Ive tried rebooting in recovery, setting up a new cyanogen account and popping in an old sim. nothing but the same message.
I never did anything fancy with the phone. It has been running the stock ROM and was up to date with the software. Im out of ideas, and am looking for any other suggestions.
Anything at all would be awesome. I dont know what information I can give that might help you, but if you need something ask.
Thanks
First thoughts would be that cyanogen are history so setting up a cyanogen account sounds potentially problematic.
Are you not able to skip the account setup? I can't remember.
What version COS is installed?
M.A.K said:
First thoughts would be that cyanogen are history so setting up a cyanogen account sounds potentially problematic.
Are you not able to skip the account setup? I can't remember.
What version COS is installed?
Click to expand...
Click to collapse
Ya... That would explain some things. So now i cant even log into my old account?
Nope.... it does not give me that option.
And when check in fastboot mode, it says the LK version is : Crackling-13-ge86e772.
And both the OEM unlocked and security fuse is set to false.
As it's unlocked, you at least have the option of installing another rom. And we'll have a new rom coming from wileyfox soon, too.
So if i download a compatible rom and install that, it should be okay? Considering my device is unrooted, I didnt think that was an option. Sorry about this...
Yes. As you've already done a factory reset you don't have to worry about your data being compatible.
It may be worth trying to flash the latest COS first just in case something has somehow been corrupted. But failing that, install TWRP and try LineageOS or crDroid.
awesome!! I will give that a go. Thanks so much
Related
I flashed Viper, now in the initial setup I am presented with this message:
"This device was reset. To continue, sign in with a Google Account that was previously synced on this device."
I enter my credentials, and it brings me back to the same prompt. It is in an endless loop and I can't get into my device. What do I do now?
Edit: Tried using the "Forgot password" link using the HTC 10, reset a new password, still having same issue.
Edit 2: I reset my Google account password last night. Today I flashed Viper, which is equivalent to a device reset. I just read this: "The moment your Google account password is changed, Device Protection starts a 72-hour timer on your protected device. For that 72 hours, if the device is wiped, the account in question cannot be used to sign into / unlock the phone." So am I on this 3-day lockout? Did the timer restart when I reset my password again today trying to get into the device? Really pissed right now.
If your bootloader is locked and you're S-ON then I don't think you have any recourse besides waiting the 3 days.
If you're unlocked / S-OFF then you should be able to wipe/format in TWRP, reinstall ViperROM and be good to go, but I've never run into this situation personally so I can't be sure.
The 72hr lock begins whenever you change your password so don't change it again.
drumz0rz said:
If your bootloader is locked and you're S-ON then I don't think you have any recourse besides waiting the 3 days.
If you're unlocked / S-OFF then you should be able to wipe/format in TWRP, reinstall ViperROM and be good to go, but I've never run into this situation personally so I can't be sure.
The 72hr lock begins whenever you change your password so don't change it again.
Click to expand...
Click to collapse
Thanks for the reply! From everything I've read, there's no way to clear out whatever identifying information is in the phone that ties it to a Google account. I'm unlocked and S-OFF, so I'll give it a shot if I get time tonight. Anyone else had any experience with this?
Flash RUU to get back to stock if one is available for your device.
yldlj said:
Flash RUU to get back to stock if one is available for your device.
Click to expand...
Click to collapse
Flashed stock RUU, was able to get back into device using my Google account. I think I might have done something wrong when flashing RUU, though, I'm getting lots of FCs. Anyway, I unlinked my Google account from the phone, should I be OK to go back to Viper now?
All is well after flashing stock RUU, removing Google account from the phone, reflashing TWRP and Viper. Thanks!
Glad you're back in business. Make sure you do a full wipe before flashing a RUU, that should clear out anything from the previous install. I think Viper's Aroma installer does it for you which could be why you don't have the same FC issues now. Just FYI.
A friend of mine has the same phone as I have - a OnePlus 3 which we both bought at launch. When he got it, he activated the secure startup in the start up configurations - I didn't.
After a while, he changed his mind to go to CyanogenMod (I always help him with flashing stuff, getting him TWRP, try to explain everything) so I got him the (back then) latest CM. The problem was (and still is) that his secure startup still shows up. He doesen't want it anymore, so do I. I go nuts asking him every time to unlock TWRP / his phone just to change something.
Until now I was always able to answer his questions - I read this forums all the time, and google is my best friend. However it seems that no one actually has this problem, or at least isn't really aware of it. The secure startup is an option under settings, but even if we disable it, after a reboot it shows up again. It shows up even after formatting the whole phone. I deleted all of the partitons, but it still shows. I have no clue where it actually is saved, since it remembers not only the language the phone was prior set to, but also the "welcome message".
Is it in the bootloader? If so, how do I get rid of it?
Another idea was to install an old backup of the original OS, but he doesen't have it anymore. My idea was to recover the backup, then disable the settings in hope that the system thinks "well ok, the hash seems to be the same so ok, I let you through with it".
Any help would be great, since I really have no idea anymore.
__revolt__ said:
A friend of mine has the same phone as I have - a OnePlus 3 which we both bought at launch. When he got it, he activated the secure startup in the start up configurations - I didn't.
After a while, he changed his mind to go to CyanogenMod (I always help him with flashing stuff, getting him TWRP, try to explain everything) so I got him the (back then) latest CM. The problem was (and still is) that his secure startup still shows up. He doesen't want it anymore, so do I. I go nuts asking him every time to unlock TWRP / his phone just to change something.
Until now I was always able to answer his questions - I read this forums all the time, and google is my best friend. However it seems that no one actually has this problem, or at least isn't really aware of it. The secure startup is an option under settings, but even if we disable it, after a reboot it shows up again. It shows up even after formatting the whole phone. I deleted all of the partitons, but it still shows. I have no clue where it actually is saved, since it remembers not only the language the phone was prior set to, but also the "welcome message".
Is it in the bootloader? If so, how do I get rid of it?
Another idea was to install an old backup of the original OS, but he doesen't have it anymore. My idea was to recover the backup, then disable the settings in hope that the system thinks "well ok, the hash seems to be the same so ok, I let you through with it".
Any help would be great, since I really have no idea anymore.
Click to expand...
Click to collapse
Just a thought.
May be the phone picks up the settings from your Google account. Try setting it up as a new phone after wiping and flashing either with a new Google account or with no account and see if the issue returns.
__revolt__ said:
A friend of mine has the same phone as I have - a OnePlus 3 which we both bought at launch. When he got it, he activated the secure startup in the start up configurations - I didn't.
After a while, he changed his mind to go to CyanogenMod (I always help him with flashing stuff, getting him TWRP, try to explain everything) so I got him the (back then) latest CM. The problem was (and still is) that his secure startup still shows up. He doesen't want it anymore, so do I. I go nuts asking him every time to unlock TWRP / his phone just to change something.
Until now I was always able to answer his questions - I read this forums all the time, and google is my best friend. However it seems that no one actually has this problem, or at least isn't really aware of it. The secure startup is an option under settings, but even if we disable it, after a reboot it shows up again. It shows up even after formatting the whole phone. I deleted all of the partitons, but it still shows. I have no clue where it actually is saved, since it remembers not only the language the phone was prior set to, but also the "welcome message".
Is it in the bootloader? If so, how do I get rid of it?
Another idea was to install an old backup of the original OS, but he doesen't have it anymore. My idea was to recover the backup, then disable the settings in hope that the system thinks "well ok, the hash seems to be the same so ok, I let you through with it".
Any help would be great, since I really have no idea anymore.
Click to expand...
Click to collapse
Format whole device leave nothing. Use this chance to convert data to f2fs. Then the password will be gone. And you will have an empty phone to start afresh with
New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
StATicxTW0T said:
New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
Click to expand...
Click to collapse
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
allstar21369 said:
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
Click to expand...
Click to collapse
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I have a rooted XT1710-01, also. If you are going to install Xposed and Gravity Box, I recommend not updating Magisk, above v14. After v15 and now v16, I have had issues with Automate It app and Tasker rules not working, until I uninstalled Xposed.
Downgrading Magisk versions requires flashing your stock ROM and basically starting over.
Motorola has not posted firmware for this model.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
So glad to see someone have it working and with a clear guide. I'm going to buy the phone this week.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Johmama said:
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Click to expand...
Click to collapse
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
allstar21369 said:
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
Click to expand...
Click to collapse
I didn't flash TWRP on my phone. I think I tried it once and it failed for some reason, so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup. Flashing it is up to you, I've always flashed a custom recovery but on this phone I'm keeping the original recovery so I can get an OTA. On my Nexus devices I don't care about OTA because I just flash ROMs all the time so it's no big deal.
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked. As far as turning off encryption, I'm not sure if there's a way to do that. There could be, but to turn it off, it wipes your data as a security measure.
Johmama said:
so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup.
Click to expand...
Click to collapse
Yeah, I can't backup my ROM most likely because I don't have an FBE password. When I go to backup my ROM in TWRP it fails.
Johmama said:
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked.
Click to expand...
Click to collapse
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
allstar21369 said:
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
Click to expand...
Click to collapse
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Johmama said:
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Click to expand...
Click to collapse
Okay. I just wiped and re-set up everything and still no FBE password was asked for OR works when I go into TWRP. I'm using TWRP 3.1.1-0... I suppose I'll try it all again using TWRP 3.2.1-0-albus after deleting data.
*Edit: I did exactly what I just said I was doing booted TWRP 3.2.1-0-albus instead of 3.1.1-0 and when I it booted up and asked me for a decryption password I entered the pin I set up previously and it has been stuck at the "Mount, Trying Decryption" screen for a long time... but it's not frozen. It says "Updating partition details... ...done
Unable to mount storage
Full SELinux support is present.
Data successfully decrypted, new block device: '/dev
/block/dm-0'
Updating partition details...
...done"
And the progress bar/thing at the bottom is still animated like it's working... no forward or back buttons or anything and turning off/on the screen hasn't done anything... not really sure what to do here... I don't want to unplug it and brick my phone or force it off...
*Edit 2:
I now have it all sorted out.
TWRP never finished trying to decrypt data so I long pressed the power button and eventually went here -> https://forum.xda-developers.com/z2-play/development/twrp-moto-z2-play-t3729531 , downloaded "twrp_albus_3.1.2_r18_64.img" and in adb used the command:
fastboot boot twrp_albus_3.1.2_r18_64.img
This TWRP looks a bit different than all of the others but it let me boot up and use my recently created PIN code to actually decrypt my data and make a full backup. After that I just installed Magisk (the latest one, 16.4) as indicated in this guide -> https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792 and everything is fine. I never even flashed TWRP, just booted it.
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
joefuf said:
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
Click to expand...
Click to collapse
I didn't want updates, especially the oreo "upgrade".
pizza_pablo said:
I didn't want updates, especially the oreo "upgrade".
Click to expand...
Click to collapse
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
joefuf said:
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
Click to expand...
Click to collapse
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Double - double \_0_/
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
Yeah, very understandable. It really is superfluous to the general experience.
allstar21369 said:
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
Click to expand...
Click to collapse
Thank you sir! Keep me posted. I'm posting everywhere right now to learn the new methods so I know if there ever comes a time. This is my first phone since my Motorola Droid 4. Back then it was one click root, install and run Safestrap apk to get custom recovery, boot into custom recovery and flash zips to your heart's content. I'm sure this will be as "simple" once I learn, but it's pretty daunting in prospect.
Hello all,
I had a nightly build of Nougat RR on my Zuk Z2 and it was giving me problems. I decided to go to AOSP Extended Oreo. I had a really long randomly generated password for my Google account, and I also had 2FA. I changed the password to something I can easily type and disabled 2FA. I didn't realize this was a no-no and would trigger FRP.
I flashed TWRP 3.2.1 (for Oreo support) and flashed 1.7 Baseband Modem with ADB.
I booted into TWRP and wiped everything. I had backed up the important files; I wanted to start from scratch. I pushed the AEX ROM and GApps using ADB and flashed it using TWRP.
The first bootup took a while, which was expected. It began the initial setup; and told me: "This device was reset to continue, sign in with a Google account previously synced on this device". So I signed in, but it kicked me back out saying "Please sign in using one of the owners accounts for this device." But that is the account that was on the device!
I did a bit of googling, and discovered if I reset the password it would trigger a 24 (or 72) hour lockout for theft prevention. I waited over 72hours and it is giving me the same error, no luck.
On my Google devices page, it tells me an Android phone was last synced.
The phone seems to work beautifully, but I can't get in! Can someone please help?
Many thanks,
Don't flash gapps yet
raz0rev said:
Don't flash gapps yet
Click to expand...
Click to collapse
Thank you for the response! So I should do another wipe using TWRP and only flash AEX? That should let me through? Then when do I flash gapps? I'll give that a shot tonight. I really don't wanna buy a new phone, the Z2 is still so nice.
You Solved?
I'm in the same situation and don't know how to solve it!
paolomatador said:
You Solved?
I'm in the same situation and don't know how to solve it!
Click to expand...
Click to collapse
Flash only ROM then reboot device, once boot up use it for a while then reboot to recovery flash gapps reboot.
Hope it helps
Yes, I did it and it solved. Great!!
Thanks
Recently I dirty flashed PE+ ROM into my moto g40 fusion in a hurry without looking at the developer instructions(which clearly says I should clean flash). So ,now my phone is stuck on starting screen with a faded Google logo.I did not even take any backup(Silly Me)!
But somehow I am able to turn on flashlight by long pressing lock button(It was previously set ). I even hear alarms. I think That means phone is awake but for some reason the display is just a grey Google logo
How to fix this?What should I do?
I think performing a factory reset might boot the device.But Can I somehow recover the data?
@arsradu Can you please help me out?
tableware said:
Recently I dirty flashed PE+ ROM into my moto g40 fusion in a hurry without looking at the developer instructions(which clearly says I should clean flash). So ,now my phone is stuck on starting screen with a faded Google logo.I did not even take any backup(Silly Me)!
But somehow I am able to turn on flashlight by long pressing lock button(It was previously set ). I even hear alarms. I think That means phone is awake but for some reason the display is just a grey Google logo
How to fix this?What should I do?
I think performing a factory reset might boot the device.But Can I somehow recover the data?
@arsradu Can you please help me out?
Click to expand...
Click to collapse
Hello,
I don't have the phone anymore. So this is general info.
For as far as I know, you can't recover the data. However, Google does automatical backups at regular intervals, if you let it. So...chances are you might already have a backup. You could try to use it after factory resetting your phone.
Something else you could try...is flashing back the older version you had on top of this one. Maybe it will let you boot into it successfully so you can get access to your data. After that, I would suggest taking a backup, if you don't have one already.
And if you want the newer version again, make sure you follow the instructions given by the developer and see if that works.
I'm not aware of any other way.
Yeah, it could be that the phone is alive, but...if you can't interact with it...it doesn't help.
Thank you arsradu for replying..
arsradu said:
Hello,
I don't have the phone anymore. So this is general info.
For as far as I know, you can't recover the data. However, Google does automatical backups at regular intervals, if you let it. So...chances are you might already have a backup. You could try to use it after factory resetting your phone.
Something else you could try...is flashing back the older version you had on top of this one. Maybe it will let you boot into it successfully so you can get access to your data. After that, I would suggest taking a backup, if you don't have one already.
And if you want the newer version again, make sure you follow the instructions given by the developer and see if that works.
I'm not aware of any other way.
Yeah, it could be that the phone is alive, but...if you can't interact with it...it doesn't help.
Click to expand...
Click to collapse
I knew you don't have the phone anymore.I read that in the conversations.But I was kinda desperate.So, Sorry that I bothered you.
I hadn't allowed Google to backup my data except for photos and videos.
Flashing the older version of the rom on top of it was the first thing I tried,But the PE Recovery said the data was corrupted , didn't let me to boot into it and it wanted me to factory reset . So in the hope of keeping the data I reflashed the same rom.
But, the exact same advice from you today gave me an idea.I know the data is intact in the device, If I somehow can backup this ,I might restore it in a clean flashed rom!
So I went through other XDA threads,watched some YouTube videos.
Then I boot it into twrp(again, thanks to your tutorial) took a backup of only data,wiped everything, flashed the previous version and restored the backup.And now I am writing from my own device🥹🥹.
But the problem is partially solved.I lost some important files from internal storage (as expected) .When I tap, I cannot open important settings options like individual app info, developer options,restore and backup etc .I can't swipe down the quick settings menu.When I try to toggle night light the display is just getting dark altogether.
tableware said:
Thank you arsradu for replying..
I knew you don't have the phone anymore.I read that in the conversations.But I was kinda desperate.So, Sorry that I bothered you.
I hadn't allowed Google to backup my data except for photos and videos.
Flashing the older version of the rom on top of it was the first thing I tried,But the PE Recovery said the data was corrupted , didn't let me to boot into it and it wanted me to factory reset . So in the hope of keeping the data I reflashed the same rom.
But, the exact same advice from you today gave me an idea.I know the data is intact in the device, If I somehow can backup this ,I might restore it in a clean flashed rom!
So I went through other XDA threads,watched some YouTube videos.
Then I boot it into twrp(again, thanks to your tutorial) took a backup of only data,wiped everything, flashed the previous version and restored the backup.And now I am writing from my own device🥹🥹.
But the problem is partially solved.I lost some important files from internal storage (as expected) .When I tap, I cannot open important settings options like individual app info, developer options,restore and backup etc .I can't swipe down the quick settings menu.When I try to toggle night light the display is just getting dark altogether.
Click to expand...
Click to collapse
Glad you managed to find a way! Good job!
My suggestion would be to make a backup, while you still can, and do a clean installation of the rom.