My LG-D802 was runnng jellybean and custom loader twrp v2.6.3.2 after receiving an update message, clicking update software app the phone restarted into the bootloader and any attempts to reboot resulted in and boot-loop.
what I tried:
First I wiped Dalvik cache and cache -didn't help
then I wiped Data -didn't help
then I wiped everything think I would get back to the stock loader.
so stuck in twrp I tried the LG support tools in windows but the program failed to find my phone.
I tried LGflash tools settign the phone driver to port com41 that also failed to detect my phone
all failed so I booted up my Debian OS managed to get adb push to work:
sent twtpv2.7 to /sdcard and ran an update
tried cm-11nightlyd02 with gapps then kernel-v3.3lgd802 -no luck
wiped everything again and installed:
testD802 80220B EUR Open.zip then KK_d802.zip then UPDATE-SuperSU-v1.93.zip
and after that no luck still in a boot-loop and not able to access download mode (vol+ and usb) tried draining the battery too
Please someone help, I think there might be some root system file missing
EDIT: fixed downlaod mode with:
abd shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Related
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!
Hey,
i've got a few problems with my HTC One S, running Cyanogenmod 11 (4.4.4) with TWRP as recovery.
Since a few days nearly every app crashes, ca. 3 minutes after I start the phone. In these minutes everything is working. After that there are only messages that "android.process.acore", "com.google.process.gapps" and nearly every other app has been closed. When I press OK, the message appears again.
So I tried to flash another ROM, which isn't possible because I first can't copy anything to the phone, the copying process stops after the half. I also couldn't download a ROM directly to the phone. Then I tried to flash again my actual ROM which is still on the phone, I selected the .zip in TWRP, but then the phone is restarting and nothing happened.
There are also other problems:
1. I tried a soft reset in the settings, isn't possible because nothing happens when i press the "Confirm" button
2. Clear storage and Factory reset in the boot loader isn't possible, when I select one of that the phone only starts into the recovery, without anything has been resetted
3. Pushing a zip with ADB doesn't work, it says I don't have permissions to copy anything on the storage
4. The ADB sideload mode doesn't start in TWRP
5. I tried to flash CWM as recovery, it says "successful", but when I start into recovery there is still TWRP..
6. Relocking the bootloader doesn't work, it also says "successful" but in the bootloader appears "*** unlocked ***" After that I tried to turn back to stock ROM with the RUU exe by HTC, but when the process starts, the phone just turns off.
Does anyone have a idea? Do I maybe have a virus? Sometimes it appears to me that there are problems with the storage or anything like that..
I really tried to do everything, and also searched in this forum and in other but I didn't find anyone with the same problem..
Thank you!
Give the Mount option a try in TRWP and see if you can copy a ROM over to the phone.
Okay I had to install the right driver for adb..
Then adb push worked, I could select the .zip in the Install option in TWRP, but the phone again just restarts without installing the rom..
ADB Sideload also worked with the driver, but after I tried to ADB sideload the ROM it said "* failed to write data 'protocol fault (no status)' *"..
I didn't find a thread for the Volt, model LS740 on Virgin Mobile. Rooted by the original owner. So I'm posting it here. I'm using adb on Ubuntu.
So I'm trying to repair a broken system by reflashing the stock ROM. I suspect the previous owner(who rooted) may have removed multiple important system apps. Upon doing a factory reset it has no home launcher or keyboard. As soon as the screen turns off it loops a com.android.systemui has stopped. Every boot you need to do a factory reset to get it to work: booting once, then again will loop the systemui crash, requiring a factory reset to work.
The android recovery works, I can get to it, but it offers install update from cache, adb, or sd card. The phone will not recognize sd card while it is in recovery, and adb doesn't work in recovery, only while booted. Copying recovery image to cache fails at 71%, I suspect the phone does not have enough RAM to move 1.17 GB from A to B. The phone may also not have spare storage space. I'm working on finding an sd card so I can try copying from there.
"adb reboot bootloader" reboots the phone normally. If there's a bootloader it skips it entirely. I found threads that say uncheck fast boot in power/battery options, but I have no such check box.
Right now, I have adb, images/zips for twrp recovery and stock rom, and I can push apks for a launcher and keyboard. But I apparently can't access bootloader or install rom via recovery. I don't have an sd card to try and copy the rom to cache, which I will try as soon as I get a card.
Adb cannot run as root, I get "adbd cannot run as root on production builds. So I can't directly push the rom to /cache/backup using adb.
Any help? I tried to get it all out there so that you guys could help better. Thanks for reading all that.
Fixed it by finding an LG recovery reflash utility and reflashing a factory version.
I have been playing around with viper4android and now my phone does not seem to boot.
It is stuck on the alcatel logo screen.
I do have TWRP backups, but I am unable to get into fastboot mode.
- Power + Volume UP brings the "stock" recovery, can I adb sideload twrp backup? Do I have to adb sideload stock rom?
- Power + Volume DOWN supposed to get me into the fastboot mode, but that always fails. How do I get into fastboot mode w/o adb (adb reboot-bootloader)
Power plus down puts the phone in "download mode" in preparation for running the Mobile Q windows software which can reset the phone to factory. It does not put you into fastboot. If you don't have twrp installed (rather dangerous to not have it when you are installing things that state they may hang the device) then your only hope is to use adb (if you had usb debugging enabled) to reboot to bootloader so you can flash twrp or use the mobile Q software to reset your phone to factory.
Got it!
So after installing the Mobile Upgrade Q, and 30 minutes the phone is back to life.
twrp restored the backups w/o any issues.
However, now it seems that I am unable to flash supersu.zip, twrp installs it w/o any issues, but once the phone boots, there is no root, and /system/xbin/su does not exist, and Xposed installer fails, since /system is read-only, which seems weird to me.
I do not think I am missing anything
famewolf said:
Power plus down puts the phone in "download mode" in preparation for running the Mobile Q windows software which can reset the phone to factory. It does not put you into fastboot. If you don't have twrp installed (rather dangerous to not have it when you are installing things that state they may hang the device) then your only hope is to use adb (if you had usb debugging enabled) to reboot to bootloader so you can flash twrp or use the mobile Q software to reset your phone to factory.
Click to expand...
Click to collapse
It appears that TWRP is having issues with /system partition now and it's in the read-only mode.
Here is the twrp log, with all the read-only issues:
http://pastebin.com/1mU1ykHs
JupoozunEd3 said:
It appears that TWRP is having issues with /system partition now and it's in the read-only mode.
Here is the twrp log, with all the read-only issues:
http://pastebin.com/1mU1ykHs
Click to expand...
Click to collapse
Go in advanced twrp settings and allow r/w of system.
famewolf said:
Go in advanced twrp settings and allow r/w of system.
Click to expand...
Click to collapse
That did not help either, nor "doing a mount -o rw,remount /system" from the TWRPs terminal. I think the issue was caused by restoring ALL partitions via TWRP (system, system image, efs, data, boot)
After a session with Mobile Upgrade Q, and just restoring /data, all is back to normal.
Hello all,
The phone was previously rooted, I just wanted to retry to get rid of the optimizing app problem. With that said, the phone is rooted, and I previously had USB debugging enabled. I reset to factory using the Android Recovery, so does this mean USB debugging was not enabled after resetting?
These were my steps:
Install and run KingRoot
Purchase Super-Sume Pro ($4) to replace KingRoot with SuperSu
On reboot it got stuck in boot loop. I have tried Android System Recovery (lmy47v) but my options are only
Code:
>reboot system now
>wipe data/factory reset
>wipe cache partition
>reboot to bootloader
>power down
>view recovery logs
I have tried all of these options several times.
I have installed ADB on windows as well as the Kyocera drivers here: kyoceramobile.com/support/drivers
I have not been successful in getting access to the phone with ADB.
I have tried to get the phone into fastboot mode by combinations of key presses, but I have not been successful. Does this phone have fastboot? Here are the recovery logs: imgur.com/a/Sn9zD
What is left? I really like this phone and use it as a waterproof GPS and would have to have made a paperweight out of it. Please help!
Hey all, looking for some general Android wisdom on how to get my phone to a state where the computer can detect it as a USB device so that I can use ADB or some other method. What are my options?
advhound said:
Hello all,
The phone was previously rooted, I just wanted to retry to get rid of the optimizing app problem. With that said, the phone is rooted, and I previously had USB debugging enabled. I reset to factory using the Android Recovery, so does this mean USB debugging was not enabled after resetting?
These were my steps:
Install and run KingRoot
Purchase Super-Sume Pro ($4) to replace KingRoot with SuperSu
On reboot it got stuck in boot loop. I have tried Android System Recovery (lmy47v) but my options are only
Code:
>reboot system now
>wipe data/factory reset
>wipe cache partition
>reboot to bootloader
>power down
>view recovery logs
I have tried all of these options several times.
I have installed ADB on windows as well as the Kyocera drivers here: kyoceramobile.com/support/drivers
I have not been successful in getting access to the phone with ADB.
I have tried to get the phone into fastboot mode by combinations of key presses, but I have not been successful. Does this phone have fastboot? Here are the recovery logs: imgur.com/a/Sn9zD
What is left? I really like this phone and use it as a waterproof GPS and would have to have made a paperweight out of it. Please help!
Click to expand...
Click to collapse
Hi..my XD bootloop too..BTW how to get in Android System Recovery?
Did you ever fix your phone?
I saw that the post just stops with you needing help