Related
Hello there,
I have recently received a Motorola Xoom MZ604 Wifi with the problem described above.
Things I have already tried:
1. Factory Reset
2. Pressing every button combination long press on power button etc etc..
3. Unlocking the device - Putting Custom Recovery (All of them)
4. Acessing adb and fastboot - Flashing stock ROM back onto it from the Stock Images from XDA
5. Try Rooting it (no luck) USB Debugging is required for rooting and I cannot access the USB Debugging option since the Xoom doesn't boot up.
Is there anything else I could try or maybe I'm doing something wrong?
BUMP
Also tried to do the SBF/RSD Format But still no luck, the RSD said it has PASSED but the Xoom still won't boot up - the Motorola logo stays for about 6 seconds and then disappears and loops again.
Qll I can suggestion is to preform the steos from motodev to unlock your device.
Then use fastboot to flaahing the imgs.
Again all the steps and imgs are at motodev.
If yoi follow that to the letter and it still hangs/loops at the "M" then I would say one or more of the partitions are corrupt which is basically the end of that tablet...without physically repairing it
runandhide05 said:
Qll I can suggestion is to preform the steos from motodev to unlock your device.
Then use fastboot to flaahing the imgs.
Again all the steps and imgs are at motodev.
If yoi follow that to the letter and it still hangs/loops at the "M" then I would say one or more of the partitions are corrupt which is basically the end of that tablet...without physically repairing it
Click to expand...
Click to collapse
If i try unlocking the device through motorola website then in fastboot I get this error "FAILED (remote: (00120000))
finished. total time: 0.245s"
slazzenger said:
If i try unlocking the device through motorola website then in fastboot I get this error "FAILED (remote: (00120000))
finished. total time: 0.245s"
Click to expand...
Click to collapse
What reads out on the tablet?
runandhide05 said:
What reads out on the tablet?
Click to expand...
Click to collapse
"Failed to process command error (0x120000) that's after the
"fastboot oem get_unlock_data" command from motorola website in order to get the unlock code
slazzenger said:
"Failed to process command error (0x120000) that's after the
"fastboot oem get_unlock_data" command from motorola website in order to get the unlock code
Click to expand...
Click to collapse
Use fast boot command
"fastboot oem unlock"
The xoom specific instructions should be followed. The get unlock data is for newer devices
runandhide05 said:
Use fast boot command
"fastboot oem unlock"
The xoom specific instructions should be followed. The get unlock data is for newer devices
Click to expand...
Click to collapse
Oh I thought that the unlock from motorola website was different from the fastboot oem unlock. I've already tried doing that and flashing all the images - still no luck :<
Ive scoured the web for the solution to this but for the life of me can not get my boot loader to unlock. I know enough of this to get me by, but obviously I am not an expert by any means. This is one of the pre recall tablets that I had rooted to avoid the kill code. It was so long ago when I did this that I don't completely remember how I did it. But apparently I didn't have to unlock the bootloader to root it.
I haven't used this tablet in ages and decided to pick it up again but was getting errors that I needed to update google play services but it was not allowing me to do so. I have the Custom Rom Blisspop installed but it appears that they have quite support for it. So I was going to wipe that off and load Lineage. so I tried to get into recovery and it kept just stalling at the loading screen. So now I am wondering if I even flashed a recovery to it to make a backup. Regardless I wouldn't want to restore and risk getting the kill code delivered.
So the next thing I tried to do was flash twrp (and yes I did use the NVidia shield tablet version) and it said that it was successful but still could not boot into recovery. Then I noticed that it said my bootloader was locked on the bootloader screen. So I installed the platform tools and the drivers and adb was recognizing my tablet and everything was good. Until.... I did "adb reboot bootloader" and then "fastboot devices" or even "fastboot oem unlock" nothing worked. No devices would show up. But this whole time adb works. No matter what drivers I install or anything, I cannot get fastboot to recognize the device. I even changed the USB port to the back of my pc straight off the mobo and ran the cmd as admin and nothing is working.
I am starting to get discourage that my efforts are going to be for naught. Expecially since I am not sure exactly how I rooted it in the first place? which is completely my fault for not documenting it. Any and all help is greatly appreciate and I apologize if this has already been solved else were or is being posted to an incorrect location.
Thank you!
Brandon
Ok, i finally figured out that the fastboot driver wasnt working. I ran "adb reboot bootloader" and while in fastboot mode, i found in the PC's device manager that there was an error with the driver. I manually updated it and i am finally able to successfully run "fastboot oem unlock".
But now im getting an error with it saying it failed....
Code:
C:\WINDOWS\system32>fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.002s
I am unsure what this means and will do some more researching. I will post back if i make any headway. Once again, i thank anyone in advance for any assistance they may be able to provide.
Apparently i had to unplug the tablet after installing the driver for fastboot before "fastboot oem unlock" would work. But it now says "Device = unlocked"!!!! hopefully i dont mess anything else up...
So now the tablet is "unlocked". I went to do "fastboot flash recovery twrp.img" and said it succeeded. I then proceeded to to do "fastboot reboot" and read that you should immediately load back into bootloader because some tablets will overwrite the recovery to stock if twrp isnt given a chance to correct this. So i did just that then volume keyed down to recovery and its back to doing the same thing where i am stuck on the nvidia logo loading screen. Does anyone have any suggestions on a fix for this? It appears that the tablet is refusing to enter recovery mode?
The reason why i need to get into recovery is for A: to make a backup. and B: to clear my current blisspop rom so that i can load a different Rom. I doubt it would be a good idea to install an OS on top of another OS. But who knows, maybe thats fine?
Code:
C:\Users\bwach>fastboot flash recovery twrp.img
target reported max download size of 570425344 bytes
sending 'recovery' (12426 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.579s]
finished. total time: 1.015s
C:\Users\bwach>fastboot reboot
rebooting...
finished. total time: 0.004s
Once again, I thank you for the help.
I was up all hours of the no ight last night trying to solve this with no luck. Is there anyone here who might be able to help me?
Still can't get recovery to load... Tried everything. I did "fastboot - w", I tried flashing lineage on top of bliss pop. Nothing I do will give me access to recovery...
Any ideas?
You have to use hardware keys combination (power + volume + or - not sure exactly which) to boot to twrp for the first time after flashing. So hold the combination while you're still in fastboot (bootloader) mode and release when you see nvidia logo. Good luck
Edit : fastboot reboot is a command that takes you to system, not recovery, to reboot to recovery by using commands you habe to type fastboot reboot recovery. But still, I believe you have to enter for the first time using the buttons combination but it may work with fastboot reboot recovery
It's possible the bootloader is too old for the current twrp release to boot. Which version of android is on the tablet? If it's like L, then you'll have to either update the bootloader manually or update stock first, then twrp will work. There's a note about this on the twrp device page.
I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved?
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.
Unfortunately, I can't describe a situation to get around this because the bootloader is still locked -- you'll probably want to unlock the bootloader and then leave it unlocked permanently if flashing the images using this method on a regular basis... I have personal notes that I've written for two scenarios. (1) is to gain root from stock and directions (2) is to flash the latest Android image and retain the data... Perhaps try the bottom block of steps (re-installing the factory image) --- but also unlock the bootloader from the top block of steps:
=======================
Code:
ROOT FROM STOCK
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - On phone: Settings > System > About Phone > tap on the 'build number' seven times.
2.0 - The Developer Options will now be visible in the main settings page. Enter it and turn on USB debugging and OEM unlocking
3.0 - Reboot into 'bootloader' and unlock bootloader (this will factory reset phone)
# adb reboot bootloader
# fastboot oem unlock
4.0 - Download 'twrp-3.2.3-0-walleye.img' to Desktop. Rename the File to 'pixeltwrp.img' (Not necessary to rename -- just did; https://dl.twrp.me/walleye/)
5.0 - Now boot your phone in bootloader mode. Turn off phone and Hold the Volume Down + Power, then release Power button or...
# adb reboot bootloader
6.0 - Run the following command
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Phone will boot in the TWRP mode. Push 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' to the phone's /data/ directory
# adb push ~/Downloads/twrp-pixel2-installer-walleye-3.2.3-0.zip /data/
# adb push ~/Downloads/Magisk-v16.7-1674.zip /data/
8.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files
9.0 - Reboot Phone
10.0 - Install busybox on /system/bin
UPDATE IMAGE TO LATEST WITHOUT WIPING PHONE
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - Remove "PIN UNLOCK" for security reasons
2.0 - Download the latest factory image from https://developers.google.com/android/images#walleye
3.0 - Unzip the factory image's ZIP and remove '-w' from "flash-all.sh"
4.0 - Reboot to bootloader
# adb reboot bootloader
5.0 - Flash image
# ./flash-all.sh
6.0 - Re-install magisk (https://dl.twrp.me/walleye/)
# adb reboot bootloader
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files (located on /data/) - If installing a new magisk version, run the magisk uninstaller first '/data/Magisk-uninstaller-20180719.zip'
7.1 - Wipe Dalvik/Cache and reboot
7.2 - Install MagiskManager and TWRP Manager if not installed
7.3 - Go to bootloader and flash kernel 'flashkernel-wahoo-v3.01.zip'
8.0 - Reboot phone
9.0 - Install busybox on /system/bin
10.0 - Re-add security unlock
=======================
...If these options don't work then the last thing I can think is to attempt to boot into the 'pixeltwrp.img' and switch the the primary slot (from Slot B to Slot A) and try to reboot.
Thanks @armordillo for your reply. I'm not planning on doing anything like this regularly - just trying to get my phone to boot or get the files off it so I can send it for repair.
Sadly I can't execute step 1 in either of your proposed processes - I literally can't get past the screen with the upturned robot
I can't turn on USB debugging, and I can't run OEM UNLOCK.
I'm completely stuck.
Can you get into the stock recovery?
On the screen with Andy in his back use the volume keys to scroll till you see Recovery Mode (or something similar) then hit the power button. At this point you should get another dead Andy. Press and hold Power button and then press the Volume UP button once. That should take you to the stock recovery. There will be a bunch of text with options for clearing cache adb sideload and other things.
Sent from my Pixel 2 using Tapatalk
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
domonicwhite said:
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
Click to expand...
Click to collapse
Sent from my Pixel 2 using Tapatalk
It says I can't do that because it's locked.
PiousInquisitor said:
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Thanks!
I don't mind not accessing my files - I'd be happy if I could just delete them.
I'm non technical and not familiar with TWRP but I'll do some searching and see what I can learn.
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Sorry for the newb questions (I literally just want my phone back)
Thanks again.
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
domonicwhite said:
Thanks!
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Click to expand...
Click to collapse
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Thank you! Does it matter that I'm using a Mac / OSX?
SargeStryker said:
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Click to expand...
Click to collapse
domonicwhite said:
Thank you! Does it matter that I'm using a Mac / OSX?
Click to expand...
Click to collapse
I'm pretty sure that it doesn't matter.
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse
Computer says no
It won't let me do this in the locked state -
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse
And doing one or both of these don't work from the bootloader either?
# fastboot oem unlock
# fastboot flashing unlock
In red? The color doesn't matter you can still choose recovery. Then hold power for a second and press up. You can the ADB sideload an OTA zip.
I'm pretty sure mine is red too, but it still let's me choose it
Did you accidently reset the bootloader lock after tinkering with your phone? that can cause this, my kid did it to my other phone after i had it messed with. so it was erroring out. nothing you can do but call your company see if you can exchange it for *faulty udate*
since your phone is *locked* just say you tried updating the software, and it reset the phoen to this. phones still locked so you have a shot at exchange..
they exchanged my *faulty update* for a new one. actually recieved it 5 days after making the request. before i had even sent the non working one back.
Sorry I didn't read where you said that it leads back to fastboot. I had to do an RMA due to this because I didn't unlock the bootloader. I then received a phone that cannot be bootloader unlocked (apparently all refurb phones can't). Horrible situation really and probably going to result in me never buying another pixel.
Hi,
I have an ROG Phone 5 that I unlocked and rooted using https://forum.xda-developers.com/t/asus-rog-phone-5-unlock-bootloader-and-root-guide.4261151/
I've realized I'm in a little bit over my head and I want to go completely back to a fresh start as if I'd just gotten the phone etc. I uninstalled Magisk but I don't know how to go about restoring the phone back to factory and relocking the bootloader. I know that re-locking the bootloader means I can't unlock it again and I'm okay with that, I just want to start fresh.
Let me know if you need any extra information.
Thanks!
Flash a stock boot image or install Magisk and use the restore include in that before deleting it again. After that, there is a fastboot command to lock the bootloader. I can't remember it off the top of my head, but the fastboot commands thread should help.
Isn't ASUS a special command?
It depends on your local
Only the Chinese version and the WW version have RAW files to be reinstalled.
Depending on your local, you can't restore it unless you create a raw file yourself.
It is presumed that local is different because the command does not pass.
twistedumbrella said:
Flash a stock boot image or install Magisk and use the restore include in that before deleting it again. After that, there is a fastboot command to lock the bootloader. I can't remember it off the top of my head, but the fastboot commands thread should help.
Click to expand...
Click to collapse
I flashed the stock rom but I can't figure out how to lock the bootloader again. I've tried;
fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot oem asus-lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
Any ideas?
Just in case you didn't know: once you lock the bootloader you cannot unlock it anymore. If there is no advantage (and I don't know any real good advantage, especially when you want to sell it) you should not do that.
EliseBelle said:
I flashed the stock rom but I can't figure out how to lock the bootloader again. I've tried;
fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot oem asus-lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
Any ideas?
Click to expand...
Click to collapse
If none of those work, then I have no idea.
Anubarak16 said:
Just in case you didn't know: once you lock the bootloader you cannot unlock it anymore. If there is no advantage (and I don't know any real good advantage, especially when you want to sell it) you should not do that.
Click to expand...
Click to collapse
EliseBelle said:
I know that re-locking the bootloader means I can't unlock it again and I'm okay with that, I just want to start fresh.
Click to expand...
Click to collapse
Gosh, for whatever reason I totally overlooked that
Let's pretend it never happened
Anubarak16 said:
Gosh, for whatever reason I totally overlooked that
Let's pretend it never happened
Click to expand...
Click to collapse
I agree, though. The nag screen and manual updates are a small price for being able to restore from home. Someone may even come up with a way to fix OTA eventually.
EliseBelle said:
I flashed the stock rom but I can't figure out how to lock the bootloader again. I've tried;
fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot oem asus-lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
Any ideas?
Click to expand...
Click to collapse
How did you enter Fastboot mode? Volume up + Power or through the stock recovery menu?
I have the same problem. If I enter Fastboot from TWRP, the "default implementation" error happens.
If I enter FastBoot mode by Volume Up+Power, the Tool does not recognize my device, so the command waits for a device...
Is it caused by configuration of the Tool? Or drivers? Please halp!
Hectorim said:
I have the same problem. If I enter Fastboot from TWRP, the "default implementation" error happens.
If I enter FastBoot mode by Volume Up+Power, the Tool does not recognize my device, so the command waits for a device...
Is it caused by configuration of the Tool? Or drivers? Please halp!
Click to expand...
Click to collapse
There is no TWRP for this device, so that is probably part of it.
It also sounds like you don't have drivers and / or fastboot installed properly.
So lemme get this straight...
When I boot into FastBoot, either by VolumeUp or by Tool-all-in-one, the phone SHOULD be picked up by the tool/PC? I mean when the phone is on the screen with "Fastboot Mode" in red lettering.
If it's a driver fault, how can I wipe them off my PC to try to start anew? Is there a step-by-step guide for dummies?
Hectorim said:
So lemme get this straight...
When I boot into FastBoot, either by VolumeUp or by Tool-all-in-one, the phone SHOULD be picked up by the tool/PC? I mean when the phone is on the screen with "Fastboot Mode" in red lettering.
If it's a driver fault, how can I wipe them off my PC to try to start anew? Is there a step-by-step guide for dummies?
Click to expand...
Click to collapse
I'm sure you could google fastboot and find 50.
Turns out my device isn't visible because Windows doesn't recognize it properly - it sees it as "Android" with an exclamation mark.
I have installed fastboot and adb drivers, Asus ROG specific USB drivers manually (as legacy), so I have no idea why it isn't recognized.
Hectorim said:
Turns out my device isn't visible because Windows doesn't recognize it properly - it sees it as "Android" with an exclamation mark.
I have installed fastboot and adb drivers, Asus ROG specific USB drivers manually (as legacy), so I have no idea why it isn't recognized.
Click to expand...
Click to collapse
For me the solution is to connect the device to the pc, boot into fastboot, then do the manual steps to install the adb drivers. If I install the drivers manually without the device already in fastboot, it will not recognize the device properly.
Good luck!
For what reason u want to re-roll from rooted phone?
aldomuwsa said:
For what reason u want to re-roll from rooted phone?
Click to expand...
Click to collapse
Because you didn't get an SSR.
Jokes aside, it's only really for warranty repair or in hopes it will enable OTA. You really shouldn't do it just for fun, though.
twistedumbrella said:
Because you didn't get an SSR.
Jokes aside, it's only really for warranty repair or in hopes it will enable OTA. You really shouldn't do it just for fun, though.
Click to expand...
Click to collapse
What kind u get from rooted phone by the way? Special hacking tools? Mod SSR Generate, or what?
Sorry for my newbie questions
aldomuwsa said:
What kind u get from rooted phone by the way? Special hacking tools? Mod SSR Generate, or what?
Sorry for my newbie questions
Click to expand...
Click to collapse
If its what u get, surely im gonna root my phone right now
aldomuwsa said:
What kind u get from rooted phone by the way? Special hacking tools? Mod SSR Generate, or what?
Sorry for my newbie questions
Click to expand...
Click to collapse
For the typical user, root is unnecessary for day to day life.
The biggest reasons people used to root were for ad blocking, sound enhancement, mobile hotspot functionality, and to modify the build.prop with values for another device (to bypass restrictions).
Of the previously mentioned uses, modifying the build.prop still requires root. Sound enhancement is a bit obsolete and mobile hotspot functionality or ad blocking can be achieved without root.
Unlike years ago, rooting is less of a "do not update or you miss the chance" process if you aren't using a Samsung. You don't have to jump into it if you don't have a reason and can always do it later if you find one.
For my Doogee N20 (Chinese Import), I have tried everything I just cannot seem to unlock the bootloader....HELP!
These are the following I have done:
Enable the "OEM Unlock" option & activated "USB debugging" under the phone's Developer Options
Downloaded ADB fastboot file (tried a number different download sources)
Download and installed USB driver (tried a number different download sources)
Ran 'CMD' prompt window in the ADB Fastboot folder (placed in C: drive) and run the following code:
C:\adb>adb devicesList of devices attachedN20EEA0000000013658 deviceC:\adb>adb reboot bootloader (the phone shows it is in 'FASTBOOT mode)C:\adb>adb devicesList of devices attached
(My phone is no longer listed. I have already restarted with 'disable signature verification in Windows 10' and also in Device Manager I have reinstalled the driver and now its under Android Device > Android ADB Interface.....but thought I continue the process).
C:\adb>fastboot oem unlock< waiting for device > (and its stuck at this point. the phone screen does not change and its still in 'FASTBOOT' mode....
What am I doing wrong? I tried various USB drivers and ADB exe. from various webpages. I tried 4 different USB ports front and back of my PC and 3 different USB cables including the original cable.
1. I am using the wrong ADB Fastboot file and wrong USB driver?
2. Is there something wrong with this particular phone because its a chinese import? (I am also having lots of problem with another phone I am trying to unlock bootloader Lenovo K5 Note (Chinese version) I think that one requires a password to unlock).
3. Is there something else I can try?
4. My aim is to install a custom ROM and nano GAPP and only install like 5 apps on it and to have it completly clean. I must first unlock the bootloader, right?
Try these drivers
Doogee N20 USB Driver for Windows (Official Mobile Driver)
Download the official Doogee N20 USB Driver for your Doogee Mobile. We also provide all other Doogee Mobile drivers for free.
gsmusbdriver.com
instead of the drivers related to Google devices as you did.
xXx yYy said:
Try these drivers
Doogee N20 USB Driver for Windows (Official Mobile Driver)
Download the official Doogee N20 USB Driver for your Doogee Mobile. We also provide all other Doogee Mobile drivers for free.
gsmusbdriver.com
instead of the drivers related to Google devices as you did.
Click to expand...
Click to collapse
Thank you for your reply, For the life of me, I dont know why but it worked this time. I installed this driver before and it didn't work but this time, I have decided to install both drivers, ADB & Mediatek. I didn't install the Mediatek before as its for flushing ROM.
I did the same thing before including restarting the PC once drivers installed and restart again in 'disable signature verification' mode and reinstalling the ADB driver once PC restarted in disable signature verification mode.
I also used a different ADK and Fastboot tools downloaded from here
C:\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\platform-tools>fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\platform-tools>fastboot flashing unlock
(bootloader) Start unlock flow
OKAY [ 15.311s]
Finished. Total time: 15.311s
CMD 'fastboot oem unlock' didn't work, but 'fastboot flashing unlock' worked for me....checking if bootloader is unlocked:
C:\platform-tools>fastboot devices
N20EEA0000000013658 fastboot
C:\platform-tools>fastboot oem device-info
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\platform-tools>fastboot getvar unlocked
unlocked: yes
Finished. Total time: 0.007s
C:\platform-tools>
CMD: 'fastboot oem device-info' didn't work, but 'fastboot getvar unlocked' worked.
Not sure how but it worked now. Nezt step is installing TWRP then 'GSI ARM64 A/B' ROM then nano Gapp , lets see what wonderfull mishap messing around with internals of a phone will bring us now
MANY THANKS