Related
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
iamdarren said:
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
Where can I find the modified boot image?
Edit: Found it, nevermind.
messiahfreedom said:
Where can I find the modified boot image?
Edit: Found it, nevermind.
Click to expand...
Click to collapse
Grab it from here, and make sure to download the corresponding boot.img to your build number.
Link: http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
If we do it this way, will we lose data? Can we just update from 6.0.1?
jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
No, you won't loose any data. Your userdata/data partition will stay as is. You will just wipe the system and boot through TWRP, and then flash the listed image files.
superchilpil said:
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
But if we do it the manual way as stated before, do we lose root? What about gapps? Will those be included?
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
I ended up loading up from the PC. It's better this way because I only had 2gb of space on my 64gb!!! Bad thing is, I have spent about 2hrs installing!
Sent from my Nexus 6P using Tapatalk
So I can use flashfire to flash the latest N beta even though I'm currently running a custom ROM?
Sent from my Nexus 6P using XDA-Developers mobile app
GatorsUF said:
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
Click to expand...
Click to collapse
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
x.0ni.x said:
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
Click to expand...
Click to collapse
why does the wug toolkit not work?
I don't know a lot about Flashfire as far as it's compatibility with Custom Roms and such. I was previously on stock android Marshmellow with root and twrp. My phone downloaded the OTA for Android N when I "enrolled" in the beta program. I chose not to allow the phone to attempt to install the OTA as it would likely fail due to my custom recovery, to my surprise when I opened flashfire it offered to install the "update.zip" (AKA the OTA) and I simply hit "flash". It installed the OTA (did not use TWRP) and rooted my phone all on it's own, I did not lose anything no data was lost.
As a side not I would not recommend using Flashfire if you don't know how to use fastboot commands and the Android SDK. It is not complicated and it is a almost certain way to fix your phone when things go haywire. I strongly encourage you to learn how to use it as it is essential to owning a Nexus imo. These root kits and flashfire programs are cool, but they are always subject to failures...
Right now I'm on 7.0 DP5, unencrypted with root. I'm willing to enable encryption if it means I won't have to constantly manually flash the security updates and keep root. Is that what the "system-less root" technique is for? (and is it still a thing?)
Should I use the lastest TWRP 3.0.2-2 to flash N factory images? I'm guessing 3.0.2-1 bug is less serious now that there's a vendor.img available, but the last I had read from the dev team was that -2 was still untested and 3.0.2-0 was still the safest bet. I'm just not sure it's compatible with N?
EvanVanVan said:
Right now I'm on 7.0 DP5, unencrypted with root. I'm willing to enable encryption if it means I won't have to constantly manually flash the security updates and keep root. Is that what the "system-less root" technique is for? (and is it still a thing?)
Should I use the lastest TWRP 3.0.2-2 to flash N factory images? I'm guessing 3.0.2-1 bug is less serious now that there's a vendor.img available, but the last I had read from the dev team was that -2 was still untested and 3.0.2-0 was still the safest bet. I'm just not sure it's compatible with N?
Click to expand...
Click to collapse
You can't have root or custom recovery and take OTAs, but you can have an unlocked bootloader. Otherwise stock only. I am pretty sure systemless appeared when people were trying to keep using Android Pay. As for TWRP, I have had no problems using the latest, just don't restore / backup between MM and N.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You can't have root or custom recovery and take OTAs, but you can have an unlocked bootloader. Otherwise stock only. I am pretty sure systemless appeared when people were trying to keep using Android Pay. As for TWRP, I have had no problems using the latest, just don't restore / backup between MM and N.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you are rooted and have TWRP installed, you can use FlashFire to install the OTA and keep root and your custom recovery.
+1 Flashfire
Cool thanks for the suggestion, I actually saw something about FlashFire this morning but haven't had a chance to look into it yet. Do I need to be encrypted for it to work? And I'm assuming it's not entirely compatible with N's update system, it still takes some interaction to flash?
EvanVanVan said:
Cool thanks for the suggestion, I actually saw something about FlashFire this morning but haven't had a chance to look into it yet. Do I need to be encrypted for it to work? And I'm assuming it's not entirely compatible with N's update system, it still takes some interaction to flash?
Click to expand...
Click to collapse
The other issue with TWRP was backing up and restoring the EFS partition, it seemed that 3.0.2-1 corrupted it on restore which would be a problem. They did have a work around. They suggested using -0 would be fine. I have -2 and did a N to N restore with no issue, but I did not restore EFS. I'm always extra careful with new versions, I tend to backup my data and backups off-phone just in case.
dratsablive said:
If you are rooted and have TWRP installed, you can use FlashFire to install the OTA and keep root and your custom recovery.
Click to expand...
Click to collapse
My situation is that my 6p is rooted , TWRP installed and with custom kernel. I have searched quite a bit and cannot make sure which is the best way to update from MM to N. My thought is that:
1. FlashFire wipe system data n cache;
2. FlashFire MM stock boot image;
3. FlashFire N ota;
4. FlashFire custome kernel; and
5. Reboot.
The above steps to be done in one sequency. Please comment n million thanks.
CK
smallvan said:
My situation is that my 6p is rooted , TWRP installed and with custom kernel. I have searched quite a bit and cannot make sure which is the best way to update from MM to N. My thought is that:
1. FlashFire wipe system data n cache;
2. FlashFire MM stock boot image;
3. FlashFire N ota;
4. FlashFire custome kernel; and
5. Reboot.
The above steps to be done in one sequency. Please comment n million thanks.
CK
Click to expand...
Click to collapse
Put this in wrong thread and want to delete it.
That's a bit too complicated. Connect your phone to a Mac. Open a terminal and
adb devices (To see if your phone is recognized. If so continue, if not fix and then continue)
fastboot flash boot boot.img
fastboot reboot bootloader
fastboot flash system.img
fastboot flash recovery stockrecovery.img
fastboot reboot
That should unroot your device.
dratsablive said:
Put this in wrong thread and want to delete it.
That's a bit too complicated. Connect your phone to a Mac. Open a terminal and
adb devices (To see if your phone is recognized. If so continue, if not fix and then continue)
fastboot flash boot boot.img
fastboot reboot bootloader
fastboot flash system.img
fastboot flash recovery stockrecovery.img
fastboot reboot
That should unroot your device.
Click to expand...
Click to collapse
Thanks. And I will have a total experience of returning my 6p back to stock boot, stock recovery n no root. What about vendor.img?
smallvan said:
Thanks. And I will have a total experience of returning my 6p back to stock boot, stock recovery n no root. What about vendor.img?
Click to expand...
Click to collapse
You don't need vendor image unless you are flashing a different boot/system from what you currently have. But it also can't hurt as long as it's the correct version.
dratsablive said:
You don't need vendor image unless you are flashing a different boot/system from what you currently have. But it also can't hurt as long as it's the correct version.
Click to expand...
Click to collapse
I believe I am looking for a suitable way to upgrade my 6p from MM to N that I have explicitly stated at my wrong thread post. This is absolutely not my intention to return my 6p back to stock of MM. And there is every reason to upgrade to N, thus, vendor.img is no doubt a must for an amateur like me.
Nevertheless, thanks for dratsablive kind suggestions.
Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Many thanks and regards
demonjo2001 said:
Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Click to expand...
Click to collapse
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.
1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk
zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse
Thank you for answering, I did used Huawei MultiTool and Unbricked my device. I flashed four img files(SYSTEM,CUST,RECOVERY,BOOT) and now i am back to stock rom and running smoothly.
I tried to use force update feature on my device after that but again i got the same result, it stopped at 5% and failed. I guess i will keep it the way it's now.
Many thanks; you guys are awesome!
hamzio7 said:
1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk
Click to expand...
Click to collapse
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
It's for the other partitions like cust, modem etc.
demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
Don't use any other img file. And don't flash userdata.
If it works, don't change it. ?
Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.
goldfinv said:
Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.
Click to expand...
Click to collapse
Fastboot woukd be the only choice.
Sent from my honor 5X using XDA Labs
adriansticoid said:
Fastboot woukd be the only choice.
Click to expand...
Click to collapse
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.
goldfinv said:
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.
Click to expand...
Click to collapse
What partitions did you flash?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
What partitions did you flash?
Click to expand...
Click to collapse
The usual. Boot. System. Recovery. Cust.
goldfinv said:
The usual. Boot. System. Recovery. Cust.
Click to expand...
Click to collapse
No errors in fastboot?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
No errors in fastboot?
Click to expand...
Click to collapse
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
Goodluck with it man. I am sorry I can't help you any further as I am new in hsing fastboot. I got used to Odin in Samsung.
Sent from my Galaxy Tab 3 using XDA Labs
goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
There's no other solution, either stock img files or some sort of transitional package.
zinko_pt said:
There's no other solution, either stock img files or some sort of transitional package.
Click to expand...
Click to collapse
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.
goldfinv said:
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.
Click to expand...
Click to collapse
Let us know if you fixed it.
Sent from my Galaxy Tab 3 using XDA Labs
Same issue with me as well please help me in this case.
zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the lasthttps://cdn-cf-3.xda-developers.com/images/smilies/frown.gif installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.
nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.
tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
I7210I said:
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
Click to expand...
Click to collapse
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
funnel71 said:
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
Well keep in mind at the moment I am not rooted. As for updates when I used to be rooted I would flash the stock images for the system recovery bootloader and vendor partitions first. After that was done route would be erased and I could take the OTA update. I should also mention that I have not updated to Oreo. Given the hardware difficulties with my phone I've chosen to stay at 7.1.2
Sent from my Nexus 6P using Tapatalk
so...i'm in 8.1 and these is the conclusion in that state after few tests.
I7210I said:
so...i'm in 8.1 and these is the conclusion in that state after few tests.
Click to expand...
Click to collapse
I would tend to agree with you either you have a version that is not compatible with 8.1 or perhaps you just downloaded a corrupted zip file. I can't speak for root on 8.1 because I don't have that version but I think you've done enough testing to prove your theory that it's the zip that cause your boot loop
Sent from my Nexus 6P using Tapatalk
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
stankyou said:
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Use Magisk it's latest greatest. Just install the Magisk app from apkmirror and it will prompt to download flaahable zip. As far as TWRP 3.2.1-0 I believe is latest.
I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
What are you trying to say? The bootloop you are talking about is different from hardware bootloop of death in nexus 6p.
Supersu works fine for everyone,if its bootlooping for you thn you are doing something wrong or flashing wrong supersu zip.
The most of the reported bootloop of death users are not rooted.
the twrp is 3.2.1 and i used now the Magisk and it works.
the way i used is :
fastboot format userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery <filename>.img
fastboot flash system system.img
Fastboot flash vendor vendor.img
ofcurse with the right names of files..