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?
Related
{
"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"
}
DISCLAIMER
Modifying or replacing your device's software may void your device's warranty, lead to data loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with the CyanogenMod project is responsible for your actions. Good luck.
NOTE
- If you are not using a Verizon Wireless branded device on Verizon Wireless, you must follow the steps below to reboot into bootloader and then enter fastboot oem config carrier vzw to ensure proper data operation.
- Unlocking the bootloader on a Nexus device will automatically wipe all device data.
- Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.
INSTALLATION
UNLOCKING THE BOOTLOADER
- Make sure your computer has working fastboot and adb.
- Enable USB debugging on the device.
- Connect the device to the computer through USB.
- From a terminal on a computer, type the following to boot the device into fastboot mode:
$ adb reboot bootloader
Click to expand...
Click to collapse
- Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
- If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation on cyanogenmod website - If you see "no permissions fastboot", try running fastboot as root.
- From the same terminal, type the following command to unlock the bootloader:
$ fastboot oem unlock
Click to expand...
Click to collapse
- A disclaimer will display on the device that must be accepted. Use the volume keys to cycle through the options. Pressing the power button should confirm your selection.
- If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked. You can confirm this is the case if you see an unlocked icon at the bottom of the Google boot screen during reboots.
- Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
INSTALLING RECOVERY
- Make sure your computer has working fastboot and adb.
Download recovery -- you can directly download a recovery image using the link below, or visit clockworkmod.com/rommanager to check for the latest version of ClockworkMod recovery for your device (if your device can be found there).
Recovery: openrecovery-twrp-2.8.4.0-shamu.img
md5: fc904a1d1d49d1797ad62bb1cb4e6775
Click to expand...
Click to collapse
- Connect the Nexus 6 to the computer via USB.
- Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
- Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
Click to expand...
Click to collapse
or by using the hardware key combination for your device while it is powered off.
- Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
Click to expand...
Click to collapse
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See documentation on cyanogenmod website
If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
- Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
Click to expand...
Click to collapse
where the latter part is the filename of the recovery image.
- Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold down the Volume Down button while booting, and use the menu to select Recovery.
INSTALLING CM12
- Make sure your computer has working adb.
- Copy zip to the root of /sdcard:
- If you are not already in recovery, boot to recovery mode now.
- Hold down the Volume Down button while booting, and use the menu to select Recovery.
In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
Optional (Recommended): Select the Backup button.
Select Wipe and then Factory Reset. If you're getting an error formatting /data, try format /data and /data/media from the Mounts and Storage Menu.
Select Install.
Click to expand...
Click to collapse
- Navigate to /sdcard and select the CyanogenMod .zip package.
Follow the on-screen notices to install the package.
Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod the first and then install any subsequent packages on top of it).
Click to expand...
Click to collapse
- Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod. Note that the first boot after installation may take 5 - 10 minutes
-------------------------------
Comment me if any problems
Press thanks ☻
Creative
XDA
DOWNLOADS
ROM CM12 - http://get.cm/get/nur
GAPPS - http://tinyurl.com/ounl8cw
Hi guys,
I was following tutorial in order to install stock international FW on my Amazfit 2. However something has failed at step 11, when I was trying to "adb shell reboot bootloader". I got
- exec '/system/bin/sh' failed: Not a directory (20) -
using port=5555
Click to expand...
Click to collapse
Watches are now stuck at amazfit logo and I cannot seem to get to fastboot. Does anybody knows, how to get to fastboot via some key combo on Amazfit 2? I could find just Amazfit solution (this "4 seconds" hint), however it does not seem to work for Amazfit 2...
Any help appreciated, thanks!
Try just this instead:
Code:
adb reboot bootloader
or
Code:
adb reboot-bootloader
Hi thanks for the help,
However I got this idea as well before (based on my general android devices experience) however what it does is that it just reboots normally leading to splash screen stuck. It does not matter whether I issue adb reboot bootloader, adb reboot-bootloader or adb reboot lalala. I think it just grasps adb reboot part only and does normal reboot. However, thank you!.
lfom said:
Try just this instead:
Code:
adb reboot bootloader
or
Code:
adb reboot-bootloader
Click to expand...
Click to collapse
Well, if your watch gets into a bootloop after you use reboot, then something else is wrong... Normal reboot works, just "reboot bootloader" fails?
No, unfortunatelly both normal reboot and reboot bootloader lead to bootloop with Amazfit logo :/
Fastboot finds your device? Can you wipe both data and cache?
{
"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"
}
Only adb devices sees it. But as I cannot get to bootloader, fastboot does not see it, so I cannot do anything...
Have you ever tried to flash another ROM? It seems that system is broken, that's why you get bootloops and cannot get to bootloader. You have to find a way to do it manually, most devices has some combination at start up to activate recovery and/or fastboot...
Make sure fastboot drivers are installed:
https://forum.xda-developers.com/showthread.php?t=2588979
Then check this for manually activate fastboot:
https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
Hi Ifom, thanks again for your energy and willingness to help me.
I would like to flash another ROM, however right for that I would need to get to bootloader. Guide in second link does not work, probably it is intended just for Amazfit 1. This is actually my original question, whether there is something like this for Amazfit 2, because I cannot find it anywhere.
lfom said:
Have you ever tried to flash another ROM? It seems that system is broken, that's why you get bootloops and cannot get to bootloader. You have to find a way to do it manually, most devices has some combination at start up to activate recovery and/or fastboot...
Make sure fastboot drivers are installed:
https://forum.xda-developers.com/showthread.php?t=2588979
Then check this for manually activate fastboot:
https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
Click to expand...
Click to collapse
Poborak said:
Hi Ifom, thanks again for your energy and willingness to help me.
I would like to flash another ROM, however right for that I would need to get to bootloader. Guide in second link does not work, probably it is intended just for Amazfit 1. This is actually my original question, whether there is something like this for Amazfit 2, because I cannot find it anywhere.
Click to expand...
Click to collapse
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
You were right! I can confirm now that this method work also for Amazfit 2, however it is kind of tricky. Took me 20 mins to do it right.
Thank you both for helping me out, I appreciate your friendliness very much!
Quinny899 said:
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
Click to expand...
Click to collapse
Quinny899 said:
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
Click to expand...
Click to collapse
Take the "Huami_AMAZFIT_Tool_1.0.1.1" and click on "reboot bootloader". This works!
schroepfer said:
Take the "Huami_AMAZFIT_Tool_1.0.1.1" and click on "reboot bootloader". This works!
Click to expand...
Click to collapse
That requires ADB, which requires the watch to at least get to that stage, which isn't the case if you break the kernel
I cannot enter Fastboot Mode.
Quinny899 said:
That requires ADB, which requires the watch to at least get to that stage, which isn't the case if you break the kernel
Click to expand...
Click to collapse
I have an Amazfit and I can't get into Fastboot Mode at all. I have tried all of the alternatives described here many, many times. One question: can Windows / USB port influence not being able to enter Fastboot? Should I try on a Windows 7 for example?
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.
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