Develop Bugs

[Q] Stuck on white HTC EVO 4G Screen

Please see the attachment.
I have searched the forum for people with my issue, but no luck.
I was not ROOTED. My phone started to reboot itself everyday for one week. Three days ago, it rebooted and then never got past the white HTC EVO 4G screen. Kept rebooting. I searched and tried so many things that my head is about to explode. There are some horrible videos on YouTube. I downloaded the PC36IMG.ZIP from the RUU an HTC EVO 4G document from this site (i cant post links) but it's not working. I tried several RUU's with no luck. I dont want to root my EVO. Can someone help me reinstall the GingerBread OS that I had before this happened?
It's not under warranty and Sprint will not replace/fix it.

My phone is now UNLOCKED. I followed the htcdev.com procedure. I tried the PC36IMG.ZIP file again. It does not say Update fail. It just goes back to the HBOOT screen.

Try one these...
Deodexed Version ruu http://www.mediafire.com/?t7u904lm502vl7l
Odexed Version ruu http://www.mediafire.com/?krpdawqca8a58t1

Do I need to rename it to PC36IMG.ZIP and use HBOOT? I thought I needed PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.zip.
I used the 4.62.651.3 file, it seemed to be working, but then it did not give me any update prompt and went back to the HBOOT screen.

I'm not really sure if it matters but don't capitalize ".ZIP" when you reaname it or just remove it and just leave it PC36IMG

I tried both files. It loads the file, starts the process with the blue bar on the right side, states Checking..... Parsing.... and then returns to the HBOOT screen.

Tried all three files again (two from moreno4xl) and the PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_ 2.15.00.12.19_NV_2.33_release_234563_signed file with .zip lowercase. No luck.
After parsing.......goes back to HBOOT.
Are there any utilities that can actually check the hardware and see if the internal RAM is ok? Maybe the RAM is bad and no software will ever install.

gene12517 said:
I tried both files. It loads the file, starts the process with the blue bar on the right side, states Checking..... Parsing.... and then returns to the HBOOT screen.
Click to expand...
Click to collapse
If all you want to do is factory reset, have you tried the "CLEAR STORAGE" option in the HBOOT menu?
At this point, you're unlocked, meaning you can easily root and flash a custom ROM. I'd say that's a better solution (if you can get the ROM working).

I tried CLEAR STORAGE. No luck. I tried to put a recovery on the device.
D:\Android>fastboot flash recovery recovery-ra-supersonic-3.11-gnm.img
sending 'recovery' (4124 KB)...
OKAY [ 1.170s]
writing 'recovery'...
OKAY [ 1.676s]
finished. total time: 2.846s
D:\Android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.089s]
finished. total time: 0.089s
Pressed power on Recovery, and it still reboots back to the HTC EVO 4G white screen. I cannt even create a recovery partition on this phone. Is the ROM bad? Where do I get the PC36IMG.diag file?

Your partitions may have become corrupted in which case you need to replace it or send it out to be jtag'd jtag is probably the cheaper route as its only about 60$ shipped both ways
Edit: jtag takes about a week round trip and the work done google "jtag service" and look for a site called mobilevideos or something like that hes been jtaging alot of bricked et4g's lately
We are legion, for we are many
Sent from my Anonymous DeathStar in the depths of GalaXy S2

Thanks Evil. So you don't think I can do anything else myself?

If you cant get recovery to work probably not if you can get recovery loaded you can wipe the whole phone and flash a ROM which may fix it but your phone is acting similar to the perm bricks that were caused by the twrp 2.0 recovery which basically f*cked up the data partition on the nand chip making it unable to be written to however im not sure what could have caused this since you were unrooted but flash memory which is what the nand chip is does have a shelf life usually far longer than the average user will keep the device however there are always bad seeds that get out jtag forces the nand to accept a binary rewrite which repairs the bad blocks in the partition, its possible to jtag yourself however the software is ridiculously priced at somewhere around a grand and cracked copies usually are no good if you can even find one
Edit: mobiletechvideos is the name of the site doing the et4g im not sure if they do the evo but its a solid place to start i noticed today he dropped his price to $50 from $60
We are legion, for we are many
Sent from my Anonymous DeathStar in the depths of GalaXy S2

I don't need to have S-OFF to install recovery?

Are there any diag utilities that can be run?

Why doesn't ADB see the phone when fastboot does?
D:\Android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
D:\Android>telnet main1 5037
Connecting To main1...Could not open connection to the host, on port 5037: Connect failed
D:\Android>adb bugreport
error: device not found
D:\Android>adb root
error: device not found
D:\Android>fastboot devices
HT097HL09284 fastboot

Maybe I can recreate all the partitions on the phone? Is there a guide on how to do that properly?
Partitions:
Followings are a list of partitions on your android phone.
misc - misc partition -
recovery - Recovery Partition - This is where the original HTC recovery or Amon Ra's recovery or any other Recovery would go. Basically if you reboot into recovery it'll boot from here.
boot - This is your boot partition
system - This is where all your system information (ROM resides)
cache - cache (When you factory reset the phone, this area is wiped)
userdata - user data (like your login, your user settings etc) When you factory reset the phone, this area is wiped)

