Database Users

Nexus 4 stuck on boot screen after update

Need some help.
I just sideloaded the 4.3 update to phone and now it's stuck on the 'X' loading screen.
My phone was rooted, but all stock (including the bootloader). I used the sideload ADB command and everything went fine, but the phone now won't boot.
How do I fix this?

did you data wipe(factory reset) before flashing?? if not, you have too.

I applied the OTA...didn't think I had to
Any idea on how I fix it now?
Really don't want to lose all my data

Install a custom recovery and wipe or apply factory image

favaroooo said:
Install a custom recovery and wipe or apply factory image
Click to expand...
Click to collapse
Is there a way I can fix it without wiping everything?

theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
I do not think because you have to change recovery you must unlock the bootloader and unlock bootloader wipe the phone

theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
no, its the data(and other stuff) causing it not to boot. same thing when flashing custom rom, you wipe when fkashing different roms. and going from android 4.2.2 to 4.3, theres many changes, enough to consider it a different rom.

Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.

theprodigy85 said:
Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.
Click to expand...
Click to collapse
are you flashing a zip or an img file??

simms22 said:
are you flashing a zip or an img file??
Click to expand...
Click to collapse
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...

Try to restore using the factory image

theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
yea, the zip youd want to wipe data/factory reset, then flash the rom. dirty flashing wont help since the changes are big enough.

theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
I bought my ole lady a Nexus 4 for Valentines day, anyway, today she got the OTA update and let it install the update. Now mind you she is 100% stock, adb debugging was not enabled, and her bootloader was still locked. (She would not let me touch her Nexus 4 lol) When the device rebooted it stuck on Android Upgrading finishing boot. So I said well let me see what I can do, this is what I did to fix it.
I use only Ubuntu so this may not work on windows i do not know. I Booted the device to the bootloader, connected it to my laptop via USB. I opened a terminal and typed in "sudo fastboot devices" and entered my password when promted and this gave me the device ID and fastboot letting me know fastboot was working. I then typed in "sudo fastboot reboot" and the device rebooted but was stuck on the bootanimation. I opened the internal storage up on my laptop in my file explorer and made a copy of her internal storage. Next I booted the device back into the bootloader then opened a terminal and typed in "sudo fastboot oem unlock" and the device gave me the unlock warning and the yes or no options. I selected yes so it would factory reset. After it did the factory reset the device reboot and booted to the setup welcome screen. Hope this helps others, also thanks to my good good friend Ljjehl for reminding me to use "sudo".
Edit: If you open the command promt with Administrative permissions in Windows this will work in Windows as well. Go to C:\Windows\System32\cmd.exe and right click on the cmd.exe file and select run as administrator. Then CD to the location with your fastboot.exe command. Thanks to another good friend TheBr0ken.

Thanks for the help...
I just ended up flashing each of the 4.3 components from the factory image. Just annoyed that I lost everything...

I'm stuck at the same screen. I received the OTA update, I didn't do anything special. My phone is unlocked and rooted (or WAS) but that was months ago, the rest is stock.
I think having encryption on my phone may have made it do this. I don't think Google anticipated doing the update properly for encrypted phones. Now I fear I've lost everything because even if I could connect, all data is encrypted...

similar problem
After starting to OTA update it was going smoothly, i was making breakfast, came back to find my screen at the "starting apps" screen frozen. The little circle that rotated wasnt doing anything so i left it there for awhile longer and still nothing. It would not move off that screen so i held power button down and restarted. now its stuck at the X screen also.

Yeah, I'm stuck there too. Already tried Factory Rest, didn't work. So what can I do?

I was on stock 4.2.2 and unrooted. I used the 'Google Services Framework' hack to force the 4.3 OTA update. The update downloaded successfully, phone restarted to apply the update and then restarted again. And now its stuck at the Google screen and keeps on restarting :crying:
I dont have the USB drivers installed on my PC too.

Same Problem
I have a nexus 4 (stock and unrooted),after 4.3 update,it is lagging during phone lock on/off (2 sec/5 sec).Hence I restarted my phone,and it stuck at "x" logo.Did clean data 3 times and then its working.
The problem is,in 2 days,I have experienced and done above thrice?
What could have gone wrong?

