[Solved] Stuck in recovery, adb kinda working? - AT&T LG G2

Hi, I could use a little help. I've flashed a few roms before, but I really got myself into a tough spot this time. I downloaded Slimrom because the one I flashed before that would slow my device down and generally just didn't run as good as I had hoped. I went into TWRP recovery, wiped the caches, flashed the rom and gapps, but it said that the archive/s were corrupt. I have a few backups, but they are all on an external hard drive. I knew I had to get the Android SDK, Java JDK, New ROM, and use adb if I wanted to fix it, but this is where I've been running into a few problems.
I made sure that the drivers for the phone were installed, I kept getting errors though. I looked at the device manager and it shows the yellow triangle and if I try to troubleshoot it says that there are no compatible drivers for my phone. I looked back at the device manager and noticed it connected with the Media Transfer. I can see the device in adb at the bootloader, but not at the recovery. When I push the rom to the phone from the bootloader using adb push ROM.zip /sdcard/ROM.zip. This fails to copy and says there is no directory. Using adb push ROM.zip /sdcard/ it fails and says it is a directory. I've tried more than this, but I can't seem to get it pushed/sideloaded onto my d800 G2.
Thanks in advance for any help or advice. I apologize if I have been doing it wrong the whole time, it's my first time having to use adb.
UPDATE: I got it into download mode and flashed the stock KK update. Thanks anyways

Related

[Q] Botched TWRP upgrade, now lost root access

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?

Stuck on CWM when trying to install CM10.2.1

