Database Users

HP slate 7 extreme a plain tegra note?

Just wondering if anybody's tried to flash tn7 ROMs on their s7e? And does the s7e read the same model number as the tegra note? P1640?
Sent from my SGH-I317 using xda app-developers app

I've been stuck trying to figure out how to adb on my slate 7 extreme for weeks. Tried every driver and every cord and port. So while I'd love to confirm that it is the same... I'm still not sure.

Same here looking for a root
Sent from my HP Slate7 Extreme using xda app-developers app

I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.

Mobilla said:
I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.
Click to expand...
Click to collapse
cool. What do you mean by locking up a lot? it often hang and jam? . So i guess, staying at 4.2.2 is the best for now?

skysoblue said:
cool. What do you mean by locking up a lot? it often hang and jam? . So i guess, staying at 4.2.2 is the best for now?
Click to expand...
Click to collapse
It will work fine for up to about 10 minutes, then the screen will freeze and the only way to get it back is to hold the power down for 10 seconds and reboot it.
I am back on 4.2.2 right now, but when I have some extra time I might try a few things.

Mobilla said:
I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.
Click to expand...
Click to collapse
Is it possible to just have root set up on 4.2.2? Would like to keep all partitions stock if possible (as well as the bootloader). Would this help with stability issues? Sorry if these are noobish questions but thanks in advance

Dude you gotta give us a detailed guide on rooting puuuhleeaase

nejinikko said:
Dude you gotta give us a detailed guide on rooting puuuhleeaase
Click to expand...
Click to collapse
+1
I tried a chinese program without luck. I just bought a keyboard which works with the wrong layout in 4.2 and works perfect with 4.4 which I have on my other devices..therefore I am really looking forward flashing it!

Almost plain tegra
Hi, I agree with @Mobilla I installed android 4.4.2 from this link but be extreme careful, backup your rom first, KitKat works fine but randomly android freeze all system, I tested ClockWorkMod recovery and work flashing root file SuperSU-v1.94.zip but I don't test backup from recovery, well maybe someone can help us to know why kitkat freeze chinese root method is complicated I rooted with this method I don't read chinese I click some buttons and it works. Sorry with my English, I'm from El Salvador, I speak Spanish

I couldn't run 4.4 more than about 10 minutes before locking up, so I went back to 4.2.2 (rooted).
You can download the stock 4.2.2 update.zip from HP's website if you experience the same issues
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
The rooting method is the same as for the TN7 with the exception of fastboot commands you need to specify the vendorid (e.g. fastboot -i 0x03F0 oem unlock) I didn't try the Chinese tool.
You can flash root from recovery once it is unlocked.
I tried looking for what was causing the lockup but I couldn't find anything in the logs. If anyone has any tips for hunting down the problem I would be happy to try.

CWM
Hi, I tested CWM from this link and it works with nandroids backup, but the default storage is strange: /storage/emulated/sdcard0 but in this dir I can't move or delete that backup and use storage space I use a root explorer and can't move or delete, CWM works to root the device with SuperSU-v1.94.zip :good: but not for backup, see ya!

Rooting Slate 7 Extreme
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download Nvidia Tegra Note 7 Super Tool 2.2
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot (this is what I did, you can actually just use the command "fastboot -i 0x03F0 reboot")
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.

Hi @duocdx.bt good tutotial in
9. Remove the usb cable and reboot
you can reboot with this command:
fastboot -i 0x03F0 reboot
:good:
duocdx.bt said:
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download http://forum.xda-developers.com/showthread.php?t=2627654
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.
Click to expand...
Click to collapse

sparkly81 said:
Hi @duocdx.bt good tutotial in
9. Remove the usb cable and reboot
you can reboot with this command:
fastboot -i 0x03F0 reboot
:good:
Click to expand...
Click to collapse
Thanks! Edited that in and fixed the link to the super tool. Hopefully this is clear enough to newer users such as myself Hopefully HP starts releasing stable updates for us but if not, things aren't too bad with root :good:

What can I do?
hi, I also install my hp slate 7 extreme with 4.4.2 tegra note7 version, like you my android is blocking a few minutes later, how I return to my 4.2.2 rom if I haven't the stock recovery but yes the update.zip from hp.

What can i do?
hi, I also install my hp slate 7 extreme with 4.4.2 tegra note7 version, like you my android is blocking a few minutes later, how I return to my 4.2.2 rom if I haven't the stock recovery but yes the update.zip from hp.

duocdx.bt said:
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download Nvidia Tegra Note 7 Super Tool 2.2
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot (this is what I did, you can actually just use the command "fastboot -i 0x03F0 reboot")
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.
Click to expand...
Click to collapse
Succesfully rooted my HP Slate 7 Extreme 4409ra Tablet ty!

