Database Info

[Q] Unable to factory reset

Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section

Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).

I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.

Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App

Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?

I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.

I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back

Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.

rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything

DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty

I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric

Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App

rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.

Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.

Please assist - Unusable Razr HD ( Spent 5-6 hours so far no luck )

Hi team,
Wondering is someone can assist or point me in right direction for fixing my wife's Razr HD. ( Australian Telstra GSM )
Issue - Currently phones starts goes to OS , however all andriod apps / core services are stopping making it unusable, usually phone will start ask for pin and within 30 seconds all apps and core services stop ( with error messages etc ).
So here is what happens and i have tried.
1. Tried uninstalling apps ( eg whatsapp / facebook etc .. ) it uninstalls sometime before the freezing / errors - but once you reboot those apps come back as there never uninstalled :|
2. Erase all data it never works it lets me press the button , but on reboot come back to original problem OS.
So i decided i should root / install custom rom or even stock rom ).
1. Boot Loader - Unlocked ( did that on motorola website no issues )
2. Tried Installing customer recovery in fastboot ( it flashes , however it goes to original recovery dead gread andriod with red traingle with belly open !, after flash i have not let it boot to OS still the same issue) - i think it has original-recovery.p file in system i cant delete it or rename it ..
3, Rooting - tried rooting no luck .. i can connect via ADB however system is read only ( doesnt let SU , busy box etc to copy or execute at all ) - tried motochoppper/ saferoot no luck .. it cant write or copy or exceute SU.
So i tried few other extreme measures as below..
fastboot erase system or -w
fastboot erase data
fastboot erase cache
All successful , however after that still boot to original OS.
Tried installing Stock ROM/Firmware using - RSDLite , it seems to install copied the files on reboot .. same old OS ..
i can goto fastboot , i can run adb shell command ( but its read only system ).
i am really stuck here wondering if you guys help / much appreciated.
rgds.

Have you tried factory reset? Or boot into safe mode?

Zeljko1234 said:
Have you tried factory reset? Or boot into safe mode?
Click to expand...
Click to collapse
Factory reset yes , however after device reboot it does nothing comes back t same faulty OS.
Safe mode?

Safe mode.
You may try to flash rom again but be very careful with unlocked bootloader. It's strange that you cannot boot into custom recovery holding volume down and power after you flashed it.

Zeljko1234 said:
Safe mode.
You may try to flash rom again but be very careful with unlocked bootloader. It's strange that you cannot boot into custom recovery holding volume down and power after you flashed it.
Click to expand...
Click to collapse
Tried flashing , in safe mode no luck either , any other suggestions?
Cheers,

You probably left your USB plugged in after you flashed Recovery and that set you back to Stock Recovery.....unplug the usb....

Hmm sounds like symptons that my dad's old Nook color experienced being stuck in read only mode. Tried everything but it was stuck in that read only state no matter what I did. Hopefully that is not the case for your phone. Have you tried house of moto or other compatible utility to restore back to stock?

this happened a few times on an older faulty version of twrp. until someone can figure out how to remove the write only from fastboot, there is no utility or script that will fix it.
no one was able to figure it out before, unfortunately, your phone is likely toast.

