Hi, I am a Nexus 7 user and was tried to root my device using the Toolkit v1.8.2
I am not experience in rooting Android machine, this was my first time and unsuccessful. My device is now could not be started up.
The following is all information I summarized for this exercise, and would like to seek all advice on the followings.
--1 Is my device "recoverable" if yes, how and what do I need to do please?
--2/ or is it definitely "bricked" so I have no chance to recover it at all.
I am totally in-familiar with rooting machine and I have no access to Linux machine.
Any advice is welcome.
Thx in advance.
Machine: Nexus 7 v2- wifi version Android 4.4.2, Build - KOT49H
Computer: Windows 7 64 bit system
Nexus Root Toolkit v1.8.2
Worked procedure:
1/ Follow the "Initial Setup - Full Driver Installation Guide- Automatic + Manual"
Step 1 to Step 4, install the drivers on the computer. and "Full Driver Test" passed
2/ Click "Unlock", pressed "Y" to proceed. - Device went into a screen asking me to select and confirm, I used the "Vol +" to select "yes" and pressed "power" to confirm, but nothing happened on both computer and device after the "power" switch was pressed. Instead, it freeze the device. nothing is responding even after 10 minutes.
3/ I have pressed the "power button again for 5 sec. and device shutdown to black screen.
4/ Since then, every time I try to start the device, the machine first show a "Google" , then a "rotating flower pattern" and won't started. i.e. - "the flower pattern" keeps looping.
5/ on the computer side, no matter what command is given in Nexus Root Toolkit, a notification of ADB device was not found error comes up.
Consequence
A) Device can be switched on and off by pressing "power" button. when switch on, it display "Google" , then a rotating flower pattern, and never end.
Switch the power button for 5 sec again, device switch off.
B) When device is off, press 'power' and "vol -" will switch on the device to a menu with a robot lay down, options "Restart bootloader", "Recovery mode", "Power off" and "Start" can be selected.
C) For "restart bootloader" the screen goes black for 2 sec, then the menu appear again with "Start" option. i.e.- no error no message
D) For "Start " - the device just just act like normal start, end up in a looping rotating flower pattern.
E) For " Recovery mode" - device screen goes black for 3 sec. show "Google" then show a dead robot with an exclamation mark on it, message " No command" is showing. - After awhile, device restarted and end up in the rotating flower pattern.
F) When plugged in, Window 7 can detect the device, when teh device is in the menu, "Android Bootloader Interface" is shown in Windows Device manager, when the device is starting, " Nexus 7" is detected in Windows Device manager but not both.Hi, I am a Nexus 7 user and was tried to root my device using the Toolkit v1.8.2
I am not experience in rooting Android machine, this was my first time and unsuccessful. My device is now could not be started up.
The following is all information I summarized for this exercise, and would like to seek all advice on the followings.
--1 Is my device "recoverable" if yes, how and what do I need to do please?
--2/ or is it definitely "bricked" so I have no chance to recover it at all.
I am totally in-familiar with rooting machine and I have no access to Linux machine.
Any advice is welcome.
Thx in advance.
Machine: Nexus 7 v2- wifi version Android 4.4.2, Build - KOT49H
Computer: Windows 7 64 bit system
Nexus Root Toolkit v1.8.2
Worked procedure:
1/ Follow the "Initial Setup - Full Driver Installation Guide- Automatic + Manual"
Step 1 to Step 4, install the drivers on the computer. and "Full Driver Test" passed
2/ Click "Unlock", pressed "Y" to proceed. - Device went into a screen asking me to select and confirm, I used the "Vol +" to select "yes" and pressed "power" to confirm, but nothing happened on both computer and device after the "power" switch was pressed. Instead, it freeze the device. nothing is responding even after 10 minutes.
3/ I have pressed the "power button again for 5 sec. and device shutdown to black screen.
4/ Since then, every time I try to start the device, the machine first show a "Google" , then a "rotating flower pattern" and won't started. i.e. - "the flower pattern" keeps looping.
5/ on the computer side, no matter what command is given in Nexus Root Toolkit, a notification of ADB device was not found error comes up.
Consequence
A) Device can be switched on and off by pressing "power" button. when switch on, it display "Google" , then a rotating flower pattern, and never end.
Switch the power button for 5 sec again, device switch off.
B) When device is off, press 'power' and "vol -" will switch on the device to a menu with a robot lay down, options "Restart bootloader", "Recovery mode", "Power off" and "Start" can be selected.
C) For "restart bootloader" the screen goes black for 2 sec, then the menu appear again with "Start" option. i.e.- no error no message
D) For "Start " - the device just just act like normal start, end up in a looping rotating flower pattern.
E) For " Recovery mode" - device screen goes black for 3 sec. show "Google" then show a dead robot with an exclamation mark on it, message " No command" is showing. - After awhile, device restarted and end up in the rotating flower pattern.
F) When plugged in, Window 7 can detect the device, when teh device is in the menu, "Android Bootloader Interface" is shown in Windows Device manager, when the device is starting, " Nexus 7" is detected in Windows Device manager but not both.
chanwt12000 said:
Hi, I am a Nexus 7 user and was tried to root my device using the Toolkit v1.8.2
I am not experience in rooting Android machine, this was my first time and unsuccessful. My device is now could not be started up.
The following is all information I summarized for this exercise, and would like to seek all advice on the followings.
--1 Is my device "recoverable" if yes, how and what do I need to do please?
--2/ or is it definitely "bricked" so I have no chance to recover it at all.
I am totally in-familiar with rooting machine and I have no access to Linux machine.
Any advice is welcome.
Thx in advance.
Machine: Nexus 7 v2- wifi version Android 4.4.2, Build - KOT49H
Computer: Windows 7 64 bit system
Nexus Root Toolkit v1.8.2
Worked procedure:
1/ Follow the "Initial Setup - Full Driver Installation Guide- Automatic + Manual"
Step 1 to Step 4, install the drivers on the computer. and "Full Driver Test" passed
2/ Click "Unlock", pressed "Y" to proceed. - Device went into a screen asking me to select and confirm, I used the "Vol +" to select "yes" and pressed "power" to confirm, but nothing happened on both computer and device after the "power" switch was pressed. Instead, it freeze the device. nothing is responding even after 10 minutes.
3/ I have pressed the "power button again for 5 sec. and device shutdown to black screen.
4/ Since then, every time I try to start the device, the machine first show a "Google" , then a "rotating flower pattern" and won't started. i.e. - "the flower pattern" keeps looping.
5/ on the computer side, no matter what command is given in Nexus Root Toolkit, a notification of ADB device was not found error comes up.
Consequence
A) Device can be switched on and off by pressing "power" button. when switch on, it display "Google" , then a rotating flower pattern, and never end.
Switch the power button for 5 sec again, device switch off.
B) When device is off, press 'power' and "vol -" will switch on the device to a menu with a robot lay down, options "Restart bootloader", "Recovery mode", "Power off" and "Start" can be selected.
C) For "restart bootloader" the screen goes black for 2 sec, then the menu appear again with "Start" option. i.e.- no error no message
D) For "Start " - the device just just act like normal start, end up in a looping rotating flower pattern.
E) For " Recovery mode" - device screen goes black for 3 sec. show "Google" then show a dead robot with an exclamation mark on it, message " No command" is showing. - After awhile, device restarted and end up in the rotating flower pattern.
F) When plugged in, Window 7 can detect the device, when teh device is in the menu, "Android Bootloader Interface" is shown in Windows Device manager, when the device is starting, " Nexus 7" is detected in Windows Device manager but not both.Hi, I am a Nexus 7 user and was tried to root my device using the Toolkit v1.8.2
I am not experience in rooting Android machine, this was my first time and unsuccessful. My device is now could not be started up.
The following is all information I summarized for this exercise, and would like to seek all advice on the followings.
--1 Is my device "recoverable" if yes, how and what do I need to do please?
--2/ or is it definitely "bricked" so I have no chance to recover it at all.
I am totally in-familiar with rooting machine and I have no access to Linux machine.
Any advice is welcome.
Thx in advance.
Machine: Nexus 7 v2- wifi version Android 4.4.2, Build - KOT49H
Computer: Windows 7 64 bit system
Nexus Root Toolkit v1.8.2
Worked procedure:
1/ Follow the "Initial Setup - Full Driver Installation Guide- Automatic + Manual"
Step 1 to Step 4, install the drivers on the computer. and "Full Driver Test" passed
2/ Click "Unlock", pressed "Y" to proceed. - Device went into a screen asking me to select and confirm, I used the "Vol +" to select "yes" and pressed "power" to confirm, but nothing happened on both computer and device after the "power" switch was pressed. Instead, it freeze the device. nothing is responding even after 10 minutes.
3/ I have pressed the "power button again for 5 sec. and device shutdown to black screen.
4/ Since then, every time I try to start the device, the machine first show a "Google" , then a "rotating flower pattern" and won't started. i.e. - "the flower pattern" keeps looping.
5/ on the computer side, no matter what command is given in Nexus Root Toolkit, a notification of ADB device was not found error comes up.
Consequence
A) Device can be switched on and off by pressing "power" button. when switch on, it display "Google" , then a rotating flower pattern, and never end.
Switch the power button for 5 sec again, device switch off.
B) When device is off, press 'power' and "vol -" will switch on the device to a menu with a robot lay down, options "Restart bootloader", "Recovery mode", "Power off" and "Start" can be selected.
C) For "restart bootloader" the screen goes black for 2 sec, then the menu appear again with "Start" option. i.e.- no error no message
D) For "Start " - the device just just act like normal start, end up in a looping rotating flower pattern.
E) For " Recovery mode" - device screen goes black for 3 sec. show "Google" then show a dead robot with an exclamation mark on it, message " No command" is showing. - After awhile, device restarted and end up in the rotating flower pattern.
F) When plugged in, Window 7 can detect the device, when teh device is in the menu, "Android Bootloader Interface" is shown in Windows Device manager, when the device is starting, " Nexus 7" is detected in Windows Device manager but not both.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=2741375&stc=1&d=1399986292
http://forum.xda-developers.com/attachment.php?attachmentid=2741374&stc=1&d=1399986292
http://forum.xda-developers.com/attachment.php?attachmentid=2741373&stc=1&d=1399986292
I'll take up the task to help you. You are not bricked. You are stuck in something called a bootloop, which is basically when the device enters the boot sequence, but never finishes. The flower pattern that you are looking at us called the boot animation. The computer never recoginizes the tablet through ADB because the tablet never gets to that point.
The screen with the Android laying on his back is actually the bootloader itself. That's why restarting the bootloader brings you to the same screen. I actually want you to be in the bootloader screen. You already have the Nexus 7.2 drivers, so you're ahead of the game.
You also need to visit here to download TWRP 2.7. You also need to put the file in the same directory as the fastboot and adb files.
You need to boot into the bootloader, and run the command:
fastboot flash recovery <recoveryname>.img
This should get TWRP onto your device. You can then download a rom of your choice to put on the tablet. Since you will not have access to place files on the device through USB, you will have to sideload it. First, let's get recovery working, then come back to me if you need help sideloading the rom through ADB while in recovery.
Dear aarsyl,
Thx for your help and it is much better to know my device is not "bricked". Thx again!
Thx for your detailed explaination and I feel much better by knowing a little bit more on what is going on.
>>>>You also need to visit here to download TWRP 2.7. You also need to put the file in the same directory as the fastboot and adb files.
[I also found it in my computer already .\WugFresh Development\data\Recovery_Custom\TWRP
but I downlaod it again from your link and put this file in the same directory where I find the fastboot.exe and adb.exe, which in my case is .\WugFresh Development\data\ ------ done.]
>>>>You need to boot into the bootloader, and run the command:
[- I supose you refer to my Nexus 7, so I will switch it on with the "power button + vol -" button. and get it into the bootloader.]
>>>>fastboot flash recovery <recoveryname>.img
[Here I got an query, what image file I need to use? is it the <openrecovery-twrp-2.7.0.0-flo> ? Do I neeed to run it as an adminstartor in Window 7?
so, do u mean I need to type: fastboot flash recovery openrecovery-twrp-2.7.0.0-flo.img ?
is it right?--(A)
if not, then I am not sure what recovery file to be used!
I do not have any other img file in package I downloaded previously
>>>>This should get TWRP onto your device. You can then download a rom of your choice to put on the tablet. Since you will not have access to place files on the device through USB, you will have to sideload it. First, let's get recovery working, then come back to me if you need help sideloading the rom through ADB while in recovery.
Not quite understand it this bit, but as you say. it can wait later.
So assume I do the "fastboot flash recovery <recoveryname>.img and get the TWRP on the Nexus 7.
What do I expect to see from the nexus screen. Does it have any note saying completed, or shuold I expect a reboot of the Nexus.
I think one of the problem dealing with these kind of thing is lack of acknowledgment fromt eh machine so we do not know if the operation is successful or not.
chanwt12000 said:
Dear aarsyl,
Thx for your help and it is much better to know my device is not "bricked". Thx again!
Thx for your detailed explaination and I feel much better by knowing a little bit more on what is going on.
>>>>You also need to visit here to download TWRP 2.7. You also need to put the file in the same directory as the fastboot and adb files.
[I also found it in my computer already .\WugFresh Development\data\Recovery_Custom\TWRP
but I downlaod it again from your link and put this file in the same directory where I find the fastboot.exe and adb.exe, which in my case is .\WugFresh Development\data\ ------ done.]
>>>>You need to boot into the bootloader, and run the command:
[- I supose you refer to my Nexus 7, so I will switch it on with the "power button + vol -" button. and get it into the bootloader.]
>>>>fastboot flash recovery <recoveryname>.img
[Here I got an query, what image file I need to use? is it the <openrecovery-twrp-2.7.0.0-flo> ? Do I neeed to run it as an adminstartor in Window 7?
so, do u mean I need to type: fastboot flash recovery openrecovery-twrp-2.7.0.0-flo.img ?
is it right?--(A)
if not, then I am not sure what recovery file to be used!
I do not have any other img file in package I downloaded previously
>>>>This should get TWRP onto your device. You can then download a rom of your choice to put on the tablet. Since you will not have access to place files on the device through USB, you will have to sideload it. First, let's get recovery working, then come back to me if you need help sideloading the rom through ADB while in recovery.
Not quite understand it this bit, but as you say. it can wait later.
So assume I do the "fastboot flash recovery <recoveryname>.img and get the TWRP on the Nexus 7.
What do I expect to see from the nexus screen. Does it have any note saying completed, or shuold I expect a reboot of the Nexus.
I think one of the problem dealing with these kind of thing is lack of acknowledgment fromt eh machine so we do not know if the operation is successful or not.
Click to expand...
Click to collapse
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I decided to have a go with the downloaded twrp img file.
I launched the command " fastboot flash recovery openrecovery-twrp-2.7.0.0-flo.img" from a command window as an adminstrator.
The command failed with an error saying (remote: Bootloader is locked)
And when I check the Nexus 7 screen, it does said "Locked Status - locked" in the last line.
photo showing both the computer and teh Nexus 7 screen.
Oh, I hadn't realized that you were still locked. No wonder you're not getting anywhere.
Reboot into the bootloader, and run:
fastboot oem unlock
Follow the screen instructions to unlock the bootloader, then run the command to flash the recovery. I advise changing the recovery name to something shorter and simpler, like twrp27flo.img, for example.
aarsyl said:
Oh, I hadn't realized that you were still locked. No wonder you're not getting anywhere.
Reboot into the bootloader, and run:
fastboot oem unlock
Follow the screen instructions to unlock the bootloader, then run the command to flash the recovery. I advise changing the recovery name to something shorter and simpler, like twrp27flo.img, for example.
Click to expand...
Click to collapse
Hi, Nice to have reply from you again.
Ammm. I switch on the device to the bootloader alright. run teh command "fastboot oem unlock"
On teh command window, it said" < waiting for device>
and there is no visible change on the device screen.
It already last for 10 minutes now.
I do noted that both windows are freezed and do not respond to key press and button press respectively. No responds on both the device and computer.
How lond does this process take to show the mentioned "screen instruction"? I don't see one!
chanwt12000 said:
Hi, Nice to have reply from you again.
Ammm. I switch on the device to the bootloader alright. run teh command "fastboot oem unlock"
On teh command window, it said" < waiting for device>
and there is no visible change on the device screen.
It already last for 10 minutes now.
I do noted that both windows are freezed and do not respond to key press and button press respectively. No responds on both the device and computer.
How lond does this process take to show the mentioned "screen instruction"? I don't see one!
Click to expand...
Click to collapse
wow.. it is unlocked now!
Should I continue to use the "fastboot recover command with TWRP file" as per your advise or should I continue to use the "Root" command in NexusRoot Toolkit ??
It is very happy to see there is progress.. Thx...
please keep coming...
I would go with using fastboot to install TWRP. In truth, to truly "root" your device, you actually need a working rom on the device. Otherwise, rooting will be in vain. Unlocking the device was the most important.
aarsyl said:
I would go with using fastboot to install TWRP. In truth, to truly "root" your device, you actually need a working rom on the device. Otherwise, rooting will be in vain. Unlocking the device was the most important.
Click to expand...
Click to collapse
Hi again,
Yes. my device is now boot up as brand new.
One side observation though, every time I issue command through window 7 in a command window, everything will freeze up, (not remember if I unplugged the device) until I press the power button to restart the Nexus 7. Same for the last time when i did the unlock and this time recovery.
The hesitation was how do I know when to do this, was worrying there is still some communication between the two machines if I unplug or interfer, may just disturb the communication and corrupt files. -- I normally give it some 10 minutes before I do the unplug and restart. any comment or advice?
Anyway, the device is now up and running. What is the status now? is it with the original version of software? or TWRP version or what?
The device is now remain "unlocked" - is it ok or I need to lock it again?
You have mentioned to download a "Rom", what about it, it is only need if i want to continue to "root " the device?
Sorry for so much question.
I am so happy to see it comes alive again but really would like to understand the current status of it.
Thank again. aarsyl
To be honest, I'm not entirely sure what the status of your device is right now. I was under the implication that you had no Rom on the device. Since you are trying to root for the first time, then yes, you are on the stock software that comes with the device. If you search your app drawer and find the SuperSU app, then you are already rooted, my friend. If it is not there, then search for SuperSU 1.94 in Google, and download the zip file. Then reboot into recovery and flash it.
In other news, I am happy that you got your device working, and I am more than happy to help. The only thing that I don't do is recommend roms. I encourage users to explore different roms for themelves.
[b]AarSyl[/b] said:
To be honest, I'm not entirely sure what the status of your device is right now. I was under the implication that you had no Rom on the device. Since you are trying to root for the first time, then yes, you are on the stock software that comes with the device.>>> since you mentioned I probably have no rom on the device...and you also mentioned "stock software with my device"..I think these are 2 different things right? because i always thought they are the same thing.
If you search your app drawer and find the SuperSU app, >>>App drawer, do you refer to the Apps Tab under Setting? I don't have SuperSU in there.
then you are already rooted, my friend. If it is not there, then search for SuperSU 1.94 in Google, and download the zip file.
Then reboot into recovery and flash it. >>>>I have to say you lost me, do u mean use the ""fastboot flash recovery <Super SU file>.img" command?
In other news, I am happy that you got your device working, and I am more than happy to help. The only thing that I don't do is recommend roms. I encourage users to explore different roms for themelves.>>>No problem, I shall be looking out for that
Click to expand...
Click to collapse
Well, sure I will continues to look up the information from the basic, but at the moment Would you please enlight me for the following 2 questions
1/ Should I uncheck or check the USB debugging tab under Developer options - it will be very good if you would like to explain a little on what it does, so I will have a more l\idea what it does when when do i need them.
2/ As i said, teh device is now unlocked, is it ok to leave it unlock or should i have it lock? - again if you would explain a little more on this that will be marvest.
cheers
chanwt12000 said:
Well, sure I will continues to look up the information from the basic, but at the moment Would you please enlight me for the following 2 questions
1/ Should I uncheck or check the USB debugging tab under Developer options - it will be very good if you would like to explain a little on what it does, so I will have a more l\idea what it does when when do i need them.
2/ As i said, teh device is now unlocked, is it ok to leave it unlock or should i have it lock? - again if you would explain a little more on this that will be marvest.
cheers
Click to expand...
Click to collapse
I'm sorry for the long delay. I got locked out trying to log in after I changed my username twice, and it just got messy for me. At any rate....the SuperSU zip file is to be flashed through recovery. When you boot into recovery, select Install, then navigate through the device to find the folder that the file is located. Follow the screen directions to flash items.
USB Debugging needs to be checked for ADB to work, so.....yeah....leave it on.
You don't have to relock your device unless you have to bring it back to the store for repairs. It only stops you from making changes in the bootloader, such as flashing new recoveries, and I think that most fastboot commands might be blocked. I have never tried to use fastboot on a locked device, so I really don't know. Leaving the device unlocked doesn't make it vulnerable or anything, at least to my knowledge.
AarSyl said:
I'm sorry for the long delay. I got locked out trying to log in after I changed my username twice, and it just got messy for me. At any rate....the SuperSU zip file is to be flashed through recovery. When you boot into recovery, select Install, then navigate through the device to find the folder that the file is located. Follow the screen directions to flash items.
USB Debugging needs to be checked for ADB to work, so.....yeah....leave it on.
You don't have to relock your device unless you have to bring it back to the store for repairs. It only stops you from making changes in the bootloader, such as flashing new recoveries, and I think that most fastboot commands might be blocked. I have never tried to use fastboot on a locked device, so I really don't know. Leaving the device unlocked doesn't make it vulnerable or anything, at least to my knowledge.
Click to expand...
Click to collapse
Thx for your advices AarSyl,
I have successfully root the device and get the Super user app running by following one of tutorial video.
For the first time, when I start at teh bootloader and conduct a "Recovery", it shows a dead robot again but without "no command". I have to redo the fastboot command in the command window with the TWRP recovery file once again. (but this time is very smooth no need to unplug cable that sorts of thing) then I get into the TWRP menu after "Recovery".
chanwt12000 said:
Thx for your advices AarSyl,
I have successfully root the device and get the Super user app running by following one of tutorial video.
For the first time, when I start at teh bootloader and conduct a "Recovery", it shows a dead robot again but without "no command". I have to redo the fastboot command in the command window with the TWRP recovery file once again. (but this time is very smooth no need to unplug cable that sorts of thing) then I get into the TWRP menu after "Recovery".
Click to expand...
Click to collapse
Great. I'm happy that it is working for you. A little tip...download Quick Boot from the Play Store. With one touch, you can power off, boot into the bootloader, boot into recovery, or reboot Android.
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
SF-Echo18 said:
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
Click to expand...
Click to collapse
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
BerndM14 said:
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
Click to expand...
Click to collapse
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
SF-Echo18 said:
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting on device for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
Click to expand...
Click to collapse
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
BerndM14 said:
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
Click to expand...
Click to collapse
I held Volume Up + Power Button and it showed the white screen with the green HTC logo. I then released all buttons. Once the screen turned off I then held Volume Down + Power Button for two minutes straight and nothing happened.
Even though we haven't found a solution yet, I am appreciative of the help.
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Just remember to change directory in command prompt to the folder where adb.exe is located.
I don't know why the device doesn't reboot into bootloader though when you hold volume down + power button, shouldn't have to hold it for 2minutes. Holding volume up + power button to simulate a "pull" should only take up to 20 seconds or so at most and pressing volume down + power will then immediately take you into bootloader mode, or at least it's supposed to.
Did you release the volume up / power combo when the screen went dead or before? Try holding it until the phone shuts off and then right away press volume down + power.
Sorry if I'm not answering right away though, busy eating, and will be here and away for the next hour or so while I get ready for work =o( once I leave for work I'll only be able to help some more after like 2 hours or so. Hopefully we can do something before then though =o)
wase4711 said:
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Click to expand...
Click to collapse
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
SF-Echo18 said:
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
Click to expand...
Click to collapse
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
BerndM14 said:
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
Click to expand...
Click to collapse
Indeed I appreciate it, but I just finished installing the RUU ha. Hopefully this thread will be of use to someone in a similar circumstance in the future.
Share another method of getting into recovery mode on non-responsive blank screen
Hi,
I just want to share how I accessed recovery mode with the same build.prop issue but with S-ON (might work with S-Off too).
I found the solution from here:
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
To get into recovery mode on a non-responsive blank screen, hold the power button and volume up button at the same time and then approximately after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. After, a white boot screen will give an option to go into recovery mode.
Hello, I'm having some serious trouble bootloading my Kyocera DuraXV Extreme (AOSP)
I've went into developer options and activated USB debugging and allowed OEM unlocking.
But I get stuck on rebooting into bootloader mode. I've tried different approaches:
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
2. adb reboot bootloader command
Both options reboot the phone without going into bootloader mode.
Seems Kyocera decided to somehow lock the bootloader mode. Anyone know of a workaround here?
jonas.sj said:
Hello, I'm having some serious trouble bootloading my Kyocera DuraXV Extreme (AOSP)
I've went into developer options and activated USB debugging and allowed OEM unlocking.
But I get stuck on rebooting into bootloader mode. I've tried different approaches:
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
2. adb reboot bootloader command
Both options reboot the phone without going into bootloader mode.
Seems Kyocera decided to somehow lock the bootloader mode. Anyone know of a workaround here?
Click to expand...
Click to collapse
My comments below are based on the belief that you are trying to unlock the bootloader.
I am not familiar with this phone but generally the two steps mentioned by you are not enough to unlock the bootloader. After those steps, you'll have to issue a command via adb to unlock the bootloader and if successful, then you can boot into it for further operations. The command will vary between devices, so search and profit.
Thanks, this cleared it up a bit, you are right, I'm trying to unlock it.
I'm trying the command fastboot flashing unlock but only getting the message < waiting for any device >. I read somewhere that I might need some USB drivers but I don't know where to find them. I have the latest version of the standard USB drivers for the phone, but as I understand it I need special drivers for this?
I'm trying to follow the steps here: https://www.ifixit.com/Guide/How+to+unlock+the+bootloader+of+an+Android+Phone/152629#s317298
I get stuck on the step:
Enter the command adb reboot bootloader
Wait a couple seconds until your device rebooted into the bootloader, then enter the command fastboot flashing unlock
My phone isn't "rebooted into the bootloader", it just reboots. It gives the message "< waiting for any device >" when I write fastboot flashing unlock
jonas.sj said:
I'm trying to follow the steps here: https://www.ifixit.com/Guide/How+to+unlock+the+bootloader+of+an+Android+Phone/152629#s317298
I get stuck on the step:
Enter the command adb reboot bootloader
Wait a couple seconds until your device rebooted into the bootloader, then enter the command fastboot flashing unlock
My phone isn't "rebooted into the bootloader", it just reboots. It gives the message "< waiting for any device >" when I write fastboot flashing unlock
Click to expand...
Click to collapse
It should be a driver issue. When the phone is on and you connect it to the PC/laptop and send the command 'adb devices', does it show an alphanumeric value? Likewise, when you are booted into the bootloader by key combination and send the command, 'fastboot devices', does it show the same alphanumeric response? If so, the drivers are installed properly. If not, either you don't have the correct drivers or they are not installed properly. Try installing the drivers again after disabling driver signing in Windows on your PC (search for it on Google).
Hello, can you clarify what you mean by "booted into the bootloader by key combination"?
My problem is I cannot boot into bootloader at all.
Any attempt at doing so results in a normal boot of the device.
jonas.sj said:
Hello, can you clarify what you mean by "booted into the bootloader by key combination"?
My problem is I cannot boot into bootloader at all.
Any attempt at doing so results in a normal boot of the device.
Click to expand...
Click to collapse
Are you sure that the key combination for booting into bootloader is what you described in the first post?
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
Click to expand...
Click to collapse
I see Power plus Volume Up as the suggested one from a Google search. Try that.
If you can't even boot into the bootloader with the correct key combination, I don't know how to help you further since we are starting to go in circles. I am sorry.
Hello, thank you so much for trying to help me. It seems I can't boot into bootloader. Volume up + power gives the same result as what I did before.: It opens a "Recovery" menu where I can choose reboot to bootloader, but this option just reboots the phone.
I've been in contact with Kyocera and they say:
Thanks for contacting the Kyocera Customer Support. We will be more than happy to assist you with your concern
In this case allow us to inform you that since this device is a basic phone , it doesn't have the option to activate fastboot mode. By installing something that will change the way the phone works , that will void the warranty that came with the phone. We as manufacture can not help you to modify the software that came with the phone.
So the phone's fastboot mode has been deactivated. But since it's an android I guess it should still be possible with some workaround. I just don't know whee to start, I've been researching for a week with no result.
Something interesting ehre, maybe someone with more coding knowledge can tell what's going on.
I found the source code for the phone and located a file called recovery.c which I guess handles the menu I see when I press volume up + power button. Maybe some clue to why the phone isn't going into fastboot mode?