Develop Bugs

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] Always boots in flash mode (cannot boot normally nor fastboot)

Hi everyone,
Sorry for the second post but the first one has lost in the conversations, so I think that would be better to open a new thread.
I was using JJ's Hybrid ROM v2.4. And when i heard about sony's original ics upgrade, i decided to install the original one. I found this thread and followed the instructions. As so many have said, i have faced with flashing aborted problem. So I have unplugged the phone try to restart but nothing happened. Led flashes green (very quickly turns off) vibrates (as usually it does when starting) but nothing happens.
I have unplugged phone try to connect it via fastboot mode, but connecting usb cable while pressing menu button has no effect. Also when i connect the phone it always connects with flashing mode (like i have been pressing the back button).
I have tried to flash the other ftf files (on the first post) but nothing happens. Flashing aborts (just before that message it says flasing loaders/null.sin. I guess java application has a null string). I have tricked that changed the LTE15.sin file name to null.sin file, it passes that phase but still it is not bootable.
So is there any way to recover my phone?
Thanks a lot

cptlogos said:
Hi everyone,
Sorry for the second post but the first one has lost in the conversations, so I think that would be better to open a new thread.
I was using JJ's Hybrid ROM v2.4. And when i heard about sony's original ics upgrade, i decided to install the original one. I found this thread and followed the instructions. As so many have said, i have faced with flashing aborted problem. So I have unplugged the phone try to restart but nothing happened. Led flashes green (very quickly turns off) vibrates (as usually it does when starting) but nothing happens.
I have unplugged phone try to connect it via fastboot mode, but connecting usb cable while pressing menu button has no effect. Also when i connect the phone it always connects with flashing mode (like i have been pressing the back button).
I have tried to flash the other ftf files (on the first post) but nothing happens. Flashing aborts (just before that message it says flasing loaders/null.sin. I guess java application has a null string). I have tricked that changed the LTE15.sin file name to null.sin file, it passes that phase but still it is not bootable.
So is there any way to recover my phone?
Thanks a lot
Click to expand...
Click to collapse
Hi cptlogos:
Sorry for your problem, the only thing that i can say you is that every times i'd flash and block the cell, everytimes flashing an original tft wiht flash tools resolved the reboot issue after bad flashing, remenber for flash with flashtools, keep pressed the back button, the left one, and plug the usb cable.
Hope you can solve it.

Thanks for your reply jcgechevarria.
Actually I have achieved to some point, now i can boot my phone.
I have tried to run the FlashTool in linux (Ubuntu 12.04) and finally flashed it successfully. But now it can not read sim card. It asks me my pin number, waits for 1 minute then asks me my language, and after all it warns for no sim card.
I have tried with different ones, but no success at all.
Is this because of some kind of wrong region installation (I am living in Turkey and i flashed LT15i 4.0.2.A.0.42 Generic Global World)
So what can i do for my next step

Now you have the phone booting you can always try using pc companion To repair the phone.
Sent from my LT15i using xda premium

zolaisugly said:
Now you have the phone booting you can always try using pc companion To repair the phone.
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
I actually upgraded to ICS with pc companion
But it still gives error about sim card. It can not read it.

For now I have tried different ways to get the phone running back:
1) * I have successfully flashed LT15i 4.0.2.A.0.42 Generic Global World rom
* Rebooted, but it could not read the sim card. (all other features, such as wifi, works great)
* Then I connected phone to PC Companion, and upgraded to ICS.
* Rebooted, but again it could not read sim again.
2) * Then I have flashed LT15i 4.1.B.0.431 Generic Global World, rebooted, again it could not read sim card.
* After that I connected phone to Software Updater, re-installed system from there, rebooted, again it did not read sim card.
While trying all these methods, I could not connect phone with fastboot option (connecting phone while pressing menu button). If I could boot phone with fastboot, at least I could try to install custom kernel & rom.
Anybody has any ideas what can I do to get my phone back :/

[Q] Bricked Galaxy Nexus

So it all started out rather stupidly. I was attempting to flash a new ROM to my phone and I was deleting everything and accidentally deleted the OS by accident (mis-touched in recovery mode). I panicked and I attempted to push a file through adb but it was halting between 4MB - 8MB on a 200MB file. I knew this wasn't right. I ran cmd in administrator mode and tried again and got the same results.
I then moved to ODIN to attempt to flash the ROM. I ran ODIN in administrative mode. Bootloader was unlocked. I attempted to flash the new ROM but it stopped at about 1/8th of the progress (as shown in the download mode). This led to my phone having communication issues with my PC (displayed the phone with a hazard sign on the cord to the PC). I assumed it was bricked after googling around.
I then tried to use OMAPFlash as suggested by other people with the same issue. I did this, followed instructions perfectly, installed certificates. It got to the point where it was attempting to download a file. After 2 hours of waiting, I stopped it stupidly because it was making no progress.
Now my phone is completely black. I have no OS and I am not even sure if I have any files on it. Screen is black, phone not responding to button pushes and it isn't being recognised by my PC. I have tried unplugging it, removing battery and then plugging it in and inserting the battery again and that has failed.
I don't know what else to do. OMAP isn't picking up the phone anymore even though I have followed the instructions perfectly again. The one sign that my phone is still alive is the beeping noise from windows as I insert it meaning something must be happening. This however is soon followed by "Your device is unrecognised".
Can anyone help me on the situation as the phone is in perfect condition (physically) and I can't really afford a new decent phone at the moment.
Here is all the information you may need:
[Before incident]:
ROM: CM11
Rooted: Yes
Bootloader Unlocked: Yes
Ask for anything else.
[Attempted to change to]
ROM: XenonHD
Ask for anything else.

first off, why odin?
its a nexus you can flash back to stock from fastboot. I would suggest you download the factory images for the phone from here:
https://dl.google.com/dl/android/aosp/takju-jwr66y-factory-5104ab1d.tgz
then extract the images into a folder - remove the battery from the phone, put it back in the phone, power up while holding down vol + and vol - to get into fastboot
hopefully you have android sdk installed and fastboot working. use the flash-all script to flash every partition of the phone back to 4.3 stock.
good luck.

Well first thing, did you select the right zip file for your Gnex when flashing XenonHD. Bcz in my case few days ago i stupidly selected the wrong zip file (ROM for Nexus 5) to flash, but luckily i was saved by the CWM via "Status 7 Error".
But your case is more complicated i would suggest you to use Gnex toolkit with Google Factory Images, i hope that it will come for your rescue . Also try this method http://www.androidrootz.com/2012/08/how-to-restore-galaxy-nexus-i9250-to.html maybe it will do some miracle for you. Best of luck.

Progress
So after sleeping on it and spending some time deeply reflecting on the derp that I had made, I successfully managed to use omap to restore my device to the Phone-Exclamation mark sign as posted by another XDA user who ended up sending his phone back. If you search galaxy nexus brick in google images, you will see what I am talking about (can't post image).
I guess the best way to explain it is: [] -- /_\ -- [ ]
Basically it is a phone connected to a yellow exclamation mark sign and then that is connected to a computer.
Is there a way to force my phone into download mode from here. I can't seem to do anything. Some good news is that ODIN is now picking up my device. It is however crashing whenever I attempt to flash the stock ROM (either "odin3 communicator has stopped working" or "odin3 downloader has stopped working").
Any help fixing this?

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!

Problems to install stock rom (Lenovo vibe K5 Plus)

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!