gene12517 said:
I don't need to have S-OFF to install recovery?
Click to expand...
Click to collapse
Not with the unlocked bootloader - you can be S-ON, but the recovery partition is still writeable.
gene12517 said:
Why doesn't ADB see the phone when fastboot does?
D:\Android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
D:\Android>telnet main1 5037
Connecting To main1...Could not open connection to the host, on port 5037: Connect failed
D:\Android>adb bugreport
error: device not found
D:\Android>adb root
error: device not found
D:\Android>fastboot devices
HT097HL09284 fastboot
Click to expand...
Click to collapse
That does sound very similar to the problem I had with the TWRP soft-brick. If you could get booted into a rooted ROM, you would be able to connect to adb over Wi-Fi, but without being able to flash a rooted ROM, I don't think there's anything you can do.
gene12517 said:
Maybe I can recreate all the partitions on the phone? Is there a guide on how to do that properly?
Partitions:
Followings are a list of partitions on your android phone.
misc - misc partition -
recovery - Recovery Partition - This is where the original HTC recovery or Amon Ra's recovery or any other Recovery would go. Basically if you reboot into recovery it'll boot from here.
boot - This is your boot partition
system - This is where all your system information (ROM resides)
cache - cache (When you factory reset the phone, this area is wiped)
userdata - user data (like your login, your user settings etc) When you factory reset the phone, this area is wiped)
Click to expand...
Click to collapse
Your problem is likely due to corruption, which flashing the misc partition should help to correct. But, you can't do that without adb, so your back to what I said above.
I don't know if there's anything you can do, to be honest.
P.S. adb doesn't work over fastboot.

UPDATE:
Before giving up I searched the internet again and found this.
http://forum.ppcgeeks.com/htc-evo-3d/147922-relocked.html
Procedure:
1. Enter FASTBOOT, and then connect to your computer (FASTBOOT USB will be shown)
2. Open command prompt in your computer
3. Relock your device by typing "fastboot oem lock" (you should know what is this if you HTC-unlock your phone before), the device will reboot.
4. Enter FASTBOOT again (you will see *** RELOCKED ***)
5. Apply the RUU
6. You device will be stocked
Note: The device must be relocked in order to apply the RUU.
I then ran the latest RUU and was getting very excited.......After 53% I got an error. Pulled the USB cord and saw the attachment. Reran RUU and got the same error. Turned the phone on and the only thing I see is a black background with HTC in the middle and four triangles in the corners.
Any suggestions?

I cant get back to unlocked now since its stuck in the RUU screen and the fastboot flash unlocktoken unlock_code.bin does not bring up the GUI on the phone....
Damn, this is complicated.

Sounds like it might be time for a replacement
We are legion, for we are many
Sent from my Anonymous DeathStar in the depths of GalaXy S2

[Q] [Help] Can't mount SD card, flash stock recovery, no RUU

Hey all, I'm looking for some help.
Here's the thing:
The problem started with what I think was a dying battery (2 yr old device) because I started to have some battery drain, screen frozen at short intervals at random times, insane heat... I was running AOSP at that time so I decided to go back to Sense to see if I could make it last a bit longer. Here's when things get strange: I flashed CWM 6.0.3.2 and then ViperX4.1.1 wuth Alex V 2 pa3 kernel. I did everything the same way I've done in the past two years, except this time after flashing the phone started to reboot itself out of the blue which made me think it was definitely the battery, but sometimes when it rebooted it wouldn't load everything, gave FC on some core apps (dialer, settings, etc) so I decided to wipe everything and reflash ROM and kernel. Stupid idea because things got worse and worse (gave FC on pretty much everything on first run, after reboot it wouldn't let me go past lockscreen, etc) and here I am today, a week later, still trying to fix this thing with no luck. I can boot to fastboot and go to recovery; I can't flash a ROM or restore a nandroid because CWM can't mount SD card I can't flash another recovery because it gives me an error and I can't flash a RUU because there's no RUU for 3.14.720.24, I cant' put anything in SD card from PC because large files keep on getting corrupted....
Really, I'm lost. Does anyone have any idea?

JuanArg said:
Hey all, I'm looking for some help.
Here's the thing:
The problem started with what I think was a dying battery (2 yr old device) because I started to have some battery drain, screen frozen at short intervals at random times, insane heat... I was running AOSP at that time so I decided to go back to Sense to see if I could make it last a bit longer. Here's when things get strange: I flashed CWM 6.0.3.2 and then ViperX4.1.1 wuth Alex V 2 pa3 kernel. I did everything the same way I've done in the past two years, except this time after flashing the phone started to reboot itself out of the blue which made me think it was definitely the battery, but sometimes when it rebooted it wouldn't load everything, gave FC on some core apps (dialer, settings, etc) so I decided to wipe everything and reflash ROM and kernel. Stupid idea because things got worse and worse (gave FC on pretty much everything on first run, after reboot it wouldn't let me go past lockscreen, etc) and here I am today, a week later, still trying to fix this thing with no luck. I can boot to fastboot and go to recovery; I can't flash a ROM or restore a nandroid because CWM can't mount SD card I can't flash another recovery because it gives me an error and I can't flash a RUU because there's no RUU for 3.14.720.24, I cant' put anything in SD card from PC because large files keep on getting corrupted....
Really, I'm lost. Does anyone have any idea?
Click to expand...
Click to collapse
Flash Philz 5.15.9 recovery and mount sd card only in this recovery this function work

