I switched from dotOS to Pixel Experience because I wanted to get a taste of A12. After the change my phone started behaving strangely. It doesn't turn up on Windows File Explorer anymore and ADB doesn't detect my phone unless I set it to USB charge only. Plus the biggest problem of them all- TWRP doesn't work anymore. Whenever I reboot my phone it boots into TWRP, and the screen keeps flashing at the TWRP logo. The only way to boot to A12 is to enter fastboot and hit fastboot continue in the CMD. I'm at my wits end here and honestly a bit desperate. I have attached the logs from when the TWRP screen kept flashing. I wiped my device completely before installing Pixel Experience and I think that may be the problem. I fear that I may have sort of permanently damaged my phone or something. Any help would be appreciated. Thank you.
Pixel Experience A12 has it's own recovery u need to use that twrp or orangefox won't work on that rom same as los has it's own recovery
Related
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Namanpuri80 said:
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Search for the Hard Bricked thread by Naman Bhalla and use it. The links in it may point to older versions, so find out if any later versions are available.
Namanpuri80 said:
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
If pc detects phone try /adb devices ,if it detects phone, go like this: /adb reboot bootloader then it should reboot into fastboot. If so try fastboot flash recovery "yourrecovery.img" (I suggest stock recovery of oos you had before brick). The next step, if you boot into recovery is to adb sideload stock oos. Command for that is /adb sideload "youroosfile.zip"
You need to use Msmdownloadtool to go back to stock because you are stuck in EDL(qualcomm emergency download mode), check Mega unbrick guide and use method 2 to go back to stock, and i guarantee it will work 100%.
ach3fck said:
You need to use Msmdownloadtool to go back to stock because you are stuck in EDL(qualcomm emergency download mode), check Mega unbrick guide and use method 2 to go back to stock, and i guarantee it will work 100%.
Click to expand...
Click to collapse
That's right I even recover a CB8 dead OP3
toolkit
try oneplus 3 toolkit
Try the Unbrick tool, everything that is bricked can be solved...
So my phone has been this way since Nov 2017, there are files that I need access to and would truly appreciate some guidance
I was experiencing issues with the bluetooth on nextbit previously so I installed a new rom after flashing the device. Once the rom also gave issues I decided to revert back to the Nextbit 7 OS and one fine day when the phone restarted it wouldnt go past the "nextbit" splash screen. Tried installing the OS again however the PC wouldnt recognize the phone anymore, switched laptop to a Mac and got the same issue
Any help would be greatly appreciated
It wont let me post a URL link. I have taken www out hopefully it allows to view the video, shows exactly whats wrong
youtube.com/watch?v=ImIk5CErWf0
It looks there's something wrong with the system boot, since it's reaching the blue boot-animation and it stays there (probably before loading the adb stuff). Fortunately u did unlock the bootloader and that annoying initial screen may be helpful this time, did u try to reach recovery or fastboot mode from there (pressing some volume key)? It's pretty hard for it to be broken there too and in such a case I would think about some hardware fault. Anyway from the recovery (I hope u have TWRP, if not install it with fastboot) you should be able to do whatever u want, including recovering your files or (re)installing a rom
Just as the title says, I'm having trouble trying to boot TWRP via adb.
As a quick overview, this phone arrived with an unlocked bootloader from the seller I bought it from at AliExpress. Because of that, I decided to flash Pixel Experience 8.0. I remember back then that it gave me a few issues as well when it came to trying to boot TWRP via adb but somehow managed to do so.
Ultimately, I was able to run the rom without a problem and it was smooth sailing from there. Fast forward to now, I thought it was time that I updated to PE 9. Again, I'm having issues trying to do the same thing. If you're wondering why I don't have TWRP installed, it's because I didn't want to root my phone
due to issues that's connected to Fate Grand Order. I remained unrooted, which meant that I had stock recovery.
My biggest problem is the (Command Write Failed [Invalid Argument]) text when trying to boot TWRP. If it's not that, then it's stuck at "Waiting for device." Both situations lead to "Press any key to shutdown" at the top left corner of the fastboot screen.
Any thoughts?
1. try different port/cable , as some times windows can't talk to device
2. try OrangeFox 8.3-2
3. also flash recovery (native) orange fox 8.3-2
YasuHamed said:
1. try different port/cable , as some times windows can't talk to device
2. try OrangeFox 8.3-2
3. also flash recovery (native) orange fox 8.3-2
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after work.
Hi Everyone,
I would gladly accept any help that is being offered. Thanks in Advance.
So I am not new to flashing my phones but Xiaomi has been one of the most frustrating experiences that I've ever had. So I flashed my phone with the Pixel Experience Rom but I wasn't getting 4G with it and I couldn't recall if I was getting 4G with the original MUI so i decided to flash MUI firmware .
So, Not really sure what I did wrong because i believe I could flash the firmware without any problems but guess not. So it flashed successfully and my phone rebooted into Fastboot and will not load into the phone. So booted into recovery and Red Wolf TWRP is asking for the encryption password which I normally enter and I do it again and behold it's telling me that the password is wrong which is am sure it isn't.
So I am unable to use Red Wolf TWRP to flash anything since i can't mount the storage section because of the encryption and tried flashing the phone with MiFlash but doesn't seem to work. It is telling me that the image and device is a mismatch which I don't believe since I've flashed those ROMS before.
So any helpful advice would be appreciated.
I guess you need to flash stock firmware in fastboot mode. Download fastboot rom from mi website. Power on your phone while pressing volume down keep pressing power button for some seconds to enter fastboot mode. Connect it with your pc and upon connection you will heard plugin sound from pc. Extract downloaded fastboot image and double click on flashall. Wait for process to complete. Your device will auto reboot upon completion
Sent from my LINQ X70 using Tapatalk
bcat00 said:
Hi Everyone,
I would gladly accept any help that is being offered. Thanks in Advance.
So I am not new to flashing my phones but Xiaomi has been one of the most frustrating experiences that I've ever had. So I flashed my phone with the Pixel Experience Rom but I wasn't getting 4G with it and I couldn't recall if I was getting 4G with the original MUI so i decided to flash MUI firmware .
So, Not really sure what I did wrong because i believe I could flash the firmware without any problems but guess not. So it flashed successfully and my phone rebooted into Fastboot and will not load into the phone. So booted into recovery and Red Wolf TWRP is asking for the encryption password which I normally enter and I do it again and behold it's telling me that the password is wrong which is am sure it isn't.
So I am unable to use Red Wolf TWRP to flash anything since i can't mount the storage section because of the encryption and tried flashing the phone with MiFlash but doesn't seem to work. It is telling me that the image and device is a mismatch which I don't believe since I've flashed those ROMS before.
So any helpful advice would be appreciated.
Click to expand...
Click to collapse
So just format storage, it will be no longer encrypted. Then mount storage in twrp, paste your rom of choice from pc and flash it. Unless im missing something here
A mismatch you say? hmm I have had this before and I managed to flash the rom without issues deleting some lines in a rom package. It's quite simple, just follow this little tutorial: http://en.miui.com/thread-178314-1-1.html
Thanks for the responses. I followed this guide here to resolve the issue.
https://forum.xda-developers.com/re...-to-unbrick-redmi-note-5-pro-bricked-t3840455
I was trying to flash vanilla AOSP GSI and everything was going as expected.
After that, I flashed "disable force encryption" and the fingerprint gestures files among with magisk and pico gapps and the phone started rebooting after a single freeze of 2 or 3 seconds right after the initial boot.
Actually I made several tries with different combinations trying to figure out what was causing that behaviour and I noticed that it used to happen patching "fstab.qcom" file in "/vendor/etc" path as stated in this guide, always keeping a backup of the original "fstab.qcom".
At some point my device started rebooting even after restoring the old "fstab.qcom" so I flashed the stock rom via fastboot but it didn't solve the problem, then I also tried to flash in edl mode (enabled with "fastboot oem edl") but no way, the phone keeps rebooting without letting me finish even the initial setup.
I can access fastboot, edl and recovery. I can also flash TWRP but I can't turn off the phone.
I don't know what else to do, please help me
Sorry for me being a big noob and for my unclear english.