Related
I got the OTA update downloaded but could not install.Read somewhere if you have CWM ota update wont work.So i have downloaded the stock image for 4.0.2 and its in .tgz format
How can i upgrade to 4.0.2 using CWM or odin and not loose my data and setup.?
Please advice
Hussainally said:
I got the OTA update downloaded but could not install.Read somewhere if you have CWM ota update wont work.So i have downloaded the stock image for 4.0.2 and its in .tgz format
How can i upgrade to 4.0.2 using CWM or odin and not loose my data and setup.?
Please advice
Click to expand...
Click to collapse
Check out Chainfire's thread. He posted a no-wipe version flashable through Odin. Follow the instructions there and make sure you download the correct version for your phone (GSM/LTE)!
mbroeders said:
Check out Chainfire's thread. He posted a no-wipe version flashable through Odin. Follow the instructions there and make sure you download the correct version for your phone (GSM/LTE)!
Click to expand...
Click to collapse
hi thanks for your reply.His update you will not be updating to new bootloader am i right?
Hussainally said:
hi thanks for your reply.His update you will not be updating to new bootloader am i right?
Click to expand...
Click to collapse
Indeed, it won't touch your data, recovery or bootloader. They're all safe afaik
mbroeders said:
Indeed, it won't touch your data, recovery or bootloader. They're all safe afaik
Click to expand...
Click to collapse
thats the prob...4.0,2 has a new bootloader right?i want that.
ok what if i just want to install fresh clean stock 4.0.2...how do i do that?
Hussainally said:
thats the prob...4.0,2 has a new bootloader right?i want that.
ok what if i just want to install fresh clean stock 4.0.2...how do i do that?
Click to expand...
Click to collapse
If you want fresh clean stock then you can do two things:
1) on linux, extract the contents of the tgz package and use the sh script inside to flash.
2) since that's not possible on windows, you could use Chainfire's odin files first and next manually flash the bootloader and/or radioimage with fastboot. You can extract the bootloader and radio yourself from the tgz/tar package or look for them in the development section, someone posted them there.
mbroeders said:
If you want fresh clean stock then you can do two things:
1) on linux, extract the contents of the tgz package and use the sh script inside to flash.
2) since that's not possible on windows, you could use Chainfire's odin files first and next manually flash the bootloader and/or radioimage with fastboot. You can extract the bootloader and radio yourself from the tgz/tar package or look for them in the development section, someone posted them there.
Click to expand...
Click to collapse
You can flash it in windows using fastboot, you don't need to use odin for anything:
Extract the factory images
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Thanks everyone...will give it a go.....Cheers
krohnjw said:
You can flash it in windows using fastboot, you don't need to use odin for anything:
Extract the factory images
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Click to expand...
Click to collapse
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
mbroeders said:
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
Click to expand...
Click to collapse
What I posted does not wipe. There's little reason to use Odin. Using Odin you *can* easily brick your device (Ask all of the folks in the Nexus S forums that used Odin to flash the wrong package for their device).
fastboot update image-yakju-icl53f.zip <-- This does not wipe
fastboot -w update image-yakju-icl53f.zip <-- This wipes (-w wipes)
mbroeders said:
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
Click to expand...
Click to collapse
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
Nevermind guys...I DID IT.Thanks so much...excellent guide
Hussainally said:
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
ok i lost root after flashing to 4.0.2 using this guide and re did install superboot windows .bat and now the phone rebooted and its stuck on google screen...how long do i wait and what do i do next???
Click to expand...
Click to collapse
Hussainally said:
Hussainally said:
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
ok i lost root after flashing to 4.0.2 using this guide and re did install superboot windows .bat and now the phone rebooted and its stuck on google screen...how long do i wait and what do i do next???
Click to expand...
Click to collapse
Give it some time, if it doesn't boot all is not lost. Pull the battery and restart.
Click to expand...
Click to collapse
ok..fingers crossed...how much time?
Halleluyah....Praise the lord....thanks a million...All is well
Hussainally said:
ok..fingers crossed...how much time?
Click to expand...
Click to collapse
I think that it depends on how many apps do you have...usually 2-3 minutes max. !
Hi,
How do I update to the latest stock OTA when using CWM?
Do I extract the image zip file from the google image
and update in fastboot as below:
fastboot -w update image-yakju-icl53f.zip
if so, will this wipe anything?
either you use fastboot or you use cwm, no point using the two at the same time, under controlled conditions.
garpunkal said:
Hi,
How do I update to the latest stock OTA when using CWM?
Do I extract the image zip file from the google image
and update in fastboot as below:
fastboot -w update image-yakju-icl53f.zip
if so, will this wipe anything?
Click to expand...
Click to collapse
-w wipes. Omit -w and it won't wipe.
With that being said it's not necessary. Download the OTA, boot into recovery and apply the update with CWM.
garpunkal said:
Hi,
How do I update to the latest stock OTA when using CWM?
Do I extract the image zip file from the google image
and update in fastboot as below:
fastboot -w update image-yakju-icl53f.zip
if so, will this wipe anything?
Click to expand...
Click to collapse
You are mixing-up two things: there is a difference between flashing the latest build or updating a previous build. In the first case, you actually flash a full ROM. In the latter, you flash an increment OTA update. Both methods should get you to exactly the same build.
See links in my signature.
Sent from my Galaxy Nexus using Tapatalk
Look at this link, Worked for me thru CWM: http://forum.xda-developers.com/showthread.php?t=1419170
Yes, i am a noob, and yes i did watch that video, but still id like to be 987% sure that im doing everything right.
Yakju(xx) GNex and i would like it to be yakju.
I will do the following.
1) Install the drivers
2) Unlock the bootloader with Galaxy Nexus ToolKit.
3) Download the yakju image via ToolKit
4) Flash it somehow.
5) Once i have yakju(im now confused if i still have bootloader unlocked)
6) I`ll use #8 (1 - CLICK for all) in Galaxy Nexus ToolKit
7) And flash custom Roms.
tihend said:
Yes, i am a noob, and yes i did watch that video, but still id like to be 987% sure that im doing everything right.
Yakju(xx) GNex and i would like it to be yakju.
I will do the following.
1) Install the drivers
2) Unlock the bootloader with Galaxy Nexus ToolKit.
3) Download the yakju image via ToolKit
4) Flash it somehow.
5) Once i have yakju(im now confused if i still have bootloader unlocked)
6) I`ll use #8 (1 - CLICK for all) in Galaxy Nexus ToolKit
7) And flash custom Roms.
Click to expand...
Click to collapse
yes, you still have unlocked bootloader after flashing a factory image, unless you lock it yourself it's always unlocked. After flashing the image with the toolkit you should flash the radio and bootloader that are found in the same archive with the factory image file. You put them in the directory "put_img_files_to_flash_here" that is found where you installed the toolkit and then navigate around the menu and flash them. After this you are stock yakju and good to go.
EDIT: The next step, it you want to flash custom ROMs afterwards, is to flash a recovery using the same toolkit and then boot to it
bgdxv said:
yes, you still have unlocked bootloader after flashing a factory image, unless you lock it yourself it's always unlocked. After flashing the image with the toolkit you should flash the radio and bootloader that are found in the same archive with the factory image file. You put them in the directory "put_img_files_to_flash_here" that is found where you installed the toolkit and then navigate around the menu and flash them. After this you are stock yakju and good to go.
EDIT: The next step, it you want to flash custom ROMs afterwards, is to flash a recovery using the same toolkit and then boot to it
Click to expand...
Click to collapse
Thanks for the fast reply ! Theres an option in ToolKit to flash the factory image. But how do i flash radio and bootloader?
tihend said:
Thanks for the fast reply ! Theres an option in ToolKit to flash the factory image. But how do i flash radio and bootloader?
Click to expand...
Click to collapse
You copy the radio and bootloader .img files from the archive with the factory image (https://developers.google.com/android/nexus/images). You put them in the directory "put_img_files_to_flash_here" which is found in the main directory of your toolkit. Then you have the option to flash or boot image files in the toolkit. Just look around the menu and choose to flash them in the correct places (radio/bootloader).
tihend said:
Thanks for the fast reply ! Theres an option in ToolKit to flash the factory image. But how do i flash radio and bootloader?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
Hello everyone,
i decide to write this guide and to collect all the future Factory Images for Galaxy Nexus (maguro [GSM/GSPA+], toro[VZW CDMA/LTE], toroplus[Sprint CDMA/LTE])
Once installed them you retourn 100% stock.
This is usefull in case you don't want to wait official OTA or you have to use warranty for some problem or you like a really clean install.
Since Android 4.0 IceCreamSandwich you can't install OTA via update.zip method in stock recovery because is no more possible. If you try via stock recovery you get "error status 7" (this problem is corrected only if you use ClockWorkMod Recovery).
Then is necessary to use Factory Image provided by Google.
Factory Images:
JDQ39 Android 4.2.2 Factory Image "yakju" for Galaxy Nexus (maguro GSM/HSPA+)
MD5 Checksum 2fe041ac195086ef09274204c7e265e2
JZO54K Android 4.1.2 Factory Image "yakju" for Galaxy Nexus (maguro GSM/HSPA+)
MD5 Checksum cc710f1539765c6ab7fbb8f50b69f0d6
IMM76I Android 4.0.4 Factory Image "yakju" for Galaxy Nexus (maguro GSM/HSPA+)
MD5 Checksum 31447212fb4fb00aab4ef8bdc78e7ffb
JDQ39 Android 4.2.2 Factory Image "takju" for Galaxy Nexus (maguro GSM/HSPA+ with Google Wallet installed [notice, if you live outside US it simply disappears])*
MD5 Checksum 2fae8a6f50016e83f232fbb2d099fd42
JZO54K Android 4.1.2 Factory Image "takju" for Galaxy Nexus (maguro GSM/HSPA+ with Google Wallet installed [notice, if you live outside US it simply disappears])
MD5 Checksum 4e79a918a9a366166d0c23f99cc240db
IMM76I Android 4.0.4 Factory Image "takju" for Galaxy Nexus (maguro GSM/HSPA+ with Google Wallet installed [notice, if you live outside US it simply disappears])
MD5 Checksum 26ede55c44b503e4ab02969c22fa16e1
JRO03O Android 4.1.1 Factory Image "mysid" for Galaxy Nexus (toro VZW CDMA/LTE)
MD5 Checksum 1df6a2a7385c4745193fe82bf2a87f78
IMM76K Android 4.0.4 Factory Image "mysid" for Galaxy Nexus (toro VZW CDMA/LTE)
MD5 Checksum e76c6fe7d2bc799e5a6168f9dcb8c4ca
FH05 Android 4.1.1 Factory Image "mysidspr" for Galaxy Nexus (toroplus Sprint CDMA/LTE)
MD5 Checksum 7b3c4c37dd64a664427d3829e2491bee
NOTICE: If you have any GSM Galaxy Nexus (for example european version Yakjuxw, Yakjusc ecc... or other GSM version branded by Samsung) you can ALWAYS safely flash Yakju or Takju images provided by google, in order to get future OTA in time, directly from Google and not from Samsung)
How to install:
Requirements:
-Android SDK
-Java JDK
-Platform-Tools
-Unlocked bootloader ("fastboot oem unlock" pay attention, wipes everything, also your data)
-experience with adb and fastboot
NOTICE: If you never used the sdk, the jdk, fastboot and adb, before installing the factory image YOU HAVE TO FOLLOW some guide here on XDA in order to get sdk and unlocked bootloader.
Now you can proceed to install the Factory Image
On Windows:
1) copy the ecxtracted files (two times with 7zip) on android-sdk/platform-tools/ (this is important, if you dont unzip it, dont complain about "radio couldnt be loaded")
2) run a cmd and moves in "platform-tools" folder
3) write those command:
4A) If you are coming from a custom rom, this wipe your data/cache:
adb reboot bootloader
fastboot flash bootloader bootloader-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot -w update image-********.zip
if you want relock the bootloader (not necessary, only for warranty) do also these two step:
fastboot reboot-bootloader
fastboot oem lock
4B) If you are coming from another stock rom (official older OTA unrooted), this doen't wipe your data/cache:
adb reboot bootloader
fastboot flash bootloader bootloader-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot update image-********.zip
if you want relock the bootloader (not necessary, only for warranty) do also these two step:
fastboot reboot-bootloader
fastboot oem lock
On Linux, Mac:
1) copy the ecxtracted files (two times with 7zip) on android-sdk/platform-tools/ (this is important, if you dont unzip it, dont complain about "radio couldnt be loaded")
2) run a terminal and moves in "platform-tools" folder
3) write those command:
chmod +x flash-all.sh
./flash-all.sh
"flash-all.sh" wipes your data (it contains fastboot -w update, if you want to remove/change it edit with notepad++)
"flash-base.sh" flashes only the bootloader and the radio.
NOTICE:
1) Instead of ******** you have to put the name of the files you download.
2) somebody is aking why "adb reboot bootloader" each passages. Is not essential, but some people think it is better because you use the updated bootloader, maybe is only a superstition.
PLEASE LEAVE ME A THANKS
WARNING! DON'T DO THESE THING IF YOU DON'T KNOW WHAT YOU ARE DOING. I'M NOT RESPONSIBLE OF BRICKED GALAXY NEXUS OR SIMILAR
While it is a nice guide there is one already and its a sticky
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my Galaxy Nexus using Tapatalk 2
In old guide on XDA you needed to unzip the main folder and unzip and unzip the image-takju-jro03c.zip file to to get the boot.img , userdata.img and so on and you flash everything manually
so my question is >> in the old guide when you use Fastboot flash userdata userdata.img << this will wipe everything on the sdcard so is this the case here ? because i can see that useing the command fastboot -w update image-takju-jro03c.zip can avoid erasing everything is that right?
and thanks of course for the great guide
D3VI0US said:
In old guide on XDA you needed to unzip the main folder and unzip and unzip the image-takju-jro03c.zip file to to get the boot.img , userdata.img and so on and you flash everything manually
so my question is >> in the old guide when you use Fastboot flash userdata userdata.img << this will wipe everything on the sdcard so is this the case here ? because i can see that useing the command fastboot -w update image-takju-jro03c.zip can avoid erasing everything is that right?
and thanks of course for the great guide
Click to expand...
Click to collapse
I never used this guide because is not "transparent", I mean, my passages are the one that Google suggest. That guide is good but there are lots of thing that are a plus and not only using Google factory image. This is the way to use them. The other guide is a plus for advanced users. When you type -w it erases your internal memory (data and apps, this is in theory, I always use stock ROM than I never wiped with fast boot, maybe copy your SD on PC to prevent damage) bye
Sent from my Galaxy Nexus using xda premium
Not quite sure how your guide is more transparent or for beginners than efrant's is...
I followed his numerous times with no issues.
Its one thing to provide an alternative guide for those who wish to use it, it's another to knock someone elses work..
What's the difference with enfant's guide because I've been using his for the longest time. Is the command update image-xxxxxxx.zip recommended by Google? It's much shorter than flashing all the files individually but I dunno.
Sent from my Galaxy Nexus using Tapatalk 2
prinzhernan said:
What's the difference with enfant's guide because I've been using his for the longest time. Is the command update image-xxxxxxx.zip recommended by Google? It's much shorter than flashing all the files individually but I dunno.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Use intuition. Why Google should have done an extra zip to extract when they created the command fast boot update? Why complicate things when they are simple? If you exclude reboot commands you need only 3 commands with same effect!
Sent from my Galaxy Nexus using xda premium
ale.landra91 said:
I never used this guide because is not "transparent", I mean, my passages are the one that Google suggest. That guide is good but there are lots of thing that are a plus and not only using Google factory image. This is the way to use them. The other guide is a plus for advanced users. When you type -w it erases your internal memory (data and apps, this is in theory, I always use stock ROM than I never wiped with fast boot, maybe copy your SD on PC to prevent damage) bye
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not sure what you mean by "not only using Google factory image". Everything I mention in that guide is from Google, except the driver (which is originally from Samsung, but repackaged by 1wayjonny).
prinzhernan said:
What's the difference with enfant's guide because I've been using his for the longest time. Is the command update image-xxxxxxx.zip recommended by Google? It's much shorter than flashing all the files individually but I dunno.
Click to expand...
Click to collapse
The difference between this and my guide is that I have included ALL the steps to flash stock, from installing the drivers and downloading any needed files (the SDK and JDK are not needed by the way) to flashing your device. Additionally, as is stated in the first post of my thread, I have expanded all the steps and eliminated all scripts, so that people can see what is actually happening for the purposes of learning. For example, executing one command which actually flashes four images behind the scenes is not as valuable to learning as executing each command individually.
Included in the factory image is a script that flashes everything at once. Do you learn anything from it? Not really. There is no difference between using the fastboot update command to flash a bunch of images in a zip file, and flashing each image with the fastboot flash command. The difference is for instructional purposes.
efrant said:
Not sure what you mean by "not only using Google factory image". Everything I mention in that guide is from Google, except the driver (which is originally from Samsung, but repackaged by 1wayjonny).
The difference between this and my guide is that I have included ALL the steps to flash stock, from installing the drivers and downloading any needed files (the SDK and JDK are not needed by the way) to flashing your device. Additionally, as is stated in the first post of my thread, I have expanded all the steps and eliminated all scripts, so that people can see what is actually happening for the purposes of learning. For example, executing one command which actually flashes four images behind the scenes is not as valuable to learning as executing each command individually.
Included in the factory image is a script that flashes everything at once. Do you learn anything from it? Not really. There is no difference between using the fastboot update command to flash a bunch of images in a zip file, and flashing each image with the fastboot flash command. The difference is for instructional purposes.
Click to expand...
Click to collapse
Which I believe is better for beginners...
But what do I know... OH WAIT... I used to be one.
Bottomline, use the one you want... or are more comfortable with.
One thing to remember however... if you end up screwing your device up... efrants procedure will pinpoint exactly where you went wrong or what step it caused issues at.
efrant said:
Not sure what you mean by "not only using Google factory image". Everything I mention in that guide is from Google, except the driver (which is originally from Samsung, but repackaged by 1wayjonny).
The difference between this and my guide is that I have included ALL the steps to flash stock, from installing the drivers and downloading any needed files (the SDK and JDK are not needed by the way) to flashing your device. Additionally, as is stated in the first post of my thread, I have expanded all the steps and eliminated all scripts, so that people can see what is actually happening for the purposes of learning. For example, executing one command which actually flashes four images behind the scenes is not as valuable to learning as executing each command individually.
Included in the factory image is a script that flashes everything at once. Do you learn anything from it? Not really. There is no difference between using the fastboot update command to flash a bunch of images in a zip file, and flashing each image with the fastboot flash command. The difference is for instructional purposes.
Click to expand...
Click to collapse
simply they are different guide. My intention was porting my nexus s guide to galaxy nexus and not writing a poem. Few passages to use the images in the correct and simplest way. Then users choose to use your or mine with same results I never said that you are wrong, is only an alternative of lot of ways
can anyone upload the 4.1.1 yakju factory image for the galaxy nexus on any site because google's links aren't working for me please help i need it so bad
jamil-m77 said:
can anyone upload the 4.1.1 yakju factory image for the galaxy nexus on any site because google's links aren't working for me please help i need it so bad
Click to expand...
Click to collapse
sorry i dont have it. Does it work now?
OP updated! Sorry for the delay
OP updated with new 4.1.2!
OP updated
Hi, can someone get me factory image for 4.1.1 maguro? In fact, stock recovery will do the trick. Does the build number matter if a want only stock recovery? Thanks
M4t3s said:
Hi, can someone get me factory image for 4.1.1 maguro? In fact, stock recovery will do the trick.
Click to expand...
Click to collapse
See here, courtesy of oldblue910.
M4t3s said:
Does the build number matter if a want only stock recovery? Thanks
Click to expand...
Click to collapse
Yes it does.
I remove link last week because google deleted it and i havent it stored on PC
Sent from my Galaxy Nexus using xda premium
Took me FOREVER to get this to work because I had to use "./fastboot" instead of just "fastboot", but it saved my ass! Thanks a lot.
op updated!
Since we have working TWRP for MHC19J build - HERE , I have one question about flashing MHC19J to my Nexus 5x.
Every month I'm flashing security updates this way:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Reboot to recovery
Flash the latest SuperSU
but in MHC19J build there is also a new bootloader - bootloader-bullhead-bhz10m.img and a new radio - radio-bullhead-m8994f-2.6.31.1.09.img . Do I need to flash this new bootloader and radio too? I assume yes, but I prefer ask first before RMA
New official TWRP build 3.0.0.1 released: https://dl.twrp.me/bullhead/
bmbm said:
Since we have working TWRP for MHC19J build - HERE , I have one question about flashing MHC19J to my Nexus 5x.
Every month I'm flashing security updates this way:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Reboot to recovery
Flash the latest SuperSU
but in MHC19J build there is also a new bootloader - bootloader-bullhead-bhz10m.img and a new radio - radio-bullhead-m8994f-2.6.31.1.09.img . Do I need to flash this new bootloader and radio too? I assume yes, but I prefer ask first before RMA
Click to expand...
Click to collapse
Yes. You need to flash the bootloader and radio because they have changed. When in doubt, flash all of them except for user data. I follow Heisenberg's directions (below).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Or you can type in "flash-all.bat" , yes this is less safe , but I have been doing this method since the day I got my Nexus 5X and I have never encountered any issue ever since ! This is the method recommended by google so ... And by the way thank you for posting the link to the new TWRP , I needed this
Rozalina340 said:
Or you can type in "flash-all.bat" , yes this is less safe , but I have been doing this method since the day I got my Nexus 5X and I have never encountered any issue ever since ! This is the method recommended by google so ... And by the way thank you for posting the link to the new TWRP , I needed this
Click to expand...
Click to collapse
Won't flash-all also write user data, thereby deleting everything? There's likely a reason that the experts on this forum have never recommended to use flash-all. If you follow Heisenberg's directions, everything will be fine, and you won't lose any data.
Edit: here's something stating that flash-all will erase data unless you modify the command.
http://9to5google.com/2015/10/05/ho...nexus-5-nexus-6-nexus-7-nexus-9-nexus-player/
I didn't know Heisenberg's method doesn't erase user's data. My bad then ^^
Sent from my Nexus 5X using Tapatalk
I've flashed the last two updates using flashfire from chainfire. It injects root during the process so twrp is easily installed using flashify. All without using PC (root is of course required for using flashfire)
Skickat från min Nexus 5X via Tapatalk