Hello all,
I initally used the Wugz root toolkit to unlock, install drivers and root my device. I flashed CWM and a ROM. Once I flashed the ROM, it wouldn't boot, but would flash the google logo, go black, then go to the google logo and open up CWM again.
I searched for backups, they were gone. So I tried a few things and now I can't even get to CWM.
All I can get to is the Recovery menu and Stock Recovery. My computer won't recognize the device in adb fastboot but will recognize it when I put it into sideload from the stock recovery.
I've tried to flash the 4.1.2 and 4.2.2 images from the Google developer website but when it verifies the installation package it says installation aborted.
Is there any way I can fix this just from the Stock Recovery sideload? Is this hopelesss?
Take a look at this THREAD
Nico_60 said:
Take a look at this THREAD
Click to expand...
Click to collapse
Thanks. I did try this first, I must have messed it up somewhere. I'll try it again. Not sure if it'll work without the device being recognized under fastboot.
To know if it's recognized type "fastboot devices" but if the driver were already installed it must be ok
Whew got it to work. Thanks.
Related
i was stuck in a bootloop after flashing a ROM, and didnt have any backups or other ROMs on the devices storage, so i was attempting to push files to it via ADB, but it wouldnt connect. i went back into the custom recovery image, and accidentally wiped the whole thing, so now i have no OS installed, and not even the seeminly 'faulty' ROM in /sdcard either. i can still get into the bootloader and the custom recovery, but cant seem to get it to connect to ADB. any ideas what i can do?
If you could boot into fastmode, then just flash stock rom.
Leonhan said:
If you could boot into fastmode, then just flash stock rom.
Click to expand...
Click to collapse
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...
bmoreyce said:
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...
Click to expand...
Click to collapse
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.
najaboy said:
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.
Click to expand...
Click to collapse
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.
bmoreyce said:
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.
Click to expand...
Click to collapse
You don't need ADB if you are in the bootloader- you use fastboot.
So I messed up my Nexus somehow. I was trying to install MIUI coming from Carbon ROM but something went wrong as it got stuck on the miui logo. So I rebooted to TWRP and restored my backup. So then I tried to install PA and then it just got stuck on the google logo. So i restored my backup again and tried again to no avail. Then after that I couldn't restore my backup ( I keep getting FAILED as soon as the data restore starts). I can boot to Recovery but I dunno what to do. I tried sideloading but that's not working. I tried the toolkit but everytime it tries to download the factory image it says 404. The phone charges and whatnot but I don't know what to do. I only have the PA rom on my phone and reinstalling it doesn't do anything. The only weird thing is that when I try to install the PA gapps I get a FAILED message. Any help would be appreciated
varem said:
So I messed up my Nexus somehow. I was trying to install MIUI coming from Carbon ROM but something went wrong as it got stuck on the miui logo. So I rebooted to TWRP and restored my backup. So then I tried to install PA and then it just got stuck on the google logo. So i restored my backup again and tried again to no avail. Then after that I couldn't restore my backup ( I keep getting FAILED as soon as the data restore starts). I can boot to Recovery but I dunno what to do. I tried sideloading but that's not working. I tried the toolkit but everytime it tries to download the factory image it says 404. The phone charges and whatnot but I don't know what to do. I only have the PA rom on my phone and reinstalling it doesn't do anything. The only weird thing is that when I try to install the PA gapps I get a FAILED message. Any help would be appreciated
Click to expand...
Click to collapse
Have you tried to install another rom on your nexus?
you can put it on with adb push command from recovery though a pc, and then wipe everything and try to install it.
Or you can download stock 4.2.2 rom here: http://forum.xda-developers.com/showthread.php?t=2147281
Here you can find your factory image directly from google: https://developers.google.com/android/nexus/images#occamjdq39
How do I adb push?
varem said:
How do I adb push?
Click to expand...
Click to collapse
you must enter into recovery, connect your phone to your pc with usb cable and then you should be able to see your device,
try
Code:
adb devices
on CMD and it can see your phone type
Code:
adb push **your-rom-from-computer** /sdcard/
then just install it from the recovery
When you say recovery do you mean the main menu? I'm using TWRP and when I'm on the main menu my PC doesnt read the device
http://forum.xda-developers.com/showthread.php?p=34674471
My bad I should have read.....you tried a tool kit already
Sent from my Nexus 4 using xda app-developers app
mmh i don't have twrp so i don't know, do you have the option to mount sdcard to usb?
varem said:
When you say recovery do you mean the main menu? I'm using TWRP and when I'm on the main menu my PC doesnt read the device
Click to expand...
Click to collapse
Ok, wait. I need some clarification. I'm going to try to be as simple as possible, to make sure we are on the same page. When you say your PC doesn't read the device, do you mean through adb or on Windows Explorer?
If you mean through Windows Explorer, then that is not where you need to be. You must get adb working as a bridge to your device. Use this sticky guide to get it set up. I would recommend reading that guide top to bottom anyway, it's extremely informative and new-user friendly. Anyway, the info you need is in the 'Setting up ADB for our device:' section.
If you have adb installed, you need to check to see if it recognizes your device. Do this by opening up cmd and navigating to the folder that adb.exe is located. After that, use 'adb devices' to see if adb recognizes your device. If so, move to the next paragraph. If not, your drivers aren't set up properly for recovery mode. Go into Device Manager on your computer and find your device (under something like 'Other devices', or 'Android device'). If you find it, then get these drivers and install them for the device. Do this by right-clicking, and selecting 'Update Driver Software...', 'Browse my computer for driver software', and browse to that folder. I may have missed a few steps on installing the drivers, it's been a while. If so, just search on how to do it, or post back here. I'm sure I can walk through it and get a more precise guide.
Assuming you have adb installed and it recognizes your device, you need to open up cmd and navigate to the folder that adb.exe is located. Then, use the adb push command as outlined above.
Download stock images from Google's website and flash it via fastboot. If you don't know how to do it then use a toolkit like WuguFresh to do it for you.
Sent from my Nexus 4
You can also use the toolkit for pushing a ROM in your SDcard, or backup your SD in your pc.
Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
The PC reads the device as it detects it but when I type in adb devices it doesnt show up. It only ever shows up when I enter the sideload menu in TWRP
atulalvenkar said:
Download stock images from Google's website and flash it via fastboot. If you don't know how to do it then use a toolkit like WuguFresh to do it for you.
Sent from my Nexus 4
Click to expand...
Click to collapse
Thanks man. This toolkit saved my nexus!
Sent from my Nexus 4 using xda premium
I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.
Motu88 said:
I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.
Click to expand...
Click to collapse
If your rooted just do a straight flash in recovery.. Please wipe 1st no dirty flashes then flash the kernel
sloanster said:
If your rooted just do a straight flash in recovery.. Please wipe 1st no dirty flashes then flash the kernel
Click to expand...
Click to collapse
Thanks for your reply. I have been flashing straight from the phone's memory, but I would still like to know what I can do to get the adb method working for future reference. If I accidentally get to a point where I can't boot properly and I don't have an available backup on the phone, I want to be able to flash from my desktop.
Motu88 said:
I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.
Click to expand...
Click to collapse
I had similar problems with TWRP. I ended up searching around Google and found some drivers that worked. Some keywords I used were the Hardware ID(s) that the unknown device gave to Windows, and "twrp". It's just using a different version of ADB or something, and Windows doesn't like it. I'm out of time for today, but I'm sure you'll find it. Look for google results that take you either to XDA or over to TWRP's website.
I need big help, my LG LS980 device is now bricked currently works only in recovery mode with ADB commands, any firmware I tried to upload I did not succeed
adb devices
List of devices attached
03xxxxxxxxxxxx07 sideload
adb sideload aokp_ls980_kitkat_unofficial_2014-01-16. zip
sending 100%
on my screen devices
finding update package
Opening update package
Verifying update package
Installing update
assert failed: run_program ("/system/bin/loki.sh") == 0
Installation aborted.
I've tried other firmware that is supposed to my device with similar result
You may need to restore to stock firmware but I can't figure out the process.
Is there anyone who can help me to restore the device
follow steps to reroot and push loki to device, reinstall recovery. try install again.
before redownload different rom and try to install that, aokp is buggy rom anyway, latest 16th build doesnt boot .
bachera said:
follow steps to reroot and push loki to device, reinstall recovery. try install again.
before redownload different rom and try to install that, aokp is buggy rom anyway, latest 16th build doesnt boot .
Click to expand...
Click to collapse
Thanks for your reply, my problem is that I don't understand how do reroot the device.
The device does not have many options, pressing the buttons (power and Vol +) the device enters in a State Factory Hard Reset.
Pressing (power and Vol-) goes into recovery mode and loads the black screen with anticipation for the adb commands
reboot system now
update from external apply sdcard
apply update from cache
apply update from ADB
wipe data/factory reset
wipe cache partition
With closed then press the device (Vol +) and connect the USB cable enters into Download Mode, here you also don't know what to do.
When I hit the power button just opens the device showing the logo of LG and the led flashing in green/blue and after a while makes itself restarted
I searched the forum for reroot and saw that need to do some settings on the device to do root, did I forget something and so I do not understand?
Sorry, I don't understand and become tedious but it's my first time playing with the object
so, you dont have recovery now?
"adb reboot recovery" not working ?
Based on what you said, you are able to get in recovery and adb is working, then push the ROM zip file over and reflash it in recovery.
I'm happy because I just unbrick my device by selecting Download Mode Firmware Update and with the LGFlashTools loaded LS980ZV8_ software 13.51097. tot.
Now I lie in my original problem, I want to unlock to accept SIM card from another provider and another country.
Some help to be able to start from somewhere the unlock process?
id3210 said:
so, you dont have recovery now?
"adb reboot recovery" not working ?
Click to expand...
Click to collapse
Who not any command except devices-sideload-kill server-start server-reboot
any other command, I was giving "error close"
votinh said:
Based on what you said, you are able to get in recovery and adb is working, then push the ROM zip file over and reflash it in recovery.
Click to expand...
Click to collapse
to command push, I was giving "error close"
But all ok, unbrick my devices with LGFlashTools
Great!
Good to hear that.
I need help as well. My phone ls980 is bricked only works in recovery TWRP. Can someone please help me?
antbox12 said:
I need help as well. My phone ls980 is bricked only works in recovery TWRP. Can someone please help me?
Click to expand...
Click to collapse
Did you accidentally accept that update too?
Sent from my SM-N900P using Tapatalk
natefuhr said:
Did you accidentally accept that update too?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
No but I fixed it. I had to put it in download mode and flash the stock rom back to it.
Hello Everyone. I need some help with restoring my shield because I seem to have soft-bricked it. Last week I rooted and installed a custom recovery file and all was well but this past weekend I was messing around with it trying to install the custom rom for full android and I think I accidentally deleted the boot file and the recovery file because all I get is the android on his back with the red triangle. Also, when I try to connect to the unit using fastboot nothing is found but I DO get a hit if I put the unit in stock recovery, it gives me the option to click apply update from adb.
From what I have been reading it sounds like I should be able to sideload the recovery and/or the stock firmware. Can anyone confirm or provide me with instructions on how to get this unit back up and running.
Any help is greatly appreciated
Wow I expected people to jump on this one. I guess I'll just keep messing around with it
Hy, here is the firmware and the instructions:
FW:
https://developer.nvidia.com/gameworksdownload (here you will have to scroll down to your console version PRO/non-PRO
Instructions:
http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
hpric said:
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
Click to expand...
Click to collapse
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
gffmac said:
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
Click to expand...
Click to collapse
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Beefheart said:
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
Click to expand...
Click to collapse
Correct. I can only use sideload at this time. Yesterday I was messing around with it a little more trying to sideload the recovery but I kept getting a message saying "The footer was incorrect" and it would cancel the install. I tried different files to make sure I wasn't dealing with a corrupted zip file but they all gave the same message.
I'm trying to figure out how to sideload the recovery
Beefheart said:
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Click to expand...
Click to collapse
Correct
Hello, I am facing the exact issue. Please let me know if you figured a way to debrick?
All I can do is ADB sideload and E:footer error keeps coming up.
Help is appricated,
Thanks