Related
Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter
Hi all,
I have a big problem with my phone.
I wanted to try out Resurrection Remix on my phone.
I installed twrp-3.0.2-0-dogo.img with fastboot.
After reboot i saw the Teamwin logo and then i did a full wipe of everything, except SD Card (like i always do when i install a custom rom)
Then i installed Resurrection Remix M v.5.7.3.zip from sd and gapps, then wiped cache and pressed reboot.
No error with flashing, when the phone booted and i saw some logo's, took like 2-3 minutes and then the phone went off and started to reboot and reboot, had to take the battery off to let it stop.
Since then my phone isn't working properly, i tried to flash different kinds of stock roms with flash tool including wipe options.
No errors with flashing, but the phone still doesn't boot or it goes off after Sony logo then i leave the battery out for 10 mins or so then it starts and it looks normal, i can install aps, i can call, but the first time when i reboot my phone with this new install it's back to rebooting. I tried to leave my battery out for 10 hours but it doesn't help.
I tried to relock my bootloader and then unlock it again.
If i tried to install twrp-3.0.2-0-dogo.img it's going to reboot also, i tried airless or evomix kernel, then recovery starts but when i try to install a custom rom zip, and try to flash it my phone reboots after 5 seconds.
And now i don't know what to do anymore, so please anyone? help?
Thanks in advance!
did you try installing stock rom with flashtool ?
What was your android version when you first flash TWRP 3.0.2 recovery?If you are coming from stock lollipop then you should flash TWRP 3.0.2 (.228).Make sure you unlocked phone bootloader.Use advance clean in the recovery,select all except sd card and clean all.Then try flashing RR Rom again.Do wipe cache/Delvik after flashing RR Rom and before flashing GAPPS.
falptekin said:
did you try installing stock rom with flashtool ?
Click to expand...
Click to collapse
Yes, i tried atleast :
C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf
C5503_10.6.A.0.454_HK.ftf
C5503_10.7.A.0.228_TR.ftf
And used all wipe options.
I used Emma tool, after that i removed the battery from the phone for 48 hours, then it booted the second time. I charged the battery and i left it like this for a few hours, then i tried to reboot but it went off after 20 seconds, tried to boot again but it goes off after Sony logo.
Røbin said:
What was your android version when you first flash TWRP 3.0.2 recovery?If you are coming from stock lollipop then you should flash TWRP 3.0.2 (.228).Make sure you unlocked phone bootloader.Use advance clean in the recovery,select all except sd card and clean all.Then try flashing RR Rom again.Do wipe cache/Delvik after flashing RR Rom and before flashing GAPPS.
Click to expand...
Click to collapse
My version was CM 13 (cm-13.0-20160801-UNOFFICIAL-dogo.zip) that was working very well, but before i flashed RR i did advanced cleaning and i checked everything except SD Card and USB OTG and a factory reset and after flashing pressed wipe cache/dalvik and then i rebooted.
The phone is off now without battery. This Sony doesn't have recovery, buttons aren't working and they never did, i can only flash twrp with fastboot wich makes it only boot into recovery and then i used this to flash custom roms.
I only started to flash custom roms about a month ago because someone gave me this Sony ZR, i bought a new original battery for it but when i call on speaker there is some underwater bubbling sound and i also wanted marshmallow and i hoped this may fix the bubbling sound, with CM 13 the sound was already better but didn't fix it completely.
TWRP won't let me flash anything anymore, it's starting to flash but after 5 seconds it reboots back into recovery.
Edit: Is it possible that there is still stuff in the RAM that is causing problems?
Edit: I thought i'm going to this phone another try. I installed twrp-3.0.2-0-dogo.img and it boots, also this version didn't want to boot anymore but now it does. I wiped everything, also SD Card, i checked everything is empty. Before i couldn't wipe my SD Card anymore and in Windows all files showed double and i couldn't copy files. Going to charge it first and think about what i want try to flash. Wipe cache/dalvik and then flash gapps is a good idea.
Edit: it almost charged now, when it charged i will remove the battery again for the night, i will decide later what i'm going to do.
Fuchsia said:
My version was CM 13 (cm-13.0-20160801-UNOFFICIAL-dogo.zip) that was working very well, but before i flashed RR i did advanced cleaning and i checked everything except SD Card and USB OTG and a factory reset and after flashing pressed wipe cache/dalvik and then i rebooted.
The phone is off now without battery. This Sony doesn't have recovery, buttons aren't working and they never did, i can only flash twrp with fastboot wich makes it only boot into recovery and then i used this to flash custom roms.
I only started to flash custom roms about a month ago because someone gave me this Sony ZR, i bought a new original battery for it but when i call on speaker there is some underwater bubbling sound and i also wanted marshmallow and i hoped this may fix the bubbling sound, with CM 13 the sound was already better but didn't fix it completely.
TWRP won't let me flash anything anymore, it's starting to flash but after 5 seconds it reboots back into recovery.
Edit: Is it possible that there is still stuff in the RAM that is causing problems?
Edit: I thought i'm going to this phone another try. I installed twrp-3.0.2-0-dogo.img and it boots, also this version didn't want to boot anymore but now it does. I wiped everything, also SD Card, i checked everything is empty. Before i couldn't wipe my SD Card anymore and in Windows all files showed double and i couldn't copy files. Going to charge it first and think about what i want try to flash. Wipe cache/dalvik and then flash gapps is a good idea.
Edit: it almost charged now, when it charged i will remove the battery again for the night, i will decide later what i'm going to do.
Click to expand...
Click to collapse
Someone maybe played with your phone in underwater to cause bubbling sound.I don't see any hardware problem in your phone.You maybe did something wrong or anything else that your phone behaving like this.Listen,You first flash a stock rom.Lollipop would be better because you can flash flashable twrp 3.0.2(.228) via flash fire or flashify app.I once tried flashing twrp img through fastboot and it caused bootloop.So I always use flashable zip.Fastboot for emergency.And try to reformatting your system pertition.I hope this will work or you'll need expert developer to help you.Maybe Daedroza can help you if my sugg. don't work.
Røbin said:
Someone maybe played with your phone in underwater to cause bubbling sound.I don't see any hardware problem in your phone.You maybe did something wrong or anything else that your phone behaving like this.Listen,You first flash a stock rom.Lollipop would be better because you can flash flashable twrp 3.0.2(.228) via flash fire or flashify app.I once tried flashing twrp img through fastboot and it caused bootloop.So I always use flashable zip.Fastboot for emergency.And try to reformatting your system pertition.I hope this will work or you'll need expert developer to help you.Maybe Daedroza can help you if my sugg. don't work.
Click to expand...
Click to collapse
The bubbling sound is a known issue with some Sony smartphones, on google i have read more stories about this problem, not only zr but also other Z models. The problem is caused by the second mic i think, if i use loudspeaker when calling and i lay the phone on the back the sound is much better. I saw on other thread about this, http://forum.xda-developers.com/xperia-zr/help/disable-mic-t3434997
On YouTube you can find many movies about this, for example https://www.youtube.com/watch?v=fC6JbuQJ_gg
It's really annoying for the other person to hear these sounds when you are calling. They need to listen very carefully to understand you, but it's only when you call on speaker.
When i wanted to flash a custom rom for the first time i wanted to do this with apps on my phone. I rooted my phone with kingroot and used an app to check if the phone was really rooted. I installed twrp app and tried to install recovery but it gave an error. I tried to install recovery with Flashify but then it says that the recovery partition is not present. When i try to flash with Flashify it says it's going to reboot into recovery but then the the phone boots like normal. The only way for me to get a recovery on the phone is just flashing with fastboot or using flashtool. Doomlord kernel and XZDualrecovery don't boot, only twrp is working.
Fuchsia said:
The bubbling sound is a known issue with some Sony smartphones, on google i have read more stories about this problem, not only zr but also other Z models. The problem is caused by the second mic i think, if i use loudspeaker when calling and i lay the phone on the back the sound is much better. I saw on other thread about this, http://forum.xda-developers.com/xperia-zr/help/disable-mic-t3434997
On YouTube you can find many movies about this, for example https://www.youtube.com/watch?v=fC6JbuQJ_gg
It's really annoying for the other person to hear these sounds when you are calling. They need to listen very carefully to understand you, but it's only when you call on speaker.
When i wanted to flash a custom rom for the first time i wanted to do this with apps on my phone. I rooted my phone with kingroot and used an app to check if the phone was really rooted. I installed twrp app and tried to install recovery but it gave an error. I tried to install recovery with Flashify but then it says that the recovery partition is not present. When i try to flash with Flashify it says it's going to reboot into recovery but then the the phone boots like normal. The only way for me to get a recovery on the phone is just flashing with fastboot or using flashtool. Doomlord kernel and XZDualrecovery don't boot, only twrp is working.
Click to expand...
Click to collapse
First of all change the kingroot with supersu.Kingroot root access control not so stable.Download selinux mode changer to set in permissive mode.If you are at LP version,twrp app won't install recovery or support it.flash twrp3.0.2(.228) via flashify or different flashing app.selinux permissive mode will let you to go to recovery mode.By the way,xzdualrecovery is for locked bootloader and should boot without any problem.I don't know it will work on unlocked bootloader or not.So try your best what I have told and this is all I have to share from my own experience.
Røbin said:
First of all change the kingroot with supersu.Kingroot root access control not so stable.Download selinux mode changer to set in permissive mode.If you are at LP version,twrp app won't install recovery or support it.flash twrp3.0.2(.228) via flashify or different flashing app.selinux permissive mode will let you to go to recovery mode.By the way,xzdualrecovery is for locked bootloader and should boot without any problem.I don't know it will work on unlocked bootloader or not.So try your best what I have told and this is all I have to share from my own experience.
Click to expand...
Click to collapse
I flashed the latest Lollipop and it's back to rebooting, i see the sony logo and before it says powered by android it goes off. I removed the battery again, i will try to root the phone and use selinux mode changer when it's booting. It wil take atleast 12 hours without battery before it boots.
Fuchsia said:
I flashed the latest Lollipop and it's back to rebooting, i see the sony logo and before it says powered by android it goes off. I removed the battery again, i will try to root the phone and use selinux mode changer when it's booting. It wil take atleast 12 hours without battery before it boots.
Click to expand...
Click to collapse
Is there any problem with your phone?Did you experiment your phone too much?I don't get it,why after flashing stock rom via flashtool gives you bootloops if no error showed up while flashing!!Is this your battery problem?And I think so because few months ago my phone battery heavily damaged and therefor It don't charge and my phone didn't bootup but bootlooping.I first thought it was my mistake to flash rom incorrectly.So i had to flash stock rom via flashtool to go back to normal but unfortunetly PC don't recoznige my phone not even fastboot.I was worried and couldn't do anything and went to service center,they changed the battery with new one and my phone comes to life again.Mainly this was for my local charger fault.it also damaged in that day too.SO brought a orginal sony charger.But you said you brought a new battery too then how come you face bootloops.well if there is no error message shows up I can't help you with anything.Only better expert member can help you.By the way you can collect log via adeb fastboot if your phone fastboot mod work.
Here is the inst:
1. Install the Android Debug Bridge using http://developer.android.com/tools/help/adb.html
2. Instructions on installing Android Debug Bridge are located here:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android- debug-bridge-utility
3. Run the following commands:
“adb logcat -c" (This clears the logs.)
4. Reproduce the issue.
5. Then, run the following command to capture the logs in a file:
“adb logcat -d > Name_of_Log_File.txt"
maybe it will gives some clues what is happening.
Røbin said:
Is there any problem with your phone?Did you experiment your phone too much?I don't get it,why after flashing stock rom via flashtool gives you bootloops if no error showed up while flashing!!Is this your battery problem?And I think so because few months ago my phone battery heavily damaged and therefor It don't charge and my phone didn't bootup but bootlooping.I first thought it was my mistake to flash rom incorrectly.So i had to flash stock rom via flashtool to go back to normal but unfortunetly PC don't recoznige my phone not even fastboot.I was worried and couldn't do anything and went to service center,they changed the battery with new one and my phone comes to life again.Mainly this was for my local charger fault.it also damaged in that day too.SO brought a orginal sony charger.But you said you brought a new battery too then how come you face bootloops.well if there is no error message shows up I can't help you with anything.Only better expert member can help you.By the way you can collect log via adeb fastboot if your phone fastboot mod work.
Here is the inst:
1. Install the Android Debug Bridge using http://developer.android.com/tools/help/adb.html
2. Instructions on installing Android Debug Bridge are located here:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android- debug-bridge-utility
3. Run the following commands:
“adb logcat -c" (This clears the logs.)
4. Reproduce the issue.
5. Then, run the following command to capture the logs in a file:
“adb logcat -d > Name_of_Log_File.txt"
maybe it will gives some clues what is happening.
Click to expand...
Click to collapse
I tried my old battery and it boots, already booted up 3x times. I never thought it maybe the battery because it's only 2 months old. Thanks so much for your help.
I tried to install recovery with selinux permissive mode and flashify but i stil can't install recovery.
It says: Partition not found, your recovery partition couldn't be found. You won't be able to flash recovery images. You can stil flash zip files.
I don't think it's possible to have recovery on this phone, atleast not the normal way.
Edit: I flashed RR and it's working fine. I'm so happy it's working again, i never really used this old battery but i think it's not so bad at all. I only lost 8% battery with flashing and booting RR. I never really thought it was the battery because it was charging normal, i used it for 2 months or something without problems.
Fuchsia said:
I tried my old battery and it boots, already booted up 3x times. I never thought it maybe the battery because it's only 2 months old. Thanks so much for your help.
I tried to install recovery with selinux permissive mode and flashify but i stil can't install recovery.
It says: Partition not found, your recovery partition couldn't be found. You won't be able to flash recovery images. You can stil flash zip files.
I don't think it's possible to have recovery on this phone, atleast not the normal way.
Edit: I flashed RR and it's working fine. I'm so happy it's working again, i never really used this old battery but i think it's not so bad at all. I only lost 8% battery with flashing and booting RR. I never really thought it was the battery because it was charging normal, i used it for 2 months or something without problems.
Click to expand...
Click to collapse
If it was a battery problem then change it or carefully use it.And the error you are facing is because the latest flashify has some bugs.But now as you are already using RR MM rom.You can download twrp app and use this app to install recovery.
Røbin said:
If it was a battery problem then change it or carefully use it.And the error you are facing is because the latest flashify has some bugs.But now as you are already using RR MM rom.You can download twrp app and use this app to install recovery.
Click to expand...
Click to collapse
I tried to install recovery, flashify hangs all the time, twrp app gives an error when i try to install recovery and flashfire says there is no partition for this image. I thought i'll do a factory reset in RR and when the phone rebooted i saw twrp. I tried with pressing the buttons when booting but no luck. I used reboot into recovery option and it worked. This is the first custom rom that gave my phone recovery.
I will throw the battery away and use the old battery, i can always buy a new one later.
Fuchsia said:
I tried to install recovery, flashify hangs all the time, twrp app gives an error when i try to install recovery and flashfire says there is no partition for this image. I thought i'll do a factory reset in RR and when the phone rebooted i saw twrp. I tried with pressing the buttons when booting but no luck. I used reboot into recovery option and it worked. This is the first custom rom that gave my phone recovery.
I will throw the battery away and use the old battery, i can always buy a new one later.
Click to expand...
Click to collapse
OH!So that the old recovery occupied all the recovery partition space that you are unable to install twrp recovery.But old recovery should be replaced by new recovery,that's strange.well I don't know how did this happen but don't use fastboot to install recovery or anything else,It's for emergency.I'm not fully familiar with fastboot though,I tried once before and caused trouble. I hope your troubles are gone now.
Røbin said:
OH!So that the old recovery occupied all the recovery partition space that you are unable to install twrp recovery.But old recovery should be replaced by new recovery,that's strange.well I don't know how did this happen but don't use fastboot to install recovery or anything else,It's for emergency.I'm not fully familiar with fastboot though,I tried once before and caused trouble. I hope your troubles are gone now.
Click to expand...
Click to collapse
My phone don't have any partition recovery, i tried 100x times with stock rom to boot recovery, with buttons, with apps that boot in recovery. I do have recovery with RR rom, but it's not in the recovery partition. I tried Tesla, CM 13, XOSP but still no recovery. I tried to boot recovery with all roms, but it doesn't matter. It's fine now, been playing a bit with RR and it's a nice rom. Thank you for helping.
So, as I say in the title, I've got this problem and I don't know how to solve it. I already looked on the other thread but I couldn't find anything really helpful.
It all started when I installed this module from Magisk (®FDE.AI, a battery optimizer). At the time I was using the xiaomi.eu ROM. When I rebooted the phone, as required, the recovery showed up, with the "/sdcard/" folder empty.
From then, I tried changing ROM back and forth, but the problem is always the same:
-When I install some apps and I reboot the phone or it boots in recovery or erase everything (showing me the initial setup screen)
-If the TWRP is installed and it reboot in recovery, I get either random error (in the data folder) or something like "Unable to mount /cache" and "Unable to mount /data"
-Random apps, at random condition, freeze. (Ex. Whatsapp, Telegram, Volum Control, Settings, Launcher, etc...)
ROM that I tried:
-xiaomi.EU
-Lineage OS
-MIUI 10.3.6.0 and MIUI 10.3.8.0 by fastboot (both messing up with the phone sensor: I had to flash persist.img)
-MIUI 10.3.11.0
What I already tried:
-Lock/Unlock bootloader
-Change TWRP
-Flash with Mi Flash the stock ROM
-Wiping Data/Cache/System and Format Data
-EDL flashing (without opening the back, but with the command "fastboot oem edl-mode"): it gives me an error, saying that my account is unauthorized
What should I try to do? I'm very desperate. Could be that the module I installed is still in the system?
You guys are my really last chance, I don't really know what to do.
EDIT:
We didn't find any kind of solutions, so some of us send the phone to get repaired.
Conclusion: DON'T EVER EVER INSTALL FDE.AI ON YOUR K20 PRO
EDIT2:
If you find to have the same problem as us, please write that on the FDE thread. Maybe the developer will do something!
EDIT3:
Mine K20 Pro got fixed by the service center by replacing the motherboard. There are no solution via software for now.
Same issue ! I dont know what to do
thelegoboy said:
So, as I say in the title, I've got this problem and I don't know how to solve it. I already looked on the other thread but I couldn't find anything really helpful.
It all started when I installed this module from Magisk (®FDE.AI, a battery optimizer). At the time I was using the xiaomi.eu ROM. When I rebooted the phone, as required, the recovery showed up, with the "/sdcard/" folder empty.
From then, I tried changing ROM back and forth, but the problem is always the same:
-When I install some apps and I reboot the phone or it boots in recovery or erase everything (showing me the initial setup screen)
-If the TWRP is installed and it reboot in recovery, I get either random error (in the data folder) or something like "Unable to mount /cache" and "Unable to mount /data"
-Random apps, at random condition, freeze. (Ex. Whatsapp, Telegram, Volum Control, Settings, Launcher, etc...)
ROM that I tried:
-xiaomi.EU
-Lineage OS
-MIUI 10.3.6.0 and MIUI 10.3.8.0 by fastboot (both messing up with the phone sensor: I had to flash persist.img)
-MIUI 10.3.11.0
What I already tried:
-Lock/Unlock bootloader
-Change TWRP
-Flash with Mi Flash the stock ROM
What should I try to do? I'm very desperate. Could be that the module I installed is still in the system?
You guys are my really last chance, I don't really know what to do.
Click to expand...
Click to collapse
Do you already tried a wipe data or format data in TWRP?
KaMyKaSii said:
Do you already tried a wipe data or format data in TWRP?
Click to expand...
Click to collapse
Yep, multiple times
try lr twrp
demonntl said:
try lr twrp
Click to expand...
Click to collapse
I tried both (the "vanilla" one and the LR), multiple times
thelegoboy said:
I tried both (the "vanilla" one and the LR), multiple times
Click to expand...
Click to collapse
if you have already open the back cover, try this:
- unplug the battery, connect the phone to computer with USB, wait for the phone to power up, connect the battery cable again and test.
if not, you should go to service center for warranty.
demonntl said:
if you have already open the back cover, try this:
- unplug the battery, connect the phone to computer with USB, wait for the phone to power up, connect the battery cable again and test.
if not, you should go to service center for warranty.
Click to expand...
Click to collapse
I think I'll send it back to get repair or something
I am having the same problem after installing fde.ai module, my phone always reset after reboot and my data is always wiped. anyone can help?
bougenville said:
I am having the same problem after installing fde.ai module, my phone always reset after reboot and my data is always wiped. anyone can help?
Click to expand...
Click to collapse
As you can see this is a serious problem.
I made a post in the FDE thread, but since no one has responded, could you make one you, too? Or just quote mine (it should be in the second-last page).
Anyone found a fix for it yet?
Nothing. I'm talking via email to the seller to send it to get repair. It's really sad that nobody help and the developer of FDE didn't care at all
After installing this mod on mi9t(not pro) also brick. Even EDL flashing didnt help
same issues, f*ck my life :laugh::laugh::laugh:
znsvs123 said:
same issues, f*ck my life :laugh::laugh::laugh:
Click to expand...
Click to collapse
Try to write a post on the FDE thread, maybe the developer will help you
thelegoboy said:
Try to write a post on the FDE thread, maybe the developer will help you
Click to expand...
Click to collapse
done, tried edl mode with someone helped me but didnt help. f*ck my life :silly:
my phone all of a sudden restart i didnt anything why?
Same here after flashing FDE.AI module my phone freezed and auto wipe data frequently. flashed fastboot and recovery roms many times and the problem still the same every time.
same here any one found fix ?!
akino553 said:
same here any one found fix ?!
Click to expand...
Click to collapse
nope, I think it's unfixable..
Sooooooo..... I have a problem. I am using AOSPK, and everything went very well, I was very happy with my new custom ROM. The Equalizer App kept crashing, so I installed Viper4android. That didn't really work, so I tried to fix it by installing APKs, Magisk Modules, which all resulted in the driver not being enabled. But then I stumbled across this thread here on XDA and there was a Module for Magisk I could flash which supposedly fixed the Error, but of course, that didn't work. As usual, I removed it with Magisk and rebooted it.
Now. The thing is, I am pretty much stuck on an endless Bootloop. I already had a Bootloop once, but those always led me back to TWRP. To get out of the AOSPK Kraken loading GIF, I had to let it like that overnight and let it drain its battery. Now, this morning I plugged the Phone in and tried again, but it didn't work. I let the battery drain itself again, but It only took like 10 minutes as it was plugged in for a short time. I only now found out I can press on Power + VolDown to force reboot.
I would REALLY love some help here, how do I get out of this mess? Do I plug into a PC and try to boot to TWRP? What do I do next? Please explain to me step by step, I am really in a sticky situation right now.
UPDATE: I can get into TWRP, not what? I wiped chache and dalvik, did nothing. What now?
Hi. I am also using Kraken rom. Check out this post if you want.
[GUIDE] Go back to stock - Galaxy S10 series
Hi 🙂 So you have bricked your Samsung S10 series handset and you need it fixed. Sometimes we try to modify our phones and it goes wrong, fret not it can be restored. DOWNLOADS Frija Microsoft Visual C++ 2008 Microsoft Visual C++ 2010 Phone...
forum.xda-developers.com
puul said:
Sooooooo..... I have a problem. I am using AOSPK, and everything went very well, I was very happy with my new custom ROM. The Equalizer App kept crashing, so I installed Viper4android. That didn't really work, so I tried to fix it by installing APKs, Magisk Modules, which all resulted in the driver not being enabled. But then I stumbled across this thread here on XDA and there was a Module for Magisk I could flash which supposedly fixed the Error, but of course, that didn't work. As usual, I removed it with Magisk and rebooted it.
Now. The thing is, I am pretty much stuck on an endless Bootloop. I already had a Bootloop once, but those always led me back to TWRP. To get out of the AOSPK Kraken loading GIF, I had to let it like that overnight and let it drain its battery. Now, this morning I plugged the Phone in and tried again, but it didn't work. I let the battery drain itself again, but It only took like 10 minutes as it was plugged in for a short time. I only now found out I can press on Power + VolDown to force reboot.
I would REALLY love some help here, how do I get out of this mess? Do I plug into a PC and try to boot to TWRP? What do I do next? Please explain to me step by step, I am really in a sticky situation right now.
UPDATE: I can get into TWRP, not what? I wiped chache and dalvik, did nothing. What now?
Click to expand...
Click to collapse
Hi, don't know if it's too late but I did have the same problem before and all I did was boot into TWRP. When you wipe make sure to check everything from Dalvil to Internal Storage and format data as well. Also if you are going to install Magisk try to do it after your phone boot into os otherwise it will stuck in bootloop again. I hope that's can help!
Hi, sorry for the bad english. My Xiaomi Note 11 worked perfectly fine for months since I bought it, but last night I accidentally left it charging for the whole night and when I woke up, it suddenly rebooted to recovery mode. I rebooted it back to system, which reboots the phone as usual, then I unlocked the lockscreen, everything went perfectly normal, until it rebooted again to recovery mode. I tried rebooting again, but it rebooted again to recovery mode after I unlocked the lockscreen. I tried booting it to safemode, but it went the same way. However, when I leave the lockscreen unlocked, it doesn't reboot itself. I tried turning it off and rebooting it with the screen unlocked but it did nothing. Do you guys ever have the same problem? Is there any way to fix it without wiping the data? I have some banking apps and other data that would be difficult to recover if I were to wipe out the phone.
I have the same problem too, I think it might have to do with the new update Xiaomi pushed to European devices in the last few days. We'll have to wait and see if they push a fix/if we find a fix...
Exact same problem, started appearing today. This is so weird. I already wiped data and the problem persists; went thorough the setup with no issue, and as soon as I finished it and the phone goes to the main screen, after a few seconds it started appearing again.
MIUI Global
13.0.16.0(RGCMIXM)
Android ver: 11 RKQ1.211001.001
asabaraba said:
Exact same problem, started appearing today. This is so weird. I already wiped data and the problem persists; went thorough the setup with no issue, and as soon as I finished it and the phone goes to the main screen, after a few seconds it started appearing again.
MIUI Global
13.0.16.0(RGCMIXM)
Android ver: 11 RKQ1.211001.001
Click to expand...
Click to collapse
It's really weird that it happens to other people too!
AdonysGames said:
I have the same problem too, I think it might have to do with the new update Xiaomi pushed to European devices in the last few days. We'll have to wait and see if they push a fix/if we find a fix...
Click to expand...
Click to collapse
That might be it since it happens not only to me.
Same problem happening for me too from today. Anyone know a fix for it ?
hrishi654 said:
Same problem happening for me too from today. Anyone know a fix for it ?
Click to expand...
Click to collapse
Did a second data wipe and it worked this time, the phone's been running all night without any issue. I disabled xiaomi updates for the time being
Same issue here, please any solution, I've not been able to do anything since 48 hours
Is there a way to go through this without losing my data and files?
same problem i will try to wipe data again and see if it works
ReaperCat65 said:
Hi, sorry for the bad english. My Xiaomi Note 11 worked perfectly fine for months since I bought it, but last night I accidentally left it charging for the whole night and when I woke up, it suddenly rebooted to recovery mode. I rebooted it back to system, which reboots the phone as usual, then I unlocked the lockscreen, everything went perfectly normal, until it rebooted again to recovery mode. I tried rebooting again, but it rebooted again to recovery mode after I unlocked the lockscreen. I tried booting it to safemode, but it went the same way. However, when I leave the lockscreen unlocked, it doesn't reboot itself. I tried turning it off and rebooting it with the screen unlocked but it did nothing. Do you guys ever have the same problem? Is there any way to fix it without wiping the data? I have some banking apps and other data that would be difficult to recover if I were to wipe out the phone.
Click to expand...
Click to collapse
I didn't put mine to charge and this happened
mateuszzsa said:
same problem i will try to wipe data again and see if it works
Click to expand...
Click to collapse
Can you give us an update if it works? I also post the problem on Reddit and some people there were also able to fix it by wiping the data.
Will wiping the data fix the issue, if it does, please do let us know
Dr_toluwani said:
Will wiping the data fix the issue, if it does, please do let us know
Click to expand...
Click to collapse
47 minutes since i wiped the data by the second time and my phone its working, I don't know until when.
Does anyone know of way to save the data? Surely it must be accessibl.
ishouldbeworking said:
Does anyone know of way to save the data? Surely it must be accessibl.
Click to expand...
Click to collapse
I found a way to do so. The problem is that once the phone is unlocked you have a few minutes before it gets booted into recovery mode. So:
Step 1) Have the phone connected to a computer before booting it up, with file explorer in the "this pc" category (where the phone storage will appear)
Step 2) boot the phone and input the password (if any)
Step 3) QUICKLY pull down the notification bar and press the usb options notification
Step 4) QUICKLY press the second option for file transferring
Step 5) QUICKLY open phone storage from pc once it pops up (at this point the phone screen will probably be black with a white loading circle but the phone storage is still accessible!!! You now have a few minutes to transfer any data you want)
Step 6) QUICKLY search through phone storage for any important data and copy/paste it to your computer
Sooner or later the phone will be booted to recovery mode and the mi logo will appear and the phone storage will disappear from the computer so repeat above steps until all your data is backed up.
If a file transfer gets stopped while running, copy/paste the data again on the next "run" and choose to ignore files that are already copied. With this method I managed to backup all my photos and files before wiping the phone.
This problem might be due to a problematic firmware update. My phone was running MIUI version 13.0.12(RGKEUXM) (europe version). I wiped the data and updated my phone to version 13.0.13(RGKEUXM) after setting it up just in case. I will update this thread if the problem reappears.
I am running RGCMIXM (13.0.16.0) and have encountered the issue. Really annoying. Did the wipe all and had no success. I hope someone can help find a fix. No feedback on the issue i logged thru the feedback app to Xiaomi.
akallabeth said:
I am running RGCMIXM (13.0.16.0) and have encountered the issue. Really annoying. Did the wipe all and had no success. I hope someone can help find a fix. No feedback on the issue i logged thru the feedback app to Xiaomi.
Click to expand...
Click to collapse
did you try to perform 2 wipes? apparently my device is working properly after that.
mateuszzsa said:
did you try to perform 2 wipes? apparently my device is working properly after that.
Click to expand...
Click to collapse
Which wipe method did you do? Just a factory reset or a reflash?