Problems to install stock rom (Lenovo vibe K5 Plus) - Lenovo Vibe K5 Plus Questions & Answers

Hello everyone! I hope you're doing well. I'm new here and I'm facing a problem that I can't seem to solve, so I'm here to ask for your help.
CONTEXT: My girlfriend had a phone whose screen broke. She couldn't afford to buy a new one, and neither could I help financially. But I had two old devices: a Motorola G1 (which I used to store some things and do simple tasks) and a Lenovo Vibe K5 Plus, which was the one I was using. Since I had just graduated from college and she hadn't, she had a greater need than me for a slightly better phone. So I gave her my Lenovo and I'm using the Motorola. When the Lenovo was still with me, I had put a custom ROM on it from Lineage (I think it was Android Nougat, if I'm not mistaken) and it also had TWRP. Before giving it to her, I only did a quick format of the phone.
A few days ago, there was a problem with the Lenovo and Android no longer worked. The phone turned on, entered the Lineage boot screen, but when it tried to turn on Android, a message appeared saying that Google's text-to-speech had continuously failed, and the phone turned off. She brought it to me yesterday and I thought about installing the original stock ROM on the device. With difficulty, I managed to get the laptop (Windows 10) to recognize the phone when it turned on. The difficulty was because when I tried to turn it on, the screen kept flashing on the Lenovo. I opened the device, took out the battery, waited for a while, and miraculously managed to turn it on. When it turned on, the laptop installed the device before it turned off. Through ADB, I managed to get the device to reboot directly to recovery, since I couldn't access recovery through the physical buttons on the device.
So, I managed to make a backup of the files that were important to my girlfriend and that were on the phone's internal memory. After that, I formatted the device through TWRP using the "format data" button. Still, I used the wipe to erase everything except for "USB-OTG" and the memory card option (which I had removed along with the SIM card before trying the procedure). After that, I restarted the phone to enter TWRP directly.
PROBLEM: After doing this, I tried to install the stock ROM using ADB sideload, but it said there was something wrong with the image I was using. The sideload gave an error message and said that the phone needed to be restarted. I restarted it from this screen by sliding my finger to the right, and... the phone no longer turned on and wasn't recognized by the laptop! I can't access TWRP through the physical buttons (at least not through the traditional method I know, which is the volume up button and the power button), ADB doesn't recognize the phone, and I don't know what else to try.
QUESTION(S): How can I force the laptop to recognize the device so that I can make it reboot directly to TWRP, since the device doesn't turn on for long enough for Windows to try to check the drivers? Or has TWRP been corrupted? If so, how can I install TWRP again? Is there any other way to access recovery? Is there any other way I can use to install the stock ROM? We can't afford to take it for repair at this time (the situation here in Brazil is very bad), much less afford to buy a new device. Does anyone have any other ideas on how I can access recovery or how I can install a ROM without necessarily turning on the device? Or any other ideas?
I really appreciate anyone who read this far and, in advance, I thank anyone who can help me. Gratitude!

Related

Please HELP: Startrek stuck in "upgrade mode"

Hi,
I was wondering if there is a way to convert my Startrek/Qtek8500 back from paper weight into a working cell phone.
After years of flashing devices it went wrong this time.
I successfully unlocked the phone and could replace the Vodafonerom with the Qtek-rom 3.6.251.0_02.67.30. But I also wanted to try out the Cingular rom 4_1_.1.502.4_02.79.30_CWS.
I hoped to find the PAN-Bluetooth-Profile in it.
However, this did not work.
The phone is stuck in the three-colour-upgrade/flash-screen since then.
Hard reset (holding the two softkeys and then turning the phone on) does not work. If I plug in the USB cord, the display shows "USB" in the left bottom but the phone is not recognized by ActiveSync.
I know there is a way to flash the phone via microsd-card, but I do not know the details about this method.
I have unpacked a RUU_xxxxx.exe file with Universal Extractor and copied the resulting files to a FAT-formatted 2GB MicroSC card. However, the card is not discovered during startup, the phone goes into the "upgrade mode".
Do you have any ideas? Any help is appreciated!
Many thanks in advance!

