Related
So I recently tried updating MIUI v5 to MIUI v6. However, I stupidly opted for the FOTA update, rather than updating using recovery.
After running the update, my phone rebooted and it worked fine, MIUI v6 running great. However, because I'd updated using the in-built updater, my data and apps were still there from before. This was causing no-end of 'process stopped running' alerts, which drove me crazy after around 10 minutes.
Therefore, I decided to try and wipe my data. I went to the recovery menu and found that MIUI had installed its own Chinese recovery, my previous TeamWin one was gone. So I fumbled around and managed to find the 'Wipe data' etc. option, and chose it. I was presented with a couple more options which I didn't understand, and (stupidly) accepted both. This left me with a phone that would no longer boot past the 'Sony' logo. I was also unable to access the Chinese recovery menu.
Feeling a little worried at this point, I started to Google around for guides on how to flash a recovery back onto a phone stuck in a boot loop. After hours of searching, I decided it wasn't possible and instead follow a guide for fixing 'boot loops' through flashing an original Sony 'ftf' firmware using flashtool.
Now, the guide I was following was quite old, and provided a link to 'C6903_14.2.A.0.290_Global LTE' - so this is what I used to flash (which I'm now regretting). Before flashing, I was presented with some options, for which the guide I was following recommended I deselect the 'kernel' option. So I did this too.
After around 10-15 minutes and what seemed like a successful flash, I tried turning the phone on. This time, the Sony logo appears, then disappears to a black screen, and then the backlight turns off, followed by the Sony logo, then a black screen, then backlight turning off, etc. So slightly different behaviour to before, but still boot looping.
I think what may have happened is that MIUI includes an updated kernel, and through flashing the 14.2.A.0.290 firmware without a kernel, I've introduced some sort of incompatibility.
The problem I'm having now is getting another firmware onto the phone in order to resolve this. For some reason, despite flashtool recognising the phone being plugged in with flash mode, it refuses to load the firmware - I'm instead presented with the message:
"You must have the according fsc script to flash this device."
Does anyone know how I might be able to get around this? I admit to being a bit of a noob when it comes to flashing so have probably dug my own hole here, and seem to have left myself completely unable to work out what I need to do in order to get back out! Any help would be hugely appreciated.
Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!
langauld said:
Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!
Click to expand...
Click to collapse
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)
Just2Cause said:
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)
Click to expand...
Click to collapse
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.
langauld said:
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.
Click to expand...
Click to collapse
Glad I could help.
I can't seem to figure out how to enter into recovery mode on my T-Mobile G4. It's running everything completely stock. I have tried holding power button and volume up until the logo comes on and releasing both buttons and then immediately holding them both down again waiting.. and nothing happens. I've even tried waiting for one second after I initially release to hold them down again. Same outcome. It always just boots back up into Android. I have tried volume down instead.. Nothing. Can someone please show me how to boot into recovery mode? Again, running stock rom.
I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.
Demati said:
I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.
Click to expand...
Click to collapse
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
From the T-mobile website: https://support.t-mobile.com/docs/DOC-21911
stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.
That's not what I'm talking about. That's talking about factory resetting your phone with the hardware keys. I'm talking about entering recovery mode (kinda like the bios of the phone) using the hardware keys.. It's different.
Demati said:
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.
Click to expand...
Click to collapse
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.
stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
stringz90 said:
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.
Click to expand...
Click to collapse
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?
Demati said:
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?
Click to expand...
Click to collapse
Alright.. I guess, I'll have to try that, but first is there any way to do a backup of some sort in case I have to go back to stock rom rooted? I got my G4 about a month ago and haven't done much research on rooting this specific device. I haven't had a high end phone with rooting and rom options in a long time. The last phone I had a chance to root and install cool custom roms on was a Samsung Galaxy S2. If you can guide me in the right direction I'd appreciate it. I guess I have to start from square one again. In the past I remember that in order to go back to completely stock you had to have a usb jib to reset the flash counter. Is it the same for this case? I welcome anyone's helpful input. Thanks, everyone.
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.
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
BJack0 said:
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
Click to expand...
Click to collapse
try booting twrp
'fastboot boot img name' then flash recovery from there. hope it works.
BJack0 said:
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
Click to expand...
Click to collapse
Don't worry, things can be recovered easily. Until you get more knowledgeable and you understand more about flashing use this failsafe to recover from (almost) anything
Go here and get the latest fastboot ROM for your phone.
https://xiaomifirmwareupdater.com/miui/raphael/
For now make sure you get the one that matches the region for your phone.
Then follow this guide to flash it
https://c.mi.com/thread-1857937-1-1.html
Use the fastboot flashing section.
Make sure you change the flash option to 'clean all' when flashing. The default option will lock the bootloader again after flashing. If you do the default option with any ROM that is not the same region as the phone you will hard brick the phone, this is why I recommend getting the ROM that matches your phone.
When unpacking the fastboot ROM, it is a Linux/Unix zipped tarball, most Windows zip software will need to extract it twice. The first time will give you a single .tar file (if it doesn't have an extension then rename it and add .tar to the end) You will then need to extract everything from the tar file, which you give you the folder, containing the ROM data, to point the Mi Flash Tool at.
After doing this you, if you've remembered to change the flash option to 'clean all', then you'll have restored to stock and kept the bootloader unlocked. Now you're good to try again.
Keep a copy of the fastboot ROM on your PC and back everything up on your phone before flashing. Then if you get in a mess you know how to easily recover things.
Once you get more experienced there will be other things you might be able to do, depending on the situation, that allow you to get things working without losing everything and needing to start from scratch.
Thanks
Robbo.5000 said:
Don't worry, things can be recovered easily. Until you get more knowledgeable and you understand more about flashing use this failsafe to recover from (almost) anything
Click to expand...
Click to collapse
Thank you so much for the details post, I will try what you have said above and will report back with my results. I have one question if you know the answer ( My phone is the UK edition of the Mi 9T pro ) Would I need to download the global or EEA fastboot version.
BJack0 said:
Thank you so much for the details post, I will try what you have said above and will report back with my results. I have one question if you know the answer ( My phone is the UK edition of the Mi 9T pro ) Would I need to download the global or EEA fastboot version.
Click to expand...
Click to collapse
For safety download the EEA ROM.
I also suggest you immediately flash dm_verity (https://forum.xda-developers.com/k20-pro/how-to/flashing-orangefox-recovery-mi-9t-pro-t3980579), after you flash twrp, wipe data and then flash that
Sent from my Redmi K20 Pro using Tapatalk
Robbo.5000 said:
For safety download the EEA ROM.
Click to expand...
Click to collapse
Everything you said worded flawlessly and your a life saver. If you dont mind do you have a link to a set of guides on how to correctly flash a custom recovery and lineage OS? since when I try to research these guides I get 5 different versions of TWRP and lock my phone out :laugh:
ishaqtkr said:
I also suggest you immediately flash dm_verity after you flash twrp, wipe data and then flash that
Click to expand...
Click to collapse
If you dont mind me asking could you go into slightly more detial on that since I have seen orange fox but I dont understand what dm_verity is.
Please ignore all reply's above as I am going to make another separate post about lineage OS
Thank you for replying and resolving my issue.
Have tried flashing various miui and a few custom roms, all get stuck on animation. Have tried miui fastboot roms first build and latest, pretty much everything I can think of to no avail. Am I missing something? Open to any suggestions to get this phone working again. Fastboot and recovery (custom and stock) all work, flashing works it just won't get past that loading screen.
hoopsnake said:
Have tried flashing various miui and a few custom roms, all get stuck on animation. Have tried miui fastboot roms first build and latest, pretty much everything I can think of to no avail. Am I missing something? Open to any suggestions to get this phone working again. Fastboot and recovery (custom and stock) all work, flashing works it just won't get past that loading screen.
Click to expand...
Click to collapse
If flashing a fastboot ROM isn't working, then maybe something physically has gone wrong with the phone. Are you using the clean all or the keep data option, when flashing? Make sure you're using the clean all option (but definitely not the clean and lock option).
Fastboot ROMs are normally the last resort, failsafe way to recover the phone, so it's unusual for them not to work.
Also how long are you waiting at the initial animation screen?
Also try a different, good quality USB lead and/or a different USB port and/or a different PC if you can.
Robbo.5000 said:
If flashing a fastboot ROM isn't working, then maybe something physically has gone wrong with the phone. Are you using the clean all or the keep data option, when flashing? Make sure you're using the clean all option (but definitely not the clean and lock option).
Fastboot ROMs are normally the last resort, failsafe way to recover the phone, so it's unusual for them not to work.
Also how long are you waiting at the initial animation screen?
Also try a different, good quality USB lead and/or a different USB port and/or a different PC if you can.
Click to expand...
Click to collapse
Something more than likely broke hardware wise.
Always clean all, but unfortunately after many hours of trying I misclicked and locked a few hours ago, on the stock rom but which would of been lucky if I wasn't already stuck in bootloop.
Next option, took back panel off and had a look, red water indicator near headphone jack, the rest are still white so many some sort of water damage has happened idk how, everything else is clean and dry.
Next best bet is edl with a authorized mi account (no luck yet) or just ship it off to Xiaomi.
Umm, what did you do before you got this problem?
tbh, most users just skip a step and then nothing works. I'm assuming this is the case?
What is your phone variant? previous ROM? ROM you tried to apply?
what vendor are you using? and most importantly, what steps are you doing to flash the new rom.
Sandeeep Kiran said:
Umm, what did you do before you got this problem?
tbh, most users just skip a step and then nothing works. I'm assuming this is the case?
What is your phone variant? previous ROM? ROM you tried to apply?
what vendor are you using? and most importantly, what steps are you doing to flash the new rom.
Click to expand...
Click to collapse
Literally nothing, flashed global stable zip a week before with f2fs, and dfe, it was about a week without modifying anything or even entering twrp and it just did a random reboot then just died and started boot looping.
K20 Pro, previous was lineage os, format data to get back to miui, flash miui, f2fs, dfe.
Now since bootloop, and edl, fastboot, recovery all work but with locked bootloader, I guess only option is edl flash.
My mi account must be magic or something, so downloaded mi unlock and bootloader unlocked immediately, no wait time. Was very surprised so to double check did fastboot OEM device-info and indeed bootloader is unlocked. Now flashing fastboot rom fingers crossed.
IT BOOTED, I have my phone backkkkkk. No idea how or what happened, happened but it's back up and running hopefully for good.
Somehow locking and unlocking bootloader fixed it.