Related
I have been trying to flash Clockwork Mod Recovery through fastboot, but it's not working. I boot into the bootloader (Power + Vol Dwn), and then into the second bootloader menu (Vol Dwn instead of Vol Up when prompted to go into recovery). When I get the 3 icons (Android Cold Boot, Fastboot USB Protocol, Wipe), I select Fastboot, and the tab displays "Starting Fastboot USB Download Protocol" but nothing happens from here. Is there a problem with the bootloader? Is there a way to replace the bootloader or the fastboot protocol?
gaxiolafm said:
I have been trying to flash Clockwork Mod Recovery through fastboot, but it's not working. I boot into the bootloader (Power + Vol Dwn), and then into the second bootloader menu (Vol Dwn instead of Vol Up when prompted to go into recovery). When I get the 3 icons (Android Cold Boot, Fastboot USB Protocol, Wipe), I select Fastboot, and the tab displays "Starting Fastboot USB Download Protocol" but nothing happens from here. Is there a problem with the bootloader? Is there a way to replace the bootloader or the fastboot protocol?
Click to expand...
Click to collapse
It was saying the same for me too,but just go ahead and flash...it will work just fine.
Pretoriano80 said:
It was saying the same for me too,but just go ahead and flash...it will work just fine.
Click to expand...
Click to collapse
I've tried like 10 times, twice I left it plugged in for about 4 hours, and nothing flashed. When I put "fastboot -i...." in the command prompt, I get "<waiting for device>" and nothing happens, and I can't type anything else.
gaxiolafm said:
I've tried like 10 times, twice I left it plugged in for about 4 hours, and nothing flashed. When I put "fastboot -i...." in the command prompt, I get "<waiting for device>" and nothing happens, and I can't type anything else.
Click to expand...
Click to collapse
Oh,check if the drivers are installed corectly.Some users reported the same issue like yours in the CWM recovery thread and some of them managed to fix it,have a look in that thread.
Pretoriano80 said:
Oh,check if the drivers are installed corectly.Some users reported the same issue like yours in the CWM recovery thread and some of them managed to fix it,have a look in that thread.
Click to expand...
Click to collapse
I've tried everything in that thread. The command window still hangs at <waiting for device>
I downloaded drivers from 4 different places, still nothing. I just flashed the .30 update downloaded directly from Asus, and ran the Debugfs root method again, still nothing. At least now I don't have TWRP! I will just wait until there is another method for flashing CWM, since I'm not seeing any official ROMs I want to flash at the time, anyway.
Thanks for taking the time to reply.
I have also been trying to flash CWM as a custom recovery on my TF700t. I have never done this before so please bear with me. I unlocked my device, turned on usb debugging, plugged it into the computer, on the computer I have fastboot installed and I have 6.0.4.7-NonTouch.img in the fastboot folder. I held down power and volume down until I saw RCK, Android, Wipe Data, and in the top left in tiny print it says starting fastboot USB download protocol. I then opened my command prompt and typed in "cd C:/Fastboot" and it brought up fastboot but when I type "Fastboot devices" to check if I am connected it does not give my serial number but it also does not say device not found. when I check my computers devices it says that I have an unspecified device named fastboot connected with all the drivers up to date. And so I typed in "fastboot -i 0x0B05 flash recovery 6.0.4.7-NonTouch.img" and it says it is sending "Recovery" eleven thousand ish KB but it never actually finishes. Am I doing something wrong that it is not recognizing my device properly? Please Help. Thanks in advance.
Titanium318 said:
I have also been trying to flash CWM as a custom recovery on my TF700t. I have never done this before so please bear with me. I unlocked my device, turned on usb debugging, plugged it into the computer, on the computer I have fastboot installed and I have 6.0.4.7-NonTouch.img in the fastboot folder. I held down power and volume down until I saw RCK, Android, Wipe Data, and in the top left in tiny print it says starting fastboot USB download protocol. I then opened my command prompt and typed in "cd C:/Fastboot" and it brought up fastboot but when I type "Fastboot devices" to check if I am connected it does not give my serial number but it also does not say device not found. when I check my computers devices it says that I have an unspecified device named fastboot connected with all the drivers up to date. And so I typed in "fastboot -i 0x0B05 flash recovery 6.0.4.7-NonTouch.img" and it says it is sending "Recovery" eleven thousand ish KB but it never actually finishes. Am I doing something wrong that it is not recognizing my device properly? Please Help. Thanks in advance.
Click to expand...
Click to collapse
Sounds like you don't have the right drivers installed on your PC. With it connected to the PC in fastboot open your device manager - what does it say - any transformer or adb devices with yellow question marks?
sbdags said:
Sounds like you don't have the right drivers installed on your PC. With it connected to the PC in fastboot open your device manager - what does it say - any transformer or adb devices with yellow question marks?
Click to expand...
Click to collapse
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
---------- Post added at 09:25 PM ---------- Previous post was at 09:12 PM ----------
Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
Click to expand...
Click to collapse
I believe its the original cable but I bought my tablet used. I double checked all my connections. And I used a different port. After trying again I realized that the tablet is actually freezing when I send the recovery before I even try to reboot. Do I need to root my device or is it possible to have a custom recovery unrooted?
Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
---------- Post added at 09:25 PM ---------- Previous post was at 09:12 PM ----------
I believe its the original cable but I bought my tablet used. I double checked all my connections. And I used a different port. After trying again I realized that the tablet is actually freezing when I send the recovery before I even try to reboot. Do I need to root my device or is it possible to have a custom recovery unrooted?
Click to expand...
Click to collapse
Rooting won't help here. You have unlocked it first right?
sbdags said:
Rooting won't help here. You have unlocked it first right?
Click to expand...
Click to collapse
Yes I unlocked it using the asus unlocker tool
Titanium318 said:
Yes I unlocked it using the asus unlocker tool
Click to expand...
Click to collapse
I tried a touch version and also a flashable zip both locked up my tablet the same as before. While my tablet is frozen after attempting to send the recovery I re-entered fastboot devices and it replied "????????????? fastboot" What does this mean?
Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..."
Click to expand...
Click to collapse
11.7 MB? Where did you get this recovery?
_that said:
11.7 MB? Where did you get this recovery?
Click to expand...
Click to collapse
This is where I downloaded CWM: http://d-h.st/YLd. So I switched and tried TWRP and it sent to my device and it did not freeze this time. It showed a blue loading bar at the bottom. I rebooted and opened RCK and TWRP opened successfully. I then Told my system to backup to my removable SD card. After it finished I tapped the reboot system button that came up. I opted not to root my device by installing superSU. I then downloaded Cromi-x to my tablet from here: http://forum.xda-developers.com/showthread.php?t=2425383 choosing the deodex option. Ithen followed the rest of the instructions and everything works great Thank you so much for your help!
Titanium318 said:
This is where I downloaded CWM: http://d-h.st/YLd.
Click to expand...
Click to collapse
Did you really expect a recovery for the Nexus 5 to run on the TF700?
Flashing stuff for different devices can just not work, as in your case, or it can turn your tablet into an expensive paperweight. Consider yourself lucky.
Hello guys. I just got my N5 and ofc rooted it , unlocked bootloader. Then when I booted it into recovery mode ( CWM recovery) I did factory reset as ussually. Then I realised that all my files on card were deleted os I couldnt even flash CM. I tried to pull off the battery. Right now phone does not want to boot into fasboot mode or normal boot. But it can be seen via pc. Is there any way to fix it? I am sure in 99% that this is a problem of deleted software not hardware. Right now its coneted to pc and the screen is on ( but it does not show anything. just pure black).
wojwem19 said:
Hello guys. I just got my N5 and ofc rooted it , unlocked bootloader. Then when I booted it into recovery mode ( CWM recovery) I did factory reset as ussually. Then I realised that all my files on card were deleted os I couldnt even flash CM. I tried to pull off the battery. Right now phone does not want to boot into fasboot mode or normal boot. But it can be seen via pc. Is there any way to fix it?
Click to expand...
Click to collapse
Connect the phone to the pc and type in cmd: adb devices (should see a serial number), if so type: adb reboot bootloader. Do you get into bootloader mode then? BTW did you format data or data factory reset?
wojwem19 said:
Hello guys. I just got my N5 and ofc rooted it , unlocked bootloader. Then when I booted it into recovery mode ( CWM recovery) I did factory reset as ussually. Then I realised that all my files on card were deleted os I couldnt even flash CM. I tried to pull off the battery. Right now phone does not want to boot into fasboot mode or normal boot. But it can be seen via pc. Is there any way to fix it? I am sure in 99% that this is a problem of deleted software not hardware. Right now its coneted to pc and the screen is on.
Click to expand...
Click to collapse
if it doesn't boot on fastboot or recovery and you said that your phone's display is on.. in what mode is it?? well if you can go into fastboot simply download the original system and flash it.. After you will boot your phone and connect it to the pc and flash recovery etc etc :good:
gee2012 said:
Connect the phone to the pc and type in cmd: adb devices (should see a serial number), if so type: adb reboot bootloader. Do you get into bootloader mode then? BTW did you format data or data factory reset?
Click to expand...
Click to collapse
I did factory reset. Tried to write in cmd adb devicies but it says that it doesnt know what it means. Maybe i need to download some kind of software to use adb?
N3xusS said:
if it doesn't boot on fastboot or recovery and you said that your phone's display is on.. in what mode is it?? well if you can go into fastboot simply download the original system and flash it.. After you will boot your phone and connect it to the pc and flash recovery etc etc :good:
Click to expand...
Click to collapse
It isnt any mode known for me. The screen is on but it doesnt show anything it is just pure black. The problem is that i can't get to fastboot mode ( volume down + power button).
wojwem19 said:
It isnt any mode known for me. The screen is on but it doesnt show anything it is just pure black. The problem is that i can't get to fastboot mode ( volume down + power button).
Click to expand...
Click to collapse
hold power for 10 seconds. then hold volume up + down + power
samersh72 said:
hold power for 10 seconds. then hold volume up + down + power
Click to expand...
Click to collapse
Okay did it. after those 10 secs the google screen showed up. Then i presed vol up+ down+ power and right now I am on this google screen. What should I do now? Right now I think it got some kind of bootloop.
Okay just updated my drives via windows and right now in Devicies menager it show up as a " Google nexus ADB Interface".
wojwem19 said:
Okay did it. after those 10 secs the google screen showed up. Then i presed vol up+ down+ power and right now I am on this google screen. What should I do now?
Click to expand...
Click to collapse
sir, hold the power button until it turned off then directly hold the volume up + down followed by power
samersh72 said:
sir, hold the power button until it turned off then directly hold the volume up + down followed by power
Click to expand...
Click to collapse
Okay did it and right now it shows in device menager as "QHSUSB_BULK" and windows can not find software for it. The google logo disappered and screen is off right now.
Okay i managed to turn it into fastboot mode. What should I do right now? and in devices menager it shows up as " Google nexus bootloader interface" Can anyone answer to me? it's really important for me.
wojwem19 said:
Okay did it and right now it shows in device menager as "QHSUSB_BULK" and windows can not find software for it. The google logo disappered and screen is off right now.
Click to expand...
Click to collapse
now try to boot into fastboot mode, volume down + power or both volume + power
wojwem19 said:
Okay did it and right now it shows in device menager as "QHSUSB_BULK" and windows can not find software for it. The google logo disappered and screen is off right now.
Click to expand...
Click to collapse
Can you get into bootloader mode? Hold power button for 10 seconds until it shuts off. Then press and hold vol + and- and then power
Sent from my Nexus 5
wojwem19 said:
Okay i managed to turn it into fastboot mode. What should I do right now?
Click to expand...
Click to collapse
good. flash stock images or boot into custom recovery (you can flash it) and sideload a rom or push a rom (see sticky threads in general section)
gee2012 said:
Connect the phone to the pc and type in cmd: adb devices (should see a serial number), if so type: adb reboot bootloader. Do you get into bootloader mode then? BTW did you format data or data factory reset?
Click to expand...
Click to collapse
Okay right now I am in fastboot mode and installed sdk manager. In folder sdk/platform-tools I enabled cmd with shift + right click. Run adb devicies and it said "daemon not running. starting it now on port 5037
daemon started successfully
list of devices attached".
And when i run it once again it says only "List of devicies attached".
wojwem19 said:
Okay right now I am in fastboot mode and installed sdk manager. In folder sdk/platform-tools I enabled cmd with shift + right click. Run adb devicies and it said "daemon not running. starting it now on port 5037
daemon started successfully
list of devices attached".
And when i run it once again it says only "List of devicies attached".
Click to expand...
Click to collapse
run this command when you are in fastboot mode
Code:
fastboot devices
and not adb
samersh72 said:
run this command when you are in fastboot mode
Code:
fastboot devices
and not adb
Click to expand...
Click to collapse
okay did it and now it showed a key. What should i do now ( i am really newbie in this things conected with flashing via adb. I always flash via recovery.) I already did fastboot flash recovery recovery.img and flashed the cwm 6.0.4.5
wojwem19 said:
okay did it and now it showed a key. What should i do now ( i am really newbie in this things conected with flashing via adb. I always flash via recovery.) I already did fastboot flash recovery recovery.img and flashed the cwm 6.0.4.5
Click to expand...
Click to collapse
now follow this guide to flash stock http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
samersh72 said:
now follow this guide to flash stock http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
i love you man <3
Hello.
I already posted my problem in the other thread, but as I think more information about it will be good, hope you will not mind for starting another thread.
So, I got my hands on a broken S6 for European market. I do not know what happened to it, when turned on, at the first screen bunch of errors appeared and phone was unusable. So I tried to factory reset it, but that did not help. After reset phone turned on but immediately a message apeared that there is no app that can perform that action and that is that. So I decided to flash another stock rom. Installed ADB and fastboot via that fast 15 sec install, installed drivers for my phone and downloaded stock rom for UK Vodafone. ADB did not see my phone, while fastboot did. I tried flashing the rom with fastboot but did get only errors... It says that file was succesfully transfered but then errors appears. I thought maybe that boot loader is locked, so I tried to execute fastboot command to see that information. but nothing happened... Just three dots and nothing, waited for one hour, nothing happened.
So, to sumarize, only fastboot sees my phone, and ADB, Kies and Odin does not. I cannot execute any order in fastboot, cannot go to download mode and I cannot check if bootloader is locked. What are my possibilities?
Thank You.
What are you trying to flash with fastboot? The tar/tar.md5 is for flashing from Odin only!
Try "fastboot" and "fastboot oem ?" and see if there's a reboot command for other modes (I can't check, I'm on the road with no PC). Post the output of these two commands if you're unsure.
Sent from my SM-G920W8 using Tapatalk
DarryDoo said:
What are you trying to flash with fastboot? The tar/tar.md5 is for flashing from Odin only!
Try "fastboot" and "fastboot oem ?" and see if there's a reboot command for other modes (I can't check, I'm on the road with no PC). Post the output of these two commands if you're unsure.
Sent from my SM-G920W8 using Tapatalk
Click to expand...
Click to collapse
Command
C:\adb>fastboot oem ?
...
returns only 3 dots, and hangs. Waited for 10 minutes and nothing happened. Maybe wait more?
Command
C:\adb>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
returns list of available commands to be used with it.
As Odin and ADB doesn´t see the phone, I tried flashing it with fastboot. Downloaded stock firmware, extracted it form .zip file and got a tar.md5 file. Then I just removed the .md5 extension and extracted .tar file and got following .img and .bin files:
boot.img
cache.img
cm.bin
hidden.img
modem.bin
recovery.img
sboot.bin
system.img
When trying command
fastboot flash recovery recovery.img
sending 'recovery' (27928 KB)...
OKAY [475.419s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 475.426s
So I think it might be boot locked, but cannot check it or unlocked it when I get those errors... Any idea?
Command
fastboot oem unlock
also returns only three dots, as if something is working, but nothing happens.
Did execute this command now, I will give it more time, maybe something come up.
Thank You.
Samsung devices doesn't support fastboot mode.
I am somewhat puzzled now. Samsung doesn't support fastboot? Then why there is fastboot mode on S6? Or you meant that flashing rom over fastboot isn't supported?
Just out of curiosity... What's on the screen?
Sent from my SM-G920W8 using Tapatalk
DarryDoo said:
Just out of curiosity... What's on the screen?
Sent from my SM-G920W8 using Tapatalk
Click to expand...
Click to collapse
On the PC screen or the S6?
On the S6 when I press Power+Volume Up+Home I get a menu with following options: Recovery Mode, Fastboot Mode and Normal Boot.
Volume Up to select, and Volume down is OK.
At one point I suspected that I have a fake S6, but recovery mode is in English, everything is. Under Android system recovery sign there are some numbers and letters, if that is important: ALPS.KK1.MP6.V1. At the time when I suspected in fake S6, I watched about dossen movies on youtube on how to know is it a fake or not. In every point compared it is original S6, even at logo and start screen.
The only thing I cannot do is go to download mode to be able to use Odin, so I am stuck with fastboot, because ADB also doesn`t see my phone.
Using fastboot I can restart it in boot loader mode, but not in download mode. If I cannot flash it with fastboot, then what are my options?
I'm confused. I thought home button was broken?
Sent from my SM-G920W8 using Tapatalk
Now I am confused. Again.
I quess you mixed something up. Home button is working. I think this is a problem with corrupted system partitions, but it is unclear why ADB doesn`t work, and why I cannot boot to download mode to be able to use Odin...
Unless it is damaged beyond repair, but before I factory reset it, it got stuck on enter PIN screen, and now it just says there is no home app and no app can do...something, I cant remember exactly, so I think it can be repared, it not bricked.
Oh, yeah, and why I cannot turn off phone when it is in ADB mode?
I really would like to fix this phone, so any and all help is welcome.
EDIT: Check this out... When pressing Power+Volume Down+Home, and then when Samsung logo appears, if I press Volume Up a Chinese recovery menu appears... Does that mean that it is a clone? Is it possible that someone did something to that phone and installed chinese recovery? Because if I press button combination for a recovery mode, normal recovery (in English) appears. So, I have a phone with both English and Chinese recovery?
Sinke1605 said:
Now I am confused. Again.
I quess you mixed something up. Home button is working. I think this is a problem with corrupted system partitions, but it is unclear why ADB doesn`t work, and why I cannot boot to download mode to be able to use Odin...
Unless it is damaged beyond repair, but before I factory reset it, it got stuck on enter PIN screen, and now it just says there is no home app and no app can do...something, I cant remember exactly, so I think it can be repared, it not bricked.
Oh, yeah, and why I cannot turn off phone when it is in ADB mode?
I really would like to fix this phone, so any and all help is welcome.
EDIT: Check this out... When pressing Power+Volume Down+Home, and then when Samsung logo appears, if I press Volume Up a Chinese recovery menu appears... Does that mean that it is a clone? Is it possible that someone did something to that phone and installed chinese recovery? Because if I press button combination for a recovery mode, normal recovery (in English) appears. So, I have a phone with both English and Chinese recovery?
Click to expand...
Click to collapse
First of all, your phone is NOT REAL S6. Your phone is a mediatek clone.
We can't do anything about it.
Ok... I suspected it is a fake. But it is a phone, wright? It is Android on it, wright? So, why you cannot do nothing about it? Is it immposible to flash Samsung stock rom on it? If it is, there has to be some other rom that can be flashed, and some other way. I am curious to see how it works, even it is a fake. Also, it looks just like the original, compared to other fakes and the original S6. How is that possible?
But ok, if no one want to help, I will look elswhere.
For those who tried to help, thanks.
For those who doesn't want to help, also thanks, but for nothing.
See you.
Sinke1605 said:
Ok... I suspected it is a fake. But it is a phone, wright? It is Android on it, wright? So, why you cannot do nothing about it? Is it immposible to flash Samsung stock rom on it? If it is, there has to be some other rom that can be flashed, and some other way. I am curious to see how it works, even it is a fake. Also, it looks just like the original, compared to other fakes and the original S6. How is that possible?
But ok, if no one want to help, I will look elswhere.
For those who tried to help, thanks.
For those who doesn't want to help, also thanks, but for nothing.
See you.
Click to expand...
Click to collapse
The phone has different hardware (cpu, camera, sensors and so on) than an original s6 so a Samsung rom will never work on it. I've seen on YouTube like for like replicas, this is most likely a Chinese clone, the problem is that it's always generic manufacturers so finding a compatible will be very difficult I'm afraid, sorry...
Sent from my SM-G920F using XDA-Developers mobile app
Good day, its my first thread here, so I'm sorry for my english and terminology.
My Photon Q had CM-13-Nightly installed, bootloader unlocked and Clockwork recovery installed. Everything was working fine, till few days ago. Phone was left unused with drained battery, so I charged it and powerd on. After that, all app started to crash one after another. I was trying to do factory reset from recovery, erase everything from bootloader menu or using bootloader commands (bootloader erase data, bootloader -w) but nothing worked. I still have my system, with same apps, wallpaper etc and apps still crash. Are these all symptoms of damaged partition or internal storage? Will be thankful for any help
Erasing in bootloader/fastboot mode can be dangerous... be careful.
I would just factory reset and reinstall the ROM. Don't use ClockworkMod for recovery tho, use TWRP. CWM hasn't had updates in a long time (and frankly I'm surprised it was able to flash the latest CM).
I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery
greedo85 said:
I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery
Click to expand...
Click to collapse
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?
I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
HTML:
C:\fastboot>fastboot flash recovery twrp-2.3.0.0-asanti_c.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6702 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 1.786s]
finished. total time: 2.298s
arrrghhh said:
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?
Click to expand...
Click to collapse
greedo85 said:
I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
Click to expand...
Click to collapse
I think you can safely ignore the bootloader message.
As for flashing TWRP, did you boot TWRP immediately after flashing, or did you boot Android?
I believe you need to make sure you boot TWRP immediately after flashing, otherwise CM Recovery will blow it out.
After flashing TWRP hold power until the device shuts off, release, and now hold power + vol down to enter recovery. Please use the latest version of TWRP from kabaldan, or the latest official TWRP.
I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think
greedo85 said:
I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think
Click to expand...
Click to collapse
Sorry it's power + vol UP (according to my own guide...)
3. Hit power - device turns off. Hold vol up + power, then release power when the screen comes on - continue holding vol up. When you see the moto logo dim a bit, release vol up. You should now be in TWRP!
Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?
greedo85 said:
Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?
Click to expand...
Click to collapse
I'm not sure why people have issues with this... I always thought it was how they 'completed' the flashing process. I don't recall being able to reproduce the condition.
Perhaps boot Android then boot TWRP? Or try to reboot directly to recovery from the fastboot cli? Try something different... or just fastboot boot the TWRP image? There is a problem in the process, I'm just not sure 'where' since I don't have the phone in front of me.
Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?
greedo85 said:
Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?
Click to expand...
Click to collapse
IIRC this device will let you 'fastboot boot' images directly - I think I suggested this - have you tried it?
I'll dig around and see what else I can find from the TWRP thread. I was pretty sure it had to do with the process, but I could be mistaken.
Edit - I'll flash CM Recovery on my old Q and see if I can recreate this as well. It's always bothered me...
How would I boot images directly? From where?
greedo85 said:
How would I boot images directly? From where?
Click to expand...
Click to collapse
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...
arrrghhh said:
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...
Click to expand...
Click to collapse
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s
greedo85 said:
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s
Click to expand...
Click to collapse
I guess they only allow fastboot booting kernels... at least I used to do that on this device.
So I just flashed CM Recovery no problem. Going to flash back TWRP.
Is there anything I can do now to put this phone back to work?
greedo85 said:
Is there anything I can do now to put this phone back to work?
Click to expand...
Click to collapse
I'm... kind of at a loss. Make sure you have the latest TWRP. I just downloaded the latest CM Recovery, fastboot flash recovery <cmrecimg> and it rebooted to Android on its own. I reboot to recovery, CM Recovery is installed. All good.
I reboot to bootloader mode, grab the latest official TWRP, fastboot flash recovery <twrpimg>, this time when I unplugged it was still in fastboot mode. So I hit the power button, phone turns off. Then I hold power + vol up until I see the screen turn on. Continue to hold vol up, but release power. Then when the screen dims (or when recovery starts if you can't tell) release vol up.
Maybe that'll help you? Good luck.
Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?
greedo85 said:
Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?
Click to expand...
Click to collapse
Dunno why it would make any difference at this point, but have at it.
so my nexus is stuck in a bootloop and even going into revocery it still keeps rebooting doesnt give me enought time to factory reset....is there anyway to get it to stop? thanks in advance
fomotomo said:
so my nexus is stuck in a bootloop and even going into revocery it still keeps rebooting doesnt give me enought time to factory reset....is there anyway to get it to stop? thanks in advance
Click to expand...
Click to collapse
Get into fastboot while connected to a computer, then try booting your recovery image with the fastboot command. You'll need the fastboot binary for your platform. The command looks like:
Code:
fastboot boot twrp-[I]version[/I].img
ok ill give that a shot thanks
Fif_ said:
Get into fastboot while connected to a computer, then try booting your recovery image with the fastboot command. You'll need the fastboot binary for your platform. The command looks like:
Code:
fastboot boot twrp-[I]version[/I].img
Click to expand...
Click to collapse
ok so i cant get into fasboot
thats the volume up+down+power correct?
if so it just keeps rebooting
Fif_ said:
Get into fastboot while connected to a computer, then try booting your recovery image with the fastboot command. You'll need the fastboot binary for your platform. The command looks like:
Code:
fastboot boot twrp-[I]version[/I].img
Click to expand...
Click to collapse
It's power and volume down.
If you can't even get into fastboot:
Your EMMC chip may just be fried, and all's lost.
But these symptoms could also come from a stuck power button.
If it keeps rebooting, it could be a power button issue.
I recommend removing the back cover, spray the power button with a bit of contact cleaner, quickly press and release the power button using a bit more pressure than normal, try and boot the phone.