Related
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.
The phone is in bootlopp (i think).When i turn on appears android on groundb with the red triangle and a chinese word.This disappears and appears again,for an infinite time.Display stays turned on.Turning on in bootloader it works,but just in bootloader.If i try to enter in "Restart bootloader,"recovery,"normal boot"ecc it's in bootloop again.So i can access only bootloader at the moment.I want to reflash system,droidboot imgs ecc with fastboot but...tried to recognize phone on an old HP Compaq nx6110 with usb 2.0 and win7.installed on it adb drivers,adb and fast-tools.don't think zenf2 drivers are important at the moment,now should consider just the adb drivers cause i can access only bootloader.however i think zenf2 drivers are installed on it.nothing.phone no recognized by fastboot and no recognized by windows.consider that on a xp and 2.0 usb pc (with fastboot,adb,and adb drivers on it) phone is recognized by windows as Android-Phone but then windows says i've not the drivers for the installation (appears the drivers' choosing window).No asus driver on it,on the win7 pc there are!!
CenereZar said:
The phone is in bootlopp (i think).When i turn on appears android on groundb with the red triangle and a chinese word.This disappears and appears again,for an infinite time.Display stays turned on.Turning on in bootloader it works,but just in bootloader.If i try to enter in "Restart bootloader,"recovery,"normal boot"ecc it's in bootloop again.So i can access only bootloader at the moment.I want to reflash system,droidboot imgs ecc with fastboot but...tried to recognize phone on an old HP Compaq nx6110 with usb 2.0 and win7.installed on it adb drivers,adb and fast-tools.don't think zenf2 drivers are important at the moment,now should consider just the adb drivers cause i can access only bootloader.however i think zenf2 drivers are installed on it.nothing.phone no recognized by fastboot and no recognized by windows.consider that on a xp and 2.0 usb pc (with fastboot,adb,and adb drivers on it) phone is recognized by windows as Android-Phone but then windows says i've not the drivers for the installation (appears the drivers' choosing window).No asus driver on it,on the win7 pc there are!!
Click to expand...
Click to collapse
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.
samteeee said:
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.
Click to expand...
Click to collapse
Thank you bro,you saved me
samteeee said:
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.
Click to expand...
Click to collapse
Didn't work for me ... if I keep pressed the power button for a long time, power off the phone and it doesn't entry in Recovery mode...
I resolved with "fastboot erase cache" command
It is normal to get that error when selecting 'recovery mode'
The next step is a little tricky. You have to press and hold the power button, then press the volume up button. It may take a few tries. Both buttons will have to be pressed together simultaneous to enter Android system recovery. Please also see http://www.asus.com/us/support/FAQ/1011956/
Sincerely,
ASUS_USA
Asus_USA said:
It is normal to get that error when selecting 'recovery mode'
The next step is a little tricky. You have to press and hold the power button, then press the volume up button. It may take a few tries. Both buttons will have to be pressed together simultaneous to enter Android system recovery. Please also see http://www.asus.com/us/support/FAQ/1011956/
Sincerely,
ASUS_USA
Click to expand...
Click to collapse
Hi,
I´m having a problem with mine. Can´t recognize phone in fastboot but it´s different. I already asked for help in general thread - all resources (page 47 to 50) but still can´t solve.
I rooted my device using method 3 (one click root) and first everything seems fine, but on my first reboot i entered on bootloader - recovery and started a wipe cache, but didn´t finished it, push power button and force it of (i seemeed stuck there - was wipping for more than 10 minutes). Since then i can´t solve anything, tried many ways to unbrick my phone but i seem the problem was i can´t connect fastboot. After a lot o tries, i entered in TWRP using method 2 and wipe, made a recovery, everything and as magic i can enter again on recovery, even tried adb sideload (it started, but when starts to write something - at 50% of the process just ended). So, long story short, i did a flash of the original firmware i downloaded from asus website using method 2 and now it´s working as original, but i still having the same problem (or maybe worst, since i can´t enter the TWRP recovery using method 2 anymore) and can´t root my device. When i tried to do anything using fastboot it´s just shows "FAILED", When i request adb devices shows a blank line. If my phone is on, using android, it shows the correct serial number.
I don´t know what´s happening, it seems to estabilsh a connection (when on its ok, method 2 freeze on teamwin logo - the tool can write something on phone) but can´t write anything. i´m worried because i think i won´t be able to do any update and i wanted a rooted phone to.
Anyone seems a solution?
I'm having the same problem today and I solved it just now! I can't even open the fastboot and recovery. Finally I install the software "shuame"(I'm Chinese, you guys may find other software) on my PC, and with it my computer read zenfone2, and I use the function in the software to open fastboot mode, then I flash the WW version recovery.img and boot.img with a one-click tool in zentalk(TW), then I just double wipe, the phone is alive now !
Sent from my ASUS_Z00AD using XDA Free mobile app
ityoung said:
I'm having the same problem today and I solved it just now! I can't even open the fastboot and recovery. Finally I install the software "shuame"(I'm Chinese, you guys may find other software) on my PC, and with it my computer read zenfone2, and I use the function in the software to open fastboot mode, then I flash the WW version recovery.img and boot.img with a one-click tool in zentalk(TW), then I just double wipe, the phone is alive now !
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
I don´t know any other software. Is this software only in chinese ? Can i try?
My phone is actually working, but i can´t flash anything, even MOFD_update.zip (the file it is used to make ota uptades)
is Your phone rooted? which method did you use? Now you can use fastboot normally?
Couple questions
I just picked up a SM-G960F/DS for experimenting with and am wondering about rooting it. I haven't put a SIM in it yet. Can it be used without a SIM card? I don't plan on using it as a phone just connecting it to Wi-Fi and experimenting with it. I am not sure what firmware to put on it. It came with BUILD R16NW.G960FXXU1BRF8. I live in Canada and I am not sure which firmware to download for it.
As far as rooting goes does it need a SIM in it to do any of this? Can i just add my Google account to get my Apps on it after rooting?
I have not rooted anything since my S6 and searched a bit and think this is the steps to root the S9.
I think that I should first be on latest Firmware before starting this?
Steps as I found info on process to get Root
got Odin3_v3.14.1.zip on PC and USB drivers - my SM-G960W connects okay
1 enable OEM unlock on phone
Downloaded twrp-3.3.1-1-starlte.img for S9 to PC
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to PC USB
2 Open Odin and un-tick auto reboot in "options" tab, make sure that device is detected, Put twrp-3.3.1-1-starlte.img file into AP tab, Click Start
3 When Odin shows "PASS", disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the download mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP recovery
4 in TWRP swipe "Allow modifications"
5 Go into Wipe menu and select "Format data"
6 Reboot into TWRP recovery again, swipe to "Allow modification" connect phone to PC again Put RMM-State_Bypass.zip and no-verity-opt-encrypt-6.1.zip zips into external sdcard (or does this get done all in step 5?)
7 Flash RMM-State_Bypass.zip
8 Flash no-verity-opt-encrypt-6.1 zip
9 Reboot the phone into system Setup Google account.
now it gets confusing as to what to do for root...
So any help?
I imagine that the first thing I need to figure out is what firmware to download for it.
I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.
veryspecialagent said:
I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.
Click to expand...
Click to collapse
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot
sd_shadow said:
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.
veryspecialagent said:
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.
Click to expand...
Click to collapse
Window 10?
Yeah. It should remember this phone, since I used this computer to root it when I first got it a year and a half ago.
I used a different cable and got it to pick up the phone (as an unknown device) in Windows but NOT ADB, and the phone to realize it was connected (see last line on phone screen) but they're not talking.
If I boot it all the way up, either regular or recovery (root), it doesn't show at all on my computer.
Like I said, I'd be fine with wiping it, but can't even get to that option.
Install the moto drivers. If that doesn't work then make sure your using a usb2 port and not a usb3 port as its a known issue with moto phones.
I just ordered a new OEM cable.
Also ordered an OTG cable to see if I can force it to startup into a different mode that'll allow me to do something with it.
I'll update this thread once I'm able to test them out.
I got a new cable. My USB ports are not labeled, and my Moto drivers reinstalled.
After rebooting to the recovery screen, I plugged it in and apparently I have fastboot. I checked the bootloader logs and it says:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Volume down key pressed
USB connected
Windows doesn't pick up anything connected by USB. I can't restart to get root because then adb doesn't pick up the phone either because of the screenlock preventing me from hitting ok to trust my computer.
I'm asking the following because I can't find answers: Can you delete the screen lock file with the only bridge being fastboot, not adb. How can I do a factory reset if rebooting to recovery is our normal way of turnin gon the device with root access? Or would reflashing something work?
command line commands are a perishable skill and it's been a couple years since I did this stuff.
Thanks in advance.
To recap, I either need to be able to get into the directory to delete the pattern lock, or factory reset the phone.
I've tried the pattern lock 79 times, which means I have to wait 300+ seconds between tries. I think an error is causing that though.
Fastboot is my only option at this point as far as using commands goes. Rebooting recovery just reboots it with root permissions, but neither adb or Windows 10 picks it up. Using a brand new factory cord and tried every USB port on my computer, even the USB-C to USB-C. But I can't find anywhere that shows how to get into the directory using fastboot.
In Device Manager, I've been getting an error with Android ADB Interface (The device cannot start; Code 10). I uninstalled, reinstalled various drivers, killed adb.exe, etc., Still happening.
HOWEVER, Motorola ADB Interface is working just fine and goes away when I unplug my phone, returns when I plug it in. Only when it's in recovery/fastboot mode though.
I got into Safe Mode, but computer won't pick it up.
I can't get into Field Test Mode. I did reboot it into something else. I don't know what, but the screen was off and the home button was illuminated. EDL mode? I don't know. Neither my computer or adb read that anything was attached, and i can't figure out how I did it.
I also tried sideloading some pattern lock removers, but apparently you can't do that in fastboot.
Thoughts?
Just to close this out with a solution: I had forgotten that in order to get to the recovery menu, you have to hold the buttons when you reboot recovery. Didn't realize that until I was rooting my Moto e6.
Factory reset complete. No more pattern lock. Though since I've now tried rooting it 4 times with 4 different images and have not succeeded even though I had root before all this, I wish I could have realized the above and possibly gotten in and deleted the gesture.
Lesson learned.
Hold what buttons? I'm afraid I'm in same spot.
onefstfoknv6 said:
Hold what buttons? I'm afraid I'm in same spot.
Click to expand...
Click to collapse
Volume up button and power button
sd_shadow said:
Volume up button and power button
Click to expand...
Click to collapse
Just found this. Timing is everything apparently.
Press and hold the Volume Down and Power buttons simultaneously until the Android Recovery screen appears.
Press the Volume Down button to navigate to Recovery.
With Recovery displayed, press the Power button.
When you see the 'Droid' with 'No Command,' hold Power and tap Volume Up just once and immediately release both buttons.
Scroll to wipe data/factory reset by pressing the Volume Down button
Press the Power button.
Scroll to YES by pressing the Volume Down button.
Press the Power button.
The 'phone will wipe all contents.
Press the Power button.
The 'phone will now reboot to the initial setup screen.
Hey everyone!
So, I've got a HD1903, 8GB RAM 128GB ROM. I updated to OxygenOS 11.0.02, but it was still buggy as hell, so I decided to downgrade. I also had rooted the phone, and decided to get rid of that too. I went to the stock fastboot roms page, downloaded the 10.0.13 ROM and used 'flash-all.bat' file to clear everything. But halfway, it reboots, goes into recovery, then goes to Qualcomm Crashdump mode. That's it. No code or anything, just Qualcomm Crashdump mode, in Blue and Red letters. I tried to hold vol-up, vol-down and power to get into fastboot, but it just loads the fastboot splash screen, then goes back to the same qualcomm crashdump mode screen. Even if i try to hard reset it, by holding vol-up and power, it still goes to the same screen.
Anyone know what to do? I have no idea how to use the 'MSM tool' that everyone talks about, so any guiding advice would be great!
Thanks!
DM me here - https://www.facebook.com/prantor.khan.16 I'll help
HueyT said:
Click to expand...
Click to collapse
I didn't install TWRP, this was all on stock recovery. I also cannot get into fastboot mode.
Msmtool does not need twrp or fastboot--just the software, rom image, drivers, and button combo pushes and holding
OK, so I got it working again, thanks to the advice of reddit users, discord users and the latest msm tool and some googling. I held the vol-up and vol-down buttons for 30 seconds, then connected it to the laptop, with msm running, to a usb 2.0 port, and pressed start. hey presto, it worked. Thanks guys!!
scoped_ar07 said:
Hello
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: only works on Windows PC
1. Unzip the contents of the RAR into a folder.
2. Run the MSM application
3. Click Start.
4. Connect the cell phone in EDL mode (volume up + down button)
5. Wait for the process to finish (it takes a long time, please be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically boot into fastboot mode and display a menu, but if it doesn't and instead boots to the T-mobile screen, you need to force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you need to unlock the bootloader with the command from a Windows CMD window, but you need to download this ADB tool first.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a Windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this time your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, on the command line, run the flash-all.bat file
12. When the phone restarts and the yellow and white letters appear informing that the phone is not safe because the bootloader is unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-PC will detect the phone again in fastboot mode and continue to flash
-Leave the phone and PC still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (ignore it)
13. Finally, the computer will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just turn it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before locking the bootloader again (if you plan to do so) first update via OTA, to the most recent version of Oxygen, otherwise the system will crash again and you will have to repeat the whole process.
Click to expand...
Click to collapse
Stronger1101 said:
Hi
Using the MSM tool is very simple, you just have to download it from this link.
hotdogt_11_O.01_190920 op7t tmo usa patched unlock bootloader.7z
drive.google.com
NOTE: It only works on Windows pc
1. Unzip the contents of the RAR into a
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it is delayed)
6. A message appears informing that the equipment is damaged, do not be careful.
7- Now you must unlock the bootloader with a command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8. Now run this command while the cell phone is connected in Fastboot mode.
fastboo ...
Hi
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: Only works on Windows PC
1. Unzip the contents of the RAR into a folder
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it's time consuming, be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically start in fastboot mode and show a menu, but if it doesn't and instead starts on the T-mobile screen, you must force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you must unlock the bootloader with command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this moment your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, in the command line, run the file flash-all.bat
12. When the phone restarts and the yellow and white letters appear informing that the phone is unsafe due to having the bootloader unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-The PC will detect the phone again in fastboot mode, and continue flashing
-Leave the phone and the pc still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (don't pay attention)
13. Finally the equipment will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just force it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before blocking the bootloader again (if you plan to do it) first update via OTA, to the most recent version of Oxygen, otherwise it will crash the system again and you will have to repeat the whole process.
Click to expand...
Click to collapse
Oh wow that was a long and well defined post. Thank you for taking the time to type it out.
As it happens, I fixed my issue already (IDK if there's a solved flair for XDA or something?). I downloaded the latest (10.0.15) MSM Tool from the XDA page, held the vol-up and vol-down for 30 seconds this time (as per advice from discord users) got the phone into edl mode, connected to a usb 2.0 port and let msm tool do it's thing. Everything is working perfectly now.
I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.
Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.
Āryan-9909 said:
Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.
Click to expand...
Click to collapse
Yes, theyll just change out the motherboard
HueyT said:
Yes, theyll just change out the motherboard
Click to expand...
Click to collapse
If they're going to just change the motherboard, I wonder what the EDL mode is meant for. Anyways, I won't go for motherboard change one can buy a new and better phone at that kinda price.
Anyways, I Fixed it through EDL method, you have to hold vol up and down simultaneously and immediately connect to windows (while still holding both buttons) via original USB cable. Check with Device manager if your device shows up, it's easy enough but you might have to keep trying to you get it right. Thereafter, disable driver verification in windows and if Sahara communications failed message appears in msm tool, turn off phone and repeat the procedure again.
The repair peeps only fix hardware and not software. It's more cost effective for them to swap out hardware faster than messing with msmtool like us
Āryan-9909 said:
I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.
Click to expand...
Click to collapse
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.
scoped_ar07 said:
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.
Click to expand...
Click to collapse
You don't have to hold buttons for that long, you can immediately connect it to PC. There is usually a sound to indicate that a new device has been connected to windows, you can also keep device manager open for confirmation. This video really helped.
After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?
hightech316 said:
After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?
Click to expand...
Click to collapse
Qualcomm 9008 drivers too?
HueyT said:
Qualcomm 9008 drivers too?
Click to expand...
Click to collapse
Yes.
I went ahead and ran another factory reset via recovery, no luck.
New cable, another PC?
HueyT said:
New cable, another PC?
Click to expand...
Click to collapse
Tried both, my desktop would always connect, adb, fastboot, etc.
I had just just freshly installed oneplus drivers including qualcomm on my laptop. Device was not recognized before driver installation or after.
Figure id try on my Mac, and linux laptop. no dice.
ADB is enabled.
Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" . Not phone will not even be seen