[Q] Help! Accidentally deleted system and can't restore or install

Coming from a phone with microSD extension, I had never encountered such an issue:
I bought this phone with a stock 4.2 Rom installed and tried to install a custom Rom. I first installed the latest version of touch recovery (tried it and it seemed to work fine) and did a backup using the default settings. Then I erroneously chose to format system and data, thinking that I could then "install from zip". Strangely, these steps deleted everything in the /sdcard directory and I couldnt select "external SD" (because the phone isnt equipped with it anyways?). Then I made a second mistake and restarted the phone, despite the message warning that I no longer had an OS installed. I took the battery out, and then held the power down while pressing the power button. The phone couldn't get into recovery, but instead showed a screen with the android logo, a large "Start" sign above it, and "Downloading...", "Do not turn off target !!" below it. Pressing the power button now got the phone to show just "Google" and a lock logo under it. The PC (windows 7) can not detect the phone throughout the process.
I tried the latest tool kit and samsung's USB driver but couldnt get the phone recognized by the PC.
Does this mean that the phone is doomed???
Please help!!!
Trent
Relax, it's not easy to 'doom' your Nexus. Especially with all the hard-workers in XDA
Try accessing Recovery mode by holding down BOTH vol up + vol down, as well as power. Holding just vol down + power is 'Download Mode', and at the least you can get to this. Means your phones far from doomed
Thanks a lot for the reply!
As a matter of fact, I also figured out how to get back to recovery (if only I had read your post earlier, my pain would've been much less!). But the problem remains that I can not get a target ROM onto the phone, since: 1. whatever I did seemed to have gotten rid of the nand backup supposedly stored in /data/media/TWRP/BACKUPS/ (I'm using TWRP V. 2.3.2.1). 2. I can not get my PC(or Mac, for that matter) to recognize the phone or the internal storage.
Any pointer from here?
Thanks again!!!
Trent
You can download a factory image and install with fastboot. It's quite easy and instructions are readily available on this forum. You can then install a custom ROM afterwards if stock is not your thing.
Found the answer finally!
It's the adb push method. Basically, it's to install adb drivers and execute a few commands via the command window. Not too bad... Don't know much about fastboot yet though ... If anyone else needs more details, please PM me (to save public bandwidth).
Thanks a lot anyways, whpnhp and jocalderone!!!
Trent

OPPO Keyboard has stopped working, leading me to stuck on a fastboot loop.