Just saw this thread and it sounds exactly like what just started happening to my phone yesterday. I was unlocked, and rooted, with stock VZW (US) ROM. All was fine. Then started getting app error popups like you state and tried using TWRP recovery to install a backup I had made and it appears to work only if I DO NOT check the 'data' box. When I try and wipe data, it errors out as well. I am worried something caused it to get stuck in read only mode like one of the last comments in this thread and the phone is toast, but not just.
If you find anything or figure it out please let me know, I'll do the same....
desitunez said:
Hi team,
Wondering is someone can assist or point me in right direction for fixing my wife's Razr HD. ( Australian Telstra GSM )
Issue - Currently phones starts goes to OS , however all andriod apps / core services are stopping making it unusable, usually phone will start ask for pin and within 30 seconds all apps and core services stop ( with error messages etc ).
So here is what happens and i have tried.
1. Tried uninstalling apps ( eg whatsapp / facebook etc .. ) it uninstalls sometime before the freezing / errors - but once you reboot those apps come back as there never uninstalled :|
2. Erase all data it never works it lets me press the button , but on reboot come back to original problem OS.
So i decided i should root / install custom rom or even stock rom ).
1. Boot Loader - Unlocked ( did that on motorola website no issues )
2. Tried Installing customer recovery in fastboot ( it flashes , however it goes to original recovery dead gread andriod with red traingle with belly open !, after flash i have not let it boot to OS still the same issue) - i think it has original-recovery.p file in system i cant delete it or rename it ..
3, Rooting - tried rooting no luck .. i can connect via ADB however system is read only ( doesnt let SU , busy box etc to copy or execute at all ) - tried motochoppper/ saferoot no luck .. it cant write or copy or exceute SU.
So i tried few other extreme measures as below..
fastboot erase system or -w
fastboot erase data
fastboot erase cache
All successful , however after that still boot to original OS.
Tried installing Stock ROM/Firmware using - RSDLite , it seems to install copied the files on reboot .. same old OS ..
i can goto fastboot , i can run adb shell command ( but its read only system ).
i am really stuck here wondering if you guys help / much appreciated.
rgds.
Click to expand...
Click to collapse
---------- Post added at 03:02 PM ---------- Previous post was at 02:52 PM ----------
I am guessing this might be the issue and I am experiencing it as well. However, I have no idea how that could have happened in the first place. I never tried to do anything with TWRP until after the phone began acting funny with all apps crashing (pop ups stating that) and the phone essentially becoming unusable.
When I am in TWRP and do wipes (factory reset, or advanced wipes) it seems to wipe everything fine, even the data partition. However, when I try and write to that partition it fails (i.e. restoring a backup including the data partition). If I don't include the data partition the restore works, but the phone is still crap.
Does this sound like the issue you mention below (data is stuck on read only and there is no way around it)?? If so, anyone in the market for a decent looking paperweight??
bweN diorD said:
this happened a few times on an older faulty version of twrp. until someone can figure out how to remove the write only from fastboot, there is no utility or script that will fix it.
no one was able to figure it out before, unfortunately, your phone is likely toast.
Click to expand...
Click to collapse

surfmly said:
Just saw this thread and it sounds exactly like what just started happening to my phone yesterday. I was unlocked, and rooted, with stock VZW (US) ROM. All was fine. Then started getting app error popups like you state and tried using TWRP recovery to install a backup I had made and it appears to work only if I DO NOT check the 'data' box. When I try and wipe data, it errors out as well. I am worried something caused it to get stuck in read only mode like one of the last comments in this thread and the phone is toast, but not just.
If you find anything or figure it out please let me know, I'll do the same....
---------- Post added at 03:02 PM ---------- Previous post was at 02:52 PM ----------
I am guessing this might be the issue and I am experiencing it as well. However, I have no idea how that could have happened in the first place. I never tried to do anything with TWRP until after the phone began acting funny with all apps crashing (pop ups stating that) and the phone essentially becoming unusable.
When I am in TWRP and do wipes (factory reset, or advanced wipes) it seems to wipe everything fine, even the data partition. However, when I try and write to that partition it fails (i.e. restoring a backup including the data partition). If I don't include the data partition the restore works, but the phone is still crap.
Does this sound like the issue you mention below (data is stuck on read only and there is no way around it)?? If so, anyone in the market for a decent looking paperweight??
Click to expand...
Click to collapse
if your phone goes to read only because of that faulty version of twrp, its toast. i am sorry for your loss

He can try to flash correct twrp...

Zeljko1234 said:
He can try to flash correct twrp...
Click to expand...
Click to collapse
that may work in some rare cases.
i hope this poster is one of them!!! that it works.
if the entire phone goes to read only. i havent seen a solution on any forum.

