probably been asked a bunch but i have been reading and im all confused:
I'm rooted, TWRP, unlocked and stock. how do i take the newest update without wiping data? do i just let the phone go for it? and what's this about vendor stuff? my old device needed one zip and one zip only to update as root
reinaldistic said:
probably been asked a bunch but i have been reading and im all confused:
I'm rooted, TWRP, unlocked and stock. how do i take the newest update without wiping data? do i just let the phone go for it? and what's this about vendor stuff? my old device needed one zip and one zip only to update as root
Click to expand...
Click to collapse
Bonus points: how will it work in the future? some have been saying some updates are different than others
FlashFire.
If you want to flash an OTA update, you have to return to stock. Download Google's factory image, extract the boot. system. and Recovery images from the image and Flash those leaving your data alone. You are now back to stock and can let the OTA install normally
Sent from my Nexus 6P using Tapatalk
I'm rooted, twrp, and stock rom, just like you.
To update my phone I use this guide and works like a charm. You keep your system intact.
STEP 9
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
joooe said:
I'm rooted, twrp, and stock rom, just like you.
To update my phone I use this guide and works like a charm. You keep your system intact.
STEP 9
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
This.
joooe said:
I'm rooted, twrp, and stock rom, just like you.
To update my phone I use this guide and works like a charm. You keep your system intact.
STEP 9
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
that guide has multiple guides, which one did you use? the "How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" seems to erase userdata as well...
uicnren said:
FlashFire.
Click to expand...
Click to collapse
please elaborate... all i get in a google search is "it's a tool" but there doesn't seem to be anything on how to use it to update and not loose userdata
reinaldistic said:
please elaborate... all i get in a google search is "it's a tool" but there doesn't seem to be anything on how to use it to update and not loose userdata
Click to expand...
Click to collapse
FlashFire.
And more info here.
And this is the first link returned when doing a google search for 'flashfire'.
reinaldistic said:
that guide has multiple guides, which one did you use? the "How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" seems to erase userdata as well...
Click to expand...
Click to collapse
He said step 9.
Heisenberg said:
He said step 9.
Click to expand...
Click to collapse
and like i said that one reads like i have to erase userdata as well, just wondering how it's done without doing that.
As in is it just as simple as not flashing userdata.img and not formatting? or will that break something?
reinaldistic said:
and like i said that one reads like i have to erase userdata as well, just wondering how it's done without doing that.
As in is it just as simple as not flashing userdata.img and not formatting? or will that break something?
Click to expand...
Click to collapse
No, you don't have to format userdata when updating. He put that in there because people may want to flash all of the images including the userdata.img, which you shouldn't ever do. If you happen to want to wipe everything while updating (who knows), that is how you would do it.
reinaldistic said:
and like i said that one reads like i have to erase userdata as well, just wondering how it's done without doing that.
As in is it just as simple as not flashing userdata.img and not formatting? or will that break something?
Click to expand...
Click to collapse
Section 9 makes no mention of wiping userdata as part of the process. That section at the bottom only serves as a warning not to flash the userdata.img, and that if the user wishes to wipe they can use the format command instead.
nathanchance said:
No, you don't have to format userdata when updating. He put that in there because people may want to flash all of the images including the userdata.img, which you shouldn't ever do. If you happen to want to wipe everything while updating (who knows), that is how you would do it.
Click to expand...
Click to collapse
Perfect thanks
Heisenberg said:
Section 9 makes no mention of wiping userdata as part of the process. That section at the bottom only serves as a warning not to flash the userdata.img, and that if the user wishes to wipe they can use the format command instead.
Click to expand...
Click to collapse
meh it seemed like it did, i dont want bricks so jsut doublechecking
Related
I was restoring a twrp backup and when it reaches "flashing system image" in the restore process it just reboots. Ive tried a few things but cant get it going. It just bootloops.
dontbeweakvato said:
I was restoring a twrp backup and when it reaches "flashing system image" in the restore process it just reboots. Ive tried a few things but cant get it going. It just bootloops.
Click to expand...
Click to collapse
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Heisenberg said:
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Click to expand...
Click to collapse
That was my first rooted twrp backup on 6p. I checked everything under what to backup. It has a system and system image to backup along with everything else. I thought it was weird to have both of them because I've never seen that before in twrp.
Well im back to normal. I must of screwed up the restore with the "system" and "system image" business. What's the difference in twrp restore between the two?
dontbeweakvato said:
Well im back to normal. I must of screwed up the restore with the "system" and "system image" business. What's the difference in twrp restore between the two?
Click to expand...
Click to collapse
Honestly, I don't know. I only know that you only need to backup system, boot, and data (if you want your apps and settings).
Heisenberg said:
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Click to expand...
Click to collapse
I have a soft bricked phone... I have done everything in your thread and flashing all the files worked except i get an error when flashing the system.img
it says error unable to allocate xxxxxxx bytes...? i really want my phone back to normal.. PLEAS HELP
taylorleach said:
I have a soft bricked phone... I have done everything in your thread and flashing all the files worked except i get an error when flashing the system.img
it says error unable to allocate xxxxxxx bytes...? i really want my phone back to normal.. PLEAS HELP
Click to expand...
Click to collapse
Try to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files.
indian84 said:
Try to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files.
Click to expand...
Click to collapse
I am sorry what do you mean?? what commands should I try?
taylorleach said:
I am sorry what do you mean?? what commands should I try?
Click to expand...
Click to collapse
Try this.
Reboot Bootloader again
1. fastboot erase userdata
And then follow the guide. Hopefully this will help.
indian84 said:
Try this.
Reboot Bootloader again
1. fastboot erase userdata
And then follow the guide. Hopefully this will help.
Click to expand...
Click to collapse
so, just to clarify... run the command "fastboot erase userdata" then run all of the IMG files?
taylorleach said:
so, just to clarify... run the command "fastboot erase userdata" then run all of the IMG files?
Click to expand...
Click to collapse
My bad.
use command fastboot format userdata
This will erase everything on your phone. Including photos and all the media.
After this use below command
fastboot reboot bootloader
And then follow guide and flash all IMG files.
indian84 said:
My bad.
use command fastboot format userdata
This will erase everything on your phone. Including photos and all the media.
After this use below command
fastboot reboot bootloader
And then follow guide and flash all IMG files.
Click to expand...
Click to collapse
that did not work same problem
"load_file: could not allocate 2014315040 bytes
error: cannot load 'C:\angler\images\system.img"
all other .img files i get OKAY except for system.img
PLEASE HELP ME UGG I REALLY NEED MY PHONE TO WORK AGAIN. I even tried re downloading the 6.0.1 again and also tried rebooting PC and multiple USB ports...
taylorleach said:
that did not work same problem
"load_file: could not allocate 2014315040 bytes
error: cannot load 'C:\angler\images\system.img"
all other .img files i get OKAY except for system.img
PLEASE HELP ME UGG I REALLY NEED MY PHONE TO WORK AGAIN. I even tried re downloading the 6.0.1 again and also tried rebooting PC and multiple USB ports...
Click to expand...
Click to collapse
You need to update your fastboot on your PC update everything in Android SDK or install latest minimal adb and fastboot. The system needs to be sent/flashed in parts as it's a big file. That will/should fix your issue.
matt1515 said:
You need to update your fastboot on your PC update everything in Android SDK or install latest minimal adb and fastboot. The system needs to be sent/flashed in parts as it's a big file. That will/should fix your issue.
Click to expand...
Click to collapse
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
taylorleach said:
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
Click to expand...
Click to collapse
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
taylorleach said:
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
Click to expand...
Click to collapse
matt1515 said:
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
Click to expand...
Click to collapse
If you already have the Android SDK it probably isn't a good idea to start installing other versions. Just go to where you installed the SDK on your PC, open SDK Manager, and update the platform-tools package.
matt1515 said:
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
Click to expand...
Click to collapse
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
taylorleach said:
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
Click to expand...
Click to collapse
Yes that's why it was stuck in a boot loop, the version of SuperSU that's included in TWRP is incompatible. Which version of TWRP did you flash? You need the latest in order for it to be able to successfully decrypt your storage so you can view it.
Heisenberg said:
Yes that's why it was stuck in a boot loop, the version of SuperSU that's included in TWRP is incompatible. Which version of TWRP did you flash? You need the latest in order for it to be able to successfully decrypt your storage so you can view it.
Click to expand...
Click to collapse
To be honest, I moved the file to my phones directory from my PC and did not just copy it so I lost it lol. Could you please tell me what one I should flash so I don't mess anything up. PLEASE and THANK YOU
taylorleach said:
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
Click to expand...
Click to collapse
+1 on Heisenberg you should use Android SDK and update properly but I knew you needed to get back up and running and figured that was the fastest way to help you. Read his thread like you would a book you will learn all you need to learn! But glad to hear I was able to help! Always use latest TWRP and SuperSU and you will be fine if you can decrypt then install SuperSU that way if not just hit cancel and adb sideload it. Look in general thread for the TWRP thread. Good luck and enjoy your working phone again!
Searched all over XDA, could not find one. The only one which is there is of an October build. Anyone has the flashable of the latest build including the January security fixes?
rajarshi10 said:
Searched all over XDA, could not find one. The only one which is there is of an October build. Anyone has the flashable of the latest build including the January security fixes?
Click to expand...
Click to collapse
Just download the factory image and use fastboot to flash the update.
Shockz said:
Just download the factory image and use fastboot to flash the update.
Click to expand...
Click to collapse
That is one thing that can be done, but I like keeping a backup zip in case something goes wrong. So you have it? Or know anyone who has it?
rajarshi10 said:
That is one thing that can be done, but I like keeping a backup zip in case something goes wrong. So you have it? Or know anyone who has it?
Click to expand...
Click to collapse
The image you download is yours to keep.
https://developers.google.com/android/nexus/images?hl=en#angler
Shockz said:
Just download the factory image and use fastboot to flash the update.
Click to expand...
Click to collapse
XxMORPHEOUSxX said:
The image you download is yours to keep.
https://developers.google.com/android/nexus/images?hl=en#angler
Click to expand...
Click to collapse
And doesn't this wipe the internal storage as well?
rajarshi10 said:
And doesn't this wipe the internal storage as well?
Click to expand...
Click to collapse
If you use the flash all script. Otherwise you can pick and choose what images you want to use.
I read that you can use the flash-all script without it deleting all your data. Just open the script with a text editor and remove "-w" from the last line. I personally did NOT do that, its just something I've read here on XDA. I followed Heisenberg's guide, step 10, to a T and everything went well. Remember you will have to reflash recovery and SuperSU again if you want those back.
I have a rooted 6P running the stock rom on the February security update with a bunch of Xposed modules and the Franco kernel. I know I won't get OTAs this way. Can I just flash the March security patch (MMB29V) and do nothing else? Or do I have to wipe data or factory reset? Do I have to do anything with the Franco kernel?
For the future, what would I need to do to flash Android N when it comes out on my rooted phone? Thanks a bunch!
Soundtallica said:
I have a rooted 6P running the stock rom on the February security update with a bunch of Xposed modules and the Franco kernel. I know I won't get OTAs this way. Can I just flash the March security patch (MMB29V) and do nothing else? Or do I have to wipe data or factory reset? Do I have to do anything with the Franco kernel?
For the future, what would I need to do to flash Android N when it comes out on my rooted phone? Thanks a bunch!
Click to expand...
Click to collapse
Most likely you cannot. An OTA update will do a check on your system and see that you have modified things and terminate install. You can leave your data alone but you will have to flash your boot and system partitions with the factory image
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Most likely you cannot. An OTA update will do a check on your system and see that you have modified things and terminate install. You can leave your data alone but you will have to flash your boot and system partitions with the factory image
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I know OTA updates are impossible, so I plan to flash the factory image from the Google developers website via fastboot. Does that change anything?
Soundtallica said:
I know OTA updates are impossible, so I plan to flash the factory image from the Google developers website via fastboot. Does that change anything?
Click to expand...
Click to collapse
Don't flash the entire factory image or you will lose data. / only the boot and system images to their respective partitions. Once you complete that you can Flash the OTA update zip file and you will still have your data you can extract the boot and system images from the main factory image you download from Google using WinRAR
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Don't flash the entire factory image or you will lose data. / only the boot and system images to their respective partitions. Once you complete that you can Flash the OTA update zip file and you will still have your data you can extract the boot and system images from the main factory image you download from Google using WinRAR
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It's easier to just flash all of the images (except userdata) top to update, rather than flashing two and then messing around with OTA.
So is there anyway to flash the update without losing my data/apps??
Thanks!
cattel said:
So is there anyway to flash the update without losing my data/apps??
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thank you very much!
Enviado de meu Nexus 6P usando Tapatalk
Step 9, right @Heisenberg ?
joooe said:
Step 9, right @Heisenberg ?
Click to expand...
Click to collapse
Yep. Probably would be a good idea to wipe data and the caches in TWRP first.
i used fastboot to install march update on my nexus 6p but now when trying to install twrp through fastboot it during writing it says permission denied. why is this?
mystertom said:
i used fastboot to install march update on my nexus 6p but now when trying to install twrp through fastboot it during writing it says permission denied. why is this?
Click to expand...
Click to collapse
Can you provide a screenshot of your attemp to flash the recovery? Also you might want to try opening the command prompt as administrator, right click on the command window in start menu and select open as administrator.
Heisenberg said:
Yep. Probably would be a good idea to wipe data and the caches in TWRP first.
Click to expand...
Click to collapse
Not at all a good idea @Heisenberg, as I just experienced. We were talking about keeping the apps and system as it was. Just wiped data and got an hardreset.
Clear cache only.
joooe said:
Not at all a good idea @Heisenberg, as I just experienced. We were talking about keeping the apps and system as it was. Just wiped data and got an hardreset.
Clear cache only.
Click to expand...
Click to collapse
Where did you say that? I know that wiping data will remove apps, but it's the right way to go about it to ensure no problems occur.
cattel said:
So is there anyway to flash the update without losing my data/apps??
Thanks!
Click to expand...
Click to collapse
It all went after this post.
But no problem.
joooe said:
It all went after this post.
But no problem.
Click to expand...
Click to collapse
Surely you were aware that wiping data was going to remove your apps? So all you needed to do was back them up first and restore them after you flashed. Apologies if I should have made that clear in my previous posts.
No problem. It was my stupid mistake.:good:
fastboot flash bootloader bootloader-angler-angler-02.45.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-angler-angler-02.50.img
fastboot reboot-bootloader
sleep 5
fastboot update image-angler-mmb29v.zip
Normally in the last line there is an option "-w" this wipes the data.
Don't do that and modify the script so the option is gone, like I did.
Uh, my phone just downloaded a system update of some sort, but I haven't installed it. Is this supposed to happen on a phone that's rooted and on the stock ROM? Can I install it safely or should I still flash the factory image instead?
And @Heisenberg, in your guide do you type in all the fastboot commands at once or do you do it line by line? Thanks again, your guide is super useful for rooting noobs like me :thumbup:
Soundtallica said:
Uh, my phone just downloaded a system update of some sort, but I haven't installed it. Is this supposed to happen on a phone that's rooted and on the stock ROM? Can I install it safely or should I still flash the factory image instead?
And @Heisenberg, in your guide do you type in all the fastboot commands at once or do you do it line by line? Thanks again, your guide is super useful for rooting noobs like me :thumbup:
Click to expand...
Click to collapse
Don't install it, it'll fail, you must flash the factory images. Each command is entered individually (press enter key to send the command), wait for flash to finish then enter the next command.
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.
Hey everyone, I need some help.
I have Magisk installed, and wanted to preserve root acces throughout the update (may security patch, ~80MB). I used this guide to do it, uninstalled Magisk, installed it on 2nd slot during phase 2, rebooted: bootloop. Stuck in an endless cycle: the kernel loads, but always reboots during the andorid one boot animation.
I'm looking for a way to make it functional while not losing my data, or a way to copy my data to a PC before flashing.
What can I do now?
Thanks in advance.
Flash stock ROM
Flash stock ROM through the MI FLASH TOOL..... download old version ROM through the XDA site nd flash it through MI FLASH TOOL also u can watch process on YouTube ....
Indiangautam said:
Flash stock ROM through the MI FLASH TOOL..... download old version ROM through the XDA site nd flash it through MI FLASH TOOL also u can watch process on YouTube ....
Click to expand...
Click to collapse
Will this preserve or wipe my data? I'm looking for a way that'll preserve my data.
droidx8 said:
Will this preserve or wipe my data? I'm looking for a way that'll preserve my data.
Click to expand...
Click to collapse
According to me no way to recover your data....if you flash stock ROM then all data will be wipe.....
Indiangautam said:
According to me no way to recover your data....if you flash stock ROM then all data will be wipe.....
Click to expand...
Click to collapse
Well let's not do that then, there could be another way... Thanks anyway!
droidx8 said:
Well let's not do that then, there could be another way... Thanks anyway!
Click to expand...
Click to collapse
As you wish....but if want to try my process then definitely your phone will bootup
droidx8 said:
Well let's not do that then, there could be another way... Thanks anyway!
Click to expand...
Click to collapse
You can choose to not wipe your data.
It's the "flash all except storage.bat"
You can download the last firmware here
http://en.miui.com/getrom.php?r=333&m=yes&app=false
You must have fastboot on your PC windows or Linux
So if you have a Windows just search how to install fastboot on Windows there's some great one on xda
Unzip the firmware open the flash all except storage bat
Remove both lines that contains
-OEM unlock
-OEM lock
Otherwise your data will be wiped and as you use magisk you want an unlocked bootloader
Open a powershell windows where the .bat file is
Then type without the quotes
"./flash_all_except_storage.bat"
Flashing procedure will take a few minutes on system partition but don't freak out
Once it's done reboot you'll be on 9.5.11 ROM version
You'll receive a 60mb ota to have the last one which is 9.11.13
You can boot TWRP to flash magisk now
And on next update download the last firmware
9.5.13 should be on the first link I gave you (there is always a delay between ota that are just patch and a full firmware that contains all the files)
Flash the boot.img or just reflash the ROM like above apply ota and reflash magisk
I ended up in the same situation but I think it's a technical problem where magisk is not concern I will not go into details but anyway this method is safe
JUST NEVER FORGET TO REMOVE THE OEM LOCK AND UNLOCK LINES since may update this will factory reset phone
ALWAYS USE THE "flash_all_except_storage" file
If you have some more questions I'm there
Dead-neM said:
You can choose to not wipe your data.
It's the "flash all except storage.bat"
I ended up in the same situation but I think it's a technical problem where magisk is not concern I will not go into details but anyway this method is safe
JUST NEVER FORGET TO REMOVE THE OEM LOCK AND UNLOCK LINES since may update this will factory reset phone
ALWAYS USE THE "flash_all_except_storage" file
If you have some more questions I'm there
Click to expand...
Click to collapse
Many thanks bro, worked perfectly! I haven't really kept up with android since 5.1, and now it's a bit hard to get back on track.
Data is intact, nothing lost, and the device is up and running.
droidx8 said:
Many thanks bro, worked perfectly! I haven't really kept up with android since 5.1, and now it's a bit hard to get back on track.
Data is intact, nothing lost, and the device is up and running.
Click to expand...
Click to collapse
Really nice to hear. Have fun with this little Beasty device