Related
I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
B1G7r33! said:
I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
Click to expand...
Click to collapse
What's the REAL difference between what you did today and what we did days ago.? Is the same thing we came up with 3 days ago.. Just your version of the same thing..
Three days ago?
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
B1G7r33! said:
Three days ago?
Click to expand...
Click to collapse
actually starting on 14th November 2018, 07:17 PM and ending about 4 days ago.. with ptballers solution.
post 118 was the beginnings of it on the thread: https://forum.xda-developers.com/ga...10-02-2018-t3747564/post78159074#post78159074
but even THAT came from earlier works that weren't detailed enough and reconstructed.
the builds seem to be way different here in the solution, i had luck with what we came up with but have only done that once so far.
I am using build NMF26X.T380DXU1ARB3 myself, what about you?
we need to figure out what ptballer is using and everyone else too as we confirm stuff so we know what to do with tablets based upon builds.
seems there is no single solution yet, and that's what we really need too keep confusion cut down to a minimum.
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
Evul1 said:
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
Click to expand...
Click to collapse
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
capriorn1971ad said:
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Click to expand...
Click to collapse
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Evul1 said:
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Click to expand...
Click to collapse
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
B1G7r33! said:
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
Click to expand...
Click to collapse
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
capriorn1971ad said:
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
Click to expand...
Click to collapse
It shouldn't be that much work at all if your method to get OEM Unlock to display actually works, as your bootloader will then be unlocked and you can immediately re-root, re-flash TWRP, and restore a nandroid backup. Rooting this tablet [flashing TWRP and su and/or magisk and/or a nandroid image] is actually quite simple and can be done in 5 minutes once you have OEM Unlock displayed.
You certainly wouldn't need a whole day just to try this. But I understand. Samsung's security nonsense makes the initial root of this tablet rather fragile if you don't know all the potential roadblocks beforehand. And a comprehensive root guide that explains all of this would certainly help people looking to root this tablet, so I don't want to rush you.
capriorn1971ad said:
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
Click to expand...
Click to collapse
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
B1G7r33! said:
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
Click to expand...
Click to collapse
don't think we can really.
trial and error..
thought i was on the right path earlier, but if it didn't work for you then it isn't the solution, cause the solution will work for everyone.
has to be some small thing were overlooking i would assume.
I worked for Metricom through Verso Technologies back in the late 90's, the first coast to coast wireless provider, had dealings with the big wigs and all, but they always opted for less security and more accessibility in most everything pertaining to networking, always afraid to give up backdoors.
i need to go back to what you said too and see what slight differences there are, did you have any luck this time around? was it repeatable?
sucks to know i am going to have to root to cause a failure to try to bypass and root again only to cause a second failure to verify, and to get it right it is going to take that really, the bypass has to be repeatable, i think setting the date back before the systems restore is key to it, but i could be wrong.
if you would lose root and be able to get it pass the first 7 days OEM unlock then your good, because even if you can't get the second, and something goes wrong to where you need it, your gonna have to wipe anyways, which means you just wipe, set date back and then do the factory reset, not being able to reboot afterwards until the OEM unlock appears and not being able to advance it through the last 7 days means little so long as the root is good and right, funny thing really, took me a while to realize that, there is no real need to rush the second 7 days, only the first 7, but it would be nice to be able to reboot it again afterwards, the same day, and not have to worry about it anymore, but like i said earlier, i got detected somehow and lost root still., wish i knew how.
that's alot of my problem though, i do things and try to document them afterwards rather than as, and i am not 20 years old anymore with a mind like a razor, it's just a serrated steak knife now at almost 50, wish i wasn't like that, because i lose bits and pieces as i go.
so if my tablet auto updates to Oreo 8.1 ... then i'm SOL huh?
tldr; the thing with the oven appears to have worked, although you'd have to be stupid, desperate, or both to try it.
Much loved Galaxy Note 4 SM-N910F started to fail with freezes, reboots and so on. Looks like a phone dying of eMMC failure, according to the bulk of articles on the specific symptoms.
Happily, I'd replaced it (with a Note 10 - lovely phone, but not as revolutionary-lovely as the Note 4 was when it was new), and had had six years of happy use out of the thing. I could bin it with my head held high.
Might have a go at recovering it, though.
Attempts to factory reset failed, resulting in boot to download mode "Firmware Update Encountered An Issue" scary screen... I see. This could be a fun challenge before I bin it then!
Odin flash of Stock ROM fell over repeatedly with various fails - often with 'mmc read' and 'could not do normal boot' scary screens
Various versions and vintages of Odin all produced similar results
Un-brick seemed to work, in as much as I could then flash TWRP (https://forum.xda-developers.com/note-4/help/samsung-galaxy-note4-sm-n910f-unbrick-t3552826)
TWRP flashing of any rom seemed to fail and fall over - generally 5-10% (guess) into the process.
Now getting bolder, tried re-partitioning, various PIT files, NAND erase, and all the forbidden things. The errors kept coming, and my 'unbrick' microSD was earning its keep.
The thing is, I really liked this phone - and I wanted it to try newer ROMs on and so forth, so I resisted the urge to chuck it in the bin. That, and finding things like using TWRP terminal mode to re-format /system and /data in different partition types, and then back to ext4, seemed to improve matters - if only temporarily - all suggested that there might be life in the old girl yet.
A couple of my searches came across articles like this and this, that suggested that the issue might have to do with failing solder joints rather than the eMMC itself and ... well then they talked about putting your phone in the oven, and I dismissed them as madness.
I mean, if putting your phone in the oven would 'reflow' dodgy solder, it would re-flow ALL the solder in the phone, right? Makes no sense. Bloody stupid.
Not going to fall for some obvious troll hoax.
So I put my phone in a 100 deg C oven for 5 mins. Took it out, and let it cool to room temperature slowly over a couple of hours.
Now
Odin can flash a whole stock ROM with success
TWRP can flash a whole non-stock ROM with success
Odin can re-flash a whole stoc... oh. Failed at around 80%. Poo.
TWRP managed a reflash, though!
Odin managed a whole stock reflash, again!
Setting up the flashed phone, though, results in freezes and boot loops. Damnit.
Another day of frustrated mucking about, hovering the thing over the bin.
OK, one more go. This time 120 deg C for 6 minutes.
This time
First and every subsequent re-flash, in Odin and TWRP, works fine.
Odin'd it back to stock, then wipe and factory reset. All fine.
Reconfig process passes without incident.
Google Play updating itself and ALL THE APPS works fine.
Setting up accounts, streaming Youtube for hours, playing games... all fine. Much more stable than it'd been in a while.
It's been a week, now, without incident.
So I thought I'd mention it.
But I still think you'd need to be an idiot to bake your phone in the hope that it'd do *anything* other than make things much worse, right?
charleshking said:
But I still think you'd need to be an idiot to bake your phone in the hope that it'd do *anything* other than make things much worse, right?
Click to expand...
Click to collapse
Maybe.
There's an app called Wake Lock - PowerManager - I've installed on my son's 910F since a month or so and the phone still works.
It'll slightly take it's toll on battery, but hey you save some $ for the next phone.
@charleshking: Reflowing def does work, I know a guy that had to do it 3 times within 6 months to fix his gaming laptop. But it's only meant to be a temp fix, sooner or later the oven thing won't work (failed on him after the 4th try).
The Wake Lock manager app just holds open a wake lock so the phone never enters deep sleep/doze mode, which in the case of an EMMC failing phone can cause it to not wake up.
Last year I had a Note 4 T-Mobile N910T which had a failing EMMC, it had most of the issues you mentioned. But eventually it died, it caught on fire while I was charging it. I now have an N910T which is working with no issues, bought new on eBay almost a year ago.
A few days ago, I was trying to launch an app from my phone's home screen when it suddenly rebooted itself and downloaded/installed an OTA update, removing root in the process. So it looks like Google just force-restarted it and updated it without my consent!
Or, if not that, then I truly must have the worst luck imaginable - like astronomically, unbelievably bad; so bad it could be legendary - almost as if I were cursed by some mythical, malevolent creature with magical powers.
For what I'm about to assume might have happened to be what actually happened, the odds are probably astronomically against it occurring, or nearing the realm of quantum impossibility (or, at the very least, it would be extremely-improbable and highly-unlikely, statistically speaking).
There have been a handful of times (3-5, but I haven't kept count) in the few months I've had this phone that, after unlocking the screen, I see a window drawn over my phone's home screen: a notification dialog with info about downloading/installing a security update for the OS. At the bottom of the window I recall there being two buttons: one to confirm, reboot my phone, and download/install the update, and the other to postpone the update until some later time at night.
Since there was no button for the polite, socially-acceptable equivalent to responding, "NO, **** YOU! STOP ANNOYING ME WITH THIS PROMPT TO UPDATE! I NEVER WANT TO DOWNLOAD AND INSTALL AN UPDATE, OR SEE THIS POP UP EVER AGAIN!", I've just used the "back" button on my phone to dismiss this notification/prompt rather than accepting one of the two equally-unacceptable choices it offered me and being forced into downloading and updating my phone.
So, in theory, it's possible that, at the same exact moment as my phone's screen refreshed to draw this update notification/prompt again, I just happened to also click in exactly the wrong place - the place where that dreaded "reboot" button was drawn - thereby selecting the option to immediately reboot my phone, downloading and installing the update in the process. It would've had to have happened so quickly - literally, within the same 1/90th of a second - that the screen was drawn so that I didn't even see the notification appear before clicking the option to accept and reboot/install the update immediately.
1/90th of a second: that's just a hair over 11 milliseconds, or a hundredth of a second. And I just happened to click in exactly the wrong spot at exactly that moment?
Utterly, unimaginably, and even ridiculously bad luck if this is what actually happened. But aside from Google simply forcing a reboot/update remotely while I was using my phone, it's the only other thing I can think of that might've caused this.
Whoever programmed this functionality should at the very least be publicly shamed and insulted for it, but possibly also dragged out of their bed in the middle of the night into the street and beaten mercilessly. I don't know the law well enough to be aware of the name of the crime for such a thing (annoying millions of people with this almost-unavoidable and heinously-obnoxious nag to update their phone's OS, and causing maybe thousands of them to suffer some sort of financial loss, pain & suffering, or tragic inconvenience by accidentally accepting and applying the update - especially if they happened to be on a limited mobile data plan, or were roaming at the time). However, I'm fairly certain that most people who have experienced something like what I've been through and am forced to deal with now as a result of an OTA update being applied against their will would be fine with either or both of these things being administered as the just and appropriate form of punishment for such a crime.
So, all that being said, what are my odds that I'll be able to not only restore root to my phone without wiping it and losing all the sensitive data I had saved with root access but hadn't had the time to back up yet during one of the most difficult and tragic weeks of my life (I can't even begin to explain all of the other **** that has gone horribly wrong recently), but to also recover compensation for the cost of exceeding my data plan while visiting another country due to the update being downloaded at an EXTREMELY inopportune time? My guess: probably worse than the odds of accidentally clicking to accept and immediately download and apply an OS update within the same ≈11 milliseconds the nag for it was drawn on my phone's screen while also in the middle of giving a presentation in a super-important, multinational business meeting.
But hey, I figured I would share this post here anyway in the hopes of maybe learning that Google force-pushed an OTA update and pissed off millions of people who then filed a class action lawsuit because of it, and I just hadn't heard the news about it yet, but it was also recent enough that I could still get in on that action and recover at least some part of what I've lost in the past week.
And if not that, maybe I'll at least somehow get confirmation of having some of the worst luck imaginable, or validation that I'm not crazy, or just some sympathy and comfort from the community during a very dark time in my life when I sorely need it.
And I guess if there's even a modicum of hope I'll discover that I'm not completely alone in this world of **** that I now find myself in, and that there are others who have suffered a similar fate or misfortune as a result of either unbelievably bad luck with their phone, or Google forcibly cramming something very large and uncomfortable into an extremely sensitive area against their will - maybe even at one of the worst possible times of their life - then maybe there's even some hope left for my life; some point to even continuing it and trying to get out of the horribly-****ty, godforsaken nightmare I'm stuck in right now.
Or maybe I'll just learn that it is actually somehow possible to restore root to my phone without needing to wipe it first so I'm at least not quite as completely screwed as it looks like I am right now.
≈-∞
Google Pixel 5, OS 11
rooted with Magisk, no TWRP/recovery
recently forcibly OTA-updated to build RQ1A.201205.011
Disable updates permanently. I'm more concerned with the damage updates will do than malware at this point
leveleyed said:
A few days ago, I was trying to launch an app from my phone's home screen when it suddenly rebooted itself and downloaded/installed an OTA update, removing root in the process. So it looks like Google just force-restarted it and updated it without my consent!
Or, if not that, then I truly must have the worst luck imaginable - like astronomically, unbelievably bad; so bad it could be legendary - almost as if I were cursed by some mythical, malevolent creature with magical powers.
For what I'm about to assume might have happened to be what actually happened, the odds are probably astronomically against it occurring, or nearing the realm of quantum impossibility (or, at the very least, it would be extremely-improbable and highly-unlikely, statistically speaking).
There have been a handful of times (3-5, but I haven't kept count) in the few months I've had this phone that, after unlocking the screen, I see a window drawn over my phone's home screen: a notification dialog with info about downloading/installing a security update for the OS. At the bottom of the window I recall there being two buttons: one to confirm, reboot my phone, and download/install the update, and the other to postpone the update until some later time at night.
Since there was no button for the polite, socially-acceptable equivalent to responding, "NO, **** YOU! STOP ANNOYING ME WITH THIS PROMPT TO UPDATE! I NEVER WANT TO DOWNLOAD AND INSTALL AN UPDATE, OR SEE THIS POP UP EVER AGAIN!", I've just used the "back" button on my phone to dismiss this notification/prompt rather than accepting one of the two equally-unacceptable choices it offered me and being forced into downloading and updating my phone.
So, in theory, it's possible that, at the same exact moment as my phone's screen refreshed to draw this update notification/prompt again, I just happened to also click in exactly the wrong place - the place where that dreaded "reboot" button was drawn - thereby selecting the option to immediately reboot my phone, downloading and installing the update in the process. It would've had to have happened so quickly - literally, within the same 1/90th of a second - that the screen was drawn so that I didn't even see the notification appear before clicking the option to accept and reboot/install the update immediately.
1/90th of a second: that's just a hair over 11 milliseconds, or a hundredth of a second. And I just happened to click in exactly the wrong spot at exactly that moment?
Utterly, unimaginably, and even ridiculously bad luck if this is what actually happened. But aside from Google simply forcing a reboot/update remotely while I was using my phone, it's the only other thing I can think of that might've caused this.
Whoever programmed this functionality should at the very least be publicly shamed and insulted for it, but possibly also dragged out of their bed in the middle of the night into the street and beaten mercilessly. I don't know the law well enough to be aware of the name of the crime for such a thing (annoying millions of people with this almost-unavoidable and heinously-obnoxious nag to update their phone's OS, and causing maybe thousands of them to suffer some sort of financial loss, pain & suffering, or tragic inconvenience by accidentally accepting and applying the update - especially if they happened to be on a limited mobile data plan, or were roaming at the time). However, I'm fairly certain that most people who have experienced something like what I've been through and am forced to deal with now as a result of an OTA update being applied against their will would be fine with either or both of these things being administered as the just and appropriate form of punishment for such a crime.
So, all that being said, what are my odds that I'll be able to not only restore root to my phone without wiping it and losing all the sensitive data I had saved with root access but hadn't had the time to back up yet during one of the most difficult and tragic weeks of my life (I can't even begin to explain all of the other **** that has gone horribly wrong recently), but to also recover compensation for the cost of exceeding my data plan while visiting another country due to the update being downloaded at an EXTREMELY inopportune time? My guess: probably worse than the odds of accidentally clicking to accept and immediately download and apply an OS update within the same ≈11 milliseconds the nag for it was drawn on my phone's screen while also in the middle of giving a presentation in a super-important, multinational business meeting.
But hey, I figured I would share this post here anyway in the hopes of maybe learning that Google force-pushed an OTA update and pissed off millions of people who then filed a class action lawsuit because of it, and I just hadn't heard the news about it yet, but it was also recent enough that I could still get in on that action and recover at least some part of what I've lost in the past week.
And if not that, maybe I'll at least somehow get confirmation of having some of the worst luck imaginable, or validation that I'm not crazy, or just some sympathy and comfort from the community during a very dark time in my life when I sorely need it.
And I guess if there's even a modicum of hope I'll discover that I'm not completely alone in this world of **** that I now find myself in, and that there are others who have suffered a similar fate or misfortune as a result of either unbelievably bad luck with their phone, or Google forcibly cramming something very large and uncomfortable into an extremely sensitive area against their will - maybe even at one of the worst possible times of their life - then maybe there's even some hope left for my life; some point to even continuing it and trying to get out of the horribly-****ty, godforsaken nightmare I'm stuck in right now.
Or maybe I'll just learn that it is actually somehow possible to restore root to my phone without needing to wipe it first so I'm at least not quite as completely screwed as it looks like I am right now.
≈-∞
Google Pixel 5, OS 11
rooted with Magisk, no TWRP/recovery
recently forcibly OTA-updated to build RQ1A.201205.011
Click to expand...
Click to collapse
yes, automatic system updates are turned off. it's the first thing i do when i set up a new phone. so like i said, either Google still forced an update on my phone - despite having the automatic update setting turned off - or i have unbelievably impeccable timing on top of horribly bad luck.
Still hoping someone might have a solution that would allow me to restore root without wiping my device/data. please oh please oh please let there be some way to do this.
leveleyed said:
Still hoping someone might have a solution that would allow me to restore root without wiping my device/data. please oh please oh please let there be some way to do this.
Click to expand...
Click to collapse
This is a simple solution and has been discussed before.
Get the boot.img for your current build
Copy it to the phone and patch it with Magisk Manager
Fastboot flash the resulting patched image
Accidentally OTA updated my pixel, all fine but root gone
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted. Of course my root is gone now, but i want to root it again. Bootloader is...
forum.xda-developers.com
UPDATING Pixel 5 Factory Image & Re-Rooting
Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...
forum.xda-developers.com
l7777 said:
This is a simple solution and has been discussed before.
Get the boot.img for your current build
Copy it to the phone and patch it with Magisk Manager
Fastboot flash the resulting patched image
Accidentally OTA updated my pixel, all fine but root gone
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted. Of course my root is gone now, but i want to root it again. Bootloader is...
forum.xda-developers.com
UPDATING Pixel 5 Factory Image & Re-Rooting
Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks! Sorry for asking something that already had an answer. I guess I wasn't searching for the info properly.
I'm still having a problem though. I got the boot.img for the new version on my device. But when trying to launch Magisk manager, I see a window that says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing that same thing.
leveleyed said:
Thanks! Sorry for asking something that already had an answer. I guess I wasn't searching for the info properly.
I'm still having a problem though. I got the boot.img for the new version on my device. But when trying to launch Magisk manager, I see a window that says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing that same thing.
Click to expand...
Click to collapse
Try downloading magisk directly and installing. Or are if it already downloaded it and install that one.
leveleyed said:
yes, automatic system updates are turned off. it's the first thing i do when i set up a new phone. so like i said, either Google still forced an update on my phone - despite having the automatic update settingl turned off - or i have unbelievably impeccable timing on top of horribly bad luck.
Still hoping someone might have a solution that would allow me to restore root without wiping my device/data. please oh please oh please let there be some way to do this.
Click to expand...
Click to collapse
I'm sorry this happened to you.
But I think you more than likely thought it was off, I don't see why Google would "force" updates for only you.
leveleyed said:
Thanks! Sorry for asking something that already had an answer. I guess I wasn't searching for the info properly.
I'm still having a problem though. I got the boot.img for the new version on my device. But when trying to launch Magisk manager, I see a window that says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing that same thing.
Click to expand...
Click to collapse
Try downloading Magisk v22.
There is no longer Magisk Manager.
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
l7777 said:
Try downloading magisk directly and installing. Or are if it already downloaded it and install that one.
Click to expand...
Click to collapse
Okay. I went to download v22 from Github (assuming I don't want Canary). But on the download page, I see written more than once, "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!" Unfortunately, I had Magisk hidden as a different app name. so I can't unhide it. I'm not sure what to do about this. Should I uninstall the hidden/renamed Magisk, or leave it and install the new one?
leveleyed said:
Okay. I went to download v22 from Github (assuming I don't want Canary). But on the download page, I see written more than once, "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!" Unfortunately, I had Magisk hidden as a different app name. so I can't unhide it. I'm not sure what to do about this. Should I uninstall the hidden/renamed Magisk, or leave it and install the new one?
Click to expand...
Click to collapse
Yes you should be able to uninstall it manually. Won't hurt anything.
leveleyed said:
Okay. I went to download v22 from Github (assuming I don't want Canary). But on the download page, I see written more than once, "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!" Unfortunately, I had Magisk hidden as a different app name. so I can't unhide it. I'm not sure what to do about this. Should I uninstall the hidden/renamed Magisk, or leave it and install the new one?
Click to expand...
Click to collapse
No don't use canary, use v22.
But why can't you inside it? It's in Magisk settling. If you must uninstall it, you can try that also then install v22
andybones said:
I'm sorry this happened to you.
But I think you more than likely thought it was off, I don't see why Google would "force" updates for only you.
Try downloading Magisk v22.
There is no longer Magisk Manager.
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Yeah, I know it was off because I am paranoid about automatic updates. I have them off in both Play Store and for system updates. I checked the setting after I rooted previously, and after it updated. So I guess it was actually just extremely bad luck/timing to click the location of the 'reboot and update now' button within the same frame the prompt appeared on my phone's home screen so that I never even saw it before it started rebooting and applied the update.
andybones said:
No don't use canary, use v22.
But why can't you inside it? It's in Magisk settling. If you must uninstall it, you can try that also then install v22
Click to expand...
Click to collapse
I couldn't unhide it because I was unable to launch Magisk at all. Every time I tried, I was just prompted to download it.
After uninstalling/reinstalling Magisk, downloading and extracting the boot.img for my current version of Android OS, patching in Magisk, and flashing the patched boot.img, I'm happy to report that I've successfully restored root without loss of my data partition!
Thank you so much to everyone here who helped me to get this resolved!
Now, hopefully I can find an app (or perhaps a Magisk module) that will prevent the system update notifications/prompts from even showing up on my phone, thereby eliminating the potential risk of needing to go through this again.
Ive actually been following the advice of many on this site for, ****, a couple few years now. i have a super unorthodox way of doing things, like how i figured out how to succesfully bypass frp on most samsung devices without a computer, last one i did was a couple weeks ago. because i dont have "class time" or training in coding or development besides what ive learned from you guys, i try alot of **** alot of pros wouldnt based on it shouldnt work that way, but, if i think i can weasel my way through anyway i usually prevail, and its usually by the application of a bunch of stupid little tiny actions. long story short i have to do things the hard way, guy could just grab a zte, install twrp app, flash recovery then in twrp recovery flash magisk, done. nope, too fricken easy. i gotta always get a lg, motorola or an iphone, before Uncover 8.0.2 was out, well before it was out i had my iphone 12 pro max jailbroken on 14.8. and i hope yall enjoy this as much as i did. i turned my ish app which i got from the app store jjst to make Apples butt hurt just a little more, i manipulated some filed and configs and basically turned it into Kali-Alpine lol, i then installed the checkrain debian, and yes jailbroke it from within, apples mdm is like neck and neck wiht you i learned while doing this, but when i did my ish filesystem editing, i didnt mount it until i was ready, and when i mounted thatfilesystem, you should ahve seen that realtime log light up, anyway, they said tell a story or something, and this will always be one of my favorite moments in triumph, because i took everything they use to keep a handle, as the very tools to take over the device lol.
in closing, i hope to give back for the advice and knowledge ive recieved in my time around. i will soon share my samsung debloat batch file, and a cople combination firmwares i have, and a magisk patched SM-A530W AP file whixh i also loaded the no verity/force encrypt kernel and twrp recovery image into, /system is mounted rw, props edited wiht all security disabled, and yes, kgclient removable, like totally uninstallable and everything is fine after, currently working on how to successfully boot and operate Samsung devices with 0x030c, bootloader code
theprimalconcretesinister said:
Ive actually been following the advice of many on this site for, ****, a couple few years now. i have a super unorthodox way of doing things, like how i figured out how to succesfully bypass frp on most samsung devices without a computer, last one i did was a couple weeks ago. because i dont have "class time" or training in coding or development besides what ive learned from you guys, i try alot of **** alot of pros wouldnt based on it shouldnt work that way, but, if i think i can weasel my way through anyway i usually prevail, and its usually by the application of a bunch of stupid little tiny actions. long story short i have to do things the hard way, guy could just grab a zte, install twrp app, flash recovery then in twrp recovery flash magisk, done. nope, too fricken easy. i gotta always get a lg, motorola or an iphone, before Uncover 8.0.2 was out, well before it was out i had my iphone 12 pro max jailbroken on 14.8. and i hope yall enjoy this as much as i did. i turned my ish app which i got from the app store jjst to make Apples butt hurt just a little more, i manipulated some filed and configs and basically turned it into Kali-Alpine lol, i then installed the checkrain debian, and yes jailbroke it from within, apples mdm is like neck and neck wiht you i learned while doing this, but when i did my ish filesystem editing, i didnt mount it until i was ready, and when i mounted thatfilesystem, you should ahve seen that realtime log light up, anyway, they said tell a story or something, and this will always be one of my favorite moments in triumph, because i took everything they use to keep a handle, as the very tools to take over the device lol.
in closing, i hope to give back for the advice and knowledge ive recieved in my time around. i will soon share my samsung debloat batch file, and a cople combination firmwares i have, and a magisk patched SM-A530W AP file whixh i also loaded the no verity/force encrypt kernel and twrp recovery image into, /system is mounted rw, props edited wiht all security disabled, and yes, kgclient removable, like totally uninstallable and everything is fine after, currently working on how to successfully boot and operate Samsung devices with 0x030c, bootloader code
Click to expand...
Click to collapse
Nice intro!, Welcome to XDA
theprimalconcretesinister said:
Ive actually been following the advice of many on this site for, ****, a couple few years now. i have a super unorthodox way of doing things, like how i figured out how to succesfully bypass frp on most samsung devices without a computer, last one i did was a couple weeks ago. because i dont have "class time" or training in coding or development besides what ive learned from you guys, i try alot of **** alot of pros wouldnt based on it shouldnt work that way, but, if i think i can weasel my way through anyway i usually prevail, and its usually by the application of a bunch of stupid little tiny actions. long story short i have to do things the hard way, guy could just grab a zte, install twrp app, flash recovery then in twrp recovery flash magisk, done. nope, too fricken easy. i gotta always get a lg, motorola or an iphone, before Uncover 8.0.2 was out, well before it was out i had my iphone 12 pro max jailbroken on 14.8. and i hope yall enjoy this as much as i did. i turned my ish app which i got from the app store jjst to make Apples butt hurt just a little more, i manipulated some filed and configs and basically turned it into Kali-Alpine lol, i then installed the checkrain debian, and yes jailbroke it from within, apples mdm is like neck and neck wiht you i learned while doing this, but when i did my ish filesystem editing, i didnt mount it until i was ready, and when i mounted thatfilesystem, you should ahve seen that realtime log light up, anyway, they said tell a story or something, and this will always be one of my favorite moments in triumph, because i took everything they use to keep a handle, as the very tools to take over the device lol.
in closing, i hope to give back for the advice and knowledge ive recieved in my time around. i will soon share my samsung debloat batch file, and a cople combination firmwares i have, and a magisk patched SM-A530W AP file whixh i also loaded the no verity/force encrypt kernel and twrp recovery image into, /system is mounted rw, props edited wiht all security disabled, and yes, kgclient removable, like totally uninstallable and everything is fine after, currently working on how to successfully boot and operate Samsung devices with 0x030c, bootloader code
Click to expand...
Click to collapse
How did your jail-breaking experience go? I've been thinking of jail-breaking my iPad Mini 4. (Look at my profile banner)
Tl;Dr - my pixel 5a5g got the black screen of death a few months ago. Last night, I tried using the flash tool to try to flash it back to Android from GrapheneOS - so that Google would be willing to fix it maybe. Flashing seemed to fail. Unsure what to try or do next.
---------------
My Pixel has had the black screen of death for a few months now. I'm assuming it is from falling a few feet to the ground. It had a custom ROM - GrapheneOS - on it. Unless I can reflash to stock Android, it sounds like Google/ubreakifix won't look at it, and thus - no chance of repairing it for free or a smaller charge.
The other night, I tried attaching an OTG keyboard to the phone to log in to it. Since the display is black, I'm not sure it worked. I also tried several times to press where I thought the numbers for logging in would be - on my completely black screen. Somehow, I was eventually able to get my PC and Google's flash tool to recognize the phone. However, I might have messed up on some steps - because I think it might be bricked now.
I think I forgot to remove the grapheneOS key via their Web installer before trying to flash android. I used minimal abd tools to unlock the bootloader (and it still says it is unlocked)... When I tried flashing back to stock android using the android web tool, it went through the motions, but then said something like it needs to detect the phone again after flashing. And it wouldn't detect the phone again. Even if I unplugged then replugged the phone. The directions said I shouldn't/wouldn't need to press any keys on the phone for this step, but it just wasn't progressing further... So, I ended up holding the power button and volume down button - and it went into fastboot(?) again - or whatever that does.
I can repeat the steps of going thru the motions of flashing the device now, but now it gives an error saying something like it can't lock the device.
Being that the 5a screen is completely black, I have no idea what is going on - or what to do from here. I've reached out to some local repair places, but honestly, if I can't flash it myself to stock so that Google/ubreakifix would look at it, then it probably isn't worth sinking money into.... There's decent condition used ones around $120 or something out there... And ubreakifix would probably charge between $160 and $200 for screen replacement + labor - and I'm assuming that's not including a motherboard replacement - if necessary.
Ubreakifix said that they would be willing to look at it, but they can't actually do any repairs to it if it isn't running stock Android. They'd charge for the labor, and they'd temporarily use a screen to look at what it is doing/not doing... But wouldn't actually do the screen repair. I'm assuming the phone never flashed completely, but I'm hoping they can tell me if their diagnostic tools work on it - since I imagine it should work -- IF stock Android is actually installed again on it.
I've also looked into doing something like getting a displaylink adapter + display link app so that I can see the screen on the computer... But even after my multiple attempts of logging in to the phone, I can't send app downloads to the phone. Google Play store shows that the phone was "last seen" months ago... And even if I could push the app download, GrapheneOS still requires manual approval from the user to accept/finalize install of the app... Which would be pretty hard to do without seeing the screen. And obviously since I've tried flashing the phone several times last night, i have no idea what the phone is looking like. Probably app downloads are out of the question now.
Apparently you can't normally do display out of any sort with Pixel phones. The rumor I've seen on here and/or reddit is that Google got rid of it years ago, maybe so that they can sell more Chromecasts...
Does anyone have any further suggestions? I could try using scrcpy or whatever it's called, but I probably should have tried to use that before attempting to flash the phone... It's sure hard to give up on something that I spent good money on. I'd like to think there's something I haven't tried yet that I can do to save it...
You could probably try these steps:
1. Open up Device Manager on PC
2. Connect your phone
3. Hold Power + Volume Down
If you have new device in Device Manager, you can do everything with your device like flashing or try "to remove the grapheneOS key".
Edit: I'm dumb and didn't notice that part where you tried this. You should just boot into fastboot and remove that custom AVB key with fastboot erase avb_custom_key, and then reflash the phone on flash.android.com. Hope that helps!