So, newb me did a bad thing. I managed to install TWRP Recovery on my Nexus 5 to attempt rooting it. It didn't work a t first so I tried cleaning up some existing data. I did a factory reset, a format data, and... drumroll... advanced wipe, where I selected everything.
When I went to reboot, TWRP told me there was no OS.
I've already downloaded the stock KitKat for my device and the sdk tools (and even the unified android toolkit found here in the forums). I couldn't find a way to flash stock yet
It seems my device does not connect on USB in ADB mode, it only shows Recovery mode. Trying "fastboot flash" gets stuck on "< waiting for device >". Using "adb devices" shows something like "some_number recovery".
Any suggestions? I can do adb shell but I don't know how to restore the files I deleted without flashing or how to make flashing work.
Thanks a lot
Someone resolved this same issue. http://forum.xda-developers.com/showthread.php?t=2533148
That worked like a charm.
Thanks a lot!
Related
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Tunameltsalad said:
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Click to expand...
Click to collapse
Can you use fastboot to reflash the stock ROM?
Dear XDA community,
I installed Clockwork recovery and the USB drivers. The device is unlocked and when in fastboot mode it is correctly identified by my PC as falcon XT1302 with an USB connection. When in recovery mode, the device appears as "Android" in the devices menu in Windows 7 and there is a yellow "!" next to it. Unfortunately after formatting system and deleting the cache as per instructions the device won't boot up. I'm stuck at the bootloader unlock warning screen. I can access fastboot mode and recovery mode but that's it.
I want to place the cyanogenmod zip inside the internal SD card of the Moto G but adb doesn't work. I get the device not found error when inputting a command. adb devices returns a blank. I don't know which drivers to install or what to do. I've tried various fixes on forums but none work. Maybe USB debugging is the problem although I distinctly remember switching it on. In any case, I can't boot so I can't change the settings.
All I want is a way to place the cyano .zip in the phone /sdcard so that I can install it. I'm all out of ideas. USB mounting doesn't seem to work. Neither does sideloader (or maybe I messed it up?) I am at wit's end.
I didn't have anything important on my phone so I did not make a backup. In hindsight, this was a stupid mistake. I've certainly learned a lot during the install attempt.
If possible please give step by step instructions. I am not a very technical person. Any help would be greatly appreciated. pls halp
kind regards
Dont worry too much if you can acces Fast Boot just download STOCK Firmware for your version I can't post links cuz im beginer searc under help "Restore STOCK Firmware" and flash it. :fingers-crossed:
Reply here i will tell you how if you not fixed it alredy
Thanks but that's not really what I want to do. I want to flash cyanogenmod on it.
regards
hechadnebiphyh said:
Thanks but that's not really what I want to do. I want to flash cyanogenmod on it.
regards
Click to expand...
Click to collapse
As above said flash stock boot up copy cm11 and gapps reboot boot loader flash cwm or twrp reboot recovery wipe data,cache,dalvik flash ROM gapps reboot all done
Sent from my Nexus 7 using Tapatalk
Thanks to the users who replied. I've managed to solve the problem. :laugh:
Would have been faster though to get your device recognized while in recovery. You can install the driver manually and it should work. Just search for seperate driver files and ignore the Windows message that it is probably 'not compatible etc.'.
Then your device is connected properly and you can get ADB sideload to work from your recovery.
I unlocked the bootloader on an old HTC One S through the directions on the HTC Developer website. I then loaded the CWM recovery and did the rooting and installed the Rom manager app. The SuperSU update had to be added with the abd sideloader and the rootcheck said it had root access. Both of those programs seemed to be working fine. Then I send the Zip file of a ROM (idk which one because I renamed it so it would be easier to enter) and from the ROM manager I select the one I just sent and go to install it.
Then the phone turns off and a long string of code ends with "transfer successful" or something to that effect but stays there. I rebooted and tried again and the same thing. Tried again and did a factory reset from the recovery but nothing would get the phone to boot past the HTC screen. I tried Wiping the davlik cache and the regular wipe and hard reset and adding the recovery again but NOW MY PHONE DOESNT SHOW UP WITH ADB DEVICES CMD.
I am already in over my head but I have been enjoying learning from this and other websites about how android works. However I think I have exhausted my research options and I am at dead end...
How can I get the adb commands to work again?
bmckeeoneill said:
I unlocked the bootloader on an old HTC One S through the directions on the HTC Developer website. I then loaded the CWM recovery and did the rooting and installed the Rom manager app. The SuperSU update had to be added with the abd sideloader and the rootcheck said it had root access. Both of those programs seemed to be working fine. Then I send the Zip file of a ROM (idk which one because I renamed it so it would be easier to enter) and from the ROM manager I select the one I just sent and go to install it.
Then the phone turns off and a long string of code ends with "transfer successful" or something to that effect but stays there. I rebooted and tried again and the same thing. Tried again and did a factory reset from the recovery but nothing would get the phone to boot past the HTC screen. I tried Wiping the davlik cache and the regular wipe and hard reset and adding the recovery again but NOW MY PHONE DOESNT SHOW UP WITH ADB DEVICES CMD.
I am already in over my head but I have been enjoying learning from this and other websites about how android works. However I think I have exhausted my research options and I am at dead end...
How can I get the adb commands to work again?
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.
Hello all,
So I made a stupid mistake yesterday, and have desperately been trying to fix it since. I have a Moto G 1st gen, which I unlocked, installed the latest CM13 nightly, and rooted. I was tinkering in the settings, and I saw that CM had OTA, so I replaced TWRP with CyanogenMod Recovery.
However, as it had been a long time since I had used an Android device, I thought I still needed to use a superuser access manager, and so I installed SuperSu. Apparently big mistake, I rebooted my device and it was bootlooped. I boot into recovery, and all I have access to is this super stripped down, minimal cyanogenmod recovery. I have a couple of TWRP backups, and the latest one should be on the phone. Since then, I have Factory Reset from recovery (both "system reset" and "full factory reset"). I hope I didn't make things worse by resetting the phone, but it's too late to undo that now if I did. Now what I need to do is get TWRP back as my recovery, and then I'll be able to restore.
The problem is, however, that when I try to flash TWRP through ADB, it tells me <waiting for devices>, and when I write "adb devices" it lists my devices, but tells me it's unauthorized. I know that this would normally be fixed by booting the device and "Trusting" the computer by accepting the one screen phone dialogue, but this is obviously not an option for me. So I do not know if there is any way to authorize the device and thereby flash TWRP without booting the device. Other than that, in the "Advanced" section of CM Recovery, there is an option to "Mount /system" but when I press it, it doesn't seem to do anything.
At this point just making any amount of progress would be phenomenal, I am super frustrated and annoyed that I made such a dumb mistake. I would very much appreciate any help you kind folks have to offer. Let me know if there is any important information that I have forgotten to include in my description of the problem. I look forward to seeing your replies, thanks in advance.
sstargrave said:
Hello all,
So I made a stupid mistake yesterday, and have desperately been trying to fix it since. I have a Moto G 1st gen, which I unlocked, installed the latest CM13 nightly, and rooted. I was tinkering in the settings, and I saw that CM had OTA, so I replaced TWRP with CyanogenMod Recovery.
However, as it had been a long time since I had used an Android device, I thought I still needed to use a superuser access manager, and so I installed SuperSu. Apparently big mistake, I rebooted my device and it was bootlooped. I boot into recovery, and all I have access to is this super stripped down, minimal cyanogenmod recovery. I have a couple of TWRP backups, and the latest one should be on the phone. Since then, I have Factory Reset from recovery (both "system reset" and "full factory reset"). I hope I didn't make things worse by resetting the phone, but it's too late to undo that now if I did. Now what I need to do is get TWRP back as my recovery, and then I'll be able to restore.
The problem is, however, that when I try to flash TWRP through ADB, it tells me <waiting for devices>, and when I write "adb devices" it lists my devices, but tells me it's unauthorized. I know that this would normally be fixed by booting the device and "Trusting" the computer by accepting the one screen phone dialogue, but this is obviously not an option for me. So I do not know if there is any way to authorize the device and thereby flash TWRP without booting the device. Other than that, in the "Advanced" section of CM Recovery, there is an option to "Mount /system" but when I press it, it doesn't seem to do anything.
At this point just making any amount of progress would be phenomenal, I am super frustrated and annoyed that I made such a dumb mistake. I would very much appreciate any help you kind folks have to offer. Let me know if there is any important information that I have forgotten to include in my description of the problem. I look forward to seeing your replies, thanks in advance.
Click to expand...
Click to collapse
Ya.... download mfastboot n then type mfastboot flash recovery recovery.img
But before that Extract mfastboot on desktop and copy recovery.img(twrp) in same folder......
skyrajparmar said:
Ya.... download mfastboot n then type mfastboot flash recovery recovery.img
But before that Extract mfastboot on desktop and copy recovery.img(twrp) in same folder......
Click to expand...
Click to collapse
Hmm, thanks for the info. However, when I try that, I get <waiting for any devices>. When I type "fastboot devices", I get nothing, I believe I installed the drivers correctly, as I used fastboot prior to bricking my phone. Any suggestions?
Hi guys, I'm normally the one who reads these forums, not starts them, so i'm in pretty desperate help.
I have a Samsung Nexus S phone that somehow got stuck in a bootloop after my dad attempted to fix the problem by wiping everything he could from the recovery; cache, system, data, factory reset. I am able to access fastboot (obviously). In fastboot mode, the only 4 options it gives are POWER OFF, REBOOT, RECOVERY, REBOOT BOOTLOADER. None of these options leads to any progress. Only one that makes sense is to click and run recovery. When recovery loads, i can:
Reboot system now
apply update from ADB
apply update from sd card
wipe/factory reset
wipe cache partition
I recently rooted and custom ROMed my Galaxy J7 Pro, and as you experts may know it wasn't too easy finding the correct files or even the support for it.
I know you have to have developer options enabled and OEM and USB Debugging as the prereqs for rooting, but this phone has nothing. I'm not sure what to do. The bootloader is locked and I obviously can't enable developer options. I guess where I'm stuck is how i can flash a custom recovery like twerp for a phone that has a locked bootloader that can't be unlocked through developer options.
As I'm writing this, i was thinking, can i prepare an SD card with the lollipop OS for the nexus to install and run on. Ive already wiped the internals and cache of the phone, meaning there is nothing on it?
Help would be appreciated, bringing back a phone that has the potential (working hardware) to run would be great.
Just do a manual restore using the google factory images (google them, first result usually and a VERY user friendly page, thanks google!).
Don't use the script, just reformat everything via fastboot, then manually flash the images to their respective partitions.
"cd [path to unzipped images]"
"fastboot format /[partition] ext4"
"fastboot flash /[partition] [path to image]"
and so on and so on. Then after, "fastboot reboot". I assume you've found a fix by now but maybe someone else will stumble on this. Keep in mind, I'm writing this from memory and with no drivers or way to test this on my mac, my Nexus S is coming in the mail soon so take what I say with a grain of salt and try to double check the commands. For the most part however, they should be correct. format, reflash, reboot. All you should have to do.
padhpataka said:
Hi guys, I'm normally the one who reads these forums, not starts them, so i'm in pretty desperate help.
I have a Samsung Nexus S phone that somehow got stuck in a bootloop after my dad attempted to fix the problem by wiping everything he could from the recovery; cache, system, data, factory reset. I am able to access fastboot (obviously). In fastboot mode, the only 4 options it gives are POWER OFF, REBOOT, RECOVERY, REBOOT BOOTLOADER. None of these options leads to any progress. Only one that makes sense is to click and run recovery. When recovery loads, i can:
Reboot system now
apply update from ADB
apply update from sd card
wipe/factory reset
wipe cache partition
I recently rooted and custom ROMed my Galaxy J7 Pro, and as you experts may know it wasn't too easy finding the correct files or even the support for it.
I know you have to have developer options enabled and OEM and USB Debugging as the prereqs for rooting, but this phone has nothing. I'm not sure what to do. The bootloader is locked and I obviously can't enable developer options. I guess where I'm stuck is how i can flash a custom recovery like twerp for a phone that has a locked bootloader that can't be unlocked through developer options.
As I'm writing this, i was thinking, can i prepare an SD card with the lollipop OS for the nexus to install and run on. Ive already wiped the internals and cache of the phone, meaning there is nothing on it?
Help would be appreciated, bringing back a phone that has the potential (working hardware) to run would be great.
Click to expand...
Click to collapse
I have the same problem.I know this was 4 years ago but as a noob I find that guides tend to assume greater levels of knowledge than I have. Trying to bypass FRP as I think this is what is causing the "system error" message when I try to access play store or Google plus. I haven't even been able to unlock bootloader or root phone . In fact I find "fastboot" and ADB downloads a mystery? How to get them to work?