Related
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.
Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?
same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.
iXanza said:
same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.
Click to expand...
Click to collapse
I got this error as well,
After some search it seems using a deep flash cable could, I cannot make one currently so maybe you could take a look and try it
http://forum.xda-developers.com/showpost.php?p=69727277&postcount=2
I just checked the second post in the xiaomi eu thread
"- NEVER wipe /system partition manually in your life!"
hmm, I have always done this
Edit:
Many people reporting the same issue their.
There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.
iXanza said:
There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.
Click to expand...
Click to collapse
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
No clue. I'm taking it to the shop for them to do it for me tomorrow.
https://www.youtube.com/watch?v=ED96PJ-qYMM
Do follow the videos, i was hard brick 2 times but now it's working
The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS
Shaky156 said:
The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS
Click to expand...
Click to collapse
I don't really think that this is the problem because the "rom" flash completely successfully. I don't think that the font flash would cause all this mess. Anyway, I left it charging overnight and I keep pressing power button with vol +/- but nothing happens. Thanks anyway. it seems I have to either use test points or deep flash cable.
Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
EDIT: ok, got it booting now. The red blinking led is actually a good sign, it means low battery. I just let it charge for about 20 min and the led changed to yellow, and then I could boot it up.
It seems like in all that time the phone was plugged into my PC usb port for flashing, it didn't charge the battery. So I think we should take into account what Shaky156 said, just in case.
jiaming2009 said:
Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
Click to expand...
Click to collapse
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.
IMTLD said:
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.
Click to expand...
Click to collapse
Good to know it also worked for you, I just didn't believe that my battery was depleted from 70% just by hardbriking it...
After installing TWRP it asks to decrypt data even though I did not encrypt, hmmm what now
Edit:
I just did factory reset in TWRP and now I can see sdcard.
IMTLD said:
Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?
Click to expand...
Click to collapse
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.
idmissile said:
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.
Click to expand...
Click to collapse
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool
IMTLD said:
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool
Click to expand...
Click to collapse
At that point, I didn't really care if I lost data since I didn't have much on it anyway. Nice to hear that you got yours back. Those were dark hours, yes?
Thanks for giving a hope (checking way to recover from video). I'll get proper screwdrivers soon and try do the same.
I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS
Shaky156 said:
I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS
Click to expand...
Click to collapse
but how my mi5 now hardbricked no fastboot no recovery no edl
IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
I can confirm that this 100% works for me. You need to be a bit patient with the tweezers and getting the contact points right. It didn't immediately work for me, and I think I had to try a dozen times at least. But eventually it did recognize it. Once MiFlash can see it, you need to use the latest China stable rom. I tried the latest china dev, but it kept on giving errors of missing hello packets.
Well this is my second time I am trying to install custom ROM on any android phone. First one was some cheap phone from local brand. And I ended up in bricking that phone. This time it seems I have boot looped beloved Nexus 6. :crying:
So now I know I have very poor experience with MODing stuff.
I decided to install latest lineage OS on my Nexus 6.
I followed steps given on lineageos.org tutorial:
Enabled developer options
Enabled USB debugging
Enabled OEM unlock from developer options
Installed adb drivers
Connected Nexus 6 to PC using USB
Selelcted transfer photos (PTP) mode on nexus 6 in the prmpt that appeared after connecting USB
Booted into fastboot by doing "adb reboot bootloader" command (I have my volume down button screwed up while replacing battery. Though there is no visible damage. I dont know what happened . So I was not able to boot into fastboot by holding volume down while mobile powers on. )
Downloaded TWRP and installed it doing "fastboot flash recovery twrp-x-x-x-x-shamu.img" command
The lineageos.org tutorial then asks to boot into recovery using volume down key. But since mine was screwed up, I didnt know how I can do that. So I fiddled a bit in fastboot mode and found that when I press volume up, there comes "recovery mode" option. So I pressed power button when recovery mode is shown when in fastboot mode. It successfully booted in TWRP recovery.
Then I tried to perform the backup from the TWRP. I used to get something "unable to mount..." error. I tried it twice/thrice. Then I booted into Android. I realized that I can run "adb reboot recovery" command to get back into the recovery. So I tried that but then I got No Command error. So I pressed and held power button for some time, it booted into android. I ran "adb reboot bootloader". When in fastboot, I pressed volume till it showed recovery option and then pressed power button to boot into recovery. Then I tried backup again and it worked this time. So it never worked when I boot into TWRP for first time. I had to boot into android and then again back into TWRP (through fastboot) second time for it to work. This pattern repeated for other things.
Then I tried to perform backup of system through TWRP. Somewhat similar thing happened. It was giving "Unable to mount..." error. So I boot into Android, then into fastboot, then into TWRP and it worked. I booted into Android and copy pasted those backup files on my PC.
Then I tried to perform wipe from TWRP. It again gave "Unable to mount..." error. So I again followed above steps. Booting Android -> Fastboot -> TWRP and then performed wipe (I wiped everything cache, system etc). It worked.
Then lineageos.org tutorial asks to put lienageos zip at /sdcard/ using command "adb push filename.zip /sdcard/". I guess I tried it in recovery and it was not working. Hence I selected to reboot in bootloader (or I guess System) from TWRP. (I am not remembering this last steps as I was noting down only those steps which worked in notepad which are explained till last point in this procedure. But I know I rebooted from fastboot after wiping) And thats where I screwed it up :crying: . Now only Google logo displays. When I long press power button, the Google logo diappears for a while and reappear. Irony is that my volume down also seems to be screwed. What options I am left with???
... mmh
I miss the step "fastboot oem unlock" between 7. and 8. (before flashing TWRP) to open the bootloader
Your step "3. Enabled OEM unlock from developer options" is just the requirement to open the bootloader!
You have to open the bootloader with the adb prompt "fastboot oem unlock" after booting to bootloader!
1. open bootloader
2. reboot system !!!
3. reboot to bootloader
4. flash TWRP (custom recovery)
my advice - back to start ...
please look here for the last factury image and flash the whole image as described
-> https://developers.google.com/android/images
Mahesha999 said:
[*]Selected transfer photos (PTP) mode on nexus 6 in the prmpt that appeared after connecting USB
Click to expand...
Click to collapse
Select Transfer files.
When you boot after flashing LOS the forced encryption flag is set.
When the internal memory was decrypted.... the encryption process starts. Can take a very long time.
MartinN6 said:
... mmh
I miss the step "fastboot oem unlock" between 7. and 8. (before flashing TWRP) to open the bootloader
Your step "3. Enabled OEM unlock from developer options" is just the requirement to open the bootloader!
You have to open the bootloader with the adb prompt "fastboot oem unlock" after booting to bootloader!
1. open bootloader
2. reboot system !!!
3. reboot to bootloader
4. flash TWRP (custom recovery)
my advice - back to start ...
please look here for the last factury image and flash the whole image as described
-> https://developers.google.com/android/images
Click to expand...
Click to collapse
ohhh I felt its optional. I indeed do that "fastboot oem unlock" and it said it was successful. I just felt its optional and it did not had any effect on my phone, so I did not included that in the steps I performed above. Sorry my bad.
NLBeev said:
Select Transfer files.
When you boot after flashing LOS the forced encryption flag is set.
When the internal memory was decrypted.... the encryption process starts. Can take a very long time.
Click to expand...
Click to collapse
My phone is bootlooped (stuck on google logo). I am not even able to get into bootloader since my volume down key is screwed. I got screwed only after wiping data and before flashing LOS. Now I am trying to understand how your comment makes sense.
Mahesha999 said:
My phone is bootlooped (stuck on google logo). I am not even able to get into bootloader since my volume down key is screwed. I got screwed only after wiping data and before flashing LOS. Now I am trying to understand how your comment makes sense.
Click to expand...
Click to collapse
The possibility that the N6 is busy with encrypting and not looping (hopefully).
Other ideas:
When connected to a PC and adb environment is ok. Try the command: 'adb reboot bootloader'
Repeatedly while booting. In a dosbox it's easy to repeat a command with arrow up/down.
Keep start and vol up pressed and see if recovery comes up.
The screwed vol down.
Try to get a bit isopropanol/alcohol under the volume button to clean. Use a needle.
Instead of keeping the button down keep both vol.buttons down; maybe you are lucky.
Hi OP
May I ask:
if the bootloader was unlocked before you tried this time or stock with bootloader locked?
When you wiped did you wipe internal storage too or left it unchecked in TWRP?
NLBeev said:
The possibility that the N6 is busy with encrypting and not looping (hopefully).
Other ideas:
When connected to a PC and adb environment is ok. Try the command: 'adb reboot bootloader'
Repeatedly while booting. In a dosbox it's easy to repeat a command with arrow up/down.
Keep start and vol up pressed and see if recovery comes up.
The screwed vol down.
Try to get a bit isopropanol/alcohol under the volume button to clean. Use a needle.
Instead of keeping the button down keep both vol.buttons down; maybe you are lucky.
Click to expand...
Click to collapse
I tried doing all that with volume button. Finally imported circuit fom ebay.com and got it working.
Was able to Install lineageOS 15.1 successfully, but the experience wasnt that smooth due to disabled CPU
cores. I tried installing elementalX on lineageOS through their official app. But seems that I am back again in bootloop. I asked
the detailed question here. Can you please have a look?
Mahesha999 said:
Can you please have a look?
Click to expand...
Click to collapse
Trials with kernels and wiping/formatting may cause issues, because LOS forces encryption every time it's installed.
When you want to use LOS don't change the kernel and use the built-in kernel.
When the phone is not smooth, you may want to decrypt your Shamu and use a custom rom, like Nitrogen OS (Pie). A decrypted phone is necessary than.
NLBeev said:
Trials with kernels and wiping/formatting may cause issues, because LOS forces encryption every time it's installed.
When you want to use LOS don't change the kernel and use the built-in kernel.
When the phone is not smooth, you may want to decrypt your Shamu and use a custom rom, like Nitrogen OS (Pie). A decrypted phone is necessary than.
Click to expand...
Click to collapse
Ok didnt get you well.
How can I decrypt? Any official link.
Also installing Nitrogen OS means wiping out LineageOS?
Also didnt get "A decrypted phone is necessary than".
Do you mean decrypted phone is what is needed.
Also does that means there is simply no custom kernel compatible with LineageOS 15.1 for Nexus 6? and I have live with only two cores?
Sorry for too many questions... ;\
Mahesha999 said:
How can I decrypt?
Do you mean decrypted phone is what is needed.
Click to expand...
Click to collapse
A decrypted phone is only needed when you want to install a Pie rom like Nitrogen OS.
A new custom rom implies you will loose LOS.
There's nothing wrong with LOS, it worked well on my Shamu, but I used the built-in kernel and didn't care about the kernel and cores
For now. Try to get LOS working and use the built-in in kernel.
Decrypting your phone can be done with TWRP. You need to format everything including the sdcard.
But when you stick to LOS forget about decryption.
NLBeev said:
Trials with kernels and wiping/formatting may cause issues, because LOS forces encryption every time it's installed.
When you want to use LOS don't change the kernel and use the built-in kernel.
When the phone is not smooth, you may want to decrypt your Shamu and use a custom rom, like Nitrogen OS (Pie). A decrypted phone is necessary than.
Click to expand...
Click to collapse
After watching some videos and some googling, I realized that its not about the kernel actually which turns off cores but its hotplug mpdecision. I installed kernel audiutor and enabled all cores of my Nexus 6. Also I realized that max frequency of my active cores were something 1958 MHz. I just increase it to max 2649 MHz and rebooted. My Nexus 6 is going super smooth now. Also ran geekbench4 benchmarks.
These are the benchmarks.
Before changing CPU stuff
================================================
Benchmarks 1
-----------------------------------------------------------------------------------------------
Single core: 593
Multicore: 997
After changing CPU stuff
================================================
Benchmarks 2
-----------------------------------------------------------------------------------------------
Single core: 818
Multicore: 1009
Benchmarks 3
-----------------------------------------------------------------------------------------------
Single core: 1069
Multicore: 3029
I feel that two cores were still offline during benchmark 2. When I checked after benchmark 2, they were off in kernel adiutor CPU monitor. I re-enabled them and I reran the geekbench. I ended up getting benchmark-3 which are quite good and in fact above average for Nexus 6. For 5-10 minutes now, all cores are active.
I then googled and realized that mpdecision restarts after every reboot. So I have to disable mpdecision on every reboot to enable all cores. Initially I was not getting meaning of two ON/OFF switches on kernel adiutor's interface. They were "Apply on boot" and "mpdecision". Now I have "Apply on boot" switched ON and "mpdecision" switched off. That means on every reboot, all my cores will be up at full frequency right?
Also that means more power consumption. So I have done certain things to compensate. Enabled dark mode so that Nexus's quad HD AMOLED will consume less power. Also installed Franco kernel's Servicely app which allows app and services to put on sleep when screen is off. I am also planning to use Nexis 6's always in battery saver mode. I am ok as long as it performs fast (with two core off, battery saver mode was useless, now it seems like very normal). Its just that only top and bottom orange bars/strips in battery saver mode annoys me.
One more thing I will love to have to save battery. In MIUI, there is per app setting for what to allow when app is in background as can be seen here: http://nine-faq.9folders.com/articl...-background-restriction-on-the-xiaomi-devices On my poco f1, I keep almost all apps "No background activity mode". Only handful have "No restriction". This is letting me extend battery to days straight. Is similar possible on lineageOS say through some apps or setting.
Also do you feel my config all fine? Latest lineageOS + All cores running at full speed + Power saving settings explained above? Is this perfect for performance and battery life? Should I disable encryption for further performance?
(Will be testing battery life soon for few days.)
(Just to add things implicit to me: I wont be installing any social media app on this, I keep data and location off always. I will be using Nexus 6 mostly for reading in chrome, pdf, word and youtube.)
Mahesha999 said:
. . .I realized that its not about the kernel actually which turns off cores but its hotplug mpdecision. Also installed Franco kernel's Servicely
Should I disable encryption for further performance
Click to expand...
Click to collapse
I think you have done well. You've found the cause of performance issues and made your Shamu smooth again.
Dark mode is important for the battery life.
Decrypting will raise performance mainly when writing to internal storage. For daily use you won't hardly notice a difference. Your phone is running smoothly now. So there's no need for.
Lemme guess, you're here because something about EMUI just doesn't serve you well.
I sure hope you're in the right thread.
I found flashing mate 10 to be too confusing, I've spent over 10 hours working on mine to make it work, so I hope you don't have to.
I am new to flashing Huawei phones, so if there are anything that could have been done better, please let me know.
Please take everything I write with a grain of salt, this worked for me but I'm not sure if it will work for anyone else.
tldr: if you find a rom for honor view 10, there is a good chance that it would work for mate 10 too
*IMPORTANT: NONE OF THESE RECOVERIES OR ROMS USED ARE OFFICIAL, FLASH AT UR OWN RISK*
PLEASE READ ENTIRE POST BEFORE TRYING ANYTHING, YOU MIGHT SRSLY SCREW UP
Model: ALP-AL00 or A00 (its the Chinese duo sim version)
Steps:
1. Get ADB here
2. Unlock the bootloader, here's how.
3. Install twrp which is downloaded here
, I used "twrp_bla_alp_0.7.img". After you installed and run 'fastboot reboot', immediately unplug ur phone and hold up volume button until twrp shows up
4. Wipe your data in twrp with format data
a) If run into system unable to unmount error, try factory reset a few times then format until the error no longer appearsb) If ur device internal storage does not load or takes forever, restart your phone and enter twrp by 'adb reboot bootloader' and 'fastboot reboot', still immediately unplug and hold up buttonc) If after restart ur touchscreen stopped working. which happened to mine, connect a mouse via type c and proceed, don't panic6. Download rom here and install, make sure you flash all system, gapps, Huawei cam and hotspot patch at one go then reboot
7. Enjoy! :good:
Before you ask any questions:
- If you don't have ur bootloader unlocked, I got my code from a personal transaction for 30 euros, pm me for more info as I am not affiliated and do not want to publicly advertise
- If you never flashed any other rom before, I don't recommend this procedure
- If during setup your phone takes forever to update, just pop a sim card in and choose to restore ur phone from google account
- If you used the above point and after you get in system tries to setup in notification bar, just disable system setup in app settings
- If something went seriously wrong, you can always do emui recovery through pressing volume up in that "ur phone is unlock and can't be trusted" bootup screen (given you didn't screw up emui recovery, data format and factory reset in twrp will not rid emui recovery)
Where I ran into problems I can't resolve:
- After flashing the rom, my twrp doesn't seem to cooperate anymore as it just gets stuck on the loading screen forever. Reflashing twrp doesn't seem to solve the problem
What works (That I care about):
- Pretty much every normal function
- Huawei camera, tho it no where near as good as stock Huawei camera on emui for mate 10 but its miles above the default camera in custom roms
What's missing that I found so far (or I'm just too dumb to find it)
- Can't customize power menu
- Can't customize icons in notification bar
- No support for Huawei's fingerprint sensor gestures
- Snapchat bug (see pics), can be bandaged by the anything that toggles nav bar hide like xda's navigation gestures
Here are some images: https://imgur.com/a/kGkFP8C
Overall I have been using this rom for around 4 days now on my daily driver, it has been very stable and I would say its daily driver material. To those of you who wants to flash their mate 10, wish you the best of luck!
Hi,
Today my device was lagging and I restart it. Just after that I get the bootloop (showing MI.com logo). I can't open the recovery menu using the Power + Vol+ combination, but at least I could load FASTBOOT using Power + Vol-.
Using terminal command "fastboot reboot recovery" also doesn't help. I can't turn off the device as well - after some time showing me the logo device reboots again.
History - I have flashed my device ~1.5 year ago using OrangeFox + MIUI 11 raphael. The reason why I did it was my stock firmware didn't allow me to use NFC, there just was no option to enable it. After flashing everything was fine until today. Btw, device is unlocked. I am not sure what ROM version did use exactly because pretty much time passed already.
I spent a day googling for a solution, but didn't find anything.
What can be the reason? Is there a way to fix it?
If you haven't tried it yet, I'd suggest you flash your latest backup (if any) or flash the stock ROM again.
@TrulyPain no, I dont have any backup unfortunately.
Regarding the flashing stock ROM
1. Before I used OrangeFox to flash the device but now I cant boot recovery mode. Is there a safe way to do so?
2. Does only stock ROM fit? No custom?
Tried so many different approaches today. None of custom recoveries worked. I tried to use stock recovery - same result.
The only thing I didn't try is Mi Flash Pro stock ROM flash, but before that I wish to be sure I tried everything else.
Also, the repair specialist told me (remotely, he didn't check the device) that potentially it can be the memory hardware problem and advised me to visit Xiaomi official repair service. But.. it's pretty complicated for me currently.
romahaaa said:
Does only stock ROM fit? No custom?
Click to expand...
Click to collapse
I would recommend starting with the stock ROM as you can then more easily see if it is a hardware-related problem or not. Also, it sets a suitable environment for any custom ROM installed afterward. This, as many custom ROMs, don't contain all partitions and need some partitions to be written by the stock ROM, e.g., the "OEM" partition.
After you have installed stock ROM - if everything works fine - you can install any custom ROM of your choice following the recommended instructions.
We tried 2 difference ways to flash to phone using stock ROM, but no luck. Seems the problem was in the motherboard. Left it for repair, but.. doesn't mater already, as everything has lost. After that case I move to iPhone back - there would never happens this **** with data lost in unexpected cases.
Thanks for the help