Related
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
What exactly were you trying to do? I mean normally you hook up old phone and use smart switch to update new phone. So why was you connected to a PC? It does sound like you bricked it.
So now you probably need to flash the ROM.
I read that smart switch is a good and valid source to check for updates. I never thought that an official Samsung software can be so bad at something so basic, resulting in bricking my phone...
Stop using smart switch to update your phone. You haven't hard bricked it because you still have recovery. It's called a soft brick. Download Odin 13.3_3B from here on xda. Do not use the 13.4 because it's suspected to have a fishy call back to a server from a dll that's in the program folder. Download the atch firmware for your model from sammobile or get it in this s20 ultra forum. You should be able to flash the new firmware.
Thanks @freebee269. Does flashing the firmware with Odin void my warranty or does this only count for rooting devices? (Sorry for stupid questions)
Julius_GER said:
Thanks @freebee269. Does flashing the firmware with Odin void my warranty or does this only count for rooting devices? (Sorry for stupid questions)
Click to expand...
Click to collapse
Odin uses official firmware from Samsung so no warranty voided.
Julius_GER said:
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
Click to expand...
Click to collapse
What kind of USB Port did you use?
Try again using a USB 2.0 port, Samsung always had problems with it's software and USB 3.0 ports.
Use USB 2.0 and try again.
Hi guys, i have a similar problem as (xReem).
Attached my GT SM-T515/10.1 tab to smart switch where the software was unable to recognise my device!? Was advised to use the Emergency Code function but i have no code due to backing up my data to sd card! I have Magisk and TWRP installed where my device was working beforehand, but since attaching to smart switch, my device is now totally "dysfunctional"!!!
Error message as follows...
...An error as occurred while updating the software. Use the Emergency Recovery function in the Smart Switch PC software. ...
Like i sad, i have no code!!!
I am able to get to the device unlock choice screen and if i choose to restart, my device always boots to the Smart Switch Emergency Code screen?! If i choose the device unlock or download screens, both screens are accessible! Tried to flash my original firmware (BTU-T515XXU3ASK5-20191224095700) using Odin3_v3.14.1 and twrp-3.3.1-6-T515XXU3ASK5-20200215 with no joy (Fail!)
Although i'm totally @"#$%* off about this, as its a new device, i am also curious if someone has ever cracked this... 'Smart Switch No Code' problem before. Hmm...
Anyways, any help appriciated...
Oh! Cannot access recovery at all...
Any help appriciated.
klantee said:
Hi guys, i have a similar problem as (xReem).
Attached my GT SM-T515/10.1 tab to smart switch where the software was unable to recognise my device!? Was advised to use the Emergency Code function but i have no code due to backing up my data to sd card! I have Magisk and TWRP installed where my device was working beforehand, but since attaching to smart switch, my device is now totally "dysfunctional"!!!
Error message as follows...
...An error as occurred while updating the software. Use the Emergency Recovery function in the Smart Switch PC software. ...
Like i sad, i have no code!!!
I am able to get to the device unlock choice screen and if i choose to restart, my device always boots to the Smart Switch Emergency Code screen?! If i choose the device unlock or download screens, both screens are accessible! Tried to flash my original firmware (BTU-T515XXU3ASK5-20191224095700) using Odin3_v3.14.1 and twrp-3.3.1-6-T515XXU3ASK5-20200215 with no joy (Fail!)
Although i'm totally @"#$%* off about this, as its a new device, i am also curious if someone has ever cracked this... 'Smart Switch No Code' problem before. Hmm...
Anyways, any help appriciated...
Oh! Cannot access recovery at all...
Any help appriciated.
Click to expand...
Click to collapse
Did you ever get things working ? If not, when you flashed with Odin - did you use the PATCHED Version ? THis is necessary when flashing firmware via Odin on the S20 Ultra.....
You can download Odin 3.14.1_3b here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Be sure to download the PATCHED version of 3.14.1_3b (it is located as an attached file at the bottom of the first post in the OP at the link above. Hope this helps.
Geekser said:
Did you ever get things working ? If not, when you flashed with Odin - did you use the PATCHED Version ? THis is necessary when flashing firmware via Odin on the S20 Ultra.....
You can download Odin 3.14.1_3b here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Be sure to download the PATCHED version of 3.14.1_3b (it is located as an attached file at the bottom of the first post in the OP at the link above. Hope this helps.
Click to expand...
Click to collapse
No, to answer your first question, and yes used the patched version of Odin you state but with no joy.
(would another version of Odin be better for my device model?)
I just need to find a way to flash the original stock recovery. Having the TWRP installed as mentioned earlier is blocking my path, and I have now tripped knox! So no more options available to access the unlock oem screen. Now frp is off, oem is on!
Also, I was wondering if anyone had thought about a totally updated version of the old "ALL IN ONE TOOL" which was available for some earlier makes of phone devices? I think due to manufacturers security upgrades of today's phones we could all do with something like this?
I heard you can do a NAND/Reset wipe via the Odin options screen which would allow you to install a new rom???
Oh, my predicament was based on Julius's post, not xReem. Sorry for the confusion.
klantee said:
No, to answer your first question, and yes used the patched version of Odin you state but with no joy.
(would another version of Odin be better for my device model?)
I just need to find a way to flash the original stock recovery. Having the TWRP installed as mentioned earlier is blocking my path, and I have now tripped knox! So no more options available to access the unlock oem screen. Now frp is off, oem is on!
Also, I was wondering if anyone had thought about a totally updated version of the old "ALL IN ONE TOOL" which was available for some earlier makes of phone devices? I think due to manufacturers security upgrades of today's phones we could all do with something like this?
I heard you can do a NAND/Reset wipe via the Odin options screen which would allow you to install a new rom???
Oh, my predicament was based on Julius's post, not xReem. Sorry for the confusion.
Click to expand...
Click to collapse
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Geekser said:
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Click to expand...
Click to collapse
Thanks for the advice. I'll try what you suggest and see what happens. Stay well!
Julius_GER said:
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
Click to expand...
Click to collapse
Hey Julius, did you get your phone to work. I am having the same issue.
Update:
I am good now. I was using the thunderbolt cable that came with the phone and update would get stuck at the same point everything with odin 3.13 and 3.14.
I used a USB 3 to thunderbolt cable that I had from an older phone and it work.
What I used:
Windows 10 x64 1909
USB 3 to thunderbolt cable
USB driver downloaded from Samsung support. I think it is the same driver that comes with smart switch because when I installed it, it prompted
to reinstall driver.
Odin3 v3.13.3_3B_PatcheD from here https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572. ( I think 3.14 will work too.
I really think the cable was the only problem)
Firmware downloaded with SamFirm
klantee said:
Thanks for the advice. I'll try what you suggest and see what happens. Stay well!
Click to expand...
Click to collapse
Open Odin as administrator and if using a stock AP file always use the HOME-CSC of the same firmware in CSC slot. Sometimes Odin plays the fool and gets stuck.
ASHLEY117 said:
Open Odin as administrator and if using a stock AP file always use the HOME-CSC of the same firmware in CSC slot. Sometimes Odin plays the fool and gets stuck.
Click to expand...
Click to collapse
Wow! This nearly worked!!!
Managed to get a (((PASS))) on Odin and my tab actually rebooted into the Samsung logo!!!
Soon after this though tab immediately Boots back into download mode??? Tried the same steps but without any progress???
I feel I'm close to cracking this but need some more advice on how to build on such "progress"!?
Many thanks for your advice...
klantee said:
Wow! This nearly worked!!!
Managed to get a (((PASS))) on Odin and my tab actually rebooted into the Samsung logo!!!
Soon after this though tab immediately Boots back into download mode??? Tried the same steps but without any progress???
I feel I'm close to cracking this but need some more advice on how to build on such "progress"!?
Many thanks for your advice...
Click to expand...
Click to collapse
Try with all slots filled but with CSC file not HOME-CSC. That may help as it flashes pit file to factory reset
ASHLEY117 said:
Try with all slots filled but with CSC file not HOME-CSC. That may help as it flashes pit file to factory reset
Click to expand...
Click to collapse
Tried your suggestion with no joy. Will keep trying though as I feel this issue can be cracked. Many thanks...
Geekser said:
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Click to expand...
Click to collapse
(((SUCCESS)))!!! :laugh::laugh::laugh:
Done what you suggested by waiting until my battery ran out!
I downloaded a different software version and as soon as I plugged my tab into my PC with USB, i flashed the new software with no problems!!!
Flashed TWRP, Magisk and Multidisabler problemless the same!
The lesson learnt here...
...(ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING)...
...is to probably only have 30% battery when flashing!!! This way you won't have to wait weeks for such a large capacity battery to run down, like I did!
I knew I'd crack it!
klantee said:
(((SUCCESS)))!!! :laugh::laugh::laugh:
Done what you suggested by waiting until my battery ran out!
I downloaded a different software version and as soon as I plugged my tab into my PC with USB, i flashed the new software with no problems!!!
Flashed TWRP, Magisk and Multidisabler problemless the same!
The lesson learnt here...
...(ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING)...
...is to probably only have 30% battery when flashing!!! This way you won't have to wait weeks for such a large capacity battery to run down, like I did!
I knew I'd crack it!
Click to expand...
Click to collapse
Glad I could hel;p- I know how frustrating it is when things seem like you can never get things to work - anyway - best of luck - and be sure to hit thanks If I helped you.
Hi Do you lose your data (vids and pics) via this method? i have had same thing happen on my s20+
Please share your stories or your thoughts what stupid thing you did to make your RN8 Pro Bricked (If not: tell how the first time you bricked your device :crying: )
My side story: I tried to flash Android 9 with Android 10 unofficial recovery & in result Bricked/Dead & device with no response at all, just light blinks & that's it. :crying::crying::crying:
Also Please share your story & also update your answer how you guys fixed it.
Also I will update my Story How I fixed my Hard Brick RN8 Pro Device in this Dark Time :'(
I Hope this thread will make some of you laugh by hearing someone's funny story,
or you will able to understand someone else feelings or you will able to feel better by hearing your experience or hearing someone's else story like yours in this Hard Brick World.
Hope this thread will make good people or devs to come here & start helping each other. hope soon we will get a new way to fix our device without having mi authorized account.
simply poor move
Xiaomi did the worst thing, I could imaging. I proudly recommended Xiaomi over Huawei, because the bootloader is unlockable.
I also own a Mi 9T, which easily modable.
The simple thing like flashing TWRP and a boot.img fried my Redmi Note 8 Pro after 7 days of ownership.
I opened the device (falsely first from the front removing the display, then gettin the guts that it must be done from the back. Cracked the back glass, ordered a new glass for 3 bucks). Pulling the battery and ack that this will not solve the EDL Mode issue.
The device was now a warrantly less mess, no service center in the world would take on.
I replaced the back and reglued the screen and payed a russian savior to bypass the Xiaomi Authorized Challenge ( a russian GSM forum, I don’t know if posting a link is allowed, so I won’t). It was 20$, far cheaper than a new Mainboard.
Device is now reborn, bootloader still unlocked, but I won‘t ever try to root this piece again.
Hardlocking a flash tool, which is commonly used for cheap 80$ MTK phones is strange. I understand that Xiaomi Shop Rom issue a while ago, but a flash only allowed by China and Russia seams not really better than the Huawei way...
The phone is now used as a Escooter Dashboard/Tachometer, because I don‘t value it any more.
Ceynt said:
Xiaomi did the worst thing, I could imaging. I proudly recommended Xiaomi over Huawei, because the bootloader is unlockable.
I also own a Mi 9T, which easily modable.
The simple thing like flashing TWRP and a boot.img fried my Redmi Note 8 Pro after 7 days of ownership.
I opened the device (falsely first from the front removing the display, then gettin the guts that it must be done from the back. Cracked the back glass, ordered a new glass for 3 bucks). Pulling the battery and ack that this will not solve the EDL Mode issue.
The device was now a warrantly less mess, no service center in the world would take on.
I replaced the back and reglued the screen and payed a russian savior to bypass the Xiaomi Authorized Challenge ( a russian GSM forum, I don’t know if posting a link is allowed, so I won’t). It was 20$, far cheaper than a new Mainboard.
Device is now reborn, bootloader still unlocked, but I won‘t ever try to root this piece again.
Hardlocking a flash tool, which is commonly used for cheap 80$ MTK phones is strange. I understand that Xiaomi Shop Rom issue a while ago, but a flash only allowed by China and Russia seams not really better than the Huawei way...
The phone is now used as a Escooter Dashboard/Tachometer, because I don‘t value it any more.
Click to expand...
Click to collapse
hmm in a same situation, decided to never gonna root this device again
just don't want to take any risk now, will try to use it normally.
glad i didn't opened the back panel, i don't wanted to take a risk
also my device was in warranty so i decided to send it to Xiaomi Service Care Center.
also there was a Gyro Problem in my device. hopefully they will return in a week,
& they also took my Gmail account/password for some reason.
I have a story fot my RN8P goes yo HARDBRICK, the first
I want to reflash the stock rom ( android 9 ) using LR TWRP, and reboot device is normal, no brick or bootloop, and next week I want to reflash again, because my Lucky Patcher can't instal app.
And I think if I reflash my stock Rom, my TWRP is lost, and I think flash stock is done, I flash TWRP .img using TWRP, but I wrong because I choose flash for "boot" not "recovery",
And I think the first reboot to TWRP for fix it, and my RN8P goes to HARDBRICK, from Mei until now -_-
cyberz2 said:
I have a story fot my RN8P goes yo HARDBRICK, the first
I want to reflash the stock rom ( android 9 ) using LR TWRP, and reboot device is normal, no brick or bootloop, and next week I want to reflash again, because my Lucky Patcher can't instal app.
And I think if I reflash my stock Rom, my TWRP is lost, and I think flash stock is done, I flash TWRP .img using TWRP, but I wrong because I choose flash for "boot" not "recovery",
And I think the first reboot to TWRP for fix it, and my RN8P goes to HARDBRICK, from Mei until now -_-
Click to expand...
Click to collapse
Hmmm i received my device from customer care center after 17 days but without charges that's good for me
Nouman112 said:
Hmmm i received my device from customer care center after 17 days but without charges that's good for me
Click to expand...
Click to collapse
How thet figure it?
Nouman112 said:
Please share your stories or your thoughts what stupid thing you did to make your RN8 Pro Bricked (If not: tell how the first time you bricked your device :crying: )
My side story: I tried to flash Android 9 with Android 10 unofficial recovery & in result Bricked/Dead & device with no response at all, just light blinks & that's it. :crying::crying::crying:
Also Please share your story & also update your answer how you guys fixed it.
Also I will update my Story How I fixed my Hard Brick RN8 Pro Device in this Dark Time :'(
I Hope this thread will make some of you laugh by hearing someone's funny story,
or you will able to understand someone else feelings or you will able to feel better by hearing your experience or hearing someone's else story like yours in this Hard Brick World.
Hope this thread will make good people or devs to come here & start helping each other. hope soon we will get a new way to fix our device without having mi authorized account.
Click to expand...
Click to collapse
My story isn't too funny because this is the only time I got hard bricked and fortunately had anti brick flashed.
I was just tinkering around with logo.bin, the bootlogo of device, I found a MTK boot logo editor tool on XDA, succesfully edited and gave to my tester to test, turns out it didn't work, usual bootlogo showed up but didn't go past it, turns out the flashing location of logo.bin in auto generated flashable zip was wrong, I edited it to correct one and took the courageous step to flash it on my device, my bad luck, I would't exactly say it got hard bricked because I could access vol down menu in CFW 1, but still clicking on recovery or fastboot made it reboot with backlight on, my heartbeat went rapidly up LOL, but by god's grace I easily flashed the device with SP flash tool
samuuurai said:
My story isn't too funny because this is the only time I got hard bricked and fortunately had anti brick flashed.
I was just tinkering around with logo.bin, the bootlogo of device, I found a MTK boot logo editor tool on XDA, succesfully edited and gave to my tester to test, turns out it didn't work, usual bootlogo showed up but didn't go past it, turns out the flashing location of logo.bin in auto generated flashable zip was wrong, I edited it to correct one and took the courageous step to flash it on my device, my bad luck, I would't exactly say it got hard bricked because I could access vol down menu in CFW 1, but still clicking on recovery or fastboot made it reboot with backlight on, my heartbeat went rapidly up LOL, but by god's grace I easily flashed the device with SP flash tool
Click to expand...
Click to collapse
And how did you do it, because i've tried many tutorials and none of them works... I think i'll just buy a new board.. Because its impossible to do anything, Tried sp flash with error 0xC0060005 that says i need authentication (that mi authorized account)
Any help is appreciated.
Hello,
In the rush of flashing the january update I've flashed by mistake the Pixel 5 image bootloader (my wife's phone)
Yest that's stupid, I've done this every months for years with several Pixel phones, but I was listening to music at the same time and did dl the wrong image...
Anyway my phone is now hard bricked but I'm sure there must be a way to enter the other bootlader slot and/or entering a special recovery tool.
I cannot enter bootloader anymore
Requesting some help as I'd avoid to send it for a reflash...
Thanks !
Try: https://pixelrepair.withgoogle.com/carrier_selection
(I've never personally used this)
foobar66 said:
Try: https://pixelrepair.withgoogle.com/carrier_selection
(I've never personally used this)
Click to expand...
Click to collapse
Unfortunately the phone is supposed to have a working bootloader
Thibale said:
Unfortunately the phone is supposed to have a working bootloader
Click to expand...
Click to collapse
Ouch ...
Thibale said:
Unfortunately the phone is supposed to have a working bootloader
Click to expand...
Click to collapse
Android Flash Tool
flash.android.com
Also doesn't work?
Morgrain said:
Android Flash Tool
flash.android.com
Also doesn't work?
Click to expand...
Click to collapse
Nope...
Thibale said:
Nope...
Click to expand...
Click to collapse
Can you still access Fastboot Mode?
(pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back)
Morgrain said:
Can you still access Fastboot Mode?
(pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back)
Click to expand...
Click to collapse
No that's the problem.
But there are 2 bootloader slots (a and b) and I'm pretty sure there is way to switch from one to another with a special tool or button sequence.
I've already tried many button combinaison with no luck.
This kind of error is so stupid that I hope there is a way to force a rescue bootloader or something on boot.
yes but you need to be able to communicate with your phone from your pc.....if you cant access fastboot then how will you change partition?
Thibale said:
No that's the problem.
But there are 2 bootloader slots (a and b) and I'm pretty sure there is way to switch from one to another with a special tool or button sequence.
I've already tried many button combinaison with no luck.
This kind of error is so stupid that I hope there is a way to force a rescue bootloader or something on boot.
Click to expand...
Click to collapse
The only special tools we have are either the pixel repair tool or the android flash tool. If both can't get you fastboot / firmware flashing, that's it. Hardbrick. Google Pixels don't have "special" hardbrick solving tools, like older OnePlus had. You need to contact Google.
Ok I'll get in touch with my local reseller on Monday then...
Thibale said:
Ok I'll get in touch with my local reseller on Monday then...
Click to expand...
Click to collapse
Do you remember what went wrong?
EDIT: Uh, never mind. So you accidentally used the P5 fw. Why on hell would the device accept the P5 fw at all?!
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
WOW. So even holding volume down and power until you see the fastboot screen wont work? sometimes you have to hold it for a while. I say that because when the December firmware came out I accidentally flashed the wrong region but was able to access bootloader and so was able to rescue myself. So sorry dude. That really sucks.
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
Yes worst case we'll have for repair but they could have implemented a simple device id check on their script prior flashing anything, especially for the bootloader.
Anyway, I'm alive, in a good health and it's just a phone
niko26 said:
Do you remember what went wrong?
EDIT: Uh, never mind. So you accidentally used the P5 fw. Why on hell would the device accept the P5 fw at all?!
Click to expand...
Click to collapse
You can flash gobbledygook to your phone if you're not careful. You can flash a non-Google phone's image. Flashing just flashes what you tell it to flash.
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
That sucks. I'm sure you know now, always go straight to the source for everything if possible, firmware, platform tools, drivers, BIOS / UEFI (for computer).
SDK Platform Tools
Get the Google USB Driver
Pixel 6 Pro Factory Images
You can also Google for official pixel firmware and the top search result is what the want. I know it doesn't help you now. Good luck with your phone!
Morgrain said:
After having played around with the January patch (came from December Europe A4 firmware that was pulled), it seems that the FP scanner got even faster and more reliable, even though it's not stated in the patchnotes. Maybe it's just placebo.
Click to expand...
Click to collapse
So many folks have reported the exact same thing, I'm really, really curious just how much faster it will seem when I get around to updating.
roirraW edor ehT said:
So many folks have reported the exact same thing, I'm really, really curious just how much faster it will seem when I get around to updating.
Click to expand...
Click to collapse
I noticed how faster it was before I saw everyone else posting about it, so at least no placebo on my end. Hope you find the same.
I know that you tried to get into Fastboot. Pixel 6/6P also has a Recovery mode. I can get to it from a working phone.
I would think that there is someway to boot into Recovery mode from a dead phone via button combos.
Thibale said:
Hello,
In the rush of flashing the january update I've flashed by mistake the Pixel 5 image bootloader (my wife's phone)
Yest that's stupid, I've done this every months for years with several Pixel phones, but I was listening to music at the same time and did dl the wrong image...
Anyway my phone is now hard bricked but I'm sure there must be a way to enter the other bootlader slot and/or entering a special recovery tool.
I cannot enter bootloader anymore
Requesting some help as I'd avoid to send it for a reflash...
Thanks !
Click to expand...
Click to collapse
Hy, how did you flashed? Via adb sideload or?
vrda08 said:
Hy, how did you flashed? Via adb sideload or?
Click to expand...
Click to collapse
factory image with modified flash-all.bat
I'll do the exact same process when I'll get my phone back but this time I'll check the image name at least 3 times
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
steady 100% overnight while playing for 5 hours, thats not good i think
My story before I got into this mess:
I received my phone as a christmas gift to myself on January 2022
I really want to remove those bloatwares so obviously I'll unlock its bootloader and flash custom roms. I tested every roms available on a whole month of february and stayed for xiaomi.eu since I want the feels of miui but not the global one.
So far so good and im happy with eu rom until 22.8.10 update.
August 12, lunchbreak at work I decided to push some updates on my device. After flashing I still have almost 70-60% , I used it until 10%, after charging it my phne constantly loops at fast-charging animation and low power warning. I thought my cables were faulty or the charger plug itself. I didnt do anything and after a while it was okay.
about an hour later it just reboots itself, constantly powering on and off, unable to start itself, and after a while, i think 4-6 unsuccessful reboots and it fixes itself.
I just slept for a day not noticing anything. The morning I woke up, this is where i notice omething strange happen with my battery stuck at 100% even using some battery intensive apps before going to bed, looked up at battery stats and saw it stays constant for 16 hours.
I thought might be a bad update then I factory reset the phone. Still sitting at 100. I flashed previous version. No changes. This is the point I worried. I downloaded that 5 gigabyte fastboot rom of poco f3 global and still no signs of luck, I even choose to lock bootloader , still the same issue.
After collecting some infos, someone on TG said it might be related to PMIC breaking things up, ahardware-related issue.
Anyone having this? Thanks
There can be bugs on the weekly builds. Use the stable builds if you don't want to deal with potential bugs
Zinnz said:
There can be bugs on the weekly builds. Use the stable builds if you don't want to deal with potential bugs
Click to expand...
Click to collapse
i even rollback to global stock rom , same results, maybe ill bring my phone to service center, it may be an isolated case
fireclouu said:
i even rollback to global stock rom , same results, maybe ill bring my phone to service center, it may be an isolated case
Click to expand...
Click to collapse
I wouldn't go to a service center unless it's a hardware issue. You should be able to fix it, it just may take awhile of trial and error. you already have more knowledge than the average service center tech when it comes to flashing roms and whatnot, they're just wanna send it away most likely.
Also, could you summarize the issue you're having? It will increase your chances of someone replying with a potential fix
Zinnz said:
I wouldn't go to a service center unless it's a hardware issue. You should be able to fix it, it just may take awhile of trial and error. you already have more knowledge than the average service center tech when it comes to flashing roms and whatnot, they're just wanna send it away most likely.
Also, could you summarize the issue you're having? It will increase your chances of someone replying with a potential fix
Click to expand...
Click to collapse
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
fireclouu said:
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
Click to expand...
Click to collapse
There are Deep Flash Cables, I don't know if those work on Poco F3..
fireclouu said:
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
Click to expand...
Click to collapse
Just wanna ask a few questions to exclude them
Have you tried using a different USB cable /different USB port on your pc?
Have you tried entering recovery and factory reseting the phone before a new Rom flash?
Have you tried factory reseting the phone via settings after a new Rom flash, and after the phone boots up?
If you do think it's a hardware issue, it couldn't hurt to flash to stock and see what service center / xiaomi can do. I just wouldn't mention anything about the whole flashing business lol. But yeah, they might swap it out for ya best case scenario. But might be without a phone for awhile :/
fireclouu said:
View attachment 5686001
steady 100% overnight while playing for 5 hours, thats not good i think
My story before I got into this mess:
I received my phone as a christmas gift to myself on January 2022
I really want to remove those bloatwares so obviously I'll unlock its bootloader and flash custom roms. I tested every roms available on a whole month of february and stayed for xiaomi.eu since I want the feels of miui but not the global one.
So far so good and im happy with eu rom until 22.8.10 update.
August 12, lunchbreak at work I decided to push some updates on my device. After flashing I still have almost 70-60% , I used it until 10%, after charging it my phne constantly loops at fast-charging animation and low power warning. I thought my cables were faulty or the charger plug itself. I didnt do anything and after a while it was okay.
about an hour later it just reboots itself, constantly powering on and off, unable to start itself, and after a while, i think 4-6 unsuccessful reboots and it fixes itself.
I just slept for a day not noticing anything. The morning I woke up, this is where i notice omething strange happen with my battery stuck at 100% even using some battery intensive apps before going to bed, looked up at battery stats and saw it stays constant for 16 hours.
I thought might be a bad update then I factory reset the phone. Still sitting at 100. I flashed previous version. No changes. This is the point I worried. I downloaded that 5 gigabyte fastboot rom of poco f3 global and still no signs of luck, I even choose to lock bootloader , still the same issue.
After collecting some infos, someone on TG said it might be related to PMIC breaking things up, ahardware-related issue.
Anyone having this? Thanks
Click to expand...
Click to collapse
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Have you tried using a different USB cable /different USB port on your pc?
Click to expand...
Click to collapse
yup i thought my cables are faulty so i borrow other cable thats also come from xiaomi
Have you tried entering recovery and factory reseting the phone before a new Rom flash?
Click to expand...
Click to collapse
done that too, I formatted the device before flashing it again, only dirty flash on eu update, after my issue arises ive done clean flash, does also too before reflashing stock rom on fastboot
Have you tried factory reseting the phone via settings after a new Rom flash, and after the phone boots up?
Click to expand...
Click to collapse
done as well, even on stock rom, i also lock my bootloader just to be sure, but still at 100%
one thing I also did was manually flashing persist but it wouldnt let me in, I tried also on recovery terminal, via orangefox, and twrp.
tried flashing persist manually too using
Code:
dd
, output says it pushed successfully but I dont think so. fastboot disabled flashing persist, needs edl mode.
Rstment ^m^ said:
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Click to expand...
Click to collapse
oh this is new to me, okay ill try bootloader, wish me luck flash it rn
Rstment ^m^ said:
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Click to expand...
Click to collapse
didnt fixed too, i even booted to fastbootd tried flashing there but boot_ab inaccessible, only in normal fastboot
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
fireclouu said:
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
Click to expand...
Click to collapse
I had to flash a ROM through EDL Mode once (I hardbricked my phone). I had to pay someone on Telegram with an Authorised Xiaomi Service Center Account 25€ and it did work.
So... it seems to be locked by Xiaomi. Apparently to stop people from importing phones from China and flashing Global ROM on them.
cyanGalaxy said:
I had to flash a ROM through EDL Mode once (I hardbricked my phone). I had to pay someone on Telegram with an Authorised Xiaomi Service Center Account 25€ and it did work.
So... it seems to be locked by Xiaomi. Apparently to stop people from importing phones from China and flashing Global ROM on them.
Click to expand...
Click to collapse
xiaomi fked up the system now blackmarket abuse this kind of restrictions
fireclouu said:
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
Click to expand...
Click to collapse
What are we even talking about anymore?
You'll pay 20$ for edl that likely won't do anything, you're just delaying inevitable. If pmic is not reset via bootloader ( fastboot reboot bootloader ) that's where you start thinking it's hardware issue.
What do u even wanna flash? Open stock ROM folder and enter folder called images on pc - look what's inside, persist, cust, boot everything is in there and was flashed already...
Just take your phone to service center while you still can , if under warranty keep requesting new motherboard . They'll likely try battery replacement first.
If it's not under warranty then ok play around as much you feel the need to , it just makes no sense to beating your head with all of this when warranty covers it
Rstment ^m^ said:
What are we even talking about anymore?
You'll pay 20$ for edl that likely won't do anything, you're just delaying inevitable. If pmic is not reset via bootloader ( fastboot reboot bootloader ) that's where you start thinking it's hardware issue.
What do u even wanna flash? Open stock ROM folder and enter folder called images on pc - look what's inside, persist, cust, boot everything is in there and was flashed already...
Just take your phone to service center while you still can , if under warranty keep requesting new motherboard . They'll likely try battery replacement first.
If it's not under warranty then ok play around as much you feel the need to , it just makes no sense to beating your head with all of this when warranty covers it
Click to expand...
Click to collapse
its true , im just trying to figure this out myself if possible or not, accessing service center here is much more troublesome rather fixing it in such way i think possible
but yeah ill update soon enough, tomorrow will be my only day off for a week, will definitely take a visit, wish me luck!
update: i sent my phone to mi authorized drop points yesterday. expected to get it repaired within 2 weeks and to pick it up next month.
update: today Ill pickup my device, will ask what could be the cause of the issue
fireclouu said:
update: today Ill pickup my device, will ask what could be the cause of the issue
Click to expand...
Click to collapse
Good luck! Let us know
so I got the device, support told me about the issue: battery only replugged, no other service, no replacements needed, seems some wirings got loose.
Ive read similar incident here, s/he only did replug the cable, got it fixed. Same issue on my end
hi, I need help. MY phone got bricked after rebooting into recovery and it has a bootloop, and I can't access Fastboot even though my bootloader is unlocked. If I try to enter BROM mode, in device manager it shows that it is connected as "Oplus Preloader" and no software recognizes it, only "MTKClient", although it gives the error of "handshake failed, retriying..." can anyone tell me how to switch to MTK preloader or some method that can revive my phone? in addition to RCSM Tool, which is a paid tool
I have the EXACT same issue. I have given my phone to a repair shop nearby and requested a chip-off flashing (a risky process), after being frustrated for a month by trying various ways. Don't know if it will survive. If it doesn't, I'm not getting a MediaTek phone next time. At least in Snapdragon phones the fastboot and recovery don't get messed up after bricking and the phone is always fixable easily.
DeviceMesser said:
I have the EXACT same issue. I have given my phone to a repair shop nearby and requested a chip-off flashing (a risky process), after being frustrated for a month by trying various ways. Don't know if it will survive. If it doesn't, I'm not getting a MediaTek phone next time. At least in Snapdragon phones the fastboot and recovery don't get messed up after bricking and the phone is always fixable easily.
Click to expand...
Click to collapse
In my case. that's happened because i was testing RMUI4 trial version, but, i losed RIL , because i'm from LATAM and Trial Version is from India region, so, when i wanted reboot to recovery (TWRP), my phone only try reboot to recovery, and i cant access to fastboot or brom mode because realme "renamed" the preloader and fix the brom exploit...
JosVel1222 said:
In my case. that's happened because i was testing RMUI4 trial version, but, i losed RIL , because i'm from LATAM and Trial Version is from India region, so, when i wanted reboot to recovery (TWRP), my phone only try reboot to recovery, and i cant access to fastboot or brom mode because realme "renamed" the preloader and fix the brom exploit...
Click to expand...
Click to collapse
As if bypassing bootloader was already not tedious enough... Thanks Realme!
JosVel1222 said:
In my case. that's happened because i was testing RMUI4 trial version, but, i losed RIL , because i'm from LATAM and Trial Version is from India region, so, when i wanted reboot to recovery (TWRP), my phone only try reboot to recovery, and i cant access to fastboot or brom mode because realme "renamed" the preloader and fix the brom exploit...
Click to expand...
Click to collapse
I even purchased the RCSM tool as I lost hope. Even it didn't work! Like it is the official service center tool and even it didn't work! That exactly was when I lost all hope and went to the repair shop. Those guys were hesitant about trying the chip off method, but I assured them that it is no problem if the phone dies. Fingers crossed, I'm hoping for the best. Looking for a POCO F4 as my next phone if it failed. Anyways, happy new year!
I'm experiencing the same problem, I didn't change the format all option when using SPFT and my phone got hardbricked, no access to fastboot or recovery, tried flashing firmwares with spft but no luck. Then I found a newer firmware with realme ui 3 and flashed it but still the phone wouldn't turn on. After that, everytime I try to use mtk client I get "31mCouldn't get device configuration" error and if I use spft it just never begins downloading.
DeviceMesser said:
I even purchased the RCSM tool as I lost hope. Even it didn't work! Like it is the official service center tool and even it didn't work! That exactly was when I lost all hope and went to the repair shop. Those guys were hesitant about trying the chip off method, but I assured them that it is no problem if the phone dies. Fingers crossed, I'm hoping for the best. Looking for a POCO F4 as my next phone if it failed. Anyways, happy new year!
Click to expand...
Click to collapse
Hope they can revive your phone.
Dhasx said:
I'm experiencing the same problem, I didn't change the format all option when using SPFT and my phone got hardbricked, no access to fastboot or recovery, tried flashing firmwares with spft but no luck. Then I found a newer firmware with realme ui 3 and flashed it but still the phone wouldn't turn on. After that, everytime I try to use mtk client I get "31mCouldn't get device configuration" error and if I use spft it just never begins downloading.
Hope they can revive your phone.
Click to expand...
Click to collapse
They actually revived the phone! Tbh, I had zero hopes for it, but thanks to them, I'm typing this on my phone. But, the rear camera isn't working for some reason. However, the phone is working as good as new .
Dhasx said:
I'm experiencing the same problem, I didn't change the format all option when using SPFT and my phone got hardbricked, no access to fastboot or recovery, tried flashing firmwares with spft but no luck. Then I found a newer firmware with realme ui 3 and flashed it but still the phone wouldn't turn on. After that, everytime I try to use mtk client I get "31mCouldn't get device configuration" error and if I use spft it just never begins downloading.
Hope they can revive your phone.
Click to expand...
Click to collapse
do you have any solution for this because i have the same problem??
DeviceMesser said:
trThey actually revived the phone! Tbh, I had zero hopes for it, but thanks to them, I'm typing this on my phone. But, the rear camera isn't working for some reason. However, the phone is working as good as new .
Click to expand...
Click to collapse
Congrats!! What firmware did they install, same region ?, is the bootloader locked ?, does dual sim work normally ?. I'm sorry for the amount of questions but I'm really curious since only one technician was willing to try the chip off method but he looked sketchy.
Wojtek512 said:
do you have any solution for this because i have the same problem??
Click to expand...
Click to collapse
Sadly no, I left my phone at a technician who said he would try to revive the phone using "special hardware", but I dont feel optimistic.