Related
Didn't see this in General so thought it would be worth adding, especially since there have been many threads lately with new users wanting to root their phone and then getting scared of the guides.
Now there is also the option to go the official way to unlock the bootloader.
http://htcdev.com/bootloader/
noob here with a question... rooting is the same as unlocked bootloader??
coldsun15 said:
noob here with a question... rooting is the same as unlocked bootloader??
Click to expand...
Click to collapse
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
thomas_wlc said:
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
Click to expand...
Click to collapse
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
coldsun15 said:
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
Click to expand...
Click to collapse
I thinks that's pretty much it, once you have unlocked your bootloader you'll be able to flash any custom rom you like. Though it'll probably a bit tricky on the first go since you don't have a custom recovery yet, so I believe you'd have to flash some pc10img.
Still it's commonly to believed to be the better choice to stick with the more exhausting solutions posted around here, since HTC will register your phone if you use their tool. At least for the time being they claim that by using their way, your warranty will be void.
I've unlocked my desire z through the htcdev.com website.
Bootloader is unlocked, S-on..
But I can't get a rom installed, it gave me an error while trying to update from the recovery mode (apply update zip) using a stock rom with root.
Akward..
So now I've unlocked my bootloader, but still can't change my rom..
Anyone know how to do it after you've unlocked the bootloader?
flash custom recovery first, from there flash the rom
if you're s-on, bootloader is still locked....
artov said:
flash custom recovery first, from there flash the rom
Click to expand...
Click to collapse
I'm working on it
Gaining temp root using this guide worked.
http://forum.xda-developers.com/showthread.php?t=1178912
But when I press start clockwordmod, it says that my phone is not rooted..
While I press "flashcockwork" clockword mod recovery, I get an error.
än error occurred while attempting to run privileged commands!
I'm doing something wrong..
pretty annoying
I get unlock my bootloader today, and YES there is S-ON, but on the top is written in hboot menu big letters UNLOCKED (How you thinks, htcdev joke?).
I've installed clockworkmod using fastboot:
Code:
fastboot flash recovery clockwork_mod_for_vision.img
Then put off battery and turn on phone with volume down + power, I pressed 'recovery' menu option. Clockworkmod runs correctly. Then tried last stable CyanogenMod 7.1.0, flash was done without errors, I wiped out what's need (cache, data). Next I tried run phone, but freezes at splash (green htc letters on white background).
I tried also miui mod, but Ive got only MIUI splash screen nothing else.
Then I restored my htc from backup (done before flashing using clockworkmod) and Im still on the stock htc android 2.3.3.
Regards,
Mariusz
p.s Sorry for my poor english.
how can I install CM7 or other roms after unlocking the bootloader
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
pentie said:
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
Click to expand...
Click to collapse
I did it, but CM7 doesnt boot.
rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
flak999 said:
I did it, but CM7 doesnt boot.
Click to expand...
Click to collapse
Booting problem is mostly kernel related, do you have logcat output? (run "adb logcat" and boot the phone)
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
Click to expand...
Click to collapse
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
flak999 said:
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
Click to expand...
Click to collapse
now I confirmed the UNBLOCKED HBOOT somehow blocks the CWM to flash boot.img
My Phone have a S-OFF HBOOT and i was considering flash it to the UNLOCK the last night, now it seems not worth the try ~
pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
Click to expand...
Click to collapse
My friend has an officially unlocked Desire Z as well and I gave him these instructions to try it out, he has the same boot problem (stuck at splash screen). Maybe this information should either be stickied or added to a faq until there is a real solution to the problem (unlike this workaround), updated cwm or something like that.
Anyway thanks for sharing this information.
HTC bootloader unlock tool is quite restrictive. It still leaves you S-ON, so you won't be able to flash a new hboot or radios.
I recommend avoiding it and using the current well-proven methods from the XDA Wiki.
Sent from my Desire Z running CM7.
Its working now...
Steps I followed:
1. flash recovery using fastboot
2. Do a nandroid backup using recovery
3. flash boot.img using fastboot
4. reboot into recovery
5. wipe data/cache
5. install update for CM7, and gapps
Also make sure before doing any of these steps you have copied CM7 and gapps update onto sdcard.
Thanks everyone for helping out.
I am experimenting with this myself and I don't seem to be having the same issues flashing a boot.img from an update.zip in ClockworkMod recovery with the official HTC unlocked bootloader that others are having. Maybe it is the version of the recovery that is the issue? Which version is everyone trying to use? I am using the 3.xxxx version that is linked from the wiki. I have had other problems with the 5.xxx version and tend to stick with the older version for that reason anyways.
I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.
Freeje said:
I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.
Click to expand...
Click to collapse
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.
e8hffff said:
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.
Click to expand...
Click to collapse
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.
Freeje said:
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.
Click to expand...
Click to collapse
Have you done an OEM unlock?
fastboot oem unlock
e8hffff said:
Have you done an OEM unlock?
fastboot oem unlock
Click to expand...
Click to collapse
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.
Freeje said:
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.
Click to expand...
Click to collapse
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.
e8hffff said:
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.
Click to expand...
Click to collapse
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back
homecare tegra note 7
Freeje said:
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back
Click to expand...
Click to collapse
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7
Tha T said:
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7
Click to expand...
Click to collapse
Don't know how to do that.
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
REcovry
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card
Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
so did the odex$.2.2 work fine or what solution did you use? And where did you get your 4.2 rom ?
Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.
Try using rootjunkie supertool and get new kit kat or flash another ROM very easy to use
Sent from my Moto G using XDA Premium 4 mobile app
Tha T said:
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card
Click to expand...
Click to collapse
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.
recovery
Freeje said:
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.
Click to expand...
Click to collapse
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen
e8hffff said:
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.
Click to expand...
Click to collapse
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.
Tha T said:
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen
Click to expand...
Click to collapse
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.
Freeje said:
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.
Click to expand...
Click to collapse
Yes try, TegraNote_bootimg_4p3p1rip.zip first as I haven't tested the 4.4 boot.img, and only use the boot.img within as there is another directory of the uncompress boot.
wifi
Freeje said:
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.
Click to expand...
Click to collapse
Does shaky156's version have a working wifi or any rom at all, (even 4.2) that has wifi, my TN7 is next to useless without it
N10, rooted (supersu), unlocked bootloader, TWRP Touch recovery v2.6.3.1, Omnirom 4.4.2, Franco Kernel R16, ART.
I been flashing a lot, tried many roms... Now looking to go back to stock, but still want to use TWRP, and FK. I'm torn between using xposed (for AppOps and other cherrypicked mods) and Dalvik, or no xposed and ART...
My Question is, what is the best way to get back to stock 4.4.2 KOT49H, while keeping root and custom recovery. Do I need to sideload the factory image, re-root, and re-install custom recovery? Ideally I'm looking for a zip I can just flash along with supersu while keeping the custom recovery. I've looked for a zip file for pure aosp, but all I am finding is the sideload files from google's git, or "pure" AOSP roms with mods....
Also, I feel silly asking this because it seems pretty basic and I probably should already know at this point... The bootloader needs to stay unlocked once a custom recovery is installed, or should I be re-locking? I have been leaving it unlocked, for fear of bricking (aware bricking is not a huge deal with Nexus) but as I understand it, there are security concerns leaving the BL unlocked. Or am I way off base here?
TIA
Not much for security concerns, at least not for me. I personally always keep bootloader unlocked
As for keeping things similar but going back to stock +rooted, I would do this
Download factory image (just Google search: android factory image and grab appropriate one)
Unpack all on pc
Then boot to recovery, make a nandroid and then move all wanted files to PC (next steps involve some data loss)
Boot to bootloader
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
Now boot to recovery and should have an option to flash su, if not sideload a su.zip here
Now reboot, you will be stock kernel and ROM, and will be rooted and have same recovery as before
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Quick question.
I flashed the radio in my 6p.
Can I install the latest OTA Android update over that or do I need to go back to stock?
Also my phone is unlocked, does it need to be locked?
The radio flash didn't solve my problems.
Anyone?
Which radio did you flash?
2.50
Crakinarse said:
2.50
Click to expand...
Click to collapse
There's a lot about your config you haven't told us. Since you're staying your phone is "unlocked", I can only assume you mean the bootloader is unlocked, and you've got a custom recovery (TWRP) installed. If this is indeed the case, then no you should not take any "OTA" as any changes to "stock" (like a custom recovery) will cause it to fail.
You can, however, wipe and flash new Roms through twrp, or with an unlocked bootloader you can download the latest image from Google's sure for our device and flash that through fastboot (Google search to find tutorials on this there's a million of them). Be aware this will wipe EVERYTHING out on the device and reset it back to defaults (your data, recovery, etc.)
ohlin5 said:
There's a lot about your config you haven't told us. Since you're staying your phone is "unlocked", I can only assume you mean the bootloader is unlocked, and you've got a custom recovery (TWRP) installed. If this is indeed the case, then no you should not take any "OTA" as any changes to "stock" (like a custom recovery) will cause it to fail.
You can, however, wipe and flash new Roms through twrp, or with an unlocked bootloader you can download the latest image from Google's sure for our device and flash that through fastboot (Google search to find tutorials on this there's a million of them). Be aware this will wipe EVERYTHING out on the device and reset it back to defaults (your data, recovery, etc.)
Click to expand...
Click to collapse
All I did was unlock the bootloader and
fastboot flash radio image.
That is it.
I did not install a custom recovery.
Crakinarse said:
All I did was unlock the bootloader and
fastboot flash radio image.
That is it.
I did not install a custom recovery.
Click to expand...
Click to collapse
If you didn't flash a custom recovery you can download the ota without any issues. This is assuming that everything is still completely stock about your device. You can upgrade and downgrade your radio as you wish. I would advise to keep your bootloader unlocked so you can fix any problems if you ever have any.
I want to make a clean Install of factory image (Android 8.0 Oct) on my Nexus 6P with TWRP.
Should wipe Dalvik, Data, System and Internal storage, then move the stock zip file (That I downloaded from google's web) from my computer to my phone and just install in TWRP? Will it work?
Device is unrooted, only has an open boot loader, I just want to make a clean install of Android 8.0
If you wipe your internal all your downloads and your factory image are gone.
Sure you can flash the unpacked *.img with twrp, but don't try to flash the bootloader or radio with twrp.
If you really want a clean start and wipe everything, then you should flash the factory image with fastboot. This will update your bootloader and radio too.
coremania said:
If you wipe your internal all your downloads and your factory image are gone.
Sure you can flash the unpacked *.img with twrp, but don't try to flash the bootloader or radio with twrp.
If you really want a clean start and wipe everything, then you should flash the factory image with fastboot. This will update your bootloader and radio too.
Click to expand...
Click to collapse
Hi coremania, I have a few questions towards this method.
1. If the stock image is stored in either external SD card OR USB OTG, even then will there be any problem installing the the stock rom back using TWRP?
2. If the boot loader is unlocked, should one has to re-lock it first before reinstalling the stock rom either thru' TWRP or thru' Fasboot commands?. and finally,
3. Is it not advisable to flash the stock rom from the full factory image using TWRP rather than Fastboot?
(As I think it is easier to flash thru TWRP than typing those ADB commands in Fastboot).
Thank you for your inputs.
AndroMani said:
Hi coremania, I have a few questions towards this method.
1. If the stock image is stored in either external SD card OR USB OTG, even then will there be any problem installing the the stock rom back using TWRP?
2. If the boot loader is unlocked, should one has to re-lock it first before reinstalling the stock rom either thru' TWRP or thru' Fasboot commands?. and finally,
3. Is it not advisable to flash the stock rom from the full factory image using TWRP rather than Fastboot?
(As I think it is easier to flash thru TWRP than typing those ADB commands in Fastboot).
Thank you for your inputs.
Click to expand...
Click to collapse
If you decide to flash and test some stuff the bootloader should be always unlocked. If anything will went wrong and your bootloader is locked you're mostly f***ed. Never relock your bootloader until you want to sell your device.
I mostly use flashfire to flash stock and custom roms, TWRP is ok too, but it's easier to keep root and TWRP with flashfire by flashing stock images. Do not flash bootloader and radio with flashfire, never ever !!! There are TWRP flashable zips for bootloader and radio here on XDA, you only should use these with TWRP, but the safe way for bootloader and radio is fastboot for sure. Fastboot is the safest way for flashing stock,
but not absolutely necessary, you have to decide this for yourself.
Edit: to your first question, I never flashed with USB otg on the n6p, but I think yes it should be fine.
I hope someone here can help answer this question. I also want to flash factory image version 8.1.0 on my nexus 6P. But somehow my phone is not recognized by any computers I tried to plug it in. When I plug in the usb cable to the phone, it doesn't pop up the usb notification to choose MTP for file transfer. Then I try with Developer tab in Settings to choose it manually (USB debugging is enable) but it still doesn't work. My laptop has been updated with android usb drivers and other stuffs. I have a second phone (Oneplus 1) and it's recognized by my laptop the moment I plug it in. Please suggest any solutions to fix this. Thanks everyone.
sinjok said:
I hope someone here can help answer this question. I also want to flash factory image version 8.1.0 on my nexus 6P. But somehow my phone is not recognized by any computers I tried to plug it in. When I plug in the usb cable to the phone, it doesn't pop up the usb notification to choose MTP for file transfer. Then I try with Developer tab in Settings to choose it manually (USB debugging is enable) but it still doesn't work. My laptop has been updated with android usb drivers and other stuffs. I have a second phone (Oneplus 1) and it's recognized by my laptop the moment I plug it in. Please suggest any solutions to fix this. Thanks everyone.
Click to expand...
Click to collapse
Check your cable, or try a different with different port.
In the Dev options you can reset the debugging options, i guess a reboot is necessary afterwards.
coremania said:
If you decide to flash and test some stuff the bootloader should be always unlocked. If anything will went wrong and your bootloader is locked you're mostly f***ed. Never relock your bootloader until you want to sell your device.
I mostly use flashfire to flash stock and custom roms, TWRP is ok too, but it's easier to keep root and TWRP with flashfire by flashing stock images. Do not flash bootloader and radio with flashfire, never ever !!! There are TWRP flashable zips for bootloader and radio here on XDA, you only should use these with TWRP, but the safe way for bootloader and radio is fastboot for sure. Fastboot is the safest way for flashing stock,
but not absolutely necessary, you have to decide this for yourself.
Edit: to your first question, I never flashed with USB otg on the n6p, but I think yes it should be fine.
Click to expand...
Click to collapse
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
AndroMani said:
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
Click to expand...
Click to collapse
You don't need to ever relock your bootloader. If you want to try stock and use TWRP try SuperXe 8.1. It's just flaahable stock with some extras you can opt out of your not intereseted.
AndroMani said:
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
Click to expand...
Click to collapse
I can't confirm the relock and unlock method to go back to stock. Senseless to me.