Hi guys,
I've just found how to correct this problem. All you have to do is to correctly wipe your phone before flashing factory image.
So :
Fastboot erase boot
Fastboot erase recovery
Fastboot format cache
Fastboot format system
Fastboot format userdata
I've just unbrick a n4 this way 15 minutes ago.
I have found the problem in recovery where you can see error log saying "cannot mount cache"
So formating correct the issue.
Hope it can help, fingers crossed.
Sent from my Galaxy Nexus using xda premium

[Q] Need help! Did OTA update to 5.0, stuck in bootloop!

I need some major help
My N7 2012 was stock, never rooted. I had only installed OTA updates. Yesterday, the OTA update for Lollipop appeared, and I installed it.
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
I've also tried getting it into fastboot, and I can issue fastboot commands. However, I've never unlocked the bootloader. And when I try to unlock it now, I get the screen that says "This will void your warranty are you sure?" But when I select Yes, fastboot's console says "Failed", and it remains locked.
If I go into Recovery, it just says "No commmand"
I need some help from the geniuses on this forum. To me it seems like an app running at startup is causing the crash, so if I could just get it to Safe Mode, I could figure it out and uninstall it. Hell, I'd be fine w/ a total wipe at this point. Just something to get it working again!
Thanks in advance!

Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.

Didn't work
bubba949 said:
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Click to expand...
Click to collapse
I tried using the Nexus toolkit, using Flash to Stock/Unroot in Bootloop mode, and it didn't work. A few sections succeeded, but most of the sections said "FAILED". Even after performing this, it still wants to boot to my normal desktop, so I know it's not re-flashing a thing.
I wish I knew more about this. I can get into fastboot by going to Power+VOL- but because it won't stay on the desktop, adb commands are a no-go. Is there something in the Advanced section of the Nexus Toolkit that will let me do a reflash? I'm afraid of just poking and trying things for fear of truly bricking it.
Thanks.

Sorry just re-read your last reply didn't realise you can't do adb commands, if you get to a point when you can then below may help...
I had a similiar issue caused differently what i did was to go to this link
http://forum.xda-developers.com/showthread.php?t=1907796
Downloaded the bootloader from JWR66V the guy mentions in his thread he mentions the same issue that i had which is when i tried to flash a stock or custom rom i kept getting messages about invalidstate on bootloader then the system and userdata images would fail when i tried to install...
In the end i downloaded the stock JWR66Y rom, replaced the bootloader image with the one mentioned above, i had to flash the seperate parts of the rom as the Nexus Root Toolkit wouldn't accept the MD5 after i replaced the bootloader so make sure the recovery, the modified bootloader, system and userdata are in your SDK tools folder then i did the following in cmd...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
Fastboot reboot
And voila it booted up and then upgraded its self and is now stock running 5.0 but its working for 2days it wasn't lol

alastria1 said:
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
Click to expand...
Click to collapse
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
bftb0 said:
[size=+1]Safe Mode Boot[/size]
From a cold start boot (press & release Power button), wait 2 seconds after the B&W Google (bootloader) splash screen appears, then press and hold Vol-Down button until the normal OS boot is fully completed (lock screen or home screen appears)
Click to expand...
Click to collapse
Sounds like something is draining the RAM. Try using the stock launcher as default.

Still crashed
dtg7 said:
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
Sounds like something is draining the RAM. Try using the stock launcher as default.
Click to expand...
Click to collapse
I didn't know that. I tried it, and I was able to boot it into safe mode doing this ... and then it crashed in 15 seconds and rebooted...
At this point, I'm considering just emailing Google, since its their update that did this.

They'll probably tell you to wipe cache partition. And by the way,
alastria1 said:
If I go into Recovery, it just says "No commmand"
Click to expand...
Click to collapse
that is a normal operation, it's supposed to say that. What you need to do to get the actual recovery menu is, with screen saying No Command, hold the power button, then click the volume Up button, them let go of power.
This will get you the recovery options, where you should scroll down to wipe Cache partition (last one I think) and select it by hitting power. Reboot into Android and see if that helped.
If not in the same recovery menu there's an option to wipe everything, factory reset. that might cure your device but it will wipe your data.
There is an adb command to pull your sdcard data off your device, but I've never tried it in stock recovery. it might work, but of course it will probably require you had turned On USB debugging.
adb pull /storage/sdcard0/ yourcomputerfolder
yourcomputerfolder being a location on your laptop, like a folder on the desktop.
try this command when in recovery, I don't think it works in bootloader. also, if it works it will only backup your regular files, not your installed apps.
if not then just do the wipe from recovery.
good luck.

