Question "Boot Command is not allowed in Lock State" or "Erase is not allowed in Lock State" - Redmi Note 10 Pro

Hello All, I've researching this thread to try to fix an issue on my Redmi Note 10 Pro.
One week ago the phone got in a reboot loop without any change from my side, In some research I saw a few foruns saying that this was because an MIUI Update which bricked my phone.
I tried to enter using the cellphone in the recovery mode, however I cant, the only thing I can do is to use the fastboot.
I installed, ran adb fastboot however when I try to erase all data or install TWRP the message "Boot Command is not allowed in Lock State" or "Erase is not allowed in Lock State"
I didnt have the chance to put the phone in Debugging mode, it only bricked w/o any change from my side.
The question is: Is there a way to remove the phone from Lock State ? using software, commandas or something else ?

lokopaca said:
Hello All, I've researching this thread to try to fix an issue on my Redmi Note 10 Pro.
One week ago the phone got in a reboot loop without any change from my side, In some research I saw a few foruns saying that this was because an MIUI Update which bricked my phone.
I tried to enter using the cellphone in the recovery mode, however I cant, the only thing I can do is to use the fastboot.
I installed, ran adb fastboot however when I try to erase all data or install TWRP the message "Boot Command is not allowed in Lock State" or "Erase is not allowed in Lock State"
I didnt have the chance to put the phone in Debugging mode, it only bricked w/o any change from my side.
The question is: Is there a way to remove the phone from Lock State ? using software, commandas or something else ?
Click to expand...
Click to collapse
In my opinion you've to go to Xiaomi shop for repairing.
If no recovery bootup with hardware buttons power and volume+ together until vibration works and bootloader locked you can't use the important fastboot commands.....

Laptapper said:
In my opinion you've to go to Xiaomi shop for repairing.
If no recovery bootup with hardware buttons power and volume+ together until vibration works and bootloader locked you can't use the important fastboot commands.....
Click to expand...
Click to collapse
Exactly, after Power Button + Volume Up I can feel the the vibration however doesnot enter in the recovery mode, only a low battery sign shows up.
In my country we dont have official Xiaomi shop
Any other tip to unlock the recovery ?

lokopaca said:
Exactly, after Power Button + Volume Up I can feel the the vibration however doesnot enter in the recovery mode, only a low battery sign shows up.
In my country we dont have official Xiaomi shop
Any other tip to unlock the recovery ?
Click to expand...
Click to collapse
Low power!?
Then leave it on the charger over night and try again!

Laptapper said:
Low power!?
Then leave it on the charger over night and try again!
Click to expand...
Click to collapse
Yes, but it is only the sign itself.
Battery is completely full, all night loading.

The is that the Booloader is locked and I cant boot the phone.

lokopaca said:
Yes, but it is only the sign itself.
Battery is completely full, all night loading.
Click to expand...
Click to collapse
Try another charger and another cable
Because empty sign means normally empty

Where abouts are you from, if theres no service shop where did you buy it, if you bought it online then i suggest you contact Xiaomi online to discuss your options which im sure will include a postal repair service. IF this is a found or handed down phone as seems to be a trend on this thread then i think you are right out of luck my friend and need a new phone, unless you can convince the registered previous owner to contact Xiaomi to get it serviced for you and pay him.

Try this and substitute with sweet image.
https://forum.xda-developers.com/t/...-destroyed-locked-bootloader-problem.4287945/

Laptapper said:
Try another charger and another cable
Because empty sign means normally empty
Click to expand...
Click to collapse
I think he's telling the icon looks similar to empty battery. Since he hasn't seen anything like that earlier.

RAMBO29 said:
I think he's telling the icon looks similar to empty battery. Since he hasn't seen anything like that earlier.
Click to expand...
Click to collapse
Hi RAMBO29, yes, you are right.
It's only the sign, battery is full

Related

Really (I mean *really*!) bricked my phone. Nothing works.

