Related
Hi there. After (an attempt) to unlock the bootloader of my A50 and installing TWRP Recovery (TWRP_A50_Magisk_Prepatched) i find myself in an orange bootstate. I can't get it into recovery, download or fastboot mode. It seems like a full brick. I can't even power off the device. Only Volume up, Volume down and Power button let's the device reboot but then the same boot problems appear. Is there anything i can do to recover my phone?
Text of first screen when booting up:
"The phone's bootloader is unlocked and it's software integrity can't be verified. Andy data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone". Press power key to continue"
Text of second screen when booting up:
"The phone is not running Samsung's official software. You may have problems with features or security and you won't be able to install software updates"
Any ideas!?
flash stock via odin
nikolas60 said:
flash stock via odin
Click to expand...
Click to collapse
I have the same problem described as above. To use odin you need access to the download menu. Personally, i can not even access the download menu using any cobination of volume up-down & power combination...
RestrictedPower said:
I have the same problem described as above. To use odin you need access to the download menu. Personally, i can not even access the download menu using any cobination of volume up-down & power combination...
Click to expand...
Click to collapse
caztricum said:
Hi there. After (an attempt) to unlock the bootloader of my A50 and installing TWRP Recovery (TWRP_A50_Magisk_Prepatched) i find myself in an orange bootstate. I can't get it into recovery, download or fastboot mode. It seems like a full brick. I can't even power off the device. Only Volume up, Volume down and Power button let's the device reboot but then the same boot problems appear. Is there anything i can do to recover my phone?
Text of first screen when booting up:
"The phone's bootloader is unlocked and it's software integrity can't be verified. Andy data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone". Press power key to continue"
Text of second screen when booting up:
"The phone is not running Samsung's official software. You may have problems with features or security and you won't be able to install software updates"
Any ideas!?
Click to expand...
Click to collapse
Try connecting your phone to your PC with the USB Type C cable, and do VolDown + Power to reboot the phone, and the moment the screen turns black, press VolUp + VolDown. It'll bring you to a different screen where you can press VolUp to go into download mode for flashing the stock firmware via Odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
jtanhw said:
Try connecting your phone to your PC with the USB Type C cable, and do VolDown + Power to reboot the phone, and the moment the screen turns black, press VolUp + VolDown. It'll bring you to a different screen where you can press VolUp to go into download mode for flashing the stock firmware via Odin. I got my stock firmware from (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
This did it for me! Many thanks...
jtanhw said:
download mode for flashing the stock firmware via Odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
I had the same problem and managed to get back to the Download Page.
How do I find out what is the correct region of the correct Modem Version of my phone? It's an S10 (intl unlocked) that I bought in the US from Amazon.
TheAsker70 said:
I had the same problem and managed to get back to the Download Page.
How do I find out what is the correct region of the correct Modem Version of my phone? It's an S10 (intl unlocked) that I bought in the US from Amazon.
Click to expand...
Click to collapse
You can find answers in the S10 forum. But I think the steps will be the same (this is A8 device/forum).
Rexton270 said:
You can find answers in the S10 forum. But I think the steps will be the same (this is A8 device/forum).
Click to expand...
Click to collapse
My bad. Apologize. Will head over there. Thanks!
No bother. Hope you are sorted by now.
this is the exact same problem that goes for me with my samsung a505gn, i flashed a twrp 3.3.1-2_zvox and im stuck at this state. i found my stock firmware at the link provided above, but there are multiple types of a505gn stock firmware (XTC, SMA, GLB), question is, how do i know the correct type of stock firmware to reinstall to my phone, hence, having a limited information of the phone because of this problem (which is stuck at orange bootstate).
Same Problem
caztricum said:
This did it for me! Many thanks...
Click to expand...
Click to collapse
for now work on not sir
i have same problem stuk n auto restart
if u work can u help me thanks
jtanhw said:
try connecting your phone to your pc with the usb type c cable, and do voldown + power to reboot the phone, and the moment the screen turns black, press volup + voldown. It'll bring you to a different screen where you can press volup to go into download mode for flashing the stock firmware via odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your model number - sm-a505f/sm-a505fn/sm-a505fm, and select the correct region. Also, select the correct modem version (the last 4 letters/number of the item to download). Then, follow the "flashing guide" at the bottom of the samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
thank you very much
thanks for your comment, its help me. my Samsung A50 hanged on boot-loader and loop turn on/off.
Is there a way to install twrp if the problem is like this every time I try to install the twrp it came to this problem. Please help me
jtanhw said:
Try connecting your phone to your PC with the USB Type C cable, and do VolDown + Power to reboot the phone, and the moment the screen turns black, press VolUp + VolDown. It'll bring you to a different screen where you can press VolUp to go into download mode for flashing the stock firmware via Odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
Hi this helped me many thanks <3
jtanhw said:
Try connecting your phone to your PC with the USB Type C cable, and do VolDown + Power to reboot the phone, and the moment the screen turns black, press VolUp + VolDown. It'll bring you to a different screen where you can press VolUp to go into download mode for flashing the stock firmware via Odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
thank you so much you just helped me save my phone
peace keeper said:
thank you so much you just helped me save my phone
Click to expand...
Click to collapse
Have you got the a21s? As can't root it, as every twrp source I use soft bricks the phone, or just bootloops, or goes into error at boot up and stops half way. Was thinking trying other custom recovery. Any tips m8?
jtanhw said:
Try connecting your phone to your PC with the USB Type C cable, and do VolDown + Power to reboot the phone, and the moment the screen turns black, press VolUp + VolDown. It'll bring you to a different screen where you can press VolUp to go into download mode for flashing the stock firmware via Odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
My phone is Realme 6 it doesnt take me anywhere my laptop only does the plugging in and plugging out sound all the time and when I let go of the volume buttons the bootloop happens again
caztricum said:
Hi there. After (an attempt) to unlock the bootloader of my A50 and installing TWRP Recovery (TWRP_A50_Magisk_Prepatched) i find myself in an orange bootstate. I can't get it into recovery, download or fastboot mode. It seems like a full brick. I can't even power off the device. Only Volume up, Volume down and Power button let's the device reboot but then the same boot problems appear. Is there anything i can do to recover my phone?
Text of first screen when booting up:
"The phone's bootloader is unlocked and it's software integrity can't be verified. Andy data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone". Press power key to continue"
Text of second screen when booting up:
"The phone is not running Samsung's official software. You may have problems with features or security and you won't be able to install software updates"
Any ideas!?
Click to expand...
Click to collapse
caztricum said:
Hi there. After (an attempt) to unlock the bootloader of my A50 and installing TWRP Recovery (TWRP_A50_Magisk_Prepatched) i find myself in an orange bootstate. I can't get it into recovery, download or fastboot mode. It seems like a full brick. I can't even power off the device. Only Volume up, Volume down and Power button let's the device reboot but then the same boot problems appear. Is there anything i can do to recover my phone?
Text of first screen when booting up:
"The phone's bootloader is unlocked and it's software integrity can't be verified. Andy data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone". Press power key to continue"
Text of second screen when booting up:
"The phone is not running Samsung's official software. You may have problems with features or security and you won't be able to install software updates"
Any ideas!?
Click to expand...
Click to collapse
I HAD the same issue an I resolved it.
There are 2 methods to overcome this problem.
I even wrote a PDF and attached here in this post.
Below is SOME content from the PDF so it could be easy for users to find it on Google. I still strongly recommend you to refer to the PDF attached as it has pictures as well.
Samsung Galaxy M31 / Samsung M31 Screen is stuck on the following error message / error screen:
‘This phone’s bootloader is unlocked and the software integrity can’t be verified. Any data on this phone may be vulnerable to attackers. Don’t store any important or sensitive information on the phone.’
‘The phone is not running Samsung’s official software. You may have problems with features or security. And you won’t be able to install software updates.’ (error screen looks like below):
I was using correct TWRP and I was on Android 11 One UI 3.1.
Just to experiment, I flashed wrong TWRP version which was meant for Android 10 while being on Android 11. And so this problem started. Stuck on the error screen. Phone will not power off or on. Could not even enter the bootloader screen. Nothing works whatever keys I press. The same screen comes up. When the phone goes off and the phone will not accept charging that mean even you it whole night connected to charger, phone will not be charged- the same error screen.
So, the battery was not charging (my battery was at 24% just before this tragedy happened. It was late night and I thought of waking up tomorrow and plug in charger for an hour thinking if its battery is quite charged then I will follow Fix Method 2).
I woke up next morning and the phone was off (Battery drained fully). To this I was happy thinking that I can now hold Volume + and Power key and connect USB cable to enter Bootloader. When I did that phone would enter bootloader and gets switched off automatically (remember the battery was drained completely, charger too failed to charge battery and phone is not drawing enough power from USB port to stay on bootloader. On bootloader screen the phone’s display is fully on so more power usage).
Now I knew that the USB port is not proving enough power so that the phone could remain On while in bootloader when I hold Volume + and Power key and connect USB cable to enter Bootloader. I know for sure that Fix Method 2 will fix this for sure but it’s quite tiring.
So I referred to my PC manual to figure out which USB port provides maximum power. I found the right port (refer pic below):
So now I figured out 5 Volts port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
If you don’t know which USB Port is 5 Volts then I recommend you to try all the ports and try getting to bootloader screen.
So when the phone was off, I pressed and hold the Volume up and Volume down key and with other hand I connected USB cable and now the phone went in bootloader and then I quickly flashed the right TWRP. Disconnected the USB cable and put the phone to charge and now it was accepting charge. Phone was back into life.
So I resolved it by Fix Method 1 below:
Fix Method 1: On my PC, I located the 5 Volts USB port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
Entered Bootloader screen.
How to enter bootloader screen:
Assuming your phone is unlocked and the developers options are on and you have enabled USB debugging in Developer options and you have little knowledge of flashing firmware or TWRP via Odin.
Press and hold Volume Up and Volume down keys together with one hand and using other hand, connect USB cable to phone and release all the keys. Now phone will show bootloader screen which looks like below pic:
I quickly flashed the correct TWRP via Odin:
Flashing TWRP:
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
· Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
· Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Use Vol up + Power + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
TWRP screen was up. I tapped on Reboot and it did not reboot because the battery was not enough charged however I saw that TWRP Menu this means TWRP was working so the phone will boot up once it is charged.
Now I plugged in charger and was happy to see the correct charging screen (refer below pic):
I would turn power switch Off and On it quicky to know the charging percentage.
When it reached 20% I started phone (obviously by long pressing power key and it booted up just fine).
I loved myself
Fix Method 2:
Remove the phone’s back cover.
Be careful while removing the back case as you could screw the finger print sensor.
Disconnect the battery connector from motherboard and reconnect it.
Do not turn on the phone. As turning On will again get you back to the same error screen.
Put the back cover on.
Connect charger. Do not turn phone On yet. Wait for 5 min.
Do not even touch the phone.
Now you need to know the percentage of charge so do not hit the power button yet instead locate the main switch to which your charger is connected. Quickly turn Off and On and look at phone it shows charging percentage.
Once charging percentage reached around 20% you can touch your phone and power it on and it should boot up fine. It should not take more than 5 min to boot up.
Atharkhan101 said:
I HAD the same issue an I resolved it.
There are 2 methods to overcome this problem.
I even wrote a PDF and attached here in this post.
Below is SOME content from the PDF so it could be easy for users to find it on Google. I still strongly recommend you to refer to the PDF attached as it has pictures as well.
Samsung Galaxy M31 / Samsung M31 Screen is stuck on the following error message / error screen:
‘This phone’s bootloader is unlocked and the software integrity can’t be verified. Any data on this phone may be vulnerable to attackers. Don’t store any important or sensitive information on the phone.’
‘The phone is not running Samsung’s official software. You may have problems with features or security. And you won’t be able to install software updates.’ (error screen looks like below):
I was using correct TWRP and I was on Android 11 One UI 3.1.
Just to experiment, I flashed wrong TWRP version which was meant for Android 10 while being on Android 11. And so this problem started. Stuck on the error screen. Phone will not power off or on. Could not even enter the bootloader screen. Nothing works whatever keys I press. The same screen comes up. When the phone goes off and the phone will not accept charging that mean even you it whole night connected to charger, phone will not be charged- the same error screen.
So, the battery was not charging (my battery was at 24% just before this tragedy happened. It was late night and I thought of waking up tomorrow and plug in charger for an hour thinking if its battery is quite charged then I will follow Fix Method 2).
I woke up next morning and the phone was off (Battery drained fully). To this I was happy thinking that I can now hold Volume + and Power key and connect USB cable to enter Bootloader. When I did that phone would enter bootloader and gets switched off automatically (remember the battery was drained completely, charger too failed to charge battery and phone is not drawing enough power from USB port to stay on bootloader. On bootloader screen the phone’s display is fully on so more power usage).
Now I knew that the USB port is not proving enough power so that the phone could remain On while in bootloader when I hold Volume + and Power key and connect USB cable to enter Bootloader. I know for sure that Fix Method 2 will fix this for sure but it’s quite tiring.
So I referred to my PC manual to figure out which USB port provides maximum power. I found the right port (refer pic below):
So now I figured out 5 Volts port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
If you don’t know which USB Port is 5 Volts then I recommend you to try all the ports and try getting to bootloader screen.
So when the phone was off, I pressed and hold the Volume up and Volume down key and with other hand I connected USB cable and now the phone went in bootloader and then I quickly flashed the right TWRP. Disconnected the USB cable and put the phone to charge and now it was accepting charge. Phone was back into life.
So I resolved it by Fix Method 1 below:
Fix Method 1: On my PC, I located the 5 Volts USB port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
Entered Bootloader screen.
How to enter bootloader screen:
Assuming your phone is unlocked and the developers options are on and you have enabled USB debugging in Developer options and you have little knowledge of flashing firmware or TWRP via Odin.
Press and hold Volume Up and Volume down keys together with one hand and using other hand, connect USB cable to phone and release all the keys. Now phone will show bootloader screen which looks like below pic:
I quickly flashed the correct TWRP via Odin:
Flashing TWRP:
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
· Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
· Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Use Vol up + Power + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
TWRP screen was up. I tapped on Reboot and it did not reboot because the battery was not enough charged however I saw that TWRP Menu this means TWRP was working so the phone will boot up once it is charged.
Now I plugged in charger and was happy to see the correct charging screen (refer below pic):
I would turn power switch Off and On it quicky to know the charging percentage.
When it reached 20% I started phone (obviously by long pressing power key and it booted up just fine).
I loved myself
Fix Method 2:
Remove the phone’s back cover.
Be careful while removing the back case as you could screw the finger print sensor.
Disconnect the battery connector from motherboard and reconnect it.
Do not turn on the phone. As turning On will again get you back to the same error screen.
Put the back cover on.
Connect charger. Do not turn phone On yet. Wait for 5 min.
Do not even touch the phone.
Now you need to know the percentage of charge so do not hit the power button yet instead locate the main switch to which your charger is connected. Quickly turn Off and On and look at phone it shows charging percentage.
Once charging percentage reached around 20% you can touch your phone and power it on and it should boot up fine. It should not take more than 5 min to boot up.
Click to expand...
Click to collapse
Atharkhan101 said:
I HAD the same issue an I resolved it.
There are 2 methods to overcome this problem.
I even wrote a PDF and attached here in this post.
Below is SOME content from the PDF so it could be easy for users to find it on Google. I still strongly recommend you to refer to the PDF attached as it has pictures as well.
Samsung Galaxy M31 / Samsung M31 Screen is stuck on the following error message / error screen:
‘This phone’s bootloader is unlocked and the software integrity can’t be verified. Any data on this phone may be vulnerable to attackers. Don’t store any important or sensitive information on the phone.’
‘The phone is not running Samsung’s official software. You may have problems with features or security. And you won’t be able to install software updates.’ (error screen looks like below):
I was using correct TWRP and I was on Android 11 One UI 3.1.
Just to experiment, I flashed wrong TWRP version which was meant for Android 10 while being on Android 11. And so this problem started. Stuck on the error screen. Phone will not power off or on. Could not even enter the bootloader screen. Nothing works whatever keys I press. The same screen comes up. When the phone goes off and the phone will not accept charging that mean even you it whole night connected to charger, phone will not be charged- the same error screen.
So, the battery was not charging (my battery was at 24% just before this tragedy happened. It was late night and I thought of waking up tomorrow and plug in charger for an hour thinking if its battery is quite charged then I will follow Fix Method 2).
I woke up next morning and the phone was off (Battery drained fully). To this I was happy thinking that I can now hold Volume + and Power key and connect USB cable to enter Bootloader. When I did that phone would enter bootloader and gets switched off automatically (remember the battery was drained completely, charger too failed to charge battery and phone is not drawing enough power from USB port to stay on bootloader. On bootloader screen the phone’s display is fully on so more power usage).
Now I knew that the USB port is not proving enough power so that the phone could remain On while in bootloader when I hold Volume + and Power key and connect USB cable to enter Bootloader. I know for sure that Fix Method 2 will fix this for sure but it’s quite tiring.
So I referred to my PC manual to figure out which USB port provides maximum power. I found the right port (refer pic below):
So now I figured out 5 Volts port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
If you don’t know which USB Port is 5 Volts then I recommend you to try all the ports and try getting to bootloader screen.
So when the phone was off, I pressed and hold the Volume up and Volume down key and with other hand I connected USB cable and now the phone went in bootloader and then I quickly flashed the right TWRP. Disconnected the USB cable and put the phone to charge and now it was accepting charge. Phone was back into life.
So I resolved it by Fix Method 1 below:
Fix Method 1: On my PC, I located the 5 Volts USB port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
Entered Bootloader screen.
How to enter bootloader screen:
Assuming your phone is unlocked and the developers options are on and you have enabled USB debugging in Developer options and you have little knowledge of flashing firmware or TWRP via Odin.
Press and hold Volume Up and Volume down keys together with one hand and using other hand, connect USB cable to phone and release all the keys. Now phone will show bootloader screen which looks like below pic:
I quickly flashed the correct TWRP via Odin:
Flashing TWRP:
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
· Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
· Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Use Vol up + Power + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
TWRP screen was up. I tapped on Reboot and it did not reboot because the battery was not enough charged however I saw that TWRP Menu this means TWRP was working so the phone will boot up once it is charged.
Now I plugged in charger and was happy to see the correct charging screen (refer below pic):
I would turn power switch Off and On it quicky to know the charging percentage.
When it reached 20% I started phone (obviously by long pressing power key and it booted up just fine).
I loved myself
Fix Method 2:
Remove the phone’s back cover.
Be careful while removing the back case as you could screw the finger print sensor.
Disconnect the battery connector from motherboard and reconnect it.
Do not turn on the phone. As turning On will again get you back to the same error screen.
Put the back cover on.
Connect charger. Do not turn phone On yet. Wait for 5 min.
Do not even touch the phone.
Now you need to know the percentage of charge so do not hit the power button yet instead locate the main switch to which your charger is connected. Quickly turn Off and On and look at phone it shows charging percentage.
Once charging percentage reached around 20% you can touch your phone and power it on and it should boot up fine. It should not take more than 5 min to boot up.
Click to expand...
Click to collapse
Hi, friend. I have the same problem. But I don't even have a bootloader. When I log in, I just get a black screen.
Hi,
my Philips 48PFS8109/12 made problems for a long time already when trying to power it on: it needed several attempts to cut off the power, reconnect the power and let it try to boot, cut off the power and reconnect again, etc.
Sometimes it entered the famous boot loop, sometimes it freezed, showing the Philips logo on screen, sometimes it only enabled the Philips logo on the camera and the screen remained black.
Over time it got worse: the more and more power cycles were needed to let it successfully boot.
But now it seems to be dead forever: most of the times it remains black now, only sometimes the logo appears on screen and I didn't managed to get it to boot successfully again.
Repair costs are around 500€ and would result in different features, due to no availability of the original hardware.
I tried everything I found on the internet to try to recover it:
- Let it boot to safe mode, a) using the joystick button on the back with pressing it in every direction and directly for over a minute when connecting the power, b) using the remote control OK and power buttons for the same time
- Let it boot from a FAT USB stick containing a) the wipe data tool, b) the firmware upgrade package, either in root directory, or in an "upgrades" subdirectory
- Connect it via USB A-to-A cable, and try to connect to it via "adb" command
Nothing helped/worked.
Problem is, that I am unable to enable any developer settings, as I am unable to get it running at all.
Question to the community: is there any other possibility to rescue the device (e. g. access the Android storage without the need to power it on, any secret way to clean the internal storage via hardware access/shortcut of some contacts)?
Its such a pity, the other hardware is so excellent, its just the Android system (or what Philips degenerated it to) that prevents the system from running.
Any help greatly appreciated.
Hello,
I had the same problem, let me explain what I do :
- Unplug power cable. Boot to safe mode using the joystick button on the back only with down arrow (without pressing it)
- Wipe data partition
- Flash the rom
- Flash android with the last update
- reboot
tontonfrancky said:
Hello,
I had the same problem, let me explain what I do :
- Unplug power cable. Boot to safe mode using the joystick button on the back only with down arrow (without pressing it)
- Wipe data partition
- Flash the rom
- Flash android with the last update
- reboot
Click to expand...
Click to collapse
Hi,
thank you for your answer. As I wrote, I already tried this in the past.
But I tried it again now and it still doesn't works. I hold the button for approx. 15 minutes, but it does not boot into safe mode. It only shows the Philips logo after some times, then goes black again. At the beginning it took long a time to first show the logo (approx. 1,5 minutes) and the logo was diplayed approx. 8 seconds, then later on the cycles got shorter and shorter. At the end, the logo was displayed for a second only.
Does s. o. knows if it is possible to just use the display? E. g. take some old Android hardware and connect it to the display only?
I don't want to throw this thing away, as the hardware is so excellent.... :cyclops:
Hi,
maybe the hardware upgrade kit is a solution for you:
https://toengel.net/philipsblog/201...pgrade-kit-fuer-2013er-2014er-und-2015er-tvs/
[email protected]
Toengel said:
[..] maybe the hardware upgrade kit is a solution for you: [..]
Click to expand...
Click to collapse
Hi and thanks for these informations.
This definitely is an option for me!
I already visited a certified Philips repair center and they offered me to replace the hardware which costs approx. 500 € all in all. I asked them for giving me the hardware to let me replace it on my own, but they denied it in answering that the new hardware has to be programmed, which is too complicated for an end user.
Using your informations, I will evaluate if this would be a doable approach for me.
Hi,
this "programming" is very easy... just putting 2 files on USB and start the TV... And 500 EUR is way to much... you should get it below 300 EUR.
[email protected]
So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?
I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.
I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.
When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.
With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.
I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.
Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
If the phone is bootloader locked don't do anything, take it to service center it's out of your hands.
If service center intends to charge you something well you could find some people online with edl accounts to do flashing for you but this sounds like hardware issue if you don't see poco logo ...
Edit: Sry didn't read the post fully - did u try fastboot devices when in fastboot mode - volume down and power ? If it is recognized and bootloader unlocked you can try flashing - go with xiaomi firmware, last thing you want is to be stuck on custom firmware when you take it in for repair - again only if bootloader is unlocked
since your brother pc can recognize, tried fastboot miui.eu on his pc
but I had this problem before and the only solution is to change mainboard on the xiaomi service center.
rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
Do you have any clue as to why this happened? Any mods done besides applying Magisk?
If the software got damaged, you could try the EDL Mode but that's difficult. Should be your last resort.
If hardware, then I don't know unfortunately...but then how?
rururi said:
So I am normally using my phone scrolling through social media but it suddenly froze so I tried to hard reset it, but it goes in to a bootloop without any display on the screen. I could tell it is on a bootloop because of the repeating vibration everytime the phone boots up.
My device is Poco F3 (alioth) Running stock MIUI 12.5 bootloader unlocked and rooted with Magisk.
Things I have tried:
Long pressing power button, long pressing both power button and volume down button, long pressing power and volume up button, then long pressing all of them.
Plugging it on my PC but it doesn't even detect it. Tried inputting
Code:
adb devices
and
Code:
fastboot devices
Still doesn't work. I even made sure that my drivers are working so I tried it on my brothers Poco F3 and the PC can detect his phone through ADB commands.
Waiting for a day if it magically turns on again. Nope.
Charging it up because maybe the battery is low. Nope.
At this point my only two choices is opening up the back panel then replugging the battery so it completely turns off and hopefully boots up. But its a risky task since I don't have special tools to open up my phone, and my another choice is just bring it on a service center.
Click to expand...
Click to collapse
If it's recognised by your brothers pc, try that pc for flashing stock fastboot rom using miflash, and don't forget to choose 'flash and wipe' instead of 'flash and lock' in bottom right corner of miflash. Let us know how you get on
Happened today. Random bootloop while under normal use. Also occasionally attempted to trigger the emergency SOS call when power BTN clicks 5 times.
Saved by a solution in poco x3 thread.
The failure mode I experienced was possibly a "sticky" power button.unsure if it's an electrical short or something mechanical in nature tho since it's intermittent triggering of the power button.
Temp fix was some quick clicks of the power button a bunch of times(20-30 clicks?).
Also shut off the emergency sos function.
jowaii89 said:
Happened today. Random bootloop while under normal use. Also occasionally attempted to trigger the emergency SOS call when power BTN clicks 5 times.
Saved by a solution in poco x3 thread.
The failure mode I experienced was possibly a "sticky" power button.unsure if it's an electrical short or something mechanical in nature tho since it's intermittent triggering of the power button.
Temp fix was some quick clicks of the power button a bunch of times(20-30 clicks?).
Also shut off the emergency sos function.
Click to expand...
Click to collapse
Same... it started calling emergency number and wouldn't shut off by holding power button.
Worst device ever
{Mod edit: Inappropriate language edited. Oswald Boelcke}
Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome
afresh said:
Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome
Click to expand...
Click to collapse
Is it still possible to back up all your data at this point?
Have you tried adb pull your userdata partition?
wenyendev said:
Is it still possible to back up all your data at this point?
Have you tried adb pull your userdata partition?
Click to expand...
Click to collapse
They can’t boot….adb only works when booting or booted, and if it bootloops, they won’t have time to pull their data.
afresh said:
Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome
Click to expand...
Click to collapse
Bootloader locked or unlocked?
Even if you cannot boot into system, but if
- USB debugging is enabled, and operational;
- a cable works;
- you can boot into recovery.
Adb shall work in recovery.
Hope it helps.
https://forum.xda-developers.com/t/bootloop-on-mi4w.3558835/
Unfortunately, USB debugging was not enabled. I stopped developing for Android quite a while back now, and I don't turn on USB debugging anymore.
@Arealhooman My bootloader is locked... I tried unlocking it with MTKClient, but no success since the phone reboots during the process.
wenyendev said:
Hope it helps.
https://forum.xda-developers.com/t/bootloop-on-mi4w.3558835/
Click to expand...
Click to collapse
This helped a lot actually!
It seems that the power button got faulty and got constantly pressed, making the phone constantly hard-rebooting itself.
I have a piece of paper preventing the buttons from contacting the motherboard, and the phone stopped rebooting when charging!
Ingenious method. Glad you solved the issue.
I enabled USB debugging to be able to reboot into fastboot / bootloader without the buttons (since my piece or paper prevents all the button from working xD)
wenyendev said:
Even if you cannot boot into system, but if
- USB debugging is enabled, and operational;
- a cable works;
- you can boot into recovery.
Adb shall work in recovery.
Click to expand...
Click to collapse
Only custom. Stock doesn’t support it.
Bro first check if your power button is working fine, if it is being pressed by any hardware issue it can happen, and when you fastboot try flashing recovery within that time fastboot remains.