Hi,
all of a sudden, my XT1039 Moto G has entered a never ending bootloop that goes like this:
- powers up, motorola animation runs fine
- if the sim is inserted, it lets me tap the numbers for 5 seconds, then it soft reboots by itself
- if the sim is not inserted, it loads fine, it lets me do what I can do in 5 seconds, then it soft reboots by itself
my XT1039 is totally stock, unrooted, the last app I've installed is a flashlight app from the Google App Store, to turn on and off the back led, three days ago, and has been working fine for three days since then.
What I have done so far:
- booted android to safe mode: 5 seconds, and it bootloops again
- booted to recovery and wiped the cache partition, rebooted to android and the problem is still there
- when powered off, held the vol up and down buttons for two minutes: somebody wrote it worked for him, it doesn't work for me
- tried all the other options on the recovery menu (Factory, BP Tools, QCOM), but they all seem to do nothing, and get me again to the bootlooping
- booted to flashboot with an otg cable and a usb pendrive, hoping a magic "backup to usb" option would show up, but it doesn't
- disconnected the battery for 5 minutes, and replaced it with a known good working one out my wife's XT1032 (same battery model), still no luck
now I'm almost ready to boot to recovery and wipe data/factory reset, but I still would like to copy the Pictures folder out of the device first, so I tried with adb:
- installed the Motorola (and the universal too) drivers on my Win 8.1 and downloaded a recent version of adb.exe (Android Debug Bridge version 1.0.32)
- during the 5 seconds of bootloop life, I can browse the XT1039 folders from Win 8.1 explorer, but 5 seconds is too short to do anything
- booted the XT1039 in flashboot, but the command adb devices doesn't see my device
- while in flasboot, navigated in Recovery --> Apply Update from ADB, the Win 8.1 alerts me there's something new on the USB chain, and adb devices says:
List of devices attached
TA98601*** sideload
but in the sideload mode it seems I can't run the pull command to get my files out of the damned device, every command like adb pull, push, shell, returns the same error:
error: closed
Is there anything else I can try to get my files out of the XT1039, before restoring it to factory ?
Any hint is highly appeciated, thanks
I can see that you were able to boot into recovery, and assuming that you are using a recent version of TWRP, you can attach the device to a computer via USB while in TWRP. and copy the pictures folder that way.
Hope this helps
Edit: It sound like you were using the stock recovery, so boot into fastboot mode and flash the recovery with instructions from here.
Professor Gibbins said:
I can see that you were able to boot into recovery, and assuming that you are using a recent version of TWRP, you can attach the device to a computer via USB while in TWRP. and copy the pictures folder that way.
Hope this helps
Edit: It sound like you were using the stock recovery, so boot into fastboot mode and flash the recovery with instructions from here.
Click to expand...
Click to collapse
You can't install TWRP with a locked bootloader, and unlocking the bootloader wipes data...
Of course. It never actually occurred to me that the bootloader would be locked.
Although, have you tried running
Code:
adb kill-server
adb start-server
and trying the 'adb pull' commands again?
Professor Gibbins said:
Of course. It never actually occurred to me that the bootloader would be locked.
Although, have you tried running
Code:
adb kill-server
adb start-server
and trying the 'adb pull' commands again?
Click to expand...
Click to collapse
Yes, unfortunately the bootloader is locked, the phone is stock as if just bought out of a shop.
Here's the sequence of commands ran while in fastboot
C:\adb>adb kill-server
* server not running *
C:\adb>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb devices
C:\adb>adb pull /system/app/Settings.apk
error: device not found
and the here's the sequence of commands ran in fastboot-->recovery --> apply update from ADB (the only option I've found that seems to enable some adb functionality)
C:\adb>adb kill-server
C:\adb>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb devices
List of devices attached
TA98601*** sideload
C:\adb>adb pull /system/app/Settings.apk
error: closed
Related
I have been running AOKP. I have tried booting the phone numerous time and have had no luck. Power+Vol down doesn't get me anywhere either, it is just stuck on the "htc quietly brilliant - This build is for devlopment purposes only. Do not distribute outside of HTC ......"
Is it possible being only on this screen to use adb to clear cache, or is the phone toast? How can the battery dying kill the phone on the next boot?
SilentLunatic said:
I have been running AOKP. I have tried booting the phone numerous time and have had no luck. Power+Vol down doesn't get me anywhere either, it is just stuck on the "htc quietly brilliant - This build is for devlopment purposes only. Do not distribute outside of HTC ......"
Is it possible being only on this screen to use adb to clear cache, or is the phone toast? How can the battery dying kill the phone on the next boot?
Click to expand...
Click to collapse
Have you charged it? I know it sounds obvious lol... but you never know.
And try to see if you can get adb initializing by booting your phone, letting it sit at the bootsplash for 10 seconds or so, and then in a command prompt type "adb devices" and see if you get your device's serial number back.
rohan32 said:
Have you charged it? I know it sounds obvious lol... but you never know.
And try to see if you can get adb initializing by booting your phone, letting it sit at the bootsplash for 10 seconds or so, and then in a command prompt type "adb devices" and see if you get your device's serial number back.
Click to expand...
Click to collapse
Will def try. I did get it booted into CWM. It says it cannot mount the sd card. I do not know how to push a file to it if I can't mount it. I cannot see the AOKP.zip file I used either when I try to "choose update from zip".
Trying the adb now though. Will be back with results.
SilentLunatic said:
Will def try. I did get it booted into CWM. It says it cannot mount the sd card. I do not know how to push a file to it if I can't mount it. I cannot see the AOKP.zip file I used either when I try to "choose update from zip".
Trying the adb now though. Will be back with results.
Click to expand...
Click to collapse
Is the CWM recovery that you have the one with the fixed adb?
Go to command prompt and when in CWM run adb devices.
If you get your device, to mount your sdcard then run this:
adb shell mount /sdcard
Then try pushing the update.zip again.
If that doesn't work, then from CWM and adb again, reboot into bootloader (adb reboot bootloader), get into fastboot mode (wait till it says "fastboot usb"), and then run the RUU.
rohan32 said:
Is the CWM recovery that you have the one with the fixed adb?
Go to command prompt and when in CWM run adb devices.
If you get your device, to mount your sdcard then run this:
adb shell mount /sdcard
Then try pushing the update.zip again.
If that doesn't work, then from CWM and adb again, reboot into bootloader (adb reboot bootloader), get into fastboot mode (wait till it says "fastboot usb"), and then run the RUU.
Click to expand...
Click to collapse
X:\Android SDK\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT24LW304682 device
X:\Android SDK\platform-tools>adb shell mount /sdcard
- exec '/system/bin/sh' failed: No such file or directory (2) -
Guess I'm going to try the RUU now...
SilentLunatic said:
X:\Android SDK\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT24LW304682 device
X:\Android SDK\platform-tools>adb shell mount /sdcard
- exec '/system/bin/sh' failed: No such file or directory (2) -
Guess I'm going to try the RUU now...
Click to expand...
Click to collapse
RUU cannot update the phone. Encountered Error [155]
Currently sitting on the black htc logo screen when it's trying to flash the stock image.
SilentLunatic said:
RUU cannot update the phone. Encountered Error [155]
Currently sitting on the black htc logo screen when it's trying to flash the stock image.
Click to expand...
Click to collapse
I wanted to note that I did re-lock the bootloader.
Fixed! Beat the phone on the desk, ran for the 5th time and it worked. Flashing TWRP now and back to AOKP I come. Mods please close this thread, and HUGE thanks to rohan32.
In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.
HOW-TO Root, Install Custom Recovery (TWRP) and Restore Stock ROM guide: https://docs.google.com/presentation/d/1NJcDBkLk8zMwyv2BTqRjn2NB_ZOWKjP1fRpSVr44Oxk
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 7.0)
- Latest Official: http://www.oukitel.com/latest-software-rom-for-all-oukitel-devices-48.html
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Previous Releases:
None yet.
Flash Tool
- Latest SP Flash Tool for Windows and Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A
Recovery:
- TWRP 3.1.1 by @jemmini (V23 based): https://mega.nz/#F!VwZU3bYY!57unJW8bd9h220AkJecing
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu
Extras (Root-Only):
Customization
- Xposed Framework (not available on Nougat yet): http://forum.xda-developers.com/showthread.php?t=3034811
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
Issue installing TWRP via SP Flash Tool
Thanks for posting this OUKITEL K6000 Plus Support thread.
However I am having an issue; I can only get down to page 11 in the ‘HOW-TO Root, Install Custom Recovery (TWRP) guide’ as I get error messages, please see attached images.
This is not my first attempt at installing just TWRP (nothing else) on my otherwise stock OUKITEL K6000 Plus, before this thread was posted I attempted to follow Appuals guide https://appuals.com/root-oukitel-k6000-plus/ just the TWRP Recovery bit; but this did not complete as it should have done.
Any help or suggestions would be much appreciated.
I got problem at this k6000 plus when I take a photo on a cross side he cut the Image
When I take photo on a cross side the camera keep the image on vertical but cut the image please help how to solve it
Alberto96 said:
Recovery:
- TWRP 3.1.1 by @jemmini : https://mega.nz/#F!oYNTnJaS!NeH0wz4v1ezR1VBul6eLdw
Click to expand...
Click to collapse
It's 3.1.0 not 3.1.1
And I think it breaks stock Rom version V23 - when I'm booting into this recovery, system won't boot later and I have to re-flash it with flashtool.
rolex0815 said:
It's 3.1.0 not 3.1.1
And I think it breaks stock Rom version V23 - when I'm booting into this recovery, system won't boot later and I have to re-flash it with flashtool.
Click to expand...
Click to collapse
Need to wait for a repack from @jemmini then.
I get a Bootloop into recovery TRWP only and cant flash with spalshtool anymore,get an Error 60003 ??
can anyone help?
@jemmini made new TWRP 3.1.1 for ROM v23
All hail @jemmini!
Download:
https://mega.nz/#F!VwZU3bYY!57unJW8bd9h220AkJecing
TWRP ask for a Password??
Yeah, and for me my phone password not working but u can click cancel or sth like that and you'll see twrp menu
cojo11 said:
TWRP ask for a Password??
Click to expand...
Click to collapse
Even if you don't have any password, you will get this prompt unless you format /data. (Encrypted Storage)
I erased userdata with
Code:
fastboot erase userdata
Phone shows still encryption status - I don't know why.
Newest TWRP still not working for me,
Code:
fastboot boot recovery
breaks system boot process.
Is it working for anyone? Am I doing something wrong? I don't want to flash it completely.
I'm on V23 and already losing some happiness ...
For me TWRP working with adb sideload but I can't decrypt data storage in TWRP. But finally I have root on v23
PS: Magisk working fine!
Eselter said:
For me TWRP working with adb sideload but I can't decrypt data storage in TWRP. But finally I have root on v23
Click to expand...
Click to collapse
Can you explain what you mean TWRP with adb sideload?
I flash or boot TWRP via fastboot.
And you flashed SuperSU or Magisk via adb sideload when recovery is booted?
I flash su from sideload and OTG both working fine. TWRP itself I install via SP Flash Tool.
boots directly in TWRP?
Hi everyone,
after installing twrp and supersu my phone stuck on the bootlogo like rolex mentioned in Post #4
i've also erased user data vis fastboot (wich wasn't that smart) and now it directly boots into twrp
can someone explain me pls how i get the stock rom back on my phone?
i'm so lost
how do i remove the password at the start in TWRP ?
With V23 /data partition is encrypted, TWRP asks for a password.
I solved it that way that I wanted to have root and a non-encrypted data partition:
flash (or boot) TWRP
hit cancel at the password question
format /data
flash SuperSU
It is crucial that SuperSU (or maybe Magisk, don't know about Magisk) is flashed during TWRP session because system is stuck otherwise.
Some mods
I tweak my device a little and I want to share some tips
Enable navbar and disable hardware buttons and backlighs:
Open /system/build.prop (I'm using Solid Explorer)
Find line with qemu.hw.mainkeys and change value to 0 this enable software navbar
In the same file you can change dpi "ro.sf.lcd_density" (I prefer 401 = ppi our phone)
Open system/usr/keylayout/Generic.kl and comment this line (add # on start):
- key 139 MENU - this disable menu button
- key 158 BACK - this disable back button
- also you can disable home button (I don't do that), key 172 HOME
To disable backlight you need init.d support:
- Download backlight_off.sh.txt from attachment and remove .txt extension
- If you are using Magisk copy backlight_off.sh to /magisk/.core/post-fs-data.d
- I don't know if SuperSU have init.d support so you can use init.d scripts support app, and put backlight_off.sh to internal memory/init.d
I also modded SystemUI:
added space after "Free:" in recent apps
Changed M to MB ex. Free: 2000MB / 3813MB
Fiixed some polish translation, and also added MB to toast after cleaning memory
Changed margin bottom increasing it by 5 dip to better fit with navbar
Disable pressing home button after clearing memory (I'm using Nova and when I clear memory it automatically go to app drawer and I don't like it )
App is deodexed now = easy modding
Copy and replace new SystemUI.apk from attachment to /system/priv-app/SystemUI
Orange State
Good afternoon,
Friends, already tried everything else continues to appear the message of the "Orange state", and the following image:
When I connect the device does not start at all just put this same message!
C:\adb>adb kill-server
C:\adb>adb start-server
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
C:\adb>adb devices
List of devices attached
0123456789ABCDEF unauthorized
C:\adb>adb devices
List of devices attached
0123456789ABCDEF unauthorized
C:\adb>adb devices
List of devices attached
0123456789ABCDEF unauthorized
C:\adb>adb kill-server
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
0123456789ABCDEF unauthorized
C:\adb>
C:\adb>adb reboot-bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
C:\adb>
Thank you very much in advance!
Ps: Did I lose my cell phone?
Lucasiron said:
Good afternoon,
Friends, already tried everything else continues to appear the message of the "Orange state", and the following image:
When I connect the device does not start at all just put this same message!
C:\adb>adb kill-server
C:\adb>adb start-server
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
C:\adb>adb devices
List of devices attached
0123456789ABCDEF unauthorized
C:\adb>adb devices
List of devices attached
0123456789ABCDEF unauthorized
C:\adb>adb devices
List of devices attached
0123456789ABCDEF unauthorized
C:\adb>adb kill-server
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
0123456789ABCDEF unauthorized
C:\adb>
C:\adb>adb reboot-bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
C:\adb>
Thank you very much in advance!
Ps: Did I lose my cell phone?
Click to expand...
Click to collapse
no, had the same problem.
just flash the stock back again, this solved it in my case
OUKITEL K6000 Plus in Canada on Bell network
Hi, I just receive a Oukitel 6000 plus. It was a winning prise in a manager party. I think the person who bring this up was from Australia.
Anyway, I win it and It sits there since 2 weeks now. I just take it and try my sim card in it. The card is recognised but no connections on the network.
I verify on the (frequency check) web site and it is supposed to work in Canada.
I'm unable to find if this device is locked or not, and also, I wanted to know if it is possible to change the band on it.
Not sure if we root it, it will allow me to change the radio settings.
It looks like a great phone, so I'd like to have it as my phone.
Thanks for your help!
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the
Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the
Click to expand...
Click to collapse
You can't see the device while on fastboot mode of you type adb devices.
You need to make sure debugging is on in the developer preferences.
ADB appears to be working just fine for me.
When using adb make sure you have debugging enabled and grant the popup on screen
adb is not fastboot. You can use adb on twrp or booted system. Fastboot is on bootloader mode.
Also need to make sure that the proper USB drivers on the computer are installed/updated.
Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
Click to expand...
Click to collapse
This is working exactly as intended, and not exclusive to Android 10, but rather has been the case as long as I can remember (Jelly Bean? KitKat? Maybe much earlier?):
adb: Only works when booted to OS or in TWRP. Debugging required to be toggle on in phone settings. Does not work in bootloader-fastboot mode.
fastboot: Only works in bootloader-fastboot mode. Debugging is not required to be toggled on.
D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...
Bringer1 said:
D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...
Click to expand...
Click to collapse
Sounds like another adb server is still running. What does adb kill-server and then trying again do
a second adb server was running.
TNX
Can I mount system rw using adb enabled recovery img from the following link:
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
On my Rooted Pixel 4a, I can use:
Fastboot - I flashed the latest update firmware as well as the rooted boot image
ADB Over WiFi - This is the most comnon way I connect for ADB
ADB While the Android OS is running
What I cannoit get woirking is ADB while in recovery mode,
If I go to recovery and connect via a high quality cable, I can see the device with
Code:
adb devices
C:\Java\x86\Android\android-sdk\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
091????????490 rescue
Click to expand...
Click to collapse
But none of the below works
Code:
>adb shell
error: closed
>adb connect 091XXXXXXXX490
cannot resolve host '091XXXXXXXX490' and port 5555: No such host is known. (11001)
>adv shell 091XXXXXXXX490
error: closed
What am I doing wrong? how can I connect in recovery?
Stock recovery?
WillisD said:
Stock recovery?
Click to expand...
Click to collapse
Yes.
DiamondJohn said:
What I cannoit get woirking is ADB while in recovery mode
Click to expand...
Click to collapse
I always thought that adb from recovery was a TWRP thing?
I did adb reboot recovery. My phone has an Android on its back, with "No command" on the screen.
Code:
$ adb devices
List of devices attached
xxx unauthorized
$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I got the same thing booting to recovery by holding Vol down at boot.
Booting to rescue (another option on the boot menu) got me the same thing on my screen and the same symptom you saw.
Code:
$ adb devices
List of devices attached
xxx rescue
$ adb shell
error: closed
Are you sure this is supposed to work with the stock recovery?
a1291762 said:
Are you sure this is supposed to work with the stock recovery?
Click to expand...
Click to collapse
Actually no, i guess it was an assumption, and the response to adb devices, gave me further hope.
However,, it does respnod to ADB. As is seen, it provides a list of devices. But, maybe one can't shell out while in stock recpvery. Which goves me an idea, maybe we can send commands from the command window in windows/linux. eg adb shell ls But it wouldn't make sense that it would allow root, which negates what I wanted to be able to do in the first place. ie recovery from a bootloop by selectively editing the data partition. in my previous case, it was to disable a single magisk module.
DiamondJohn said:
It wouldn't make sense that it would allow root, which negates what I wanted to be able to do in the first place. ie recovery from a bootloop by selectively editing the data partition. in my previous case, it was to disable a single magisk module.
Click to expand...
Click to collapse
Yeah, it certainly seems to be speaking adb...
I didn't think to try...but maybe adb push and pull work?
So my screen broke on my Note 10+, leaving only the top 15% with display and the bottom 60% with touch. I am trying to activate ADB on it so that I can backup my internal storage.
I booted into TWRP so that I could backup the rest of my system, which I did successfully, but because of the bad touch screen I am unable to hit the ADB side load button. I'd like to reboot into the system because I have ADB enabled there, however I also cannot click the reboot to system button, only reboot to download and shutdown. Since I can't see most of the screen, it is also not possible to access the terminal and work from there.
Anybody know how I can escape TWRP or otherwise activate ADB? Thanks for the help.
Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload
jwoegerbauer said:
Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload
Click to expand...
Click to collapse
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.
AllanRSS said:
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.
Click to expand...
Click to collapse
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot
jwoegerbauer said:
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot
Click to expand...
Click to collapse
I can not use ADB. It is for this very reason I am asking how to enable ADB. But thank you for these valuable ADB commands, I'll be sure to reboot my system once I enable ADB