Hi p970ies,
EDIT: NEW problems, see last pages.
here is my story:
I was on IZS v1.1, when I decided to go into recovery and make a full-wipe for having a "fresh install" again. You know, the phone was laggy, I had to many apps etc. I pressed the on/off-button for 1-2 secs to reboot into recovery, then my phone turned off and restarted but just with a "bright" black screen, the display was on. I thought "something went wrong", pulled the battery out and put it back in again, started, but then same screen again.
A few months ago an easy "unbricking" method (I know, not really unbricking) was to flash Redy2006's touch-recovery and boot into it with his scripts. So I flashed it (I know it's dumb, because of the u-boot and v30 thing, Idk), same result.
After that, I grabbed smartflash and two .bin/.fls packs of 2 roms, went into that special mode (phone off, press vol+, plug in) but there was no "sign" (screen that shows that you are in that mode) like the other day, the screen kept being black, but on.
Nonetheless the flashing worked and the software said everything alright. I started the phone but same result, in addition that there was now this effect: When the battery is put in and/or the phone is charging, the screen changes from being on and off. I can't do anything, no restarting with buttons, no LG screen, nothing but on and off, on and off. Every few seconds.
Thank you, I hope you experts can help me. (Even when I have the phone 2 years now and I was a ROM-junkie since the first day )
Edit: Tried smartflash with another patched v20 ROM. Tried KDZ Updater, just errors. But now the phone seems to boot, but there's nothing on the display, just the 4 softkeys are fading in and out.
Tomatengelee said:
Hi p970ies,
here is my story:
I was on IZS v1.1, when I decided to go into recovery and make a full-wipe for having a "fresh install" again. You know, the phone was laggy, I had to many apps etc. I pressed the on/off-button for 1-2 secs to reboot into recovery, then my phone turned off and restarted but just with a "bright" black screen, the display was on. I thought "something went wrong", pulled the battery out and put it back in again, started, but then same screen again.
A few months ago an easy "unbricking" method (I know, not really unbricking) was to flash Redy2006's touch-recovery and boot into it with his scripts. So I flashed it (I know it's dumb, because of the u-boot and v30 thing, Idk), same result.
After that, I grabbed smartflash and two .bin/.fls packs of 2 roms, went into that special mode (phone off, press vol+, plug in) but there was no "sign" (screen that shows that you are in that mode) like the other day, the screen kept being black, but on.
Nonetheless the flashing worked and the software said everything alright. I started the phone but same result, in addition that there was now this effect: When the battery is put in and/or the phone is charging, the screen changes from being on and off. I can't do anything, no restarting with buttons, no LG screen, nothing but on and off, on and off. Every few seconds.
Thank you, I hope you experts can help me. (Even when I have the phone 2 years now and I was a ROM-junkie since the first day )
Edit: Tried smartflash with another patched v20 ROM. Tried KDZ Updater, just errors. But now the phone seems to boot, but there's nothing on the display, just the 4 softkeys are fading in and out.
Click to expand...
Click to collapse
Oh man, its sad to hear that.
I can just think on two situations.
One is a broken screen, but thats pretty obvious.
And the other is a broken boot partition. Its very strange that you cant get into software upgrade mode. You sure you removed SIM, battery and SD, and then plugged it to the cable while holding the volume buttons?
I dont doubt you did it well, just making sure. Anyways AFAIK you should be able to enter that mode unless you got a broken boot partition.
Best of luck, sorry Im not of much help.
Grakel said:
Oh man, its sad to hear that.
I can just think on two situations.
One is a broken screen, but thats pretty obvious.
And the other is a broken boot partition. Its very strange that you cant get into software upgrade mode. You sure you removed SIM, battery and SD, and then plugged it to the cable while holding the volume buttons?
I dont doubt you did it well, just making sure. Anyways AFAIK you should be able to enter that mode unless you got a broken boot partition.
Best of luck, sorry Im not of much help.
Click to expand...
Click to collapse
Hi, thank you for your answer.
Yesterday oder so, I connected my phone without SIM, SD and battery while pressing vol+ to my pc and it showed the S/W-Update "Wait while update is in progress" or something. I was happy because the display isn't broken. But then I flashed again and the display is as black as before...
I thought about a broken bootloader. Do you guys know a way to fix it? Or the boot partition?
Tomatengelee said:
Hi, thank you for your answer.
Yesterday oder so, I connected my phone without SIM, SD and battery while pressing vol+ to my pc and it showed the S/W-Update "Wait while update is in progress" or something. I was happy because the display isn't broken. But then I flashed again and the display is as black as before...
I thought about a broken bootloader. Do you guys know a way to fix it? Or the boot partition?
Click to expand...
Click to collapse
Im pretty sure that if you can see the software update mode, you can unbrick the device.
When you said you reflashed something, do you actually mean that you smartflashed the fls and bin files from a stock v20 rom? AFAIK the bin file carries a bootloader with it so it should get fixed if your problem is the bootloader.
And by the way, while the phone has that black screen and is stuck booting... Are you able to use adb commands? You could try to jump to the recovery with "adb reboot recovery" to see if you got a working recovery.
Best of luck, tell me how it goes
Grakel said:
Im pretty sure that if you can see the software update mode, you can unbrick the device.
When you said you reflashed something, do you actually mean that you smartflashed the fls and bin files from a stock v20 rom? AFAIK the bin file carries a bootloader with it so it should get fixed if your problem is the bootloader.
And by the way, while the phone has that black screen and is stuck booting... Are you able to use adb commands? You could try to jump to the recovery with "adb reboot recovery" to see if you got a working recovery.
Best of luck, tell me how it goes
Click to expand...
Click to collapse
yep, I tried every version (10, 20, 30) in bin/fls and kdz. But I never got the screen to show something again.
And no, I can't use adb commands, sadly. It says "cannot find device" or something like that.
Tomatengelee said:
yep, I tried every version (10, 20, 30) in bin/fls and kdz. But I never got the screen to show something again.
And no, I can't use adb commands, sadly. It says "cannot find device" or something like that.
Click to expand...
Click to collapse
Huhmmm... Quite strange.
You can try to open up device manager, look for the phone (will probably have no drivers and the icon will have a yellow triangle) and force installing adb drivers. After that you are supposed to use adb even in middle of a boot.
I'd say that your best chance is to get to your recovery, so you can wipe everything (even formatting system) and start from scratch...
Anyways Im no expert at all... Just trying to help.
Grakel said:
Huhmmm... Quite strange.
You can try to open up device manager, look for the phone (will probably have no drivers and the icon will have a yellow triangle) and force installing adb drivers. After that you are supposed to use adb even in middle of a boot.
I'd say that your best chance is to get to your recovery, so you can wipe everything (even formatting system) and start from scratch...
Anyways Im no expert at all... Just trying to help.
Click to expand...
Click to collapse
Sometimes ADB works, but it says "device offline". When I flashed PRE-IZS fls/bin from the spanish forum, and then V30B bin/fls, something really weird happens: The phone is on, the wake-button works well - it turns on and turns off the display and the softkeys. But the screen doesn't show anything - just black.
Hello there!
Did You try out the B2C tool provided by LG? And there is one other tool provided by LG. Just try these oit. If they dont work, then try claiming it under warranty. They might replace the motherboard.
P.S: If You have the money, sell this piece of **** and get a Sony or Samsung. Cheers!
Sent from my LG-P970 using xda app-developers app
rokr05 said:
Hello there!
Did You try out the B2C tool provided by LG? And there is one other tool provided by LG. Just try these oit. If they dont work, then try claiming it under warranty. They might replace the motherboard.
P.S: If You have the money, sell this piece of **** and get a Sony or Samsung. Cheers!
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
I think I'm going to buy a Nexus 4, but I have to convince my parents
Oh and yes, phone is older than 2 years and in Germany we only have 2 years of warranty I think.
Tomatengelee said:
Sometimes ADB works, but it says "device offline". When I flashed PRE-IZS fls/bin from the spanish forum, and then V30B bin/fls, something really weird happens: The phone is on, the wake-button works well - it turns on and turns off the display and the softkeys. But the screen doesn't show anything - just black.
Click to expand...
Click to collapse
An easy, possible fix for The Device offline is to use the latest ADB. Just use the attached zip anywhere and use ADB, its the latest version from the android SDK, but just the files required for ADB. My nexus 4 had the same problem, but Solved it by updating ADB.
ykumar00 said:
An easy, possible fix for The Device offline is to use the latest ADB. Just use the attached zip anywhere and use ADB, its the latest version from the android SDK, but just the files required for ADB. My nexus 4 had the same problem, but Solved it by updating ADB.
Click to expand...
Click to collapse
damn it says "error: device not found" when in S/W or bootloop... or device offline in bootloop
any ideas?
did you try patched bins ? (for being able to boot into recovery right after the flash process, maybe you just need right wipes)
#700th post yay...
Ilko said:
did you try patched bins ? (for being able to boot into recovery right after the flash process, maybe you just need right wipes)
#700th post yay...
Click to expand...
Click to collapse
Yes, I did, but Smartflash works "less" than the KDZ-Updater. Actually the phone beeped today while it was on (with some kdz flashed) :silly:
Is it possible to convert patched bin/fls files to kdz?
I don't know, probably not... what I can say is that kdzu doesn't perform full wipes since it's intended to update the system and keep datas at the same time. You probably need wipes...
Ilko said:
I don't know, probably not... what I can say is that kdzu doesn't perform full wipes since it's intended to update the system and keep datas at the same time. You probably need wipes...
Click to expand...
Click to collapse
Oh ok... But with KDZ-Updater, it's possible to turn the phone off and on (screens is "on" but shows the color black while the softkeys are on too).
I'll try again with Smartflash... Do you know another version of it or a good tutorial? Maybe I've done the wrong method or something...
there are several tuts in this forum. smartflash is the quickest and safest way to restore / unbrick as it erases everything in the internal memory
Ilko said:
there are several tuts in this forum. smartflash is the quickest and safest way to restore / unbrick as it erases everything in the internal memory
Click to expand...
Click to collapse
I know, but it never works. That problem is so weird! :silly:
Man, nothing works... After smartflashing display flashing off and on again, after kdz display on, softkeys flashing
ADB side service is not active while in S/W mode. The only chance to access to recovery is to boot normally, and access to the device via ADB. The problems are : device needs to pass initial boot process for being able to be detected by ADB (even if you don't see the desktop it's ok), and USB debug must be enabled by default...
so, if you can't pass initial boot process, no chance to use ADB, and, if it passes, usb debug must be enabled or device will remain offline...
Ilko said:
ADB side service is not active while in S/W mode. The only chance to access to recovery is to boot normally, and access to the device via ADB. The problems are : device needs to pass initial boot process for being able to be detected by ADB (even if you don't see the desktop it's ok), and USB debug must be enabled by default...
so, if you can't pass initial boot process, no chance to use ADB, and, if it passes, usb debug must be enabled or device will remain offline...
Click to expand...
Click to collapse
Is there a chance to enable it manually?
the only chance is to flash a ROM which have it enabled by default for the most of them.
mine died because of the new twrp 2.6. It has definitively corrupted the boot partition as even smartflash can't ends its process. I had to buy another device...