Still a no go...
So, I got into the recovery menu, and did a full factory reset. After it rebooted, it went right back to Nova Launcher (with my usual wallpaper on there), and crashed as before. Getting into safe mode confirmed that it no apps were wiped. Factory reset didn't reset a thing.
Its almost like the flash memory is stuck on read-only mode. No matter what I do, nothing changes the contents of memory.

That is weird. And I suppose you can't do what 'wakers' suggested and flash the individual partitions since it probably requires an unlocked bootloader, which you already tried to unlock unsuccessfully. I'd say you were up sh-- creek without a paddle, but... Google searching, maybe there's still a tiny bit of hope:
See this discussion: http://android.stackexchange.com/qu...p-after-lollipop-flash-no-adb-and-no-fastboot
to summarize the suggestions:
- try holding the power button for over ten seconds to kind of reset... something
- try sending the command: fastboot oem lock
yes I know you never unlocked but try it anyway, it might go thru where unlock failed.
speaking of fastboot oem unlock, I know it failed but maybe you can just keep sending the command a few times, one of them might go thru.
I'd add another suggestion: carefully remove the back and carefully unplug the battery and let it sit for a while. then put it back together and try booting up.
may the force be with you.

Finally resolved
Thanks to the posters for the help. I contacted Google customer support and they're overnighting a refurb replacement for free.

Remove device encryption

Hi everybody, i would like to remove the devices encription under Security-Encryption
Under Encrypt device i've got Encrypted.
I've tried to restore to factory default, from recovery, from fastboot using format userdata, but, no way.
How i can remove the encryption?
My device is ZE552KL
Thanks

swet90 said:
Hi everybody, i would like to remove the devices encription under Security-Encryption
Under Encrypt device i've got Encrypted.
I've tried to restore to factory default, from recovery, from fastboot using format userdata, but, no way.
How i can remove the encryption?
My device is ZE552KL
Thanks
Click to expand...
Click to collapse
I had a same issue with this device, but I had some experiment.
If your device is unlocked, you can flash TWRP, boot to recovery, wipe, format data.
Backup your data first! It will erase all of your data (Very noob answer)
Totally careful, don't do this if you didn't want a unexpected things. Or something...

The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM.

sensi277 said:
The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM.
Click to expand...
Click to collapse
Thanks!

TWRP isn't allowing me to Mount my Storage because it's asking for a password I don't know.

ZeldaLinkAaron said:
TWRP isn't allowing me to Mount my Storage because it's asking for a password I don't know.
Click to expand...
Click to collapse
I'm having the same issue. I just got my daughter this phone (the 552KL?), downloaded the official Asus bootloader unlocker APK and ran it, then rebooted to the bootloader to flash TWRP.
TWRP installed, but wants a password to unlock it. Before the bootloader unlock, I did put her Google account on the phone, but the tool said it would completely wipe the phone. Either way, I tried her google account password, but it just says wrong password. Same thing when I tried to boot to system.
Any tips?

@Flapjack
Format through twrp

wang1chung said:
@Flapjack
Format through twrp
Click to expand...
Click to collapse
That's what I ended up doing. I got some help on another thread. The problem I'm having now is that I can't format /cache. It's really weird. If I do a full wipe on the phone, it says it can't format it. I even tried formatting it through fastboot ("fastboot erase cache" then "fastboot format cache"), which says "OKAY finished", but doesn't fix the issue when trying to wipe cache inside of TWRP.
This phone is flat out weird compared to other phones. I don't get the bootloader unlock screen. It doesn't seem to want to boot system... it just keeps going to TWRP. On the few times I have gotten to boot into system (after flashing Carbon 6.1 unofficial), it ends up hanging on a blank screen. Windows makes a sound that a new device is connected, so I'm guessing it's connecting in EDL mode or something (no devices show with a "fastboot devices" or a "adb devices").
I really don't know where to go from here. I'm used to working with Axons, Motorolas, and OnePlus phones. They just work.

