Database Users

5.0.2 - Experience and Discussion

Thought it would be good to have a thread dedicated to 5.0.2, instead of sifting through the 5.1.x Rolling Out and Stock OTA threads.
Got the prompt and updated this morning. Took about 10 minutes -- 3-4 minutes to install the updat and then a good 6-7 to go through app optimization (for 120+ apps).
Haven't had a chance to put it through its paces yet, but interested in what others experiences are. Improvement? Same old?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Screen flicker possibly gone? Was pretty bad before on mine, haven't had it since update now.

This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.

b1bub4bu said:
This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.
Click to expand...
Click to collapse
You basically have two choices:
1) Flash the stock 5.0.1 system.img (this will install stock recovery) and boot.img, then vendor. Img then take the OTA.
2) Wait until Google posts the factory image.

Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
and if you have TWRP, then also recovery.img
once all these are stock, then you can take the OTA.
After the OTA, you can either reflash TWRP, or just simply fastboot boot it, then apply the latest SuperSU zip from chainfire's web site, and you'll be back to stock and rooted.

Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.

Ive tried the ota 3 times now and every time it 'errors' in recovery while flashing, I'm flabber gasted this is how Google now treats its nexus customers.

Ok I'm going to update my vendor
if any one wants it just tell me

Something else ... if you attempt the OTA once, you're done ... you can't re-attempt it unless you reflash back to original 5.0.1 stock.
It checks System first, and updates it ...
Then it checks Vendor, and updates it ...
Then it checks the boot image, and updates it.
So you you fail the vendor test, it's already updated System, and it won't run again.
You have to reflash system.img, vendor.img, AND boot.img before you can try again.
A much smarter method would have put the three verification steps one after the other, but obviously Google did not write the script that way.

Roxas598 said:
Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.
Click to expand...
Click to collapse
I think it's just some bug fixes. This is the only Nexus not moved to 5.1.1 by now, it's also the only Nexus using the K1 chipset. Not sure if the two are related, but it seems reasonable that they are running into some nVidia issues. 5.1.1 isn't out for the Shield tablet either.

ok guys updated to 5.0.2 just to get the vendor.img. it was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79

_litz said:
Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
.
Click to expand...
Click to collapse
I appreciate this. Coming from Nexus 6, vendor.img doesn't exist.
And on Nexus 6 when flashing the stock system.img it checks recovery and if not stock will automatically flash recovery.img. Is Nexus 9 the same?

When will my Nexus 9 LTE Model get this?

USBhost said:
ok guys updating to 5.0.2 just to get the vendor.img was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79
Click to expand...
Click to collapse
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...

stadicon said:
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...
Click to expand...
Click to collapse
I was going to
But got lazy

The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?

stadicon said:
The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?
Click to expand...
Click to collapse
I know man I'm crying inside

Ok so I got my ota update and downloaded it. Now my Nexus 9 keeps trying to come on,then saying android updating apps, then shutting off and restarting , and then repeats the same thing ! I never rooted or flashed anything ! Its completely stock ! WTH ! Help !!!!!!!

Update showed up when I turned mine on, ended up bricking my device.
Would show the spinning balls and nothing else, tried wiping cache, factory reset and still ended up at the spinning balls. Google sent me a new one, but I really wish I could just return the stupid thing.
I'll never buy another "premium" Nexus tablet again, the only way I buy another is if they give us another Nexus 7 like device.

I'm doing a factory reset .It seems it still on android deleting screen for 10 min already. Is it frozen ??

Lollipop 5.1 for Shield Portable released!

https://forums.geforce.com/default/...android-5-1-lollipop-ndash-available-7-23-15/
Finally the OTA has been released

Anyone use the 5.1 xposed on this yet? Waiting to see if it works before I update.
Sent from my bacon

Is the update even out yet? It's not showing up when I click check for updates..

zach jeremay said:
Is the update even out yet? It's not showing up when I click check for updates..
Click to expand...
Click to collapse
Yeah, I downloaded it and tried to install it. I forgot I had installed a custom recovery, so it failed. I reinstalled the factory recovery and now I'm waiting for the update again.

Does anyone have the img file for lollipop? I don't know why my updates not showing up.

Ok, seems the old CWM from KitKat is working. Also SU 2.46 does.
Sadly no Miracast anymore.
A few games apart from the mentioned ones in the link above won't work too: ARC Redux (more to come)

Did anyone catch the OTA. I have the factory Image for 103 but wont flash due to the "insufficient memory" for the system.img and the userdata.img I had similar problems with the tablet and only updated via the OTA. My system isn't showing as an update available.

