Any help appreciated. I was trying to install second bootloader to my kfhd7 and HAD twrp working and when trying to complete the process upon reboot when the red triangle recovery screen showed up(i thought nothing of it) and it asked to restore device or something else, i believe i chose the restore option. ever since i have been stuck at the splash screen with orange kindle fire replaying over and over. I made a flimsy fastboot cable(which is now broke, I ordered a skorpn one) and was able to get into fastboot but i absolutely cannot get the device recognized in fastboot or adb. Mind you i had the drivers/adb working previously. I fear that without FB recognition on my pc I will be SOL... running windows 8 and FB cable should be here tomorrow or next day. wanna be prepared when they arrive. In advance thank anyone who helps for your help.
psver the last week im pretty sure i've read almost every kfhd7 post out there and haven't found one exactly like this. do not seem to find anyone else having some much trouble getting ADB/Fastboot to see device as me when in this situation(used to be the easiest part for me).
Related
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
issact said:
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
Click to expand...
Click to collapse
zironia said:
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
Click to expand...
Click to collapse
Hey, it's good to hear I'm not alone in this. lopestom has been friendly enough to correspond with me about it and he suspects it's a new model of the same phone. I sent him a screen cap of the factory settings screen (VOL-/POW)
In the end we might be out of luck until more people get their hands on the new version of the phone.
Hello!
I purchased my HTC One M8 from Verizon about a month and a half ago. I love the phone, and it hasn't caused me any issues at all - until a few days ago. I went to pick up my phone and the screen was off; I couldn't turn the phone on.
After fidgeting with the power/up+down buttons, I got it to load the boot loader. I tried almost every option on the menu in there, and I seem to be stuck in a boot loop. When I try hooking up my phone to my PC, HTC Sync loads but says there is no device connected. My PC doesn't recognize the device, either. I've never tried to root the device or anything, so it's "Locked" with S-ON.
I am trying to figure out if I can get my photos off of the device before I send it into Verizon for a replacement. I (stupidly) thought that the photos were being automatically backed up on Google, and I never put my SD card into the phone.
Does anyone know if or how I can do this? I'm not a developer, but I'm pretty technical, so any step-by-step advice would help!
Thank you!
You may be able to issue an "adb pull" of the data partition if you have adb setup on a computer. You should Google it and see if you can get adb up and running.
cntryby429 said:
You may be able to issue an "adb pull" of the data partition if you have adb setup on a computer. You should Google it and see if you can get adb up and running.
Click to expand...
Click to collapse
Thank you! I'll let you know if I can get in that way.
Hi,
I have an iRulu (some off-brand Chinese tablet that is also somewhat branded as Allwinner) 9.7" tablet. I was going install a recovery and try to learn how to compile a ROM for it but things went wrong at step one. I hooked it up to my computer (running Arch linux) and got ADB to recognize the device. I typed "adb reboot bootloader" to get into fastboot and see if the bootloader was unlocked, but when it rebooted it just got stuck on the logo screen and was not responsive to fastboot and adb no longer recognized its presence. I haven't been able to find any other examples online of that command bricking a device. As far as I can tell, none of the normal button combinations work to get to recovery or anything like that. It's not really a bootloop because it doesn't restart and try to boot again. It's just frozen and I can't find my way in. I found a forum that said to disconnect the battery for 30 seconds but it's soldered in (I'm comfortable desoldering and resoldering but I'd prefer another solution). Any ideas on how to recover the situation? Thanks in advance!
830hobbes said:
Hi,
I have an iRulu (some off-brand Chinese tablet that is also somewhat branded as Allwinner) 9.7" tablet. I was going install a recovery and try to learn how to compile a ROM for it but things went wrong at step one. I hooked it up to my computer (running Arch linux) and got ADB to recognize the device. I typed "adb reboot bootloader" to get into fastboot and see if the bootloader was unlocked, but when it rebooted it just got stuck on the logo screen and was not responsive to fastboot and adb no longer recognized its presence. I haven't been able to find any other examples online of that command bricking a device. As far as I can tell, none of the normal button combinations work to get to recovery or anything like that. It's not really a bootloop because it doesn't restart and try to boot again. It's just frozen and I can't find my way in. I found a forum that said to disconnect the battery for 30 seconds but it's soldered in (I'm comfortable desoldering and resoldering but I'd prefer another solution). Any ideas on how to recover the situation? Thanks in advance!
Click to expand...
Click to collapse
When you open the back cover, do you see the board number? You can try searching for firmware using the number, and flashing it. Mine was stuck in bootloop for months before i figured it out(i own a ubislate 7c+ edge, a11 firmware worked for me).
Sent from my GT-I9082 using XDA Free mobile app
NoobInToto said:
When you open the back cover, do you see the board number? You can try searching for firmware using the number, and flashing it. Mine was stuck in bootloop for months before i figured it out(i own a ubislate 7c+ edge, a11 firmware worked for me).
Sent from my GT-I9082 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks that's a great idea. Might not solve the problem to know the firmware, but more information is always helpful.
OK, I solved this. Here's what I did:
- Let the tablet die. All the way. After I left it on that stupid boot screen it was stuck on until it died, I left it another week just sitting there.
- Plug in the power connector and the micro usb connector.
- Turn it on once it gets charged enough that it's willing to start.
- Move the USB connector to the USB-to-go (HOST) spot while still connected to your computer. This crashes the device from some kind of voltage protection mechanism.
I'm not sure exactly what happened but after that the device started just fine. I think the voltage protection mechanism might have kicked it out of "boot to bootloader" mode, where I think it was frozen, and into actual boot mode. I wouldn't necessarily recommend this solution since I put the actual hardware of my computer and the tablet at risk, but I figured my laptop was old and my tablet was bricked so there wouldn't be any huge loss.
Anyway, I'm marking this as solved. If anyone has this happen to them and my solution actually works for you, let me know. I'd get a huge kick out of hearing someone else follow my stupidity. Good to have my tablet back!
Sisonke= We are on the same path in my language
i am currently having the same situation RIGHT NOW. Loved messing with ADB and its ....functions... also typed adb reboot-bootloader and guess what i got.. Stuck at the boot face. lol:laugh: but im gonna take our advice, if you say draining the power is the key...well i find no harm in cutting the main battery source for a while and then reconnecting it again. If this procedure doesn't work...I'll have to do it your way. Crossing fingers ..hope it works. email me wen u get this. [email protected]:angel:
Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.
Hi all,
So my I decided to bring my old Oneplus One back to life by following some 'Unbrick Tutorials'. I've tried a couple but nothing seems to work.
So I followed this tutorial as last resort:
http://www.androidbrick.com/unbrick-oneplus-one-two-3-3t-qualcomm-hs-usb-qdloader-9008/
Everything went like it's supposed to happen I guess. My cmd window gave me positive info (Things like: flashing recovery.img - okay... Sending packages etc. etc.) So I wanted to perform the final step -> reboot to recovery and all of a sudden my phone vibrates! yay!
But then it showed some nasty vertical stripes and it didn't boot in recovery at all. I don't see anything exept those lines. But my PC seems the recognize my OPO. When I launch fastboot my pc can find it.
But what do I do now!? How do I boot it normally and get rid of those vertical lines!? PLEASE HELP!!
Thank you for your time and effort in helping me! I'll donate a beer for the guy that helps me fix this issue!
Thread on OnePlus Forums: here
Are you sure it's not hardware damaged? "Bring to life" from what? What happened to it in the first place?
use wugfresh tool kit and go back to stock and start again and see if it fixes the issue may just been a bad flash of the recovery