"Device Is Corrupted" System Files Wiped - Nexus 6 Q&A, Help & Troubleshooting

Another "device is corrupted" message - Syatem files wiped
I have a real problem on my hands. Just got a new Nexus 6 and used the Nexus Root Toolkit to unlock and root and add TWRP. The process went smoothly until after TWRP install. I recall that from TWRP I was rebooting after installing Busy Box and SuperSU. On the reboot I got the dreaded “Your device is corrupted…” and the phone instantly shut down. Pressing the power button after that message does not work. I went back to the toolkit and tried everything (stock, unroot, etc.) and nothing worked. I've rooted a NOTE 2 a few years ago but I forgot most of what I learned.
I can however boot into recovery and bootloader mode. Also it looks like all system files on the phone got wiped. The problem is that my computer can see the phone's file system only when I'm in recovery, not when I'm on the bootloader screen. Any ideas as to how to fix?
Can I put an image file on a USB stick and install from recovery? Thanks for your help..

Use fastboot. Flash system and boot and recovery from bootloader. Adb doesn't work in bootloader mode.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 06:58 AM ---------- Previous post was at 06:55 AM ----------
Actually just boot the phone. The corrupted message will disappear and the phone will boot. After 30 or 60 seconds. I forget. The kernel sets the flag that you're on a modified recovery so the message displays. Nothing wrong with the phone. Your system is still there.
Sent from my Nexus 6 using Tapatalk

Also make sure you applied the latest SuperSU available plus the boot image
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

i fixed that by flashing to factory firmware if you don't know how message me for steps

Related

Phone stuck in factory reset

Hi. I'm unexperienced with this in general, so please bear with me. I treid to search similar threads but didn't find anything about my problem exactly.
I've a rooted European (Exynos, Polish or German distribution) version of Note 4. I don't run any custom OS nor did I make any changes to my phone in the last few months. As of now, it's running Lollipop.
A few weeks ago, my phone started randomly rebooting. I blamed it on old apps, did a check with antivirus and uninstalled some apps I wasn't sure about. But the problem grew worse (reboot every few minutes). I've erased all apps that had something to do with my root (Lucky Patcher was constantly popping up in my SU logs in the same minute my phone rebooted, so I uninstalled all patched app and then Lucky Patcher), deleted almost everything, checked that system apps were all the newest version. Nothing helped so I thought a factory reset seems like the best option now. I went to the Settings and did a factory reset.
But now I'M STUCK. There is this picture of the Android with the blue web that should be turning (but isn't) the screen says "Systemupdate wird installiert" (system update is installing), the picture disappears (black screen) and comes back every few seconds. There is no blue line signalising progress or anything. All this for some two hours now.
I don't want to try anything myself because I don't want to make my phone a brick. Does any of you know what my problem could be? Thanks.
I'm not too sure why your device is stuck in an update loop. But are you positive you havent tried flashing anything to your device??
---------- Post added at 05:28 PM ---------- Previous post was at 05:23 PM ----------
Wait a second, you're saying you arent running a custom rom, yet your device has root with superuser.. Therefore you should also have a custom firmware flashed to your device.. Twrp or cwm. Irecommend twrp. If you have a custom recovery. Then boot in to recovery mode and clear cache/dalvik wipe/ factory reset etc.
TheTecXpert said:
I'm not too sure why your device is stuck in an update loop. But are you positive you havent tried flashing anything to your device??
---------- Post added at 05:28 PM ---------- Previous post was at 05:23 PM ----------
Wait a second, you're saying you arent running a custom rom, yet your device has root with superuser.. Therefore you should also have a custom firmware flashed to your device.. Twrp or cwm. Irecommend twrp. If you have a custom recovery. Then boot in to recovery mode and clear cache/dalvik wipe/ factory reset etc.
Click to expand...
Click to collapse
Positive I haven't flashed anything. I didn't even connect it to a computer.
I think that my device has cwm but it's long since I've used it. I tried getting into recovery mode and the only thing I can see is the android figure with the blue ball, no menu, no anything.
UPDATE: I flashed twrp with ODIN, phone rebooted like after a factory reset.
keinalu said:
Hi. I'm unexperienced with this in general, so please bear with me. I treid to search similar threads but didn't find anything about my problem exactly.
I've a rooted European (Exynos, Polish or German distribution) version of Note 4. I don't run any custom OS nor did I make any changes to my phone in the last few months. As of now, it's running Lollipop.
A few weeks ago, my phone started randomly rebooting. I blamed it on old apps, did a check with antivirus and uninstalled some apps I wasn't sure about. But the problem grew worse (reboot every few minutes). I've erased all apps that had something to do with my root (Lucky Patcher was constantly popping up in my SU logs in the same minute my phone rebooted, so I uninstalled all patched app and then Lucky Patcher), deleted almost everything, checked that system apps were all the newest version. Nothing helped so I thought a factory reset seems like the best option now. I went to the Settings and did a factory reset.
But now I'M STUCK. There is this picture of the Android with the blue web that should be turning (but isn't) the screen says "Systemupdate wird installiert" (system update is installing), the picture disappears (black screen) and comes back every few seconds. There is no blue line signalising progress or anything. All this for some two hours now.
I don't want to try anything myself because I don't want to make my phone a brick. Does any of you know what my problem could be? Thanks.
Click to expand...
Click to collapse
There is a chance that you put your phone in odin download mode instead doing factory reset
keinalu said:
UPDATE: I flashed twrp with ODIN, phone rebooted like after a factory reset.
Click to expand...
Click to collapse
So you got it working now? Or?? You mean rebooted successfully? Or rebooted back in to download mode?
TheTecXpert said:
So you got it working now? Or?? You mean rebooted successfully? Or rebooted back in to download mode?
Click to expand...
Click to collapse
There seems to be no problem now, my phone went back from 5.1 to 5.0.1 though. Maybe the whole thing started because of the last update. I tested and I can get to recovery mode normally, so I did a back-up just in case somethin goes wrong again.
If you managed to flash twrp and successfully booted back in to your device, then i recommend rebooting back into twrp recovery, and doing a cache and dalvik cache from within the recovery menu. And if you want root access, download the latest superSU (itll be a zip file), copy the file to the download folder of your internal storage, reboot in to your recovery, install the superSU zip file you downloaded, once its indtalled, wipe both caches again. And reboot.
Let me know how you go, and if you get stuck somewhere, dont be afraid to ask. Im happy to help

