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
Related
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
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.
I have an old Moto G 1st gen, and I forgot its password. Now I'm trying to hard reset it, or do whatever necessary to wipe everything, but no success. I have already tested all options below with the bootloader unlocked, but USB debugging mode is off.
Things I have tried:
1) Hard reset and wipe data from boot menu. Here it says its cleaning, with no error, but when the phone reboots, nothing have changed and no data was erased.
2) Install the stock firmware, both kit kat and lollipop roms in fastboot. Here it copies all files, without any error, reboots the phone but nothing have changed either!
3) Tried to install any custom recovery, but no success because it has USB Debugging mode off. Besides that, I tried to load the custom recovery into RAM and runs it from there (read here the thread), but the phone reboots in the stock recovery.
4) Tried to erase the password with Android Multi Tools, but since USB Debugging is off, ADB commands are not working.
I'm lost and don't know what options I have left.
Hi !
I see that you`re getting help here https://forum.xda-developers.com/mo...set-moto-g-t3539447/post70585087#post70585087
Thread closed
I have an old Moto G 1st gen, and I forgot its password. Now I'm trying to hard reset it, or do whatever necessary to wipe everything, but no success. I have already tested all options below with the bootloader unlocked, but USB debugging mode is off.
Things I have tried:
1) Hard reset and wipe data from boot menu. Here it says its cleaning, with no error, but when the phone reboots, nothing have changed and no data was erased.
2) Install the stock firmware, both kit kat and lollipop roms in fastboot. Here it copies all files, without any error, reboots the phone but nothing have changed either!
3) Tried to install any custom recovery, but no success because it has USB Debugging mode off. Besides that, I tried to load the custom recovery into RAM and runs it from there (read here the thread), but the phone reboots in the stock recovery.
4) Tried to erase the password with Android Multi Tools, but since USB Debugging is off, ADB commands are not working.
I'm lost and don't know what options I have left.
henriquebs12 said:
I have an old Moto G 1st gen, and I forgot its password. Now I'm trying to hard reset it, or do whatever necessary to wipe everything, but no success. I have already tested all options below with the bootloader unlocked, but USB debugging mode is off.
Things I have tried:
1) Hard reset and wipe data from boot menu. Here it says its cleaning, with no error, but when the phone reboots, nothing have changed and no data was erased.
2) Install the stock firmware, both kit kat and lollipop roms in fastboot. Here it copies all files, without any error, reboots the phone but nothing have changed either!
3) Tried to install any custom recovery, but no success because it has USB Debugging mode off. Besides that, I tried to load the custom recovery into RAM and runs it from there (read here the thread), but the phone reboots in the stock recovery.
4) Tried to erase the password with Android Multi Tools, but since USB Debugging is off, ADB commands are not working.
I'm lost and don't know what options I have left.
Click to expand...
Click to collapse
Have you tried "factory data reset" option in custom recovery.. because it worked for me when i faced the same problem
on recovery "wipe>advance wipe>check all"
tried?
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?