Flashing 4.3 with a Mac keeping all your data - Nexus 4 General

You will find other versions but this is how I did it and how I solved a few common problems. If you do it exactly following the instructions, you should not loose data. I flashed from Android 4.2.2 rooted.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Then if you want to root:
1. On your Mac, download TWRP recovery from here: http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img
2. Connect your Nexus 4 (debug mode) and put it in fastboot mode (point 5 above)
3. In terminal mode enter: ./fastboot flash recovery FILENAME.img (replace FILENAME by the file name of TWRP file you just downloaded)
4. Reboot your phone
5. Download directly from your phone this file (SuperSU): http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip
6. Shut down your phone and boot it in recovery mode (Once off, push vol+, vol-, and power all together). Choose recovery mode with vol-
7. Once you are in TWRP recovery mode push "Install", look for SuperSU file you just downloaded and follow instructions to flash the zip file.
That's it! You are now root. All your data are intact.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/ and http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/

jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse
I have the OTA file ... Will this work?
Sent from my Nexus 4 using Tapatalk 2

veteran_troller said:
I have the OTA file ... Will this work?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have no idea but it takes only a few minutes to download the original factory file.

jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse
this procedure wipe everything...I updated in this way yesterday

Works
Nice post. Works exactly as described.
Thanks!!
Matt
jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse

alakyr said:
this procedure wipe everything...I updated in this way yesterday
Click to expand...
Click to collapse
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!

jipi said:
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!
Click to expand...
Click to collapse
If you delete userdata.img from zipfile it will not wipe your data.

My data wiped too
I followed everything precisely on a completely stock Nexus 4 and it wiped my data too.. Not to critical for me since I dont do much with my phone so its not a bother but just for reference for others...

Well this method will keep your SD card contents, but will wipe your data/data on internal storage. So depends on what you mean by wipe

Remoteconcern said:
Well this method will keep your SD card contents, but will wipe your data/data on internal storage. So depends on what you mean by wipe
Click to expand...
Click to collapse
My Nexus 4 doesnt have an sd card..

I am sorry for those who have lost data but I did exactly what I have said and preserved all my data without any other manipulation. All my apps are still there, gmail accounts, WiFi passwords, etc... I am not an expert, maybe somebody will be able to explain when data are deleted and when not.

For anyone having trouble flashing on a mac, I kept getting a usb_write error when I tried to flash the system.img. Bootloader and radio flashed just fine, but not the actual rom. I got it working in windows and narrowed the problem down to either the version of adb and fastboot I was using ( they came from a zip in another thread called rootnexus4.zip) or the archive app I was using on macOS (The Unarchiver). Hope this helps someone.
Sent from my Nexus 4 using xda premium

Is the root okay?
Thanks

Root is fine. Using SuperSU 1.43
Sent from my Nexus 4 using xda premium

this didnt wipe /data for me either.

jipi said:
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!
Click to expand...
Click to collapse
sirry my bad...i used also the -w flag that wipe everything
Sent from my Nexus 4 using Tapatalk 4 Beta

alakyr said:
sirry my bad...i used also the -w flag that wipe everything
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, that was the problem, you didn't follow exactly the process. If you use -w flag it will wipe your data. I am sorry for you.

Noiseboy1176 said:
For anyone having trouble flashing on a mac, I kept getting a usb_write error when I tried to flash the system.img. Bootloader and radio flashed just fine, but not the actual rom. I got it working in windows and narrowed the problem down to either the version of adb and fastboot I was using ( they came from a zip in another thread called rootnexus4.zip) or the archive app I was using on macOS (The Unarchiver). Hope this helps someone.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
It is better to download a fresh version of Android SDK (link on the first post) and then upgrade it following the method as described in the link in point 4. It seems that ADB has to be upgraded to work with 4.2.2 because 4.2.2 implemented a new security feature with certificate.
So, if ADB works fine, don't change anything but if it doesn't, upgrade to the newest version. If you don't know how to do it follow the procedure, it is easy.

jipi said:
It is better to download a fresh version of Android SDK (link on the first post) and then upgrade it following the method as described in the link in point 4. It seems that ADB has to be upgraded to work with 4.2.2 because 4.2.2 implemented a new security feature with certificate.
So, if ADB works fine, don't change anything but if it doesn't, upgrade to the newest version. If you don't know how to do it follow the procedure, it is easy.
Click to expand...
Click to collapse
Agreed. That's what I usually do, but was feeling lazy and the version of adb I had works for everything I've tried so far... Unlocking boot loader on 4.2.2, flashing numerous recoveries, radios etc. So I thought it would be fine. Of course, it is possible that my problem was the archive utility I used to extract the ROM and not adb related at all. Either way, I figured ppl should know in case it happens to them.