I have a Slate 7 Extreme 4400ca, and today installed the update listed on the HP webpage:
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6617231#N147
after a non-destructive installation, 'about tablet' reports that I'm running ANdroid 4.3, kernel 3.4.57-gc102837
Not 4.4 yet, but this should be helpful.
I haven't tried rooting yet.

Just a update on a simple way to root stock 4.2.2 slate 7 extreme
http://towelroot.com
Download apk
Install
Restart
Enjoy
Worked for me.

problem unlocking/rooting

Went through the Guide, however i've run into roadblocks.
i've installed all sdk packages, adb commands work, and fastboot commands return serial numbers. however once i run fastboot flashing unlock, there is a thread run in command promp window, with no change in the device's bootloader screen.
i've done the 6.0.1 update, the bootloader screen reads (some important ?) console NULL; device is LOCKED; download mode DISABLED; CONNECT USB DATA CABLE (while plugged in)
usb debugging is enabled, and the OEM unlock option is checked.
Any advice is appreciated.

Is it necessary to use this method? Won't something like Nexus Root Toolkit work too? Just a thought, I may be way off

gman88667733 said:
Is it necessary to use this method? Won't something like Nexus Root Toolkit work too? Just a thought, I may be way off
Click to expand...
Click to collapse
Haven't seen this mentioned before, but im new to this forum. Will defiantly try later if nothing else works

well it worked with unlocking, when rooting flashing twrp, i sucesfully flashed .zips in twrp, then stuck in bootloop. downlownloading the recovery to fix bootloop, any suggestions on how to succesfully root without BL using nexus root toolkit?

AlPoo said:
Went through the Guide, however i've run into roadblocks.
i've installed all sdk packages, adb commands work, and fastboot commands return serial numbers. however once i run fastboot flashing unlock, there is a thread run in command promp window, with no change in the device's bootloader screen.
i've done the 6.0.1 update, the bootloader screen reads (some important ?) console NULL; device is LOCKED; download mode DISABLED; CONNECT USB DATA CABLE (while plugged in)
usb debugging is enabled, and the OEM unlock option is checked.
Any advice is appreciated.
Click to expand...
Click to collapse
When you issue the "fastboot flashing unlock" command does it return a huge list of compatible commands? If so, your adb/fastboot is out of date.

Have you enabled bootloader unlocking in developer options?

Wiley Fox Swift2+ Bootloader Unlock

It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead

I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.

Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.

Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.

thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable

I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.

SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll

Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip

"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553

Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?

got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)

Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?

bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery

Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now

bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .

I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|

When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.

My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse

bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.

After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818

Boot loop after Android O DP2 update

I installed Android O DP2 update via OTA yesterday. The phone updated, rebooted to the new build and restarted abruptly and since then has been stuck in a boot loop. The Google logo shows up, goes to the android animation step and then Google logo appears again.
I don't have bootloader unlocked, don't have TWRP and have done OTA updates. I am able to get into the stock recovery mode.
How do I fix this, i.e. make it work in any way without erasing the user data? I don't mind extreme steps (without erasing user data) because I was planning to reflash 7 with unlocking & rooting today.

Try to wipe cache from recovery - in recovery hold volume-down and select "Wipe cache partition". Should do the trick

I tried, didn't work. Had to factory reset in the end. Also opted out of beta

I just read that some people that took the update from certain builds had boot loops due to the update only replacing part of the OS but leaving the 7.x.x system in place causing it to boot loop. I think it was like on android authority or something like that.
Sent from my Nexus 6P using XDA-Developers Legacy app

I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks

citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
POWER BUTTON + VOLUME DOWN BUTTON
Click to expand...
Click to collapse
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.

Mavelos said:
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.

citifone said:
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
Click to expand...
Click to collapse
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.

FAILED (remote: OEM unlock is not allowed)
Mavelos said:
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
Click to expand...
Click to collapse
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.

Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?

citifone said:
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
Click to expand...
Click to collapse
To unlock you first need to have ticked the allow OEM unlock from developer menu within the OS. It won't work otherwise.

Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.

Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here [="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?

Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.

scorneil said:
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
Click to expand...
Click to collapse
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Lord Aguacate said:
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Click to expand...
Click to collapse
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.

i have the same problem with this, and i cannot unlock it too, is there anyway to unlock this phone?

OTG works Perfect! But.....
Mavelos said:
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
Click to expand...
Click to collapse
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards

Lord Aguacate said:
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Click to expand...
Click to collapse
You're welcome. Get your phone fixed and return to the flashing community.

last night i my phone inside my freezer hehehe and this morning i tried to turn it on, and it pass the google logo boot normally but it only lasted for a few minute and then turn off and bootloop again. so i guess my 6p has a hardware faulty

HTC U Ultra stuck in bootloop..Can you experts validate the STEPS to solve the issue?

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.