bweN diorD said:
that may work in some rare cases.
i hope this poster is one of them!!! that it works.
if the entire phone goes to read only. i havent seen a solution on any forum.
Click to expand...
Click to collapse
Well it looks like I was able to get through some of it. I followed the instructions here: http://www.droidrzr.com/index.php/topic/49699-1834614xt926-ota/. I did the extra step of going to stock 183 (unrooted) and then flashed the update in that and the phone is working fine. I am already unlocked (have been for long time), but not rooted at the moment. I believe I can root now (being that I am unlocked) but haven't tackled that yet. At the very least I have a phone that works for my upcoming business trip.....
BTW - the TWRP I had installed has been used on my phone for a long time (8-12 months??) so not sure why that version all of a sudden would have caused the issue, but at this point it doesn't appear to have been that issue (with data locked in read only mode).

I'm really glad that you found solution for you and for all of us who may have the same problem in the future. Thx.

Help very much appreciated (boot loop nexus 5)

Hello Everyone,
I have searched this forum and followed many useful threads which seemed related to my issue, alas none have actually been able to fix my phone.
I am using a stock ROM which upgraded to marshmallow not too long ago. The other day my phone rebooted for no reason got it's self into a boot loop. Since them I have tried the following:
1) I have used recovery mode and cleared the cache/performed a factory reset. I just the get the can't mount/cache line pop up.
2) Tried to use ADB to boot an image over the USB but couldn't get much from this (so I may have missed something with this).
3) Tried to use fastboot to move flash back to a version of marshmallow downloaded. When I go to flash files in I get failed messages on command prompt. (Failed, remote flash write error).
additional info
1) the device was encrypted from the settings menu when functional.
Any advice or help would be good at this point. Let me know if additional information is needed.
Thanks!

[Completed] Recovery mode is gone, Factory mode is gone, help me XDA you're my only hope...

So here is a string of steps I've already been through in trying to save my bricked Nexus 6: [Can't post outside link yet...]
Basically I got the 'your phone is corrupt' message from google and it kept forcibly shutting down. It would not boot up so someone suggested I side load a rescue OTA. At this point recovery existed and I went through all the steps and had it installing, only to fail mid-way through (~52%) and give me a 'read error' on my command prompt. I started the whole process over again just fine and it got to 73% before 'read error' failing again. I thought no big deal, I'll just keep doing this until it gets to 100%. Nope, recovery is gone. I cannot get there anymore. I start into Fastboot mode and scroll to recovery and hit power and it just goes to a new Fastboot screen and keeps flashing every time I try to select it. The Bootloader logs give me a 'failed to validate boot image: ret=-1' message and says 'Boot up failed.'
I can't find a single guide online that doesn't require recovery mode to work. At this point I don't care about my data and just want to get this phone working again before I throw in the towel and pay Motorola $175 for a refurb. I'm just barely over a year too. The Nexus 'expert' gave up and blamed the memory and maybe he is right but I wanted to run this by you guys first. This phone was completely stock and unrooted.
The only reason why I feel there is still a chance is because when I connect USB my computer reads it as an Android Device in Device Manager with 'Android Bootloader Interface' as a sub device. If the computer can read it, isn't there a chance that some kind of software exists that can forcibly load a new bootloader onto this phone without recovery? I'm 'competent' with computers and android phones but I haven't rooted or done any custom stuff in years so I'm at a loss for what's out there.
Thanks in advance for any help you can give me, even if it's to tell me I'm SOL.

Ok so far I have tried to load a custom recovery but that requires an unlocked bootloader. Then I tried using a toolkit to flash stock as a soft-bricked device but that also requires an unlocked bootloader and I can't unlock the damn bootloader. You know, I thought I was just playing it safe by leaving this phone as-is instead of playing around with it but it looks like I screwed myself by doing so.

Is this the wrong forum for this question?