Thanks a lot for you reply, I tried it but I got the following:
C:\fastboot>fastboot flash recovery philz_touch_5.15.9-endeavoru.img
sending 'recovery' (8198 KB)...
OKAY [ 1.109s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: err = 0xa)
finished. total time: 7.896s
--EDIT: Now everytime I try to go to recovery the phone goes back to fastboot menu. What the hell...

JuanArg said:
Thanks a lot for you reply, I tried it but I got the following:
C:\fastboot>fastboot flash recovery philz_touch_5.15.9-endeavoru.img
sending 'recovery' (8198 KB)...
OKAY [ 1.109s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: err = 0xa)
finished. total time: 7.896s
--EDIT: Now everytime I try to go to recovery the phone goes back to fastboot menu. What the hell...
Click to expand...
Click to collapse
are your bootloader is unlocked? And rename the gole name to recovery.img dont use so many symbols
EDIT: Now I read for your problem on other places and the solution is to try again and again to flash the recovery

OK, now this is starting to get pretty insane. I rebooted to bootloader to continue trying to flash a recovery and it shows ***LOCKED*** as if I had never unlocked it.
If I go to fastboot and try to flash it gives me a "not allowed" error when attempting to write recovery.
I'm starting to think that the battery failed and somehow shorted something in the mobo.

JuanArg said:
OK, now this is starting to get pretty insane. I rebooted to bootloader to continue trying to flash a recovery and it shows ***LOCKED*** as if I had never unlocked it.
If I go to fastboot and try to flash it gives me a "not allowed" error when attempting to write recovery.
I'm starting to think that the battery failed and somehow shorted something in the mobo.
Click to expand...
Click to collapse
just unlock your bootloader and flash the recovery

I would, but as soon as I rebooted it went back to UNLOCKED and back to post #3... I'm close to smash this thing against the wall. I'll keep trying to flash the recovery.

Phone got in APX mode. Bye bye HOX, it was fun.

JuanArg said:
Phone got in APX mode. Bye bye HOX, it was fun.
Click to expand...
Click to collapse
Exact same thing happened to me... Didn't even get to try lollipop :l

I had a similar problem last week, what I had to do was to unlock the bootloader, then I flashed TWRP recovery and I mounted the SD with MTP enabled. Nothing happened in the first 2 or 3 minutes, and I was getting insane until TWRP did the magic and the PC recognized my hox as a MTP device, I copied a rom and I flashed it with the recovery and everything is fine right now. I hope this is helpful for you

dario_pet said:
I had a similar problem last week, what I had to do was to unlock the bootloader, then I flashed TWRP recovery and I mounted the SD with MTP enabled. Nothing happened in the first 2 or 3 minutes, and I was getting insane until TWRP did the magic and the PC recognized my hox as a MTP device, I copied a rom and I flashed it with the recovery and everything is fine right now. I hope this is helpful for you
Click to expand...
Click to collapse
my problem is also same............
but in my hox twrp not working.. actually ..touch not working...
what to do......

Nexus stuck in boot loop - unrooted - Backing up photos from bootloader or recovery

Hi.
Apologies if this is a very naive question, I am not particularly familiar with mods, roms and so forth.
I have rooted another phone in the past, but that is all.
The situation:
- Samsung Galaxy Nexus
- Not rooted/unlocked. Stock android automatically updated to the latest Android version supported
- Android developer option NOT set in settings
- Stuck in a boot loop: boots to android and then after a few seconds reboots, so no time to do anything
- Not sure how it happened, I had it for years, it was in my pocket and suddenly started doing that.
- Android fastboot and recovery loads up no problem
- I have tried anything I could find online to fix it: deleted cache, rebooted in safe mode, removed battery for 10 hours
- Nothing seems to fix it, it keeps rebooting
- I want to try a factory reset, but my family photos are in the phone
- Google synch seems to have stopped functioning for this device a year ago, all my 2016-17 photos and videos are locked in the phone.
Admitting there is nothing to do about the loop problem:
Is there any way I can copy photos and videos via usb while in recovery mode?
After I will reset the phone via recovery menu, hoping it will fix it. IF that does not fix it, I will flash another rom in. But I really do not want to wipe my data before backing them up.
I am assuming the answer is no, you cannot access the internal memory in fastboot/recovery unless your phone is rooted.
But I would like an expert opinion before I resolve to wipe one year of photos and videos which I will regret losing.

@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards

____Mdd said:
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
Click to expand...
Click to collapse
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?

