Related
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)
As there is no official Surface RT image inc 8.1 update 3 final image to download, is there anyone who has been successful in updating so far willing to upload a current working latest recovery image to allow other users who continue to struggle with the forever "Checking for updates" message just to bring their Surface RT up to the current spec. This is really poor from Microsoft so long after the update, had this been Apple or Samsung an updated recovery image would have been updated at the same time so all users could re-flash to the current system update if req. The windows update process has many flaws so why not update the latest image at least so to avoid drip-fed downloads that often seem to fail for one reason or another ?
Couldn't agree more. Although this has been an issue for a while. It would seem the issue is now worse. I think some recent update or removal of a critical update is locking the old RTs into the first 8.1 Update. I have tried all the tricks, and I can't get any of them to work. Hoping a sideload of Win10S happens soon.
I just got a pixel 3 xl 128 GB, but it's in Android 11 beta version.
I would like to flash back to android 10, is it any of instruction please? Thank you.
Gnahznuy said:
I just got a pixel 3 xl 128 GB, but it's in Android 11 beta version.
I would like to flash back to android 10, is it any of instruction please? Thank you.
Click to expand...
Click to collapse
you can also flash the factory image again, assuming you can unlock your bootloader and have another phone or PC with the adb & fastboot tools and any drivers (if using win10, linux hasn't needed any in my experience) installed and working correctly.
make a backup like the other guy said. I know when flashing the factory image files, if you open the flash-all.sh or flash-all.bat files in a text editor, you can remove the "-w" on the bottom line of the script and it won't erase your data. But as the other poster said, maybe that won't work if you're going back a version. I've not experienced that with flashing images, I've only run into issues like that when installing OTAs from adb. Flashing seems to let you get around that.
good luck
From the Google page: First, make sure you are running a beta version of Android. View devices to find the device you want to remove and click Opt out. Your device will receive an update within 24 hours that will wipe all user data and install the latest stable public version of Android. You will not be able to unenroll and revert back to a lower public release version of Android without first wiping all locally saved data on your device. You may also encounter issues restoring a backup.
https://www.google.com/android/beta#faq
As the title says. I've seen some older posts from 2019 about it not working, and need to know its status as of right now. I checked their website, and it provides a guide for this specific model, but it doesn't work. What else can I use?
Twrp has not worked on our phones since Android 9. So no it does not work on 10 or on 11
Tom Dude said:
As the title says. I've seen some older posts from 2019 about it not working, and need to know its status as of right now. I checked their website, and it provides a guide for this specific model, but it doesn't work. What else can I use?
Click to expand...
Click to collapse
According to the TWRP website their latest release 3.5 does work on Android 10 and they are working to get it usable on Android 11
Unfortunately our device tree is outdated; there is no android 10 branch let alone 11. The latest release for our device is for those still on android 9, as denoted by TeamWin's new naming convention. If a new branch for 10 and/or 11 can be added to Github, maybe we'll see a build that works for those that have moved on from pie.
GitHub - TeamWin/android_device_google_bonito
Contribute to TeamWin/android_device_google_bonito development by creating an account on GitHub.
github.com
41rw4lk said:
Unfortunately our device tree is outdated; there is no android 10 branch let alone 11. The latest release for our device is for those still on android 9, as denoted by TeamWin's new naming convention. If a new branch for 10 and/or 11 can be added to Github, maybe we'll see a build that works for those that have moved on from pie.
GitHub - TeamWin/android_device_google_bonito
Contribute to TeamWin/android_device_google_bonito development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
so what does this mean?
i just got a brand new 3a XL
i updated it to 11 and now the phone has so many issues that it is not even useable for me anymore, i need to go back to 9 or flash a custom ROM
so can i downgrade it to pie or dirty flash a stock pie rom and then install TWRP on it and flash a custom rom?
or am i now stuck on a 11 with no way to flash to an older stock rom or custom rom or install TWRP?
also if you install TWRP on 9 then i assume you can still flash a stock 10 or 11 rom and revert back to 9 right
gdroid666 said:
so what does this mean?
i just got a brand new 3a XL
i updated it to 11 and now the phone has so many issues that it is not even useable for me anymore, i need to go back to 9 or flash a custom ROM
so can i downgrade it to pie or dirty flash a stock pie rom and then install TWRP on it and flash a custom rom?
or am i now stuck on a 11 with no way to flash to an older stock rom or custom rom or install TWRP?
also if you install TWRP on 9 then i assume you can still flash a stock 10 or 11 rom and revert back to 9 right
Click to expand...
Click to collapse
i see you quoted my post but it is blank
also i am having major problems navigating this new site now , it logs me out whenever i do anything or move between pages and then i can no longer log in it gives an error " Security error occurred. Please press back, refresh the page, and try again. "
on chrome
First you might want to post what issues you are having in 11 as really there have not been many postings about issues on 11 at all.
That said to answer your question:
Android 9 is very old and of course no longer being updated. I cannot even think of a custom rom that is still based on android 9, but if your dead set on going back to 9 and being a huge security risk you need to download the last android 9 full from from google factory images and run the flash-all file either vat or sh depending on what os your on, This will completely wipe your phone.
If you want to try a custom rom there are very few that are actively updated. The only one I can think of that I KNOW is updadated and current is LOS. Unfortunately while it works really well there is absoluetly no support at all for it on our phone. Not even a dedicated xda thread for it. I wqas on it for a while but ran into an issue with dialing 911. Not sure if it was an LOS issue or not but immediately went bqck to stock with custom kernel after that and have been that way ever since.
To summarize:
Android 9 is basically dead and outdated.
Android 10 lives on only in the very few custom roms available
Android 11 at least for me is at least as stable and usable as 9 or 10 was
TWRP is likely never going to return to our phone and honestly really isnt needed anymore. Really the only thing we cannot do anymore is flash something directly from our phone. Without TWRP you must now flash all images and kernels and such from a pc.
Yeah this site is not quite ready for prime time yet. I also have constant issues with it. Hopefully the reply goes through this time
gdroid666 said:
so what does this mean?
i just got a brand new 3a XL
i updated it to 11 and now the phone has so many issues that it is not even useable for me anymore, i need to go back to 9 or flash a custom ROM
so can i downgrade it to pie or dirty flash a stock pie rom and then install TWRP on it and flash a custom rom?
or am i now stuck on a 11 with no way to flash to an older stock rom or custom rom or install TWRP?
also if you install TWRP on 9 then i assume you can still flash a stock 10 or 11 rom and revert back to 9 right
Click to expand...
Click to collapse
Haven't seen a reply
gdroid666 said:
i see you quoted my post but it is blank
also i am having major problems navigating this new site now , it logs me out whenever i do anything or move between pages and then i can no longer log in it gives an error " Security error occurred. Please press back, refresh the page, and try again. "
on chrome
Click to expand...
Click to collapse
Did you see the reply this time?
adm1jtg said:
Haven't seen a reply
Did you see the reply this time?
Click to expand...
Click to collapse
yes i can see it
the problems i have are
1)using assistant via "hey Google" does not respond to what i say, instead it brings up a menu of suggestions , and i have to repeat myself
or sometimes it won't work at all just says can't reach google try again later
2) smart lock trusted device does not work it constantly relocks my phone after minutes no matter what trusted bluetooth devices are paired , not only annoying but dangerously distracting while driving"
3) problems with android auto and android auto with assistant ,
4) bug where pressing the volume rocker to adjust media or ringer volume (in either direction) causes all sound, media or ringer to just stop
5)problems with the accessing the phone screen while in a call
when i pull the phone from my ear and go to use the screen when in a call the screen goes off and is not responsive to touch then it goes on for a split second , then off, then on, then off , then on
seems like the software service that controls the (light?) sensor that detects if the phone is being held to your ear is not working right, i had issues with this on my nexus 6p too though but it had a different sort of behavior , it would just be black and unresponsive and i had to press the power button to wake the screen again, and i had to stop using power button ends call cause it would end the call whenever i needed to use my screen while in a call and the glitch happened and kept the screen from waking when i pulled away from my ear
6) sometimes get glitches with the app switcher/recents
sometimes the "pill" gesture does not respond and i can not bring it up at all,
and the animations are all glitched out too nearly all the time
animations are a mess jumpy, glitchy ,shaky
it's going to give someone a seizure
7) no visual VM tab in the stock phone dialer app
this was working on 9 on another 3aXL ut stopped after update to 10 ,same carrier but this had been a problem on the nexus 6p too
off /on issue , mostly off
8) texting photos to IOS devices does not go through now
i thought it said you could install TWRP on the 3a XL if you were on Android 9
so what i was asking is, what happens if you dirty flash a stock Android 9 ROM? then would i be able to install TWRP from there
or i can not do it now since i updated it to 11?
I am just curious if it can be done, I will probably just take your advice and stay on 11 for now though and hope there is aoe improvements in android 12 developer preview
i am not at all hopeful though
and after testing my old phone some of the same assistant and auto bugs are on those devices too so i guess it is just issues with assistant that cropped up the same ties i updated
gdroid666 said:
yes i can see it
the problems i have are
1)using assistant via "hey Google" does not respond to what i say, instead it brings up a menu of suggestions , and i have to repeat myself
or sometimes it won't work at all just says can't reach google try again later
Cant comment on this as I dont use assistant
2) smart lock trusted device does not work it constantly relocks my phone after minutes no matter what trusted bluetooth devices are paired , not only annoying but dangerously distracting while driving"
Dont use smartlock either
3) problems with android auto and android auto with assistant ,
Dont use android auto either
4) bug where pressing the volume rocker to adjust media or ringer volume (in either direction) causes all sound, media or ringer to just stop
Never had this happen and had this phone on both stock 10 and 11 and also on LOS 17.1
5)problems with the accessing the phone screen while in a call
when i pull the phone from my ear and go to use the screen when in a call the screen goes off and is not responsive to touch then it goes on for a split second , then off, then on, then off , then on
seems like the software service that controls the (light?) sensor that detects if the phone is being held to your ear is not working right, i had issues with this on my nexus 6p too though but it had a different sort of behavior , it would just be black and unresponsive and i had to press the power button to wake the screen again, and i had to stop using power button ends call cause it would end the call whenever i needed to use my screen while in a call and the glitch happened and kept the screen from waking when i pulled away from my ear
Never had this happen with any of the above roms either
Could your tempered glass somehow be blocking the sensor as I have heard of symptoms like that being caused by one.
6) sometimes get glitches with the app switcher/recents
sometimes the "pill" gesture does not respond and i can not bring it up at all,
and the animations are all glitched out too nearly all the time
animations are a mess jumpy, glitchy ,shaky
it's going to give someone a seizure
Not helpful I know but also never seen this occur in all my time using many android phones
7) no visual VM tab in the stock phone dialer app
this was working on 9 on another 3aXL ut stopped after update to 10 ,same carrier but this had been a problem on the nexus 6p too
off /on issue , mostly off
Only seen this when your not using the correct/default stock phone apk
8) texting photos to IOS devices does not go through now
I text stuff to iphones all the time, could be a carrier or apn issue
i thought it said you could install TWRP on the 3a XL if you were on Android 9
I was never on android 9 on this phone but I believe thats correct. However you would lose all security updates for well over a year and a half or so. I BELIEVE the last android 9 rom update was aug 2019
so what i was asking is, what happens if you dirty flash a stock Android 9 ROM? then would i be able to install TWRP from there
or i can not do it now since i updated it to 11?
You could go back but it would not be advised and since twrp shares the boot partition as soon as you flashed any rom greater the android 9 you would lose twrp.
I am just curious if it can be done, I will probably just take your advice and stay on 11 for now though and hope there is aoe improvements in android 12 developer preview
i am not at all hopeful though
and after testing my old phone some of the same assistant and auto bugs are on those devices too so i guess it is just issues with assistant that cropped up the same ties i updated
Click to expand...
Click to collapse
ugh I really am not liking this new forum format. I answered each of your line items under each number but it really isnt showing up very well.
Sorry it has taken so long to respond but i wanted to give a complete answer. Given all the issues you are having and that in my personal opinion going back to 9 really isnt a good idea I would recommend giving los 17.1 a try. It will NOT get you twrp but it is based on android 10, and updated weekly. The only downside to LOS 17.1 is that there is literally no support at all. Even the responsibvle dm's I dont believe even own our phone. That said it ran perfactly for me except a wierd 911 issue that may or may not have been due to LOS. I am seriously thinking of going back to LOS myself, am just really lazy as I would have to redo my entire phone and start with a clean android 10 stock flash.
When you have backup religion: 'tWRp IsNt NEedEd ANyMoRE'
Yet nobody can answer OP's question.
ssurell said:
When you have backup religion: 'tWRp IsNt NEedEd ANyMoRE'
Yet nobody can answer OP's question.
Click to expand...
Click to collapse
There is no alternative for our device running 10 or 11. If we had a device tree newer than 9 we could probably get an auto build from teamwin, but as of now there is none.
As for backing up, most things are backed up using cloud services, not to mention twrp isn't so elegant on a/b devices. You have to reinstall after updates, it can interfere with built in updaters, and restoring backups on a/b devices seem to cause more problems that anything.
41rw4lk said:
There is no alternative for our device running 10 or 11. If we had a device tree newer than 9 we could probably get an auto build from teamwin, but as of now there is none.
As for backing up, most things are backed up using cloud services, not to mention twrp isn't so elegant on a/b devices. You have to reinstall after updates, it can interfere with built in updaters, and restoring backups on a/b devices seem to cause more problems that anything.
Click to expand...
Click to collapse
An often repeated mantra it seems that has little to do with creating and restoring partition images. Where I might agree is the lack of need for an elaborate gui to perform update and flash procedures. Seems LOS recovery could fit a dd function into the recovery partition. But lack of user control over boot slot after a crap system update is all the code politics I need to know. No wonder DU folded up.
I have a working TWRP for Android 11.
Captain_Throwback said:
I have a working TWRP for Android 11.
Click to expand...
Click to collapse
Well throw us a link and give any disclaimers you may have about us using it lol
adm1jtg said:
Well throw us a link and give any disclaimers you may have about us using it lol
Click to expand...
Click to collapse
I posted it in the Telegram group here: https://t.me/pixel3a/161825