@Flapjack
The cache issue is a glitch with the build of twrp, it's not a big deal. There's a workaround posted somewhere, can't remember. Just use the file browser and delete the files on it. I think there's only one file that isn't 0 bytes.
Have you flashed magisk?
Sometimes a full wipe (system/data) and then flashing the raw firmware helps. Try magisk first.

wang1chung said:
@Flapjack
The cache issue is a glitch with the build of twrp, it's not a big deal. There's a workaround posted somewhere, can't remember. Just use the file browser and delete the files on it. I think there's only one file that isn't 0 bytes.
Click to expand...
Click to collapse
So you're saying it doesn't need to be actually wiped, I just need to go into cache and delete all the files in there? How about getting it to boot to system? It just keeps booting to recovery. Not sure when it started that, as after the first time I flashed the ROM, I was able to get it to boot to system by pressing the power button when the "bootloader unlocked" screen came up. That isn't working now.
Have you flashed magisk?
Sometimes a full wipe (system/data) and then flashing the raw firmware helps. Try magisk first.
Click to expand...
Click to collapse
For my first non-stock ROM flash, I flashed the Oreo modem, Carbon 6.1 unofficial ROM, ARM64 Gapps nano, and Magisk 16.0... all at once. I tried booting and it looked like it was setting up... but as I mentioned, it just went to a blank screen. After trying a full wipe and seeing the "couldn't wipe cache" message, I figured that was why.
How will flashing Magisk help me with wiping the cache partition or getting the thing to boot right? Sorry for my ignorance.

Flapjack said:
So you're saying it doesn't need to be actually wiped, I just need to go into cache and delete all the files in there?
Click to expand...
Click to collapse
wiping/formatting cache is the same as deleting all the files. Wiping is easier but as I said, doesn't work at the moment.
Flapjack said:
How will flashing Magisk help me with wiping the cache partition or getting the thing to boot right? Sorry for my ignorance.
Click to expand...
Click to collapse
magisk won't help with cache, but it will remove the verity flag that is tripped from having twrp. From my experience, if I don't flash magisk, it'll bootloop.

Yeah.... absolutely nothing I do will get it to boot to system now. I've flashed the ROM and Magisk, but no matter what, it keeps booting to recovery.
There were two folders under /cache... "Lost&Found" and "recovery". I deleted both, but that didn't help.
---------- Post added 5th July 2018 at 12:40 AM ---------- Previous post was 4th July 2018 at 11:44 PM ----------
wang1chung said:
wiping/formatting cache is the same as deleting all the files. Wiping is easier but as I said, doesn't work at the moment.
Click to expand...
Click to collapse
So I take it I did it right? I would say it's "pretty much" the same. Formatting a partition is different than deleting files/folders in an existing partition. Still, if deleting the files/folders is good enough, then that rules out why the system wouldn't boot after the first ROM install attempt. It would also explain why "fastboot erase cache" seems to work, but TWRP still throws an error. Fastboot erase is probably working just fine.
magisk won't help with cache, but it will remove the verity flag that is tripped from having twrp. From my experience, if I don't flash magisk, it'll bootloop.
Click to expand...
Click to collapse
Is there a custom version of Magisk for this phone? I'm just installing the usual magisk 16.0 zip file you can get on their site, but it doesn't seem to be helping with the phone continuously booting into recovery. Is there a way to remove that verity flag via adb?

@Flapjack
Magisk modifies one of the partitions to get around the flag (I believe), not doable through adb.
Standard magisk off their site is fine
Try this:
Format system/data
Flash custom Rom
Flash magisk
"Wipe" cache and davlik
Reboot
OR
Flash the raw firmware
Flash twrp
Flash whichever custom Rom & gapps where needed
Flash magisk
Factory reset and "Wipe" cache and dalvik
Reboot

