So, my HTC U Ultra got stuck in bootloop just 3 days after warranty ended(tough luck level : 100).
My phone runs on everything stock and no root.
I press all the buttons when powered off and it goes into bootloader mode. It displays options to boot into recovery mode, boot into download mode and power down, all of which(except power down) gets device into bootloop again.
THE PRIORITY OF GOALS IS : DATA RECOVERY > PHONE BOOTING AND WORKING PROPERLY AGAIN
I did a little research and figured out some sort of procedure by putting bits and pieces together :
1. Download ADB/Fastboot toolkit || universal driver from koush github // I have HTC Sync manager installed as well || twrp custom recovery image for htc u ultra || new ruu from htc support for rom update.
2. Now I put my phone into fastboot mode (since it doesn't show up on adb devices), connect to pc using usb.
3. I type in cmd : "fastboot devices" --> My device shows up there --> Again in cmd : "fastboot boot recovery mytwrp.img" --> the twrp boots into my phone
I was able to put this many steps together and after the last step, i have an abstract idea of what to do :
Enable USB Debugging using twrp recovery --> Use ADB Pull Command to get my all my data from phone to pc --> Use adb wipe the old Firmware (Not sure which command) --> Use adb again to flash new RUU (again not sure how, I've got an .exe file as RUU || should I get it in zip or img or any other format ? || Please help on this too) --> Finally Boot and hopefully everything turns out smooth and secure.
CAN YOU EXPERTS HELP ME TO PUT TOGETHER REMAINING STEPS (AND MODIFY ERRORS, IF ANY, OF EXISTING STEPS ) OF THIS PROCEDURE...???
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
jwoegerbauer said:
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
Click to expand...
Click to collapse
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly ?
noobie12112 said:
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly in my case?
Click to expand...
Click to collapse
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
jwoegerbauer said:
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
Click to expand...
Click to collapse
@jwoegerbauer Thank you for the insight. In my case, the phone wasn't physically damaged, the bootloop occurred out of the blue one day. Now, what I presumed I should do, is to flash a custom recovery (twrp) using "fastboot boot recovery.img" command, and using twrp (Can I enable USB Debugging using twrp ?) to access files, backup and then flash a new RUU. But I found that I need to unlock bootloader, is there any way to use command "fastboot oem unlock" and not lose data, or any other method to unlock bootloader, where i don't lose data?
Thank you for your help.
Unlocking phone's bootloader always causes complete loss of data.
Forget the TWRP thing, it's not helpful at all in your case.
Try to flash phone's Stock ROM by means of ADB - what requires ADB got installed on Windows computer and USB debugging got ( manually !!! ) enabled on phone.
Related
Introduction
The purpose of this guide is to provide you with step-by-step instructions on how to unlock the bootloader on your Nvidia Shield.
Why Would I want to Unlock my Bootloader?
Unlocking your bootloader allows you to modify all aspects of your device to suite your needs which includes but is not limited to, installing custom Recovery images such as Clockworkmod Recovery or Team Win Recovery Project, installing custom ROM's, custom Kernels, as well as other MOD's and patches.
Will Unlocking my Bootloader Void my Warranty?
Warning: Unlocking your Nvidia Shield's bootloader will void the warranty, please note that even if you re-lock the bootloader the bootloader still show a flag that the device is voided for warranty.
This warning being given please also see this post by JordanKeyes regarding warranty information as it relates to hardware issues or hardware failures.
Unlocking your Bootloader
1. Backup everything on your device that you don't want to loose such any apps (And there respective data), pictures, videos, music, etc. as unlocking your devices bootloader will erase all data on the device. You can fully backup your devices contents without root using ADB's backup command or by using the Holo Backup Tool.
2. Download and install the ADB and Fastboot drivers for your Shield, the drivers can be downloaded here. You can also follow along with wwjoshdew's excellent video tutorial on how to properly install the ADB and Fastboot drivers for your Shield on Windows.
3. Make sure you have ADB and Fastboot setup and installed on your computer. If you haven't already setup and installed ADB and Fastboot a simple ADB and Fastboot installer can be downloaded from here.
4. Fully power off your Shield by long pressing on the Power button until the power menu appears, then select the "Power off" option.
5. Boot your Shield into Fastboot mode using one of the following ways:
5. A. Power on your Shield while simultaneously holding the Power button + Back button + Home button. Release the buttons once the Fastboot bootloader screen appears.
5. B. Run the following ADB command from a command prompt window (USB cable must already be connected from your Shield to your Computer):
Code:
adb reboot bootloader
6.Now that you are at the Fastboot bootloader screen, connect your Shield to your computer using your USB cable. Make sure that your USB cable is plugged into a USB 2.0 port directly connected to your motherboard as sometimes USB 3.0 ports can cause problems and front panel USB connections can be unreliable.
7. Open up a command prompt window (cmd) in the directory where installed ADB and Fastboot to. For example if I installed ADB and Fastboot to a folder on my Desktop which is on my D: drive I would open a command window in "D:\Desktop\Fastboot_ADB".
8. From the command prompt windows enter the following command:
Code:
fastboot devices
If you device is detected and it shows your devices serial number you are ready to move on to the next step. If no device is shown make sure you have the correctly installed the ADB and Fastboot drivers from step number 2.
9. Now that your device is detected by Fastboot the following command is used to unlock your bootloader:
Code:
fastboot oem unlock
10. You will now be presented with the bootloader unlock menu. After reading the disclaimer, use the Back button and the Home button to navigate to the "Unlock" option. Once the "Unlock" option has been highlighted use the Shield button to confirm your selection of unlocking your bootloader. It's important to remember that unlocking the bootloader will wipe all your data from the device, and that a flag showing your warranty is void will appear at the bootloader screen.
11. Once your bootloader has finished being unlocked, you will be taken back to the fastboot bootloader screen. From here you can power off your Shield.
Re-locking your Bootloader
To re-lock your bootloader you can following steps 4-8 of the procedure listed above and when you come to step 9 run the following command instead of "fastboot oem unlock":
Code:
fastboot oem lock
The above command will re-lock your Shield's bootloader. Note: As previously mentioned re-locking your Shield's bootloader will not restore your warranty or remove the warranty void flag on your device's bootloader.
Conclusion
Now that you have successfully unlocked the bootloader on your Nvidia Shield you are free to flash custom Recoveries, ROM's, Kernel's, MOD's etc. enjoy :good:.
If you are stuck with the bootloader unlocking procedure I would recommend checking out this great video tutorial by wwjoshdew.
I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Edit: followed the instructions in the following video and all is dandy now. http://www.youtube.com/watch?v=XSisjVwcPbE&hd=1
themichael said:
I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Click to expand...
Click to collapse
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.
fastboot error
chevyowner said:
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.
Click to expand...
Click to collapse
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.
gogul1 said:
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.
Click to expand...
Click to collapse
Nvidia just released a new set of USB drivers in their Tegra for Android Development Pack which you can download from here. I would recommend installing the development pack and the drivers it includes.
ok
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148
gogul1 said:
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148
Click to expand...
Click to collapse
From that pic you posted the mount command failed because you were not root.
chevyowner said:
From that pic you posted the mount command failed because you were not root.
Click to expand...
Click to collapse
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.
shimp208 said:
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.
Click to expand...
Click to collapse
Huh??????????
EDIT
Were you trying to answer this post
chevyowner said:
Huh??????????
EDIT
Were you trying to answer this post
Click to expand...
Click to collapse
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!
shimp208 said:
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!
Click to expand...
Click to collapse
No problem.
I had to change to oil in my car in a parking lot earlier because it was cheaper to change it then it would have been add 3-4 quarts and change it when I got home. My car need 5 quarts of oil. I was not in a a good mood then.
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
thx. works nice.
wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: [
How To Root the Nvidia Shield: []
Click to expand...
Click to collapse
Sweet thanks
wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Click to expand...
Click to collapse
I tried another proggie to root and got jammed up.. following the videos josh did had me rooted in minutes. Great job and thanks!
why?
Code:
C:\Users\Thomas>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 0.582s
I tried it with the Shield RAM tool, but won't work either..
so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.
mr.dude5660 said:
so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.
Click to expand...
Click to collapse
Where did you find the towelroot apk? Been searching for over a month with no success.
Sent from my VS980 4G using Tapatalk
BTW, bootloader mode on the tablet:
- Hold "Volume Down" -> Press "Power" and continue to hold "Volume Down" until device boots into bootloader mode.
There is no home or back button to press while the device is off.
Sorry for bump this thread, but i have to.
I want to unlock my bootloader to revert back into KK and then try to do a clean installation of LP. Reading this guide and watching the videos, and also looking into the img downloaded from nvidia, it says i have to install the fastboot drivers. The problem is that i have already installed fastboot and adb drivers since i have some other devices as a Xperia and stuff. For me, there is no Yellow sign as shown in the video, my device is recognized as Portable Device and it already says "Shield Tablet" MTP.
I've tried going into bootloader to see if it prompts any new devices but i got nothing. adb devices show my device, but i'm not sure if i need more.
My Remix Ultratablet current running 2.0.305 keep random restart everyday.
So I wish to downgrade to OS 1.5
I ask for help form office Jide support , they told me I need to
Q1) Problem # stuck on step #1 already , When I ask where is the Remix Ultratablet driver when I install adb and fastboot ? Offical jide support told me I don't need a driver? How so ?
I can't get the tablet connect ??
Note: 1, I connect the tablet with USB to PC
Note: 2, I turn the USB debugging option on Tablet already.
Note: 3, I Test it on pc adb folder by trying "fastboot devices" only get "Waiting for Device" error
Q2) I also try other method (Power key + Volume up) on tablet which show
"Continue
Fastboot Protocol
Recovery Kernel
Reboot
Poweroff
Forced Recovery"
But when i press"Fastboot Protocol" , doesn't do anything ?
For your references:
Steps of instruction I receive from Jide offical support so far....
1) have ADB and Fastboot running, I download the Minimal ADB and Fastboot[/URL])
2)Download Remix OS 1.5 ROM[/URL]
3) Unzip the downloaded zip file ( SK1WG.zip ) and go to the folder
4. Connect the Remix 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.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination for your device while it is powered off.
7. 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 "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
-If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
8. Clean the existing data by entering the following command: fastboot -w
9. Flash images onto your device by entering the following three commands:
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
-fastboot reboot
did u download the correct fastboot? you need Android 5.0 to get Remix 1.5
AmoraRei said:
did u download the correct fastboot? you need Android 5.0 to get Remix 1.5
Click to expand...
Click to collapse
That makes no sense what so ever.
Maybe it would be better to ask what platform he is using to flash his device with, as the instructions he has copy and pasted refer to Linux (udev rules)
it makes sense to me cause you have download the correct Android SDK to work on certain Android platforms.
https://developer.android.com/studio/releases/platforms.html
To compile your application against a particular version of Android, you must use the SDK Manager to download and install the SDK Platform for that release.
AmoraRei said:
it makes sense to me cause you have download the correct Android SDK to work on certain Android platforms.
To compile your application against a particular version of Android, you must use the SDK Manager to download and install the SDK Platform for that release.
Click to expand...
Click to collapse
Thanks of the reply ,
I'm using Win7 amd the Remix Ultratablet current running 2.0.305
I can't post link , but the ADB /Fastboot verson I download is also from xda Title "[TOOL]Minimal ADB and Fastboot [10-22-16]"
I download the "Version 1.4.1 Portable Here" with
MD5 Checksum: D7B1C009C87C77AAF045FA3ED239E591
Thanks for all the help in advance
When u plugged up the tablet to the pc, what did device manager say?
my associate said try this fastboot http://forum.xda-developers.com/showthread.php?t=2588979
AmoraRei said:
When u plugged up the tablet to the pc, what did device manager say?
my associate said try this fastboot http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
not exactly,i said to try this ,to install adb drivers.
http://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089
tailslol said:
not exactly,i said to try this ,to install adb drivers.
http://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089
Click to expand...
Click to collapse
well thank u for coming here and posting
:victory:
AmoraRei said:
When u plugged up the tablet to the pc, what did device manager say?
my associate said try this fastboot http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
when the tablet plugin to WIN7 , I got pop up windoes "Autoplay"
Name REMIX SK1WG
-Sync digital media file to this device
-Open device to view files
-Import picture and Video
when I click "Open device to view files" , I get to to see tablet "Internal Storage"
Thanks
sfbay998 said:
when the tablet plugin to WIN7 , I got pop up windoes "Autoplay"
Name REMIX SK1WG
-Sync digital media file to this device
-Open device to view files
-Import picture and Video
when I click "Open device to view files" , I get to to see tablet "Internal Storage"
Thanks
Click to expand...
Click to collapse
and what happens when you plug it when the device is in fastboot mode?
tailslol said:
and what happens when you plug it when the device is in fastboot mode?
Click to expand...
Click to collapse
That's the part I'm lost : What is consider "in fastboot mode"
I go to the WIN7 Folder there is unzip the "[TOOL]Minimal ADB and Fastboot [10-22-16] Version 1.4.1 Portable" and type fastboot devices , nothing happen
then I go to the tablet : turn off, then I try other method (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Nothing Happen ??
Note: I'm a first time ADB/ Fastboot user, but not totally a newbie. thanks
sfbay998 said:
That's the part I'm lost : What is consider "in fastboot mode"
I go to the WIN7 Folder there is unzip the "[TOOL]Minimal ADB and Fastboot [10-22-16] Version 1.4.1 Portable" and type fastboot devices , nothing happen
then I go to the tablet : turn off, then I try other method (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Nothing Happen ??
Note: I'm a first time ADB/ Fastboot user, but not totally a newbie. thanks
Click to expand...
Click to collapse
you should look the picture i gave you in my first message.
tailslol said:
you should look the picture i gave you in my first message.
Click to expand...
Click to collapse
Thanks, I will try the install "15 seconds ADB Installer v1.4.3" tonight when back home.
on side question: anyone know WHEN to use the (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
The reason I ask because when I press "Fastboot Protocol" , it doesn't do anything. !!??
Also , the whole purpose for me to do the ADB/fastboot is to download back to OS 1.5, because my OS 2.0.305 keep random reboot ! So if anyone can tell me how to fix the OS 2.0.305 random reboot ? I might not have to do all this ADB/fastboot things ?
Thanks
sfbay998 said:
Thanks, I will try the install "15 seconds ADB Installer v1.4.3" tonight when back home.
on side question: anyone know WHEN to use the (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
The reason I ask because when I press "Fastboot Protocol" , it doesn't do anything. !!??
Also , the whole purpose for me to do the ADB/fastboot is to download back to OS 1.5, because my OS 2.0.305 keep random reboot ! So if anyone can tell me how to fix the OS 2.0.305 random reboot ? I might not have to do all this ADB/fastboot things ?
Thanks
Click to expand...
Click to collapse
when you turn it on,it seems you do not have the minimum knowledge required to flash a device... you should stay away from downgrading it or study adb and fastboot videos and tutorials on google and youtube before doing anything.if you do anything wrong and brick your device,the warranty will not work,any bad flash could void your device warranty.
tailslol said:
when you turn it on,it seems you do not have the minimum knowledge required to flash a device... you should stay away from downgrading it or study adb and fastboot videos and tutorials on google and youtube before doing anything.if you do anything wrong and brick your device,the warranty will not work,any bad flash could void your device warranty.
Click to expand...
Click to collapse
I have try
Connect the Remix to the computer via USB.
fastboot devices
Which show:
xxxxxxxxxxxxxx fastboot
Then I type the following commands
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
ALL successful , then when reboot , it stuck on "Remix" flashing logo forever !!
Any help ?
sfbay998 said:
I have try
Connect the Remix to the computer via USB.
fastboot devices
Which show:
xxxxxxxxxxxxxx fastboot
Then I type the following commands
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
ALL successful , then when reboot , it stuck on "Remix" flashing logo forever !!
Any help ?
Click to expand...
Click to collapse
yea you forgot to wipe your device...
return to fastboot if you can then use those commands:
fastboot -w
fastboot reboot
update:
Now when i type
fastboot devices
I got :
xxxxxxxxxxxxxxxxxxxxxxxxxxxx fastboot
When I type: adb devices
I got:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On the Tablet side:
Bootloop only
But I can still press "Vol up + Power" and see the following menu
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Any help would be appreciated !!
Thanks
sfbay998 said:
update:
Now when i type
fastboot devices
I got :
xxxxxxxxxxxxxxxxxxxxxxxxxxxx fastboot
When I type: adb devices
I got:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On the Tablet side:
Bootloop only
But I can still press "Vol up + Power" and see the following menu
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Any help would be appreciated !!
Thanks
Click to expand...
Click to collapse
go to fastboot protocol ,hook it to your pc and proceed with the command i told you,but anyway caution,i told you you could brick your device...
tailslol said:
go to fastboot protocol ,hook it to your pc and proceed with the command i told you,but anyway caution,i told you you could brick your device...
Click to expand...
Click to collapse
Will try
but just want to check When I type: adb devices , iy did not list my drvice number , does it matter since I will be using "Fastboot -W" only?
sfbay998 said:
Will try
but just want to check When I type: adb devices , iy did not list my drvice number , does it matter since I will be using "Fastboot -W" only?
Click to expand...
Click to collapse
don't forget fastboot reboot and yes it matter,if the computer does not see the device the device can't receive commands...
Orea beta is great but battery drain so much.
for 30 min of screen use it used 11%, is it normal ?
and I am looking to go back to Nougat, could any one please tell me how can I go back.
Thank you.
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Yup those are them, I just did it yesterday.
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
vjyrdy said:
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Click to expand...
Click to collapse
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
swagglepuff said:
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
Click to expand...
Click to collapse
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
tech_head said:
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
Click to expand...
Click to collapse
I have ran both unlock commands successfully and still get permission denied
swagglepuff said:
I have ran both unlock commands successfully and still get permission denied
Click to expand...
Click to collapse
And you checked the OEM unlock in developer options?
Hmmmm
tech_head said:
And you checked the OEM unlock in developer options?
Hmmmm
Click to expand...
Click to collapse
The issue has something to do with Mac and the platform tools. I was able to downgrade with no problem using a friend's Windows PC.
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
trizon2016 said:
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
Click to expand...
Click to collapse
Nothing confusing about that statement for Windows, MacOS or Linux.
A command path needs to exist so that when you type the command it can be found.
I want to install LineageOS so I closely followed the fastboot and adb instructions on the official site. During my first (failed) attempt, there were some old Google USB and ADB things on my PC, so I deleted everything and started again with a clean slate.
I managed to make ADB work (adb devices detects my device, could authenticate the computer, all seems good there). But if I start the phone in fastboot mode, connect and run fastboot devices, I get nothing back. It doesn't give any sign of the connected device. Windows's "Devices" window lists a device called "Android", but it's under "Unspecified" and has the yellow triangle/exclamation mark on the icon.
1. Am I right to assume that this will stop me from unlocking the bootloader (if I will use the unofficial method) and flashing TWRP and a custom ROM on the device?
2. More importantly: What could be wrong, how can I make fastboot see my phone?
Many thanks for the suggestions!
hi,
first do you have latest ADB and Fastboot
then connect your device and run adb devices. check if it detect the device means from the command prompt run "adb reboot bootloader" (without quotes)
now once after device reboots to bootloader check fastboot devices it will detect now
if not then goto device manager,right click on the device and click on update driver software and choose android fastboot interface
you are done now run fatboot devices,it will detect the device
Solved!
adbdriver com/downloads/
Very new to this so explain to me like I'm 5
I installed Ubuntu Touch on a Nexus 4. The install went fine, I did not install TWRP - wasn't required hadn't really planned on experimenting more. However, now I would like to try both Lineage and Paranoid Android.
How do I proceed at this point? Do I need to re-install original ROM or can I install TWRP directly? I am assuming that to install either OS I need to have TWRP installed - is that right?
Again, if you could please keep it simple - I am still swimming in the shallow end of the pool with Custom ROMs and Android.
Thanks
You said you already installed Ubuntu Touch.
I'm presuming that you have unlocked your bootloader before doing so and that you might have used the terminal and might be running Ubuntu.
If this is correct it should be no problem for you to:
- With your device powered off, press and hold the volume down button and then the power button simultaneously until the screen turns on to enter "Fastboot mode"
- Connect your device to your PC
- Open a terminal window and type
Code:
fastboot devices
if that does return
Code:
no permissions fastboot
it can be fixed by running fastboot as root from now on, i.e.
Code:
sudo fastboot [...]
- next, enter
Code:
fastboot oem device-info
if the output contains the line
Code:
(bootloader) Device unlocked: true
you are able to flash a custom recovery.
- To flash the recovery go directly dl.twrp.me/mako, and download the latest (topmost) image.
Now, find out where the image is downloaded and open a terminal there.
Then enter this command
Code:
fastboot flash recovery twrp-3.3.1-0-mako.img
(again with sudo if necessary)
- Reboot and you should be good to go
Code:
fastboot reboot
Thanks, that worked fine. Appreciate the step by step instructions.
I'm glad it worked for you
Does it mean, that u have Ubuntu, and android?
If possible can u share the screen shot or TWRP and boot options