Is there away you can change the wallpaper on the start screen section?
In windows RT 8.0 no. In the 8.1 update it can be set to match your desktop background though.
There is a pre release version of 8.1 out, I don't recommend updating unless you are familiar and capable of restoring your device from a recovery USB (8.1 over-writes the built in recovery so it must be a USB recovery). The actual update should be out some point by christmas, I think october is the predicted release.
You can't jailbreak 8.1 either yet, there was a changing of the guards and they swapped the locks.
I just sideloaded KitKat on my Nexus 7 2013 edition 32 GB. Yesterday, however, I received a notification about a second update (KRT16S) so I download the update and proceed to install. As soon as it booted into recovery it gives an error and installation aborts. I then press power+vol.up key to get the reboot option and get back into Android. No other error surfaces at this point except I'm not running the KRT16S version and when i go to check for updates I'm no longer prompted to download anything. I'm rooted with stock recovery and stock Android 4.4 (KRT16O).
I know Google updated the firmware images and I want to make a firmware restoration from the newest firmware image but I haven't found any solid description of the procedure anywhere on the internet so I'm asking if someone could help me.
Edit:
Never mind guys. I finally made it. All I had to do was realize I had do extract the restore image in the "Platform Tools" folder and not anywhere else. Everything is fine now and I'm running KRT16S. Thanks for everyone jumping in to help anyways. Good luck.
Just bought a N7 2013 and I'm afraid it bricks after update and wanted to know if I could avoid it by flashing Marshmallow factory image instead of updating via OTA, skipping lollipop, or if there is any precaution to not brick it...
carpamagica said:
Just bought a N7 2013 and I'm afraid it bricks after update and wanted to know if I could avoid it by flashing Marshmallow factory image instead of updating via OTA, skipping lollipop, or if there is any precaution to not brick it...
Click to expand...
Click to collapse
why would it brick via OTA? almost all N7s are updated that way.
the best precaution for not bricking it is if you follow the instructions that are given for manually flashing factory image, although I don't think it is necessary to do it manually. I did it OTA and it works perfectly normal.
Hard Brick
FWIW,
I've used Ubuntu with the adb utility and if I "bricked" my N7 2013, I found when I got to the bootloader "START"
window, I could simply do the sudo ./Install-all.sh command that comes in the package for the "stock" Android
kernel without any prerequisite commands and the ROM would load.
Of course anything that was on there previously was wiped out but at least I had a new system to start from.
I discovered this when I had my "bricked" device at the START window and the "adb devices" command showed that the N7 2013 was recognized at the USB port. Just went ahead and did the Install-all.sh command and away it went.
I tried to get Android 6 installed, rooted and with MultiROM operating but no dice. When I got to the point of installing MultiROM on Marshmallow, the device would perpetually boot into TWRP, never booting Marshmallow. I ditched it and went back to KitKat 4.4.4 and got it settled and then loaded a Cyanogenmod
snapshot. I'm liking CM more and more.
I'm just a script kiddie that's dinked with Linux since '93 and am by no means an expert. The background has helped when slogging away with my N7 2103 Flo. Kurt
reso91 said:
why would it brick via OTA? almost all N7s are updated that way.
Click to expand...
Click to collapse
Huh... back when Lollipop was released I heard a lot of N7s hard bricked because of the update(5.0.2), causing a motherboard problem, idk, but no one could flash anything, and I thought I could avoid this problem with lollipop skipping it (ex: N7 come with JB and I flash Marshmallow factory image instead of going through KK,LP till MM)
carpamagica said:
Huh... back when Lollipop was released I heard a lot of N7s hard bricked because of the update(5.0.2), causing a motherboard problem, idk, but no one could flash anything, and I thought I could avoid this problem with lollipop skipping it (ex: N7 come with JB and I flash Marshmallow factory image instead of going through KK,LP till MM)
Click to expand...
Click to collapse
Sigh. The issue was widely reported as being caused or exacerbated by the OTA update to the initial release of lollipop. The best way to avoid the issue, if there ever truly was one, is to simply use custom ROMs, or stock rooted ROMs, which can be installed via custom recovery as opposed to through installing the factory image...
One of the nice things about Nexus devices is that Google posts factory images on their site. I generally prefer to use those, rather than OTA updates, as it guarantees a fresh install. I use a variety of other methods to backup/restore data and apps, but I've had pretty good luck doing it that way.
There's a really simple way to not hard brick your N7 with an OTA update:
If your present Android version is working okay, is stable, and does what you want it to do...wait for it...LEAVE IT ALONE!
Seriously. Other than for additional stability and MAYBE security enhancements, stick with what you have. Don't fall for all the hype out there.
The bricking caused by lollipop was due to a bug in the update causing a excessive amount of read/writes to the NAND and caused premature failure of the chip, this has long since been fixed and lollipop is safe for use again.
Sent from my Nexus 7 2013 using Tapatalk
Hey guys. I wanna asj something. I know I'm already late to the part and still very new to the Interop unlocking (and other such unlockings) but I already Interop, Cap unlock and jailbreak my phone. But I'm still being careful and know what I'm doing and the repercussions and consequences of the actions I already did. Now after I did all these things, I haven't updated my phone with the latest Insider build yet (yes I'm on WIP, pretty much like any of us here), now I wanna ask?
Does newer WIP or updates gonna harm/undo all my tweaks, registries, and unlocks? Does after every update, do I need to redo somethings that are reverted by the updates? Could updates harm my phone with all these unlockings and tweaks after it update?
I would love a reply and help. Thanks
Should be fine. I currently have my 640 on latest insider build (15063 ->>) with continuum hack-enabled, dynamic page file scaling and interop unlock functioning normally. The updates didn't break any of them but anything can happen out of nowhere so be careful.
worst case it will revert whatever changes you made, its unlikely you will get in a bootloop or something because of whatever tweaks you made, each major build overwrites the current build after creating a backup of it in the recovery partition, after that it then gets user files and settings from the backup to the new working build, that is when something can go wrong, a previous tweak for example could be asking for a certain file to be used that the new build doesn't have, so after a reboot it shows a BSOD, because of a missing file that it supposed was mission critical
EspHack2 said:
worst case it will revert whatever changes you made, its unlikely you will get in a bootloop or something because of whatever tweaks you made, each major build overwrites the current build after creating a backup of it in the recovery partition, after that it then gets user files and settings from the backup to the new working build, that is when something can go wrong, a previous tweak for example could be asking for a certain file to be used that the new build doesn't have, so after a reboot it shows a BSOD, because of a missing file that it supposed was mission critical
Click to expand...
Click to collapse
Hey thanks for y'all replying. So what could I do? List all the tweaks I've made and unlocks I did? And what should I do when I did get on that situation? Is hard reset is the only way out after that?
PrinceKicksters said:
Hey thanks for y'all replying. So what could I do? List all the tweaks I've made and unlocks I did? And what should I do when I did get on that situation? Is hard reset is the only way out after that?
Click to expand...
Click to collapse
you could wait for people with disposable phones to inform of the situation, chances are they applied all known tweaks and mods so if their phones keep working after RS2 RTM goes to release preview, yours will too
there are things that cant be undone, an example was my 928 that got some files corrupted so I could no longer install-update apps and the registry was locked, as in, not keeping changes after reboots, including interop unlocking so it was a dead end, there's no dism in mobile to fix this, so yea hard reset is the only fix
EspHack2 said:
you could wait for people with disposable phones to inform of the situation, chances are they applied all known tweaks and mods so if their phones keep working after RS2 RTM goes to release preview, yours will too
there are things that cant be undone, an example was my 928 that got some files corrupted so I could no longer install-update apps and the registry was locked, as in, not keeping changes after reboots, including interop unlocking so it was a dead end, there's no dism in mobile to fix this, so yea hard reset is the only fix
Click to expand...
Click to collapse
OMG, I think I'm actually experiencing your 928 issue rn, I'm just only interop unlocked like only for a week rn, and now after had some of tweaking, now I can't update nor install apps from Windows Store, Windows Update also stucked on Initializing too and I can't install latest Fast build, but just today I've noticed that it actually download (I think?) and got passed 50% and still stucked there rn. Can you confirm that we're same on issue? Is hard reset reset really the fix here? How about the WDRT? Is it the same with hard reset?
Also I want to note that my PC too have this issue too, and yea I asked this on MS Answers and they did suggest DISM, but I can't really finished or start properly a DISM with an ISO or ESD. Here's the thread if mind to see it. So what i did is to do a in place upgrade repair, it did work and update apps for like a week, and two, now we're back again and I can't install, update apps from Windows Store, nor Windows Update too. Tho some installs after a very long time, and for only very small apps. I noticed that the netsvcs.exe process from wuaserv (Windows Update service) doesn't respond time to time, and just fades away and end itself even if the downloading isn't finished yet. I still don't know whats wrong with the service nor the Microsoft too. My 830 never experienced this before, updates and downloads are much smoother responsive than on my PC, until now they're on the both state
Also what happened to your 928, you said it does have this issue, why don't you hard reset it?
PrinceKicksters said:
OMG, I think I'm actually experiencing your 928 issue rn, I'm just only interop unlocked like only for a week rn, and now after had some of tweaking, now I can't update nor install apps from Windows Store, Windows Update also stucked on Initializing too and I can't install latest Fast build, but just today I've noticed that it actually download (I think?) and got passed 50% and still stucked there rn. Can you confirm that we're same on issue? Is hard reset reset really the fix here? How about the WDRT? Is it the same with hard reset?
Also I want to note that my PC too have this issue too, and yea I asked this on MS Answers and they did suggest DISM, but I can't really finished or start properly a DISM with an ISO or ESD. Here's the thread if mind to see it. So what i did is to do a in place upgrade repair, it did work and update apps for like a week, and two, now we're back again and I can't install, update apps from Windows Store, nor Windows Update too. Tho some installs after a very long time, and for only very small apps. I noticed that the netsvcs.exe process from wuaserv (Windows Update service) doesn't respond time to time, and just fades away and end itself even if the downloading isn't finished yet. I still don't know whats wrong with the service nor the Microsoft too. My 830 never experienced this before, updates and downloads are much smoother responsive than on my PC, until now they're on the both state
Also what happened to your 928, you said it does have this issue, why don't you hard reset it?
Click to expand...
Click to collapse
I did hard reset it after all, its just that I dont use it too often nowadays
in your case if you can still make registry changes and they dont revert after a reboot, then its not the same issue, I see you're downloading from cellular, maybe it has something to do with that
hard reset and WDRT is almost the same thing, WDRT just flashes the rom essentially making a clean install, like reformatting a disk and installing windows on pc, hard reset does that but it installs from a recovery partition and it contains a "fresh" image of the last OS installed, so it can contain bugs acquired from the last working state, its just very unlikely anyway
just make sure everything is backed up and do a hard reset, then login to your account while setting it up and it will show a list of the backups, get the latest one you made and it will be back where you left it(almost)
Per the title I tried to go to A13 to see if it would fix the low ringer volume on my Unlocked Pixel 6 Pro, or whether I have a hardware issue. It did not. I decided to go back to A12 and wait until the stable release and trying to flash via adb tells me I can't downgrade. When I try the Android Flash Tool and select the A12 build I need, it starts and then shows a "HEAD request failed: Unknown network error" and stops.
I'm soft-bricked now. I get a message that the device is corrupt and may not work properly, then the bootloader unlocked warning I've always gotten after I unlocked that. After that I At best I get to a white screen with the Google logo or bootloader mode.
Has anyone worked through this error or does anyone have a solution on how to recover my phone? Thanks!
Reflash A13 and make a backup then flash - wipe A12
Paz9 said:
Reflash A13 and make a backup then flash - wipe A12
Click to expand...
Click to collapse
Thanks - that's exactly what I did. I was traveling and trying to get my phone working again and you are on the right track. I got it fixed fairly quickly, but I left the thread open to give another instance of hope to folks who may stumble across this in the future. I'm guessing I was flashing the OTA image and not the factory image, and it was confusing because it would partially succeed and then fail with no obvious indication of the reason for the failure. I've since flashed the factory image several times and while it too has the .sig files missing errors that appears to be a non-issue, it works just fine and I'm back in business.
It may be related to what we seen today with A13 being released. The Bootloader cant be rolled back to earlier version.
Someone posted today they can get Android 12 installed back, AS LONG as they edit the factory image script to skip the bootloader flash part.
chaco81 said:
It may be related to what we seen today with A13 being released. The Bootloader cant be rolled back to earlier version.
Someone posted today they can get Android 12 installed back, AS LONG as they edit the factory image script to skip the bootloader flash part.
Click to expand...
Click to collapse
It's not, he was on the Android 13 beta and was trying to flash the full OTA when the recovery does not permit flashing a lower firmware than what is already running. He only had to instead flash the firmware from the bootloader to downgrade from the beta.
However yes, if you take the Android 13 release bootloader you cannot downgrade back to Android 12's bootloader. How long the Android 13 bootloader will continue to boot Android 12 or if they will put another antirollback measure in is unknown.