Charging device when switched off reboots to TWRP

Hey
I have a problem with my device; Whenever it is switched off and I plug the charger on it always boots to TWRP but it does not work- The touch screen doesn't work and pressing the power button locks it and cant swipe meaning I have to manually reboot it.
Thanks
indy140 said:
Hey
I have a problem with my device; Whenever it is switched off and I plug the charger on it always boots to TWRP but it does not work- The touch screen doesn't work and pressing the power button locks it and cant swipe meaning I have to manually reboot it.
Thanks
Click to expand...
Click to collapse
There are a lot of other threads talking about this this problem is known, and there's no solution yet (we have to wait for official twrp support). The only solution for now is to reflash original recovery.img and get back to stock recovery
gibihr said:
There are a lot of other threads talking about this this problem is known, and there's no solution yet (we have to wait for official twrp support). The only solution for now is to reflash original recovery.img and get back to stock recovery
Click to expand...
Click to collapse
Thanks for this. To save starting a new thread do you know if there's a way to remove the red HTC boot text?
indy140 said:
Thanks for this. To save starting a new thread do you know if there's a way to remove the red HTC boot text?
Click to expand...
Click to collapse
that shows only when you booting into recovery. the only way is to flash stock recovery
Oh, well, it's good to know I'm not the only one with this issue.
However, why should I flash stock recovery? I mean, there are no further issues, the phone still charges while in this state, and I can reboot it with my PC. There is one thing I'm worried about;
What if I turn off USB debugging? If I would end up in the "stuck recovery" after I have done so, would I be unable to get out?
And also, I think there is a possible fix.. Wouldn't it be possible to reboot the phone by just pulling out the battery and turning the phone back on? Yes I know, "battery is not removable" but I'm pretty sure it is, it always is. It's not going to be easy tho.
HTCOneX+ said:
Oh, well, it's good to know I'm not the only one with this issue.
However, why should I flash stock recovery? I mean, there are no further issues, the phone still charges while in this state, and I can reboot it with my PC. There is one thing I'm worried about;
What if I turn off USB debugging? If I would end up in the "stuck recovery" after I have done so, would I be unable to get out?
And also, I think there is a possible fix.. Wouldn't it be possible to reboot the phone by just pulling out the battery and turning the phone back on? Yes I know, "battery is not removable" but I'm pretty sure it is, it always is. It's not going to be easy tho.
Click to expand...
Click to collapse
i don't see why you have to switch off your phone. theres a lot of options in stock rom like "do not disturb", "airplane mode" etc so you don't have to switch off.
It seems this problem happens when you reboot your phone while charging ( i never had problems) try to avoid that.
ps - i never switch off my phone and only reboot it if needed or maybe once a month. But thats me.
kativiti said:
i don't see why you have to switch off your phone. theres a lot of options in stock rom like "do not disturb", "airplane mode" etc so you don't have to switch off.
It seems this problem happens when you reboot your phone while charging ( i never had problems) try to avoid that.
ps - i never switch off my phone and only reboot it if needed or maybe once a month. But thats me.
Click to expand...
Click to collapse
I never turn my phone off, but sometimes I can't charge my phone in time and the battery runs dry. See? I can't reboot at 0%, so I have to charge it a little. Now you could tell me that it still isn't a problem, since the phone still charges in recovery and I can use commands to reboot system.. sure, but I'm working on a way to prevent anyone from entering recovery or using adb-debugging or hard resetting my phone (from a distance, if phone is stolen). This would turn off adb-debugging, causing the phone to be stuck in recovery for ever, if it were to charge in off mode. I guess I'm the only one having a problem with the bug
---------- Post added at 06:09 PM ---------- Previous post was at 06:04 PM ----------
oh, and are you saying that you never had this problem, as in, you tried charging it in off-mode and it worked just fine?
[/COLOR]oh, and are you saying that you never had this problem, as in, you tried charging it in off-mode and it worked just fine?[/QUOTE]
Hi: guess im one of the lucky ones who never had to deal with this.
You can remote reset your phone using Google device manager. You can ring, lock or erase phone and check last location.
https://www.google.com/android/devicemanager
kativiti said:
[/COLOR]oh, and are you saying that you never had this problem, as in, you tried charging it in off-mode and it worked just fine?
Click to expand...
Click to collapse
Hi: guess im one of the lucky ones who never had to deal with this.
You can remote reset your phone using Google device manager. You can ring, lock or erase phone and check last location.
https://www.google.com/android/devicemanager[/QUOTE]
I'm using avast since there are more options for rooted devices I'm well aware of the google device manager, but thank you anyway!
I'm using the Honor 7 with TWRP 3.0.2.0by paulobrien and Unofficial CM13 by papsi177 and having the same issue.
When charging while the device is turned off, it automatically boots into twrp. Does anyone have a solution? Are there other recoveries (except the stock recovery) which doesn't have this problem? Is it somehow possible to modify e.g. a file to have a nice charging animation instead?
It isn't that big issue, but it would be nice to solve this anyway...
tomtomk99 said:
I'm using the Honor 7 with TWRP 3.0.2.0by paulobrien and Unofficial CM13 by papsi177 and having the same issue.
When charging while the device is turned off, it automatically boots into twrp. Does anyone have a solution? Are there other recoveries (except the stock recovery) which doesn't have this problem? Is it somehow possible to modify e.g. a file to have a nice charging animation instead?
It isn't that big issue, but it would be nice to solve this anyway...
Click to expand...
Click to collapse
I found that users phones and recovery gets different reactions.
When i tried cm12 i had that same "issue" but with cm13 i had the battery animation. Same thing with getting phone freeze when battery run out.
The best chance is to try different recovery versions and hope for the best.
That said, i only switch off phone when battery died on me.
im currently still with TWRP 2.7.1.0-20140802
.
kativiti said:
That said, i only switch off phone when battery died on me.
Click to expand...
Click to collapse
I do so, too.. but I love details ?
kativiti said:
im currently still with TWRP 2.7.1.0-20140802
Click to expand...
Click to collapse
I'll try to downgrade and see if my charging animation gets back ?
Try the new TWRP 3.0.2-0 from nightcore500. The freeze in charging only mode is fixed on his recovery