mcaldo said:
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
Click to expand...
Click to collapse
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..

____Mdd said:
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
Click to expand...
Click to collapse
Thanks for the advice.
I followed the instructions closely, and nearly got there.
adb devices returns
#serialnumber sideload
so all good
but adb pull /sdcard returns
adb: error connect failed: closed
I tried several other commands with no success
kill-server and start-server work fine but do not solve the problem
adb usb returns
error closed
So, I am starting thinking that the problem is in the bootloader being locked.
However, if I unlock it, it will be wipe all my data, I understand?
Googling about it, I found this:
The behavior is status-by-design. Your stock recovery is not designed to grant shell access. Your only choice here is to somehow manage to flash a custom recovery. – Firelord Dec 30 '15 at 14:19
3
To achieve something similar to what @FireLord suggested: TWRP can be booted on many devices without being installed. For that, find a matching image, then boot to the bootloader and run fastboot boot twrp.img. Btw: you can check with fastboot devices resp. adb devices whether a device is visible to the corresponding tool. – Izzy♦ Jul 8 '16 at 19:40
So I understand one could boot TWRP without installing it, but I am not sure if that means I could do that with the bootloader locked?
I found WugFresh nexus root toolkit which seems to do that, among many other things, but again it warns that the phone must be unlocked (using the android build "Android *.* Any", I did not know what else to choose, not sure if that makes any difference as for locked/unlocked requirements)
EDIT: my fastboot screen reads "FASTBOOT STATUS - Failbootloader locked" as the last line, when trying to run TWRP without installing.

Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.

____Mdd said:
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
Click to expand...
Click to collapse
What actually you did ? Why it went into bootloop ???
Click to expand...
Click to collapse
A very good question, to which I have no answer, unfortunately.
The phone was used by my wife for 2 years and then by me for other 2. I recently changed the battery.
Never rooted or unlocked. No unusual apps installed. I am a very basic user, as you might have guessed, and being my only phone at the moment, I really would not risk experimenting with it.
It went very slow over the last 4 months, so I was planning to reset it.
I put in my coat pocket for a few hours, when I took it out it had a train ticked stuck to the screen and was quite warm and on the lock screen. It froze, so I took the battery out and restarted it. From then on it is stuck in a loop, not sure why really.
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex
Click to expand...
Click to collapse
That's good to know. I'll research more than.
It seems there might be a problem with the fastboot drivers on my computer, even selecting them from device manager did not work. Win7 refuses to install. The ADB drivers in theory work fine though.

If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...

____Mdd said:
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
Click to expand...
Click to collapse
Thanks so much.
Looking at google's documentation on the nexus:
You can remove data from your Pixel phone or Nexus device by resetting it to factory settings. Resetting to factory settings is also known as formatting the device or doing a "hard reset".
If you're factory resetting your device to fix an issue, make sure that you've tried all other troubleshooting options first. Find out how to troubleshoot your issue.
Important: Performing a factory reset will erase all data from the device.
Click to expand...
Click to collapse
It would seem that indeed all data will be removed.
This point, I will research a bit more into drivers, in case that is what it's preventing adb pull from working.
I really need a working phone, so if that fails I will hard reset, then unlock, root, flash in an alternative bootloader and perhaps a rom, and put ubuntu touch in dual boot. That will hopefully prevent me from loosing data in the future.
Sorry, this is out of topic to my question, but, , could you suggest any stable, solid rom for the nexus?
I read good things of CM12, and I ran into one which seemed to do to quite well with split windows, but I do not remember the name right now.
EDIT: I remember the name of the rom now, it's https://omnirom.org/about/

A last question if you can..
I tried to solve my boot loop problem by sideloading an update from google (maguro yakju yakju-jwr66y-factory-4cadea65.zip)
It loaded it fine but then failed because the installation it says it is not signed.
Basically, being a stock bootloader recovery from Samsung, it will only sideload OTAs from samsung, not the stock ones from google..
I cannot find the samsung ones anywhere, not for the nexus anyway, just the newer devices..
By any chance do you know where I could download proper Samsung OTA zip updates for the nexus?

Well, I talked with an android developer who confirmed that, unless you have a friend working in criminal forensic technology or similar, there is no way to get around a lock on this phone to pull data out.
So, sadly, I have wiped my phone by unlocking it, flashed TWRP and then omnirom with gapps.
My photos are gone, including a bunch of stuff my kid had made and asked me to photograph for safeeping. Very safe indeed
He kept asking me why they make the lock like that, instead of allowing some kind of password, perhaps he has a point.
So, it is quite unlikely that somebody who knows as little as I did will ever read this *before* finding themselves in the same situation.
But if you do, back up your data, unlock and flash TWRP, clockworks or some alternative, and thank yourself if and when disaster strikes..

