Hi there,
I am a newbie and hoping that someone could help to give me some clear pointers about options that i could take to rescue my phone - I hope its not bricked.
I was attempting to install LineageOS 16 on my Oppo R7s. This is my second attempt at installing a ROM - I did it a couple of weeks ago with Project Spectrum, and it worked, but Project Spectrum didn't impress me, so i wanted to try lineage OS instead).
I entered developer mode and enabled USB debugging
I downloaded the LineageOS zip to my SD card, as well as a Google Apps zip.
I downloaded the TWRP app on my phone just in case it was needed, however I've never used that app and not 100% sure how to use it.
I rebooted in recovery mode, and tried to install from the LineageOS zip file. It didn't start installing, I got some error message which I cannot recall... so I tried wiping the application data first, to see if that would help (maybe that was my mistake??)
I then went back to the install menu, and tried to install the Google Apps package first.... it started downloading, but then crashed and black screened.
Now, when I try to power on the phone, I get the oppo logo, and then it briefly goes back to the install screen for a second, with a message on the screen saying: "updating please wait, do not remove battery, do not co other operations" - but this only lasts for a second, then it crashes.
When I try to reboot into recovery mode (Power key +volume down), it does the same thing. I cannot get back to the white recovery menu.
Is there any way that I can rescue the situation and get back into recovery mode to try again? Or get back to a functioning USB connection so I can load a new ROM zip to try that instead?
When I plug it into the power, I get no indication that the phone is charging.
I'm worried the battery will go flat.
I have ADB installed on my computer, but I dont really know how to use it - the only command I know is "adb push" to load the roms onto the SD Card
Any advice on how to get access again would be greatly appreciated!
Related
I just downloaded and installed it and now my phone just resets back and again, i can't seem to turn it on. Tried installing the patch a few times, tried wiping catche, still the same bug, i reboot, the phone loads, suddenly there s a vib, screen goes black, then to android opo logo and to android logo, then it does the same thing again, constantly. I have no other patch to install (recently wiped them all because of lack of space, such thing has never happened to me before, but i should have left at least one =(( and i can't copy it to disc from my computer because i have no access while it's off on in recovery. I'm in deep **** now, that was like the worst moment ever for my phone to break down. Please HELP.
Did you took backup of yout last ROM ? .. If yes then flash it in recovery. If NO then use USBOTG .. Download 12.1 rom and copy it to pendrive from computer and connect to Phone and flash rom by selecting USB-OTG
sent from Bacon (OnePlus One)
just restore stock: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
cant i try flashing 6.0 gaps via fastboot mode? if yes what is the command
Can you boot into recovery mode if you press the power and vol down button at the same time? If you can you'll be able to see your phone through your computer.
The title says it all, but I explain calmly how it happened.
I was trying to want to install the official version of LineageOS for my Zenfone 2 and after downloading all the necessary files, have formatted and clean everything (except the SD), trying to install the new custom rom and then have the same "error 7". Then I realized immediately that lacked the Bootloader for Marshmellow, so I tried to look for a ZIP file for this, being able to find it right for my smartphone. The folder was known as "M_BL_upgrade_for_zf2_ze551ml_6.0" and once I had entered the USB cable to my PC and started the "Upgrade.bat" program, after the strangely reboot bootloader returned closed (it was understood from the screen, which instead to be white background with black writing was black with white lettering), then I tried to go back in recovery mode, realizing that every time I tried to get in, it was as if I were locked in a deadly circle and then kept restart and then return to where we started ... you have any idea how to do it, maybe re-add the Recovery Mode standard via CMD?
I've had a problem with my phone since flashing Lineage and Gapps in TWRP, something went wrong, it's acting like I have a corrupted version of Lineage with only the basic functions, Gapps is not installed and I've lost root.
The phone is an Xperia Z5, prior to flashing Lineage zip I had successfully rooted the phone, i flashed Lineage and then Gapps, an error appeared saying Gapps had not installed (possibly because it was the wrong version). After that the phone went into a bootloop (Sony logo, battery icon, then restart with red light in the corner). I was able to turn the phone on by holding down the power button for 5 seconds and lineage started up as normal with just the basic apps, I have been using the phone for the last month like this unable to find an answer on the forum. If I was able to connect the phone to PC i could use flashtool to flash the stock rom and start from scratch, but it only charges even though i have usb set to MTP in developer options, it's not detected by PC no matter how many cables I try. Also, it will not install apps from the Play website, it downloads and says app is installed but app isn't shown in list of apps. Can't get into TWRP because it says device is not rooted. When I switch phone off it restarts again and goes into bootloop, have to hold down power button to start it up. I wondered if anyone was familiar with these strange symptoms and knew if there was any way out? My phones stuck in limbo until I can find a way of doing a hard reset but without being able to get into TWRP or connect phone to PC I'm stuck.
Please help!!
I decided I didn't want the lineage os I flashed a couple of months ago and wanted to go back to my old Lenovo os which I had a nandroid backup of ( my phone is a Lenovo k5). I opened twrp recovery and started the restoration proccess. However, Halfway through the proccess I get an error message that said *error:extracttarfork()proccess ended with error=255*.
This made my nervous and Instead of pressing the back option I pressed the reboot system, which is obviously wrong since the system wasn't fully Installed and the old one was deleted as part of the reboot process. So now I am stuck at the screen that says "lenovo" on it and the phone doesn't go any further. I can't open twrp recovery using the key combination ever since I flashed lineage and I can't boot into bootloader. Any computer that I connect to the phone won't be of any use since the phone won't be visible to the computer. Please tell me if you have any idea how to access the recovery page or how to make th key combination work again, or if you have another solution to solve this problem.
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
rraphrr said:
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
Click to expand...
Click to collapse
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
muhammad42620 said:
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
Click to expand...
Click to collapse
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
rraphrr said:
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
Click to expand...
Click to collapse
These phones get emmc errors. Common issue with this device