Bootloop, can get to "firmware update screen", fastboot commands not working

Bootloop, can get to "firmware update screen", fastboot commands not working
Out of nowhere my phone rebooted and started bootlooping. Eventually it came on but within minutes it did it again. After about an hour of pulling the battery abd trying to boot it, it finally came on. I went to use some app (I cant remember the title) to boot into twrp but it froze and started to bootloop again. I had never granted SU permissions to the app and it hadnt come up. Now that i have my computer I was able to boot into download mode (Firmware update screen) but my fastboot boot twrp.img command is stuck on waiting for device. Im guessing a malicious app caused the bootloop as i granted some app SU permissions only to later realize that it never needed it. All it did was download apk files for pentesting and diagnosis apps. It may be one of those apps however. I was on a custom ROM with an unlocked bootloader and twrp (although i cant seem to boot to it). LG Bridge couldnt find the device. Any help would be appreciated as this is my only device and I'm waiting for a call back for a speeding ticket and don't want to be screwed over :crying:
Since you have twrp and unlocked bootloader you should be able to access twrp still. This happened to me but from wiping internal storage by accident. Make sure you have your custom rom of choice on your sd card or the one you were running. Power off your G4 completely and while its off enter recovery mode manually. You may need to do this a few times for your G4 to enter recovery but it will boot to twrp. I believe its hold power button and volume down button then release for a sec both buttons when you see the lg logo then continue to hold them again. Do the factory reset option and after that it will boot to twrp and flash your rom again. Hope this works.
Sent from my LG-H811 using Tapatalk
srod562 said:
Since you have twrp and unlocked bootloader you should be able to access twrp still. This happened to me but from wiping internal storage by accident. Make sure you have your custom rom of choice on your sd card or the one you were running. Power off your G4 completely and while its off enter recovery mode manually. You may need to do this a few times for your G4 to enter recovery but it will boot to twrp. I believe its hold power button and volume down button then release for a sec both buttons when you see the lg logo then continue to hold them again. Do the factory reset option and after that it will boot to twrp and flash your rom again. Hope this works.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
I tried that and it doesnt take me to twrp or the factory reset screen
Did you try it a few times? I had to do it like 5 times before I got the factory reset option. Maybe you have the dreaded hardware failure bootloop.
Sent from my LG-H811 using Tapatalk
Happened to me. Every time I would use the hardware keys to get into TWRP it would go back to the bootloop. Most likely is hardware issue like he said ^^ I contacted LG and they told me to send it. It's on its way back to me
Sent from my LG-H830 using XDA-Developers mobile app
My phone started bootlooping on Saturday so i called T-mobile and i just received my replacement phone today. Now im afraid that they're going to find out that my phone was rooted because when u turn the phone on it says bootloader unlocked and if they even get into recovery mode it will have twrp installed
Sent from my LG-H811 using XDA-Developers mobile app

