Hi there,
I'm not new to rooting and flashing devices, but something went wrong during my last root. I was using CWM to root the most recent paranoid android rom, a 4.4 rom, and after I rebooted, the device started normal and works fine. However, it's completely lost root AND has no recovery. Just the little opened up android guy with his red triangle.
I've tried using the toolkit, but the ADB drivers just are not being recognized. I've tried all of the driver options, and it says that it worked, but when I run the driver test it says failed. When I connect the device as MTP, it shows up as having recognized the device, but I can't actually access the device from the computer. When I try fastboot, nothing happens. The device just goes black and sits like that until I hold the power button down for awhile.
So, the toolkit can't get me back to stock, at least not any way I've tried. And since I can't install a recovery, I can't flash a new rom or stock.
I guess it could be worse, as the device does still work, but I want it fully functional.
Does anyone have any solutions?
Hopefully this is the right place to ask this question.
Thanks in advanced!
lasnaranjas said:
Hi there,
I'm not new to rooting and flashing devices, but something went wrong during my last root. I was using CWM to root the most recent paranoid android rom, a 4.4 rom, and after I rebooted, the device started normal and works fine. However, it's completely lost root AND has no recovery. Just the little opened up android guy with his red triangle.
I've tried using the toolkit, but the ADB drivers just are not being recognized. I've tried all of the driver options, and it says that it worked, but when I run the driver test it says failed. When I connect the device as MTP, it shows up as having recognized the device, but I can't actually access the device from the computer. When I try fastboot, nothing happens. The device just goes black and sits like that until I hold the power button down for awhile.
So, the toolkit can't get me back to stock, at least not any way I've tried. And since I can't install a recovery, I can't flash a new rom or stock.
I guess it could be worse, as the device does still work, but I want it fully functional.
Does anyone have any solutions?
Hopefully this is the right place to ask this question.
Thanks in advanced!
Click to expand...
Click to collapse
Few things:
try another soft reset. power the device on, and then hold the power button down until it restarts.
download superuser/supersu to see if there actually is no root. sometimes it's just being difficult and says there is no root.
Following that, try downloading ROM manager and seeing if it'll flash the recovery.
Related
I've done about 3 hours of research on this forum and the internet in general, and I can't seem to find a situation like the one I'm in. I'm not particularly savvy at all of this, but have successfully rooted a few phones and have played with a variety of ROMs for both tablet and phone. I have the Android SDK installed, the drivers for my phone installed on my computer, PDANet, the works. I'm on a Windows 7 laptop.
I had a new JRO03L ROM build for my verizon GNex flashed, and was getting quicker than expected battery drain. So I decided to flash a custom kernel. I must have flashed the incorrect version of this kernel.
When I rebooted after flashing the kernel in CWM, it went into a bootloop on the Google screen. I waited an hour, pulled the battery and tried to boot into hboot (volume down+power button). Lo and behold, I can't get back into CWM! I have no option to enter recovery, I'm only able to start the boot process.
So I plug it into my computer, hoping that I might be able to use the GNex Toolkit (v7.8) to restore to stock and start over, or even just try to use fastboot to ... do something - anything! - and my computer doesn't recognize my phone when in hboot. When in hboot, my device manager recognizes the phone as "SAMSUNG Mobile USB CDC Composite Device" and as a modem. When I start the boot process and it is bootlooping, my computer recognizes it as my phone, but can't install the drivers properly.
Any help would be greatly appreciated, even if you can get me back to stock. I have a nandroid backup on my SDCard; I just need to be able to get to it and flash it. I would be forever in your debt if you can help me out! Thank you in advance!
rs18 said:
I've done about 3 hours of research on this forum and the internet in general, and I can't seem to find a situation like the one I'm in. I'm not particularly savvy at all of this, but have successfully rooted a few phones and have played with a variety of ROMs for both tablet and phone. I have the Android SDK installed, the drivers for my phone installed on my computer, PDANet, the works. I'm on a Windows 7 laptop.
I had a new JRO03L ROM build for my verizon GNex flashed, and was getting quicker than expected battery drain. So I decided to flash a custom kernel. I must have flashed the incorrect version of this kernel.
When I rebooted after flashing the kernel in CWM, it went into a bootloop on the Google screen. I waited an hour, pulled the battery and tried to boot into hboot (volume down+power button). Lo and behold, I can't get back into CWM! I have no option to enter recovery, I'm only able to start the boot process.
So I plug it into my computer, hoping that I might be able to use the GNex Toolkit (v7.8) to restore to stock and start over, or even just try to use fastboot to ... do something - anything! - and my computer doesn't recognize my phone when in hboot. When in hboot, my device manager recognizes the phone as "SAMSUNG Mobile USB CDC Composite Device" and as a modem. When I start the boot process and it is bootlooping, my computer recognizes it as my phone, but can't install the drivers properly.
Any help would be greatly appreciated, even if you can get me back to stock. I have a nandroid backup on my SDCard; I just need to be able to get to it and flash it. I would be forever in your debt if you can help me out! Thank you in advance!
Click to expand...
Click to collapse
Post three of my guide.
Push another rom.zip to your phone and flash it (if you don't already have one there).
If you have one...You're not getting into the correct menu.
You're in ODIN.
Bootloader/Recovery is BOTH volume buttons.
Jubakuba said:
Post three of my guide.
Push another rom.zip to your phone and flash it (if you don't already have one there).
If you have one...You're not getting into the correct menu.
You're in ODIN.
Bootloader/Recovery is BOTH volume buttons.
Click to expand...
Click to collapse
Thank you. I'm an idiot. It's been a long while since I've put this into recovery via physical buttons.
By the way, your guide is excellent. How have I not stumbled across this?
So I rooted my Nexus 7 (2013) a while back, and it was working fine. I have TWRP recovery installed, bootloader unlocked, and I thought it was rooted. Then (don't kill me, I can't remember what I did, it was so long ago - I think maybe I installed the official KitKat update, although I am pretty sure I sideloaded a rooted version of the stock KK ROM), root just stopped working. Root Checker says I'm not rooted, even though I have the SU app installed. So, I thought, I'll just flash the SU.zip from recovery. So I flash it. And literally nothing happens. It says it flashed successfully, but when I reboot, no root.
In fact, any time I flash anything, it appears to work, but doesn't actually do anything. I tried flashing a different ROM and no dice. I tried accepting the official 4.4.2 update and again, looked like it flashed, but was still 4.4 when I rebooted.
So I thought I'll just plug it into my PC and re-root and maybe flash everything if need be. Except, when I plug it in, it 1) isn't recognized by my computer at all, no matter how many times I uninstall and reinstall drivers, and 2) the ADB connected icon doesn't show up, even when I enable it in Developer Settings.
So basically I'm dead in the water: I can't do anything via recovery, and if recovery is messed up, I can't do anything because it won't connect to my computer (Windows 7, SP1, 64 bit). I have a Mac running OS X Mavericks, if anyone knows some Terminal tricks for stuff.
So…advice?
darnocs1 said:
So I rooted my Nexus 7 (2013) a while back, and it was working fine. I have TWRP recovery installed, bootloader unlocked, and I thought it was rooted. Then (don't kill me, I can't remember what I did, it was so long ago - I think maybe I installed the official KitKat update, although I am pretty sure I sideloaded a rooted version of the stock KK ROM), root just stopped working. Root Checker says I'm not rooted, even though I have the SU app installed. So, I thought, I'll just flash the SU.zip from recovery. So I flash it. And literally nothing happens. It says it flashed successfully, but when I reboot, no root.
In fact, any time I flash anything, it appears to work, but doesn't actually do anything. I tried flashing a different ROM and no dice. I tried accepting the official 4.4.2 update and again, looked like it flashed, but was still 4.4 when I rebooted.
So I thought I'll just plug it into my PC and re-root and maybe flash everything if need be. Except, when I plug it in, it 1) isn't recognized by my computer at all, no matter how many times I uninstall and reinstall drivers, and 2) the ADB connected icon doesn't show up, even when I enable it in Developer Settings.
So basically I'm dead in the water: I can't do anything via recovery, and if recovery is messed up, I can't do anything because it won't connect to my computer (Windows 7, SP1, 64 bit). I have a Mac running OS X Mavericks, if anyone knows some Terminal tricks for stuff.
So…advice?
Click to expand...
Click to collapse
Does it recognize your device when it's booted into the bootloader (aka fastboot mode)?
charesa39 said:
Does it recognize your device when it's booted into the bootloader (aka fastboot mode)?
Click to expand...
Click to collapse
It didn't, but I found I was using a bad USB cable. Swapped out, and now it works (yay). However, root still wouldn't work after I ran several rooting methods from the computer.
Finally, I went to the Play Store, downloaded Superuser from Clockworkmod, followed their link in that description to download the flashable zip, flashed that, and FINALLY got root working. So happy.
darnocs1 said:
It didn't, but I found I was using a bad USB cable. Swapped out, and now it works (yay). However, root still wouldn't work after I ran several rooting methods from the computer.
Finally, I went to the Play Store, downloaded Superuser from Clockworkmod, followed their link in that description to download the flashable zip, flashed that, and FINALLY got root working. So happy.
Click to expand...
Click to collapse
Cool. Glad it worked out for you. :good:
Alright, so i hadn't used my nexus 7 (2013 wifi only version) for awhile but i decided to start using it again. It was running a custom ROM (paranoid android) but it was very outdated. I decided i would just start fresh, and would flash the stock ROM before doing anything else.
So i tried to put the stock ROM (4.4.3 from google's site) but it would not let me flash it using clockwork recovery mod when i just put the file onto the device. So i tried to adb sideload it. This is where the problems started.
In my command prompt (using windows 8) it showed it was loading files, then it started to fail, im not sure where because it was moving very fast. But it said it failed and ended the side load. On my nexus 7 the screen was at the bootloader but none of the hardware buttons did anything so i turned it off. turned it on again and let it sit for 5 minutes but it just stayed at the google screen. I turned it off and held the power and volume down to launch the bootloader. This time i could use the hardware buttons but when i tried to select the recovery mode option it just rebooted and stayed on the google screen again...
So right now, it is either stuck at the google screen, in the bootloader, or off and i can go between these. I also can't seem to get it to show up on adb but im going to try to install the drivers again.
If anyone knows of a fix to get the device working again, preferably on the stock android ROM but I'll take anything at this point I just want my tablet working again Thanks.
Hello,
The issue you are experiencing is because the files found on https://developers.google.com/android/nexus/images from google can't be flashed through a custom recovery. They must be flashed through the bootloader. If are able to get ADB to recognize the device in bootloader then you should be good to go.
You can follow the steps listed here: http://forum.xda-developers.com/showthread.php?t=2382618
Hi there,
I've been trying to fix this issue for a while now and I haven't seen any guides on my particular issue.
Basically what's going on is I tried doing a factory reset on the phone while having cyanogenmod flashed and when it booted, it would keep booting up in the recovery.
There seem to be no backups or roms on the phone.
Now here's the kicker, when I try using the Nexus root toolkit, it doesn't recognize my device whatsoever. I've uninstalled the drivers fully and reinstalled them and still nothing.
When I plug the phone in, it doesn't show up as an external source (other than in the device manager with a "!" by 'galaxy nexus'), so I can't just put a ROM on there and try flashing that.
I'm stuck. I have no idea what I can do to get this back up & running.
It's a GSM phone, being from Canada I believe it to be Yakju...
Anybody have any ideas? I really need this phone to start working!!
Have you tried the method in this tutorial?
you may bring ti back to samsung customer service.
Hi all,
I'm turning to forums now because I'm desperately in need of help.
I have an Oppo Find 7a which I bought about 9 months ago. When I first got it I tried flashing Cyanogenmod to it (unsuccessfully), and then tried rooting the phone. I have since unrooted the phone, and am running Color OS v 1.2.5i and really really need to update. Problem is, I cannot seem to update the operating system. Here's what happens:
Phone fails to boot to recovery
In my attempts to install Cyanogenmod, I installed a custom recovery. However I couldn't get Cyanogenmod to flash properly, so I tried reverting to the stock recovery. Did that, which seemed to work fine. However, since rooting and unrooting my phone, I cannot boot into reocovery at all. When turning off the phone and then pressing power+volume down to try and boot in, the "OPPO" logo comes up as if trying to boot into recovery, then the phone just turns off and boots into normal OS. Have tried many things but can't seem to get into recovery at all. This means that when an OS update is detected (which it is), the phone tries to reboot into recovery to install the update and cannot. So I'm stuck on a very buggy OS and can't do anything to update. Before you suggest adb+fastboot solutions, please read below:
Phone not recognised in PC at all
When plugging the phone into a PC via usb cable literally nothing happens (aside from the phone detecting it is charging). The phone does not mount as a volume in Windows, the phone is not detected as a device in device manager, as far as the computer is concerned, the phone is not even there. I have tried having the phone plugged in and installing all the proper adb drivers, but this has still yielded no results. And yes USB debugging is definitely enabled on the phone. I don't know why, but for some reason I literally cannot plug my phone into a PC anymore which limits me a LOT in terms of fixing the problem above.
Basically I really need to update the OS on this phone and am compeltely stuck: nothing seems to work. Can anyone help me out here. What do I need to do?? Any help is greatly appreciated.
seem adb device in windows device manager when the phone plug USB at bootloader?
if yes, you can use adb+fastboot solution