My Note 8 Had a Bootloop then never turned on / charged [PLEASE HELP]

Hi Guys this is my first time posting here and hoping to find a solution to what I'm experiencing right now.
This is actually the second time and what happened is that my phone got into a BOOTLOOP so of course, Ideally the first thing I did was to forced it to shutdown using the Volume down + Power button combination and so I did, the phone turned off, But after that, When I tried to turned it on again, it won't turn itself on. I even tried to hold various button combinations but to no avail, nothing worked. Aside from that, I have tried to plug in the charger periodically after 20 - 30 seconds with the same interval before plugging it out and repeated the cycle for 20 tries but same result, it didn't worked as well..
So I'm here hoping that someone will be able to help me out as I don't know what to do anymore and I badly need to use my phone for my studies as well.. :crying::crying:
Hello @johnmark21t, I will do my best to help you to figure out what's going wrong with your Note8
Have you tried to boot into download mode (volume down + Bixby + power button) ? Does it work or not ?
If you can't boot your device into Recovery Mode then the motherboard is fried. You are better off getting a new device rather than replacing the motherboard
Alek7 said:
Hello @johnmark21t, I will do my best to help you to figure out what's going wrong with your Note8
Have you tried to boot into download mode (volume down + Bixby + power button) ? Does it work or not ?
Click to expand...
Click to collapse
Yes I do have tried it but nothing happened or no response at all..
iceepyon said:
If you can't boot your device into Recovery Mode then the motherboard is fried. You are better off getting a new device rather than replacing the motherboard
Click to expand...
Click to collapse
That's what I'm also thinking about but I cannot comprehend as to why it became like this as my phone was just on standby mode and then just turned off by itself and by the time that it restarted, it was stucked on the Samsung logo in which after I saw that it was like that, I have forced restarted it so I think that's my last conclusion but I don't think that that is the case for me...
What rom and what kernel you have what modes?. What twrp you have? You have flash wrong rom? Wrong kernel? Is impossible for the phone to turn in boot loop mode itself. You did something wrong before the bootloop. Try volume up and Bixby and power button for 30 secs. Or volume down and Bixby and power button for 30 secs. Motherboard failure no give you boot loop. Give you blue screen. Try to flah with Odin is the easy way.
y0000 said:
What rom and what kernel you have what modes?. What twrp you have? You have flash wrong rom? Wrong kernel? Is impossible for the phone to turn in boot loop mode itself. You did something wrong before the bootloop. Try volume up and Bixby and power button for 30 secs. Or volume down and Bixby and power button for 30 secs. Motherboard failure no give you boot loop. Give you blue screen. Try to flah with Odin is the easy way.
Click to expand...
Click to collapse
Unfortunately I'm only at stock, not even rooted and I don't have custom recovery mode installed.. all in stock. Even the Odin mode is inaccessible as well.. and again I didn't do anything prior before this happened..
Try connecting your device to a computer with Smartswitch installed and run the emergency recovery process. If that doesn't work then I would recommend that you take your device to a Samsung Service Center and let them take a look at it.
However you should be able to repair your issues using Smartswitch.
iceepyon said:
Try connecting your device to a computer with Smartswitch installed and run the emergency recovery process. If that doesn't work then I would recommend that you take your device to a Samsung Service Center and let them take a look at it.
However you should be able to repair your issues using Smartswitch.
Click to expand...
Click to collapse
Can you please further tell me how can I do this? Thank you alot!
johnmark21t said:
Can you please further tell me how can I do this? Thank you alot!
Click to expand...
Click to collapse
Download and install Smartswitch onto your computer. Then connect your device to your computer and launch Smartswitch. If your device is detected by Smartswitch then launch the Emergency Recovery Process.
I'd like to dig this topic out.
I'm also experiencing bootloop after latest OTA update. I've taken device to Samsung Service and they told me that it's faulty motherboard and they want to charge me 1300pln which is about 335$ so I'm like - Hell no, it's not worth it.
Anyway, I'm kind of sceptical about whole fried motherboard story, since recovery mode is working correctly, download mode is showing up as well. I tried to flash same firmware as it has now. It passed but result is the same.
Gonna download some older SW version and try again but maybe any other suggestions from you guys?
UPDATE: Older SW version downloaded and result is still the same. So yeah, screw it
Acuap said:
I'd like to dig this topic out.
I'm also experiencing bootloop after latest OTA update. I've taken device to Samsung Service and they told me that it's faulty motherboard and they want to charge me 1300pln which is about 335$ so I'm like - Hell no, it's not worth it.
Anyway, I'm kind of sceptical about whole fried motherboard story, since recovery mode is working correctly, download mode is showing up as well. I tried to flash same firmware as it has now. It passed but result is the same.
Gonna download some older SW version and try again but maybe any other suggestions from you guys?
Click to expand...
Click to collapse
Try flashing firmware that's at least one update above the version you have on the phone and after you flash it in Odin and it finishes with a "PASS" then go into recovery mode and do a factory reset in fact try doing a factory reset right now just to see if it'll work since you have nothing to lose at this point.
johnmark21t said:
Can you please further tell me how can I do this? Thank you alot!
Click to expand...
Click to collapse
Have you got the Samsung drivers installed on your computer?
https://developer.samsung.com/mobile/android-usb-driver.html
I had a similar issue with my note 8. Just today . My phone carrier sent me an update (from USA T-Mobile ) to install. I had my phone connected to power .. and Phone just died during the update . I wonder if motherboard got fried ...
Same issue
Acuap said:
UPDATE: Older SW version downloaded and result is still the same. So yeah, screw it
Click to expand...
Click to collapse
Any update on your phone?
I hope there's a class-action lawsuit about this. My Note8 had the same problem. An OTA update was done, and the phone shut off, never to turn on again. No combination of buttons powered the phone on at all.

