Related
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
Galaxy S4 I9505
Phone was second hand to me at the start of this year, though had been well looked after, always in a case etc
I flashed it with the newest stock ROM in January this year
I9505XXUHOJ2_I9505BTUHOJ1_I9505XXUHOJ2
& rooted with CF AutoRoot
It has worked fine until about 2 weeks ago, when it randomly shut down. After restarting, it kept bootlooping.
Left it off & charging overnight, & the next morning it booted ok. Managed to use spotify for a few hours.
Then it started bootlooping again, sometimes getting all the way but then crashing after a few minutes.
Managed to boot into recovery & do a 'wipe cache', that didnt fix it.
'Wipe data' didnt fix it
Have flashed the PIT file & ROM (via odin), no errors in odin, done it twice now
wiped cache & data
still wont boot past the white splash screen, only sometimes boots into recovery
(also, only the menu button lights up, not the back button.)
I've checked the power button (clicks & dosnt stick)
Dont think the batteries the issue (charges fine, dosnt get warm, isnt bulging)
What else could stop it booting?
Have you tried booting into safe mode?
Safe mode, from what I read, can be accessed by holding the menu button while the phone boots.
But you should also do some reading about it, in case I'm wrong.
The other idea would be to try a custom ROM.
GDReaper said:
Have you tried booting into safe mode?
Safe mode, from what I read, can be accessed by holding the menu button while the phone boots.
But you should also do some reading about it, in case I'm wrong.
The other idea would be to try a custom ROM.
Click to expand...
Click to collapse
Can't boot into safe mode
(& having read up on it, it would only not run apps that arn't already in the ROM)
Any suggestions for a custom ROM
& why would it work when the original official one won't?
Well, it's booted far enough to get into android & add a google account, then it bootloops again.
Then after leaving it off for a while, it will boot & let me look at settings etc, then bootloop
however
the menu soft key stays lit all the time after a boot
the top half of the phone, around the camera, gets very warm
Does that indicate it's a hardware issue?
Could it be the battery?
If it's the top half warming up without you doing anything, it's the motherboard.
Boot into recovery and and let it stand by, see if it reboots.
xedge said:
Well, it's booted far enough to get into android & add a google account, then it bootloops again.
Then after leaving it off for a while, it will boot & let me look at settings etc, then bootloop
however
the menu soft key stays lit all the time after a boot
the top half of the phone, around the camera, gets very warm
Does that indicate it's a hardware issue?
Could it be the battery?
Click to expand...
Click to collapse
The battery can't prevent the ROM from booting. It would have to turn off during the boot, which it doesn't. So, by my logic, it isn't the battery.
Try official CM.
GDReaper said:
The battery can't prevent the ROM from booting. It would have to turn off during the boot, which it doesn't. So, by my logic, it isn't the battery.
Try official CM.
Click to expand...
Click to collapse
Hello Reaper, I have exactly same problem. Please help. In my case leds are working fine, rest is exactly the same problem. And It all happened suddenly on its stock rom. I never rooted my phone before.
kingpin090 said:
Hello Reaper, I have exactly same problem. Please help. In my case leds are working fine, rest is exactly the same problem. And It all happened suddenly on its stock rom. I never rooted my phone before.
Click to expand...
Click to collapse
Try this.
GDReaper said:
Try this.
Click to expand...
Click to collapse
I am not able to go into recovery after firmware flash. The recovery bot appears and when the blue loading bar goes to half, the phone reboots and then again boot loop. I just noticed this always happened when i flashed a rom. I was never able to enter recovery on first boot.
kingpin090 said:
I am not able to go into recovery after firmware flash. The recovery bot appears and when the blue loading bar goes to half, the phone reboots and then again boot loop. I just noticed this always happened when i flashed a rom. I was never able to enter recovery on first boot.
Click to expand...
Click to collapse
Does phone go into download mode ?
gosha98_ said:
Does phone go into download mode ?
Click to expand...
Click to collapse
Yes it goes normally into download mode. Firmware always flashed without any error. But i noticed I can't enter recovery on first boot to do factory wipe.
Sent from my GT-I9300 using XDA-Developers mobile app
kingpin090 said:
Yes it goes normally into download mode. Firmware always flashed without any error. But i noticed I can't enter recovery on first boot to do factory wipe.
Click to expand...
Click to collapse
Why do you want to do factory wipe after one boot?
Its the only thing i didn't tried till now, my phone crashes and reboots everytime during boot.
Sent from my GT-I9300 using XDA-Developers mobile app
VS995 Unlocked with dirty santa, Konverged kernel, stock rom
The other day phone just randomly shut off without warning, battery was low (5%) so I figured battery just died. Went to plug phone in, got to the "device cannot be trusted" screen and to the LG screen, screen goes black, and gives me this yellow "RPM Crash" screen (see below). I can boot into fastboot just fine, and up until just a few minutes ago I was able to boot into twrp by flashing my twrp image as boot and rebooting the phone (if I use the button method it gives me the factory reset screens, goes to the lg screen, and goes back to the crash screen). I can reboot to recovery from twrp and it works just fine. Booting into download mode shows the download mode icon for a few seconds and then it goes black and to the crash screen.
Issues found/fixed so far
I saw in another thread someone had a boot.img issue so I messed with the boot1 and boot2 imgs from the dirty santa process and managed to get to a looping verizon screen with boot1 and the encryption unsuccessful screen with the boot2.img
In twrp my data and dalvik partitions were corrupted but I was able to reformat and repair them. (I found out when trying to wipe them in fastboot)
In fastboot, after working in twrp I was able to wipe and reflash all partitions except system I extracted from a kdz with no luck as far as getting past the error.
My system partition is currently wiped and I have not flashed a new system.img as fastboot won't let me flash it and I cannot get back into twrp to flash it.
I'm curious if this is more of a hardware fault than it is a software fault as download mode was also affected
Thoughts? Suggestions?
spalding1028 said:
VS995 Unlocked with dirty santa, Konverged kernel, stock rom
The other day phone just randomly shut off without warning, battery was low (5%) so I figured battery just died. Went to plug phone in, got to the "device cannot be trusted" screen and to the LG screen, screen goes black, and gives me this yellow "RPM Crash" screen (see below). I can boot into fastboot just fine, and up until just a few minutes ago I was able to boot into twrp by flashing my twrp image as boot and rebooting the phone (if I use the button method it gives me the factory reset screens, goes to the lg screen, and goes back to the crash screen). I can reboot to recovery from twrp and it works just fine. Booting into download mode shows the download mode icon for a few seconds and then it goes black and to the crash screen.
Issues found/fixed so far
I saw in another thread someone had a boot.img issue so I messed with the boot1 and boot2 imgs from the dirty santa process and managed to get to a looping verizon screen with boot1 and the encryption unsuccessful screen with the boot2.img
In twrp my data and dalvik partitions were corrupted but I was able to reformat and repair them. (I found out when trying to wipe them in fastboot)
In fastboot, after working in twrp I was able to wipe and reflash all partitions except system I extracted from a kdz with no luck as far as getting past the error.
My system partition is currently wiped and I have not flashed a new system.img as fastboot won't let me flash it and I cannot get back into twrp to flash it.
I'm curious if this is more of a hardware fault than it is a software fault as download mode was also affected
Thoughts? Suggestions?
Click to expand...
Click to collapse
I have a H910 that just received a screen replacement and I am also getting the yellow error screen. I am still able to get into Twrp though. However no matter how many times I flash a Rom, it keeps getting stuck at the yellow screen.
ozymandiasmusic said:
I have a H910 that just received a screen replacement and I am also getting the yellow error screen. I am still able to get into Twrp though. However no matter how many times I flash a Rom, it keeps getting stuck at the yellow screen.
Click to expand...
Click to collapse
Can you take a picture of of the screen, or is it identical to the one that has been posted? My guess is that you put the wrong screen on.
-- Brian
runningnak3d said:
Can you take a picture of of the screen, or is it identical to the one that has been posted? My guess is that you put the wrong screen on.
-- Brian
Click to expand...
Click to collapse
Here is the photo, sorry it's not the best quality since it's taken with a OnePlus One.
I had gotten the screen replaced by a cell phone repair shop. Luckily they still gave me the original screen. If it's a bad screen I will just get them to switch it out again...
You will have to upload a better quality picture for me to be sure, but I can tell you that you are getting an selinux failure for some reason when it is trying to load some driver. Again, I need a better picture.
-- Brian
runningnak3d said:
You will have to upload a better quality picture for me to be sure, but I can tell you that you are getting an selinux failure for some reason when it is trying to load some driver. Again, I need a better picture.
-- Brian
Click to expand...
Click to collapse
Sorry for the delay, I had the repair shop reinstall the original screen I was using. I am still getting an error screen, but I have my actual camera with me so here you go. I have tried installing a new ROM, I've tried doing "STEP3.BAT": https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 Because thought it needed a new boot.img
Still having errors. Any advice would be great. I haven't reverted back to stock because not sure how, and worried I'll lose twrp and would prevent me from actually doing anything.
I have a LG g4 that got the blue screen of death and it won't respond to anything I've tried so I'd say this is the same...........
my lg v20 started displaying this RPM crash screen two days ago. I am not certain what caused it, but it was immediately after charging it with a power bank. To boot mine, I have to plug the phone to a wall charger, once it shows charging, I press the power button and it will boot flawlessly, after that I am free to unplug it. I cant say if it wouldnt degenerate and I havent tried flashing the phone afresh. For now, I would back up my data to avoid surprises.
ozymandiasmusic said:
Sorry for the delay, I had the repair shop reinstall the original screen I was using. I am still getting an error screen, but I have my actual camera with me so here you go. I have tried installing a new ROM, I've tried doing "STEP3.BAT": https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 Because thought it needed a new boot.img
Still having errors. Any advice would be great. I haven't reverted back to stock because not sure how, and worried I'll lose twrp and would prevent me from actually doing anything.
Click to expand...
Click to collapse
did you try changing the battery?
ozymandiasmusic said:
Sorry for the delay, I had the repair shop reinstall the original screen I was using. I am still getting an error screen, but I have my actual camera with me so here you go. I have tried installing a new ROM, I've tried doing "STEP3.BAT": https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 Because thought it needed a new boot.img
Still having errors. Any advice would be great. I haven't reverted back to stock because not sure how, and worried I'll lose twrp and would prevent me from actually doing anything.
Click to expand...
Click to collapse
How do you boot into twrp? I am unable to. Are you currently able to copy your files from your internal memory to sd via twrp?
Hi
RP2, GSI roms (I tried three: LOS 17, NitrogenOS, RevenageOS), arter97-kernel-r12, Magisk-v20.3
I am installing a GSI ROM, the system is working. after the third or more reboot, the phone is booted to a black black screen.
Wipe all data, phone booted.
doing something simple (install software from google play,restore data from old device via google restore)
restart
phone booting to blank black screen with sound. computer (USB) recognized the phone.
Tried with Magisk, withour Magisk, restored vendor.img from origin (I was deleted the two apks for BT).
clear data
phone booted
restore
blank again
where to start debug it ?
Same problem with me, I had my phone on phhusson treble ROM (android 10) then went back stock and hated it....tried to flash the phhusson treble ROM again and she boots but to a black screen, you can hear via sound it's up just the screen is black....let me know if ya finger anything out
DaveyBoy2002 said:
Same problem with me, I had my phone on phhusson treble ROM (android 10) then went back stock and hated it....tried to flash the phhusson treble ROM again and she boots but to a black screen, you can hear via sound it's up just the screen is black....let me know if ya finger anything out
Click to expand...
Click to collapse
did you tried Android 9 ROMS or this is only 10 problem?
I was rooted and installed Magisk on the stock, I hate the stock like you but it works.
Haven't tried a android 9, I'm back at work and used 4gb of data screwing around yesterday trying to get things fixed so I gotta go easy today ?
moshe_lm said:
Hi
RP2, GSI roms (I tried three: LOS 17, NitrogenOS, RevenageOS), arter97-kernel-r12, Magisk-v20.3
I am installing a GSI ROM, the system is working. after the third or more reboot, the phone is booted to a black black screen.
Wipe all data, phone booted.
doing something simple (install software from google play,restore data from old device via google restore)
restart
phone booting to blank black screen with sound. computer (USB) recognized the phone.
Tried with Magisk, withour Magisk, restored vendor.img from origin (I was deleted the two apks for BT).
clear data
phone booted
restore
blank again
where to start debug it ?
Click to expand...
Click to collapse
Yea I've had the same results as well.
Try Havoc and PE from these links. They are phhusson based and work with some bugs but at least you can boot up after the third time
https://sourceforge.net/projects/expressluke-gsis/files/
moshe_lm said:
did you tried Android 9 ROMS or this is only 10 problem?
I was rooted and installed Magisk on the stock, I hate the stock like you but it works.
Click to expand...
Click to collapse
SO! got home from work, flashed the rom that i was having issues with (phhusson's android 10 build) BAM, booted just fine, did the whole big restore thing, figured this was going TOO well so i figured i better test a restart.....and BAM black screen, lock sounds, everything just nothing on the screen. so I volume down & powered till it reboot....and the screen is back!.. so why does it need this? idk but atleast it gets me workin with android 10 again!
DaveyBoy2002 said:
SO! got home from work, flashed the rom that i was having issues with (phhusson's android 10 build) BAM, booted just fine, did the whole big restore thing, figured this was going TOO well so i figured i better test a restart.....and BAM black screen, lock sounds, everything just nothing on the screen. so I volume down & powered till it reboot....and the screen is back!.. so why does it need this? idk but atleast it gets me workin with android 10 again!
Click to expand...
Click to collapse
It is working after second restart ? or one time ?
moshe_lm said:
It is working after second restart ? or one time ?
Click to expand...
Click to collapse
If you want/need to restart if you do it via the power button then hitting restart, it will boot to a black screen. But if you hold the power and volume down till it reboots, it'll boot perfectly. Happens every time for me
DaveyBoy2002 said:
If you want/need to restart if you do it via the power button then hitting restart, it will boot to a black screen. But if you hold the power and volume down till it reboots, it'll boot perfectly. Happens every time for me
Click to expand...
Click to collapse
volume down isn't go to fastboot mode ?
moshe_lm said:
volume down isn't go to fastboot mode ?
Click to expand...
Click to collapse
Not if you let go when you see the screen turn off, then it's just a dirty restart I guess?
In my case, it only happens when you use the Encrypt password to start the device.
So I suggest skipping the encrypt part on startup setting and the problem should gone.
*Sorry for my bad English.
In my case, Don't use the "Secure start-up" thing when you set up your phone in Android 10.
Nor It will mess and cause a black screen on your device.
I am at a loss here. After almost 2 years of working flawlessly, my s5e won't boot.
The screen got frozen while using anydesk, and had to force a restart (power button + up and fown volume buttons).
I can see the Samsung logo for less than a second, and then it switches off. Without touching anything, after some seconds the same thing happens.
I tried charching it and similar behaviour: i see charging circle for less than a second, and off again.
I AM AT A LOSS.
I managed to boot it pressing power+volume_up buttons and this is what i see (attached). It can stay like that for a long time so I guess battery and it's connection to the tablet are fine.
PLEASE ANY HELP WOULD BE VERY WELCOME
UPDATE:
I have tried MANY things in the 6 hours since I wrote this post. I am able to put the tablet in download mode and ODIN (and my PC) recognizes it. I am able to flash VBMETA but now TWRP (fail).
At some point the tablet rebooted in normal mode (why?) but got frozen again and had to reboot it.
Anyone can point me to how to recover it? I don't mind right now to loose what is in the internal memory.
Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!
Abd El-Rahman El-Batal said:
Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!
Click to expand...
Click to collapse
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?
iruiz2 said:
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?
Click to expand...
Click to collapse
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro
Abd El-Rahman El-Batal said:
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro
Click to expand...
Click to collapse
It just loads the screen attached in my first post.
Try flash via Odin, it still in download mode with this warning.
The tablet was still covered by warranty so I called the seller and they took it to a Samsung repair store. They replaced the motherboard, so I guess it was not recoverable.
The bad news is that they updated to android 11, I was quite happy with old 9.0 because I had TWRP and Magisk working.
Thank you for all that tried to help.