So, I'm not using it as my daily phone yet, left my mac at work this weekend and I want to apply depixel8 before setting it up the way i want. Knowing full well I would be wiping it, I decided to restore from a google backup from August. This was the last backup before applying Android N to my Nexus 6P. After that update, my 6P bootlooped non stop until I wiped in recovery and set it up without anything restored. Well, after about an hour or so, the Pixel is also stuck in a bootloop. Only way to end it was recovery and wipe. I'm guessing there is something in that Marshmallow backup that isn't compatible with N. Bummer because that's where all my saved wifi networks are.
After I get to run depixel8 tomorrow I'll try restoring and just leave the apps out and see if it sticks.
Related
Hey guys Im running stock rooted and for some reason my phone SD is saying im full. I have literally nothing on it. Any ideas?
I tried once to install a ROM but it borked so I went back to a backup I had and it was fine.
Via windows it says my SD only has around 8 gigs used but android is saying 24?!?!?!?
WTF MATE?
Try wiping userdata in twrp.
Illogi.xbone said:
Try wiping userdata in twrp.
Click to expand...
Click to collapse
thanks, I was about to try and just redo the device with a ROM. Clear cahces and such.
I was actually wrong, every time I go into the phone in windows its giving me different storage use #'s. One time its 8 then 17 then 23 then 9. its weird. I think when I tried dirty flashing it just screwed it all up. I have nothing on the SD I care about really so maybe Ill just back up what I want (TWRP backup and titanium apps) and start from scratch if I Cant solve this.
That might be the best. Try backing up to an OTG then completely wiping and installing a fresh ROM. After backing up apps and such.
ugh IM having trouble using any roms on my 5x. No matter the way I install the phone always boots to "internal problem with device"
Ive tried installing different roms (I only like stock style ones) and the vendor.zip and it just doesnt work for me. Ive gone back to my backup for the moment until I figure this out. Never had these issues with my nexus 5
this is odd now my pattern no longer work since my restore back to my TWRP backup! GOD DAKNIT!
let me do the start patttern fine for android then when unlocing the phone it tells me "pattern needed to start device"
what the hell man!
tevil said:
this is odd now my pattern no longer work since my restore back to my TWRP backup! GOD DAKNIT!
let me do the start patttern fine for android then when unlocing the phone it tells me "pattern needed to start device"
what the hell man!
Click to expand...
Click to collapse
Try 1st: Completely wipe device, System, data etc. Including Internal Storage and flash a new rom. If that does not fix the issue try flashing stock firmware and start from scratch. Use THIS guide to flash the stock images.
Flash vendor.img that matches your rom base. MMB29Q is the February OTA base. February AOSP roms are based on MMB29U master code but MMB29Q vendor file works fine.
For password issues after TWRP restore, do this: http://forum.xda-developers.com/showthread.php?t=3245070
Sent from my Nexus 5X using Tapatalk
SERIOUS ISSUE!
Bricked the phone!
CRAP, this whole thing went downhill. Can get into TWRP, and get the android crash logo (triangle) was trying to restore back to stock to start fresh and it bombed completely!
Any tips!!!
Been a while since I used ADB or fast etc, but man if I have to relearn I will
Hello,
sorry if this has been mentioned anywhere before, but I wasn't able to find something similar.
So I know why way around with my old Nexus 5 in things backing up the phone with Titanium or TWRP, but since it's wifi module died on me I switchted to the HTC 10, which is kinda intimidating to me when it comes to updating to new OS or backing up. With the NExus 5 it was a walk in the park for me.
First, I don't really understand the concept of S-On and S-Off. Don't know if this is related to my problem, just wanted to mention it.
My HTC 10 is rooted, bootloader unlocked, S-On and runs on 7.0 2.41.401.41.
TWRP is the latest available version.
Before I rooted the phone I made a backup of the stock system image etc like explained in one of those "how to root the htc 10" tutorials (no writing allowed).
To root I had to allow writing onto the system partition of course.
Now, I made an TWRP backup. I backed up everything that was available in TWRP. Userdata, cache, system etc.
Few weeks ago I ran into some problems (I though I did, turned out Google App is just weird) and wanted to restore my TWRP backup.
So I did. Went to TWRP and restored the backup from my SD card.
Got no error messages during the process, but when I wanted to boot up the phone the green HTC boot animation did its thing and then froze at the HTC logo, which would result in a bootloop after ~10 minutes of waiting.
Could force the phone to go into bootloader and from there into TWRP, but that's the best I could do.
Also removed SD and SIM card trays, but that didnt do anything.
Had to factory reset and then do a backup via Titanium backup, which is better than nothing but still a pain in the a** because some things just have to be set up manually, which took me quite a while. I honestly don't want do that again anytime soon
Does anyone have an idea what could went wrong or what I did wrong during the backing up and restoring process?
Except for that, I tried to understand how to update to an upcoming version of the OS when the phone is rooted with S-On and how I could keep my userdata? On the Nexus 5 I just manually installed everything via adb except userdata.img and only had to re-root the phone afterwards. I am afraid this isn't possible with the HTC 10, am I right?
The HTC 10 forces encryption and that has broken TWRP restore for me if I try to switch between ROMs. If I switch ROMs then I have to do a full wipe / format. The one time I tried to go back to my original OS I had a similar issue and I ended up flashing the full RUU to get back to stock.
The only time I am able to restore in TWRP is if I'm returning to the same ROM that I am currently running. Even then I usually just restore the data.
This morning I received the Android 8.1 OTA, it took over an hour to process and when it had finished my tablet had been wiped.
Not happy!
Hi same thing happened to me . I called Google up and they gave me a useless answer.
All I can say to others is do not update to 8.1 just yet or back up your data.
Did you by any chance have your bootloader unlocked?
Bhushan8128 said:
Did you by any chance have your bootloader unlocked?
Click to expand...
Click to collapse
I can't remember, it's possible...
Reset for me, and bootloader is NOT unlocked for either device we have (at least I was the first to take the update, so can plan for my girlfriend). Didn't expect this. Especially after the update to 8.0 left things alone. I had JUST started to install apps with data (long time flasher... left these stock, so I tend to avoid non-cloud apps, especially without root backup options).
Wish I'd come on here half an hour ago. Just got the notification about the update and has wiped mine as well.
Sent from my Pixel 2 using Tapatalk
Same here. Just did the OTA. Basically new tablet, never unlocked the bootloader etc..
Interestingly I could not initialize the tablet as new device.
The error I got was that the device was resetted and only the previous owner can go on with the setup (something like this).
I logged into my Google account and now my Pixel C is loading the backup.
But I highly doubled that many of my apps settings were backuped.
In the same boat. Jumped straight into the OTA when prompted, ended up with factory reset and all internal storage wiped. Stock ROM, only thing possible unusual we that when I first went to install it complained I didn't have free space. Fixed that and tried again, ended up reset and wiped.
with my Pixel C it is looping between "Google" and "erasing" and getting no further
Got the OTA update too and it wiped my device, good thing I just brought it so had nothing on it
Amazingly incompetent - who do they think they are - Apple?!
TimSharrock said:
with my Pixel C it is looping between "Google" and "erasing" and getting no further
Click to expand...
Click to collapse
I tried factory reset, and it seemed to make no difference, but I left it looping for several more hours, and it eventually booted into a wiped state. I reconnected it to my account, and is now merrily reinstalling everything from the backup
I just updated with adb sideload and full OTA Image. No wipe for me.
Apparently this is now fixed, time will tell.
https://productforums.google.com/forum/#!topic/nexus/rwWqnT_397c
Can I restore a nandroid backup made on a different device to a new device? I am getting a new RMA unit soon and I want to restore a nandroid backup made on my old device to the new one. I don't know if it is possible though.
EDIT: I have tried it and it doesn't work. All the data and apps are restored and the device mostly works but Pixel imprint will refuse to add any fingerprints at all.
Look into how this was done on the Nexus 6P - the finger prints and lockscreen stuff would be screwed up, but could be fixed with modifications to certain files. Having said that, I'm not sure if this would trip SafetyNet with the Pixel 2 XL (I was using system root with SuperSU back on the N6P, so I didn't care about SafetyNet.)
Also, I'm not even sure the same fixes would work, but it's worth exploring if need be.
Don't think it's a good idea and could cause problems...
darkfire404 said:
Can I restore a nandroid backup made on a different device to a new device? I am getting a new RMA unit soon and I want to restore a nandroid backup made on my old device to the new one. I don't know if it is possible though.
EDIT: I have tried it and it doesn't work. All the data and apps are restored and the device mostly works but Pixel imprint will refuse to add any fingerprints at all.
Click to expand...
Click to collapse
You can do restores all day long with HTC 7,8,9,10,11's and Nexus 6 among others. But I have failed so many times on OG Pixel and P2-XL.
Haven't given up, but it doesn't look good.
So here's the story. My phone hasn't been updated since April. I was warry because I messed it up that time and lost some data. So I finally get around to updating it again. I updated to Pie stock. It went well. I then installed a custom rom, pixel dust. It went well. I rooted it, no problem, restored some stuff, etc. This happened last night. I couldn't get Always on Display to work, but whatever.
So today, I am uninstalling apps that I no longer want, setting up widgets, etc. I go to attempt to restore some data from Titanium Backup, to avoid having to sign into everything again, see if that works. If not, no big deal. I notice, however, that magisk is gone! Where did it go? It was just there last night!
So I'm like ok, let's just reflash magisk. It's a no go. Now I get bootloops. After being stuck on the pixel dust animation for a bit, it boots into recovery. I don't know what went wrong, the very same magisk was working last night, and can't remember root disappearing out of the blue like that before.
This is all in slot A. My slot B is empty according to TWRP. Not sure how that happened. My i tried to flash the rom, it corrupted while copying to the phone, so I flashed with ADB sideload. That worked fine, but one consequence is that I don't currently have the zip of the rom on the phone. I also did not bring a USB cable to the office with me, didn't expect to need it. So I won't be able to use a USB to transfer a ROM or anything until later today.
Any ideas what happened? Is it possible to fix this soft brick without a USB cable before I go home? Is it possible to fix without losing all the setup I have done so far? Critical data is backed up to Titanium, Google Cloud, and my work Mac. But I would prefer to not need a full wipe if possible. How do you use both slots?
Thank you very much.