@mcaldo wiping data/factory reset in STOCK RECOvERY will wipe everything... There is very few chances to get backup...
And yeah i found something interesting..
You can flash system.img.. only system files will be corrected not anything else..
Get appropriate zip from here : https://developers.google.com/android/images
Now take system.img to ADB/Fastboot folder ( i assume you know how it works )
Just go "Fastboot flash system system.img"
It will rewrite system partition..
Another one:
See downloads on this thread..
One says NON-WIPE, if you want me to try that zip, i will again require time for that. See here : https://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------
I don't saw your reply, it was on next page.. its sad... Sorry i am late..

Possibly Bricked?

Hey all. Hopefully someone can provide a little assistance with this..
TLDR; Phone was fine, this morning it went into a bootloop. Tried restore which didn't work, tried wiping which didn't work, wipe everything and installed a new factory image and now it still won't boot and recovery is giving "no command" but I can still see everything with fastboot.
So a few months ago I rooted my Pixel Xl and flashed a "official" 8.1.0 ROM on it along with TWRP and Magisk. Everything was going fine and then about a week ago my phone shut off and wouldn't turn back on. I had to hold the power button about thirty seconds for it to come back. That was the only issue until this morning. This morning the same thing happened, the phone had shut off at some point last night while it was plugged in and this morning it was a black screen. Again, I held the power button down for about thirty seconds until it booted up, but this time a couple minutes after it booted, it shut back off again. Rinse and repeat and every time the time on was shorter and shorter until it just got to the Google boot screen and would freeze up and shut off.
After playing with it for a little while trying to figure out what was going on, I tried to do a factory wipe/reset. That didn't resolve anything. I booted back into TWRP and tried to do a restore, but about 80% of the way through it froze up. I restarted the device and tried restore again, but it froze up towards the end once more. So I tried doing a wipe, then a restore but only the first two boxes checked, system and something else.. It completed successfully, but was still boot looping just like before.
Then I thought maybe it was something internal and did a full wipe of everything.. Still no luck. Then I figured since there wasn't much to lose, I pushed the newest factory image to the phone using platform tools/fastboot.
Now what I get is when I try to start the phone it'll go to the Google logo, then restart, then do that once more and then it will go to a little screen with the Android on his back and an exclamation saying "No command", which I'm assuming is recovery mode since it does the same thing when I try to go there.
I can access fastboot still and all the system menus, I don't care about losing my data obviously and I just need my phone to work. Is there anything I can do?
In the bootloader my information is..
BL: 8996-012001-1808030001
Baseband: 8996-130181-1806061856
Product/Variant: marlin-US-PVT
Serial Number: HT68Hxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 32GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED

premedicated said:
Hey all. Hopefully someone can provide a little assistance with this..
TLDR; Phone was fine, this morning it went into a bootloop. Tried restore which didn't work, tried wiping which didn't work, wipe everything and installed a new factory image and now it still won't boot and recovery is giving "no command" but I can still see everything with fastboot.
So a few months ago I rooted my Pixel Xl and flashed a "official" 8.1.0 ROM on it along with TWRP and Magisk. Everything was going fine and then about a week ago my phone shut off and wouldn't turn back on. I had to hold the power button about thirty seconds for it to come back. That was the only issue until this morning. This morning the same thing happened, the phone had shut off at some point last night while it was plugged in and this morning it was a black screen. Again, I held the power button down for about thirty seconds until it booted up, but this time a couple minutes after it booted, it shut back off again. Rinse and repeat and every time the time on was shorter and shorter until it just got to the Google boot screen and would freeze up and shut off.
After playing with it for a little while trying to figure out what was going on, I tried to do a factory wipe/reset. That didn't resolve anything. I booted back into TWRP and tried to do a restore, but about 80% of the way through it froze up. I restarted the device and tried restore again, but it froze up towards the end once more. So I tried doing a wipe, then a restore but only the first two boxes checked, system and something else.. It completed successfully, but was still boot looping just like before.
Then I thought maybe it was something internal and did a full wipe of everything.. Still no luck. Then I figured since there wasn't much to lose, I pushed the newest factory image to the phone using platform tools/fastboot.
Now what I get is when I try to start the phone it'll go to the Google logo, then restart, then do that once more and then it will go to a little screen with the Android on his back and an exclamation saying "No command", which I'm assuming is recovery mode since it does the same thing when I try to go there.
I can access fastboot still and all the system menus, I don't care about losing my data obviously and I just need my phone to work. Is there anything I can do?
In the bootloader my information is..
BL: 8996-012001-1808030001
Baseband: 8996-130181-1806061856
Product/Variant: marlin-US-PVT
Serial Number: HT68Hxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 32GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED
Click to expand...
Click to collapse
Ok, so I'm assuming you have the latest factory image currently downloaded on your PC and extracted all the files to the same folder as fastboot/ADB. Hook up your phone to the PC and boot into the bootloader on the phone by powering on while holding in Volume Down + power. In the folder where you have fastboot on your PC, hold down shift and right click the mouse and select open command prompt (or powershell, depending on Windows version). Type fastboot devices to make sure your phone is being seen by your PC. If it is, type fastboot erase system, after that runs type fastboot erase userdata, once that runs type fastboot erase system, and finally fastboot erase boot. Then type fastboot --set-active=b , and run the same commands on that slot. Then type fastboot reboot bootloader, and when it reboots to bootloader type in flash-all.bat . That should wipe everything properly on both slots and install the latest factory image. If that doesn't work then I would say there's definitely a hardware defect. Also if it doesn't work I would try a different port on your PC.

