Hi folks!
I wanted to install Cyanogenmod as described in Cyanogenmod Wiki.
So I downloaded ioroot, rootet my phone via adb and used AutoRec to install TWRP (version 2.7.0.0).
Then I rebooted into recovery mode, wiped EVERYTHING and wanted to sideload the CM image via adb.
So in TWRP I selected Advanced/ADB Sideload and swipe to start sideload but all that happens is the notification "Starting ADB sideload feature...".
Consequently the phone is not recognized by adb on my PC.
What can I do to make the sideload feature work?
BTW: TWRP tells me that my devices doesnt appear to be rooted when I want to leave TWRP (reboot). Moreover when i want to enter TWRP again (by pressing POWER + VOLUE DOWN) I first get a screen that asks me if want to do a factory hard reset! Only if I agree (by pressing the power key) I get into TWRP.
Contrary when I enter the Download Mode (VOLUME UP when when connecting the powered off phone to the USB port) I am told that the phone is rooted. Moreover the LG Mobile Support Tool is able to detect the device and tells me that the installed software is up to date.
Thx!!
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Make sure you're in the proper folder in prompt and the device name will be sideload if you do, adb devices.
Sent from my LG-D800 using Tapatalk
meangreenie said:
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Click to expand...
Click to collapse
Thanks but this doesnt help either. Same error message "error: device not found"
boot into twrp, don't start sideload
try adb devices, if you get not find you need to change the usb drivers
when you have it working, type, adb push /sdcard/ rom.zip .. check the syntax on that command, but i think that's right from memory
OK, so I am at a loss. I have installed Android Studio, SDK Manager and updated everything I can think of, plus everything that any developer on the web says should be updated. I have checked that the drivers are updated, but every time I try to sideload the latest OTA for my Nexus 6P I get the message "error: no devices/emulators found."
I have done the following:
a) USB debugging is enabled under Developer Options on the device
b) When I execute "adb devices" it shows the device
c) When I execute "adb reboot recovery" it reboots into In recovery
d) I then choose "select update from adb" on the device
e) And then try to execute "adb sideload angler-ota-nrd90u-ffef6b27.zip" only to be given the message that its loading and then "error" no devices/emulator found"
I have searched the web and tried all of the "fixes" and still cannot get the OTA to load, currently tried about 10 times and all have ended up needing to just reboot the system. Does anyone out there have any ideas of the problem and a solution? I have seen several forums that show others with the same issue, but none seem to verify if they have been able to correct the problem. Currently updated to Nougat through the beta program, but my devices shows that I am on NRD90M, which according to the Nexus Files for Developers is for the "ryu" for Pixel C?
Really would like to update the OS to the latest security patch prior to the October date, can anyone help?
There are different drivers for Fastboot and Recovery modes. Once your phone is in Recovery, execute "adb devices", if the phone is not listed there, go to Device Manager in Windows and install the driver.
Plug and Un-plug phone from computer after below step:
c) When I execute "adb reboot recovery" it reboots into In recovery
Faced the same issue earlier. Above thing worked for me.
I finally found a solution, had to do a lot of research but basically I needed to wipe the cache partition. Here is the site that shows you what to do.
https://productforums.google.com/forum/#!topic/nexus/hdrNONCCoNE
Currently my device is updating and is at about 75%! Success!!!
AP_Nex said:
Plug and Un-plug phone from computer after below step:
c) When I execute "adb reboot recovery" it reboots into In recovery
Faced the same issue earlier. Above thing worked for me.
Click to expand...
Click to collapse
This is exactly what worked for me. Happened twice and this fixed it twice.
Hi Everyone.
After look up for a 2nd hand phone works for one hours, and just dead. the google logo bootloop.
after a ton of google, i choose Nexus root toolkit to understand if that is really a "hardware fail" as everyone says, or just another OS issue.
i saw that was nothing happening after some tries (google logo still looping) to re-flash, and left the phone and goes for lunch, when i´m back suddenly i have a few different screens randomly:
1- from google logo goes for the 4 animated dots.
2- from google logo goes to "encrypt unsuccessfull"
3- from google logo goes to android animated logo.
Nexus toolkit still showing "waiting device" and no other action there.
may the brute force or persistent attempts have any different effects on that massive issue?
thanks
erico.albino said:
Hi Everyone.
After look up for a 2nd hand phone works for one hours, and just dead. the google logo bootloop.
after a ton of google, i choose Nexus root toolkit to understand if that is really a "hardware fail" as everyone says, or just another OS issue.
i saw that was nothing happening after some tries (google logo still looping) to re-flash, and left the phone and goes for lunch, when i´m back suddenly i have a few different screens randomly:
1- from google logo goes for the 4 animated dots.
2- from google logo goes to "encrypt unsuccessfull"
3- from google logo goes to android animated logo.
Nexus toolkit still showing "waiting device" and no other action there.
may the brute force or persistent attempts have any different effects on that massive issue?
thanks
Click to expand...
Click to collapse
The common denominator of the BLOD is not being able to get into recovery mode at all. Are you able to get into recovery mode, and are you using a custom recovery (TWRP) or stock recovery? If stock have you tried doing a factory reset? The first boot will take a long time while it is encrypting.
Sounds like you are unlocked and maybe ADB debugging is enabled? Next method would be to get ADB/Fastboot installed on your PC and flash the stock Google image using the flash-all. bat file. But.... since you already have NRT running, you could open "Advanced Utilities" and fastboot format cache, system and userdata (check all 3 boxes). Then go back to the main menu and run "Flash Stock and Unroot". Use the "bootloop/semi-bricked" option. For now, don't root or install a custom recovery. Just see if you can boot into the OS.
v12xke said:
The common denominator of the BLOD is not being able to get into recovery mode at all. Are you able to get into recovery mode, and are you using a custom recovery (TWRP) or stock recovery? If stock have you tried doing a factory reset? The first boot will take a long time while it is encrypting.
Sounds like you are unlocked and maybe ADB debugging is enabled? Next method would be to get ADB/Fastboot installed on your PC and flash the stock Google image using the flash-all. bat file. But.... since you already have NRT running, you could open "Advanced Utilities" and fastboot format cache, system and userdata (check all 3 boxes). Then go back to the main menu and run "Flash Stock and Unroot". Use the "bootloop/semi-bricked" option. For now, don't root or install a custom recovery. Just see if you can boot into the OS.
Click to expand...
Click to collapse
i tried with the adb sideload the Stock one and it keeps o loop. no changes on the screen.
i'm not unlocked at all, its shows on the recovery screen. i will re-try some root and another windows7 and mac for this.
as you say, if BLOD consist to not get in to recovery, i'm safe for now, just need to figure out how to make it works.
thanks a lot so far.
erico.albino said:
i tried with the adb sideload the Stock one and it keeps o loop. no changes on the screen.
i'm not unlocked at all, its shows on the recovery screen. i will re-try some root and another windows7 and mac for this.
as you say, if BLOD consist to not get in to recovery, i'm safe for now, just need to figure out how to make it works.
thanks a lot so far.
Click to expand...
Click to collapse
You said "i'm not unlocked at all" So do you mean your bootloader is LOCKED? Also, the status of bootloader is shown in BOOTLOADER MODE not recovery mode. Perhaps you need to research the difference and answer whether your bootloader is locked (yes/no) and whether you are able to access RECOVERY MODE, or not (yes/no). And whether that is stock recovery? I have no problem with English being your second language, but you need to try to be clear in your answers so we all understand where you are so we can help you. Cheers.
How to enter Recovery Mode: https://www.youtube.com/watch?v=wq_gzT-fV2E
v12xke said:
You said "i'm not unlocked at all" So do you mean your bootloader is LOCKED? Also, the status of bootloader is shown in BOOTLOADER MODE not recovery mode. Perhaps you need to research the difference and answer whether your bootloader is locked (yes/no) and whether you are able to access RECOVERY MODE, or not (yes/no). And whether that is stock recovery? I have no problem with English being your second language, but you need to try to be clear in your answers so we all understand where you are so we can help you. Cheers.
How to enter Recovery Mode: https://www.youtube.com/watch?v=wq_gzT-fV2E
Click to expand...
Click to collapse
thanks for all the word, V12...!
dont have english as my mother language is complicated. specially when you need help on some topics that is not available or dont have good places to go here! (brazil).
anyway, i'm following your first suggestions, and i'm going to share the results soon.
the nexus screen on recovery mode shows:
Console:NULL
Battery OK
Device is LOCKED
Qfuse status ENABLED
off-mode Chager ENABLED
download mode DISABLED.
on my first attempts, i was able to enter on ADB upload menu as you indicate on the video, was able to load the stock rom but stop on the boot loop.
the second shot was my main topic status, using nexus root toolkit with "flash stock+unroot" selecting "softbrick+bootloop". three different screen results on loop.
thanks a lot for the help, bro!
:good:
erico.albino said:
thanks for all the word, V12... Device is LOCKED.... on my first attempts, i was able to enter on ADB upload menu as you indicate on the video, was able to load the stock rom but stop on the boot loop. the second shot was my main topic status, using nexus root toolkit with "flash stock+unroot" selecting "softbrick+bootloop". three different screen results on loop.
Click to expand...
Click to collapse
Because your bootloader is locked, the only real option is to sideload an OTA from the stock recovery. Not possible to flash a full image. You will need to find an OTA that is newer than your current build. If it won't boot, try a factory reset and boot again. If that doesn't work, try fastboot formatting (only) userdata and cache partitions and try the OTA again.
ps: encryption unsuccessful keeps on 7.1.1 NUFK26Kversion, after 30min google bootloop. will give a try with another versions, but my default built is NRD90T 7.0. that is what is showing on the recovery screen (the second one, on the power+volume up on recovery mode). runnning the nexus root toolkit and flash+unroot.
ps: i',m supposed to be almost there, just need to figure out
erico.albino said:
ps: encryption unsuccessful keeps on 7.1.1 NUFK26Kversion, after 30min google bootloop. will give a try with another versions, but my default built is NRD90T 7.0. that is what is showing on the recovery screen (the second one, on the power+volume up on recovery mode). runnning the nexus root toolkit and flash+unroot.
ps: i',m supposed to be almost there, just need to figure out
Click to expand...
Click to collapse
Firstly, NRT doesn't work flashing for you because your bootloader is locked (it even tells you this) and you need to be sure you are using an OTA image. You cannot flash a full stock image. The Flash Stock + Unroot option in NRT downloads the full image. You are supposed to use the ADB side load option from your phone's recovery and send it from your PC. Not that it makes a huge difference, but you are also using the wrong image for Verizon only in the U.S... You need N4F26O not NUFK26K. What happens when you do a factory reset from recovery mode? There is another update out next week (March Security Update) you can try that OTA when it is posted to the link above.
v12xke said:
Firstly, NRT doesn't work flashing for you because your bootloader is locked (it even tells you this) and you need to be sure you are using an OTA image. You cannot flash a full stock image. The Flash Stock + Unroot option in NRT downloads the full image. You are supposed to use the ADB side load option from your phone's recovery and send it from your PC. Not that it makes a huge difference, but you are also using the wrong image for Verizon only in the U.S... You need N4F26O not NUFK26K. What happens when you do a factory reset from recovery mode? There is another update out next week (March Security Update) you can try that OTA when it is posted to the link above.
Click to expand...
Click to collapse
-Factory reset/wipe data goes OK. if i restart the system, it back to bootloop.
-for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)
-adb devices works and show my current device on prompt.
-NRT sideload option is aborted as "verification filed" after some steps and pointing to factory image or automatic img from NRT.
-at NRT, adb sideload device is been recognized, fastboot device recognized but adb recovery device not found status its showing up in the end.
i'm sure i'm doing something wrong, just cant figure out where..... =(
erico.albino said:
-
-for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)
-adb devices works and show my current device on prompt.
-NRT sideload option is aborted as "verification filed" after some steps and pointing to factory image or automatic img from NRT.
-at NRT, adb sideload device is been recognized, fastboot device recognized but adb recovery device not found status its showing up in the end.
i'm sure i'm doing something wrong, just cant figure out where..... =(
Click to expand...
Click to collapse
What is the name of the file you are trying to sideload, and is it an OTA? (angler-ota-n4f26o-6a853f19.zip)
What happens when you follow the method #1 on this page? You will have to "adb push" the OTA file to your phone. If you can't do this, you may not have the correct drivers installed or not have adb installed correctly.
Not sure what you mean by "for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)"- can you elaborate?
v12xke said:
What is the name of the file you are trying to sideload, and is it an OTA? (angler-ota-n4f26o-6a853f19.zip)
What happens when you follow the method #1 on this page? You will have to "adb push" the OTA file to your phone. If you can't do this, you may not have the correct drivers installed or not have adb installed correctly.
Not sure what you mean by "for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)"- can you elaborate?
Click to expand...
Click to collapse
OTA file name: angler-n4f26o-factory-c53f0a50 (1).zip
download page/link: https://developers.google.com/android/images
i cant access internal storage. so i cant run step 1 on that page.
if i hit "adb sideload angler-n4f26o-factory-c53f0a50 (1).zip" on command prompt on windows, i receive this:
R:\Desktop\nexus\Fastboot\Fastboot>adb devices
List of devices attached
84B7N15C21000379 host
R:\Desktop\nexus\Fastboot\Fastboot>adb sideload angler-n4f26o-factory-c53f0a50.z
ip
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
here some images: https://goo.gl/photos/zLZ9CEh1dtpgPJf17
erico.albino said:
OTA file name: angler-n4f26o-factory-c53f0a50 (1).zip
download page/link: https://developers.google.com/android/images
i cant access internal storage. so i cant run step 1 on that page.
if i hit "adb sideload angler-n4f26o-factory-c53f0a50 (1).zip" on command prompt on windows, i receive this:
Click to expand...
Click to collapse
You are not flashing the OTA. You are attempting to sideload the full image. I'm still reading through the rest of your post, but go ahead and download the correct file.
https://developers.google.com/android/ota#angler
v12xke said:
You are not flashing the OTA. You are attempting to sideload the full image. I'm still reading through the rest of your post, but go ahead and download the correct file.
https://developers.google.com/android/ota#angler
Click to expand...
Click to collapse
forget the long post, i was missing the quotes on the image file name.
i'll run your suggestion now...
erico.albino said:
i cant access internal storage. so i cant run step 1 on that page.
Click to expand...
Click to collapse
You can use adb push to move transfer the file over to your phone. "adb push ota.zip /sdcard/ota.zip" then use the "apply update from sdcard" option in recovery. To avoid typos/syntax errors, simply rename the file you are using to ota.zip first. I still think you might have issues with your adb/driver installation.
v12xke said:
You can use adb push to move transfer the file over to your phone. "adb push ota.zip /sdcard/ota.zip" then use the "apply update from sdcard" option in recovery. To avoid typos/syntax errors, simply rename the file you are using to ota.zip first. I still think you might have issues with your adb/driver installation.
Click to expand...
Click to collapse
thanks at all for all the help. unfortunately, after successfully sideload the OTA file, boot loop still here
Sorry to hear that. See if you are allowed to fastboot FORMAT userdata and cache from your PC and try the OTA again. You may get an error formatting userdata. Remember, next week brings a new March security update, and if you haven't given up on your device you can try to flash that OTA when it is posted by Google. You can now get back to your math homework...
Before you go, does your Recovery screen still say NRD90T or did it update to N4F26O?
i can see 7.1.1 N4F26O on recovery screen.
you can bet i will not git it up on this, lol. it was a very good deal based o the value of the device here in brazil.
i'll keep this post up to date about this and let you know about any news.
thanks again for all the help bro, much appreciate it!
cheers from brazil!
erico.albino said:
i can see 7.1.1 N4F26O on recovery screen.
Click to expand...
Click to collapse
March Security Update OTA's posted on Google. Boom!
v12xke said:
March Security Update OTA's posted on Google. Boom!
Click to expand...
Click to collapse
no chanfes unfortunately
There is any specific variant of nexus that can be down for this kind of brick?
Sent from my iPhone using Tapatalk
I want to unroot my phone and I did manage to flash stock recovery.
But now I want to flash stock firmware through adb sideload.
But when I typ adb devices it does not recognize my device and when I type the sideload command, it says error: device not found.
I am using minimal adb fastboot version 1.4.2.
I already tried to use all the different kinds of drivers @ device manager
I am really out of idea's and hope someone here knows what to do.
Edit:
When I use TWRP recovery and I use sideload, adb can recognize my device (and fastboot can also recognize my device).
So only through stock recovery adb cannot recognize my device.
And I remember that USB debugging is off, I do not know if that has to do something with this?
vldholy said:
When I use TWRP recovery and I use sideload, adb can recognize my device (and fastboot can also recognize my device).
So only through stock recovery adb cannot recognize my device.
And I remember that USB debugging is off, I do not know if that has to do something with this?
Click to expand...
Click to collapse
For the stock recovery, Side load Works.
But only Side load, not "adb devices".
After you have selected Side load from stock recovery,
(Boot in stock recovery,
Select your language, -> install from usb -> yes )
Only after this, your device will show in "adb devices"
It will show as Side load device. Then Side load as usual., It will work.
P.S. - USB debugging is not checked in recovery mode.
pollob666 said:
For the stock recovery, Side load Works.
But only Side load, not "adb devices".
After you have selected Side load from stock recovery,
(Boot in stock recovery,
Select your language, -> install from usb -> yes )
Only after this, your device will show in "adb devices"
It will show as Side load device. Then Side load as usual., It will work.
P.S. - USB debugging is not checked in recovery mode.
Click to expand...
Click to collapse
Sorry for late reply!
I did what you said, but I get this error:
error: device '(null)' not found
And when I select install from usb -> yes, Windows notify that there is a problem with the device and cannot recognize it.
What drivers must be installed, OnePlus drivers and ADB drivers?
Does someone know how to fix it?
vldholy said:
Does someone know how to fix it?
Click to expand...
Click to collapse
The problem is stock recovery that you Install does not work well in windows 10
1 Boot in bootloader install TWRP again here
2 Reboot in TWRP Recovery
3 Wipe> Advance Wipe> Select Dalvik & Cache System & Data> Swipe to Wipe
4 Reboot in TWRP Recovery Transfer OOS 4.5.8 Full Rom Zip to the device over MTP
5 Install Menu> Select OOS 4.5.8 Full Rom Zip> Swipe to Flash
6 Reboot System
Now you are in full stock OOS
If you restart now in stock recovery you will see that sideload will work
Adb sideload with stock recovery not work in Windows 10, if you use Windows 7, you'll find that it work well.
The problem is stock recovery from the official site
This OP5_recovery.img
If you are in TWRP and install OOS stock rom sideload will work in windows 10
Had driver issues to what j did was with twrp installed I transferred the Oxygenos rom to internal storage installed it from twrp and then put the OnePlus recovery back on
Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck
I need my phone for work tomorrow so any help would be greatly appreciated.
I'm on TWRP 3.2.3-1 and was using the latest stock oreo rom from here: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
My phone suddenly didn't have a reception today, after rebooting I regained reception but couldn't make calls. I rebooted to recovery and tried to dirty flash the same stock twrp flashable oreo rom that I was using and it failed. Apparently the OS got corrupted. I tried repeatedly to flash the ROM and then noticed I was getting an error : failed to mount system , invalid argument. I couldn't mount system via the Mount tab in TWRP and I couldn't find anything helpful to resolve this error.
I did some more research downloaded the fastboot flashable ROM from here : https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 and tried to flash the rom via adb using adb sideload in twrp but twrp doesn't seem to load that function correctly. In the elevated command prompt in the adb directory I type adb sideload filename.zip and it just freezes up my PC. My device does show up with the adb devices command and shows " *Serial Number* RECOVERY ".
I don't understand what to do with the instructions in the fastboot flash stock thread I posted above and I'm at the limit of my knowledge. No idea how to proceed... any help is greatly appreciated.
I tried extracting the xml.zip into the adb folder and rebooted to bootloader/AP Fastboot Flash Mode and was going to try the commands in the fastboot Rom thread but my device only shows up in adb devices when I load twrp. uhhhhgggghhhhhh guess I'll have to buy a backup phone tomorrow while I try to get this one working
Holy hell.... I didn't realize since I was in the fastboot/bootloader I had to use "fastboot devices" command to see the device. Tried that and saw the device listed, so I created a .bat file using the commands in the fastboot roms thread above and I have a functional device again. Whohoooooo!
Did you try to format /System/ as EXT4?