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.
Related
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).
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:
So here is a string of steps I've already been through in trying to save my bricked Nexus 6: [Can't post outside link yet...]
Basically I got the 'your phone is corrupt' message from google and it kept forcibly shutting down. It would not boot up so someone suggested I side load a rescue OTA. At this point recovery existed and I went through all the steps and had it installing, only to fail mid-way through (~52%) and give me a 'read error' on my command prompt. I started the whole process over again just fine and it got to 73% before 'read error' failing again. I thought no big deal, I'll just keep doing this until it gets to 100%. Nope, recovery is gone. I cannot get there anymore. I start into Fastboot mode and scroll to recovery and hit power and it just goes to a new Fastboot screen and keeps flashing every time I try to select it. The Bootloader logs give me a 'failed to validate boot image: ret=-1' message and says 'Boot up failed.'
I can't find a single guide online that doesn't require recovery mode to work. At this point I don't care about my data and just want to get this phone working again before I throw in the towel and pay Motorola $175 for a refurb. I'm just barely over a year too. The Nexus 'expert' gave up and blamed the memory and maybe he is right but I wanted to run this by you guys first. This phone was completely stock and unrooted.
The only reason why I feel there is still a chance is because when I connect USB my computer reads it as an Android Device in Device Manager with 'Android Bootloader Interface' as a sub device. If the computer can read it, isn't there a chance that some kind of software exists that can forcibly load a new bootloader onto this phone without recovery? I'm 'competent' with computers and android phones but I haven't rooted or done any custom stuff in years so I'm at a loss for what's out there.
Thanks in advance for any help you can give me, even if it's to tell me I'm SOL.
Ok so far I have tried to load a custom recovery but that requires an unlocked bootloader. Then I tried using a toolkit to flash stock as a soft-bricked device but that also requires an unlocked bootloader and I can't unlock the damn bootloader. You know, I thought I was just playing it safe by leaving this phone as-is instead of playing around with it but it looks like I screwed myself by doing so.
Is this the wrong forum for this question?
JQ3 said:
Is this the wrong forum for this question?
Click to expand...
Click to collapse
Sorry for the delay
We have a dedicated help section for your device here
http://forum.xda-developers.com/nexus-6/help
Ask there to receive help
Good luck
Hello,
I recently unlocked, flashed TWRP and flashed Pixel Experience onto my Mi Mix 2s. After some time a notification of an available update appeared. I tried to install it but it didn't work. After some troubleshooting it appeared that I couldn't get my device booted into TWRP recovery mode.
I tried reflashing it via fastboot but that didn't work. It did not give any errors upon executing the command lines in the fastboot command prompt but just nothing happened. It just sat still like it was waiting, and waiting, and waiting.
So i thought, let's just reset the phone via the normal settings menu in Android. In hindsight that was quite a dumb move I guess, because after all the phone used to be working. But still I followed through and now it wound up in a bootloop. I can still get it into the bootloader mode, and in fastboot it shows my device when I execute <fasboot devices> but flashing or erasing the recovery doesn't work. It looks as if it sees the phone, can get info from it but is not able or allowed to flash anything to it. But it doesn't give any errors, it just seems to keep waiting on something, I don't know.
I hope any of you guys can help me because searching this forum or googling hasn't helped me getting any further. All topics I found at least had some errors in fastboot/bootloader mode which gave them a direction to go into...
So please help me!
Whoops, I solved it myself. On another laptop it magically worked the first time. Probably an issue with either the USB port or the drivers.
Thread closed at OP request
So this was what happen, i have been trying to format my phone this day to put a rom and i had an issue (that which never happend to me) my phone was always getting an error either on Parse, or Vendor check, i kinda decided to install TWRP on bootloader as i thought i could go around, but figure out i had to download the files, since i didnt want to lose time what i actually did, was flashing the phone again to see if the phone could go further.. but the phone didnt want to pass to that phase.. i was getting impatient.. i disconnected the cable or "how we can say i closed the program multiple time betwen a flash.
I was on 1909. My bootloader was detected everything was detected the phone everything, but since i thought that windows 10 version 1909 might had something with it, i thought "well why not download a recent version" take in mind i have no option, i have no recovery, i tried already to acess it by pressing and hold POWER UP, it returns right away to fastboot, my phone name isnt detected under device manager, nor when i do adb devices, fastboot devices detects it, and i tried already some commands like passing the TWRP to it, but it doesnt overwrite anything, sometimes i get the error"No devices or emulators found" .
Im lost i think i lost my phone, im desperate
Any expert here that can help me with this?
Im gonna try to go back to an early windows 1809, which i used to format this phone a lot to other rom
Meanwhile i need some help on this