Related
fastboot flash the factory image and install ota files.while restarted,the system encountered a error. manual restarted the system ver not 4.2.1.
it was still the original version
You need to flash the fixed 4.2 factory image from Google's site.
See this post: http://forum.xda-developers.com/showpost.php?p=34829307&postcount=144
How many sections are you going to post the same question in?????
Hey guys,
Its been a very long time since I flashed a rom on my N7. I was busy with the damn uni but now that summer is here I can play with my N7
Let me make this quick, I have unlocked the N7 using the tool kit long time ago and Im not sure if it still exists on my PC
Im currently running - CM10 4.1.2
Modle - GT-I9000
-Bootloader-
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
UNLOCKED
Recovery - i think CMW
Now I want to update to 4.2.2
Can I just flash a ROM with 4.2.2 or I have to do something with bootloader?
And btw just after going to the bootloader today which I didn't see long time ago the N7 didn't boot when I choose start then I held the power button till it rest and it worked but now a random reboot occurred :|
You need to update your bootloader to 4.18 or you may encounter problems. Also flash a new recovery (I recommend TWRP). From there you can just flash cyanogenmod 10.1.0 rc5 + gapps to upgrade (dirty flash).
Westervoort said:
You need to update your bootloader to 4.18 or you may encounter problems. Also flash a new recovery (I recommend TWRP). From there you can just flash cyanogenmod 10.1.0 rc5 + gapps to upgrade (dirty flash).
Click to expand...
Click to collapse
should I use the kit to update the bootloader? will it erase every thing? I want a new clean 4.2.2
mr.dj26 said:
should I use the kit to update the bootloader? will it erase every thing? I want a new clean 4.2.2
Click to expand...
Click to collapse
Just download the latest firmware from your device from Google (or look on this forum for the latest bootloader file). Extract all the contents in your fastboot folder. Open a terminal there and type:
fastboot flash bootloader name-of-bootloader.img
fastboot reboot-bootloader
Extra double check that you flash the correct and appropriate bootloader for your device. A corrupt bootloader might hard brick your device. I prefer to do this myself so therefore I don't use toolkits.
This will not erase anything and your bootloader remains unlocked.
Flashing a new recovery is done by:
fastboot flash recovery name-of-recovery.img
From there you can start wiping everything again and start flashing new roms. TWRP supports usb-otg, so you can use it to wipe the internal memory and install cyanogenmod 10.1.0 (android 4.2.2) from a usb stick. Way better then stock.
If you just want the official stock firmware, or for troubleshooting, then I recommend the sticky for manually flashing the official Google Android firmware.
Westervoort said:
Just download the latest firmware from your device from Google (or look on this forum for the latest bootloader file). Extract all the contents in your fastboot folder. Open a terminal there and type:
fastboot flash bootloader name-of-bootloader.img
fastboot reboot-bootloader
Extra double check that you flash the correct and appropriate bootloader for your device. A corrupt bootloader might hard brick your device. I prefer to do this myself so therefore I don't use toolkits.
This will not erase anything and your bootloader remains unlocked.
Flashing a new recovery is done by:
fastboot flash recovery name-of-recovery.img
From there you can start wiping everything again and start flashing new roms. TWRP supports usb-otg, so you can use it to wipe the internal memory and install cyanogenmod 10.1.0 (android 4.2.2) from a usb stick. Way better then stock.
If you just want the official stock firmware, or for troubleshooting, then I recommend the sticky for manually flashing the official Google Android firmware.
Click to expand...
Click to collapse
Hey there,
thank for the help.
I saw a vid on youtube, he just flashed the zip from recovery and it updated the bootloader.
Anyway, one last thing, can I use this " [BOOTLOADER] [4.2.2] JDQ39 4.18 Now Has Flash able Zip! "
other there are variants versions?
mr.dj26 said:
Hey there,
thank for the help.
I saw a vid on youtube, he just flashed the zip from recovery and it updated the bootloader.
Anyway, one last thing, can I use this " [BOOTLOADER] [4.2.2] JDQ39 4.18 Now Has Flash able Zip! "
other there are variants versions?
Click to expand...
Click to collapse
should work, check the latest comments in the thread to check whether it has been successful
whichever method you use, make sure to verify the md5 of the bootloader.img or zip before you flash it. pretty sure a corrupt bootloader will end up in a brick!
eddiehk6 said:
should work, check the latest comments in the thread to check whether it has been successful
whichever method you use, make sure to verify the md5 of the bootloader.img or zip before you flash it. pretty sure a corrupt bootloader will end up in a brick!
Click to expand...
Click to collapse
okay m8
thank you all for being very helpful ^^
Great im on 4.18
now ill get in to recovery and erase every thing then ill flash a new recovery and a new rom
Hi,
Currently on build LRX21P. (5.0 for the 2012 Nexus 7 wifi)
I recently received a notification that an OTA update to 5.0.2 was available.
When I tried to install it, the tablet would reboot into TWRP and stay there.
It looks like the update installed a file /cache/a6645eee89af34f58db74f6a1ad93fe400fcfc7b.signed-nakasi-LRX22G-from-LRX21P.a6645eee.zip but TWRP can't install it. I have attached the logfile from TWRP.
Any suggestions? I would much rather do an upgrade than wipe in order to install the 5.0.2 image.
Thanks!
Download the factory image from Google's website. Extract the system.img file from the zip. Use fastboot to flash: "fastboot flash system system.img". It worked fine for me.
On other devices I have been advised to NOT take an OTA if I had a custom recovery, even with a stock ROM. So one had to flash back to stock recovery before taking the OTA.
I have been trying to see if the same is true for the Nexus 7 with Android 5.x, but haven't found a definitive answer yet.
jbaumert said:
Download the factory image from Google's website. Extract the system.img file from the zip. Use fastboot to flash: "fastboot flash system system.img". It worked fine for me.
Click to expand...
Click to collapse
That worked perfectly. (used WUG toolkit to flash).
Thanks!
https://yadi.sk/d/v93-GFXngmcbq
Hi ,
Can i restore stock US retail 4.4.4 and update this OTA.
thanks
eugineprakash said:
Hi ,
Can i restore stock US retail 4.4.4 and update this OTA.
thanks
Click to expand...
Click to collapse
Yes thats how it usually works!
Are there any issues with upgrade?
AgentChaos said:
Yes thats how it usually works!
Click to expand...
Click to collapse
Are there any issues with upgrade?bcos iam currently in cm12.1 my bootloader version 41.19
I am planing to restore 4.4.4 us retail without downgrade my bootloader after that i am going upgrade from OTA in above thread.
Are there any issues with upgrade?Please guide me if i wrong.
Thanks,
eugineprakash said:
Are there any issues with upgrade?bcos iam currently in cm12.1 my bootloader version 41.19
I am planing to restore 4.4.4 us retail without downgrade my bootloader after that i am going upgrade from OTA in above thread.
Are there any issues with upgrade?Please guide me if i wrong.
Thanks,
Click to expand...
Click to collapse
I have been unable to install the update. Was with custom recovery and root and tried to install it and failed. Did factory reset, install stock recovery, download again the OTA from phone an try to install it and did not work.
Used the guide to go back to the stock firmware (though I already had it)
Try to install it using stock recovery, threw and error. (books.apk blabla).
Don't know what problems could yo be facing but man, this has been tough.
EDIT:
Just figured it out! The problem was exactly that I was already using the stock ROM and deleted some system APKs.
After trying going back to the really stock one once again (first I did not flash system images) it is installing correctly!
Btw this is my mirror for those who prefer using MEGA servers.
https://mega.co.nz/#!qJIE0SAY!u5-ezdk4o9OWfEKWVAJtW1KKQrV82NhiG1-myqlwOJ4
working confirm Thanks
Joandvg6 said:
I have been unable to install the update. Was with custom recovery and root and tried to install it and failed. Did factory reset, install stock recovery, download again the OTA from phone an try to install it and did not work.
Used the guide to go back to the stock firmware (though I already had it)
Try to install it using stock recovery, threw and error. (books.apk blabla).
Don't know what problems could yo be facing but man, this has been tough.
EDIT:
Just figured it out! The problem was exactly that I was already using the stock ROM and deleted some system APKs.
After trying going back to the really stock one once again (first I did not flash system images) it is installing correctly!
Btw this is my mirror for those who prefer using MEGA servers.
http s:/ / mega . co . nz/ #!qJIE0SAY!u5-ezdk4o9OWfEKWVAJtW1KKQrV82NhiG1-myqlwOJ4
Click to expand...
Click to collapse
working confirm Thanks
Where can I get the stock 4.4 so I can upgrade? I need stock recovery too.
I have problems to update too. XT1032, Retail US. As a first information, I have KK 4.4.4
I managed to download the update from my mobile (zipfile Blur_Version.210.12.61.falcon_umts.Retail.en.US, I already transferred to my PC thanks to Root Explorer), but when I go to "install now" and reboot, trying to install from zip file, pops a message from my recovery (PhilzTouch) Error Status 7. My phone is rooted by SU v2.46
So, what are the exactly step-by-step guide. I will appreciate that. Greetings from Chile
tifossi88 said:
I have problems to update too. XT1032, Retail US. As a first information, I have KK 4.4.4
I managed to download the update from my mobile (zipfile Blur_Version.210.12.61.falcon_umts.Retail.en.US, I already transferred to my PC thanks to Root Explorer), but when I go to "install now" and reboot, trying to install from zip file, pops a message from my recovery (PhilzTouch) Error Status 7. My phone is rooted by SU v2.46
So, what are the exactly step-by-step guide. I will appreciate that. Greetings from Chile
Click to expand...
Click to collapse
Change your recovery por el Stock Recovery for Kitkat 4.4.4
newellj79 said:
Where can I get the stock 4.4 so I can upgrade? I need stock recovery too.
Click to expand...
Click to collapse
This is the 4.4.4 Retail US (Last Build released)
https://mega.co.nz/#!ZIxQGJSJ!dnHim2zF3vDIenrvw24NeTDAeneA8m5BEidoD6hz4_k
That's the one I flashed following the guide to flash stock firmware in this forum and then updated with the OTA I posted before (I suppose the one of the topic is the same)
Finally, it's out!
kykemejia said:
Change your recovery por el Stock Recovery for Kitkat 4.4.4
Click to expand...
Click to collapse
Followed your steps:
- Flashed my phone (XT1032) with Retail US 4.4.4 Stock (RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml) using CMD, fastboot, typing list of files, etc.
- Updated some Motorola apps. Noticed Super SU is already included and installed by default, no way to uninstall it.
- Downloaded to my computer the OTA file (Blur_Version.210.12.61.falcon_umts.Retail.en.US), then moved OTA file to SD Card
- Turn off mobile
. Reboot in stock recovery, with the robot and the exclamation sign.
- Try to apply update from SD card with the file previously loaded on it (Blur_Version.210.12.61.falcon_umts.Retail.en.US)
- At verifying update package, update stops popping a message. The message in yellow is:
Package expects build fingerprint of motorola/falcon_retuglb/falcon_umts:4.4.4/KXB21.14-L1.61/62:user/release-keys or motorola/falcon_retuglb/falcon_umts:5.0.2/LXB22.99-36/35: user/release-keys; this device has motorola/falcon_retuglb/falcon_umts:4.4.2/KXB
Installation aborted.
Click to expand...
Click to collapse
What should I do in that case? Feel free to answer me in spanish for PM.
Is this any different from the February Canada release?
tifossi88 said:
Followed your steps:
- Flashed my phone (XT1032) with Retail US 4.4.4 Stock (RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml) using CMD, fastboot, typing list of files, etc.
- Updated some Motorola apps. Noticed Super SU is already included and installed by default, no way to uninstall it.
- Downloaded to my computer the OTA file (Blur_Version.210.12.61.falcon_umts.Retail.en.US), then moved OTA file to SD Card
- Turn off mobile
. Reboot in stock recovery, with the robot and the exclamation sign.
- Try to apply update from SD card with the file previously loaded on it (Blur_Version.210.12.61.falcon_umts.Retail.en.US)
- At verifying update package, update stops popping a message. The message in yellow is:
What should I do in that case? Feel free to answer me in spanish for PM.
Click to expand...
Click to collapse
In the SU menu you can find a way to delete the root, but I don't think that is causing the error.
Can you please tell me the version of recovery your phone have? You may have installed a kit kat 4.4.2 recovery or one with a different build number and that's causing the error.
IKXB21.14-L1.61
In the recovery menu, you should see the .61. I got the same problem as you and was using .32.
Did full factory reset, and installed stock again (w/o updating anything at all), when I checked the recovery, it was .61 and it updated perfectly.
In case you are really sure you got the actual last kitkat update firmware, you can try to extract the recovery.img and flash it using moto tool,
(rename it to StockKitkatrecovery.img and replace the one it brings with this one)
Joandvg6 said:
In the SU menu you can find a way to delete the root, but I don't think that is causing the error.
Can you please tell me the version of recovery your phone have? You may have installed a kit kat 4.4.2 recovery or one with a different build number and that's causing the error.
IKXB21.14-L1.61
In the recovery menu, you should see the .61. I got the same problem as you and was using .32.
Did full factory reset, and installed stock again (w/o updating anything at all), when I checked the recovery, it was .61 and it updated perfectly.
In case you are really sure you got the actual last kitkat update firmware, you can try to extract the recovery.img and flash it using moto tool,
(rename it to StockKitkatrecovery.img and replace the one it brings with this one)
Click to expand...
Click to collapse
I solved my problem by myself, thanks anyway. The issue for me, was updating some apps once in 4.4.4. You should not to do it.
Explanation for dummies, as me, in order to get Lollipop 5.0.2:
1) Flash your phone (XT1032) with Retail US 4.4.4 Stock (RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml), as it follows:
A) Extract the Retail US 444. Stock zip file (475 MB)
B) Download this file too: (1,5 MB) https://www.dropbox.com/s/nlbrn71wfqyup4u/mfastboot-v2.zip?dl=0 , and unzip it inside the same folder as you extracted Retail US Stock zip file. All files together in the same path.
C) Put your phone on fastboot (turn off, and then press Vol-and Power 3 secs, and release both buttons). Connect your phone to USB port.
D) Inside the folder containing all all these files, press **** + right click and choose "open file command", and a CMD window will open.
E) Once in CMD window, execute one by one:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
F) After reboot, unplug phone from USB port.
G) Done, you have now Stock Retail US 4.4.4 installed on your phone, Turn it on and set all things in order to go to home screen.
2)Once in the main screen , don't update your apps, no matter if they are even from Google or Motorola, don't do it
3) Download to your PC the OTA file (372 MB) Blur_Version.210.12.61.falcon_umts.Retail.en.US
4) Connect again your phone to USB port , and move OTA file to your phone SD Card
5) Once done previous step, go to Stock Recovery Mode. It is:
A)Turn Off your phone
B) Press Power and Vol- for 3 secs, then release
C) Select with vol- recovery option, and confirm it with vol+ button
D) Android Robot with exclamation sign will show up on the screen
E) Press vol+ and vol- for 5 secs, then press power once and release all the 3 buttons at the same time
F) Recovery Stock will appear you now.
6) Apply update from SD card with the file previously loaded on it (Blur_Version.210.12.61.falcon_umts.Retail.en.US). Select OTA file on "apply update from zip file".
7) Process will take up to 10-15 minutes aproximately. Voilá, you will have Lollipop 5.0.2 on your RetailUS mobile.
Hope it will be useful for dummies, like me. Thanks.
Greetings from Chile.
Perfect
I had same issue and after all these steps my phone updated perfectly.
Many thanks.:good:
Really great help. Many thanks :victory:
Can anyone give me the link of IKXB21.14-L1.61 recovery?
Anyways, I downloaded and now uploading only the IKXB21.14-L1.61 recovery.
Link of IKXB21.14-L1.61 Recovery
eugineprakash said:
Are there any issues with upgrade?bcos iam currently in cm12.1 my bootloader version 41.19
I am planing to restore 4.4.4 us retail without downgrade my bootloader after that i am going upgrade from OTA in above thread.
Are there any issues with upgrade?Please guide me if i wrong.
Thanks,
Click to expand...
Click to collapse
You cannot downgrade the 41.19 bootloader to the 41.13. If you try to do that you WILL hardbrick your phone. However you can downgrade from Lollipop to Kitkat 4.4.4 (I know because I am on the 41.19 bootloader and was on cm 12.1 but restored to 4.4.4 successfully).
You have to flash the firmware for your phone except for the gpt.bin and motoboot.img. Flash all the other files in the firmware for your phone without those two and you should be fine.
xt1028 Moto G
I'll never flash stuffs with Motorola recovery! Today I did a factory reset with the stock recovery and damn! it deleted all my files in the internal SD! IT would have never happened if I would have factory reset with TWRP!
I'll wait for lost101's zip!
I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop
I would like to know the same thing
Naruto101 said:
I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop
Click to expand...
Click to collapse
stkman32 said:
I would like to know the same thing
Click to expand...
Click to collapse
No you can't take an OTA if you have any modifications to /system (root). Have a look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?
Thanks for answering my question
roughriduz said:
I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?
Click to expand...
Click to collapse
No way around it, any modifications will cause the update to fail.
Heisenberg said:
No way around it, any modifications will cause the update to fail.
Click to expand...
Click to collapse
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
User data should never be affected during an OTA anyway.
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I am rooted now so I'll wait a while before updating an ota until there's a big deal of info. However, in the past if I was sticking with stock there's usually at least one developer who posts the updates with root and stuff built in so you can easily flash with twrp. So I'm kind of waiting for that. That or cataclysm or another awesome rom that's close to stock.
GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I wait for factory image for that build and flash over the new images when they become available (provided that root can still be achieved). Some will do a clean wipe and start fresh with the new build and reload in their apps and user data, others will just dirty flash the updated system (and boot/bootloader or whatever else was changed too).
If you think about it, it really isn't all that different from taking an OTA, the difference is that we're applying the commands to flash instead of having it automated. It's not that big of a trade off in my book.
I have 2 questions...
What is the easiest way to make flashing updates a breeze if I have mods in /system partition? I have heard of "freezing" them. Or is the only option... to delete every mod and flash updates? If so, should I keep a note of every change I make to/system?
And last... Should I make a backup of any file i am replacing or overwriting in /system? And if so, do I have to put them back how they were before flashing an update?
Delete
If you're rooted then you need to download the full factory image, extract system and vendor and flash those. Reflash SuperSU.
roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.
amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.
Click to expand...
Click to collapse
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. Latest factory image is the latest factory image from the nexus factory images page. It's not an update like ota, but rather the entire image they would return you to stock if all is flashed.
2. Flashing a modified boot does not give you root. You still have to flash SU, so saying the modified boot contains root isn't right.
3. I flash boot first unless there is an updated bootloader.
JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. This can be whatever the latest factory image is at the moment. It’s currently MDB08M. All the OTA does is update your phone to whatever build it was made for. Factory images already have previously released updates built into them. You can upgrade but avoid downgrading unless you want to factory reset your phone.
2. I’m referring to the boot.img without root by @mrRobinson found https://www.androidfilehost.com/?fid=24269982086992320 although this process can be used for systemless root also. For systemless root you wouldn’t flash SuperSU in TWRP but instead sideload the SuperSU APK as per Chainfire’s instructions and use the matching systemless root boot.img
3. I don’t think it matters but as long as you have the matching modified boot.img with the system.img installed before you restart, you should be fine.
amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit..
Click to expand...
Click to collapse
What the heck did I do wrong here? I just tried to apply the November OTA update to my MBD08K build, it didn't work, and now I am in the process of doing a full reset and rebuild of my phone (flash-all of factory images from Google)
Here are the notes I made as I attempted to follow the procedure in this thread:
Code:
- Download latest build for MBD08K from https://developers.google.com/android/nexus/images?hl=en
- Extract boot.img, system.img, vendor.img to C:\adb (or wherever where adb and fastboot are
installed). You have to
- Right-click, open command window here
- Ensure USB debugging is enabled on phone (grant permissions on phone if you get the popup)
- In command prompt, "adb devices"
- Should see serial number and "device"
- type "adb reboot bootloader"
- Should get to bootloader screen with little android man lying down with hatch open
- type "fastboot devices" - should see your serial # again and "fastboot" beside it.
- type "fastboot flash boot boot.img"
- type "fastboot flash system system.img"
- type "fastboot flash vendor vendor.img"
- Use volume keys to boot into recovery (in my case TWRP)
- Swipe to allow modifications
- Install -> SuperSU.zip that you should have on your phone from last time.
- Reboot system
I saw a red "your phone is corrupt" scary message on startup... took a while to boot. Couldn't get past the dancing circles.
Interrupted boot, rebooted to fastboot, tried to flash old modified boot.img
Booted again, got encryption unsuccessful warning
Flashed most recent boot.img again, stuck booting forever
try again:
- flash system.img
- flash vendor.img
- flash boot.img (modified)
reboot to recovery - your device can't be checked for corruption (yellow warning instead of red)
- swipe to allow modifications
- reboot with TWRP, swipe to install SuperSU
- Encryption unsuccessful. Prompt to factory reset. Click OK. Boots through TWRP.
Give up, start flashing factory images.
EDIT: I might be the stupidest person alive. I think I should have been using the files for MDB08M. Arggghhhh. Someone please confirm I am an idiot.
Edit 2: Factory reset worked, I am at MDB08M. Now rooting again... grr. At least I backed up all my apps & settings to Google Drive with TB.
Edit 3: Rooted and restoring all apps with TB. If anyone has any insight into where I F'ed up I'd appreciate it.