JQ3 said:
Is this the wrong forum for this question?
Click to expand...
Click to collapse
Sorry for the delay
We have a dedicated help section for your device here
http://forum.xda-developers.com/nexus-6/help
Ask there to receive help
Good luck

Cannot load Android System. Your data may be corrupt.

Backstory: I upgraded to android 10 a few weeks ago, aside from a few user apps breaking, there weren't any system issues. Recently, I received another update (seems like a patch ?) to android 10 and updated as well. I'm not sure if this recent update actually completed.
Last night, it seems like my phone went into a boot loop while I was sleeping. When I woke up the phone was hot, and each boot was so short that there was no opportunity to go into recovery mode. I pretty much had no choice other than to let the battery drain.
So I walked away and came back a while later to a peculiar recovery screen that said "Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."
There's only 2 options: "Try again" and "Factory data reset". `adb devices` from the PC is unable to detect my pixel 3 here. "Try again" simply attempts to boot, and I just return to this same screen again (at least it doesn't loop now). I'm reluctant to factory reset as I want to at least have the chance to back up some data.
I am able to enter fastboot from this screen using Power + Volume Down. `fastboot devices` from the PC is able to detect the phone. However, because the bootloader is locked (haven't unlocked the bl since i started using nexus/pixel phones), I don't know if there's much i can do here.
My question is, is there anything that I can try at this point to boot into android 10, recover some data, then do a factory reset ?

From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota

sliding_billy said:
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
Click to expand...
Click to collapse
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.

superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Not knowing what is available with the BL locked... Is the new rescue mode option one of the power up/down choices from your BL/Fastboot screen? That rescue mode is supposed to allow ADB command to work. If not, you are going to have to do a factory reset and if that doesn't help contact Google and RMA. Ability to get out of bricks is the biggest reason to unlock your BL (if you purchased a Google unlockable BL phone) unless you purchased a Verizon phone and can't. In that case, back to the last comment about factory reset/RMA.

superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Had this happen and I had to do a factory reset prior to unlocking bootloader ,which as was mentioned above is way easier to fix because you can reflash factory image without wiping all data

same thing happened to me; the previous comments gave me the outline of what was needed, so thank you. now for the op:
1. on the screen that offers try again or factory erase, choose "try again"
2. IMMEDIATELY press and hold volume down
3. when you reach the bootloader screen, you may release volume down
4. this is the standard bootloader screen for pixel 3. you should be able to cycle options do so to select 'recovery" (or whatever it says. I'm not going to reboot my phone to see exactly what it says, but I'm sure you get the idea)

Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.

Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
Sounds like this problem. https://forum.xda-developers.com/t/...xxxx_sn-xxxxxxxx.4205331/page-7#post-85981389

Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.

AsItLies said:
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
Click to expand...
Click to collapse
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.

Prudhvi89 said:
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Click to expand...
Click to collapse
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructions​The factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers

AsItLies said:
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructions​The factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
Click to expand...
Click to collapse
Hi, thanks for quick response. I am getting below error, not sure how to correct it.

Prudhvi89 said:
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Click to expand...
Click to collapse
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.

Currently I am not able to switch on my phone !!!

AsItLies said:
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Click to expand...
Click to collapse
Currently I am not able to switch on the device !!

Prudhvi89 said:
Currently I am not able to switch on the device !!
Click to expand...
Click to collapse
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.

AsItLies said:
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
Click to expand...
Click to collapse
Ok got it !! Thanks for your prompt response & support.

The "Cannot load Android system, Your data may be corrupt" error is known as Rescue Party. Fortunately, fixing it should be relatively simple.
Try dirty flashing the factory image. Do not attempt to flash a patched boot image; leave everything stock.
If that fails, select "Factory data reset". It will wipe your phone, but it should reboot into Android system.
That bootloader message "Your device is corrupt. It can't be trusted" means that the signed key for Verified Boot somehow got screwed up. In this case, I would also recommend reflashing the factory image.
In both cases, the easiest option is to use the Android Flash Tool. It's like a GUI for flashing the factory image.