Phalanx7621 said:
Ok, so I'm assuming you have the latest factory image currently downloaded on your PC and extracted all the files to the same folder as fastboot/ADB.
Click to expand...
Click to collapse
Inside of the factory image file, once unzipped there is another zip file contained in there with the same name. Do I need to extract that as well since it has options such as boot.img, keymaster.img and several other .img files in it, or do you just extract the main files containing bootloader-marlin-8996-012001-1808030001.img, flash-all.bat, etc.?
Phalanx7621 said:
Then type fastboot --set-active=b , and run the same commands on that slot.
Click to expand...
Click to collapse
Awesome, thanks for the reply. Question though since i'm not entirely sure about the slots. Since it's already reading it as slot B, will I change the active to slot A at some point or will running those commands in slot B erase slot A, as I understand that it basically works in whatever slot is not active.

It should detect slot A by defualt, but as long as you run those commands for both slots you'll be wiping it clean. Keep in mind we aren't talking about TWRP, we're in fastboot. And no, once you extract the files from the zip you don't need to extract the other file inside of it. The flash-all command will read it and do the proper magic. Just make sure the extracted files are in the folder with fastboot/ADB.

Well, I followed it to a T with your first post and I made it further than before. I got it all the way to where it asked if I wanted to copy files and then it froze. Restarted and it made it to finding my sim before it restarted and then it makes it to a different point before restarting, which is further than I made it before, however it still hasn't made it all the way into the software, so I guess I'm pretty well screwed unless it's something with Slot A. But I'm pretty doubtful at this point.
Update: Now it won't make it past the Google logo anymore again...

Ok, so it still isn't working. I'm going to try flashing the 8.1.0 image in a bit and see if maybe that some how resolves it. Doubtful, but it's my last step before I go spend a thousand dollars buying a new phone..
A couple questions though, when I flash-all I'm getting a lot of "Archive does not contain 'xxxxx.xxx'" errors. Archive does not contain boot.sig, boot_other.img, dtbo.img, dt.img, odm.img, product.img, product-services.img, recovery.img (this one seems important..), super.img, system.sig, vbmeta.sig and vendor.sig are all missing from the archive. This normal?
Also, I can play around in bootloader and I could in TWRP before it was erased for hours with no reboot or anything, but once the OS starts to load or loads, that's when it freezes up and fails. If it was a hardware issue shouldn't it be restarting regardless of what I'm running under?
Just trying to expend all my options before spending more ludicrous amounts of time for a piece of hardware that can just die without reason.

Help..Pixel 2 XL..Android 10 update..Lockscreen flickers..Cannot load android system

Hello everyone,
This saga started after I updated my Pixel 2 XL to Android 10 about a month ago. My phone had become a bit laggy for a while so I was keenly waiting for the update since it promised to smoothen things up for but post the update nothing changed so I was a little disappointed. Anyways, one fine day when I tried to change my lockscreen wallpaper through an app which I had been using for a while, 'Wallpaper Modder' (downloaded from the Google Playstore) nothing happened. I tried again and still, nothing happened. So I simply restarted my phone since it seemed a little laggy. Since then it goes through the usual bootup sequence with Google on the screen, then the Google logo (G) with 'Powered by android' at the bottom but then the lockscreen doesn't load. Instead, I get a flashing time, battery symbol & percentage and the back arrow (bottom left) on the screen, and after a while it restarts and shows up the Android Recovery screen:
Android Recovery
google/taimen/taimen
10/QP1A.191005.007.A1/5908163
user/release-keys
Use volume up/down and power.
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.
Try again
Factory data reset
The reason I am asking for your help is that I do not want to lose my data that I have on the phone by doing a factory data reset. FYI, I do have my photos backed up to Google Photos but there's more stuff in there that I didn't backup. :|
Please note that I have already taken the following troubleshooting steps after going through a lot of forums since then.
1. Restart the phone in Safe Mode
2. Soft Reset - Restarting the phone 7 times continuously
3. Sideload the October OTA update again using ADB and recently the November update as well.
PS: I have stock android and have not tweaked my phone in any manner whatsoever. Hence the bootloader is locked. I simply had the developer options enabled. But I am unsure if USB debugging is enabled or not.
Please help!!!

