As the title says. I am trying to use ioroot25 and when I get to the recovery stage to push from adb, the iroot .bat says,
"error: device not found"
This is confusing me because each time I try to do this, I open up a separate cmd window and do "adb devices" and it tells me that my phone is connected. Not to mention that when adb DOES NOT detect my device, I can't even get to this step of ioroot.
All of this comes from me having numerous issues with CM11 (after installing from Malladus 2.0.3, had TWRP as recovery), so I decided to wipe clean and start over again. I used the LG Flash tool and flashed the correct Verizon 24a_11.kdz. Then I tried to root after checking the device was operational and adb couldn't find my device. I then did a factory reset through the phone as the restored version was acting a bit goofy, and this is where I'm at now.
Related
Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic
I have not received the OTA update to Marshmallow yet and getting impatient so I'm attempting to sideload the update myself. I've installed the SDK and drivers. The device is listed when I use 'adb devices' at the command prompt and it allows me to boot into the bootloader. But from there it disconnects from my computer and I'm not able to push the update to the device. I get "error: device '(null)' not found". Any advice?
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Didgeridoohan said:
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Click to expand...
Click to collapse
Ok, but all the instructions I'm finding online to sideload the OTA say to type "adb sideload [the full name of the file].zip". This is after enter Recovery Mode and select "apply update from adb"
I typed "fastboot devices" and my device came up in the bootloader. I click into Recovery Mode and the computer makes the disconnect sound. That's where I'm cut off.
Have you tried unplugging and plugging in the usb again after entering recovery?
Didgeridoohan said:
Have you tried unplugging and plugging in the usb again after entering recovery?
Click to expand...
Click to collapse
I ended up trying NRT and caused even more problems at first, so I ended up just flashing the update instead of sideloading it. I was freaked out for a while because it was stuck in the boot sequence but as of right now, it's working and I have 6.0.
Yay!
ok, sideloading is for twrp recovery. but thats not needed anymore as you can just move files in and out of twrp without adb. flashing factory images is only via fastboot while you are in bootloader. adb and fastboot are different.
I have two H811, mine and my wife's. I managed to root and install TWRP fine on mine via adb/fastboot with no problems but I can NOT get my PC to see the other H811. I can see it in the LGUP app just fine. I see it in device manager just fine. But, from the cmd box, I get nothing when I type "adb devices" or "fastboot" devices. Dev options are enable, OEM unlock checked and USB debug works because I can see it in my file explorer. I've rebooted both devices a bunch of times after disabling and reenabling stuff. Still, nuthin'.
Any suggestions?
EDIT -- After much muckin' about with reinstalling devices and drivers, I finally got adb to see the H811. Fastboot still doesn't see it though.
EDIT 2 -- It dawned on me that I have to be in the bootloader (I think) before I can use fastboot. At least fastboot sees the H811 and I can issue commands to the device. However, I can't flash anything to it.
After all the above stuff, I FINALLY got to flash SuperSu! Seems there's been some changes in the latest command verbage in fastboot. Since I've been using it, it's always required something like "fastboot flash recovery recoveryimagename.img" With the latest version, the word "recovery" is no longer required. Once I got it up and running, I flashed TWRP using Flashify. YMMV
I'm trying to backup my system directly to PC on my OnePlus 3T. I have FreedomOS CE 2.6 installed with TWRP 3.1.0-1. Rooted, unlocked bootloader, USB debugging enabled and everything.
But when i try to turn on ADB sideload so that i can run the commands, it fails. Am i missing anything? I'm not sure how this might help, but i tried sideloading with and without "wipe dalvik and Cache" enabled but both options didn't work....
Is there an error message when it fails?
I'll assume you've got the path and syntax right (sounds like you know what you're doing). So beyond that, sideload can be very finicky from what I've seen on my past devices. I've seen folks having problems with sideload, when simply putting a zip on the phone and flashing it the "standard" way works without a hitch.
I also think it sounds like you know what you're doing but are the adb drivers installed does the phone say it's in adb mode? I have seen people reporting issues with both windows 8 and 10 and sideload, so a little more info may help like whats the error message is it on pc or phone.
Helhound0 said:
I'm trying to backup my system directly to PC on my OnePlus 3T. I have FreedomOS CE 2.6 installed with TWRP 3.1.0-1. Rooted, unlocked bootloader, USB debugging enabled and everything.
But when i try to turn on ADB sideload so that i can run the commands, it fails. Am i missing anything? I'm not sure how this might help, but i tried sideloading with and without "wipe dalvik and Cache" enabled but both options didn't work....
Click to expand...
Click to collapse
your missing to tell us what actually happens
"it fails" means pretty much nothing...
can you connect to the device (adb devices)
do you get any error message?
is your mobile catching fire?
maddler said:
your missing to tell us what actually happens
"it fails" means pretty much nothing...
can you connect to the device (adb devices)
do you get any error message?
is your mobile catching fire?
Click to expand...
Click to collapse
Haha sorry about that.
I can use ADB normally. Like "adb devices" on CMD returns my device ID and everything when I'm booted into Android. This is the first time I'm doing this but to my understanding, I have to be in TWRP for the "adb backup --twrp" command to work. So that's why I'm trying to turn on ADB sideloading using TWRP... Which results the phone to be stuck in "enabling ADB sideloading". After a few minutes of this I get a "failed" in red lettering (literally, that's it.).. and the buttons to reboot and go back...
Helhound0 said:
Haha sorry about that.
I can use ADB normally. Like "adb devices" on CMD returns my device ID and everything when I'm booted into Android. This is the first time I'm doing this but to my understanding, I have to be in TWRP for the "adb backup --twrp" command to work. So that's why I'm trying to turn on ADB sideloading using TWRP... Which results the phone to be stuck in "enabling ADB sideloading". After a few minutes of this I get a "failed" in red lettering (literally, that's it.).. and the buttons to reboot and go back...
Click to expand...
Click to collapse
I think I had something similar when I 1st tried the --twrp option, but that worked next time.
Didn't try again so far.
I'll give it try later today.
I don't think you're supposed to start adb sideloading for this. Just be booted to TWRP.
I updated from 4.0.3 to beta 4 via local, but now I want to go back because of the battery drain problem. I tried several times via adb sideload to flash the zip but I keep getting the same error <cannot read 4.0.4.zip> over and over again. Even after installing the drivers, I got a little yellow exclamation triangle near the driver in device manager. Honestly I'm starting to give up, I think I wiped my phone more than 5 times in order to flash via sideload, only to get the same error continuously. as far as I know, I cannot go back to 4.0.3 via local from beta 4 right?
Please help...
Device: Verizon's Motorola Droid Turbo with Android 6.0.1 and build number MCG24.251-5-5
Hey guys. Newbie here.
So recently i accidentally deleted an important video file and searched google for data recovery methods on smartphone. So most of the post that I read mentioned rooting and a recovery software called Dr.Fone etc. So I installed this software, connected my phone, turned on usb debugging and oem unlocking and started the recovery process. But it was not successful because dr.fone could not root my phone for deep data recovery.
so i googled again and tried sunshine, kingroot, kingoapp and iroot.
Then i tried adb and fastboot(to unlock bootloader).
The thing is in adb command line, the command "adb devices" shows my device. Then I wrote "adb reboot bootloader" and my phone rebooted. then i wrote "fastboot oem unlock(or something like this i copy/pasted it)" it told me that "waiting for any device".
I mean whenever i boot my phone into bootloader my "adb devices" command shows no device but i start my phone in normal mode the "adb command" is working.
Another thing, the "fastboot device/devices" is also not working. It just takes me back to a new line to enter a new command.
Any command containing fastboot is not recognizing my device and all the adb commands are recognized easily.
I have installed all the latest device drives including the universal adb drivers and motorola device manager.
Guys, i am open to all suggestions.
Please help me out.
You have to unlock your bootloader to get permanent root, and you have to do it with Sunshine.
Sunshine is a $25 paid app.
There IS an unstable, temporary root method appropriately called "temp root" that is actually the first step to using Sunshine to unlock the bootloader. Some people cheap out and ONLY use that. But it doesn't survive reboots and you have to run a special command to uninstall it, otherwise you bootloop.
https://forum.xda-developers.com/showthread.php?t=3639316
However, it's possible this temp root method will allow Dr. Done software to do what it needs. Read up on it, try it, see. (Ignore the parts about Magisk, you don't need that.) Just be sure to run the correct uninstall commands. But you would have to do that anyways, if you used Sunshine to unlock the bootloader.
ChazzMatt said:
You have to unlock your bootloader to get permanent root, and you have to do it with Sunshine.
Sunshine is a $25 paid app.
There IS an unstable, temporary root method appropriately called "temp root" that is actually the first step to using Sunshine to unlock the bootloader. Some people cheap out and ONLY use that. But it doesn't survive reboots and you have to run a special command to uninstall it, otherwise you bootloop.
https://forum.xda-developers.com/showthread.php?t=3639316
However, it's possible this temp root method will allow Dr. Done software to do what it needs. Read up on it, try it, see. (Ignore the parts about Magisk, you don't need that.) Just be sure to run the correct uninstall commands. But you would have to do that anyways, if you used Sunshine to unlock the bootloader.
Click to expand...
Click to collapse
Thanks man. Will try this method too.
ahm259 said:
Device: Verizon's Motorola Droid Turbo with Android 6.0.1 and build number MCG24.251-5-5
Hey guys. Newbie here.
So recently i accidentally deleted an important video file and searched google for data recovery methods on smartphone. So most of the post that I read mentioned rooting and a recovery software called Dr.Fone etc. So I installed this software, connected my phone, turned on usb debugging and oem unlocking and started the recovery process. But it was not successful because dr.fone could not root my phone for deep data recovery.
so i googled again and tried sunshine, kingroot, kingoapp and iroot.
Then i tried adb and fastboot(to unlock bootloader).
The thing is in adb command line, the command "adb devices" shows my device. Then I wrote "adb reboot bootloader" and my phone rebooted. then i wrote "fastboot oem unlock(or something like this i copy/pasted it)" it told me that "waiting for any device".
I mean whenever i boot my phone into bootloader my "adb devices" command shows no device but i start my phone in normal mode the "adb command" is working.
Another thing, the "fastboot device/devices" is also not working. It just takes me back to a new line to enter a new command.
Any command containing fastboot is not recognizing my device and all the adb commands are recognized easily.
I have installed all the latest device drives including the universal adb drivers and motorola device manager.
Guys, i am open to all suggestions.
Please help me out.
Click to expand...
Click to collapse
Have you tried just connecting to your pc, enable 'Transfer Files'/mtp mode, and using PhotoRec to scan it as attached storage? The video should not have been anywhere you would need root to access, so this should work. I personally haven't used PhotoRec on a phone in several years, but in the past it worked great. It's free software from CGSecurity (often bundled with TesDisk).
http://www.cgsecurity.org/wiki/Phot...data_from_my_phone.2Fdisk.2Fusb_key.2F..._.3F
Just remember, everytime you use the device you risk rendering the video totally unrecoverable. At best you'll get the whole thing back. More than likely if you're lucky, you'll only get part of it and it will be enough that video software can recognize and play what's left. (based on my own experience). It just depends on how large the video was (data-wise) and how many blocks were overwritten by other data.