diigibio said:
Did anyone catch the OTA. I have the factory Image for 103 but wont flash due to the "insufficient memory" for the system.img and the userdata.img I had similar problems with the tablet and only updated via the OTA. My system isn't showing as an update available.
Click to expand...
Click to collapse
You can try flashing the factory Image from update 103.
It's available now too...
https://developer.nvidia.com/gameworksdownload
Just make an account (it's free) and set the filter to "SHIELD".
Here you go.

astuermer said:
You can try flashing the factory Image from update 103.
It's available now too...
https://developer.nvidia.com/gameworksdownload
Just make an account (it's free) and set the filter to "SHIELD".
Here you go.
Click to expand...
Click to collapse
Thanks but already tried.
Sent from my A0001 using Tapatalk

Hi !
It seems my CWM is nit "compatible" with OTA 103, i get all sort of errors in CWM when trying to execute OTA update.
Do you have any hint where to download a compatiple CWM or stock recovery ?
(Or any smarter solution for that problem of course).
Greetings,
Ender

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can anybody confirm this issues?
1. Volume way too loud
2. Volume often varies, step 1 isn't always the same level.
3. Shield Hub can't be activated with button

Couldn't install with TWRP. Got some weird error after flashing and it wouldn't boot up at all. Had to go back and restore a backup.
Sent from my bacon

Hmm, i "solved" my Problem by flashing 5.1 with Linux instead of OTA...
Greetings,
Ender

Problems I can confirm are, cant install or update anything from the play store because of "insufficient space" when I clearly have 2GBs and a 64GB micro SD card, its alot slower and Apex Launcher is now utterly terrible with the new update.

After trying to install it won't boot up. Then I tried to fastboot but I'm getting an error saying target reported max download size of 643825664 bytes error: cannot load 'recovery.img' : No error .
Any ideas

I disabled "Google" so the Shield button does not activate it but still the Game Mapper is not showing up. Thats horrible, dis anyone manage to get back the Game Mapper ?
Ender

enderffx said:
I disabled "Google" so the Shield button does not activate it but still the Game Mapper is not showing up. Thats horrible, does anyone manage to get back the Game Mapper ?
Ender
Click to expand...
Click to collapse
To enable it open the app / game then hold down the start button until it pops up, If it didn't work then read down...
for me it's working perfectly i think because i flashed it using a computer (or maybe a factory reset should do the trick) if you're going to do it make sure you do a backup in the external sdcard because everything in the internal sdcard will be deleted I'm not responsible for any lost file or any damage, I'm not trying to scare you but I will help you if I can
By the way I disabled "google" and still the gamepad mapper is working fine so "google" has nothing to do with.

How did you guys use a computer to flash it? Sis they release the img? I would like to flash it with my computer because I still haven't received the ota.
---------- Post added at 12:14 AM ---------- Previous post was at 12:10 AM ----------
Did they release the img? How did u flash it with a computer, please help me because I didn't receive the ota and ima fan of lollipop.

All of these have been brought up on the Nvidia forums, so yes, they can be confirmed. I would like to add, that the volume changes dynamically depending on the sound being played In some games and emulators, I noticed that the sound would get quieter and louder without touching anything. I had Virtua Racing for 32x running in Retroarch and the volume dropped and raised in the same places during the demo mode every time, like it was done on purpose.
Is it just me, or does it seem like Nvidia is trying to de-Nvidia the Portable?
astuermer said:
Can anybody confirm this issues?
1. Volume way too loud
2. Volume often varies, step 1 isn't always the same level.
3. Shield Hub can't be activated with button
Click to expand...
Click to collapse

[Discussion] Dumb attempt to upgrade to Marshmallow with TWRM in osprey

Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.

+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?

did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk

Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.

sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.

No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.

golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM

i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download

hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning

I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too

Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk

nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again

VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.

hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.

So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??

Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk

nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.

Little Help needed to get my 6p alive again

please help me.
I have completely wiped my device. nothing is there in internal storage. Just the TWRP folder.
it has unlocked bootloader and twrp installed
but it is the unrooted device.
so please tell me what is best for me?
shall I root it or can I directly go to stock Oero?
I have already downloaded stock file '8.1.0 (OPM6.171019.030.E1, Jul 2018)- angler-opm6.171019.030.e1-factory-1abcb2f1.zip'
I am confused, how should I proceed?
please explain me stepwise, so I can save my phone.

smartpreet said:
please help me.
I have completely wiped my device. nothing is there in internal storage. Just the TWRP folder.
it has unlocked bootloader and twrp installed
but it is the unrooted device.
so please tell me what is best for me?
shall I root it or can I directly go to stock Oero?
I have already downloaded stock file '8.1.0 (OPM6.171019.030.E1, Jul 2018)- angler-opm6.171019.030.e1-factory-1abcb2f1.zip'
I am confused, how should I proceed?
please explain me stepwise, so I can save my phone.
Click to expand...
Click to collapse
You will be fine I wipe my internal from time to time. Just make sure you update your bootloader and vendor. If you use the flash all I'm pretty sure it's done for you but if using fastboot method follow the steps in the hiesenberg guide. Just so you know once on the latest Oreo builds from what I've read can no longer downgrade. I haven't verified or read up on it myself but maybe look into if you think you might want to go back to nougat .

Exodusche said:
You will be fine I wipe my internal from time to time. Just make sure you update your bootloader and vendor. If you use the flash all I'm pretty sure it's done for you but if using fastboot method follow the steps in the hiesenberg guide. Just so you know once on the latest Oreo builds from what I've read can no longer downgrade. I haven't verified or read up on it myself but maybe look into if you think you might want to go back to nougat .
Click to expand...
Click to collapse
i have tried that earlier, but still i got the red triangle.
since i failed to go to stock today i installed latest twrp-3.2.2-0-angler using latest SDK tool.
then i flashed Magisk-v16.0 and then ResurrectionRemix-M-v5.7.4-20161008-angler and it immediately went to google logo and stuck there.

just use this to get back to stock https://developers.google.com/android/images
all you do is boot in to fast boot plug into pc and run flash all
there are ways to save data but you already wiped so no need
if your still confused just look up a guide of how to flash factory images and install the usb drivers

billycar11 said:
just use this to get back to stock https://developers.google.com/android/images
all you do is boot in to fast boot plug into pc and run flash all
there are ways to save data but you already wiped so no need
if your still confused just look up a guide of how to flash factory images and install the usb drivers
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
these are my files.
as you said i I had connected the phone and double-click the flashall
the process started and finish but still i am on google logo.it keeps booting to logo. nothing else is happening

smartpreet said:
these are my files.
as you said i I had connected the phone and double-click the flashall
the process started and finish but still i am on google logo.it keeps booting to logo. nothing else is happening
Click to expand...
Click to collapse
What did the command line windows say when it was flashing

billycar11 said:
What did the command line windows say when it was flashing
Click to expand...
Click to collapse

smartpreet said:
Click to expand...
Click to collapse
It looks good but didn't seem to flash radio and bootloader maybe just not in screen shot should boot but if it still won't boot in to the stock recovery and factory reset might help

You could have the bad big cores try flashing one of the 4 core fixes. Also I wait to flash magisk until after first boot. It can hang you on the Google screen .

Galaxy J5 (2017) stuck in recovrey mode.

Hi. During the update to Android 10 the phone turned off and after switching on it goes into recovery mode.
The phone is not mine and this description was provided to me by the owner of the phone. I was unable to see the phone directly because of the quarantine, so as a first solution I thought about a restore via odin. Has anyone had this problem? And is there a less drastic way than Odin to solve? Because the owner has some data that he would prefer not to lose.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

How did you get android 10 on j530f?
I get the same messages when I enter recovery but I'm able to get out. You could use odin to reflash the firmware but keep all the data.

You won't be able to do a thing with Odin if the device doesn't have an unlocked bootloader and USB debugging enabled which I doubt it has seeing as it's a stock update that was attempted.
What happens to the device once plugged into a PC? Is the data corrupt or is the device recognized and files can be seen?

I have the same problem with almost the same recovery messsges. It also says dm verity failed. Odin and samsung 300k tool both dont work.

myusernamesucks said:
I have the same problem with almost the same recovery messsges. It also says dm verity failed. Odin and samsung 300k tool both dont work.
Click to expand...
Click to collapse
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...

Emelin.2004 said:
How did you get android 10 on j530f?
I get the same messages when I enter recovery but I'm able to get out. You could use odin to reflash the firmware but keep all the data.
Click to expand...
Click to collapse
I don't know how the phone has Android 10, as I said "The phone is not mine and this description was provided to me by the owner of the phone", sorry.
garylawwd said:
You won't be able to do a thing with Odin if the device doesn't have an unlocked bootloader and USB debugging enabled which I doubt it has seeing as it's a stock update that was attempted.
What happens to the device once plugged into a PC? Is the data corrupt or is the device recognized and files can be seen?
Click to expand...
Click to collapse
Not even to flash a stock firmware? It seems strange to me, in the past I have often used odin on my S2 also for the stock ROM.
The device always reboot in recovery, I don't think the PC can see it.
jaggedN said:
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...
Click to expand...
Click to collapse
Hi, the details were given to me by another person, the only thing that I (and this person knows) is that the phone during an update has turned off and reboots in the attached image window.
Thanks for the tips, I will report it to the person concerned, hoping that he can install the twrp.

TheNightmare97 said:
I don't know how the phone has Android 10, as I said "The phone is not mine and this description was provided to me by the owner of the phone", sorry.
Not even to flash a stock firmware? It seems strange to me, in the past I have often used odin on my S2 also for the stock ROM.
The device always reboot in recovery, I don't think the PC can see it.
Hi, the details were given to me by another person, the only thing that I (and this person knows) is that the phone during an update has turned off and reboots in the attached image window.
Thanks for the tips, I will report it to the person concerned, hoping that he can install the twrp.
Click to expand...
Click to collapse
Put the j5ylte update onto sd card.
Get the update from updato or sammobile or somewhere.
Then reboot stock recovery and apply update from sd card. Or sideload it using adb on a computer. Not very complicated at all

Install the stock rom like i described here: https://forum.xda-developers.com/galaxy-j5/help/to-stock-rom-t4099857

jaggedN said:
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...
Click to expand...
Click to collapse
I cant even access download mode neither can I apply an update from SD card. It says dm-verity failed. System is completely stock. I didn't modify anything.