anubhavsood said:
Hello everyone,
This saga started after I updated my Pixel 2 XL to Android 10 about a month ago. My phone had become a bit laggy for a while so I was keenly waiting for the update since it promised to smoothen things up for but post the update nothing changed so I was a little disappointed. Anyways, one fine day when I tried to change my lockscreen wallpaper through an app which I had been using for a while, 'Wallpaper Modder' (downloaded from the Google Playstore) nothing happened. I tried again and still, nothing happened. So I simply restarted my phone since it seemed a little laggy. Since then it goes through the usual bootup sequence with Google on the screen, then the Google logo (G) with 'Powered by android' at the bottom but then the lockscreen doesn't load. Instead, I get a flashing time, battery symbol & percentage and the back arrow (bottom left) on the screen, and after a while it restarts and shows up the Android Recovery screen:
Android Recovery
google/taimen/taimen
10/QP1A.191005.007.A1/5908163
user/release-keys
Use volume up/down and power.
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.
Try again
Factory data reset
The reason I am asking for your help is that I do not want to lose my data that I have on the phone by doing a factory data reset. FYI, I do have my photos backed up to Google Photos but there's more stuff in there that I didn't backup. :|
Please note that I have already taken the following troubleshooting steps after going through a lot of forums since then.
1. Restart the phone in Safe Mode
2. Soft Reset - Restarting the phone 7 times continuously
3. Sideload the October OTA update again using ADB and recently the November update as well.
PS: I have stock android and have not tweaked my phone in any manner whatsoever. Hence the bootloader is locked. I simply had the developer options enabled. But I am unsure if USB debugging is enabled or not.
Please help!!!
Click to expand...
Click to collapse
First, try fastbooting the current boot.img to both slots with..fastboot flash boot boot.img --slot=all
If that doesn't work, then try fastbooting the factory image, not the OTA, one slot at a time with the -w removed from the flash-all.bat file.
If neither of those 2 work, then you'll likely have to do a factory reset

Badger50 said:
First, try fastbooting the current boot.img to both slots with..fastboot flash boot boot.img --slot=all
If that doesn't work, then try fastbooting the factory image, not the OTA, one slot at a time with the -w removed from the flash-all.bat file.
If neither of those 2 work, then you'll likely have to do a factory reset
Click to expand...
Click to collapse
Unfortunately, his bootloader is locked; so I can't imagine flashing the full factory is a viable option....
I'm wondering if it'll do anything by switching the slots and/or updating via an OTA/sideloading... I don't know the commands for it offhand and/or if it can be done with a locked bootloader....

