[Q] OPO Softbrick! How to solve (get back to stock)? - ONE Q&A, Help & Troubleshooting

I've got problems updating my OPO CM updating and after searching for a solve I've found this Thread
forum.cyanogenmod.org/topic/89400-ota-update-failing-to-install-seeing-status-7-errors-while-applying-an-update-read/
So I followed the steps
I've installed the newest TWRP and made a backup
After deciding to flash OxygenOS ('cause I wanted to try that one out) I downloaded it from oneplus.net
I flashed the OxygenOS and got a softbrick
(I did not wipe)
I can boot normally, but I will get a black screen (after the boot animation) overlaying some sort of form I should fill out, but I can´t interact with it
I can also see the status, showing me my battery status and time
I can also boot into fastboot, but am troubeling booting into recovery to restore that backup
My PC (win 7) detects that I'm plugging in my phone, but I'm not able to access the files
I have the "cm-12.1-20150505-NIGHTLY-bacon" on the phone (same dir as the oxygenOS)
As TWRP I used "twrp-2.8.6.0-bacon"
So how can I fix this?
How can I restore that backup file?
I've searched for an solution, but did not find anything which seemed to fit my case or asured me that it´ll work for me
Could that solve my problem?
forums.oneplus.net/threads/has-anyone-tried-downgrading-from-oxygen-os-to-cm11s.290671/#post-10672763
Also I don´t want to use this tool, ´cause I read a lot of thread telling me that flashing from OxygenOS to CM back will cause a hardbrick
It also won´t detect my phone ...
forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Thanks in advance!

Flash the stock images using fastboot, see section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
It's safe as long as you don't perform any reboots between any of the commands.
Transmitted via Bacon

Thanks a lot! But got another question ...
Thanks! I was able to flash to an working CM ^^
saved my Day
Now I´ve got the CM version "12.0-YNG1TAS0YL"
CM says that there is an update ("YNG1TAS17L") and downloads it
After hitting the "install" button I see a little loading Animation with the name of the new vesion, but nothing happens
The loading Animation goes away, but the phone does not reboot
I the rebooted it, but still got the old version (and the notification about updating)
It´s like the problem which made me decide to flash to an update (but then I decided to use OxygenOS ... not again ...)
Any ideas of solving this problem?
Or shall I just download the newest CM version for Bacon and flash it?

Related

[Q] Acer Iconia Tab A700 Bootloop HELP!!

Ok so today CyanogenMod released the m10 snapshot version for the A700 and before installing it, i decided to factory reset my tablet from CWM and then install the new version.
My tablet did run the cyanogenmod intro start up like all new devices but I found out that my music, videos, pictures, etc were still there even though I formatted from recovery. SO, I decided to factory reset from the settings, tablet reboots, won't start up! I've come to the conclusion that I might have reset my tablet to stock firmware even though there isn't any installed. I can open recovery but can't do anything other than scroll through the menus. Whenever I confirm an action the tablet bootloops. I think I can solve this by re-flashing the new rom but whenever I go to install zip the tablet reboots into a bootloop. Is there anyway to install the rom without recovery? Like using command prompt? And if that's not the case then could you help me solve this issue?
Many thanks to anyone who can help me out
SOLVED: After spending 7 non-stop hours on command prompt typing in fastboot and adb commands, managed to somehow luckily figure it out. I can't really explain how I did it but I did it
AusomBabs said:
Ok so today CyanogenMod released the m10 snapshot version for the A700 and before installing it, i decided to factory reset my tablet from CWM and then install the new version.
My tablet did run the cyanogenmod intro start up like all new devices but I found out that my music, videos, pictures, etc were still there even though I formatted from recovery. SO, I decided to factory reset from the settings, tablet reboots, won't start up! I've come to the conclusion that I might have reset my tablet to stock firmware even though there isn't any installed. I can open recovery but can't do anything other than scroll through the menus. Whenever I confirm an action the tablet bootloops. I think I can solve this by re-flashing the new rom but whenever I go to install zip the tablet reboots into a bootloop. Is there anyway to install the rom without recovery? Like using command prompt? And if that's not the case then could you help me solve this issue?
Many thanks to anyone who can help me out
SOLVED: After spending 7 non-stop hours on command prompt typing in fastboot and adb commands, managed to somehow luckily figure it out. I can't really explain how I did it but I did it
Click to expand...
Click to collapse
Good Job if You Could Explain For Latest Problem Solved. I Think this is the problem from cwm or maybe the latest rom of cwm snapshot, need to investigate for problem occured. before this update we never have this problem. "When Reset Factory Default within Setting than it will always bootlop". My a701 have this problem too. looks like @Flupkes Problem too, the different is i Reset it From Snapshot M7 this my old thread and could make the adb working because the usb slot problem.

Phone won't boot to OS anymore.

I went to bed last night, did what I normally do, set my alarm and turned on sleep tracking. I woke up this morning to find that my phone had booted back into TWRP. I rebooted and found that after the LG screen it goes directly into TWRP which had replaced factory reset using bump. I tried to restore the phone using a saved backup and that didn't work. I tried to wipe it then restore and that didn't work. I am afraid that my phone is a lost cause and that I cannot get a replacement due to it booting to the TWRP screen every time it is turned on. The phone had been working fine for the past week since I had installed TWRP. Does anyone have any suggestions on what to do or what might have caused this?
Look in the lg g3 international forum there is a fix there your phone tried to flash a ota update
jerrycoffman45 said:
Look in the lg g3 international forum there is a fix there your phone tried to flash a ota update
Click to expand...
Click to collapse
Sounds awesome thanks.
All the times that I tried to it to flash a ROM itself it doesn't do it but it does it by itself.
Here is a link http://forum.xda-developers.com/showthread.php?t=2908290 after you fix it freeze software update with titanium backup
I cannot get the first step to work. ADB cannot see the device. I tried installing the Google USB Driver but that didn't work and TWRP ADB sideload doesn't work either.
EDIT: I put the zip on my phone using MTP and flashed it using TWRP but it still stuck booting into TWRP.
EDIT 2: Tried one more time again after flashing my backup ROM. Now it loads.
I can't help more on a road trip sorry
Try this, worked for me
Go to this website and do what ot says. http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=57453756 this should fix it. I had the same issue and this worked :good: sorry if im late.

Unable to recover my OPO

Hi all,
well, to be honnest I already posted my story in the help thread but no answer came so I try with a new thread
We'll see if I'm luckier this way !
a few weeks ago I broke my screen and decided to change it myself.
Everything went fine (even restarted successfully my phone before applying the tape to fix the screen) until I finally tried to restart my phone after the repair is done.
Since then I'm not able to turn on my phone
Holding the power button starts fastboot mode, UP + power doesn't do anything and DOWN + power enters recovery. Weird !
Another weird thing: it only works if I'm not plugged. When I'm plugged nothing ever happens.
I suspected I could have damaged buttons or cables. I have looked carefully but nothing appears to be broken.
Here is what I already did without any result:
- I had access to the original recovery so wiped the cache
- I tried to recover the phone but that did not work so
- I installed twrk using adb (like here)
- and then installed the rom as explained here (I used the last release here, so it should be cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-bacon.zip). It seemed to work but finally no, same situtation
- I tried this but so far not able to get the qualcomm port listed once the phone is on. It may be related to the fact that I have to unplug to boot it but I always got a Android bootloader interface listed.
Any idea someone ?
Thank you very much for your help !
Did you try to "fastboot reboot" while in fastboot mode?
Try flashing a CM14 rom. Mine came with CM12 so I tried flashing back to CM11 and I did flash it successfully through Fastboot but alas it won't boot. The boot logo loads but then I'm introduced to a black screen.. So I flashed back to a (at that time the latest stable) CM12.1 but same result. And I got worried. Then I decided to flash a CM13 rom which was a beta build (at that time newly released Android 6) and it booted into it alright! So I suggest flashing a CM14 and let me know how it does.
The problem seems be much deeper than just a broken screen. It may sometime affect the chipset of the cellphone.
For that we can't do anything.
For now you can try the following things :
1 . Flash the latest Cyanogen Firmware from the same place you have downloaded the snapshot cm13.
2. Flash recovery (TWRP) using adb.
3. Wipe
-System
-Data
-Cache and Dalvik Cache
4. Flash the latest Cyanogen Rom .
5. Boot into recovery.
6. Flash some gapps as per the Android version.( Open Gapps I recommend)
7. Boot back to recovery .
8. Boot into System.
This is the max you can do for now.
You can also check device forums for recovering from a bricked device post.
Go through the post and check if any symptoms matches yours. You'll find the answer right away.
And the last option you can do is going to service center, they will charge you mostly (even if in warranty as you have yourself tampered hardware of the phone.)
Hope it will help. Thanks

[Need Help] Flash 7.0 Nougat FIrmware on a SM-J710FN (8.1 to 7.0)

Hello everyone,
This is my first post on this forum, sorry in advance if the format is not correct.
Here's my problem: I was given a SM-J710FN that displayed an overheating problem on the screen while the phone was not heating at all, as well as buttons at the bottom of the phone were not working anymore.
I reset the device to factory default, erased the data from the recovery mode and flashed the 8.1 Oreo version with a ROM STOCK J710FXXU6CSK1
After all these manipulations, the buttons still did not work and the overheating message still appeared, preventing the phone from being charged even when it was switched off.
So I thought of programmed obsolescence, and thought it was worth trying to downgrade the phone to 7.0 from version 8.1.
Could you help me on this subject and tell me what you think?
Sorry for the up
try flash a custom rom, it does not need buttons, like this https://www.google.com/url?sa=t&source=web&rct=j&url=https://m.youtube.com/watch?v=veWLleEULe4&ved=2ahUKEwigx7TjmoTvAhVUIIgKHWbJCjIQ28sGMAJ6BAgFEBc&usg=AOvVaw3xJ6phS4kotjx4fk6Ypfuq
home button work or not
Thank you for the answer, I really appreciate it
Here is the update since I followed the Youtube link you sent me:
I have transferred the Custom ROM (Pixel-AB-11-20200909-ErfanGSI.img-0125.7z) as well as H-VENDOR_V1.0.zip to the mobile phone via a USB cable plugged to my PC in the root of the phone in order to proceed to its installation.
I then used Odin to flash Orange Fox (also TWRP on other attempts) with AP, but when I get to the Orange Fox recovery screen, the .zip files do not appear in the files. When searching on the Internet, it is advisable to flash via Fastboot, but despite several attempts, I cannot detect the phone with Fastboot, but only ADB. Even the manipulation saying to install the drivers manually from the device manager doesn't work because a message saying that the file to be used doesn't contain a driver is displayed. (android_winusb.inf)
And I also notice that after having flash TWRP or Orange Fox, the phone can no longer boot on the system.
Have you got any advices?
I continued my tests on my side, I was able to better understand how TWRP and Orange Fox work, in fact to make it usable, you first have to FORMAT the /data (not swipe), so, make TWRP / Orange Fox operational.
I was then blocked during the installation of the personalized ROM with the error of the /vendor, following my research, it would be necessary to install a .zip dedicated to that (Mokee from what I saw)
But I did something I shouldn't have done, and I flashed the zip "twrp-3.2.1-0-20180414-codeworkx-dumpling" from the Orange Fox recovery, and since then, the phone is stuck at startup, and when I try to access Download Mode, I get stuck at the Warning Message because my volume buttons don't react.
Is it possible to do something about it or the phone will be forever bricked?
up

Hoping someone can help rescue my phone.( Moto G5)

Hi everyone last night i decided to root my ohone. I have had it for a while but for some reason hadn't got round to doing it.
I followed all the instructions firstly unlocking bootloader, TWRP then installing no verity and magisk etc and every looked to be good phone starts up with the the your device has been unlocked message and something about bad id key but then would start like normal and set about installing all my apps etc again for the phone to be back to how it was just rooted.
However tonight i restarted my phone and when it's went to start up it throws me into the fast loader screen wtih your device didnt stat up successfully use the software repair assistant on computer to repair your device.
I had only been installing my usual apps/ new luancher etc... however the only thing i think that could have caused an issue was i checked for an android version update and it found i already had the most up to date one so nothing was downloaded but possibly just checking has caused an issue ?
Any help with this would be appreciated.
I can still boot into team win recovery mode but was hoping as i've now installed everything a new... i could resolve this without another fresh install if possible ?
Thanks
fendertele said:
Hi everyone last night i decided to root my ohone. I have had it for a while but for some reason hadn't got round to doing it.
I followed all the instructions firstly unlocking bootloader, TWRP then installing no verity and magisk etc and every looked to be good phone starts up with the the your device has been unlocked message and something about bad id key but then would start like normal and set about installing all my apps etc again for the phone to be back to how it was just rooted.
However tonight i restarted my phone and when it's went to start up it throws me into the fast loader screen wtih your device didnt stat up successfully use the software repair assistant on computer to repair your device.
I had only been installing my usual apps/ new luancher etc... however the only thing i think that could have caused an issue was i checked for an android version update and it found i already had the most up to date one so nothing was downloaded but possibly just checking has caused an issue ?
Any help with this would be appreciated.
I can still boot into team win recovery mode but was hoping as i've now installed everything a new... i could resolve this without another fresh install if possible ?
Thanks
Click to expand...
Click to collapse
You could try reflashing the boot.img
What does getvar all say?
Code:
fastboot getvar all

Categories

Resources