I have searched everywhere and have found nothing does a anyone know of a root method for the T-Mobile REVVL 4 model number 5062z
Texasblazed said:
I have searched everywhere and have found nothing does a anyone know of a root method for the T-Mobile REVVL 4 model number 5062z
Click to expand...
Click to collapse
Because phone is based on Mediatek MT6761 Helio A22 chipset you can use either MTK Easy SU or MTK-SU tool
jwoegerbauer said:
Because phone is based on Mediatek MT6761 Helio A22 chipset you can use either MTK Easy SU or MTK-SU tool
Click to expand...
Click to collapse
wrong, its a qualcomm
So can this device be rooted or not? Correct replies only would be great.
I am actively working towards it. The phone is def TCL....a lot of the package-names give that away. I installed a new Linux distro yesterday in hopes of getting to the bootloader. There might be an added advantage to loading a DSU in Developer Opyions...will update ASAP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
like this?
krayzieiyian23 said:
View attachment 5351809like this?
Click to expand...
Click to collapse
I can't get the DSU loader to work on mine. It downlaods and says it's ready so I tap on the PROCEED button or whatever and it just reboots back to my Android 11 Stock over and over.
(
I know little about Android development but I have the device it's not my daily driver so I can test stuff on it and if it goes south it's no big deal. Btw the revvl 4+ is the Qualcomm model, the 4 is the mediatek soc.
clintongsan said:
I am actively working towards it. The phone is def TCL....a lot of the package-names give that away. I installed a new Linux distro yesterday in hopes of getting to the bootloader. There might be an added advantage to loading a DSU in Developer Opyions...will update ASAP.
Click to expand...
Click to collapse
Have you had any luck on this yet???
I selected the first DSu , let it install and now the bootloader is corrupt. ( which im pretty sure means its inoperable) so the verity is definitly disabled. I can load into fastboot and baout to test the fastboot oem unlock.
clintongsan said:
I can't get the DSU loader to work on mine. It downlaods and says it's ready so I tap on the PROCEED button or whatever and it just reboots back to my Android 11 Stock over and over.
Click to expand...
Click to collapse
I was bale to let it install. You gotta downgrade to the first firmware it came with and let the DSU install. My dm-verity is corrupted which is, Im pretty sure disabled, and im able to boot into fastboot
Official Bootloader Unlock for T-Mobile REVVL 4G (TMRVL4G)
Unlock DeVops by selecting build number 5 or 6 times. get usb debugging and fastboot oem unlock. if it is not there go to about phone and select the first DSU. itll reboot and say your dm-verity is corrupted. Was then able to boot fastboot by adb reboot fastboot getting the Android with an exclamation coming out of his chest, held power vol + then pressing vol - fastbootd prompted. once your in fastbootd select reboot recovery and then youll get a recovery, fastboot and reboot selection. select fastboot and then you will be able to fastboot devices. once you get an indication your device is there then I used tiny adb with the command: fastboot flashing unlock_critical. An, are you sure? prompt in adb and press y then enter. it'll unlock the bootloader. and boot Orange_state and tell you your device is unlocked.
Anyone found a stock firmware for this yet?
sketchscarz said:
Official Bootloader Unlock for T-Mobile REVVL 4G (TMRVL4G)
Unlock DeVops by selecting build number 5 or 6 times. get usb debugging and fastboot oem unlock. if it is not there go to about phone and select the first DSU. itll reboot and say your dm-verity is corrupted. Was then able to boot fastboot by adb reboot fastboot getting the Android with an exclamation coming out of his chest, held power vol + then pressing vol - fastbootd prompted. once your in fastbootd select reboot recovery and then youll get a recovery, fastboot and reboot selection. select fastboot and then you will be able to fastboot devices. once you get an indication your device is there then I used tiny adb with the command: fastboot flashing unlock_critical. An, are you sure? prompt in adb and press y then enter. it'll unlock the bootloader. and boot Orange_state and tell you your device is unlocked.
Click to expand...
Click to collapse
I tried this with no luck.
OEM unlock and usb debugging is on.
adb reboot fastboot
This brings me to fastbootd which seems to be the only place for running fastboot commands. I tried going to recovery but theres no option to go to fastboot. I think mine is running anewer version.
fastboot oem unlock gives this error:
FAILED (remote: Command not supported in default implementation)
fastboot flashing unlock and unlock_critical gives this error:
FAILED (remote: Unrecognized command flashing unlock_critical)
Any thoughts or ideas?
mfoster978 said:
I tried this with no luck.
OEM unlock and usb debugging is on.
adb reboot fastboot
This brings me to fastbootd which seems to be the only place for running fastboot commands. I tried going to recovery but theres no option to go to fastboot. I think mine is running anewer version.
fastboot oem unlock gives this error:
FAILED (remote: Command not supported in default implementation)
fastboot flashing unlock and unlock_critical gives this error:
FAILED (remote: Unrecognized command flashing unlock_critical)
Any thoughts or ideas?
Click to expand...
Click to collapse
when yourein fastboot d, in adb type fastboot reboot bootloader
sketchscarz said:
when yourein fastboot d, in adb type fastboot reboot bootloader
Click to expand...
Click to collapse
hmm this justs boots the phone back into the android os
then select reboot to bootloader when in fastbootd
or you can hold the volume up while plugging into your computer until you get fastboot mode at the bottom of the screen, you gotta select the dsu at least once to be able to enable orange state on tmobile boot screen
let it sit there forlike 20 minutes itll say android annd ot boot for a long time.... i let it sit there for about 15-20 minutes
im trying to figure out how to make a twrp for this device ow that the bootloader is unlocked
Related
I just sold my phone on eBay. So I followed the instructions at: http://forum.xda-developers.com/showthread.php?t=2006946 to Unroot, relock bootloader, & get back to stock firmware.
Everything seems to be working fine expect for the fact I can't get into Stock Recovery or fastboot screen. When I try to get into stock recovery/fastboot screen by pressing the power & Volume up buttons, the phone just starts up as normal instead.
How do I fix this?
satam55 said:
I just sold my phone on eBay. So I followed the instructions at: http://forum.xda-developers.com/showthread.php?t=2006946 to Unroot, relock bootloader, & get back to stock firmware.
Everything seems to be working fine expect for the fact I can't get into Stock Recovery or fastboot screen. When I try to get into stock recovery/fastboot screen by pressing the power & Volume up buttons, the phone just starts up as normal instead.
How do I fix this?
Click to expand...
Click to collapse
Try this:
1) Turn on Developer Features (if you rooted it you know how).
2) download Android SDK (adb and fastboot) again if you rooted you phone I am assuming you know how to use those.
3) type
Code:
adb reboot bootloader
or
Code:
adb reboot recovery
it should reboot into recovery or bootloader if it doesn't. What method did you use for relocking your bootloader ? If you did it manulay via terminal (or cmd) (the laborious/error prone/manual method for re-locking the phone and installing the stock recovery/bootloader/kernel) that might cause this. Try reseting it via LGNPST. you can use the IRC if you need any help : #lg-optimus-g
alexthelionheart99 said:
Try this:
1) Turn on Developer Features (if you rooted it you know how).
2) download Android SDK (adb and fastboot) again if you rooted you phone I am assuming you know how to use those.
3) type
Code:
adb reboot bootloader
or
Code:
adb reboot recovery
it should reboot into recovery or bootloader if it doesn't. What method did you use for relocking your bootloader ? If you did it manulay via terminal (or cmd) (the laborious/error prone/manual method for re-locking the phone and installing the stock recovery/bootloader/kernel) that might cause this. Try reseting it via LGNPST. you can use the IRC if you need any help : #lg-optimus-g
Click to expand...
Click to collapse
I've been meaning to update the OP.
I downloaded "Minimal ADB and Fastboot" tool from: http://forum.xda-developers.com/showthread.php?t=2317790, instead of Android SDK.
When I put in the command "adb reboot-bootloader", the phone just starts up as normal instead. When I put in the command "adb reboot recovery", I get the icon of an Android robot laying down with a red triangle having an exclamation mark.
I used the AutoLGNPST instructions to get get back to stock.
I've seen y'all mention to go to IRC channel if folks need help in several threads. But no one ever mentions a link or instructions how to get to the IRC channel.
What should I do next?
satam55 said:
I've been meaning to update the OP.
I downloaded "Minimal ADB and Fastboot" tool from: http://forum.xda-developers.com/showthread.php?t=2317790
When I put in the command "adb reboot-bootloader", the phone just starts up as normal instead. When I put in the command "adb reboot recovery", I get the icon of an Android robot laying down with a red triangle having an exclamation mark.
I used the AutoLGNPST instructions to get get back to stock.
I've seen y'all mention to go to IRC channel if folks need help in several threads. But no one ever mentions a link or instructions how to get to the IRC channel.
What should I do next?
Click to expand...
Click to collapse
did you type adb reboot-bootloader ?
it's suppose to be
Code:
adb reboot bootloader
(with a space between reboot and bootloader)
and the android with a triangle is the stock recovery I think you need the press either the power of the vol button to get a menu like in CWR.
To join the IRC channel you download an IRC Client add Freenode as a server and then type /join #lg-optimus-g
If you don't know how to do any of the above remember Google is your Friend
alexthelionheart99 said:
did you type adb reboot-bootloader ?
it's suppose to be
Code:
adb reboot bootloader
(with a space between reboot and bootloader)
and the android with a triangle is the stock recovery I think you need the press either the power of the vol button to get a menu like in CWR.
To join the IRC channel you download an IRC Client add Freenode as a server and then type /join #lg-optimus-g
If you don't know how to do any of the above remember Google is your Friend
Click to expand...
Click to collapse
I typed in
Code:
adb reboot bootloader
. The dash is just typo.
This is the icon I get when I type
Code:
adb reboot recovery
:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
satam55 said:
I typed in
Code:
adb reboot bootloader
. The dash is just typo.
Click to expand...
Click to collapse
Try
Code:
adb reboot fastboot
For the recovery press vol up when you get to that icon, you will get something that looks like CWR
alexthelionheart99 said:
Try
Code:
adb reboot fastboot
For the recovery press vol up when you get to that icon, you will get something that looks like CWR
Click to expand...
Click to collapse
"adb reboot fastboot" gets the same result as "adb reboot booloader", the phone starts up as normal instead.
Pressing (& holding) the Volume Up button with the dead android icon does nothing.
satam55 said:
Pressing (& holding) the Volume Up button with the dead android icon does nothing.
Click to expand...
Click to collapse
Have you tried Vol-down ?
For the fastboot retry running
Code:
adb reboot bootloader
MAKE SURE THERE ARE NO TYPOES IN THE WORD BOOTLOADER
I just tried it on my LGOG Worked like a charm.
alexthelionheart99 said:
Have you tried Vol-down ?
For the fastboot retry running
Code:
adb reboot bootloader
MAKE SURE THERE ARE NO TYPOES IN THE WORD BOOTLOADER
I just tried it on my LGOG Worked like a charm.
Click to expand...
Click to collapse
Vol-down does nothing either.
The phones still boot up into Stock Firmware as normal when putting in the "adb reboot bootloader" command.
satam55 said:
Vol-down does nothing either.
The phones still boot up into Stock Firmware as normal when putting in the "adb reboot bootloader" command.
Click to expand...
Click to collapse
You can try downloading the full sdk but at this point and time I am running out of ideas. my suggestion would be re root and unlock bootloader and then try relocking the bootloader again (using the same method) have you asked the guys over at the IRC ?
alexthelionheart99 said:
You can try downloading the full sdk but at this point and time I am running out of ideas. my suggestion would be re root and unlock bootloader and then try relocking the bootloader again (using the same method) have you asked the guys over at the IRC ?
Click to expand...
Click to collapse
How do you get a response on IRC?
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
64875585 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.490s
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance for your help!
dimxr said:
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
Thanks in advance for your help!
Click to expand...
Click to collapse
I had same problem once all I could do was reboot fastboot but since the bootloader was locked but luckily I found this thread https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/ on oneplus forums this really helped hope this will help you
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Are you ready to start? Type y[yes] or n[no]:y
Device mode detected: Fastboot Mode
Device Serial Number: 64875585
Checking bootloader state..
Device bootloader state is: Locked
Do you want to unlock the bootloader? Type y[yes] or n[no]:y
When prompted, Press the Volume Up/Down button to select Yes on the screen, then
press the Power button to Unlock the Bootloader. If it is already unlocked this
will just be skipped and your device will not be wiped.
Sending oem unlock command to device..
Device bootloader is already unlocked so no data will be wiped
Rebooting back to Android..
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
dimxr said:
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Click to expand...
Click to collapse
Being in the same situation right now. Did you manage to come out of it?
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Kéno40 said:
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Click to expand...
Click to collapse
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
MrEasy666 said:
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
Click to expand...
Click to collapse
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Kéno40 said:
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Click to expand...
Click to collapse
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
MrEasy666 said:
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
Click to expand...
Click to collapse
Lucky you. There was no way for me to get to recovery. Something was wrong there.
The only thing that really worked in the end was the Mega Unbrick Guide. I've got my phone back on track and working.
Glad you managed.
Hello, I'm trying to unlock the bootloader of my cell phone which is lg k9 tv to be able to root but I can't do it at all, I've tried the tutorials of the entire internet, the adb drivers don't appear to be updated in the windows device manager 10, even with the help of a friend who has more knowledge on cell phones he was unable to unlock, and I also can't get into fastboot mode which is essential from what I saw, I've seen a tutorial on how to get into fastboot but my lg k9 doesn't no way in fastboot, if you can help me thank you.
diego998kk said:
Hello, I'm trying to unlock the bootloader of my cell phone which is lg k9 tv to be able to root but I can't do it at all, I've tried the tutorials of the entire internet, the adb drivers don't appear to be updated in the windows device manager 10, even with the help of a friend who has more knowledge on cell phones he was unable to unlock, and I also can't get into fastboot mode which is essential from what I saw, I've seen a tutorial on how to get into fastboot but my lg k9 doesn't no way in fastboot, if you can help me thank you.
Click to expand...
Click to collapse
LG's USB driver doesn't get updated by Windows: it's on you to ensure to have driver's latest version installed.
Visit LG's website.
To root device's Android 1st of all these 2 options must be enabled/allowed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and FASTBOOT binary must be installed.
After device got rebooted
Go to the folder where ADB and Fastboot binaries are installed.
Right-click in an empty location inside the folder while holding the Shift button.
Then select ‘Open command window here’ or ‘Open PowerShell window here.’
Enter the command fastboot flashing unlock and hit Enter-button
You will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode.
Enter the command fastboot reboot and it will boot into PC.
jwoegerbauer said:
LG's USB driver doesn't get updated by Windows: it's on you to ensure to have driver's latest version installed.
Visit LG's website.
To root device's Android 1st of all these 2 options must be enabled/allowed
and FASTBOOT binary must be installed.
After device got rebooted
Go to the folder where ADB and Fastboot binaries are installed.
Right-click in an empty location inside the folder while holding the Shift button.
Then select ‘Open command window here’ or ‘Open PowerShell window here.’
Enter the command fastboot flashing unlock and hit Enter-button
You will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode.
Enter the command fastboot reboot and it will boot into PC.
Click to expand...
Click to collapse
a question, can it be the universal drivers or does it have to be the device itself?
jwoegerbauer said:
LG's USB driver doesn't get updated by Windows: it's on you to ensure to have driver's latest version installed.
Visit LG's website.
To root device's Android 1st of all these 2 options must be enabled/allowed
and FASTBOOT binary must be installed.
After device got rebooted
Go to the folder where ADB and Fastboot binaries are installed.
Right-click in an empty location inside the folder while holding the Shift button.
Then select ‘Open command window here’ or ‘Open PowerShell window here.’
Enter the command fastboot flashing unlock and hit Enter-button
You will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode.
Enter the command fastboot reboot and it will boot into PC.
Click to expand...
Click to collapse
When I try to put it on bootloader mode it fails.
Follow the steeps I've done:
1. Turn On USB Debug mode and OEM Unlock at Developer menu.
2. Plug in and do adb command "adb devices"
3. When appear the list with my phone I do the command "adb reboot bootloader"
But when it restarts it goes to system and not to bootloader screen.
Ive tried also "adb reboot fastboot" and "adb reboot download" but the same happens.
@diego998kk
Press and hold the volume down and power buttons until the LG logo appears, then release them. If this doesn’t work, you may have to release the power and volume down buttons for a second when the LG logo appears, then re-press them until the bootloader shows up what may take some seconds.
jwoegerbauer said:
@diego998kk
Press and hold the volume down and power buttons until the LG logo appears, then release them. If this doesn’t work, you may have to release the power and volume down buttons for a second when the LG logo appears, then re-press them until the bootloader shows up what may take some seconds.
Click to expand...
Click to collapse
None worked
diego998kk said:
When I try to put it on bootloader mode it fails.
Follow the steeps I've done:
1. Turn On USB Debug mode and OEM Unlock at Developer menu.
2. Plug in and do adb command "adb devices"
3. When appear the list with my phone I do the command "adb reboot bootloader"
But when it restarts it goes to system and not to bootloader screen.
Ive tried also "adb reboot fastboot" and "adb reboot download" but the same happens.
Click to expand...
Click to collapse
Me too
Someone did unlock LG K9 TV bootloader
Hello everyone,
I've been googling this for the past couple days it's been driving me crazy. Stock 7 (I think), should have been unlocked but is showing locked.
1. My friend gave me the Nexus 9 which turned off one day, then wouldn't turn on again.
2. I plugged it in, and it turned on fine. Assumed bad usb port, he said keep it. I enabled developer options, then did "OEM [bootloader?] unlock" and "USB Debugging" toggles on (from memory, may not be right phrasing)
3. While trying to back up his data on it by ADB Pull, it would randomly stop. Using it, it would reboot unexpectedly.
4. So I went to Software Update.. bad idea in retrospect probably it rebooted during or something? It was fully charged and on AC power but I wasn't watching it.
5. I come back and it keeps bootlooping. Went into recovery, says "Device Locked" - Tried clearing cache, no difference. Tried sending bootloader unlock command with fastboot, says I have to delete all data to unlock.
The only lead that I have is that it might be possible to image TWRP to recovery, then boot into it so that I can get files off it (With OTG Flash drive or USB?) - I wanted to ask for help here first.
I did my best to search for this prior, but I've been out of the ROM game since 2012 cyanogenmod days.. Hope that it's possible to save my friend's data, and then also to flash a new ROM which will solve the reboot issue.. Thanks!
Boot to recover, then when you get the Android mascot with the belly open, press ( I think vol up plus power) to get to a functional recovery with ADB support.
gk1984 said:
Boot to recover, then when you get the Android mascot with the belly open, press ( I think vol up plus power) to get to a functional recovery with ADB support.
Click to expand...
Click to collapse
Thanks GK,
After going into recovery mode, there's the android mascot with the belly open as you describe. Then, I do (VolUp+Pwr) and it produces this screen below, which I'm guessing people call "fastboot". When I'm there, my Win10 PC makes the "USB item attached" noise, and I can use fastboot commands, but adb devices won't show anything. Do you have any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thought I could use the fastboot access I have to flash twrp, but I get the following error. I switched the "OEM Unlock" toggle, but i'm guessing that doesn't mean anything until I unlock the bootloader in recovery (which necessitates deleting all the files). I followed the directions on the twrp website which claim that root isn't needed, but I guess unlock is.
Code:
PS C:\Users\User Profile\Downloads\platform-tools_r30.0.1-windows\platform-tools> .\fastboot flash recovery twrp.img
Sending 'recovery' (13254 KB) OKAY [ 0.838s]
Writing 'recovery' (bootloader) Device State : Locked
FAILED (remote: 'Can not flash any images while device state is locked!')
fastboot: error: Command failed
Thanks again,
luciant
luciant said:
Thanks GK,
After going into recovery mode, there's the android mascot with the belly open as you describe. Then, I do (VolUp+Pwr) and it produces this screen below, which I'm guessing people call "fastboot". When I'm there, my Win10 PC makes the "USB item attached" noise, and I can use fastboot commands, but adb devices won't show anything. Do you have any ideas?
I thought I could use the fastboot access I have to flash twrp, but I get the following error. I switched the "OEM Unlock" toggle, but i'm guessing that doesn't mean anything until I unlock the bootloader in recovery (which necessitates deleting all the files). I followed the directions on the twrp website which claim that root isn't needed, but I guess unlock is.
Thanks again,
luciant
Click to expand...
Click to collapse
You need to be in recovery for adb to work. The Android with belly open is recovery but you need to unlock it with a button combo. Fastboot won't work unless you unlocked the bootloader.
I may have the steps a little off for getting to recovery but I'm sure searching how to boot to recover for the Nexus 9 will find you the right steps. It's been a long time since I've used the stock recovery on this tablet.
For future bootloopers: Well in the end, I wasn't able to figure out how to pull files using the stock HTC Nexus 9 recovery. Since it was locked, I wasn't able to install or execute TWRP .img , and unlocking it meant losing the files. It was weirdly looping even in Recovery & Fastboot. I tried every mode, and different drivers in the device manager, but ADB couldn't connect. Maybe it's not meant to for security purposes.
If you're bootlooping even in recovery, try the following:
I gave up on trying to recover the data, and decided to just unlock the bootloader. booted to Fastboot (Pwr+Vol Down on start up, select Recovery, Pwr+Vol Up, should say "Fastboot") Then I used fastboot oem unlock, which unlocked the bootloader and Deleted ALL DATA. Then, I could flash TWRP, using fastboot flash recovery twrp.img. Once I flashed TWRP, I booted to twrp recovery using Pwr+Vol Up at boot, wiped all partitions. Then I went to TWRP Advanced -> ADB sideload. Issued adb sideload ota.zip, and this gave me a clean stock install.
Thanks gk for your advice.
Hey!
I am having difficulties unlocking the bootloader of my Redmi Note 5. I have already rooted a meizu phone and a lenovo tablet before and had no problems. However, with this one, I am able to enter the bootloader using the following command.
Code:
adb reboot bootloader
However, when I do this:
Code:
fastboot oem unlock
It outputs the following:
Code:
FAILED (remote: 'Token Verify Failed, Reboot the device')
fastboot: error: Command failed
The command
Code:
fastboot oem unlock-go
outputs the same results and rebooting my phone doesn't resolve the issue.
Additionnaly, using the Miui Unlock App doesn't work because it doesn't recognise my phone when in bootloader.
Please help!
Thanks in advance.
PS: I am using a Win10 64bits PC
Edit: I tried an older version of Miui Unlock and it detected my device, but couldn't unlock it. It stopped at 99% and output "couldn't unlock"
IMHO it's always recommended to check for boot-loader can get unlocked
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
0
Seppppx said:
You are supposed to use the mi unlock tool. Not these simple fastboot commands (xiaomi wants to make unlocking complicated)
Here is a steb-by-step guide
1. Make a Mi account
2. Apply for an unlock here https://en.miui.com/unlock/
3. Download Mi unlock by clicking on the unlock now and then download Mi Unlock.
4. Download the Mi Unlock app to PC, and sign in with your Mi Account;
5. Shut down your phone manually, and hold Volume down key and Power button to enter Fastboot.
6. Connect your phone to PC using USB cable and click "Unlock".
You will probably have to wait some time (3 days, maybe a week or even a month).
it's been some time since I have unlock my Xiaomi phone so these steps might be wrong. If yes point that out please.
Click to expand...
Click to collapse
As I said in my post, I have tried using Mi Unlock. I have done all your steps up to the 6th because the app doesn't allow me to click unlock. I am guessing that it doesn't detect my phone in fastboot mode. About the time I have to wait, is it the time between when I apply for an unlock and when I can unlock my phone? This would explain why I can't unlock it. However I saw on another thread that Xiaomi removed the need to apply and wait to be able to unlock a phone. I don't really know how to feel about this one...
0
Seppppx said:
Do you have fastboot/adb drivers installed?
Click to expand...
Click to collapse
I'm pretty sure I do, because I have already rooted devices before. How do I check?
0
Seppppx said:
To check your drivers (and install) do this.
1. Plug your phone to the Pc.
2. Boot to fastboot (use googles platform tools, download below)
3. Open CMD as an administrator.
4. Navigate to the folder there you have platform tools in.
5. Type "fastboot devices" if you see no output you either have the wrong drivers installed or not installed
(Download the Google USB driver linked down)
6. To install drivers you open your Device Manager in windows.
7. Look for something like "Android Device" there. If it also has a warning sign that means that there are no drivers.
8. Right click on "Android Device"
9. Click on "Update driver"
10. Click on "Browse my computer for driver software"
11. Click on "Let me pick from a list of available drivers on my computer"
12. Click on "Have Disk..."
12. Browser for a driver under "Copy manufacturer's files from:"
13. Find the driver folder in the folder you saved it to and open it.
14. Double click on "android_winusb.inf
15. Click on "OK"
16. Click on "Next"
Done, you have installed a driver.
Download the Google fastboot/adb here https://developer.android.com/studio/releases/platform-tools
Direct download https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Download the google fastboot/adb driver here https://developer.android.com/studio/run/win-usb
Direct download https://dl.google.com/android/repository/usb_driver_r12-windows.zip
Click to expand...
Click to collapse
Well, I tried and went up to step 5 and there was no output. So I continued the steps, on step 7 I saw that my Adroid Device Driver had no warning sign, meaning that I have the wrong drivers. I continued on with your steps. After step 11, the control pannel shows 2 drivers named as "Android Bootloader Interface", however before step 15, the control pannel shows 3 different drivers named as "Android ADB Interface", "Android Bootloader Interface" and "Android Composite ADB Interface". The second one is selected by default, so I click ok and it installs. However, the "adb devices" and "fastboot devices" commands still show nothing in the command prompt. Is there something I am doing wrong?
0
Seppppx said:
You should reboot your phone after installing these drivers. I had the same problem, that fixed it.
Click to expand...
Click to collapse
Still nothing... There is no output to "adb devices" even after I install the driver and reboot my phone.
0
DemonBlu3000 said:
Still nothing... There is no output to "adb devices" even after I install the driver and reboot my phone.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Xiaomi USB Drivers are essential while connecting your smartphone in Fastboot Mode & Emergency Download Mode [EDL].
Seppppx said:
Do you get an output to "fastboot devices" that's the thing that matters when unlocking. I managed to my redmi note 4 to unlock without adb.
You also can get adb in the classic system where you boot. That works for me.
Click to expand...
Click to collapse
No, "fastboot devices" has no output on my computer, but it has one on another computer for some reason. On mine it doesn't and I need it to on mine.
0
Okay guys I figured it out. I was missing a step. I indeed had to use the Mi Unlock tool, but before doing so I had to enable an option beneath the "OEM unlock option", I don't remember how it was called but everything's fine now!