Badger50 said:
First, try fastbooting the current boot.img to both slots with..fastboot flash boot boot.img --slot=all
If that doesn't work, then try fastbooting the factory image, not the OTA, one slot at a time with the -w removed from the flash-all.bat file.
If neither of those 2 work, then you'll likely have to do a factory reset
Click to expand...
Click to collapse
Didn't work...this is what I get...
PS C:\adb> fastboot flash boot boot.img --slot=all
Sending 'boot_a' (40960 KB) OKAY [ 0.563s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
PS C:\adb> flash-all.bat
Sending 'bootloader_b' (36352 KB) OKAY [ 0.601s]
Writing 'bootloader_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.006s
Sending 'radio_b' (60388 KB) OKAY [ 1.005s]
Writing 'radio_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.006s
--------------------------------------------
Bootloader Version...: TMZ30h
Baseband Version.....: g8998-00012-1905270706
Serial Number........: 712KPMZ1266923
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
Press any key to exit...

simplepinoi177 said:
Unfortunately, his bootloader is locked; so I can't imagine flashing the full factory is a viable option....
I'm wondering if it'll do anything by switching the slots and/or updating via an OTA/sideloading... I don't know the commands for it offhand and/or if it can be done with a locked bootloader....
Click to expand...
Click to collapse
Looks like it's a lost cause...I have even tried to boot TWRP but I get the same error 'Flashing is not allowed in Lock State'
PS C:\adb> fastboot flash recovery twrp-3.3.0-0-taimen.img
Sending 'recovery' (40960 KB) OKAY [ 0.348s]
Writing 'recovery' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
PS C:\adb>
Apart from this I was trying to uninstall the Wallpaper Modder app in the hope that the default lockscreen wallpaper might get loaded when I bootup the phone but unfortunately the I get 'error: closed' when I try to run any adb shell commands...
Anyways, I seriously feel that there should be a way to fix this. Because I am pretty sure it's the custom lockscreen wallpaper that messed up my phone post the update. I don't remember where but I did come across a post where this has happened to someone else as well. This situation is pretty lame if you ask me. I expected more from Google.

simplepinoi177 said:
Unfortunately, his bootloader is locked; so I can't imagine flashing the full factory is a viable option....
I'm wondering if it'll do anything by switching the slots and/or updating via an OTA/sideloading... I don't know the commands for it offhand and/or if it can be done with a locked bootloader....
Click to expand...
Click to collapse
Ah crap simple man, I overlooked that in his post. My old eyes miss things from time to time. However, you are correct....he's jacked. FDR time

Exactly same thing here just that I haven't installed any app recently. Phone starts, flickrs on login screen and restarts and goes to recovery screen. I don't want to factory reset w/o backing up my data. Is there a way to recover my photos atleast ?

Sharing my experience while looking for answers: Twice this week, I woke up to find my Pixel 2 XL bricked. Completely stock, not rooted.
"Cannot load Android system. Your data may be corrupt. If you continue to get this message, you need to perform a factory data reset and erase all user data stored on this device."
When retrying, both in safe and regular mode, the lock screen flashes. If I'm quick enough to get it unlocked, it just shuts down. One time, I managed to get a "System UI" crash dialog.
I attempted flashing the latest Android 10 OTA (without a factory reset) and it did not resolve the issue. Since I have everything backed up (except my 2FA tokens...lesson learned) I went ahead and did a factory reset. Spent an entire day getting my phone set back up, and this morning I woke up to the same issue. I'm new so I can't link the video, but look for YouTube Video ID: NLrI6bIsTNM
I have a message in to support since my phone should still be under warranty (bought in June of 2018).

I am having same issue, Factory data reset then next morning, it happens again. is there any way to fix this? No more warranty for my phone

huteri said:
I am having same issue, Factory data reset then next morning, it happens again. is there any way to fix this? No more warranty for my phone
Click to expand...
Click to collapse
Add me to the club - same issue on my Pixel 2 XL. First time it happened was on 9 March 2020, now it's done it again twice in 24 hours.
Mine is doing exactly the same thing as xraydrx's phone is - screen flashes on and off for a minute or so before it goes back to the recovery screen.

Same problem - 2 Phones!
Would you believe I now have this same issue...and it's happened 3 times on 2 different phones?
Each time it happens overnight. First was March 14th into 15th, and the second was 11 days later (March 25th into 26th). I requested a RMA, received it March 30th, set up the new phone with the backups I had from my old user profile...and now basically 11 days later (April 10th into 11th) it has happened once again on the new phone. So I'm basically willing to say that it's not a hardware issue.
Sideboots don't work, mounting /system doesn't work...each time it needs a full factory reset.
Curiously, I thought I posted about this in the Android Community forums, but that post now appears to be missing.
Only thing I can think of was brought up earlier in this thread with wallpaper modding - I was using the "cityscapes" wallpaper setting and telling the phone to download a new wallpaper every day. Going to not do that this time around; we'll see if the phone can make it past 11 days.

Same issue. Something with one or more of their new updates. It actually happened -during- (not immediately after) the last update, and I did the factory reset (OUCH! I had that whole 128GigaBytes FULL of... well, God knows what. And God only knows now because I can't remember all the junk I had on there but I know that a lot of it was not replaceable. Videos, movies, personal videos and photos, music, my own music and recordings and etc. etc. etc.
Thought I was good, I did the factry reset and unlocked bootloader, but didn't take the time to install TWRP nor a custom ROM, nor even root. Just unlocked bootloader. Welp, it just happened again now. Reboots, the lockscreen flashes, then disappears, then flashes and disappears, a few times, then the phone reboots and goes to the recovery screen stating that I may be corrupted and asking if I want to try to reboot again, or factory reset.
This is clearly happening to many of us, so it's a software issue, but one that we have not been able to solve yet; and one that Google seems unwilling to help us with. I am already on my first Refurb replacement (I had the vertical pink line issue that eventually grew into a large vertical yellow bar or something. Phone was ugly and began to become unusable. So I ate the bullet and paid the hundred or so to get a replacement Refurb. Not sure what that gets you exactly. It looked brand new and had plastic all over it, but who knows. I guess they'd HAVE to replace the battery, and ensure it was working correctly and wiped of any data. So hey, I was fine with it. Until this. Not sure if they'll throw me another phone at this point. I think they will give you 2 in every calendar year, as long as you keep paying for that damn insurance. I'm sure I've already given them enough insurance payments to cover a new Pixel 4 XL at this point...
Can anyone help me avoid another Factory Butt-Rape? I have a bunch of inspired musical recordings, drone videos, and sentimental photos that I'd really like to keep. And all this covid19 documentation...! Unless we can factory reset the entire planet, coronavirus itself, all of the lost lives, and our global economy... well, then I'd much rather find another way out of this bootloop. Thanks...

Grrrrr... I ended up doing another factory reset. Couldn't get the Pixel 2 xl to show up in adb devices. Screw it. Sucks because I lost another batch of important, non-replaceable stuff. Is this gonna keep happening? It's been over a month since the first time. I think I'm going to root, install a custom recovery (TWRP), and maybe even a custom ROM based on the latest version/security patch of Android (Pie?). Any suggestions? Anyone figure out how to fix this without a factory reset?

It's happened 3 or 4 times now, Factory Reset each time. And every time I tell myself, I have to root and install TWRP and create a nandroid backup, etc. and every time I've skipped it and regretted it. Like now. My phone is so empty after these resets that this may be my new norm. Or I'll somehow get to the bottom of it, and actually install TWRP, etc.
4th times a charm? I'm surprised more people aren't posting on this thread because I'm starting to see reference to this issue on a number of different forums and it looks like Google done messed us up good this time (possibly in combination with a number of apps, but still....).
Anyone else having this issue? ANyone solve it? Post! Post! Post! The more people report this the better chance we have of getting big G's attention for a fix....
THanks!

have you tried cleaning / stopping digital wellbeing? That produced me some bug, but when I reinstalled it the bugs gone