wang1chung said:
@Flapjack
Magisk modifies one of the partitions to get around the flag (I believe), not doable through adb.
Standard magisk off their site is fine
Try this:
Format system/data
Flash custom Rom
Flash magisk
"Wipe" cache and davlik
Reboot
Click to expand...
Click to collapse
No go. Still just boots into recovery. Here's what the boot screen looks like (then the Asus logo pops up, then recovery loads)
Code:
< More information :
Dm-Verity in EIO mode
Your device software can't be
checked for corruption. Please
lock the bootloader.
Visit this link on another device:
g.co/ABHg.co/placeholder
Your device will shutdown in 10 seconds
I can press the power button to boot immediately, or wait the 10 seconds... which just boots anyway (doesn't shut down). If I press the volume buttons, I get the following options menu:
Power off
Restart
Recovery
Fastboot
Back to previous page
Flash the raw firmware
Flash twrp
Flash whichever custom Rom & gapps where needed
Flash magisk
Factory reset and "Wipe" cache and dalvik
Reboot
Click to expand...
Click to collapse
I haven't tried this yet. Would this be the best guide to follow?
HOW-TO: Go back to Stock Rom on ZE552KL/ZE520KL
https://forum.xda-developers.com/zenfone-3/how-to/how-to-to-stock-rom-recovery-zenfone-3-t3666223

@Flapjack
That is the correct screen for an unlocked bootloader.
Try this guide for the raw firmware instead, and verify it boots to the OS. Then flash twrp and the rom again.

wang1chung said:
@Flapjack
That is the correct screen for an unlocked bootloader.
Try this guide for the raw firmware instead, and verify it boots to the OS. Then flash twrp and the rom again.
Click to expand...
Click to collapse
Grrr... no matter what I do, it won't flash. The guide says to put it in fastboot mode, but the flash tool won't detect it (even though "fastboot devices" shows it just fine). If I boot it to recovery, it'll show up in the tool, but never actually flashes (see screenshot).

Flapjack said:
Grrr... no matter what I do, it won't flash. The guide says to put it in fastboot mode, but the flash tool won't detect it (even though "fastboot devices" shows it just fine). If I boot it to recovery, it'll show up in the tool, but never actually flashes (see screenshot).
Click to expand...
Click to collapse
This is why I stopped using Windows. Maybe try disabling "driver signature verification"? Swap USB ports? My computer has some high power and low power USB ports, certain devices won't work properly in the low power ones. A couple of guides mentioned unplugging and re-plugging the USB.

wang1chung said:
This is why I stopped using Windows. Maybe try disabling "driver signature verification"? Swap USB ports? My computer has some high power and low power USB ports, certain devices won't work properly in the low power ones. A couple of guides mentioned unplugging and re-plugging the USB.
Click to expand...
Click to collapse
That's a good idea. I'm going through a powered hub right now, but who knows...
I'll try that as soon as I get home.

Ok, different computer. This is my laptop I normally use to flash.
This time, I can get it it to start to flash, but with a second or two, it throws an error (see attached).

Flapjack said:
Ok, different computer. This is my laptop I normally use to flash.
This time, I can get it it to start to flash, but with a second or two, it throws an error (see attached).
Click to expand...
Click to collapse
are you running ASUS flash tool with admin privileges?

Bootlooping - Just Started Outta Nowhere

Very happy XT1575 user (rooted on TruPure 2.4). Cruising along without issue for months and then it suddenly froze and started bootlooping. Sometimes it gets all the way to the lock screen but that's it.
Steps taken:
-Restored a nandroid backup but no dice.
-Next did a factory reset- also not successful.
-I did the Return To Stock method at this thread but it still bootloops.
Am I out of options? Is this a hardware issue?
Thanks for any suggestions. I really hate to give this phone up!

trptcom said:
Very happy XT1575 user (rooted on TruPure 2.4). Cruising along without issue for months and then it suddenly froze and started bootlooping. Sometimes it gets all the way to the lock screen but that's it.
Steps taken:
-Restored a nandroid backup but no dice.
-Next did a factory reset- also not successful.
-I did the Return To Stock method at this thread but it still bootloops.
Am I out of options? Is this a hardware issue?
Thanks for any suggestions. I really hate to give this phone up!
Click to expand...
Click to collapse
Did you lock bootloader? What is status code in BL screen?

No, I did not re-lock the bootloader when I returned to stock. That shouldn't matter?

Yes. After re lock you cannot do anything.
Flash stock again without bootloader & gpt. All sparsechunks you have in zip file, from 0 to last. Each command should end with "ok".
Don't lock BL.
Problem is - you are flashing the older version than you have on phone.
Post here results(screenshots from pc maybe too). @trptcom
---------- Post added at 07:32 AM ---------- Previous post was at 07:28 AM ----------
Of course it could be hardware problem(eMmc), you can check with twrp:
"fastboot boot twrp3xxx.img"
Into twrp: format data and after it check what sizes(MB) of backup are showing.

@dzidexx - Even though I returned to stock I never did relock the bootloader. Since then I...
--Reflashed TWRP and reinstalled my ROM after a complete wipe and data reformat. Bootloops after getting to the setup screen.
--Tried again to return to stock and omitted the bootloader and gpt commands, as you suggested. Still bootloops at the setup screen.
One FAILED result this time during fastboot, however..
fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.328s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.344s
Getting frustrated. Any suggestions welcome!

Maybe it is eMmc issue. Try & check:
fastboot boot twrp.img (3.+)
In twrp do:
Format data/factory reset,
Advanced wipe - all,
Go to backup section and check what are sizes of partitions.
System should be 0MB, data too. @trptcom
---------- Post added at 08:45 PM ---------- Previous post was at 08:44 PM ----------
Maybe it is eMmc issue. Try & check:
fastboot boot twrp.img (3.+)
In twrp do:
Format data/factory reset,
Advanced wipe - all,
Go to backup section and check what are sizes of partitions.
System should be 0MB, data too.
@trptcom

Thanks @dzidexx, I did that. Data is 0MB but system is 7MB (Boot shows 40MB).
Also I get this error when wipe and format commands are entered:
flash_image /dev/block/bootdevice/by-name/metedata /dev/zero process ended with ERROR: 255

Error sometimes is present - 1st should be done format data, than adv.wipe.
Emmc looks ok, check also partitions file system - adv.wipe - repair.
Should be: Cache, system ext4, data f2fs.
I think you should flash twrp and last good custom - you had tru pure?
Try another(not last) version.
Twrp - I think twrp 3.0.2 works the best. @trptcom

Okay, thanks again @dzidexx.. I did all that and reinstalled my last good ROM. Same result- phone starts up, gets to the welcome screen and starts bootlooping.

trptcom said:
Okay, thanks again @dzidexx.. I did all that and reinstalled my last good ROM. Same result- phone starts up, gets to the welcome screen and starts bootlooping.
Click to expand...
Click to collapse
Check sizes & file system in backup/adv.wipe sections with twrp. Post here.

Wiped everything.
Cache and system partitions are ext4, data partition is f2fs.
System has 7MB, Data has 0MB
Installed ROM
Cache and system are ext4, data is f2fs.
System now has 1140MB, Data has 0MB
Still bootlooping

Sorry, I don't know what is going on. You have to try flashing stock rom. @trptcom

Since this all started I have flashed stock several times now using fastboot from the "restore to stock' thread . Gets up to the Welcome screen and then goes into bootlooping.
Reflashed my last good Rom with the same result... gets up to the Welcome screen and then goes into bootlooping.
This all started out of the blue... phone had been humming along fine for many months. I had it all set up how I liked it and never updated anything. Then just the other day I tried to answer a phone call and the phone locked up. Started rebooting/bootlooping right after.
I'm so bummed....

Maybe you can try one more trick(only with newest twrp - 3.1.x):
Adv.wipe - change file system for data to ext4, wipe all, reboot recovery, change FS to f2fs and flash tru pure. @trptcom

@dzidexx, was excited to try your last tip. So I rebooted to bootloader from my existing TWRP to get to fastboot mode to flash the newer 3.1x TWRP and the phone completely died. Won't power on, nothing.
I guess that's what you call bricked?

Update: I was able to power the phone on. Installed the updated 3.1x TWRP, executed the file system trick, and installed the ROM. Still bootlooping. And actually it's bootlooping TWRP!
Thanks for all your tips but I'm out of luck I think..

I think you need new/used mainboard to fix it.
You can also try more wipe options.
Boot twrp with fastboot: "fastboot boot twrp3_1_1.img", repair/change file system to f2fs. Check if it done.
Erase all partitions with fastboot:
"fastboot erase boot", recovery, system, userdata, cache.
Flash the newest stock rom without bootloader & gpt.
If not helped, erase one more time & flash again with gpt.
Nothing more you can do. @trptcom

Install twrp-3.1.0-0-clark using fastboot. Then change to ext4 data and system and STAY THERE. Do not switch to f2fs. Wipe and reinstall your rom. Should work...let us know.

@dzidexx - tried the options in your last post (#17)... each time I got a couple of screens past the Android welcome screen before rebooting commenced.
@Kutty - thanks for your suggestion (actually used twrp-3.1.1-0-clark) but with that method my Rom wouldn't even finish installing before bootlooping commenced.
Thanks for all the assistance but I reckon that by now I've spent entirely too much time on this. I'm resigning myself to chalk it up to hardware failure. (The phone had been starting to act up in the week before it froze- I was getting prompted to reauthorize permissions when I started up apps. I didn't know what to make of that..)

Sorry to hear that bud, hope you get up and running soon.

Recover Data from OnePlus 5 without USB Debugging and locked Bootloader

Hello guys,
I've got following problem:
For no particular reason my brothers OnePlus 5 get caught in a bootloop, but he has quite a lot of photos and other personal data on it. Unfortunately, he never unlocked the bootloader nor had USB-Debugging enabled. I still can enter the Recovery-Mode and the fastboot mode. Sadly, adb is of no use without the USB-Debugging enabled and fastboot is useless for transferring data, isn't it?
I couldn’t find anything helpful to retrieve the photos on the phone.
I thought about using the sideload function of the stock recovery mode of OnePlus to "repair" the system with a fresh update.
My second guess was to use "fastboot boot" to boot the TWRP-recovery or the stock rom that is currently on the phone, without flashing it. For both ways, however, you would need to have USB-Debugging enabled or the bootloader unlocked....
Do you have any other ideas, how to retrieve the data on the phone? I would really appreciate your help.

try to wipe cache in recovery mode or sideload,even reset system setting(apps with data lost)
do not format data(erase everything...)

billsz said:
try to wipe cache in recovery mode or sideload,even reset system setting(apps with data lost)
do not format data(erase everything...)
Click to expand...
Click to collapse
Thanks for the fast reply. I already tried wiping the cache without success. I would like to do the same with the Dalvik Cache but the stock Recovery seems not to support that.
I was a little scared of the "reset system settings" option, because I couldn't really find what it was doing in comparison to a factory reset. So you recon it will only wipe the system and the data and leaves the rest on the phone (photos, Documents, ...) untoched. That would be totally fine, I only care about the photos.

I tried the system settings reset, however nothing has changed. I guess that means the problem is a malfunctioning bootloader and the system is fine. (I wonder if that could have anything to do with the bend in the phone that is there since it is malfunctioning)
Is there any way to repair that with a locked bootloader or to access the data via the command line and fastboot?

DevilsThumb said:
I tried the system settings reset, however nothing has changed. I guess that means the problem is a malfunctioning bootloader and the system is fine. (I wonder if that could have anything to do with the bend in the phone that is there since it is malfunctioning)
Is there any way to repair that with a locked bootloader or to access the data via the command line and fastboot?
Click to expand...
Click to collapse
in recovery mode,there are three options for clean
1.clean cache(just caches)
2.reset system(clean system settings and apps)
3.erase everything including 1.2 and format user's data(like photos,docs etc.) as factory reset
so u reset the system(2),nothing changed,then u could sideload the system image to fix it and the system image shoud be the same version with ur phone
the sideload procedure is just flashing system part,user data should be safe.

billsz said:
in recovery mode,there are three options for clean
1.clean cache(just caches)
2.reset system(clean system settings and apps)
3.erase everything including 1.2 and format user's data(like photos,docs etc.) as factory reset
so u reset the system(2),nothing changed,then u could sideload the system image to fix it and the system image shoud be the same version with ur phone
the sideload procedure is just flashing system part,user data should be safe.
Click to expand...
Click to collapse
Thanks, I already tried sideload. I used the newest version of the system image, that should be on the phone as well. I thought it would actually work, the phone even said the update was successful. However in the command line the process was interuped at 84%. The phone was still caught in a bootloop. I also tried an older version which was interuped much earlier.