Hi there,
Not sure what happened - I'm using my Tab S3 (SM-T820) for ages in the same (stable) configuration - rooted Stock, no changes/installations for months.
This morning it was in Odin/Download mode and I cannot boot into system.
I can get into recovery (TWRP), but I cannot boot into system from there either, it always returns to Odin (tried wiping Cache/Dalvik, didn't help).
For now my only idea is to let it completely discharge, charge again and give it another try.
No buttons appear to be stuck.
Any ideas or suggestions, eg sth I could check in TWRP to see what's going on?
(hopefully nothing wrong with the system partition).
Note - I'm only familiar with the typical TWRP functions needed to install custom firmware, haven't used it for much else. Obviously would prefer not to destroy my (stable) setup and spent a full day re-installing everything
Thanks a lot for your help everyone!
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
bmwdroid said:
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - yes, I will try that once the complete discharge is finished.
Reflashing stock - could cause this any troubles as it's already unlocked/rooted?
Or is there a chance dirty flashing the Tweaked Stock ROM could work, too?
Tablet was still on the original Stock it came with, but rooted with magisk and manually debloated...
Thanks again!
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
bmwdroid said:
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
Click to expand...
Click to collapse
Hi there and thanks again -
Took me a while to try everything but finally it's working again.
Complete battery drain didn't help, but dirty flashing did - once I got the correct version.
Basically made a nandroid backup, then flashed the tweaked rom over my existing one, starting with newer versions down to older ones.
So, flash, reboot - didn't work, restore nandroid (all), flash slightly older rom....
Till it started booting with v2.0 (probably matching my existing rom close enough).
Had to reflash Magisk as the 2.0 Rom included didn't match my Magisk Manager, but now my Tab S3 is working again!
Related
This is my first time posting.
I am a noob, but I am trying to get beyond that. I have flashed kernels and ROMS to my GT-I9100, with success. The other day, I was going to flash a new ROM, and I tried to make a Clockworkmod backup of my current ROM...while the phone was charging. Is this a major blunder?
The reason that I ask is that CWM crashed in the middle of the backup, and now I can't enter CWM recovery and the phone doesn't boot properly. I just get stuck in a bootloop. I can get into download mode. I used Pistachio's post about how to fix a soft-bricked GS2 to flash back to stock thru Odin. Then I used CF-ROOT to re-root the phone. After that, everything works fine, and I can get to Android recovery mode. Then when I try to flash a ROM, Titanium Backup must be restoring the previous version of ROM Manager, and I get stuck in the same bootloop when trying to get into CWM recovery.
Is Clockworkmod corrupted? Did the recovery partition get corrupted? Should I flash back to stock, delete ROM Manager, then re-install it? Should I bite the bullet and delete my Titanium Backup folder, then re-install everything from scratch? Should I flash back to stock with Pistachio's .PIT file and tick RE-PARTITION?
I looked for an answer specific to this problem, and cannot find the exact same scenario in any other threads. There are similar problems, but I think that I have a CWM app or recovery partition problem, or I may have a NAND rw corruption. I don't think that it is a NAND rw corruption though, because I can flash different kernels and ROMs.
I have been using Resurrection Remix versions 2.2, 2.4.1, and 2.5.3.
I have been using Siyah 3.3.2 kernel.
Please help, and excuse my noobness if I am beating a dead horse with this question.
Sounds like Rom Manager borked CWM/CWRecovery, which it seems to do on SGS2 quite a lot.
Most of the scenario you outlined in para.3 of your post (back to stock, delete ROM Manager) sounds like a good WTG, but do not reinstall it.
If you're going to use a kernel which has CWM/CWRecovery (like Siyah), do not use Rom Manager at all. Uninstall it & keep it that way. CWM/Recovery can do pretty much everything Rom Manager can, and you're playing with fire having both on the phone. Eventually Rom Manager will bork CWM again if you use it.
In the first instance, go back to stock, re-root your phone & reinstall the rom/kernel you're wanting to use. If Rom Manager is installed by default, uninstall it before you do anything else. With a bit of luck, you shouldn't have to do anything else (like messing around with PIT's which you also mentioned in para.3). If you batch restore your apps with TI, make sure you don't restore Rom Manager.
Thanks for the speedy reply.
I will try what you have suggested, but how do I flash the .zip file from my phone without ROM Manager? Do I have to do it through Odin?
Yep, that's right. Get an Odin flashable rom from Intratech's thread (search for it on here). If links in that thread don't work, search here or Samfirmware.
Edit - And once you've got your phone back up & running the way you want, use CWRecovery to do all your flashing.
My apologies, I should have been more specific. I want to flash the RR 2.5.3.zip. Should I still download it to the PC, then flash through Odin, or can I use Android recovery to do it through the phone?
OK. Let's rewind a bit.
What state is your phone in right now ?
I am flashed back to stock, and about to use CF-ROOT.
OK. Root the phone, CWM/Recovery will be installed by default. Once the phone is rooted, reboot into CWRecovery, flash your RR zip & you should be GTG. Just remove Rom Manager if it's installed as part of that process before you do anything else (including backing up). If you're going to restore a backup, again, uninstall Rom Manager immediately after you restore.
OK, after I flash CF-ROOT, I will re-install Titanium Backup, and delete ROM Manager to be safe before proceeding. Then I will flash the ROM.zip and test CW recovery and reboot again. I will reply after doing so.
Thanks
ARRRGH!
After flashing CF-ROOT I cannot get to the splash screen upon reboot. I made sure that I ticked USB debugging before flashing the kernel. I can still get into download mode and CWRecovery, so I flashed back to stock, and tried again to no avail. I tried flashing the RR 2.5.3.zip, in CWRecovery, and it flashed. I get to the splash screen but no further. I feel like a terrible noob now, because yesterday I had the phone flashed to stock and rooted no problem. Is there something that I am missing? I made sure that I used the proper CF-ROOT kernel.
So you're getting bootloop when you flash RR ? Have you tried booting into recovery & doing a wipe/factory reset ?
I believe that I am fixed.
I restored a Nandroid backup of my stock ICS from right after my original rooting, and the phone booted fine. I did a wipe/factory reset and wiped cache. Then I flashed RR 2.5.3. The phone rebooted fine again. I IMMEDIATELY uninstalled ROM Manager and made sure it was out of Titanium Backup as well. I have rebooted several times, normal, download, and CWRecovery, and everything works as it should. I think that I am getting over my noobness.
I WILL NEVER INSTALL ROM MANAGER AGAIN...DOWN WITH ROM MANAGER!!!!!!!!!!!!!! Except for the Little Alex icon, that's still pretty cool.
A thousand thanks for your help. At least I was on the right track when I first asked for help. I was pretty sure it was a problem with ROM Manager, because when it crashed, it started this whole mess. I'll be sure to press the THANKS button for your help, and I'm going to thank Pistachio for his thread as well.
Not n00bness, stuff happens sometimes ;-) You weren't the first person to get tripped up by Rom Manager (I did not long after I got my phone), and you won't be the last.
Yep you had a fair idea of what might have caused it, and your detailed OP certainly made it a lot easier to work out WTF was causing the problems.
No probs. Glad you got it sorted ;-)
I installed TWRP on my phone, and went into Bootloader an hit RECOVERY so I can get to the program (the first time I did this it brought me to the TMRWP program). THIS time, it completely wiped my friggin' phone... after I sat there like 4 hours re-setting up everything PERFECTLY how I wanted it.
What's weird is it kept ALL my apps that I converted to SYSTEM APPS, but all my user stuff is gone.
Lesson learned... Don't click recovery from Bootloader.
That has yet to happen to me with any recovery and 3 devices currently with twrp. Might be a step missed with the install or maybe you left a bootloader update zip and ran it when you rebooted? Or it can be a bug as going to recovery from bootloader via a cold start is how to get there traditionally. I would email teamwin and try to sort it out or redo the recovery install, making sure to check the md5 of the file after you download it.
Sent from my Transformer TF101 using Tapatalk 2
Your supposed to click recovery at bootloader. Thats where you do backup, restore and flash new roms.
HTC Sensation z710e
ICS 4.0.3
Sense version 4.0
Software Sense-o-maniac v1.3
Kernel. 3.0.30 Bricked
Radio 11.68.3504
That's what I thought too. If I'm not mistaking, I flashed the new firmware after I did the TWRP, so maybe that screwed it up somehow. I take it TWRP must be the LAST image you flash? Only flashes I remember doing were:
Customize bootloader screen
TWRP.
firmware update
Do I need to re-flash the new firmware before re-flashing TWRP, or is the firmware going to remain no matter what I do from this point on?
Just adb flash recovery. Put the recovery image in your platform tools folder. Adb reboot bootloader. when you are rebooted adb flash recovery recovery.img.
Or use one of the many tools made to do that on our forums
Sent from my ADR6425LVW using xda premium
Well I went ahead and used the GOO Manager to flash TWRP again, and this time it worked fine. I'm going to re-setup my phone again then before I customize it back like I had it, going to try to get to recovery and see if it works.
With it now being installed, does that mean I can't flash anything directly from SD Card or modify the bootloader anymore without it causing problems?
What I mean, moreso, is... if I ever put factory reset. will it reload the factory rom + keep the newest firmware I installed (etc.) or do I nee to back up the phone with TWRP and recover from that when I want to load it back?
Factory reset just puts things back to the way they were without the stuff in the data partition or any user apps or settings. This means that say you flash a custom rom, it will reset to as if that custom rom was freshly installed since the custom rom has replaced the factory rom in the /system/ parition and anything else related to it.
With that said it is usually a good practice after rooting a fresh device to do the nandroid and then transfer it to a computer before you do anything else. Note that while you probably won't be switching recoveries a lot, that nandroid backups generally work only with the recovery that generated them so don't get them mixed up.
I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
* RECOVERY: Install Rom: Download
* RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
* RECOVERY: Wipe Cache Partition
* RECOVERY: Wipe Dalvik Cache
* Reboot and enjoy
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted
Hi all
How exciting it is to see that so many people are so involved in improving or fixing their mobile devices.
I got some sort of a virus on my Samsung Galaxy S3 so decided to try to wipe it clean and load a more up-to-date version of Android on it. It had 4.3.?. On a Windows 7 PC, I downloaded the Skipsoft Unified Android Toolkit (version 1.4.5). I think now I didn't need to but probably succeeded in rooting my S3 with Kingo ROOT.
Next, using the toolkit and Odin, I think I succeeded in flashing the recovery-twrp-2.7.1.0-i9300.tar custom recovery.
My phone would only boot up with the stock Android.
I took me a while before I learnt about entering the recovery mode by holding the volume up, home and power-on buttons simulateously.
In the recovery mode, I used Wipe, Advanced, ticked all of the boxes and wiped everything on the phone.
Then, using the toolkit and Odin again, I flashed the same recovery-twrp-2.7.1.0-i9300.tar custom recovery I'd flashed before.
I still can't boot my phone. If I choose Reboot from twrp (v2.7.1.0) and then either System or Recovery, I just get, "No OS installed! Are you sure you wish to reboot?"
I can still enter either download or recovery modes but the latter is something of a hit and miss affair.
Using File Manager in the twrp I can see lots of files and directories so guess I managed to flash something.
Also, using Terminal Command I see that my prompt is a "#"so think I'm still rooted.
I know something about Unix and programming mainframe computers but am not an expert with mobile devices. I'd be so grateful if someone could please advise me as to what to do?
Mike
You wiped system partition ;-;
If you want stock rom you need to flash the stock rom by odin.
I recommend you to install a custom rom like Temasek or CM13, it's real easy just flash the zip.
Haha yes^ this guy is right
You might have to flash stock rom if you somehow wiped efs, most of the time custom roms doesn't include efs with them
Turga said:
You wiped system partition ;-;
If you want stock rom you need to flash the stock rom by odin.
I recommend you to install a custom rom like Temasek or CM13, it's real easy just flash the zip.
Click to expand...
Click to collapse
Thanks for your response, Turga and snkmv, below. I didn't know what efs was so looked it up on the net and found this worrying but expert explanation from ryanrazer and Rukbat in androidcentral ( http://forums.androidcentral.com/as...erstanding-cwm-backups-efs-partition-etc.html )
In twrp's recovery mode on my phone and using File Manager, I see that the directory /efs is empty (all files are shown in File Manager, right, including invisible files?)
I'd prefer to try to flash a custom ROM which includes efs rather than the stock ROM. Do Temasek or CM13 include efs or does another, reliable custom ROM?
Thanks again folks
Mike
Hi guys. I've been using custom ROMs for a few years now and I always used TWRP.
But lately, my banking app and some other important apps simply won't work because of my custom recovery.
Having that said, can I keep my LineageOS AND flash via Odin JUST the stock recovery to "bypass" the security these apps need? I'm using Magisk and I'm hiding root access from these apps.
What would happen if I flash the stock?
Thanks in advance!
This sounds like a device specific issue, as I use TWRP and LOS on my V20 with no issues. I'd say the banking apps aren't working because you are rooted which means MagiskHide might not be working properly.
This can also happen if you fail the SafetyNet test in Magisk depending on certain apps.
I'm not aware of a way for you to use a custom ROM with a stock recovery. It may be possible but hasn't been as far as I've seen.
I recommend asking this question in the proper Q/A section for your device (which I assume is a Samsung since you mentioned ODIN) to see if other users of that device can help you. Then, report this thread to have it closed/deleted once you have done so.
Also: Backing up with Titanium Backup isn't enough, in almost any case. Do a FULL backup from TWRP of your device, store it somewhere else like an SD card or PC and then mess around.
Redline said:
This sounds like a device specific issue, as I use TWRP and LOS on my V20 with no issues. I'd say the banking apps aren't working because you are rooted which means MagiskHide might not be working properly.
This can also happen if you fail the SafetyNet test in Magisk depending on certain apps.
I'm not aware of a way for you to use a custom ROM with a stock recovery. It may be possible but hasn't been as far as I've seen.
I recommend asking this question in the proper Q/A section for your device (which I assume is a Samsung since you mentioned ODIN) to see if other users of that device can help you. Then, report this thread to have it closed/deleted once you have done so.
Also: Backing up with Titanium Backup isn't enough, in almost any case. Do a FULL backup from TWRP of your device, store it somewhere else like an SD card or PC and then mess around.
Click to expand...
Click to collapse
Thanks for that. I wiped the whole thing and installed a stock ROM. Will only root now and see where it goes.
Titanium backup crashes on this phone (yes, it's a Samsung J7 Prime) if I use Magisk anyway.
I trusted my Google syncing and I kinda got a lot of backups back from the cloud. Not perfect, but acceptable.
yea you can use it
Following is the procedure :
A Nandroid Backup
The quickest way to revert your phone back to its stock ROM is to restore your Nandroid backup. Assuming you have an up-to-date one available it shouldn’t result in much — or any — data loss.
A Nandroid backup creates a complete snapshot of your phone: the operating system, apps, data, and everything else. Restoring it, therefore, restores the ROM you were using at the time. If you have a backup you took when using the stock ROM, then you’re set.
How to Restore a Nandroid Backup
Boot your phone into your custom recovery. We recommend TWRP.
Select Restore. You’ll see a list of all the available backups.
Pick a backup made using the stock ROM.
Select the partitions you want to restore. Normally this means you should check all the boxes.
Finally, swipe the bar labelled Swipe to Restore. It takes a few minutes to complete, then you can reboot.
Flash a Stock ROM
If restoring a Nandroid backup isn’t a viable option, then the next best bet is to flash a stock ROM. This comes with the added inconvenience that you will probably need to perform a factory reset along the way
There are benefits, too. You might be able to find a version of the ROM that is pre-rooted. Flashing ROMs is also really easy to do.
How to Flash a Stock ROM
Find a stock ROM for your phone. Go to forum.xda-developers.com and locate the forum for your device. Stock ROMs are often found in stickied posts at the top of the development boards.
Download the ROM to your phone.
Backup all your data.
Boot into recovery.
Select Wipe to reset your phone. This is optional (if you don’t want to bother with backing up and restoring), but you may encounter bugs or even get stuck in a bootloop if you don’t do it. Swipe the bar to begin the wipe.
From the recovery home screen, select Install and navigate your way to the stock ROM you downloaded.
Swipe the bar to begin installation. You can reboot your phone when it’s finished.
Flash a Factory Image
The ultimate method for getting your phone back to stock is to flash a factory image. This reverts your phone almost to the state it was in when you first unboxed it. All you need to do afterwards is lock the bootloader, and your device will be completely factory fresh.
How to Flash a Factory Image
The procedure to flash a factory image can differ from one device to another. In the case of a Pixel, the steps are simple:
Download and setup the ADB and Fastboot tools.
Download the factory image from the Android website. Unzip the download on your desktop.
Connect your phone via USB and boot into Fastboot mode.
Launch the command line or terminal app.
At the command prompt run flash-all.bat on Windows, or flash-all.sh on Mac or Linux.
Wait for it to finish, then reboot.