Related
Finally TWRP 2.4 - HTC One X + (AT & T) can charge the battery with the phone off?. In the official website says no, many people say yes. I'm waiting for this confirmation to install the recovery.
questions:
What happens if after installing the recovery my phone runs out of battery and is not charged by the recovery?. How I can charge the battery?
Lloir fixed issues and made it official - everything works, even off mode charging
http://forum.xda-developers.com/showthread.php?p=34192991
Dottcent said:
Lloir fixed issues and made it official - everything works, even off mode charging
http://forum.xda-developers.com/showthread.php?p=34192991
Click to expand...
Click to collapse
This means that now the off mode charge is not working? And What happens if after installing the recovery my phone runs out of battery ?
Thanks!
marceloalvarez said:
This means that now the off mode charge is not working? And What happens if after installing the recovery my phone runs out of battery ?
Thanks!
Click to expand...
Click to collapse
This means off mode charging IS working in the official release V2.4.1.1. I installed the official release earlier and charging works great. This is indicated by a + after the battery percentage. If your phone runs out of battery after installing the recovery, plug it up. Thanks Lloir!
Lloir's most recent post clearly states OFF MODE CHARGING IS WORKING ON BOTH AT&T AND INTERNATIONAL. Now I do understand the desire to verify so: Download the latest image from the twrp website (2.4.1.1) and flash it via fastboot (I RECOMMEND AGAINST USING GOO TO FLASH, PEOPLE HAVE REPORTED PROBLEMS). Boot into recovery and verify the version in the top right. ADDITIONALLY, while in recovery plug it in and WAIT up to 2 minutes. The batter percentage should change from 66% to what ever it is AND have a + next to it. Example : 98%+
This percent change with a plus will indicate that off mode charging will work.
Really great work with everything. Hats off to the devs
BrendenDonaher said:
Really great work with everything. Hats off to the devs
Click to expand...
Click to collapse
I use TWRP 2.4.1.1 and it works.
OFF Mode Charge works fine for me.
Okay, I've been driving myself crazy trying to find the answer to this little bootloop, and have been all over the place. So I apologize in advance if there is an elusive thread answer to this somewhere...
Here goes:
I downloaded and installed (properly) the [ [ROM] CM9 (ICS) for the Galaxy Player 5.0 USA ] by JackpotClavin. Now normally I would post my issue there, but due to me being a new member, it isn't allowed as you all know. So please bear with me.
Everything works fantastic, until I plug it in when the device is off. Then the screen and buttons light up, it shows the busy signal asterik, and gets to where it would NORMALLY show the battery next, but powers down. Now if I do something that stops the boot loop here (can't remember what right now; no internet at home) then when I plug it in, it actually boots up. But as soon as I unplug it, it kills itself as if it had no battery.
But if I plug in the device when it is already on, then it charges like normal. So I am REALLY confused here.
I already un-bricked it by myself at home when I did something dumb during the ROM restore (CWM). Set it back to stock, and it ran fine. As soon as I switch to the ICS ROM, issues
Now I did a little searching, and in the boot.log it references a "charging_mode_booting" I followed the file path, and found no file there. Now I am aware that I have little (none ) experience in android until now, so that may be normal. I would post the exact log here, but since the device is bootlooping as I type, this will have to wait until I get home again and can troubleshoot
Anyways, I hope I'm not wasting your time. Hope you can help me solve this!
Thank you for your time
N7_X
Samsung Galaxy Player 5.0 (US)
Are you charging your device (while it's shut off) via laptop, console, desktop, or anything else besides a wall charger?
Look under your /system/media
There should be a bunch of battery charging files. If they aren't there, find the files from another ROM and move it there.
Sent from my YP-G70 using xda app-developers app
Jistropy said:
Are you charging your device (while it's shut off) via laptop, console, desktop, or anything else besides a wall charger?
Click to expand...
Click to collapse
Ah thanks mate, that's what I did to get it to boot up while plugged in. Then it has the error here that if I unplug it, whole device shuts off as if the power was the only power source, but will reboot from the battery if I turn it back on.
iurnait said:
Look under your /system/media
There should be a bunch of battery charging files. If they aren't there, find the files from another ROM and move it there.
Click to expand...
Click to collapse
Good idea, I'll get right on it and see if I have any progress.
Thank you both, cheers!
EDIT: Just looked into my system/media folder, and have all "battery_charging_#" 5-100.
Also:
chargingwarning.qmg
Disconnected.qmg
LMprec_508.emd
PFFprec_600.emd
And of course the boot animation and folders
Strange boot loop too with YP-G70
iurnait said:
Look under your /system/media
There should be a bunch of battery charging files. If they aren't there, find the files from another ROM and move it there.
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
Hello everyone ,
first thank you for all your developments.
Secondly, excuse my English but I'm Portuguese.
I spent a lot of time to read all the topics related to this problem, and I have too with my Intl Player.
Since I installed the rj 's custom kernel (r14) if my player is turned off, as I branch as a wall charger or on USB in my MacBookPro , I boot loop load as described above.
So I installed a file explorer that allowed me to see that I had none of the files in the directory system / media.
Ok, I installed adb and fastboot on my Mac , and successful (despite the write permissions only one I managed to get around) to copy the files I found there.
I was sure now it was going to fix my problem, but unfortunately, I have always this kind of boot loop charge if my player is turned off.
Apart from that , everything seems to work well , I do not even know if this is really a problem , I did not let my battery run down lest I get stuck . As long as the player stays on, no worries, battery charging well. Of course I did all the basic wipe's (data/factory, cache, dalvik cache, battery stats).
Sorry for the long post, but I wanted to give as much information .
If someone has an idea of where it may come again, or at least tell me if it's serious in case my battery is fully discharged .
Thank you ! :good:
Edit : actualy I have installed the [ROM][4.3][YP-G70]CyanogenMod 10.2 - M1 Release whith the KKernel R2.1 by KOala888 (My YP-G70 run super fast...).
ToniOsX said:
Hello everyone ,
first thank you for all your developments.
Secondly, excuse my English but I'm Portuguese.
I spent a lot of time to read all the topics related to this problem, and I have too with my Intl Player.
Since I installed the rj 's custom kernel (r14) if my player is turned off, as I branch as a wall charger or on USB in my MacBookPro , I boot loop load as described above.
So I installed a file explorer that allowed me to see that I had none of the files in the directory system / media.
Ok, I installed adb and fastboot on my Mac , and successful (despite the write permissions only one I managed to get around) to copy the files I found there.
I was sure now it was going to fix my problem, but unfortunately, I have always this kind of boot loop charge if my player is turned off.
Apart from that , everything seems to work well , I do not even know if this is really a problem , I did not let my battery run down lest I get stuck . As long as the player stays on, no worries, battery charging well. Of course I did all the basic wipe's (data/factory, cache, dalvik cache, battery stats).
Sorry for the long post, but I wanted to give as much information .
If someone has an idea of where it may come again, or at least tell me if it's serious in case my battery is fully discharged .
Thank you ! :good:
Edit : actualy I have installed the [ROM][4.3][YP-G70]CyanogenMod 10.2 - M1 Release whith the KKernel R2.1 by KOala888 (My YP-G70 run super fast...).
Click to expand...
Click to collapse
The charging mode bootloop has been a problem since the first gingerbread custom kernels and has been a problem up until KitKat. It is solved in KitKat. There is no fixing this problem in pre-KitKat custom roms without recompiling the kernel.
Here is information about the fix:
https://github.com/Meticulus/nutell...mmit/2f7c4affa392c9d0603c23cd3a007ed91dfe62f0
I have answered this question before. Getting tired of explaining it.
Strange boot loop too with YP-G70
Meticulus said:
The charging mode bootloop has been a problem since the first gingerbread custom kernels and has been a problem up until KitKat. It is solved in KitKat. There is no fixing this problem in pre-KitKat custom roms without recompiling the kernel.
Here is information about the fix:
....
I have answered this question before. Getting tired of explaining it.
Click to expand...
Click to collapse
Thanks for your answer. I understand you be tired of answering this problem ... But everything I 've read (and I read for hours and hours , really), I thought it only happened when a USB connection to a computer, not to a wall charging.
If it's just a minor bug and I can use my YP-G70 like that, it's going well, I 'm just afraid to let the battery get to the end and did not do anything. (I also read an old post that says let the battery get to 5% and then moving into CWM mode, and let it discharge completely before reconnecting to a wall charger)...
Last question, is there an kitkat "light" version of that will go as fast as the YP-G70 I installed (4.3) ?, because really outside this bug, all is so good and speed all I 'm doing it (basic use) is really fast.
Strange boot loop too with YP-G70 (4.3)
So I try to install a kitkat to see if the speed is correct.
Thank you again. :angel:
ToniOsX said:
Thanks for your answer. I understand you be tired of answering this problem ... But everything I 've read (and I read for hours and hours , really), I thought it only happened when a USB connection to a computer, not to a wall charging.
If it's just a minor bug and I can use my YP-G70 like that, it's going well, I 'm just afraid to let the battery get to the end and did not do anything. (I also read an old post that says let the battery get to 5% and then moving into CWM mode, and let it discharge completely before reconnecting to a wall charger)...
Last question, is there an kitkat "light" version of that will go as fast as the YP-G70 I installed (4.3) ?, because really outside this bug, all is so good and speed all I 'm doing it (basic use) is really fast.
Click to expand...
Click to collapse
When I was running pre-KitKat ROMs, I let the battery drain completely a few times. It does charge, when it is bootlooping. I let it bootloop for a while, say 10 mins or so and then disconnected it and started it up. Then plugged it back in and let it charge the rest of the way...
:good:
Strange boot loop too with YP-G70 (4.3) --> 4.4
Meticulus said:
When I was running pre-KitKat ROMs, I let the battery drain completely a few times. It does charge, when it is bootlooping. I let it bootloop for a while, say 10 mins or so and then disconnected it and started it up. Then plugged it back in and let it charge the rest of the way...
:good:
Click to expand...
Click to collapse
Well, I installed a Kitkat's ROM ,apart from the start a little longer, everything seems to work well. (Perhaps the least stable wireless)...
I'll try to use it like that a few days and I'll see.
Thank you again. :good:
Dear XDA friends :angel: I know this question has been asked before, but my current smartphone just died today and I'm in a hurry to revive my good old Xperia Z2.
Before I start I want to install a more current ROM than the last stock ROM (Android 6.0). What would you advice?
It should be stable, as few "not working" items als possible and current - in this order. (I unplugged the NFC chip anyway, camera and camera quality are higher priorities.)
Oero would be nice, but Nougat should do the job as well if there are more stable ROMs for it.
I want to install the ROM and then work with it as it is (no other mods and so on).
I would prefer one of the more known ROMs like Lineage or Resurrection Remix.
Forgive my "Let me google it for you" question, but you would really help me. Thanks in advance!
Ok, I'm pulling back my question after spending 6 hours to boot into recovery without success I've unlocked the bootloader and installed twrp but I can't boot into recovery neither from adb nor from key combinations. I can't root either. From what I've understand so far I have to go back to an older android version, then root, then do some other nasty stuff. I guess I'm out
fluxxis said:
Ok, I'm pulling back my question after spending 6 hours to boot into recovery without success I've unlocked the bootloader and installed twrp but I can't boot into recovery neither from adb nor from key combinations. I can't root either. From what I've understand so far I have to go back to an older android version, then root, then do some other nasty stuff. I guess I'm out
Click to expand...
Click to collapse
to boot into recovery : Press Volume Down + Power button until it vibrates .. and when the sony logo appears press Volume up + volume down + power button
hope it helps
Here is TWRP 3.2.1 build for Project Tango K1 ATAP.
Download
gdrive: twrp-3.2.1-yellowstone.img
mailru: twrp-3.2.1-yellowstone.img
Sources
device tree: https://github.com/HighwayStar/android_device_google_yellowstone
kernel: https://github.com/HighwayStar/android_kernel_google_yellowstone
How to install
enable USB debugging in stock ROM and run command: adb reboot bootloader
Unlock bootloader using command: fastboot oem unlock (it will wipe all your user data!)
With unlocked bootloader boot into stock rom and enable USB debugging again. Reboot to bootloader: adb reboot bootloader
Flash recovery image: fastboot flash recovery twrp-3.2.1-yellowstone.img
To boot into recovery you could run adb reboot recovery after booting to stock ROM or use Vol+ Vol- Power combo to boot in bootloader menu and select Recovery using volume keys and confirm by pressing Power.
XDA:DevDB Information
[RECOVERY][TWRP] Project Tango K1 ATAP TWRP 3.2.1, Tool/Utility for the Nvidia Shield Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/HighwayStar/android_kernel_google_yellowstone
Version Information
Status: Testing
Created 2019-02-19
Last Updated 2019-02-19
Any ROMs available for yellowstone? I can see one in use on the LineageOS Statistics page (search 14.1-20190208-UNOFFICIAL-yellowstone)
But I can't find it on xda.
I didn't get it to boot, but I was in a hurry and hopefully just forgot something simple. If anyone gets it working please post details. Hopefully this is legit:
Edit: link removed. Per the developer: "please don't use them. They're experimental, and won't be booting for some time... you run the chance of bricking. Definitely stay away until I make some form of announcement otherwise."
@highwaystar_ru gave me this ROM that is working splendidly on my yellowstone: https://cloud.mail.ru/public/Hmco/XryszodXm
From @highwaystar_ru:
It uses binary files from stock yellowstone and has some issues:
cameras doesnt work, video playback sometimes has artifacts, all cpu
cores always up (without it video playback lags), accelerometer sensor
inverted.
Me and couple of lineage devs working hard to port shieldtablet kernel
to yellowstone, it will allow to use shield binary files and resolve
most problems, but progress are really slow (but there is some
progress lately).
Click to expand...
Click to collapse
shiznit1618 said:
@highwaystar_ru gave me this ROM that is working splendidly on my yellowstone: https://cloud.mail.ru/public/Hmco/XryszodXm
From @highwaystar_ru:
Click to expand...
Click to collapse
Thanks! This is working very well so far for the limited testing I've done. I'll have to take it into the field and see how that goes .
Tried out that ROM , it's pretty good outside of issues listed bluetooth is non functional.
Mobile data , text, wifi etc working.
Back to life
Thanks to highwaystar_ru I was able to install twrp and then lineage 14.1 with Open GApps pico.
I hope that somebody will be able to bring this to 15.1
Please keep up your effort, Hurray I can use my tango again , at least some of it, would be great that bluetooth and cameras working and good luck with the shield software i'll be looking for it . Thanks alot
thanks
worked for me. . with all the restrictions added.. but still brought a perfectly fine tablet from no usage to home automation dashboard device
Great work thank you,
Also i tested that Rom in the thread and it works well despite the reversed sensor, bluetooth (and i report USB on dock non fuctional with rom)
has there been any progress on the Rom at all? thanks.
Any progress with this rom?
Also @shiznit1618 and @highwaystar_ru where are you guys collaborating? If this is a telegram, discord, or other chat group. I'd love to get in and talk, maybe help a bit. I'm currently on arcore devs slack chat but there isn't much activity in their #yellowstone channel.
https://arcore.slack.com
ShapeShifter499 said:
Any progress with this rom?
Also @shiznit1618 and @highwaystar_ru where are you guys collaborating? If this is a telegram, discord, or other chat group. I'd love to get in and talk, maybe help a bit. I'm currently on arcore devs slack chat but there isn't much activity in their #yellowstone channel.
https://arcore.slack.com
Click to expand...
Click to collapse
There does seem to be some active development on GitHub (within the last week) and I also found (from same developer on GitHub) a newer rom based on 15.1 although I couldn't get it to boot, seems I need to update TWRP, but trying to update TWRP it tells me the recovery partition exceeded size, so I assume I have to update boot as well (which I didn't do). i'd suggest checking on GitHub and contacting that developer.
https://github.com/TegraDevelopment/android_device_google_yellowstone
Bazathoth said:
There does seem to be some active development on GitHub (within the last week) and I also found (from same developer on GitHub) a newer rom based on 15.1 although I couldn't get it to boot, seems I need to update TWRP, but trying to update TWRP it tells me the recovery partition exceeded size, so I assume I have to update boot as well (which I didn't do). i'd suggest checking on GitHub and contacting that developer.
https://github.com/TegraDevelopment/android_device_google_yellowstone
Click to expand...
Click to collapse
Where did you find the 15.1 build?
ShapeShifter499 said:
Where did you find the 15.1 build?
Click to expand...
Click to collapse
http://updater.ods.ninja/yellowstone
This is the same project I had mentioned in post #3. I took the link down because it wasnt ready at the time and I've been waiting for the dev to let us know when its working. See post #3 for a quote from him...
But... there is a build from Feb 12. Please let us know how it goes if you try it. :good:
xaxxelous said:
http://updater.ods.ninja/yellowstone
This is the same project I had mentioned in post #3. I took the link down because it wasnt ready at the time and I've been waiting for the dev to let us know when its working. See post #3 for a quote from him...
But... there is a build from Feb 12. Please let us know how it goes if you try it. :good:
Click to expand...
Click to collapse
I have a new issue, my tablet is rebooting constantly. It will crash to a "red battery icon" and then boot back up to the lockscreen. I'm not sure if the battery in my unit is bad or if the battery calibration is messed up. Do you have any ideas what to do here?
My device was restored to stock btw.
ShapeShifter499 said:
I have a new issue, my tablet is rebooting constantly. It will crash to a "red battery icon" and then boot back up to the lockscreen. I'm not sure if the battery in my unit is bad or if the battery calibration is messed up. Do you have any ideas what to do here?
My device was restored to stock btw.
Click to expand...
Click to collapse
Will it stay on while plugged into the dock? Or usb even?
xaxxelous said:
Will it stay on while plugged into the dock? Or usb even?
Click to expand...
Click to collapse
I never got a hold of a original dock, I didn't check to see if keeping it on charge helped.
ShapeShifter499 said:
I never got a hold of a original dock, I didn't check to see if keeping it on charge helped.
Click to expand...
Click to collapse
Did you flash that build from Feb 12?
How did you return to stock? A TWRP backup or do you have original firmware?
Does it keep bootlooping by itself without any input from you or will it sit stable at the lockscreen? Can you keep it turned off?
Depending on the answers to those questions, the first thing I would do is turn it off and plug it in. Let it sit until fully charged. It takes a long time via USB, and even longer if it is on. Not that this is a solution, just troubleshooting...
xaxxelous said:
Did you flash that build from Feb 12?
How did you return to stock? A TWRP backup or do you have original firmware?
Does it keep bootlooping by itself without any input from you or will it sit stable at the lockscreen? Can you keep it turned off?
Depending on the answers to those questions, the first thing I would do is turn it off and plug it in. Let it sit until fully charged. It takes a long time via USB, and even longer if it is on. Not that this is a solution, just troubleshooting...
Click to expand...
Click to collapse
It reboots without me touching. The main OS has a full battery icon but the reboot flashes the red battery icon before booting. I flashed using NVFlash a copy of the stock OS I got from the arcore stack. Someone gave me their APX package that NVFlash requires.
That file is here: https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Conversation starts here: https://arcore.slack.com/archives/C68HHETL7/p1549401595001100
Main quote of interest from that chat:
Greg Willard (r3pwn) 1:20 PM
Around 3 mins left on the upload
1:24
What I did in the interest of still letting a device turn on if someone didn't get the chance to back up their persist/persistbk, was I took mine, and scrubbed the mac addresses and serial number. So the macs are set to 00:11:22:33:44:55:66, and the serial num is 012345678.
1:25
... aaaand here you go https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Click to expand...
Click to collapse
ShapeShifter499 said:
It reboots without me touching. The main OS has a full battery icon but the reboot flashes the red battery icon before booting. I flashed using NVFlash a copy of the stock OS I got from the arcore stack. Someone gave me their APX package that NVFlash requires.
That file is here: https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Conversation starts here: https://arcore.slack.com/archives/C68HHETL7/p1549401595001100
Main quote of interest from that chat:
Click to expand...
Click to collapse
I can't see that convo without an account. Have you asked for help there?
Until I get home I can't really look at that apx. Maybe install TWRP and the ROM from post #4 or a TWRP backup? Without knowing what that apx flashed its hard to say. The ROM from highwaystar_ru (mostly) works. Might at least get you out of the bootloop.
And just to be clear, you did not flash that 15.1 build, right? What were you running before flashing the apx?
Unless TWRP and that LOS 14.1 ROM or a TWRP backup help we've gone off topic for this thread...
Hello guys,
I flashed the Android 11 firmware on my Samsung Galaxy A21s (SM-A217F) using odin. The progress didn't finish successful because of an fail.
Now my phone seems to not boot anymore. It shows the "Samsung powered by Android" - Screen and after this nothing more is happening. It's not possible to fully start the device. Also downloadmode doen't work. Connect the phone to PC doesn't work because phone is not turned on.
Is it possible to install OS/ROM/firmware with an SD-card or otherwise?
Do you have any other ideas to safe the phone und make it running again?
Please bear with me if the topic already exists and I didn't find it in the search. I apologize in this case and ask for reference to the forum post.
Thanks a lot!
Knut222 said:
Hello guys,
I flashed the Android 11 firmware on my Samsung Galaxy A21s (SM-A217F) using odin. The progress didn't finish successful because of an fail.
Now my phone seems to not boot anymore. It shows the "Samsung powered by Android" - Screen and after this nothing more is happening. It's not possible to fully start the device. Also downloadmode doen't work. Connect the phone to PC doesn't work because phone is not turned on.
Is it possible to install OS/ROM/firmware with an SD-card or otherwise?
Do you have any other ideas to safe the phone und make it running again?
Please bear with me if the topic already exists and I didn't find it in the search. I apologize in this case and ask for reference to the forum post.
Thanks a lot!
Click to expand...
Click to collapse
@Knut222
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A as it didn't qualify for development.
Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
download mode will work again once device left boot-loop. shutdown can be achieved by draining battery or long press power
aIecxs said:
download mode will work again once device left boot-loop. shutdown can be achieved by draining battery or long press power
Click to expand...
Click to collapse
Hello alecxs,
thanks for your answer. The phone is turned off. It shuts off automaticly after showing the first screen. Nothing else happens.
Downloadmode with pushing the buttons and insert the data cabel is not working. It also shows that screen and goes to black screen again.
It can work if phone Is bootloop will go again on download mode open your phone disconnect battery and replace wait for 7 or 10second then connect the battery hold volume up and down connect usb cable will redirect you for download mode thank you
Verspot said:
It can work if phone Is bootloop will go again on download mode open your phone disconnect battery and replace wait for 7 or 10second then connect the battery hold volume up and down connect usb cable will redirect you for download mode thank you
Click to expand...
Click to collapse
Hello Verspot,
thanks for your answer!
The battery is permanently installed and not possible to take out.
Knut222 said:
Hello Verspot,
thanks for your answer!
The battery is permanently installed and not possible to take out.
Click to expand...
Click to collapse
It's possible sir you can do it also for doing that there's no skill required
Verspot said:
It's possible sir you can do it also for doing that there's no skill required
Click to expand...
Click to collapse
well, that's not true. this device requires high skills and hair dryer - I do strongly not recommend this
just wait few weeks for the battery is drained
aIecxs said:
well, that's not true. this device requires high skills and hair dryer - I do strongly not recommend this
just wait few weeks for the battery is drained
Click to expand...
Click to collapse
I will give it a try, if there is no other option.
But is my phone really in a bootloop? I don't think so. In the loop the Android-screen shows again and again. In my case, it only shows once including vibration and after this the screen turn off again. No second boot. The phone seems to turn off again.
In this case it will take ages to let the battery be empty.
yes that's boot-loop
if device would have powered off you would see charging animation when plugged..
according to this factory reset will solve?
Fingerprint sensor after update
Just installed UPDATE for A22. Fingerprint sensor not working any suggestions?
eu.community.samsung.com
aIecxs said:
yes that's boot-loop
if device would have powered off you would see charging animation when plugged..
Click to expand...
Click to collapse
I've tried it. The is truely no charging animation.
So now I need to let die battery die and once that happend booting into download-mode is possible again?
Why did u try to flash using odin in the first place?
don't nail me but I believe buttons for download mode are read from ABL (aboot.mbn) it's very unlikely that OTA or stock ROM caused corrupted bootloader...
you can see Samsung logo, guess that means aboot is alive
@Verspot pointed out it requires vol dn + vol up + usb cable to enter download mode (imho bit unusual)
https://www.hardreset.info/devices/samsung/samsung-galaxy-a21s/download-mode
aIecxs said:
don't nail me but I believe buttons for download mode are read from ABL (aboot.mbn) it's very unlikely that OTA or stock ROM caused corrupted bootloader...
you can see Samsung logo, guess that means aboot is alive
@Verspot pointed out it requires vol dn + vol up + usb cable to enter download mode (imho bit unusual)
https://www.hardreset.info/devices/samsung/samsung-galaxy-a21s/download-mode
Click to expand...
Click to collapse
The mentioned button combination is the one I used to get to download mode before I flashed the firmware.
Now the button combination is not working.
It will not boot to recovery or the download mode.
Yes but what I meant the usb cable is important (instead pwr button) - obviously you did it right before, just wanted to clarify intentionally/unintentionally.
The error screen "fingerprint protection failed." suggest it can not read fingerprint so I guess your phone stucks somewhere beyond aboot, that's why it does not work
after doing some more research I have bad news for you:
found two other sites with same issue "fingerprint protection failed" (in espanol and nepalese) both suggest bricked bootloader which can only fixed by JTAG or ISP.
If that's true I recommend RMA to Samsung there is a good chance they treat as hardware failure (don't tell anything)
https://www.google.com/search?q=a21s+dead+boot+repair
Woo
aIecxs said:
well, that's not true. this device requires high skills and hair dryer - I do strongly not recommend this
just wait few weeks for the battery is drained
Click to expand...
Click to collapse
Woow but it's possible and easy maybe for myself
aIecxs said:
after doing some more research I have bad news for you:
found two other sites (in espanol and nepalese) both suggest bricked bootloader which can only fixed by JTAG.
If that's true I recommend RMA to Samsung there is a good chance they treat as hardware failure (don't tell anything)
Click to expand...
Click to collapse
I don't like to hear that but after nothing so far worked, I expacted something like that.
Is my idea to boot the phone from an SD-card (like booting windows from USB-drive) and reinstall Android Firmware nonsense or is it somehow possible?