Related
hi guys, i have clockworkmod recovery version 2.5.1.3 and i can't access from pc it by sending 'adb shell' commands.. my question is if i have to use adb_recovery.img stock image or if exist the clockworkmod with adb support..
thanks for any answers
do you have the drivers installed? try the command "adb devices" and see if adb can recognise your device.
of course, it can, but only if i use adb_recovery.img image from here: http://xdafil.es/?path=DesireHD/
i am asking if i can do this with clockwork mod too.. when i try to use some commands, i can't even replace system apps in developer mode when charging due to system's mount r/o --> is there some way to mount for example system partition to r/w ? for example command: adb shell mount /system r/w ?
so.. can i use the adb shell when i am in clockwork mod recovery, not the adb_recovery (stock one) ? thanks for your answer
you can either use the command "adb remount" or while logged into shell just use the command "mount /system" either command mounts /system as r/w
thanks mate.. but how i can access my phone through adb.. it's only one way ?
i mean go to bootloader, then stock recovery (adb) or can i use clockwork mod with adb too.. i don't wanna reflash the recovery every time, i need to replace system app.. atm i have to reboot into bootloader, then type fastboot flash recovery adb_recovery.img ..but i don't want.. i just want to type fastboot flash recovery clockwork_recovery.img (2.5.1.3) and when i am at bootloader i would like to go to recovery and use adb shell commands in clockwork mod recovery version 2.5.1.3.. but i am not able to do ..so is the any way how i can get the adb working in clockwork mod recovery or have i to use the stock one ?
blueeyeblue said:
thanks mate.. but how i can access my phone through adb.. it's only one way ?
i mean go to bootloader, then stock recovery (adb) or can i use clockwork mod with adb too.. i don't wanna reflash the recovery every time, i need to replace system app.. atm i have to reboot into bootloader, then type fastboot flash recovery adb_recovery.img ..but i don't want.. i just want to type fastboot flash recovery clockwork_recovery.img (2.5.1.3) and when i am at bootloader i would like to go to recovery and use adb shell commands in clockwork mod recovery version 2.5.1.3.. but i am not able to do ..so is the any way how i can get the adb working in clockwork mod recovery or have i to use the stock one ?
Click to expand...
Click to collapse
adb should work fine with cwm, i have never tried it on the DHD to be honest, but im always using adb with my desire while in cwm recovery
AndroHero said:
adb should work fine with cwm, i have never tried it on the DHD to be honest, but im always using adb with my desire while in cwm recovery
Click to expand...
Click to collapse
do you only boot to recovery or you go to the mounts settings and you choose mount /system /data or how ?
This is a followup to this thread.
I got some help at androidcentral.com and now have Fastboot driver installed. I don't have access to ADB mode or the main Android OS. What can I do now to get my phone back to working. My phone can also enter Download mode if that's useful.
I can enter Recovery from Fastboot but then what do I do?
Edit:
Run this command in ADB.
adb backup -apk -noshared -nosystem -all -f C:\backup.ab
Your phone will ask for a password...
Don't put one in.
Once it's finished...
It will say backup complete.
Or your phone might just boot straight up.
Then navigate to recovery.
And factory reset.
Does your phone now boot?
(If not, stop here, and hit me again)
GOOD!
Now get back in fastboot and run:
adb restore C:\backup.ab
This will give you your applications back.
This MIGHT brick you again...but I doubt it.
If so...simply factory reset.
Thanks for the response.
Can I use ADB from recovery mode because I don't have access to the main OS and It was my understanding that you access ADB from the main OS?
If so, I'm using GNex TOOLKIT V5.6. Would I need to boot to CWM Recovery to use ADB or is the stock recovery ok?
I tried using the command in Fastboot and I get the error "adb: unable to connect for backup"
In GNex TOOLKIT at the top is says:
FASTBOOT MODE
List of devices attached
(the phones serial) fastboot
ADB MODE
List of devices attached
(blank space)
Click to expand...
Click to collapse
When i try "adb devices" in the command prompt, I also get "List of devices attached" with a blank line under it.
OK, I gave up on trying to access my data and attempted to do a restore with the toolkit. I had to unlock the bootloader as the first step and after that the system would boot again.
It would be nice if I could have figured out how to reflash the stock bootloader as a first step but I couldn't figure hot if you can or how.
Anyway, I should have unlocked it from day one. If i had, I would have has access to ADB from CWM recovery and would have been able to backup my stuff and access files even with it in the unbootable state it was in.
I guess not unlocking the bootloader was a mistake I need to learn from.
Jubakuba, thanks for trying to help me out.
Hey guys, as the title states, I'm struggling to install a custom ROM on my Nexus 5X, and I was hoping you guys could read what I did and tell me where I'm going wrong. This is my first time rooting via fastboot commands as whenever I try to root via NRT, SuperSU doesn't flash.
I've had a few failed attempts where my phone has been stuck in bootloop and I've flashed stock using Nexus Root Toolkit. I'll list what I do when trying to root, and if you could tell me where I'm going wrong, that'd be brilliant.
- My first step was to install stock (build number: MTC19T) via NRT
- Connect to the device via fastboot
- Bootloader is already unlocked so I don't bother with that
- Download SuperSU 2.74 in the phone
- Flash over a modified boot.img (found one for my build number on XDA by Tigerstown) via the fastboot commands
***I did this because when I tried to install the SuperSU zip from TWRP 3.0.2, my phone would reboot halfway through the flash and not root***
- Flash over the custom recovery (TWRP 3.0.2 for bullhead)
- Enter recovery from the bootloader
- Install SuperSU via TWRP
- Reboot the phone
- Check if I have root via a Root Checker app in the Play Store
***This part usually goes fine, I've tried it without the boot.img, but TWRP keeps rebooting the system when I try flashing SuperSU***
- Once my phone is rooted, I download Dirty Unicorns 6.0.1 and Banks Dynamic GApps to my phone (I've got these 2 downloaded to my laptop and I just transfer them over to my phone)
- I go back into recovery, I wipe the system (but not internal storage)
- Go to install in TWRP and try to install DU 6.0.1
***My problem here is that TWRP reboots halfway through the installation. I can't flash GApps after the ROM. My phone takes a while to boot up, but when it does, I have DU 6.0.1 even though the installation in TWRP didn't finish***
- I then go back into recovery to install GApps, but the same thing happens to TWRP, it freezes for a second and then reboots my phone.
***However, unlike DU, my GApps won't install. I've tried different a GApps package (Opengapps) but TWRP does the same thing every time***
To summarize, after I root and flash my ROM, I'm left with DU with no GApps. The issue I seem to be having is with TWRP not flashing GApps and I've tried a different version of it but the same thing ends up happening, it freezes for a second and then reboots my phone. I've also tried using SuperSU 2.65 but the same thing happens.
I know this is a long read, but any help would be seriously appreciated!
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
thatguynaveed said:
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
Click to expand...
Click to collapse
1) yes
2) yes
3) factory image zip found here
4) no, when you are in TWRP connect the phone to the computer you will get a window pop up that allows you to brows the internal storage of your device (sd card) you can freely move files back and fourth.
If you didn't execute "Fast boot Flash System 'system.img" not erase System Partition vis Recovery then no, it will not erase the system partition of the device.
Sent from my Nexus 5X using XDA-Developers mobile app
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Since TWRP continues to reboot halfway through the flashing sequence I would recommend that you RMA the device and get a new 5X. There could possibly be a hardware failure occurring and with those it's best to try not to fix them yourself.
thatguynaveed said:
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Click to expand...
Click to collapse
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
berndblb said:
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
Click to expand...
Click to collapse
No, I can't even get to that stage. TWRP reboots whilst I'm trying to install SuperSU.
And by flashing the SuperSU zip, wouldn't I already have SuperSU on my phone? Why would I have to install it form the Play Store?
Anyways, I've given up on trying to root my 5X, like HesThatGuy said, my phone probably has some hardware issues and seeing as I bought my phone second hand, I can't replace it. So I'm just sticking with stock.
Thanks for the reply though mate :good:
Why in Matias Duarte's name are you rooting your phone before flashing a custom ROM? That is a massive waste of time and effort. DU is rooted. You dont need to root the stock ROM first.
First, redownload and fastboot flash TWRP. Redownload DU and the recommended GAPPS while you are at it. If you want to be unencrypted go to WIPE and select Format Data (this will nuke all photos, video, music, whatever on your phone. Back it up first). Don't reboot. Now plug your phone into your computer. Move DU and the GAPPS package you redownloaded to your phone. Wipe everything but internal storage. Add both DU and GAPPS to the flash queue. Flash those buggers. Enjoy.
Attempted to root phone use ADB and fastboot.
during process noticed difficulty in getting recovery mode open manually and had to use adb reboot recovery, whereupon android recovery picture was there but no menu options.
Could not install TWRP conventionally thus attempted the method shown here.
"NSTALL TWRP
Make sure you have ADB and Fastboot installed.
I always put TWRP.img in the ADB folder - so if I want to boot into TWRP with out installing it this is what I do:
make sure you open a command prompt in the ADB folder "VERY IMPORTANT" and type:
adb reboot bootloader <enter>
fastboot boot TWRP.img <whatever your TWRP image is called in your ADB folder><enter> dont forget the .img at the end
That will re-start your phone straight into TWRP - You can transfer files to and from your computer while in recovery.
If you want to install TWRP permanently, copy your TWRP image to your mobile "while you are in TWRP RECOVERY mode" then press install, then select images, then select recovery NOT BOOT, then swipe to flash. This method does not install TWRP app on your phone, all you need is a reboot app from the play store that will re-boot you into recovery. "
Flashed both twrp image and super-su within the TWRP booted from pc through adb (as shown in the previously mentioned method).
Upon reboot phone has hung at LG symbol. LED is flashing. ADB recognises device as connected however won't respond to reboot requests.
How do i fix this?
GhostlessShell said:
Attempted to root phone use ADB and fastboot.
during process noticed difficulty in getting recovery mode open manually and had to use adb reboot recovery, whereupon android recovery picture was there but no menu options.
Could not install TWRP conventionally thus attempted the method shown here.
"NSTALL TWRP
Make sure you have ADB and Fastboot installed.
I always put TWRP.img in the ADB folder - so if I want to boot into TWRP with out installing it this is what I do:
make sure you open a command prompt in the ADB folder "VERY IMPORTANT" and type:
adb reboot bootloader <enter>
fastboot boot TWRP.img <whatever your TWRP image is called in your ADB folder><enter> dont forget the .img at the end
That will re-start your phone straight into TWRP - You can transfer files to and from your computer while in recovery.
If you want to install TWRP permanently, copy your TWRP image to your mobile "while you are in TWRP RECOVERY mode" then press install, then select images, then select recovery NOT BOOT, then swipe to flash. This method does not install TWRP app on your phone, all you need is a reboot app from the play store that will re-boot you into recovery. "
Flashed both twrp image and super-su within the TWRP booted from pc through adb (as shown in the previously mentioned method).
Upon reboot phone has hung at LG symbol. LED is flashing. ADB recognises device as connected however won't respond to reboot requests.
How do i fix this?
Click to expand...
Click to collapse
use you variant KDZ file and flash it with LGUP.
raptorddd said:
use you variant KDZ file and flash it with LGUP.
Click to expand...
Click to collapse
That worked very well. Thankyou raptorddd.
Praise him. Praise him with great praise.
Hey everyone,
I'd like to flash some custom roms but I also want to make sure I can go back to stock OOS. I have a MacBook and I can't use the MSMDownloadTool to go back to the stock rom.
My question is, are there some EU based OOS fastboot roms flying around the internet?
Thank you in advance
xCopyright said:
Hey everyone,
I'd like to flash some custom roms but I also want to make sure I can go back to stock OOS. I have a MacBook and I can't use the MSMDownloadTool to go back to the stock rom.
My question is, are there some EU based OOS fastboot roms flying around the internet?
Thank you in advance
Click to expand...
Click to collapse
After you unlock the bootloader, before root or flash any roms or recoveries, temp boot TWRP via fastboot and take a backup of everything but your internal storage. Take note of which slot you were on when you took the backup, maybe put the active slot in the name of the backup. Save the backup to a USB drive or your computer's hard drive. If/when you restore, make sure you switch back to the slot the phone was on when you took the backup.
Here's something else you can do.
Temp boot TWRP and run the following commands in adb shell or in TWRP's terminal emulator. Do this before you root or make any other changes to the phone.
su
cd /dev/block/by-name
dd if=boot_a of=/sdcard/boot_a.img
dd if=boot_b of=/sdcard/boot_b.img
Now you have both boot partitions backed up. Next you can root either by flashing Magisk in TWRP or by patching whichever boot image came from the active slot, then flashing it with fastboot. Once you have root, install Partitions Backup & Restore from the play store and back up the rest of your partitions. Check everything but boot_a boot_b and userdata and run the backup. Move your boot_a and boot_b images to the Partitions Backup & Restore folder and put it on your computer or a USB drive. Once this is done you'll have stock backups of all your partitions, that can be flashed through fastboot or through adb shell or terminal in TWRP with the dd command.
Personally, I do both. I backup the boot partitions with the dd command, take a full backup in TWRP recovery, install magisk, then backup all the other partitions before I make any other changes to the device.