{
"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
Related
Hi!
So earlier today I was using the phone as usual and I decided to update some apps because I had wifi available for once.
I go to the Xposed installer and updated a youtube addon and Gravitybox, about 20 seconds later the phone freezes and turns off (before I even get to reboot myself).
Since then it continues to bootloop - I try to access TWRP and the phone just freezes on the kernel bootscreen, or restarts.
My computer won't recognize the phone and there's nothing I can do.
Sometimes my phone actually goes further than just the kernel bootscreen, it acctually boots the system, but it always freezes before I get to do anything (but the time is random)
Although the phone doesn't freeze when I'm in the recovery menu (the white one, but as soon as i click yes for twrp, it gets stuck)
I have a regular H815, BL is unlocked and im using the Genysis Rom. (Marshmallow)
What I've tried:
Access TWRP through ADB
Access TWRP through the phone ( vol down etc)
Access Download Mode, computer won't recognize the device.
Boot normally.
Remove SD/Sim and do the above.
I'm stumped guys. So I came here. Any help would be apprecieted.
Deciding to bump this popular thread by updating my progress.
I managed to make download mode work, I flashed a KDZ matching my current rom, it was successfull according to the LGUP program, but the phone is still rebooting, I cleared data, but it's still not booting up.
I later tried downgrading and wiping the whole phone. Flashed the original rom i had when I bought the device... The screen with Lg and (Bootloader is unlocked) is still the only screen I get, anything I do doesn't seem to work and I'm starting to lose hope.
Although I've noticed, that everytime I flash KDZ, it still shows the same rom of origin, even if i just flashed another, meaning the flash wasn't effective. Is there any other programs than LGup? the LG flashtool won't find it, although Up will
It seems like the phone broke completely, yet it's still actually starting up. After googling I found that there was a common flaw with it actually bootlooping because of hardware issues - which I'm starting to think is the issue.
What S/N is it? ..if its starts with 505-509 it definitely has the hardware problem that causes the device to bootloop which you can read about in reddit(there are tons of reports there) also by quick searching in this same forum you can see threads of report of same issue... this is a known issue and LG themselves announce that there was a solder of some kind that causes the bootloop...if its still on warranty I suggest you go with that. They usually change the mobo itself to latest 601-60* and probably the screen if your having burn ins on the lcd..goodluck
innocence07 said:
What S/N is it? ..if its starts with 505-509 it definitely has the hardware problem that causes the device to bootloop which you can read about in reddit(there are tons of reports there) also by quick searching in this same forum you can see threads of report of same issue... this is a known issue and LG themselves announce that there was a solder of some kind that causes the bootloop...if its still on warranty I suggest you go with that. They usually change the mobo itself to latest 601-60* and probably the screen if your having burn ins on the lcd..goodluck
Click to expand...
Click to collapse
It's definetly a 505... lol.
y bootloaders been unlocked, meaning warranty is void. How would you reccomend hiding the fact its UBL?
Perhaps I could dirtyflash it with the wrong kernel, making it completely bricked. And just cluelessly leave it for warranty, but although I feel like that's a risk.
As far as I know there is no going back once you Unlock your bootloader and no warranty will be given whatever you do as IMEI of your phone is sent to LG when you unlock the device thru their site so when you do claim your warranty they will check to see if yours are unlock/lock. If you still push for a warranty they will charge you 200-250 dollars(estimated cost in our country) for the mobo replacement. Friendly advice, since its a paperweight now you could just sell it on ebay for 80-100 so dollars and buy a new phone.
So my phone is stuck on this issue. I haven't done anything wrong. My phone was just peacefully charging then the phone switches off by itself then the bootloop happened.
This showed on the screen:
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
Although it does turn off by itself if I ignore it, after I turn it on again and press enter or power button it boot until lockscreen and if I try to do something like unlocking, scrolling down notifs bar, and sliding through different page on home screen it will turn off again. It seem like it's crashing. The thing is I am not trying to root or flash something. I haven't done anything on my phone. I only have one phone and I badly need your help. I hope wiping or reformatting the phone is my last resort. My phone is updated to Android 11 and lateset MIUI (provided by the system itself and not downloaded somewhere). Thank you.
Well seems like something is corrupt.
It reboots when you touches the screen(or do anything)?
LR7875 said:
It reboots when you touches the screen(or do anything)?
Click to expand...
Click to collapse
It's more like it turns itself off again and if I try to press again power button if the problem show again, same thing happen. Sometimes MIUI logo appears and shuts down again it can't even go to lock screen.
Is there any chance you can unlock it?
It seems like your internal storage is corrupted.
LR7875 said:
Is there any chance you can unlock it?
It seems like your internal storage is corrupted.
Click to expand...
Click to collapse
At some point I did manage to unlock it but it happened only once and when I tried to open the notifs by scrolling down or tried to different part of homescreen it just shuts down. After that, it can't even go to the lockscreen after reboot. It's a never ending cycle. I can go to fastboot mode but I don't know if I can do miracle with that.
Well immediately plug into a computer and pull photos amd videos from it if you get it unlocked.
LR7875 said:
Well immediately plug into a computer and pull photos amd videos from it if you get it unlocked.
Click to expand...
Click to collapse
I reformatted it hoping that it will fix the problem. I was wrong. *sigh*
hyung_z said:
I reformatted it hoping that it will fix the problem. I was wrong. *sigh*
Click to expand...
Click to collapse
Well most likely your EMMC internal storage chip went bad R.I.P. (well maybe you sending those emojis will be more appropriate, but, oh well)
Maybe search more on google, I can't help you more
LR7875 said:
Well most likely your EMMC internal storage chip went bad R.I.P. (well maybe you sending those emojis will be more appropriate, but, oh well)
Maybe search more on google, I can't help you more
Click to expand...
Click to collapse
Do you think service center can help me with this or they'll probably just say to replace the phone if a bad chip is the case?
Maybe they will replace the motherboard with some fee. Or they will try to convince you to buy a new fancy phone just purely because xiaomi could earn more.
Thats all about luck (and problem is on xiaomi side, not your fault)
what's the smartphone model?
Redmi note 8 pro is the OP's phone.
Wait Wait just found some interesting lead.
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Patched SP flash tool!
heh, i have the same phone. reflash yours with the firmware that was on it before everything that happened. but don't flash userdata if you want your data on it
flashing it is simple process
LR7875 said:
Redmi note 8 pro is the OP's phone.
Wait Wait just found some interesting lead.
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Patched SP flash tool!
Click to expand...
Click to collapse
there is already a way to flash it with SPFT without authorization
also he must try to flash it in fastboot because it's not bricked
AsyJAIZ said:
there is already a way to flash it with SPFT without authorization
also he must try to flash it in fastboot because it's not bricked
Click to expand...
Click to collapse
He probably doesn't have his bootloader unlocked.
Fastboot OEM unlock wont work as oem unlock is probably not enabled in settings dev options.
LR7875 said:
He probably doesn't have his bootloader unlocked.
Fastboot OEM unlock wont work as oem unlock is probably not enabled in settings dev options.
Click to expand...
Click to collapse
ok i got it, then he should somehow put it in download mode...
Do you guys think I need to go to the service center because I don't know what to do. I really don't want to brick my phone. But a while ago my phone booted. I set it up just like buying a new phone but after I finished setting up, I just wait for the phone to catch up because I was afraid the phone will just shut down suddenly. And then, it happened again the phone shut downs without me doing anything. Now I tried to boot it up again but it is currently stuck at Redmi logo (plus "powered by android" at the bottom").
hyung_z said:
Do you guys think I need to go to the service center because I don't know what to do. I really don't want to brick my phone. But a while ago my phone booted. I set it up just like buying a new phone but after I finished setting up, I just wait for the phone to catch up because I was afraid the phone will just shut down suddenly. And then, it happened again the phone shut downs without me doing anything. Now I tried to boot it up again but it is currently stuck at Redmi logo (plus "powered by android" at the bottom").
Click to expand...
Click to collapse
SPFT enables when phone is a brick, so there's no need in service center.
they will flash it like we are going to do
Help, does anyone know how to fix dm-verity corruption? I was using my tab normally, then it suddenly shuts down and this error keeps popping up whenever my device boots. It goes on a loop unless I press the power button again.
deleted
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Thanks in advance.
PunkOz said:
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Thanks in advance.
Click to expand...
Click to collapse
Reflash the entire android 13 image
DespairFactor said:
Reflash the entire android 13 image
Click to expand...
Click to collapse
How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.
Read this thread if you haven't...
blackhawk said:
Read this thread if you haven't...
Click to expand...
Click to collapse
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
PunkOz said:
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
Click to expand...
Click to collapse
Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.
lottarake said:
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Click to expand...
Click to collapse
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.
If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.
Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.
rajchelu said:
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Click to expand...
Click to collapse
If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command
Then direct install in magisk app
If it fails when booting the image, device will just reboot into normal mode.
PunkOz said:
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Click to expand...
Click to collapse
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
DespairFactor said:
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Click to expand...
Click to collapse
I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle
96carboard said:
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
Click to expand...
Click to collapse
Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked
If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Markelijk said:
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Click to expand...
Click to collapse
We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.
Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".
But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.
I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.
But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.
Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.
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.
I flash different roms from time to time and on this occasion during a flash of Xiaomi eu rom my wire accidentally became disconnected from my PC and the phone just went black. no response to power button or volume buttons. I then did some research concerning EDL mode, got in touch with an authorized Xiaomi account user to do the flashing, opened up my phone, shorted the two pins and connected as Qualcomm 9008 Device driver. The Xiaomi account person then used team viewer to flash the rom. the whole process was a success software wise and i was really excited to use my phone again. the moment of truth came and i pressed the power button but still dead, no response. sadly just got a little over a year out of it. It was 8 gig ram version. Over $300 bucks. Do you guys think it could be possible that it's hardware failure instead of software? Like perhaps the phone was going to die anyway but just coincidentally died during a flashing process with the wire becoming disconnected. IDK seems too crazy for a situation like that.
Try it again. If you can connect with it, it's not bricked. Possible hardware failure but it might have been the flash got corrupted for other reasons during the process... assuming the right firmware was flashed. So repeat and see what you got.
Personally I avoid flashing and OTA updates/upgrades whenever possible. I will only use them when neccessary which is very rare.
blackhawk said:
Try it again. If you can connect with it, it's not bricked. Possible hardware failure but it might have been the flash got corrupted for other reasons during the process... assuming the right firmware was flashed. So repeat and see what you got.
Personally I avoid flashing and OTA updates/upgrades whenever possible. I will only use them when neccessary which is very rare.
Click to expand...
Click to collapse
Thanks for your response man. This phone originally came with a global firmware installed on it however I would flash china official firmware from time to time with no issues as well. the Xiaomi person flashed a china firmware. you think I should try again and flash global instead?
Jawadbz said:
Thanks for your response man. This phone originally came with a global firmware installed on it however I would flash china official firmware from time to time with no issues as well. the Xiaomi person flashed a china firmware. you think I should try again and flash global instead?
Click to expand...
Click to collapse
You're welcome.
Use what worked. Then if that works proceed at your own peril if you want to flash other firmware...
Be patient as you may get replies from others here that are more relevant to this specific device and issue.
Hi,if u say the flashing was done successfully there should not be a problem anymore.Just try to charge ur phone some time,maybe this can help...Is your phone still in EDL mode if u connect this to pc?