HELP!! Le2 x526 Not booting Up, nor Charging

Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Try to check your USB cable, most of the time charging issue is due to cable
shubham1358 said:
Try to check your USB cable, most of the time charging issue is due to cable
Click to expand...
Click to collapse
Cable is ok. I have another Le2 and it is charging with that cable very well
I am facing same problem. How you solve this issue? Blue led blinks after flashing any rom and bootloop.
xerol said:
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Click to expand...
Click to collapse
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Forthe55 said:
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Click to expand...
Click to collapse
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Brother same thing happened to me, a week ago. I cant say about your problem but my problem was due to faulty power button. Actually due to that reason my phone actually kept restarting itself. It showed red light blinking while charging and wasn't able to bypass the optimizing app screen. I also thought it was a software issue but actually it wasn't. I spent about 2 hours figuring out what the actual problem was. The problem was: As we know when power button is hard pressed for about 10-15 seconds it reboots itself.
Although the repair shop guy didn't put new power button but he added a tiny piece of paper in between the power button and body housing to prevent the issue and voila the problem was solved.
delltech1 said:
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Click to expand...
Click to collapse
Hi, Thanks. I actually did that first, flashing through qfil the same rom. it helped me to go to settings after umpteen attempts to go past language selection screen, and i was just able to oem unlock and enable usb debugging (actually after a 2nd partial failed flashing). the phone kept freezing within seconds of booting up. Now After i unlocked the bootloader and installing twrp and flashing many roms thru twrp, i am still having the same problem of booting up and freezing at start-up. cant flash again through qfil, as i will again loose the unlocked bootloader and twrp.
At least , now i can try different roms to see which can unbrick it. last one used was the twrp flashable rom based on eui (small eui by aurel) but it also freezes on language selection screen or beyond.
I am running out of ideas, lets see.
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
If nothing helps it can be only a HW failure, maybe the power button, try usb 2.0 port during the flash process, i had issues with 3.0 on my pc, if that doesnt help.try a different cable, no more suggestions, sorry.
delltech1 said:
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
Click to expand...
Click to collapse
My phone has been flashed multiple times by qfil method. And always it hangs at initial setup (so it boots up, but hangs at language selection or further up screens, before setup can complete and launcher could be loaded).
While trying to flash again with qfil once it stopped at 25 percent (because the battery went dead). Charged the battery and booted up the phone, and i was surprised it booted up. After 2-3 attempts i was able to reach the launcher screen and immediately enabled developer options and oem unlock / usb debugging. Only had few split seconds to do this and the phone froze again. After that i installed twrp and hence treying different roms. Most fail at setup.
Just tried MIUI 9PRO ROM. It also froze at setup multiple times, but once i was able to complete the setup and miui launcher is up , but it reboots or turn off the phone just after that. So cant do anything with the phone. Unsure of whether a newer bootloader will help in these freezing issues as i have been able to boot up at least in some roms only if for few seconds. Will try to tinker the settings of miui rom (if the phone let me do it before freezing/hanging). Lets see. Thanks for suggestions. More suggestions welcome, because i am still unsure weather this is a software or hardware related problem. I am guessing that it may have something to do with Google security as earlier i was getting msg that phone has been wrongly resetted and needs to verify with Google (but i couldn't get a chance to use the same account, as phone kept freezing at setup).
Did you fully charge the battery, if not let it fully charge in twrp. Flashing the roms in twrp works everytime or do you see any errors? Before you flash anything disconnect the usb cable.
---------- Post added at 09:54 PM ---------- Previous post was at 09:47 PM ----------
Try to flash the 21s bootloarder with modem, one zip using twrp. Go to fastboot mode and wipe modems. fastboot erase modem1st fastboot erase modem2st. Put the phone to flash mode and reimage with qfil. Before you do it write down both imeis, you can find them also on the original package on the backside. Also try to remove all sim cards from the phone and try a different cable. If nothing helps, hw issue, maybe the power button mention earlier in this thread.
After reflash skip everything at setup and reset phone to factory defaults. OEM is already unlocked, you dont have to do it again.
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Forthe55 said:
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Click to expand...
Click to collapse
Yeah sorry i screwed the command its fastboot erase modest1 modemst2, my bad.
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Forthe55 said:
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Click to expand...
Click to collapse
So you erased modems and reflashed with qfil right? If so i assume its a HW problem. Try the fix with the power button, i ran out of ideas
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
delltech1 said:
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
Click to expand...
Click to collapse
Did that also, the same problem. The phone freezes after the os is booted. I was wondering what is that isnt touched by flashing ( in download mode or fastboot mode or through twrp). I may need to tinker that. The roms are all fine in the sense they all stop at the same points. Something in the phones partition, which isnt touched by flashing? (There must be, as i flashed with qfil, the oem unlock remains, the bootloader didn't lock, and it remains unaffected by re-imaging)
Try this, maybe it helps:
https://forum.xda-developers.com/le-2/help/issues-installing-twrp-rom-le-s3-x522-t3618662/page2

Help me return to stock PLEASE!

Hi,
Using latest Odin I am trying to return to my phone to stock but cannot 
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
Use smart swirch recovery method in help tab. The process guide you to process. Dont worry it will be ok.
Sent from my SM-N950F using Tapatalk
---------- Post added at 07:05 AM ---------- Previous post was at 07:03 AM ----------
In more there is option of emergency software recovery, plug phone and it will help you.
Sent from my SM-N950F using Tapatalk
Try installing the last rom... one which is showing up in ur pc... remove any encryption if its there.... that should solve ur problem.....

Pixel 4XL Stuck On "Pixel Is Starting"

My Pixel 4XL no longer boots to home screen...it will reboot fine but gets stuck on PIXEL IS STARTING.
I've tried safe mode and recovery modes but not 100% sure what to do.
I want to avoid factory reset as I want to get some physical media off of the phone first. I tried connecting to a PC and selected USB File Transfer but it never would mount the drive.
Can I get my media off of this without a factory reset or can a recovery/safe mode option work?
If you don't do any mod to your phone, I think press power button longer and force phone reboot. Your problem can be fixed !
garak0410 said:
My Pixel 4XL no longer boots to home screen...it will reboot fine but gets stuck on PIXEL IS STARTING.
I've tried safe mode and recovery modes but not 100% sure what to do.
I want to avoid factory reset as I want to get some physical media off of the phone first. I tried connecting to a PC and selected USB File Transfer but it never would mount the drive.
Can I get my media off of this without a factory reset or can a recovery/safe mode option work?
Click to expand...
Click to collapse
If you are rooted try this...(assuming you installed some Magisk modules)
Once phone reboots and you are on PIXEL IS STARTING screen see if you can access settings via drop-down. If you can, go to Settings -> Apps -> Magisk. Once there you should have the option to open magisk. Once you open magisk go to the modules section and disable all the modules then reboot.
Try flash boot image magisk A core only
---------- Post added at 11:12 AM ---------- Previous post was at 11:11 AM ----------
Also try to flash sysytem, you have to make some change on Run all bat file. It will flash other partitions other than data
Once you've tried the us easier stuff as mentioned above or possibly following this post you can get it back by flashing the full image with the wipe removed. Your phone will come up like nothing happened other than if you were rooted it will be gone and you'll have to root again. There several guides you can reference if you're not familiar with the procedures.
krabman said:
Once you've tried the us easier stuff as mentioned above or possibly following this post you can get it back by flashing the full image with the wipe removed. Your phone will come up like nothing happened other than if you were rooted it will be gone and you'll have to root again. There several guides you can reference if you're not familiar with the procedures.
Click to expand...
Click to collapse
Agreed. Download the latest full image, modify the "flash-all.bat" file to remove the "-w" Then Boot the phone to fastboot and run the modified batch flash-all file, you should be good.
garak0410 said:
My Pixel 4XL no longer boots to home screen...it will reboot fine but gets stuck on PIXEL IS STARTING.
I've tried safe mode and recovery modes but not 100% sure what to do.
I want to avoid factory reset as I want to get some physical media off of the phone first. I tried connecting to a PC and selected USB File Transfer but it never would mount the drive.
Can I get my media off of this without a factory reset or can a recovery/safe mode option work?
Click to expand...
Click to collapse
Is you bootloader unlocked? If so, you can flash the factory image and remove the "-w" command as suggested above, but if your bootloader is not unlocked this will not be an option. If you are on a locked bootloader, you can sideload an OTA image (which really is a full factory image). This will not wipe your phone or do a factory reset. It will however replace your OS with a clean version. Hopefully that fixes the issue. If not, then you will have to do a factory reset in order to "clean out" the problem.

Categories

Resources