Question Bricked after trying to root (Magisk)

Hello everyone, everything good ? I would like to know if you could help me I bought a OnePlus ACE 5G (PGKM10) I followed a tutorial here on the forum on how to root using Magisk and patching boot.img, I tried a few times and the device was in bootloop with the OnePlus logo and when I started the system crashed and restarted.
But after trying to patch again, I saw that when it started, the image was horrible as if it had a video problem there, it crashed and restarted again.
I tried to fix the error by doing another patch procedure and now the cell phone does not turn on anymore nor does the image appear, if you hold the power button and try to turn it on it just vibrates, the same happens if you try to enter fastboot windows beeps that it has detected a device and soon after it disconnects.
Could anyone shed some light on how to get it working again?
darklegends2008 said:
Hello everyone, everything good ? I would like to know if you could help me I bought a OnePlus ACE 5G (PGKM10) I followed a tutorial here on the forum on how to root using Magisk and patching boot.img, I tried a few times and the device was in bootloop with the OnePlus logo and when I started the system crashed and restarted.
But after trying to patch again, I saw that when it started, the image was horrible as if it had a video problem there, it crashed and restarted again.
I tried to fix the error by doing another patch procedure and now the cell phone does not turn on anymore nor does the image appear, if you hold the power button and try to turn it on it just vibrates, the same happens if you try to enter fastboot windows beeps that it has detected a device and soon after it disconnects.
Could anyone shed some light on how to get it working again?
Click to expand...
Click to collapse
Try EDL method bro
Junel Ortiz 🇵🇭 said:
Try EDL method bro
Click to expand...
Click to collapse
I tried to boot pressing volume up and down but nothing happens on windows, i will give a search in how to put my device in EDL mode again.
Thanks bro
darklegends2008 said:
I tried to boot pressing volume up and down but nothing happens on windows, i will give a search in how to put my device in EDL mode again.
Thanks bro
Click to expand...
Click to collapse
Welcome bro. I think that's the final to survive your device. Hope always good bro. Good luck ..
Junel Ortiz 🇵🇭 said:
Welcome bro. I think that's the final to survive your device. Hope always good bro. Good luck ..
Click to expand...
Click to collapse
Hi!
How are you ?
I tried to enter EDL mode but without success, I think it's with HardBrick, making the button combinations the only thing that happens is vibrating, although windows recognize a new device after a few seconds it disconnects.
I have no way to send it to OnePlus.
Is there anything else I can do to resolve this?
darklegends2008 said:
Hello everyone, everything good ? I would like to know if you could help me I bought a OnePlus ACE 5G (PGKM10) I followed a tutorial here on the forum on how to root using Magisk and patching boot.img, I tried a few times and the device was in bootloop with the OnePlus logo and when I started the system crashed and restarted.
But after trying to patch again, I saw that when it started, the image was horrible as if it had a video problem there, it crashed and restarted again.
I tried to fix the error by doing another patch procedure and now the cell phone does not turn on anymore nor does the image appear, if you hold the power button and try to turn it on it just vibrates, the same happens if you try to enter fastboot windows beeps that it has detected a device and soon after it disconnects.
Could anyone shed some light on how to get it working
Click to expand...
Click to collapse
Is your issue resolved?
yashaswee1708 said:
Is your issue resolved?
Click to expand...
Click to collapse
Not, still trying to fix the issue.
darklegends2008 said:
Not, still trying to fix the issue.
Click to expand...
Click to collapse
Did you used your current ColorOS version's boot img? Or from where you got the boot.img?
Received help from an engineer from India.
+91 70174 26154 WhatsApp
Symptoms are cyclic loading, goes into Recovery and is displayed in computer devices in BROM mode for a couple of seconds.
Called in and got it done in 10 minutes.
mrkorus said:
Received help from an engineer from India.
+91 70174 26154 WhatsApp
Symptoms are cyclic loading, goes into Recovery and is displayed in computer devices in BROM mode for a couple of seconds.
Called in and got it done in 10 minutes.
Click to expand...
Click to collapse
Which tool did you used to unbrick? or did you got your device fixed remotely?
yashaswee1708 said:
Did you used your current ColorOS version's boot img? Or from where you got the boot.img?
Click to expand...
Click to collapse
Both but none worked
mrkorus said:
Received help from an engineer from India.
+91 70174 26154 WhatsApp
Symptoms are cyclic loading, goes into Recovery and is displayed in computer devices in BROM mode for a couple of seconds.
Called in and got it done in 10 minutes.
Click to expand...
Click to collapse
Sounds exact like my device, how is done the fix ?
darklegends2008 said:
Sounds exact like my device, how is done the fix ?
Click to expand...
Click to collapse
I think you'll have to contact the mentioned person, he'll give you the software. He'll login remotely and flash the firmware. He'll charge you for it.
mrkorus said:
Received help from an engineer from India.
+91 70174 26154 WhatsApp
Symptoms are cyclic loading, goes into Recovery and is displayed in computer devices in BROM mode for a couple of seconds.
Called in and got it done in 10 minutes.
Click to expand...
Click to collapse
@xCadbury Try this maybe.
yashaswee1708 said:
I think you'll have to contact the mentioned person, he'll give you the software. He'll login remotely and flash the firmware. He'll charge you for it.
Click to expand...
Click to collapse
All right. Connected remotely through the UltraViewer program. He checked that the phone is at least somehow determined, then asked to pay for the service. I downloaded everything from my own google drive links. Installed, opened the program under your username and password and set everything up. Waited for the unlock key from the server. Sometimes the key did not come and he sent requests again. As the key came, the ColorOS firmware was immediately installed

