Hi Friends,
I have decided to create a new post, since I researched and it seems that my issue is not covered exactly by any previous thread.
I have Sony F5321, used years with Stock ROM. While playing a game, it turned off randomly, but when I play the same game while charging with USB cable (with AC charger or connected to a laptop), the phone was working fine. I have unlocked the bootloader and flashed LineageOS 16 (Android 9) in case a battery issue was solved better with LineageOS than with stock ROM. After some weeks with same (supposedly) battery issue, I decided to go back to Stock ROM. I have flashed OK with Flashtool (no errors), but phone is now stuck in Sony boot logo.
The status is:
1) Boot into Stock Rom: doesn’t work
2) Boot into recovery: doesn’t work
3) Force shut down (3 vibrations): works
4) Force reboot (1 vibration): doesn’t work, it stops at Sony boot logo
5) Charging while powered off: doesn’t work (no battery logo appears, red light)
6) Flashtool into flashmode: doesn’t work (it’s not detected)
7) Flashtool into fastboot mode: works, but I cannot do anything with that.
Please, your help, how can I get the phone works again? Preferably with Stock ROM, or any other stable ROM, but working! Thanks!
Nobody will help?
jayeffpee said:
Hi Friends,
I have decided to create a new post, since I researched and it seems that my issue is not covered exactly by any previous thread.
I have Sony F5321, used years with Stock ROM. While playing a game, it turned off randomly, but when I play the same game while charging with USB cable (with AC charger or connected to a laptop), the phone was working fine. I have unlocked the bootloader and flashed LineageOS 16 (Android 9) in case a battery issue was solved better with LineageOS than with stock ROM. After some weeks with same (supposedly) battery issue, I decided to go back to Stock ROM. I have flashed OK with Flashtool (no errors), but phone is now stuck in Sony boot logo.
The status is:
1) Boot into Stock Rom: doesn’t work
2) Boot into recovery: doesn’t work
3) Force shut down (3 vibrations): works
4) Force reboot (1 vibration): doesn’t work, it stops at Sony boot logo
5) Charging while powered off: doesn’t work (no battery logo appears, red light)
6) Flashtool into flashmode: doesn’t work (it’s not detected)
7) Flashtool into fastboot mode: works, but I cannot do anything with that.
Please, your help, how can I get the phone works again? Preferably with Stock ROM, or any other stable ROM, but working! Thanks!
Click to expand...
Click to collapse
Sounds like hardware failure to me, happened to me before... However, if you can get into fastboot, just go ahead and flash back to a custom kernel and recovery, and see if you can boot to recovery. That will tell you if it's not a hardware issue, then you can figure out how to get back to stock...
levone1 said:
Sounds like hardware failure to me, happened to me before... However, if you can get into fastboot, just go ahead and flash back to a custom kernel and recovery, and see if you can boot to recovery. That will tell you if it's not a hardware issue, then you can figure out how to get back to stock...
Click to expand...
Click to collapse
I tried a lot of things now. To confirm, I tried to use Flashtool in fastboot mode, but not sure where I get a custom kernel file to use with Fastboot menu option "select kernel to flash" but I have downloaded again lineage-16.0-20200511-UNOFFICIAL-kugo.zip file, should I take "boot.img" from unzipped directory? and how to flash the twrp-3.3.1-0-kugo.img file with Flashtool? which is the option to flash recovery using Flashtool in fastboot mode?
jayeffpee said:
I tried a lot of things now. To confirm, I tried to use Flashtool in fastboot mode, but not sure where I get a custom kernel file to use with Fastboot menu option "select kernel to flash" but I have downloaded again lineage-16.0-20200511-UNOFFICIAL-kugo.zip file, should I take "boot.img" from unzipped directory? and how to flash the twrp-3.3.1-0-kugo.img file with Flashtool? which is the option to flash recovery using Flashtool in fastboot mode?
Click to expand...
Click to collapse
Don't need Flashtool for fastboot. If you have the drivers installed, use your computer, and connect with the power off, holding the volume up button, and let go of the button when you see the blue led light, (if you don't get a blue led light, could be further evidence of a hardware issue). Now you're in fastboot mode.
Open a command prompt, and type "fastboot". If fastboot / adb is installed on your computer, and is set in the path, you will get a fastboot reply, if not, you will get, "fastboot is not recognized as a program or command...", or something like that. In that case, you need to either install fastboot, (look it up - it takes about 30 seconds), or, in the case of Linux or if you have the fastboot / adb files on your computer, but it's not in the Windows path, just change directory in your terminal to the directory where the files are, then try the command again.
Once you have fastboot working, just copy whatever you want to flash to the same directory you're in, and the commands are:
Kernel -
Code:
fastboot flash boot [name of file].img
Recovery -
Code:
fastboot flash recovery [name of file].img
ROM -
Code:
fastboot flash system [name of file].img
OEM (needed for recent AOSP -based roms) -
Code:
fastboot flash oem [name of file].img
Curious - how did you flash Lineage last time?
levone1 said:
Don't need Flashtool for fastboot. If you have the drivers installed, use your computer, and connect with the power off, holding the volume up button, and let go of the button when you see the blue led light, (if you don't get a blue led light, could be further evidence of a hardware issue). Now you're in fastboot mode.
Open a command prompt, and type "fastboot". If fastboot / adb is installed on your computer, and is set in the path, you will get a fastboot reply, if not, you will get, "fastboot is not recognized as a program or command...", or something like that. In that case, you need to either install fastboot, (look it up - it takes about 30 seconds), or, in the case of Linux or if you have the fastboot / adb files on your computer, but it's not in the Windows path, just change directory in your terminal to the directory where the files are, then try the command again.
Once you have fastboot working, just copy whatever you want to flash to the same directory you're in, and the commands are:
Kernel -
Code:
fastboot flash boot [name of file].img
Recovery -
Code:
fastboot flash recovery [name of file].img
ROM -
Code:
fastboot flash system [name of file].img
OEM (needed for recent AOSP -based roms) -
Code:
fastboot flash oem [name of file].img
Curious - how did you flash Lineage last time?
Click to expand...
Click to collapse
If I remember correctly, I have flashed the LineageOS (and also stock ROM downloaded by XperiFirm) with Flashtool in "flashmode", but then when I got the logo bootloop, it didnt work anymore. Only fastboot works. Not even booting in recovery mode seems to work.
I have already tried with fastboot in windows 10 cmd prompt (now called PowerShell).
fastboot flash boot boot.img --> works OK
fastboot flash recovery twrp-3.3.1-0-kugo.img --> works OK
fastboot flash system [system file].img --> there's no other IMG file inside LineageOS zip file besides boot.img, if you could provide another custom ROM zip file which includes both boot.img and system.img, please let me know
in addition. after flashing recovery OK, I tried "fastboot boot recovery" and the phone boots into bootloop again.
after shutting it off, there's no way to get into recovery mode. Only sony logo and red light (or no light)
jayeffpee said:
If I remember correctly, I have flashed the LineageOS (and also stock ROM downloaded by XperiFirm) with Flashtool in "flashmode", but then when I got the logo bootloop, it didnt work anymore. Only fastboot works. Not even booting in recovery mode seems to work.
I have already tried with fastboot in windows 10 cmd prompt (now called PowerShell).
fastboot flash boot boot.img --> works OK
fastboot flash recovery twrp-3.3.1-0-kugo.img --> works OK
fastboot flash system [system file].img --> there's no other IMG file inside LineageOS zip file besides boot.img, if you could provide another custom ROM zip file which includes both boot.img and system.img, please let me know
in addition. after flashing recovery OK, I tried "fastboot boot recovery" and the phone boots into bootloop again.
after shutting it off, there's no way to get into recovery mode. Only sony logo and red light (or no light)
Click to expand...
Click to collapse
So you tried to hold power and volume down to get into recovery? Also, if the only file in the LOS zip is a boot img, then the zip is incomplete. Try one of the Omni roms from the roms thread here. I've used them for N, O, and P, and they all work fine. There's a link to the Sony OEM files in the first post...
levone1 said:
So you tried to hold power and volume down to get into recovery? Also, if the only file in the LOS zip is a boot img, then the zip is incomplete. Try one of the Omni roms from the roms thread here. I've used them for N, O, and P, and they all work fine. There's a link to the Sony OEM files in the first post...
Click to expand...
Click to collapse
Yes, I tried vol+down while power on, and it stuck in sony logo white screen. Also tried from fastboot mode with "fastboot boot recovery" and "fastboot boot twrp.img" and it says "rebooting" but it only disables fastboot mode (windows' typical unplug drive sound), but phone get stuck with blue light.
its really strange. Is it possible that the phone has a battery HW issue that avoids it to charge (sometimes the empty battery big icon black screen appears), and that issue avoids recovery or reboot process?
jayeffpee said:
Yes, I tried vol+down while power on, and it stuck in sony logo white screen. Also tried from fastboot mode with "fastboot boot recovery" and "fastboot boot twrp.img" and it says "rebooting" but it only disables fastboot mode (windows' typical unplug drive sound), but phone get stuck with blue light.
its really strange. Is it possible that the phone has a battery HW issue that avoids it to charge (sometimes the empty battery big icon black screen appears), and that issue avoids recovery or reboot process?
Click to expand...
Click to collapse
Maybe specific to battery, but any issue with the main board is going to caused general wackiness... Could be what's happening. Maybe it would be worth it to try a new battery. Have you already tried different cables?
levone1 said:
Maybe specific to battery, but any issue with the main board is going to caused general wackiness... Could be what's happening. Maybe it would be worth it to try a new battery. Have you already tried different cables?
Click to expand...
Click to collapse
yes, I have 2 USB 3.0 cables. Both works perfectly with my other phone Moto G6 plus, in fast charge mode. it I can flash anything in fastboot mode, but cannot reboot into recovery, do you have other option to try? I downloaded and flashed the Sony OEM file (8.1/9/10) and flashed with fastboot normally. Then I have downloaded the Omni WEEKLY zip file, but in the Omni XDA thread, it says that the zip file must be flashed from Recovery (copied into the SD card), but I cannot access Recovery. I really want to revive this phone.
jayeffpee said:
yes, I have 2 USB 3.0 cables. Both works perfectly with my other phone Moto G6 plus, in fast charge mode. it I can flash anything in fastboot mode, but cannot reboot into recovery, do you have other option to try? I downloaded and flashed the Sony OEM file (8.1/9/10) and flashed with fastboot normally. Then I have downloaded the Omni WEEKLY zip file, but in the Omni XDA thread, it says that the zip file must be flashed from Recovery (copied into the SD card), but I cannot access Recovery. I really want to revive this phone.
Click to expand...
Click to collapse
Oh right - I forgot about that... Try AOSP https://androidfilehost.com/?fid=1899786940962592899 Unzip it and there should be a system img in it...
PHP:
levone1 said:
Oh right - I forgot about that... Try AOSP https://androidfilehost.com/?fid=1899786940962592899 Unzip it and there should be a system img in it...
Click to expand...
Click to collapse
Thanks for the link! I have downloaded and flashed all the IMG files inside with fastboot, everything OK. But the phone is still not rebooting to system nor to recovery mode. same behaviour. Stuck in sony logo.
Related
hey anything please i wiped everything and installed zip"rom" from sd and installed secussful and then i clicked reboot and it just stays on the motorola screen with unlocked in the corner and is stuck there what am i not doing or doing wrong its rooted and unlocked
INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"
clod007 said:
INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"
Click to expand...
Click to collapse
i made a back up with titanium and android recovery....
i pulled the battery installed it 2 or 3 times and same thing
what exactly do i type in my cmd prompt on fastboot
If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"
clod007 said:
If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"
Click to expand...
Click to collapse
i dont know how to reinstall it but i made back ups of everything
Enter in Android recovery mod
Backup
Chose restore
Atrix - "CM7"
Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight
android-DEP said:
Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight
Click to expand...
Click to collapse
ok it rebooted and went off the screen now its in a boot loop and flashes the motorola sign then shuts down and keeps going
ok, so the issue was partly the cache not being wiped prior the rom being installed and something went wrong with the installation of the kernel. That happens if the boot.img didnt properly extract and write to partition or its just incompatible with the rom\device.
Visit faux123's thread with kernels for ATT froyo, GB, CM7 & CM9
download the kernel that's compatible for your rom(froyo, gb, cm7 or cm9). Once you download the zip, go in there and pull out the "boot.img" file and put it into the same folder you have fastboot.exe in and boot into fastboot again.
quickly check connectivity with "fastboot devices" to verify and if that checks out, use this command.
"fastboot flash boot boot.img"
it takes like 3 seconds or something to complete so its an easy fix, after its done just do the "fastboot reboot" command.
i had this same exact issue last week plus my recovery was being erased along with this problem so i keep boot.img & recovery.img just sitting inside the fastboot folder just in case
atrix reboot project - it has every single file thats for the atrix and copies of systems, roms, tools, recovery files, mods, tweaks
Try this:
Pull battery
Replace battery while holding volume down until you see fastboot
Tap volume down to until you see android recovery, then press volume up to enter recovery
First try wiping cache/dalvik, if that doesn't work restore nandroid backup, if that doesn't work reflash rom
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?
videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work
sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.
Stuck twrp says no os installed . But i did learn how to push files.
just trying to get back to stock now
videodave1 said:
just trying to get back to stock now
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
thanks everyone.
videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.
I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical
videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.
Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.
I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.
inwarse said:
I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.
Click to expand...
Click to collapse
You downloaded the KENZO (this is not oneplus2! ) TWRP and flashed it on another phone (oneplus2), just normal that it doesn't work and your phone is messed up.
If you can enter fastboot (vol up and power button to boot) you can rescue your phone:
-enter fastboot (vol up + power, while phone is completely off, u can also hold it until you can see "fastboot" written on the screen)
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
If something is not clear, use google, because this is most likely basic stuff you have to know when flashing your phone
I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?
inwarse said:
I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?
Click to expand...
Click to collapse
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
wertus33333 said:
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
Click to expand...
Click to collapse
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far
Oh, the link is dead, sry for that. try this one (GDrive links are up and working).
inwarse said:
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far
Click to expand...
Click to collapse
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Do you still have TWRP? If yes go to TWRP and shut down the phone there, afterwards you should be able to enter qualcomm mode again.
otherwise you have to try (i think 10s power button will shut the device completely down). You should be able to enter qualcomm mode if the device is fully shut off (your scenario sounds as if the device is not fully shut off when u connect it to the pc).
Just to go sure: You are absolutely sure to have a oneplus2, are you?
inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Could you resolve the issue?
wertus33333 said:
Could you resolve the issue?
Click to expand...
Click to collapse
nope. kept running into issue after issue, so got dejected and gave up.
Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
FrancescoPtr said:
Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Click to expand...
Click to collapse
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
ImmorTaLGiLL said:
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
Click to expand...
Click to collapse
I tried but didn't see it
Sadistic_Loser said:
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
Click to expand...
Click to collapse
ok but it does not go into fastboot mode or in recovery mode
FrancescoPtr said:
I tried but didn't see it
Click to expand...
Click to collapse
Make sure the device is off,Press volume up + volume down button then connect it to the computer.
If your device still doesn't show up,try pressing volume up+volume down+power button and then connect it.
This worked for me in many cases.
When I connect my phone via USB it shows up in the device manager as Qualcomm HS-USB.... But when I try using MSM it shows the phone connected on port 16 and I hit start and it fails after 16 seconds because it can't do a download. My question is is the download external via internet or is it a file in the MSM folder? I might be blocked by firewall at work if external.
EDIT: Looks like I found my issue. I couldn't tell if my phone was on or off since I had no display after trying about 20 more times I guess I got it ON.
Hey guys!
It's been a while since I've used my Mi A1. I turned it back on after a very long time and it was stuck on the android screen as if there was nothing to boot into so I tried booting into my recovery but there was nothing there either. I figured I probably formatted some stuff a while ago but I don't really remember what happened. Anyways, here's what I did next:
I could only boot into fastboot so I ran the command
Code:
fastboot boot path/to/tissot/twrp.img
but that didn't work.
So I flash the img to boot and tried rebooting to recovery but I was stuck on the android logo and again. I then again had to wait for my battery to run out before I could do anything else (I couldn't enter fastboot again. Only works when the phone is off for some reason)
I then erased the system partition using fastboot and tried booting into the recovery again but no luck. Can someone help me?
I know I messed up... big time. Someone save me
EDIT: Some more details
I tried two recoveries. The Pitch Black on XDA and also the standard "twrp-3.3.1-0-tissot.img" but had the same issue of getting stuck at the splash screen for both.
Also, I remember using Android 10 before all this happened.
EDIT 2: I ran the following commands:
Code:
fastboot set_active a
Code:
fastboot flash boot path/to/tissot/twrp.img
And I can now use the button combination to boot into recovery but I still get stuck on the splash screen
Hi,
have you fixed it? I face the same/similar issue, that I stuck at twrp splash screen after booting in twrp with fastboot
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I have erased/formatted everything (userdata, cache, boot) and also tried to reflash the original rom with mi flash tool, but without success.
Any ideas?
MBR might be creating problem , try clean install with mi flash tool with official ROM .
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
xiaomiA1 said:
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
Click to expand...
Click to collapse
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
MIN313 said:
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
Click to expand...
Click to collapse
If Phone Showing Charging Only and Can't Even Transfer Data , Not Detected on Pc then will have to do EDL flash
My phone is recognized by MiFlash when I enter the fastboot mode
It is also shown with
Code:
fastboot devices
and I can boot into TWRP, but it stucks in splash screen of twrp.
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I also tried older versions of twrp for tissot.
smilar issue, following attempts:
flashed with MiFlash, with or without EDL
flashed installing image with twrp
flashing after wiping dalwik, data, system and so on
flashed several type of ROM: official from xiaomi, crdroid, pixel, lineage
phone only booting with twrp (if installed) or stuck on mi logo