Must the bootloader be unlocked to do this flash? Have flash many roms with Windows PC but now Im a mac user and never flashed roms with mac and yesterday i tried and didnt get it is the an video tutorial on this?

Related

Flash the Android 4.3 Build [Clean FLASH or Keep Data /w Flash] Root Available

*I'm not responsible for anything you do with this. I'm just trying to contribute back to the community*
Prerequisites
1. YOU MUST BE ON THE FACTORY IMAGE (NO MODIFICATIONS that means no custom recovery, kernels, radios, etc)
**User Impo5sible says its possible with custom recovery and kernels I'm not 100% sure so YMMV*** *ANOTHER EDIT - USERS REPORT GETTING STUCK ON NEXUS LOGO if you have a custom rom/kernel and not using the -w command to wipe DATA)
2. YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
SDK /w adb & fastboot Link: http://developer.android.com/sdk/index.html
PDAnet Link:http://pdanet.co/
3. ENABLE USB Debugging via Developer settings
(press the build button 7 times to activate it the "settings --> about phone --> Build Number --> go back --> Developer Settings --> Check USB Debugging)
4. Android 4.3 Image can be obtained from Google
Image Link: https://developers.google.com/android/nexus/images
When you have all of this installed... you may proceed
Step 1: Use 7zip or compression program equivalent to extract the stock image file that is .TGZ
Step 2: You should see a stock image file that is .TAR...extract this once again with any compression program (you should see a butt load of flash files)
Step 3: Plug your device in the computer (USB debugging should be enabled & I recommend switching the transfer type to PTP/Camera)
Step 4: Launch command prompt (start --> run --> "cmd")
Step 5: type in command prompt "cd directory where you have the adb & fast boot"
for example here is mine "cd C:\Users\MC704\Desktop\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\platform-tools"
Step 6: Verify that it is detecting your device by typing in command prompt "adb devices" (YOU SHOULD SEE YOUR DEVICE HERE ) if not recheck usb debugging & camera ptp... unplug and replug the phone back into your comp
**take a breather we are almost done**
Step 7: Turn your device off and go into fastboot mode (Hold Power Button + Volume Up & Down)
Step 8: Unlock your bootloader by typing in command prompt "fastboot oem unlock" [THIS WILL DELETE ALL YOUR DATA]
It will prompt you to unlock the Device
Step 9: Remember all those files you extracted from the ".TAR"? Copy them to the same folder where your adb and fastboot files are
Step 10: ****************VERY IMPORTANT************* DO THIS IN ORDER
I got these commands from the flash-all.sh file
Type in the command prompt each step one at a time and wait for it to complete
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot -w update image-occam-jwr66v.zip"
***NOTES FOR THIS STEP***
*REMOVE the -w from the last step if you want to keep your data (assuming your bootloader was already unlocked)*
***User chrisjcks noted you can use the flash-all.bat file that was in the zip to make life easier***
Step 11: Enjoy! If you do not plan on putting any custom roms or rooting etc. I recommend rebooting into fastboot mode (Hold Power Button + Volume Up & Down) when the phone is unlocked and type in the command prompt "fastboot oem lock" (you have to have USB debugging & PTP camera enabled)
If I missed out on any steps, please do let me know I will update the OP.
MISC info.
1. People who are using custom recoveries & root & would like to KEEP ROOT... Check this post out it should help you fellars
http://forum.xda-developers.com/showpost.php?p=43917716&postcount=56
2. STUCK ON BOOT LOGO? Check this post out for the fix
http://forum.xda-developers.com/showpost.php?p=43920888&postcount=85
3. NEW ROOT BY CHAINFIRE
http://forum.xda-developers.com/showthread.php?t=2025274
mc704 said:
*I'm not responsible for anything you do with this. I'm just trying to contribute back to the community*
FIRST
1. YOU MUST BE ON THE FACTORY IMAGE (NO MODIFICATIONS that means no custom recovery, kernels, radios, etc)
2. YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
3. ENABLE USB Debugging via Developer settings (press the build button 7 times to activate it the "settings --> about phone --> Build Number"
4. 4.3 Image from Google (https://developers.google.com/android/nexus/images)
When you have all of this installed... you may proceed
Step 1: Use 7zip or compression program equivalent to extract the stock image file that is .TGZ
Step 2: You should see a stock image file that is .TAR...extract this once again with any compression program (you should see a butt load of flash files)
Step 3: Plug your device in the computer (USB debugging should be enabled & I recommend switching the transfer type to MTP/Camera)
Step 4: Launch command prompt (start --> run --> "cmd")
Step 5: type in command prompt "cd directory where you have the adb & fast boot" for example here is mine "cd C:\Users\MC704\Desktop\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\platform-tools"
Step 6: Verify that it is detecting your device by typing in command prompt "adb devices" (YOU SHOULD SEE YOUR DEVICE HERE ) if not recheck usb debugging & camera mtp... unplug and replug the phone back into your comp
* take a breather we are almost done
Step 7: Turn your device off and go into fastboot mode (Hold Power Button + Volume Up & Down)
Step 8: Unlock your bootloader by typing in command prompt "fastboot oem unlock" [THIS WILL DELETE ALL YOUR DATA]
It will prompt you to unlock yadda yadda
Step 9: Remember all those files you extracted from the ".TAR"? Copy them to the same folder where your adb and fastboot files are
Step 10: ****************VERY IMPORTANT************* DO THIS IN ORDER
I got these commands from the flash-all.sh file
Type in the command prompt each step one at a time and wait for it to complete
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot -w update image-occam-jwr66v.zip"
Step 11: Enjoy! If you do not plan on putting any custom roms or rooting etc I recommend rebooting into fastboot mode (Hold Power Button + Volume Up & Down) when the phone is locked and type in the command prompt "fastboot oem lock" (you have to have USB debugging & MTP camera enabled)
If I missed out on any steps, please do let me know I will update the OP.
Click to expand...
Click to collapse
or you could just unzip it, and double click the Flash All bat file. :laugh:
My bootloader is already unlocked so I would skip step 8. In this case, would it still wipe all of my data since this is not an OTA or will it just upgrade my OS leaving the apps/data/etc intact? I've done this process many times before with the factory images, but I thought it always wiped the system.
chrisjcks said:
or you could just unzip it, and double click the Flash All bat file. :laugh:
Click to expand...
Click to collapse
I'm old school I'm not too familiar with it . If you want to write a mini guide to consolidate all of this for everyone, I'll update the OP.
mbwelch said:
My bootloader is already unlocked so I would skip step 8. In this case, would it still wipe all of my data since this is not an OTA or will it just upgrade my OS leaving the apps/data/etc intact? I've done this process many times before with the factory images, but I thought it always wiped the system.
Click to expand...
Click to collapse
It wipes the system. or atleast it did for me
If you remove the "-w" from the last step it won't wipe data
Sent from my Nexus 7
mc704 said:
.... no custom recovery, kernels, radios, etc)
Click to expand...
Click to collapse
I had custom kernel and recovery - still Im able to flash factory image from google with no problem, at all..
Is there a easier alternative?
Sent from my HTC One using Tapatalk 4 Beta
chrisjcks said:
or you could just unzip it, and double click the Flash All bat file. :laugh:
Click to expand...
Click to collapse
Impo5sible said:
I had custom kernel and recovery - still Im able to flash factory image from google with no problem, at all..
Click to expand...
Click to collapse
There are always exceptions but I'll note that in the OP for people to see. I'd wrote the guide with the intention of a no failure rate or possible errors.
mc704 - in most cases that would be true - but the Flash-All.bat file is inside the ROM itself.
its as safe as you can get.
I'm on stock 4.2.2, but with custom recovery and kernel.
If I want to get those back to stock, can I just connect my device in fastboot mode, go to command prompt and type:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
?
I have the JDQ39 factory image, and will make sure everything is in the right directory.
LOVE ME PLEASE said:
Is there a easier alternative?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
They are pushing the OTA I believe for a short time
chrisjcks said:
mc704 - in most cases that would be true - but the Flash-All.bat file is inside the ROM itself.
its as safe as you can get.
Click to expand...
Click to collapse
Sure thing I'll update it in the OP:good: thanks for the contribution
To avoid losing data, unzip image-occam-jwr66v.zip with 7 zip.
Now use fastboot to flash bootloader, boot, radio, recovery and system. everything except userdata.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
dan in la said:
I'm on stock 4.2.2, but with custom recovery and kernel.
If I want to get those back to stock, can I just connect my device in fastboot mode, go to command prompt and type:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
?
I have the JDQ39 factory image, and will make sure everything is in the right directory.
Click to expand...
Click to collapse
yup. and system.img if you want to remove root
delete - misread the previous question.
(sure i used to be able to delete my own posts.....)
how can we check which radio version is currently on device
mangomonkey00 said:
how can we check which radio version is currently on device
Click to expand...
Click to collapse
Settings > about phone > baseband version (last 2 numbers)
Sent from my Nexus 4 using xda app-developers app
Look in Settings => About
easy way
For me, All i did was extract the package and edit the .bat file and remove the -w in the code. Then ran it under fastboot. It updated my apps and updated to 4.3, no data wipe.
thanks OP got mine updated to 4.3 without -w
vickpick said:
To avoid losing data, unzip image-occam-jwr66v.zip with 7 zip.
Now use fastboot to flash bootloader, boot, radio, recovery and system. everything except userdata.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
yup. and system.img if you want to remove root
Click to expand...
Click to collapse
Who would like to remove root?
And to summarize:
If someone has stock rom, rooted, with custom kernel, all he has to to do in order not to lose his data and rooting is to flash everything except: system.img and userdata.img?
After that, he will have the update with all data still available?
otariq said:
Settings > about phone > baseband version (last 2 numbers)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
mine says 84 i suppose the latest was 83 have i done something wrong and also in quick system info pro in properties its opengl es cm 1.1 which i think should be 3.0
what should i do
checked it has to be 84 but what about opengl es

Please Help Tried Updating to 4.4 Kitkat Bricked

Ok so I tried updating my phone that was already rooted on Android 4.3 S-OFF to 4.4 kitkat with sinless rom sense. Transferred the rom zip to my phone, then proceeded to wipe the system and data, as well as davalik cache with clockworkmod recovery. Attempted to flash the rom and it aborted. Tried a few times and nothing worked. Didn't realize till after that my phone had no OS, and now all I can do is enter the bootloader. Can't enter recovery as the phone will enter clockworkmod then abort and reboot the phone. Not sure what to do at this point as I tried one of the guides and couldn't figure it out. If anyone can help me I'd greatly appreciate it. At least I backed everything up on my computer manually and am using my iPhone 4 until I can get this fixed. Thanks in advance.
Try reflashing recovery then if that works ad b push or usb otg a working Rom to your phone
Sent from my HTC One using Tapatalk
nathlynn22 said:
Try reflashing recovery then if that works ad b push or usb otg a working Rom to your phone
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
How do I reflash recovery when I can't access the filesystem? Do I need to setup ADB and connect to my phone via command line to initiate the transfer? Can you link me to a thread that explains how to setup ADB in a case like this? Thanks
You need to reflash cwm. I'll try find a link. But after recovery is working you would have to use ad b to sideload the Rom. Have you tried from bootloader fastboot erase cache?
Sent from my HTC One using Tapatalk
nathlynn22 said:
You need to reflash cwm. I'll try find a link. But after recovery is working you would have to use ad b to sideload the Rom. Have you tried from bootloader fastboot erase cache?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
My biggest issue is being able to reflash clockworkmod. If I could that out of the way, I already have the rom on the phone storage, so I should in theory be able to reflash I'd think.
I don't have the option to delete cache within the bootloader under fastboot
One Hype said:
How do I reflash recovery when I can't access the filesystem? Do I need to setup ADB and connect to my phone via command line to initiate the transfer? Can you link me to a thread that explains how to setup ADB in a case like this? Thanks
Click to expand...
Click to collapse
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!
hardstuffmuc said:
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!
Click to expand...
Click to collapse
Gotcha. Makes sense. Will try and let you know. Thanks so much!
Htc one kiktkat 4.4 update gone wrong
hardstuffmuc said:
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!
Click to expand...
Click to collapse
I did all what you said there its still takes me back to bootloader...
and that red message active cmdline overflow (1085bytes) still there...any soulutions to fix this please?
hardstuffmuc said:
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!
Click to expand...
Click to collapse
Just tried everything and it worked 100%! Can't thank you enough!

Use fastboot to flash 4.4.3 without waiting for OTA

This is the well-established way to flash factory images without waiting for the OTA, using a Windows computer.
You can have a custom recovery, but you must otherwise be stock.
Your bootloader must be unlocked.
You should not lose apps (except for non-stock system apps) or data, but don't hold me responsible if you do.
You will have to reload non-stock system apps like Xposed framework (in fact, I uninstalled the Xposed framework using the Xposed framework installer before starting this process).
This is a modification of the process explained here, which I have mostly cut-and-pasted:
http://forum.xda-developers.com/nexus-4/general/flash-android-4-3-build-clean-flash-t2376681
(Credit to mc704.)
1. You must have ADB, fastboot, and USB drivers for the N4 on your PC. Not hard to find; the thread referenced above tells you one way to get them. Put adb.exe, fastboot.exe, AdbWinApi.dll, and AdbWinUsbApi.dll in a folder on your PC - let's call it C:\N4Update
2. Enable USB Debugging via Developer settings on your phone.
3. The Nexus 4 (mako) 4.4.3 image can be obtained from Google
Image Link: https://developers.google.com/android/nexus/images#occamktu84l
Step 1: Use 7zip or an equivalent compression program to extract the stock 4.4.3 image file that has extension .TGZ
Step 2: You should see a stock image file that has extension .TAR...extract this once again with 7zip (or equivalent) into C:\N4Update
Step 3: Plug your device into the PC (USB debugging should be enabled)
Step 4: Launch command prompt from C:\N4Update, or alternatively start a command prompt (start --> run --> "cmd") and cd to it (cd C:\N4Update)
Step 5: Verify that the PC is detecting your device by typing in command prompt "adb devices" (you should see a code representing your device, and then "device" following it); if not, recheck usb debugging, and unplug and replug the phone back into your PC
Step 6: Turn your N4 off and go into fastboot (bootloader) mode (hold power button + Volume Up & Down all together)
Step 7: Type in the command prompt each step one at a time and wait for it to complete (obviously, don't enter the quotation marks):
"fastboot flash bootloader bootloader-mako-makoz30d.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img"
"fastboot reboot-bootloader"
"fastboot update image-occam-ktu84l.zip"
Step 8: At this point, your N4 will reboot. This will take some time as your apps are re-initialized, but it should be clear what's going on.
Step 9: You will now have 4.4.3. You will be unrooted and have stock recovery. If you want, you can stop here.
If you want to install the TWRP custom recovery and regain root:
Step 10: Download the new version of SuperSU onto the N4 from here: http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip
Step 11: Download TWRP onto your PC in C:\N4Update from here: http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.7.0.0-mako.img
Step 12: Boot N4 back into fastboot (bootloader) mode while connected to the PC.
Step 13: With the command prompt from Step 4 above, type "fastboot flash recovery openrecovery-twrp-2.7.0.0-mako.img"
Step 14: Boot from the bootloader into Recovery by pressing volume up to display "Recovery" and then the power button to select.
Step 15: Use TWRP to install the zip (SuperSU) file from Step 10 to regain root.
Step 16: Reboot system.
You should now have a rooted system, with all of your old apps and data (except for system apps, which need to be reinstalled), and the latest TWRP custom recovery.
Don't wanna sound rude, but is there point in creating another how-to thread, along the other threads which some(link) are even mentioned in sticky roll-up threads? Plus it's 99% copy/paste, which you even mention so that's nice from you.
It's nice that someone have will to write(or even copy/paste/edit) tutorials, but by having more threads help is harder to find(search).
Just my humble opinion and experience
Also you can jsut remove the recovery img from the update package to keep your custom recovery
well I for one appreciate you posting this as now I don't have to search all over gods creation to find the old thread
Nevermind
i did all steps... but im spammed google now launcher has stopped
will factory reset help?
Night5talker said:
i did all steps... but im spammed google now launcher has stopped
will factory reset help?
Click to expand...
Click to collapse
Factory reset seems extreme. How about just uninstalling and reinstalling the launcher? (I assume the stock launcher still works.)
NYZack said:
Factory reset seems extreme. How about just uninstalling and reinstalling the launcher? (I assume the stock launcher still works.)
Click to expand...
Click to collapse
i did factory reset but apps did left on my phone storage and when i turned it on google play started to download it everything again
ps couldnt do anything it was poping right back up wheni press ok even if i go to another launcher
Night5talker said:
i did factory reset but apps did left on my phone storage and when i turned it on google play started to download it everything again
ps couldnt do anything it was poping right back up wheni press ok even if i go to another launcher
Click to expand...
Click to collapse
Well, sorry, don't quite understand: you could always just uninstall the Google Now launcher, make sure everything else is working, and then reinstall it once you confirm there's no other problem.
Anyone could just mention the procedure for doing same thing but through Wug toolkit.
In general I prefer to avoid fastboot commands and flash everything though pc.
Unleashed by my Nexus 4
No need to do all these steps (flashboot). They included scripts that will run all things
On Windows you can just run "flash-all.bat" or on Unix "flash-all.sh".
DarsVaeda said:
No need to do all these steps (flashboot). They included scripts that will run all things
On Windows you can just run "flash-all.bat" or on Unix "flash-all.sh".
Click to expand...
Click to collapse
Yeah but edit it with notepad and remove the -w flag to disable the wipe also remove the recovery.img from the zip to keep the custom recovery !
mashedbymachines said:
Yeah but edit it with notepad and remove the -w flag to disable the wipe also remove the recovery.img from the zip to keep the custom recovery !
Click to expand...
Click to collapse
Yeah, this is the key point - if that -w flag is not removed, you will lose all apps/data. One of the reasons I put this up is that I think the step-by-step method is interesting, instructive (you can see what's actually happening), not much more time-consuming than running the automated script, and lets you have more granular control.
(And I apologize if it's littering the forum and semi-plagiarism, but I thought a very detailed, confirmed step-by-step guide with up-to-date precise download links might be useful to people who haven't gone through the process before.)
What the ....
So I edited my flash-all.bat and removed the -w
It looks like this:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-occam-ktu84l.zip
echo Press any key to exit...
pause >nul
Click to expand...
Click to collapse
And yet my phone was wiped.... sigh
** Update **
Nevermind, it was Notepad++ that screwed me over. The changes to the bat file was not written to the file, only kept in Notepad++'s temporary memory. ****ing bull**** feature.
Erroneus said:
What the ....
So I edited my flash-all.bat and removed the -w
It looks like this:
And yet my phone was wiped.... sigh
** Update **
Nevermind, it was Notepad++ that screwed me over. The changes to the bat file was not written to the file, only kept in Notepad++'s temporary memory. ****ing bull**** feature.
Click to expand...
Click to collapse
so in order to run this comand you only need to unzip the tar(?) file downloaded and then you are done, you don't have to unzip the actual factory image, correct?
fdg59 said:
so in order to run this comand you only need to unzip the tar(?) file downloaded and then you are done, you don't have to unzip the actual factory image, correct?
Click to expand...
Click to collapse
Actually, you have to run the unzip program twice:
For example, when updating to Android version 4.4.4 (Yes, a new version has already been released since this post):
Here is the downloaded file
occam-ktu84p-factory-b6ac3ad6.tar
Unzipping it will give you this:
occam-ktu84p-factory-b6ac3ad6
And unzipping that one more time will give you the directory "occam-ktu84p" containing the following files:
bootloader-mako-makoz30d.img
flash-all.bat
flash-all.sh
flash-base.sh
image-occam-ktu84p.zip
radio-mako-m9615a-cefwmazm-2.0.1701.03.img
WARNING: As was mentioned many times, remove the -w from the following line in the flash-all.bat file unless you intend to wipe your phone clean. I don't understand the issue with Notepad++ noted in a previous post, as you have to hit "save" like any other program (It is the program that I use as well).
fastboot -w update image-occam-ktu84p.zip
If what you were really asking is whether you need to unzip the file image-occam-ktu84p.zip.......The answer is no.
ah ah yes 4.4.4, that's why i am asking, because i always used to unzip everything and the flash items individually using fastboot which i always liked. The problem however was that my nexus 4 has 16gb and after flashing and wiping everything clean the memory showed up at 8gb so i had to factory reset through stock recovery which i didn't enjoy as much. thanks for all the help!

Recovery Mode/Boot Screen Loop

Hi all,
I have an HTC One M8. I bought it used and run a AT&T sim on Straight Talk. Previous owner had rooted it. I was trying to get the 4.4 updates and Sense 6.0.
The phone was already running HD Revolution 12.1 and Android 4.2.2 with TeamWin Recovery Partition v2.5.0.0
I downloaded and installed Android_Revolution_HD-One_71.1.zip.
I've run it several ways:
1. First w/o wiping from TWRP. (Factory reset settings)
2. Installed w/o "Wiping Userdata Partition" and then tried "Wiping Userdata Partition" from the HD Revolution installer.
3. SuperUser by Koush checked.
4. Stops at setting permissions "set_metsdata_recusrsive: some changes failed."
5. Finish
6, Zip Install details say "no MD5 file found".
7. Reboot System and it tells me "Root permissions appear to be lost. Fix root permissions now?" Yes....
Then reboots into white Bootloader screen. Anything selected here takes me to the Recovery page. Anything selected from the REBOOT menu in TWRP takes me to the Bootloader screen.
When this is done it reboots into the white bootloader screen. Any option I pick there takes me to the TWRP recovery.
I'm stumped. Any help /bread crumbs would be appreciated.
Bootloader shows:
**TAMPERED**
**UNLOCKED **
M7_UL pvt ship s-on rh
HBOOT-1.44.0000
RADIO-4A.14.3250.15
OPENDSP-v26.120.274.0202
eMMC-BOOT
May 3 2013, 20:01:28-1
Thanks
TJB
fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.
TWRP 2.6
BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Click to expand...
Click to collapse
I'm actually trying to mount the phone so I can see it from the PC update the TWRP. I downloaded openrecovery-twrp-2.7.1.1-m7.img but can't see how to load it to the phone.
PC sees the phone from Device Manager as a Disk Drive but it doesn't show up as a drive under My Computer.
I have Minimal ADB and Fastboot. Am I on the right track?
TJB
BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.
Click to expand...
Click to collapse
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB
teebright said:
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB
Click to expand...
Click to collapse
You cannot install like that, they have to be flashed via bootloader.
Do you have ABD installed on your PC?
If not you have two options.
OPTION 1
This guide for Windows 7 machine, this is the quickest way IMHO
Download the adb files for your respective PC from here : http://developer.android.com/sdk/index.html
Once you have downloaded the correct one for your PC (i.e. 32 or 64bit) you will be left with a zip FOLDER named something like this adt-bundle-windows-x86_64-20130522.zip (this is for 64 bit machine), Unzip it somewhere on your pc
Locate the unzipped folder and you should have/see the following inside
• Eclipse
• Sdk
• SDFK manager .exe
Open up the sdk folder and you will find 6 folders inside, cut the 'platform-tools’ folder , then double click my computer and then enter the C: drive of your PC. Paste this folder here in the C: drive and rename it Andriod-adb.
Then right mouse click my computer and go properties, then go and click Advance system settings located on left hand side this will bring up system properties box, click the Environment Variables… tab (it will open further details) and locate the Environment Variables list scroll down until you find path, highlight this then click edit.
Click mouse in here and scroll right to the end after the last entry
Type the following ;C:\Android-adb (noting only adding the first ; if not already there), if it is already there just type C:\Android-adb. Then hit Ok then OK again and your ADB should now be successfully setup.
To test this
From the windows start button, and in the search programs and files box type cmd and enter, this should bring up a command window.
Plug in your device and type adb devices, you should see it locate your phone
OPTION 2
Or try this, extract the attached file to your desk. place your recovery img in here and in a blank spot here hold the shift key down and right mouse click this should bring up list allowing you to "open command prompt here" then follow instructions below..View attachment 2850273
------------------------------------------------------------------------------------------------------------------------------------------------------
Once you have ADB working via either of the above sorted from a
1. Command prompt you should be able to type adb reboot boatloader, if you phone reboots into bootloader go to next step
2. Place the recovery image "openrecovery-twrp-2.7.1.1-m7.img " in the same adb folder as downloaded in option 2
3. Open a command prompt from within this folder and then type fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
4. Once sent it should com back to prompt
5. Type fastboot erase cache, then when completed type fastboot reboot
Good luck
fixed!
I fixed it! Per the recommendation I was trying to upgrade TWRP to 2.6.3.3.
I plugged in the phone to the PC via USB and made sure the phone is in FASTBOOT USB mode from the bootloader menu.
I installed "Minimal ADB and Fastboot" on the PC. Running that from the command line (cmd.exe) you type "fastboot flash recovery " then drag the file in. (watch the youtube video "How to install TWRP recovery on the HTC One M8" by ROOTJUNKIE-it will make more sense). In my case it was the 2.6.3 TWRP.img file. That pushes the update to the phone. I already had the HD 71.1 zip on the phone. I installed that via the TWRP install and from there it booted up normally. Had to setup the phone again but my music/pics were still there. Thanks all for the help!

Update Nexus 7 to 5.0 from 4.4.4 (root + unlocked bootloader) KEEP DATA

This is a "re-tread" of a post I previously made, taking an account of the steps I took to successfully update my Nexus 7 from 4.4.4 to 5.0. Note: This is for an unlocked bootloader, if you don't have an unlocked bootloader you will lose your data; consider TiBackup.
My Nexus 7 [WiFi] was rooted on 4.4.4, unlocked bootloader, but stock rom, stock system (as far as I remember). I couldn't find a walkthrough so I'll make one with my experience. This worked for me on my Mac, I hope this helps you.
In the end I didn't lose any data, still have unlocked bootloader and rooted with CWM Recovery & SuperSU (you can replace with TWRP recovery or CWM Touch if desired)
Directions ("./" = file path to platform-tools folder, if you 'cd' to that location the "./" will pull that location in the terminal)
1. You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html.
2. UNZIP and you will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
3. Download the factory images 4.4 (KRT16S) (4.4 required, see HERE, Google broke its own bootloader) and 5.0 (LRX21P) for your Nexus 7: https://developers.google.com/android/nexus/images#nakasi (WARNING: Download the correct images for YOUR device, Nexus 7 Wi-Fi vs Mobile)
4. Unzip the 4.4 image file you downloaded and copy "bootloader-grouper-4.23.img" (img name depends on your build) to your "platform-tools" folder (where adb and fastboot are). (WARNING: the bootloader image in 5.0 is broken see HERE)
5. Unzip the 5.0 image file you downloaded and copy all content, except for "bootloader-grouper-4.23.img," to your "platform-tools" folder (where adb and fastboot are).
6. Plug your Nexus 7 into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate "Developer Options" menu where you will be able to activate "USB debugging")
7. Open terminal and "cd" to the platform-tools folder
8. Verify ADB is working type "./adb devices"
9. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
10. Type:
"./fastboot flash bootloader ./bootloader-grouper-4.23.img" (img name depends on your build)
11. If you have "WiFi Only" skip to step 12; for Mobile flash radio type:
"./fastboot reboot-bootloader"
"./fastboot flash radio ./radio-XXXXXXXX.img" (img name depends on your build)
12. Type:
"./fastboot reboot-bootloader"
"./fastboot update ./image-nakasi-lrx21p.zip" (zip name depends on your build)
It will then reboot (takes a while, 5-10 minutes on boot animation, then it must update App info, another 5-10 miuntes) and then you will be in Android 5.0 with all your data preserved.
Then if you want a custom recovery:
1. On your computer, download CWM, CWM Touch, or TWRP recovery from here: CWM Dwnld or TWRP Dwnld (WARNING: Download the correct image for YOUR device, Nexus 7 WiFi vs Mobile)
2. Place the image file you downloaded in your "platform-tools" folder (where adb and fastboot are)
3. Connect your Nexus 7 (debug mode) and put it in fastboot mode (step 9 above): type in terminal "./adb reboot-bootloader"
4. In the terminal type:
"./fastboot flash recovery ./FILENAME.img" (replace FILENAME.img by the file name of the CWM/TWRP file you just downloaded)
5. Verify Recovery - Shut down your device and boot it into recovery mode (Once off, push vol- and power together). Choose recovery mode with vol-, then power to select (Note: if you get an Android on his back you still have stock recovery, retry Steps 1-4. I flashed CWM, CWM Touch. and TWRP with no success, plugged my cable into a different USB port and got it first try; try different cables and ports)
Then if you want a root:
Note: If you don't have an unlocked bootloader you will lose data. Already unlocked should be fine, when you boot there should be an open lock at the bottom of the screen below the Google logo. On PC WugFresh Nexus Root Toolkit might be your best option, for me on Mac it is not available so this is what I did.
1. On your computer, download CF-Auto-Root from here: Auto Root Dwnld (WARNING: Download the correct image for YOUR device, Nexus 7 WiFi vs Mobile)
2. Unzip the CF-Auto-Root file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are)
3. Connect your Nexus 7 (debug mode) and put it in fastboot mode (step 9 above): type in terminal "./adb reboot-bootloader"
4. Type: (Note: Step 4 commands need to be run as Admin)
"chmod +x root-mac.sh"
"ls -al"
"./root-mac.sh"
5. Follow on-screen prompt and type your Mac User Account password and ENTER
6. Let the phone go through its thing (Red Android screen), it will reboot when complete.
That is it!
Thanks to Phil Tech: http://youtu.be/IPg_FGbeyq0
Thanks to jipi: http://forum.xda-developers.com/showthread.php?t=2377691
Good luck and happy flashing.
Thanks for the effort.
Thanks ! I did that, more or less adapted. The result was just awefully slow, so I had to do a wipe to start with a clean slate.
Android, the new Windows: reinstall every 6 months....
I've followed the procedure on w8.1 64bit.
All went well but I lost adb after 5.0 finally booted. So I could not install root through NRT (1.9.8).
Adb mode was recognised in windows device manager but adb commands failed with no device found.
Suprisingly fastboot was working.
The solution was to uninstall NRT and adb drivers and reinstall them.
Great guide!!
Followed the steps to the 'T' and I've got Lollipop on my Nexus 7 Wi-Fi.
If the Bootloader is already on 4.23 then Step 10 can be skipped, as I did.
dg170775 said:
Great guide!!
Followed the steps to the 'T' and I've got Lollipop on my Nexus 7 Wi-Fi.
If the Bootloader is already on 4.23 then Step 10 can be skipped, as I did.
Click to expand...
Click to collapse
True, I was already on 4.23, but still flashed it anyways. Thanks for the input.

Categories

Resources