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.