Please help. This is a serious matter for me.
Started having this problem at February 14th, 02.10 AM.
Have been looking for the answers in the Oppo Forums too but still got no answers.
Okay, I have a habit, which is moving all of my applications from my internal storage to my external SD card, after I let those applications doing their functions and programs and features and so on for a while. It's not a big deal for me to set up my phone again after I restarted it, and usually it works perfectly. Just restart and I would get to operate my phone again. However, this time, I got a bad luck. The worst one, considering the fact that I'm all-around-gadget.
Here's the results I got from reading a lot of threads (not only from this forum and OPPO forums):
OPPO Swype Keyboard has stopped working? Really?
After restarting my un-rooted Find 7 (9076), I cannot type the password on my lock screen. Like any other Android devices, it would always come back to it's system or default applications, I knew that fact. But this time, when I touched the blank space to type my password, nothing came out. No OPPO Keyboard, which happened to be OPPO's default keyboard. No other keyboards. None at all.
So, I cannot do one single thing to my phone except just turn it on and stared at it like a complete idiot.
Then I decided to turn my phone off and turn it on again after a while.
But still, the same thing happened. No keyboards.
That time, I decided to turn off my phone again and pulled out the battery and my external SD card.
After putting the battery back (External SD Card was still outside), and turned it on again, the same thing still happened.
Sliding my fingers up and down, nothing happened. The touchscreen was still there, showing me my date and time even though I was sliding my fingertips up and down.
Not too long after, I felt my phone got warmer and warmer. I tried double-clicking the home button, which I already set to unlock the lock screen, was also useless. The screen was still black and locked. When it got over-heating, automatically I pulled out the battery without even turning off the phone.
That one was my fault. I knew, and well, honestly speaking, this is the first time I'm in this kind of situation. In the past, my Find 7 would just suddenly restarted itself then everything went back to normal, but not this time.
And here's the beginning of my Fastboot Loop.
Fastboot Loop on un-rooted device
After pressing the Power button and the Volume Up button at the same time, it would bring you to the Recovery Mode. When I did that to my Find 7, it brought me to a black backgrounded screen with cute OPPO mascot and some Hanzi (Chinese handwritings). Picture attached.
I tried to wait for 2-3 hours and found nothing happened.
Pulling the batter out and putting the batter back would do the same.
In other words, I am not able to gain access to my Recovery Mode.
Why didn't bring the phone to the service centre?
I thought about this already.
When I tried to connect my phone to my pc, it can detect the phone but cannot access the files because the phone was still locked with the password.
Usually, the service centre requires us to unlock the phone if there's a problem with it, right? In my cases, yes.
I was searching all night to find out the answers.
I found some threads about the Fastboot Loop thing and etc, but they are only for rooted devices.
I'm using:
OPPO Find 7 (9076)
Color OS 2.0.5i Beta
Android KitKat 4.4.2
Device is not rooted, still original.
Still dealing with the same problem until now (the time I post this thread).
Anyone has solved this problem and guide me step by step to finish this?
daiichi said:
Please help. This is a serious matter for me.
Started having this problem at February 14th, 02.10 AM.
Have been looking for the answers in the Oppo Forums too but still got no answers.
Okay, I have a habit, which is moving all of my applications from my internal storage to my external SD card, after I let those applications doing their functions and programs and features and so on for a while. It's not a big deal for me to set up my phone again after I restarted it, and usually it works perfectly. Just restart and I would get to operate my phone again. However, this time, I got a bad luck. The worst one, considering the fact that I'm all-around-gadget.
Here's the results I got from reading a lot of threads (not only from this forum and OPPO forums):
OPPO Swype Keyboard has stopped working? Really?
After restarting my un-rooted Find 7 (9076), I cannot type the password on my lock screen. Like any other Android devices, it would always come back to it's system or default applications, I knew that fact. But this time, when I touched the blank space to type my password, nothing came out. No OPPO Keyboard, which happened to be OPPO's default keyboard. No other keyboards. None at all.
So, I cannot do one single thing to my phone except just turn it on and stared at it like a complete idiot.
Then I decided to turn my phone off and turn it on again after a while.
But still, the same thing happened. No keyboards.
That time, I decided to turn off my phone again and pulled out the battery and my external SD card.
After putting the battery back (External SD Card was still outside), and turned it on again, the same thing still happened.
Sliding my fingers up and down, nothing happened. The touchscreen was still there, showing me my date and time even though I was sliding my fingertips up and down.
Not too long after, I felt my phone got warmer and warmer. I tried double-clicking the home button, which I already set to unlock the lock screen, was also useless. The screen was still black and locked. When it got over-heating, automatically I pulled out the battery without even turning off the phone.
That one was my fault. I knew, and well, honestly speaking, this is the first time I'm in this kind of situation. In the past, my Find 7 would just suddenly restarted itself then everything went back to normal, but not this time.
And here's the beginning of my Fastboot Loop.
Fastboot Loop on un-rooted device
After pressing the Power button and the Volume Up button at the same time, it would bring you to the Recovery Mode. When I did that to my Find 7, it brought me to a black backgrounded screen with cute OPPO mascot and some Hanzi (Chinese handwritings). Picture attached.
I tried to wait for 2-3 hours and found nothing happened.
Pulling the batter out and putting the batter back would do the same.
In other words, I am not able to gain access to my Recovery Mode.
Why didn't bring the phone to the service centre?
I thought about this already.
When I tried to connect my phone to my pc, it can detect the phone but cannot access the files because the phone was still locked with the password.
Usually, the service centre requires us to unlock the phone if there's a problem with it, right? In my cases, yes.
I was searching all night to find out the answers.
I found some threads about the Fastboot Loop thing and etc, but they are only for rooted devices.
I'm using:
OPPO Find 7 (9076)
Color OS 2.0.5i Beta
Android KitKat 4.4.2
Device is not rooted, still original.
Still dealing with the same problem until now (the time I post this thread).
Anyone has solved this problem and guide me step by step to finish this?
Click to expand...
Click to collapse
boot into recovery and format the phone, this should fix it. If you want to backup your data, just boot into fastboot, connect phone to pc, run fastboot command from sdk tool, push custom recovery, flash twrp, make nandroid backup, fomat phone along with all the storage and then flash oppo stock rom (you need to download) or any other custom rom with gapps. To restore use nandroid manager, do not restore system files if you are flashing custom rom.
treacherous_hawk said:
boot into recovery and format the phone, this should fix it. If you want to backup your data, just boot into fastboot, connect phone to pc, run fastboot command from sdk tool, push custom recovery, flash twrp, make nandroid backup, fomat phone along with all the storage and then flash oppo stock rom (you need to download) or any other custom rom with gapps. To restore use nandroid manager, do not restore system files if you are flashing custom rom.
Click to expand...
Click to collapse
Thank you for your help Sir.
But, my Find 7 already operated normally again since I left it for a few days uncharged and off.
Then I got into Recovery Mode by pressing Power button and Volume Down button (not Volume Up button) while in the middle of my fast-boot loop.
It worked. I could gain access to ColorOS Recovery Mode.
So, I reset my Find 7, then re-installed my applications and everything again.
Thank you for answering!