Question Help please! OnePlus 10r / ace hard bricked

I tried flashing from coloros to oxygenOS...
I failed and i got it on bootloop with orange alert
But now it's in hard brick...
Can someone help me please?
xCadbury said:
I tried flashing from coloros to oxygenOS...
I failed and i got it on bootloop with orange alert
But now it's in hard brick...
Can someone help me please?
Click to expand...
Click to collapse
Can you turn on your device? Or just black screen? Did you try to get your device into fastboot mode or recovery mode? Can you please tell us more about the situation you are facing with your device?
No, i cant power it on...
Before in fastboot enhance it loaded only 3/4 of the bar then stuck... Always the same...
Then it bootlooped with orange state bootloop
Now it's just dead... As in hard bricked... Didn't check if it's still recognizable by my pc
xCadbury said:
No, i cant power it on...
Before in fastboot enhance it loaded only 3/4 of the bar then stuck... Always the same...
Then it bootlooped with orange state bootloop
Now it's just dead... As in hard bricked... Didn't check if it's still recognizable by my pc
Click to expand...
Click to collapse
Well, plug your phone to charger and leave it for couple of hours. Later you can try to put in into recovery mode or fastboot mode.
I mean there's no dispay anymore...
xCadbury said:
I mean there's no dispay anymore...
Click to expand...
Click to collapse
There are some chances to turn some devices ON by charging, which are with dead batteries due to boot looping.
If the display is broken, time to go to a service centre.
Goddamn_srilankan said:
There are some chances to turn some devices ON by charging, which are with dead batteries due to boot looping.
If the display is broken, time to go to a service centre.
Click to expand...
Click to collapse
No, the dispay still is good but because it's hard bricked it doesn't display anything
xCadbury said:
No, the dispay still is good but because it's hard bricked it doesn't display anything
Click to expand...
Click to collapse
If you didn't resize, delete or replace partitions of your device, that brick can't be that bad at all. The problem what i see is your battery is dead. That's why i told you to charge it for couple of hours even the display isn't working. In my experiences, i've seen such devices which doesn't show the charging screen but charging silently.
Goddamn_srilankan said:
If you didn't resize, delete or replace partitions of your device, that's brick can't be that bad at all. The problem what i see is your battery is dead. That's why i told you to charge it for couple of hours even the display isn't working. In my experiences, i've seen such devices which doesn't show the charging screen but charging silently.
Click to expand...
Click to collapse
It's charging... Phone gets warm and sometimes vibrates, but no display...
About partition i didn't go to that part...
xCadbury said:
No, the dispay still is good but because it's hard bricked it doesn't display anything
Click to expand...
Click to collapse
What is the last recovery you had in that phone? Did you wipe the recovery partition using it?
I didn't wipe anything thru pc
Some says my last resort is replacing motherboard... The thing is, i can't seem to find one
Some says my last resort is replacing motherboard... The thing is, i can't seem to find one
xCadbury said:
I didn't wipe anything thru pc
Click to expand...
Click to collapse
If that last recovery was a TWRP, ofcourse you can bring your phone back to life. I'll be helping you to get your phone work. Plug the device into a specific charger and leave it to charge for two hours.
xCadbury said:
Some says my last resort is replacing motherboard... The thing is, i can't seem to find one
Click to expand...
Click to collapse
Was the bootloader unlocked? Which recovery image did you use to flash those roms?
Goddamn_srilankan said:
Was the bootloader unlocked? Which recovery image did you use to flash those roms?
Click to expand...
Click to collapse
Bl unlock, i think so...
Recovery image, the stock one... I don't use twrp
xCadbury said:
Bl unlock, i think so...
Recovery image, the stock one... I don't use twrp
Click to expand...
Click to collapse
How did you flash those ROMs? What tool you use to flash ROMs?
Fastboot enhance
xCadbury said:
Fastboot enhance
Click to expand...
Click to collapse
To flash firmware with that tool, you have to put your device in bootloader mode right?
Yep in fastboot... Im in the mid of getting it to fastbootd, then it stops at 3/4 progression

Categories

Resources