Hello,
I got this HTC One X from AT&T (->evita) and tried to get CM 10.2.1 running on that.
The steps I made:
Boot into bootloader, go to fastboot, then get the identifier, get unlock token via htcdev and unlocked it with fastboot.
I then flashed CWM 6.0.4.6 for evita via "fastboot flash recovery *filename*". Now I booted into CWM (recovery) and wiped everything instead of first trying to copy the cm.zip onto the sdcard. (I also didnt do this when the stock ROM was still running...)
Now I can access the phone via fastboot in the bootloader but I can not use adb or the USB mount when in CWM. Whenever I plug the phone into my computer (or laptop, doesn't matter. Also tried switching between USB 2 and 3 ports!) Windows keeps making the "unplugged" sound every second.
Reinstalling the latest HTC drivers did not change anything.
Anyone here knows a way how I can stop that or get the zip file on the memory? I also tried flashing the boot.img on boot and tested if I can copy the file then through CWM but that did not work.
Hoping,
NyphoX
Not sure if it'll work but try using TWRP recovery instead:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita
Installed the most recent version.
I get into the recovry and when I plug it into a computer Windows will keep making the "unplugged"-noise.
I can see the sdcard-directory perfectly when I hit install in both, TWRP and CWM but when I want to mount it via USB it will not change anything and I cannot access it on my PC.
adb doesn't list any device either.
Also, TWRP and CWM keep telling me that my phone is not rooted, when I try to power off or restart. Is that normal?
My other HTC One X (non AT&T) just works fine with cwm 5.*.*.*
It's normal for the recovery to inform you that you're not rooted, it'll suggest that you install superuser but there's no point doing that in your case because you have no working OS installed. Did you at any point perform a factory reset from the bootloader? If so, you've corrupted the internal storage (known bug on modified Evitas) and will need to wipe it with TWRP.
Sent from my Evita
Saw that in your Q&A.
I wiped the internal_sd and tested it after but it still did not work. I also tried a factory reset through TWRP but that did not help either.
Both recovery programs keep telling me "E:Unable to mount '/cache'.
Still not working. Q_Q
Update: I got like the oldest laptop I ever owned and installed the most recent HTC drivers there and tried to mount it. It told me in device manager that the "evita" is not recognized. When I let Windows search automatically it installed the drivers and I am now able to access the memory.
I can only assume what the problem was but it seems like the HTC One X (endeavoru) driver and the evita don't like each other...
TL;DR trying to install now. Will edit.
//EDIT: Windows still screws when I plug the phone to the other computer/laptop, so I just have to use the old machine now. Still thanks for your help, timmaaa!
//EDIT: It does work when I booted CM and enable the USB storage at the other two machines.

[Q] ADB not finding device?

Quick note: I'm very new to all this so I don't really know entirely what's going on.
Alright, basically I'm trying to install the Paranoid Android ROM and I've run into a bit of an issue. I've unlocked the bootloader and flashed the ClockworkMod Recovery. The problem I've ran into is that when I go into the CWM recovery and attempt to do anything with ADB it comes up with "error: device not found"
What am I doing wrong?
Sidenote: ADB can find my phone if it's booted up normally, it's only when I boot to the CWM custom recovery that it can't find it...
I think you are doing it wrong way buddy..
Boot in to Bootloader mode not in CWM Recovery, then try with fastboot and check again..
I did boot into bootloader, then went to CWM and tried to push the ROM using ADB but it wasn't recognising my phone.
Doesn't matter now anyway. I got around it by literally just drag and dropping the zip files onto my phone's internal memory when it was booted up normally and connected to my PC. Then I rebooted into the bootloader, flashed CWM and installed from ZIP. That method was far easier than messing around with ADB etc.

[Q] Wiped in TWRP then flashed new ROM... now can't boot to recovery and boot looped

Everything was working fine but I haven't updated my ROM (Mokee ROM in my sig) in a long time. I also wanted to just start fresh. So, I rebooted into recovery and wiped absolutely everything. I downloaded the same (but updated) ROM I was using before. I put the files on a microSD and put the microSD into the tablet. I flashed the ROM and then GApps as described in the instructions and then rebooted. Now I am stuck in a boot loop. At first, I thought maybe the downloaded files were corrupt. So I downloaded them again on another computer. It didn't change a thing.
But every time I try getting into recovery mode, it just boots to the ROM. So how do I get things up and running again? I'm comfortable with the command line but right now ADB and Fastboot dont see the device. I've installed the USB drivers and 15 second ADB/fastboot install on Windows. I've never had this problem and haven't found anything online yet that provides a solution. What now?
x000111 said:
Everything was working fine but I haven't updated my ROM (Mokee ROM in my sig) in a long time. I also wanted to just start fresh. So, I rebooted into recovery and wiped absolutely everything. I downloaded the same (but updated) ROM I was using before. I put the files on a microSD and put the microSD into the tablet. I flashed the ROM and then GApps as described in the instructions and then rebooted. Now I am stuck in a boot loop. At first, I thought maybe the downloaded files were corrupt. So I downloaded them again on another computer. It didn't change a thing.
But every time I try getting into recovery mode, it just boots to the ROM. So how do I get things up and running again? I'm comfortable with the command line but right now ADB and Fastboot dont see the device. I've installed the USB drivers and 15 second ADB/fastboot install on Windows. I've never had this problem and haven't found anything online yet that provides a solution. What now?
Click to expand...
Click to collapse
Restore backup or flash some other Rom,
Sent from my GT-P3100 using Tapatalk
Yes, that is what I'd like to do. But how would you suggest doing that since I cannot get into recovery and am stuck in a boot loop?
Whew... I let the tablet sit for a couple of days while I worked on other things. I decided to try, just for the heck of it, to put it into recovery mode (Power+Vol Down) and it worked. I already had a new ROM ready to install on my microSD and did it. It looks like CM10 is going to be my ROM now. It installed and is running! What a relief!
It must not have been shutting down all the way before. Even though I saw the Samsung Galaxy Tab logo, there must have been something it didn't like at the time. No idea besides that.

How to finish rooting unlocked Blu J1 Marsh 6.0 phone with Adb

Okay, happy post Vday. :good:
So, Im trying to root an unlocked Blu J1, running Marsh. 6.0.
I recently reset it, due to perf. issues & now trying to root.
My setup is Win7, w/ the latest Usb drivers through Sdk & UniversalAdb. I have Usb debugging active on the phone & the device shows at command level with Adb devices & in Fastboot mode**Ive unlocked the bootloader on the phone itself, & then xferred the Twrp.img files different times.
The twrp files were the latest 2 off the site Twrp.me as of 02/15. Its a successful transfer on fastboot, which is good. but when I go to restart, it shows as stock recovery studio_j1_6.0/user/release-keys but not the touch responsive Twrp. ..
I eventually want to use Su or Magisk zip to gain root. The phone remains bootloader unlocked which is good. I've tried the Adb command, adb root, and then went through these steps, -still nothing. Im on the hunt for recent clockwork mod, to try that way, only ones are like '11 or'12.
So, is the stock recovery hard coded. -it doesnt have 2 separate partit-I ran a partit check just in case. I also went to grab the omnirom androidrecovery 6.0 off Github at github.com/omnirom/android_bootable_recovery/tree/android-6.0, but its .zip. And when I apply updates through Sd card update in stock recovery, I get install aborted across the board on any .zips.. Im on the waiting list for Kingroot to add my device. so thats good.
Either way Android SU shows as not rooted once fully on.
Any feedback greatly appreciated.

Categories

Resources