bricked/completely dead Myphone S-line

Hi guys,
recently my friend's MyPhone S-line (Polish version), was full with weird apps and it was impossible to operate with it at all, so I wanted to help him and flash new fresh S-line ROM. I downloaded all necessary drivers, I found the ROM I needed and used the SP flash tools. Before that I formatted the phone (option "without bootloader"), and flashed the ROM. After flashing it, the phone ran perfectly fine, but was unable to make any calls. It was not recognizing the SIM. After more reading and tries I ended with completely dead phone. I did this, when I tried to flash one more time the ROM (don't ask me why), but this time formatted it together with the bootloader. After the format, the PC couldn't find the phone at all. All drivers are installed, but the only reaction after plugging the phone is appearing some network adapter "Alcatel Single RNDIS Interface #2", which from time to time appears with "!" mark. I tried to take out battery, press continuously volume + and plug it, insert battery and so on, but simply nor the PC neither the SP flash tool get any signs of life from the phone. So to summarize: after formatting all (including bootloader), the phone stopped responding. Any key combinations don't work.
I tried couple of youtube advices, but non of them were about completely dead phone.
And here are my 2 questions:
1. Is it possible to get back the phone to life and how?
2. If I manage do so, how to make it run the SIM again?
the phone: MTK6589, 1GB RAM, 4GB ROM, running Android 4.2.1 (last applicable version).
Thanks in advance!

Custom ROM will not boot, can't use TWRP, can't use fastboot, can't use Jodin, ARGH!!

Hey all,
My S4 Mini LTE got a bit water damaged. Was booting up fine for a while, but now is not getting past the splash screen (using Ressurection remix v. 6.0), just keeps splashing on and on, and I can't seem to successfully connect to my Mac to fix it.
TWRP is acting weird: not letting me wipe caches ('unable to mount storage') not showing any internal storage (0mb), only showing SD card at 15mb, and some buttons like reboot option are just freezing. It seems to be able to format (with some errors), but then acts the same way after.
On my Mac Fastboot is not showing any devices.
Similarly, I can't get OS X to recognize the phone with android file transfer.
The only thing that seems to recognize it is connected is Jodin, but it gives an error when trying to obtain my PIT!
edit: Heimdall ALMOST seemed to let me flash the kernel and recovery, but then gave some error right at the end.
Might be new motherboard time?!?!
Please help!
Motherboard change is easy
Yeah just replaced it... now power seems to turn off randomly in my pocket and mouthpiece doesnt work... eh probably just buy new phone

Categories

Resources