Related
Hi, I am a Nexus 7 user and was tried to root my device using the Toolkit v1.8.2
I am not experience in rooting Android machine, this was my first time and unsuccessful. My device is now could not be started up.
The following is all information I summarized for this exercise, and would like to seek all advice on the followings.
--1 Is my device "recoverable" if yes, how and what do I need to do please?
--2/ or is it definitely "bricked" so I have no chance to recover it at all.
I am totally in-familiar with rooting machine and I have no access to Linux machine.
Any advice is welcome.
Thx in advance.
Machine: Nexus 7 v2- wifi version Android 4.4.2, Build - KOT49H
Computer: Windows 7 64 bit system
Nexus Root Toolkit v1.8.2
Worked procedure:
1/ Follow the "Initial Setup - Full Driver Installation Guide- Automatic + Manual"
Step 1 to Step 4, install the drivers on the computer. and "Full Driver Test" passed
2/ Click "Unlock", pressed "Y" to proceed. - Device went into a screen asking me to select and confirm, I used the "Vol +" to select "yes" and pressed "power" to confirm, but nothing happened on both computer and device after the "power" switch was pressed. Instead, it freeze the device. nothing is responding even after 10 minutes.
3/ I have pressed the "power button again for 5 sec. and device shutdown to black screen.
4/ Since then, every time I try to start the device, the machine first show a "Google" , then a "rotating flower pattern" and won't started. i.e. - "the flower pattern" keeps looping.
5/ on the computer side, no matter what command is given in Nexus Root Toolkit, a notification of ADB device was not found error comes up.
Consequence
A) Device can be switched on and off by pressing "power" button. when switch on, it display "Google" , then a rotating flower pattern, and never end.
Switch the power button for 5 sec again, device switch off.
B) When device is off, press 'power' and "vol -" will switch on the device to a menu with a robot lay down, options "Restart bootloader", "Recovery mode", "Power off" and "Start" can be selected.
C) For "restart bootloader" the screen goes black for 2 sec, then the menu appear again with "Start" option. i.e.- no error no message
D) For "Start " - the device just just act like normal start, end up in a looping rotating flower pattern.
E) For " Recovery mode" - device screen goes black for 3 sec. show "Google" then show a dead robot with an exclamation mark on it, message " No command" is showing. - After awhile, device restarted and end up in the rotating flower pattern.
F) When plugged in, Window 7 can detect the device, when teh device is in the menu, "Android Bootloader Interface" is shown in Windows Device manager, when the device is starting, " Nexus 7" is detected in Windows Device manager but not both.Hi, I am a Nexus 7 user and was tried to root my device using the Toolkit v1.8.2
I am not experience in rooting Android machine, this was my first time and unsuccessful. My device is now could not be started up.
The following is all information I summarized for this exercise, and would like to seek all advice on the followings.
--1 Is my device "recoverable" if yes, how and what do I need to do please?
--2/ or is it definitely "bricked" so I have no chance to recover it at all.
I am totally in-familiar with rooting machine and I have no access to Linux machine.
Any advice is welcome.
Thx in advance.
Machine: Nexus 7 v2- wifi version Android 4.4.2, Build - KOT49H
Computer: Windows 7 64 bit system
Nexus Root Toolkit v1.8.2
Worked procedure:
1/ Follow the "Initial Setup - Full Driver Installation Guide- Automatic + Manual"
Step 1 to Step 4, install the drivers on the computer. and "Full Driver Test" passed
2/ Click "Unlock", pressed "Y" to proceed. - Device went into a screen asking me to select and confirm, I used the "Vol +" to select "yes" and pressed "power" to confirm, but nothing happened on both computer and device after the "power" switch was pressed. Instead, it freeze the device. nothing is responding even after 10 minutes.
3/ I have pressed the "power button again for 5 sec. and device shutdown to black screen.
4/ Since then, every time I try to start the device, the machine first show a "Google" , then a "rotating flower pattern" and won't started. i.e. - "the flower pattern" keeps looping.
5/ on the computer side, no matter what command is given in Nexus Root Toolkit, a notification of ADB device was not found error comes up.
Consequence
A) Device can be switched on and off by pressing "power" button. when switch on, it display "Google" , then a rotating flower pattern, and never end.
Switch the power button for 5 sec again, device switch off.
B) When device is off, press 'power' and "vol -" will switch on the device to a menu with a robot lay down, options "Restart bootloader", "Recovery mode", "Power off" and "Start" can be selected.
C) For "restart bootloader" the screen goes black for 2 sec, then the menu appear again with "Start" option. i.e.- no error no message
D) For "Start " - the device just just act like normal start, end up in a looping rotating flower pattern.
E) For " Recovery mode" - device screen goes black for 3 sec. show "Google" then show a dead robot with an exclamation mark on it, message " No command" is showing. - After awhile, device restarted and end up in the rotating flower pattern.
F) When plugged in, Window 7 can detect the device, when teh device is in the menu, "Android Bootloader Interface" is shown in Windows Device manager, when the device is starting, " Nexus 7" is detected in Windows Device manager but not both.
chanwt12000 said:
Hi, I am a Nexus 7 user and was tried to root my device using the Toolkit v1.8.2
I am not experience in rooting Android machine, this was my first time and unsuccessful. My device is now could not be started up.
The following is all information I summarized for this exercise, and would like to seek all advice on the followings.
--1 Is my device "recoverable" if yes, how and what do I need to do please?
--2/ or is it definitely "bricked" so I have no chance to recover it at all.
I am totally in-familiar with rooting machine and I have no access to Linux machine.
Any advice is welcome.
Thx in advance.
Machine: Nexus 7 v2- wifi version Android 4.4.2, Build - KOT49H
Computer: Windows 7 64 bit system
Nexus Root Toolkit v1.8.2
Worked procedure:
1/ Follow the "Initial Setup - Full Driver Installation Guide- Automatic + Manual"
Step 1 to Step 4, install the drivers on the computer. and "Full Driver Test" passed
2/ Click "Unlock", pressed "Y" to proceed. - Device went into a screen asking me to select and confirm, I used the "Vol +" to select "yes" and pressed "power" to confirm, but nothing happened on both computer and device after the "power" switch was pressed. Instead, it freeze the device. nothing is responding even after 10 minutes.
3/ I have pressed the "power button again for 5 sec. and device shutdown to black screen.
4/ Since then, every time I try to start the device, the machine first show a "Google" , then a "rotating flower pattern" and won't started. i.e. - "the flower pattern" keeps looping.
5/ on the computer side, no matter what command is given in Nexus Root Toolkit, a notification of ADB device was not found error comes up.
Consequence
A) Device can be switched on and off by pressing "power" button. when switch on, it display "Google" , then a rotating flower pattern, and never end.
Switch the power button for 5 sec again, device switch off.
B) When device is off, press 'power' and "vol -" will switch on the device to a menu with a robot lay down, options "Restart bootloader", "Recovery mode", "Power off" and "Start" can be selected.
C) For "restart bootloader" the screen goes black for 2 sec, then the menu appear again with "Start" option. i.e.- no error no message
D) For "Start " - the device just just act like normal start, end up in a looping rotating flower pattern.
E) For " Recovery mode" - device screen goes black for 3 sec. show "Google" then show a dead robot with an exclamation mark on it, message " No command" is showing. - After awhile, device restarted and end up in the rotating flower pattern.
F) When plugged in, Window 7 can detect the device, when teh device is in the menu, "Android Bootloader Interface" is shown in Windows Device manager, when the device is starting, " Nexus 7" is detected in Windows Device manager but not both.Hi, I am a Nexus 7 user and was tried to root my device using the Toolkit v1.8.2
I am not experience in rooting Android machine, this was my first time and unsuccessful. My device is now could not be started up.
The following is all information I summarized for this exercise, and would like to seek all advice on the followings.
--1 Is my device "recoverable" if yes, how and what do I need to do please?
--2/ or is it definitely "bricked" so I have no chance to recover it at all.
I am totally in-familiar with rooting machine and I have no access to Linux machine.
Any advice is welcome.
Thx in advance.
Machine: Nexus 7 v2- wifi version Android 4.4.2, Build - KOT49H
Computer: Windows 7 64 bit system
Nexus Root Toolkit v1.8.2
Worked procedure:
1/ Follow the "Initial Setup - Full Driver Installation Guide- Automatic + Manual"
Step 1 to Step 4, install the drivers on the computer. and "Full Driver Test" passed
2/ Click "Unlock", pressed "Y" to proceed. - Device went into a screen asking me to select and confirm, I used the "Vol +" to select "yes" and pressed "power" to confirm, but nothing happened on both computer and device after the "power" switch was pressed. Instead, it freeze the device. nothing is responding even after 10 minutes.
3/ I have pressed the "power button again for 5 sec. and device shutdown to black screen.
4/ Since then, every time I try to start the device, the machine first show a "Google" , then a "rotating flower pattern" and won't started. i.e. - "the flower pattern" keeps looping.
5/ on the computer side, no matter what command is given in Nexus Root Toolkit, a notification of ADB device was not found error comes up.
Consequence
A) Device can be switched on and off by pressing "power" button. when switch on, it display "Google" , then a rotating flower pattern, and never end.
Switch the power button for 5 sec again, device switch off.
B) When device is off, press 'power' and "vol -" will switch on the device to a menu with a robot lay down, options "Restart bootloader", "Recovery mode", "Power off" and "Start" can be selected.
C) For "restart bootloader" the screen goes black for 2 sec, then the menu appear again with "Start" option. i.e.- no error no message
D) For "Start " - the device just just act like normal start, end up in a looping rotating flower pattern.
E) For " Recovery mode" - device screen goes black for 3 sec. show "Google" then show a dead robot with an exclamation mark on it, message " No command" is showing. - After awhile, device restarted and end up in the rotating flower pattern.
F) When plugged in, Window 7 can detect the device, when teh device is in the menu, "Android Bootloader Interface" is shown in Windows Device manager, when the device is starting, " Nexus 7" is detected in Windows Device manager but not both.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=2741375&stc=1&d=1399986292
http://forum.xda-developers.com/attachment.php?attachmentid=2741374&stc=1&d=1399986292
http://forum.xda-developers.com/attachment.php?attachmentid=2741373&stc=1&d=1399986292
I'll take up the task to help you. You are not bricked. You are stuck in something called a bootloop, which is basically when the device enters the boot sequence, but never finishes. The flower pattern that you are looking at us called the boot animation. The computer never recoginizes the tablet through ADB because the tablet never gets to that point.
The screen with the Android laying on his back is actually the bootloader itself. That's why restarting the bootloader brings you to the same screen. I actually want you to be in the bootloader screen. You already have the Nexus 7.2 drivers, so you're ahead of the game.
You also need to visit here to download TWRP 2.7. You also need to put the file in the same directory as the fastboot and adb files.
You need to boot into the bootloader, and run the command:
fastboot flash recovery <recoveryname>.img
This should get TWRP onto your device. You can then download a rom of your choice to put on the tablet. Since you will not have access to place files on the device through USB, you will have to sideload it. First, let's get recovery working, then come back to me if you need help sideloading the rom through ADB while in recovery.
Dear aarsyl,
Thx for your help and it is much better to know my device is not "bricked". Thx again!
Thx for your detailed explaination and I feel much better by knowing a little bit more on what is going on.
>>>>You also need to visit here to download TWRP 2.7. You also need to put the file in the same directory as the fastboot and adb files.
[I also found it in my computer already .\WugFresh Development\data\Recovery_Custom\TWRP
but I downlaod it again from your link and put this file in the same directory where I find the fastboot.exe and adb.exe, which in my case is .\WugFresh Development\data\ ------ done.]
>>>>You need to boot into the bootloader, and run the command:
[- I supose you refer to my Nexus 7, so I will switch it on with the "power button + vol -" button. and get it into the bootloader.]
>>>>fastboot flash recovery <recoveryname>.img
[Here I got an query, what image file I need to use? is it the <openrecovery-twrp-2.7.0.0-flo> ? Do I neeed to run it as an adminstartor in Window 7?
so, do u mean I need to type: fastboot flash recovery openrecovery-twrp-2.7.0.0-flo.img ?
is it right?--(A)
if not, then I am not sure what recovery file to be used!
I do not have any other img file in package I downloaded previously
>>>>This should get TWRP onto your device. You can then download a rom of your choice to put on the tablet. Since you will not have access to place files on the device through USB, you will have to sideload it. First, let's get recovery working, then come back to me if you need help sideloading the rom through ADB while in recovery.
Not quite understand it this bit, but as you say. it can wait later.
So assume I do the "fastboot flash recovery <recoveryname>.img and get the TWRP on the Nexus 7.
What do I expect to see from the nexus screen. Does it have any note saying completed, or shuold I expect a reboot of the Nexus.
I think one of the problem dealing with these kind of thing is lack of acknowledgment fromt eh machine so we do not know if the operation is successful or not.
chanwt12000 said:
Dear aarsyl,
Thx for your help and it is much better to know my device is not "bricked". Thx again!
Thx for your detailed explaination and I feel much better by knowing a little bit more on what is going on.
>>>>You also need to visit here to download TWRP 2.7. You also need to put the file in the same directory as the fastboot and adb files.
[I also found it in my computer already .\WugFresh Development\data\Recovery_Custom\TWRP
but I downlaod it again from your link and put this file in the same directory where I find the fastboot.exe and adb.exe, which in my case is .\WugFresh Development\data\ ------ done.]
>>>>You need to boot into the bootloader, and run the command:
[- I supose you refer to my Nexus 7, so I will switch it on with the "power button + vol -" button. and get it into the bootloader.]
>>>>fastboot flash recovery <recoveryname>.img
[Here I got an query, what image file I need to use? is it the <openrecovery-twrp-2.7.0.0-flo> ? Do I neeed to run it as an adminstartor in Window 7?
so, do u mean I need to type: fastboot flash recovery openrecovery-twrp-2.7.0.0-flo.img ?
is it right?--(A)
if not, then I am not sure what recovery file to be used!
I do not have any other img file in package I downloaded previously
>>>>This should get TWRP onto your device. You can then download a rom of your choice to put on the tablet. Since you will not have access to place files on the device through USB, you will have to sideload it. First, let's get recovery working, then come back to me if you need help sideloading the rom through ADB while in recovery.
Not quite understand it this bit, but as you say. it can wait later.
So assume I do the "fastboot flash recovery <recoveryname>.img and get the TWRP on the Nexus 7.
What do I expect to see from the nexus screen. Does it have any note saying completed, or shuold I expect a reboot of the Nexus.
I think one of the problem dealing with these kind of thing is lack of acknowledgment fromt eh machine so we do not know if the operation is successful or not.
Click to expand...
Click to collapse
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I decided to have a go with the downloaded twrp img file.
I launched the command " fastboot flash recovery openrecovery-twrp-2.7.0.0-flo.img" from a command window as an adminstrator.
The command failed with an error saying (remote: Bootloader is locked)
And when I check the Nexus 7 screen, it does said "Locked Status - locked" in the last line.
photo showing both the computer and teh Nexus 7 screen.
Oh, I hadn't realized that you were still locked. No wonder you're not getting anywhere.
Reboot into the bootloader, and run:
fastboot oem unlock
Follow the screen instructions to unlock the bootloader, then run the command to flash the recovery. I advise changing the recovery name to something shorter and simpler, like twrp27flo.img, for example.
aarsyl said:
Oh, I hadn't realized that you were still locked. No wonder you're not getting anywhere.
Reboot into the bootloader, and run:
fastboot oem unlock
Follow the screen instructions to unlock the bootloader, then run the command to flash the recovery. I advise changing the recovery name to something shorter and simpler, like twrp27flo.img, for example.
Click to expand...
Click to collapse
Hi, Nice to have reply from you again.
Ammm. I switch on the device to the bootloader alright. run teh command "fastboot oem unlock"
On teh command window, it said" < waiting for device>
and there is no visible change on the device screen.
It already last for 10 minutes now.
I do noted that both windows are freezed and do not respond to key press and button press respectively. No responds on both the device and computer.
How lond does this process take to show the mentioned "screen instruction"? I don't see one!
chanwt12000 said:
Hi, Nice to have reply from you again.
Ammm. I switch on the device to the bootloader alright. run teh command "fastboot oem unlock"
On teh command window, it said" < waiting for device>
and there is no visible change on the device screen.
It already last for 10 minutes now.
I do noted that both windows are freezed and do not respond to key press and button press respectively. No responds on both the device and computer.
How lond does this process take to show the mentioned "screen instruction"? I don't see one!
Click to expand...
Click to collapse
wow.. it is unlocked now!
Should I continue to use the "fastboot recover command with TWRP file" as per your advise or should I continue to use the "Root" command in NexusRoot Toolkit ??
It is very happy to see there is progress.. Thx...
please keep coming...
I would go with using fastboot to install TWRP. In truth, to truly "root" your device, you actually need a working rom on the device. Otherwise, rooting will be in vain. Unlocking the device was the most important.
aarsyl said:
I would go with using fastboot to install TWRP. In truth, to truly "root" your device, you actually need a working rom on the device. Otherwise, rooting will be in vain. Unlocking the device was the most important.
Click to expand...
Click to collapse
Hi again,
Yes. my device is now boot up as brand new.
One side observation though, every time I issue command through window 7 in a command window, everything will freeze up, (not remember if I unplugged the device) until I press the power button to restart the Nexus 7. Same for the last time when i did the unlock and this time recovery.
The hesitation was how do I know when to do this, was worrying there is still some communication between the two machines if I unplug or interfer, may just disturb the communication and corrupt files. -- I normally give it some 10 minutes before I do the unplug and restart. any comment or advice?
Anyway, the device is now up and running. What is the status now? is it with the original version of software? or TWRP version or what?
The device is now remain "unlocked" - is it ok or I need to lock it again?
You have mentioned to download a "Rom", what about it, it is only need if i want to continue to "root " the device?
Sorry for so much question.
I am so happy to see it comes alive again but really would like to understand the current status of it.
Thank again. aarsyl
To be honest, I'm not entirely sure what the status of your device is right now. I was under the implication that you had no Rom on the device. Since you are trying to root for the first time, then yes, you are on the stock software that comes with the device. If you search your app drawer and find the SuperSU app, then you are already rooted, my friend. If it is not there, then search for SuperSU 1.94 in Google, and download the zip file. Then reboot into recovery and flash it.
In other news, I am happy that you got your device working, and I am more than happy to help. The only thing that I don't do is recommend roms. I encourage users to explore different roms for themelves.
[b]AarSyl[/b] said:
To be honest, I'm not entirely sure what the status of your device is right now. I was under the implication that you had no Rom on the device. Since you are trying to root for the first time, then yes, you are on the stock software that comes with the device.>>> since you mentioned I probably have no rom on the device...and you also mentioned "stock software with my device"..I think these are 2 different things right? because i always thought they are the same thing.
If you search your app drawer and find the SuperSU app, >>>App drawer, do you refer to the Apps Tab under Setting? I don't have SuperSU in there.
then you are already rooted, my friend. If it is not there, then search for SuperSU 1.94 in Google, and download the zip file.
Then reboot into recovery and flash it. >>>>I have to say you lost me, do u mean use the ""fastboot flash recovery <Super SU file>.img" command?
In other news, I am happy that you got your device working, and I am more than happy to help. The only thing that I don't do is recommend roms. I encourage users to explore different roms for themelves.>>>No problem, I shall be looking out for that
Click to expand...
Click to collapse
Well, sure I will continues to look up the information from the basic, but at the moment Would you please enlight me for the following 2 questions
1/ Should I uncheck or check the USB debugging tab under Developer options - it will be very good if you would like to explain a little on what it does, so I will have a more l\idea what it does when when do i need them.
2/ As i said, teh device is now unlocked, is it ok to leave it unlock or should i have it lock? - again if you would explain a little more on this that will be marvest.
cheers
chanwt12000 said:
Well, sure I will continues to look up the information from the basic, but at the moment Would you please enlight me for the following 2 questions
1/ Should I uncheck or check the USB debugging tab under Developer options - it will be very good if you would like to explain a little on what it does, so I will have a more l\idea what it does when when do i need them.
2/ As i said, teh device is now unlocked, is it ok to leave it unlock or should i have it lock? - again if you would explain a little more on this that will be marvest.
cheers
Click to expand...
Click to collapse
I'm sorry for the long delay. I got locked out trying to log in after I changed my username twice, and it just got messy for me. At any rate....the SuperSU zip file is to be flashed through recovery. When you boot into recovery, select Install, then navigate through the device to find the folder that the file is located. Follow the screen directions to flash items.
USB Debugging needs to be checked for ADB to work, so.....yeah....leave it on.
You don't have to relock your device unless you have to bring it back to the store for repairs. It only stops you from making changes in the bootloader, such as flashing new recoveries, and I think that most fastboot commands might be blocked. I have never tried to use fastboot on a locked device, so I really don't know. Leaving the device unlocked doesn't make it vulnerable or anything, at least to my knowledge.
AarSyl said:
I'm sorry for the long delay. I got locked out trying to log in after I changed my username twice, and it just got messy for me. At any rate....the SuperSU zip file is to be flashed through recovery. When you boot into recovery, select Install, then navigate through the device to find the folder that the file is located. Follow the screen directions to flash items.
USB Debugging needs to be checked for ADB to work, so.....yeah....leave it on.
You don't have to relock your device unless you have to bring it back to the store for repairs. It only stops you from making changes in the bootloader, such as flashing new recoveries, and I think that most fastboot commands might be blocked. I have never tried to use fastboot on a locked device, so I really don't know. Leaving the device unlocked doesn't make it vulnerable or anything, at least to my knowledge.
Click to expand...
Click to collapse
Thx for your advices AarSyl,
I have successfully root the device and get the Super user app running by following one of tutorial video.
For the first time, when I start at teh bootloader and conduct a "Recovery", it shows a dead robot again but without "no command". I have to redo the fastboot command in the command window with the TWRP recovery file once again. (but this time is very smooth no need to unplug cable that sorts of thing) then I get into the TWRP menu after "Recovery".
chanwt12000 said:
Thx for your advices AarSyl,
I have successfully root the device and get the Super user app running by following one of tutorial video.
For the first time, when I start at teh bootloader and conduct a "Recovery", it shows a dead robot again but without "no command". I have to redo the fastboot command in the command window with the TWRP recovery file once again. (but this time is very smooth no need to unplug cable that sorts of thing) then I get into the TWRP menu after "Recovery".
Click to expand...
Click to collapse
Great. I'm happy that it is working for you. A little tip...download Quick Boot from the Play Store. With one touch, you can power off, boot into the bootloader, boot into recovery, or reboot Android.
I got my G4 H815 yesterday and, like a few people, I had a lot of updates when first starting up, but not android 6. I was going to try installing it manually but I am unable to get the phone into bootloader mode, either by using adb command or using the hardware method (VOL UP+PWR).
Using the adb method "adb reboot bootloader" I get the message "error: device unauthorized. This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server if that seems wrong. Otherwise check for a confirmation dialog on your device." There isn't, of course, any confirmation dialog on my device.
Using the hardware keys method, when I turn my phone off (I pull the battery each time to ensure its really off) and hold VOL UP+PWR together, I get a "Display IMEI" white screen with a barcode and a message to press the power button to restart the phone.
USB debugging and Enable OEM Unlock are both enabled. Android version is 5.1, kernel version is 3.10.49, build number is LMY47D and software version is V10e-234-10.
Any help with this would really be appreciated.
1. firmware
CN firmware:X(U1005)-Android8.1-CN-190123-------chinese firmware,no google play,SN number begin with U1005
update:X(U1005)-Android8.1-CN-20190225update2:X(U1005)-Android8.1-CN-20190514
NON EU firmware:X(U1005)-Android8.1-ALLDOCUBE-NONEU-190116------with google play,but for Non-European Region.SN number begin with U1005
update:X(U1005)-Android8.1-ALLDOCUBE-NONEU-190313
EU firmware：X(U1005E)-Android8.1-ALLDOCUBE-EU-190108------with google play,but for European Region.SN number begin with U1005E
update:X(U1005E)-Android8.1-ALLDOCUBE-EU-190313
2. UNLOCK,TWRP,ROOT,AND OTHER
Ⅰ.UNLOCK
"Settings"-"System"-"About tablet"-tap "build number" six times-go back to "System"-"Developer options"-let "OEM unlocking" enable.
download google adb and fastboot tool for windows
"Developer options"-let "USB debugging" enable.connect the tablet to your windows computer via type-c cable.The "Allow USB debugging" window pops up on the machine and clicks the "OK" button to allow
unzip platform-tools-latest-windows.zip file, open the "platform-tools" folder.Hold down the shift key and right-click to open the command line or power shell window
type “adb devices” in command line,if the result is "0123456789ABCDEF device"，that means the type-C line is well connected and the ADB debugging is successfully opened.
type "adb reboot bootloader" in command line to let tablet goto fastboot mode.
type "fastboot getvar unlocked" in command line.if the result is "unlocked: no",that means oem is locked.
type "fastboot oem unlock" in command line.and the tablet will metion you press "volume up" to allow unlock the tablet,press volume-up button on tablet.
if the command line shows like:
"(bootloader) Start unlock flow
OKAY [ 5.970s]
finished. total time: 5.974s"
that means Unlock success。
or you can type "fastboot getvar unlocked" in command line.if the result is "unlocked: yes" ,that also means Unlock success。
PS: unlock will wipe out all data.
Ⅱ. TWRP
twrp-u1005-20190113-zh.img------by WUXIANLIN default chinese language
update:twrp-u1005-20190223-zh.img by WUXIANLIN
recovery-U1005-TWRP-noMTP-1204.img------complied by me,default english language ,no mtp ,some bug
update:twrp-u1005-en-20190313.img
type "fastboot flash recovery xxxx.img" in command line.xxxx.img is one of two twrp images you have downloaded above ,and please place the twrp images file in " platform-tools"folder .
When tablet boot, you can press the volume up button to select recovery mode
Ⅲ. ROOT
downloadMagisk-v20.0.zip,and place zip file in "platform-tools" folder
in twrp mode--cancel "enter password "--then Swip to allow Modifications--Advanced-ADB Sideload-Swipe to Start Sideload.
type "adb sideload Magisk-v20.0.zip " in command line to install magisk Module
reboot the tablet ,and the tablet is rooted 。
install full magisk manager app
Ⅳ. OTHER
U1005-decrypt-data-sign.zip,in twrp mode .use adb sideload command flash the zip file,and then format data partition
3. tips
Do not use the "Format All + Download" option when flash firmware with MTK SP flash tool.
when the wire flashing process is interrupted, the machine may enter a fake dead state, and the mtk spflashtool does not recognize the port. The machine needs to be completely powered off or powerless before it can be reset.
4.ROMS
First thanks to wuxianlin.wuxianlin has ported lineageos 15.1 to alldocube x.
lineageos device link:android_device_cube_u1005 by wuxianlin
lineageos vendor link:android_vendor_cube_u1005 by wuxianlin
lineageos 15.1 rom link: lineage-15.1-20190303-UNOFFICIAL-u1005.zip for cn firmware by WUXIANLIN
lineage-15.1-20190406-UNOFFICIAL-u1005.zip for cn firmware by WUXIANLIN
lineage-15.1-20190320-UNOFFICIAL-u1005.zip uploading
Guys who have the ability to port ROM can also refer to his device and vendor for porting.
Thanks WUXIANLIN again!
5.kernel source
CUBE-kernel-U1005
RESERVE
Wonder if it has project treble and if we can flash gsi on it
It does have Treble.
But only Treble without Seamless Updates
Please share some official updates !
hassan_1000 said:
Wonder if it has project treble and if we can flash gsi on it
Click to expand...
Click to collapse
you can flash system-aonly PT image
wangyiling said:
you can flash system-aonly PT image
Click to expand...
Click to collapse
Thanks for all support wangyiling... :highfive:
Thanks wangyiling!!!
Thank you wangyiling
Could you perhaps help, I did choose the 'download' option only, not with the 'Format All', but some error occurred,
and now the tablet does not show any sign of life; It is even not detected by SP Flash Tool.
Is there anything to do at this point? I tried pressing the power button for ages and ages, but nothing would happen.
The tablet had a charge of approximately 80%, but it even won't charge at this point.
Is this the fake-dead state that you were referring to? What is there to do? :-/
MiOBi said:
Thank you wangyiling
Could you perhaps help, I did choose the 'download' option only, not with the 'Format All', but some error occurred,
and now the tablet does not show any sign of life; It is even not detected by SP Flash Tool.
Is there anything to do at this point? I tried pressing the power button for ages and ages, but nothing would happen.
The tablet had a charge of approximately 80%, but it even won't charge at this point.
Is this the fake-dead state that you were referring to? What is there to do? :-/
Click to expand...
Click to collapse
Try first to click Download on SP Flash Tool, then connect the cable and then press the Power Button (it can take some time, keep pressing) until the program detect the tablet and start to flash the Rom...
There's one guy on 4PDA forum that wake up his X like this...
Perhaps you will have the same luck!
MiOBi said:
Thank you wangyiling
Could you perhaps help, I did choose the 'download' option only, not with the 'Format All', but some error occurred,
and now the tablet does not show any sign of life; It is even not detected by SP Flash Tool.
Is there anything to do at this point? I tried pressing the power button for ages and ages, but nothing would happen.
The tablet had a charge of approximately 80%, but it even won't charge at this point.
Is this the fake-dead state that you were referring to? What is there to do? :-/
Click to expand...
Click to collapse
I'm on vacation.
make sure that the driver for MTK is installed properly (the driver for MTK should be very easy to find on web). you also can try this mtk inf driver
if it's the fake-dead state mentioned by me, the machine can only be reset untile the battery is completely cut off or the battery power is exhausted.
my above steps use the ADB or FastBoot command to flash the file like twrp , just in order to avoid the machine into a fake-dead state because of interruption in flash .
best luck @MiOBi
Thank you wangyiling for replying while on your vacation Thank you SafuPT too for trying...
I'm afraid nothing has helped, no matter how long I pressed... Is there a way to drain the battery quickly? it had almost %80, so I think it would take weeks to drain by itself :-/
Thanks for the TWRP / Root Guide.
All working well here just need better battery life
Do we have alternative option for camera app that could perform better than stock one?
is there any screen modes, like on samsung?
I read screen colors are inacurate ...
thanks
Has anyone successfully rooted their device and installed Miravision? If so does it work well?
Vertron said:
Has anyone successfully rooted their device and installed Miravision? If so does it work well?
Click to expand...
Click to collapse
I have the same question! Mine it's still in customs, hope to received it next week...
If you don't like the screenshot button (I find I keep hitting it by accident), or the layout of the buttons in the 'nav bar', you can follow this article to change them: https://www.xda-developers.com/how-to-change-your-nav-bar-icons-or-re-arrange-the-buttons-without-root/
You will first need to enable developers mode (go to 'Settings->System->About tablet', and keep tapping 'Build number' until developer mode is enabled). You should now have the 'Developer options' in 'System'.
Go to 'Developer options' and enable 'USB debugging'. Connect to your PC and follow the instructions.
I found a 'sysui_nav_bar' setting of ';left[1.0WC],back[1.0WC],home[1.0WC],recent[1.0WC],right[1.0WC];' was similar to my other Android devices.
Does this tablet support 10bit HDR x265 content? When I am playing 10bit HDR x265 content the colours look washed out and dull.
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...
Hi!
I recently bought an LG G4 from an online seller. The cell phone itself is working fine, but it has some problems. It is a refurbished model.
I will very much appreciate any help.
The cell phone is actually a F500L model (I checked it by looking at the motherboard), but in the software information it shows to be a model H81510h.
The phone is not rooted. But I believe that someone did it, changed the device's descriptions and then uninstalled it.
It is an android 5.1, but I cannot update using the update center. There it shows that it is already in the latest version.
In the developer settings, I try to enable OEM unlock, it activates for 1 second and deactivates automatically.
I try to do the hard reset, but when restarting to start the process, it presents an error "Secure booting error 1002".
I can activate USB debugging, it is recognized in ADB tools and I can send commands to it. But it does not start the bootloader with the command "adb reboot bootloader", and it presents the same error "Secure booting error 1002" if I try to send the command "adb reboot recovery".
I can activate the Download mode (by pressing the VOL UP button and inserting the USB cable), but it is not recognized by LGup (UNKNOW / COM5 H81510h), LGup does not let me work with it.
In the LG Flash Tool, it does not start the flash process, when it reaches "BIN CRC Check" it presents the error "Failed PreviousLoad0". (I already changed the port to COM41)
In LG Bridge, it is recognized as F500L and shows that there is an update. But when trying to update, it does the first steps, but after the download, when installing it gives an error and asks to start over.
I have tried to use UPPERCUT_1.0.0.0, without success.
I do not know what else to do...
Any help will be appreciated.