Related
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
7.If this is all fine boot into bootloader again.
From bootloader go to fastboot.
Go back to the cmd window on your PC from earlier, type in:
•Fastboot oem lock
Then type:
•fastboot oem rebootRUU
•fastboot flash zip firmware.zip
•fastboot reboot-bootloader
unlock the bootloader again using the Unlock_code.bin you got from HTC:
•fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
stuck in the same place... before unlocking bootloader pc would recognise the phone. now it doesn't... i think were stuck unless a developer helps us
Hmm, remove and reinsert the battery, and plug it into a computer, don't power the phone on, wait and see if the computer detects it, if it does, try "adb devices" to see if it shows up.
Sent from my Desire HD using Tapatalk 4 Beta
humzaahmed155 said:
Hmm, remove and reinsert the battery, and plug it into a computer, don't power the phone on, wait and see if the computer detects it, if it does, try "adb devices" to see if it shows up.
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Windows detects an "Android Phone" in Devices but "adb devices" is still empty.
konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
i had the same problem but fixed now. The way i did this was to actually take out the hardware for the volume rocker and check if the contacts are all in place. i then booted into bootloader by connecting my phone to a power source (computer or ac) and pressed the volume down button so that it registered. For some reason it seems to register you clicking the button better when its out of the key. Sorry if you don't understand this, I really don't know how to explain the rocker and the keys separately 0_o
Some times guys the firmware.zip file once flash does get stuck on the HTC White screen during the exploit just run ADB and continue with the unlocking of your radio. Its safe.
IBeKay said:
i had the same problem but fixed now. The way i did this was to actually take out the hardware for the volume rocker and check if the contacts are all in place. i then booted into bootloader by connecting my phone to a power source (computer or ac) and pressed the volume down button so that it registered. For some reason it seems to register you clicking the button better when its out of the key. Sorry if you don't understand this, I really don't know how to explain the rocker and the keys separately 0_o
Click to expand...
Click to collapse
Wooh!!! It worked !!! Thank you very much!!!
For future reference, this is how what I did to complete the root process:
1. Pull off the battery cover, take out the battery.
2. Rip off the label with IMEI and S/N and then use a toothpick or plastic tweezers to pull out the ribbon cable from the volume rocker (see video here: youtube[dotcom]/watch?v=JfatoeWbMRk&feature=player_detailpage&t=143)
3. Press the volume down button on the cable a few times to make sure it clicks then clean the inside of the volume rocker a bit, put the cable back in, and press volume down a few times to test it.
4. Put the battery back in, connect the USB to your computer, hold volume down and press the power button so that it goes into the bootloader.
5. Go into fastboot and continue the rest of the steps from the guide.
Note: if adb doesn't detect your phone then reboot it and enable USB debugging again in Settings > Applications > Development and then reboot into the bootloader.
Thanks to everyone that helped ! :good:
konungr said:
Wooh!!! It worked !!! Thank you very much!!!
For future reference, this is how what I did to complete the root process:
1. Pull off the battery cover, take out the battery.
2. Rip off the label with IMEI and S/N and then use a toothpick or plastic tweezers to pull out the ribbon cable from the volume rocker (see video here: youtube[dotcom]/watch?v=JfatoeWbMRk&feature=player_detailpage&t=143)
3. Press the volume down button on the cable a few times to make sure it clicks then clean the inside of the volume rocker a bit, put the cable back in, and press volume down a few times to test it.
4. Put the battery back in, connect the USB to your computer, hold volume down and press the power button so that it goes into the bootloader.
5. Go into fastboot and continue the rest of the steps from the guide.
Note: if adb doesn't detect your phone then reboot it and enable USB debugging again in Settings > Applications > Development and then reboot into the bootloader.
Thanks to everyone that helped ! :good:
Click to expand...
Click to collapse
glad I helped
konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
Hi
I have followed your all steps perfectly... after done i have reboot my desire hd it shows htc screen and goes to qualcom mode...plz tell what should i've to do now
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.
Hello all,
My unlocked (for a long time) Nexus 7 stopped responding so I turned it off and on and now it won't go beyond the google screen.I have tried connect it to my computer but windows doesn't see it as a device (usually does) so I can't run any adb commands.
I pressed power + volume down until the menu appears but nothing I select helps. I have left it for hours after selecting 'recovery mode' from that menu and still no joy. I have left the battery completely empty then changed it up again and it still won't get beyond that Google screen.
Does anyone please know anything else I can try?
standardman said:
Hello all,
My unlocked (for a long time) Nexus 7 stopped responding so I turned it off and on and now it won't go beyond the google screen.I have tried connect it to my computer but windows doesn't see it as a device (usually does) so I can't run any adb commands.
I pressed power + volume down until the menu appears but nothing I select helps. I have left it for hours after selecting 'recovery mode' from that menu and still no joy. I have left the battery completely empty then changed it up again and it still won't get beyond that Google screen.
Does anyone please know anything else I can try?
Click to expand...
Click to collapse
Does your computer recognize your N7 when it's booted into the bootloader (aka fastboot mode)?
charesa39 said:
Does your computer recognize your N7 when it's booted into the bootloader (aka fastboot mode)?
Click to expand...
Click to collapse
That's the menu with the start/recovery/power off options isn't it? It doesn't detect it at that point either, I'm afraid.
standardman said:
That's the menu with the start/recovery/power off options isn't it? It doesn't detect it at that point either, I'm afraid.
Click to expand...
Click to collapse
Well, if you've already unlocked it in the past, you should still have the drivers on your computer. You need to select the correct drivers, and it should detect it. Once you've done that, you can confirm this by using the "fastboot devices" cmd to make sure your device shows up in fastboot mode.
charesa39 said:
Well, if you've already unlocked it in the past, you should still have the drivers on your computer. You need to select the correct drivers, and it should detect it. Once you've done that, you can confirm this by using the "fastboot devices" cmd to make sure your device shows up in fastboot mode.
Click to expand...
Click to collapse
Thanks for the reply.
Sorry I'm not exactly sure how to do that. Will they just be files on my PC, what should they be called?
If it helps, I used the nexus root toolkit to root mine.
standardman said:
Thanks for the reply.
Sorry I'm not exactly sure how to do that. Will they just be files on my PC, what should they be called?
If it helps, I used the nexus root toolkit to root mine.
Click to expand...
Click to collapse
Give this a try: http://forum.xda-developers.com/showthread.php?t=2588979. Once you have the correct drivers installed, it should detect it in fastboot mode.
charesa39 said:
Give this a try: http://forum.xda-developers.com/showthread.php?t=2588979. Once you have the correct drivers installed, it should detect it in fastboot mode.
Click to expand...
Click to collapse
Thanks again!
Ok, so it didn't detect so I rebooted the device a few times while connected to USB and it appeared, did some windows instally drivers stuff then the DEVICE booted. Unfortunately the touchscreen wasn't working (happens fairly often) so I rebooted and now it won't get beyond the google screen again and windows isn't detecting it again.
So close!
standardman said:
Thanks again!
Ok, so it didn't detect so I rebooted the device a few times while connected to USB and it appeared, did some windows instally drivers stuff then the DEVICE booted. Unfortunately the touchscreen wasn't working (happens fairly often) so I rebooted and now it won't get beyond the google screen again and windows isn't detecting it again.
So close!
Click to expand...
Click to collapse
Well, if it detected it, then you should have the correct drivers. Boot into the bootloader by holding Power + Volume Down. Plug in your device. Open a command window in the folder where your adb/fastboot was installed. The easiest way to do that is to navigate to that folder (default location should be something like C:/android-sdk/platform-tools) and hold SHIFT on your keyboard and right click. The drop down menu should have an option to open a command window in that location. Type "fastboot devices" (obviously, without the quotation marks), and you should see the serial number for you device pop up. That's when you know you can then use fastboot commands successfully.
charesa39 said:
Well, if it detected it, then you should have the correct drivers. Boot into the bootloader by holding Power + Volume Down. Plug in your device. Open a command window in the folder where your adb/fastboot was installed. The easiest way to do that is to navigate to that folder (default location should be something like C:/android-sdk/platform-tools) and hold SHIFT on your keyboard and right click. The drop down menu should have an option to open a command window in that location. Type "fastboot devices" (obviously, without the quotation marks), and you should see the serial number for you device pop up. That's when you know you can then use fastboot commands successfully.
Click to expand...
Click to collapse
Great, that worked, it output my serial number. Now we know we can use those commands, what's next please?
standardman said:
Great, that worked, it output my serial number. Now we know we can use those commands, what's next please?
Click to expand...
Click to collapse
Good. The easiest thing to do to try to recover without wiping your data would be to format the cache. Sometimes, your issue can be caused by a corrupted cache partition. So type "fastboot erase cache" and hit enter. Let it do it's thing. Then, type "fastboot format cache" and hit enter. Let it do it's thing again. Then, on your Nexus 7, select "reboot" and see if it boots into the Android OS.
charesa39 said:
Good. The easiest thing to do to try to recover without wiping your data would be to format the cache. Sometimes, your issue can be caused by a corrupted cache partition. So type "fastboot erase cache" and hit enter. Let it do it's thing. Then, type "fastboot format cache" and hit enter. Let it do it's thing again. Then, on your Nexus 7, select "reboot" and see if it boots into the Android OS.
Click to expand...
Click to collapse
Hooray! This is looking waay more positive! I can nowe boot my device but still have that touchscreen issue (I tend to do this stuff until it sort itself out).
Thank you so much for all your help. Just in case I can't get the damn touchscreen working. How would I use command line to factory reset this thing please?
standardman said:
Hooray! This is looking waay more positive! I can nowe boot my device but still have that touchscreen issue (I tend to do this stuff until it sort itself out).
Thank you so much for all your help. Just in case I can't get the damn touchscreen working. How would I use command line to factory reset this thing please?
Click to expand...
Click to collapse
Great! Well, except for those touch issues... To flash the factory image, check out the OP in this thread over in the Nexus 5 forums: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Although it's for the N5, the procedure is pretty much exactly the same for the N7 (2013) (and Nexus 10 for that matter). Just make sure you have the correct factory image for your device. Basically, after you download the factory image, you have to extract the folder inside the zip. Then, open the command window there, and type "flash-all.bat" (assuming you're using a Windows PC). IMPORTANT: After everything is done running, boot back into the bootloader and boot into recovery. Select "wipe data/factory data reset." After that's done, just reboot and you're good to go.
charesa39 said:
Great! Well, except for those touch issues... To flash the factory image, check out the OP in this thread over in the Nexus 5 forums: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Although it's for the N5, the procedure is pretty much exactly the same for the N7 (2013) (and Nexus 10 for that matter). Just make sure you have the correct factory image for your device. Basically, after you download the factory image, you have to extract the folder inside the zip. Then, open the command window there, and type "flash-all.bat" (assuming you're using a Windows PC). IMPORTANT: After everything is done running, boot back into the bootloader and boot into recovery. Select "wipe data/factory data reset." After that's done, just reboot and you're good to go.
Click to expand...
Click to collapse
Thank you once. Honestly, I feel like I found a saint on the internet :highfive:
standardman said:
Thank you once. Honestly, I feel like I found a saint on the internet :highfive:
Click to expand...
Click to collapse
Haha! I don't know about all that. Just glad I could help. :highfive: Hope it all works our for you. :good:
I just bought a 2013 Nexus 7 today for very cheap, to use in my car as a headunit and learn a bit about flashing different roms, using the timur kernal, etc. It looks like it was used at some sort of healthcare facility though, because it has some "Optum Health" software on it, deeper than just an app it remained after a factory reset. On restart the optum health logo comes up, immediately after the google logo and says loading, well before it actually loads to the home page of the tablet. So it's pretty deep. I was thinking a fresh factory ROM would help me out.
I was following this guide to get twrp on the phone, as wifi wasn't working (most likely because I had tried to remove the optum stuff by disabling apps, and I got a little trigger happy) load via adb:
https://www.xda-developers.com/how-to-install-twrp/
Everything was cool until I went to restart it. I typed "fastboot reboot" into the command prompt, she restarted, and gets infinitely stuck at the "Optum Health" logo, and the word "Loading" pulses underneath.
I can't get it back to the bootloader by holding the volume buttons and "hold", the cmd/powershell doesn't see the device connected. However, the computer makes the chime sound of a device connecting when I try to open the bootload menu using the buttons, the power shell waits longer to say it failed, but it still doesn't work.
Do I have any options? Or did I completely brick my old, cheap, facebook marketplace, probably stolen from a hospital tablet?
solson1041 said:
I can't get it back to the bootloader by holding the volume buttons and "hold", the cmd/powershell doesn't see the device connected. However, the computer makes the chime sound of a device connecting when I try to open the bootload menu using the buttons, the power shell waits longer to say it failed, but it still doesn't work.
Do I have any options? Or did I completely brick my old, cheap, facebook marketplace, probably stolen from a hospital tablet?
Click to expand...
Click to collapse
Follow these instructions to resolve the problem and flash up-to-date Android - https://wiki.lineageos.org/devices/flo/install
"With the device powered off, hold Volume Down + Power until the bootloader appears, then release the buttons." it really works.
Then connect it to a PC and install proper USB driver - https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Once you get ADB & Fastboot installed on your PC or linux , do a command prompt with the device connected.
adb devices
It should list your device in your terminal output. If and when it does..If your a little hinky on the buttons just do a command prompt: adb reboot recovery, adb will reboot your device for you into recovery mode. Then follow the LOS instructions provided for you & you will be amazed at how great your tablet works. Just a little FYI, if you've never done this before, find the "pico" gapps, don't try to install any of the bigger ones, there is not enough room on the sys partition for the full gapps install. After & if you get pico installed you can always add to it with all the room you have left now on the rest of the device. Also when you are installing LOS, make sure you find and install the gapps at the same time you install the OS, before you reboot your device. It will save you a lot of headaches. Just follow the directions and you will be very happy.
Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Phone is on continuous boot loop, and sometimes (really seems randomly), the device starts up in the "no command" mode and stays there for a while. I read that we could go into fastboot mode by pressing "power button and tapping volume up key", but this doesn't do anything.
I've tried this thread: https://www.the***********.com/boot-xiaomi-mi-a2-fastboot-mode-recovery-mode/
But I'm not even getting into fastboot.
I'm almost thinking that the volume buttons are just broken, though from the feedback of the buttons this doesn't seem realistic.
EDIT: ok, now I'm somehow able to get it into fastboot.... sometimes. Now I'm here:
I switched the partition from a to b, but it still goes into bootloop. Then I switched it back to a, still bootloop. Then back to b. Still bootloop! But at least now sometimes I'm able to get into fastboot. No matter what kind of commands I'm typing in the cmd console, after about 10 seconds on the fastboot screen, the phone just reboots.
idk, it looks almost as if both partitions have the bad android 10...
Do you guys have any idea? Please let me know if more info is helpful.
You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Go here and grab the image you prefer (latest should do the trick) : https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Then go ahead and follow this guide here to flash the stock ROM : https://c.mi.com/oc/miuidownload/detail?guide=2
This will wipe the data on the device, but it seems like you have no other option at this point. Cheers.
Thanks! I've tried that now. It starts flashing the device until... after about 10 seconds, the phone reboots from Fastboot mode .
As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
I've tried to do a recovery via TWRP. If I execute `fastboot boot path/to/twrp.img` then I go from fastboot to TWRP (the teamwin logo), but right after that the phone already reboots.
https://www.xda-developers.com/how-to-install-twrp/ - I don't know if it means anything, but when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
I installed ADB usb drivers, so when I get my phone connected in fastboot, it shows up as Android Bootloader Interfacee in device manager. So not sure what's going on here, but it's all weird.
What I'm facing is very, very similar to https://www.reddit.com/r/Xiaomi/comments/4ltzt9/xiaomi_mi_note_boot_loop_even_in_fastboot/ <-- but that thread is a bit of a dead end (and 3 y/o)...
daize said:
after about 10 seconds, the phone reboots from Fastboot mode .
Click to expand...
Click to collapse
Hmm, it should never do that, maybe it's a hardware issue that we can not fix via Fastboot ?
daize said:
As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
Click to expand...
Click to collapse
When the device is in Fastboot mode, it will only be recognized as Fastboot. Only when it's properly booted, the device can be recognized in ADB, so no issues there.
I assume your bootloader is already unlocked as you have successfully booted into TWRP. You might try EDL (Emergency Download Mode) flash as a last resort :
Download MiFlash (20160401) from here : https://www.xiaomiflash.com/download/
You're downloading that particular version because it is able to EDL flash on your phone. Install the MiFlash you've downloaded and open it, then put the phone into fastboot mode. Connect it to your PC and use this code to take the phone into EDL mode:
Code:
fastboot oem edl
After you hit enter, you will see the screen turn off and notification LED blinking, this is normal. This means the phone is in EDL mode. Open the MiFlash you've installed (likely in C:\Program Files\Xiaomi\MiPhone) and browse to the ROM location and connect the phone. Choose "Flash All" and start flashing.
After the EDL flash is complete the phone will not reboot. It will stay in EDL mode. You need to disconnect the phone from PC and hold power button (about 10-15 seconds) to boot the phone. If the phone boots properly, you can go into fastboot and connect it to PC, then use:
Code:
fastboot oem lock
to relock your bootloader. Try it and let me know. :fingers-crossed:
Thanks for the continued help!
I've followed your steps - When I run fastboot oem edl, the console returns "... okay [ 0.0202s] finished. total time: 0.022s" and the phone turns to a black screen (no notification led blinking). Then... after a couple of seconds, goes back into the boot loop .
Something maybe to note: every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.
daize said:
every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.
Click to expand...
Click to collapse
The screen with the ugly text is normal, since you have an unlocked bootloader, it's there to warn you that the device's software might've been tampered with. On the main subject though, I'm out of ideas. You might try booting the phone by holding Power + Vol Up, which should normally boot into stock recovery or wipe the data on the device. But I'm slowly beginning to think that this might be a hardware issue rather than a software issue that I can help you to fix.
Under normal circumstances, EDL flash is the way to fix any problems you might encounter with the software, that's why it's called the Emergency Download mode. But since we're past that stage, I believe I will not be able to assist you further. Hope you can fix your device my dude/dudette!
If the phone gets out of fastboot mode your phone does not get recognized from your computer. Try to delete fastboot and minimal adb and download the latest version. [https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
Open MiFlash, click Driver left on the top and install them.
Set path to the downloaded firmware. Now boot into fastboot, once that is done connect your USB cable to both, computer and phone. If this doesn't work try different USB-Ports and USB-cables. Some work, some don't. This might be the reason for leaving the fastboot mode.
Click refresh and see if your device appears
@marstonpear thanks for your help so far <3 @Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...
@marstonpear thanks for your help so far <3
@Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...
What did change now after installing these drivers: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
I did try some other USB cables. The one I've been trying triggers the windows sound for "new device successfully connected" when I boot the phone up in fastboot, and then of course gives the "device disconnected" sound when the phone then reboots. With another USB cable in this case, windows just states: "USB device not recognized". So it seems like the cable I haven't been using is defect .
I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot
daize said:
Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Click to expand...
Click to collapse
The response by marstonpear below makes sense.
marstonpear said:
You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Click to expand...
Click to collapse
Although u shd consider this link, i tried to arrange it step by step:
https://forum.xda-developers.com/sho...php?p=79365091
Follow the instructions, as dat was how i revived mine. Hopefully it may help u.
Note; wen using twrp, preferably use " twrp - offain "
Miflash tool:
Link 1: https://www.xiaomiflash.com/download/
Preferably use Link 1 & choose either 2016, 2017 or 2018 versions. They come preloaded with the drivers u need
Link2: https://xiaomibuzz.com/downloads/download-xiaomi-mi-firmware-flash-tool-latest-version-2018.html
Lets know how it goes
Cappucinto said:
I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot
Click to expand...
Click to collapse
Hey there When I get into fastboot and run `fastboot devices`, a code returns <tab> fastboot.
... and then the phone restarts I'm trying but I guess I'm beyond the stage of being upset, haha.
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!
daize said:
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!
Click to expand...
Click to collapse
Sorry bout d previous link. I believe this shd take u directly to the tutorial:
https://forum.xda-developers.com/mi...tboot-mode-t3920925/post79365091#post79365091
remember to use "twrp offain for daisy". It works better than the regular twrp for daisy
It my take and procedure that worked for me at the time. Good luck tho
Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .
daize said:
Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .
Click to expand...
Click to collapse
Try getting another chord and try again.
Tried some other cables. Every time I run fastboot oem edl, it keeps saying "finished", and then reboots the phone in about 5 seconds. One time, it said "Catastrophic failure" as "status" for the flashing.
Otherwise, it most often says "The operation completed successfully.(0x00000000: cmd <?xml version="1.0"?><data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISC_SECTORS-1." value="CRC32(NM_DISK_SECTORS-1.,92)" what="Update"/></data>)
But then still continues in the bootloop...