Related
Nexus 7 was rooted,unlocked bootloader and was running paranoid anroid 3.90+ i think . i plugged it into the computer to get a new rom using nexus root toolkit v1.7.2. i was asked to update a few things, so i clicked yes. i then tried to flash stock + unroot and chose 4.3 cause i wanted to try the new OS. but i guess something happened because when i turned my nexus 7 back on i was stuck on the load screen (GOOGLE image with a unlocked lock) i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side. when trying to flash stock +unroot using NRT i get up to the sending "bootloader" part and my nexus 7 just freezes, how do i fix this. please and thanks
download the factory image from the google factory image and extract the archive.
try flashing the bootloader manualy with fastboot.
locate your fastboot binary and copy the bootloader image to that directory.
open a commandline in that directory and type
fastboot flash bootloader name-of-bootloader.img
after that you can try to flash the whole factory image with the flash-all.sh script.
Simple
dieselmonkeyy said:
i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side.
Click to expand...
Click to collapse
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
MlucianoEze said:
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
Click to expand...
Click to collapse
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
You have to be in the folder with fastboot inside else those commands will not work.
It will be easier if you put the images extracted from the zip into the zip together with the fastboot program.
If you don't understand yet I'll try to be more specific.
Sent from my Nexus 7 using xda app-developers app
dieselmonkeyy said:
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
Click to expand...
Click to collapse
It can be intimidating... and the so-called tool-kits don't help you learn
I assume you are using Windows.
follow the unzip instructions from the previous poster. (not quoted here). note the directory.
find the directory containing your android tools... ADB.exe and FASTBOOT.exe.
transfer your unzipped files to this directory. Open your CMD prompt window and change to this directory if necessary.
plug in your Nexus.
type fastboot device at the prompt. MAKE SURE YOUR NEXUS 7 is listed (serial number)
proceed with the complete instructions from the previous poster.
that should do it.
YES!!!
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
dieselmonkeyy said:
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
Click to expand...
Click to collapse
I'm glad the problem is solved. Do not forget to click the THANKS button.
Sent from my Nexus 7 using xda app-developers app
Hello. My brother's Nex 7 is also has this issue. I cannot follow any of the steps as it gets stuck on erasing any of the partitions. I tried erasing those partitions in any order and they still get stuck. His device was stock and bootloader locked too. When I try to unlock the bootloader, it gets stuck as well at the erasing userdata part. I suspect a bad memory chip. Anyone else experience this?
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
jophisdrazin said:
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
Click to expand...
Click to collapse
Send your device for repair. My brother did so. My suspicions were correct. A faulty chip. They replaced the whole board, according to my brother.
Sent from my Nexus 7 using Tapatalk
Hi there,
I think I screwed in such a fashioned manner that I did not spot any spot to better expose my issue.
I run a Nexus 4 root which used to run fine with 4.3.
I did ota to Nexus 4.4 failure.
Then I did Efrant guide (without step 10) to go 4.4, it worked.
fastboot devices
fastboot reboot-bootloader
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 flash system system44.img
fastboot flash boot boot44.img
fastboot flash recovery recovery44.img
fastboot format cache
fastboot reboot
I had really bad experience with kitkat. No notification, sms history gone, home virtual button not working (only blipping), same for the top right notification menu.
Well I thought going to 4.3 would be best.
I did 4.3 through the same steps with different archives and boot loop at the X.
Then I tried a 4.2.2 but I did a huge mistake, I did it with Nexus 7 files. After sweating a bit I got it back in fastboot mode.
Then I tried 4.3 occam and 4.4 occam. Bootloop, old style and new one.
Now I can try 4.2.2 or 4.4 with fastboot flash userdata userdata.img
Any clue?
Edit: From Efrants:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
I can go to the red exclamation mark.
Than all the combinations I do just reboot me. What is the trick? Power on then volume up? Power on and volume up at the same time? How long should I press?
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I get the idea. By flashing the ROM of your choice what do you mean, flashing an OTA zip? I know how tosideload, just trying to understand what to flash.
I am about to try to flash a recovery (twrp) to wipe cache.
I tried and added system and boot.
/!\ fastboot erase system -w Erase all userdata I wanted to do that as a last option... Well now it is done...
The phone is now properly booting a 4.2.2 I will see tonight if I can get it to 4.3 or 4.4
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
demkantor said:
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well thanks for your help.
I think that my first install of 4.4 was messy. I really suspect that I installed bad radio and or bootloader. Thank you google for giving same name to different versions. Or may be I got some corrupted stuff on userdata?
When I went back to 4.3 I dont know what went wrong, maybe only that cache issue?
Then messing with the nakasi img (call me stupid) could not do any good.
I took too much confidence in messing the previous upgrades and recovering without loosing personnal data...
Now I have a fresh start to think about it...
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
omairanwar said:
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery recovery.img
reboot to recovery
flash rom of choice
There are many guides on rooting and fastboot, i would suggest staying away from any toolkit
as if you would like to learn, you wont from a toolkit.
the above take minuets and is far from a difficult task, its a nexus, its meant to be easy.
peek your nose around the forum a bit, you have any issues or are unsure just ask and id be glad to help
Hi guys,
In front of me, I have my friend's very stubborn LG Nexus 4. It's about 7 months old and a month ago, he dropped it and cracked the screen's glass (and the case's glass back as well). The phone still worked fine for a few weeks after that after that, but the touchscreen was not always responding correctly. He decided to give it to a service center for repair, but they returned it in a few days claiming there's a bootloop and they won't repair it (even if he paid) since the phone wasn't purchased in the same country. (Such BS, isn't it?)
An easy thing to fix, I thought, after fixing all sorts of bootloops on my SGT, SGS1 and my other friend's SGS2. Turns out, it's anything but.
Regardless of whether I flash stock following this guide or CM11 following the CM wiki, the phone is stuck on boot animation. 4 swirling colored balls for stock or an arrow rotating aroud Cid in case of CM11.
I have tried both stock recovery and CWM. I have tried wiping cache, data, Dalvik cache, any combination of only one or two or all three, tried waiting for an hour on first boot (someone suggested the first boot can take up to 15 minutes... find that hard to believe since even my sluggish SGS1 will manage in 3 minutes tops after a flash, but still tried) - all in vain. All I get is the screen's backlight level suddenly jumping up about 5 minutes into the boot process, as if the "Welcome to Android!" menu is about to appear - but it's still bootlooping until the battery runs out. (It gets quite warm too.)
TL;DR Nexus 4 flashes successfully with both stock 4.4.2 and CM11 but bootloops no matter what.
What can I do at this point to troubleshoot it? I'm out of ideas.
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As I said, I've already tried CWM, custom ROM (CM 11 - which required rooting, which I did) and followed the guide I linked for flashing the latest stock ROM I got from Google. The only thing I haven't tried is the fastboot erase commands - thanks for suggesting that, I will try them ASAP before trying to flash stock again though I don't have much hope left
Give it a shot, if you do everything in this order you will be good if its a software issue, if it doesn't work than possibly hardware
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hi Guys...
My nexus 4 Stocked on logo last friday, I try to recovery, wipe cache, and nothing.
So I learn that some devices of Nexus 4 after update to 4.4 are having this problem.
By the way I try to flashtool on a 4.3 version, the system was installed, but I am still stocked on logo...
Anyone have any Idea, how I can fix this?
I have no access to adb, only by flashtool
here are the way that I installed the old stock version:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader D:\Nexus\SDK\android-sdk-windows\platform-tools\bootloader-mako-makoz20i.img
fastboot reboot botloader
fastboot flash radio D:\Nexus\SDK\android-sdk-windows\platform-tools\radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot bootloader
fastboot -w update D:\Nexus\SDK\android-sdk-windows\platform-tools\image-occam-jwr66y.zip
Thanks btw
Have you done a factory reset in the stock recovery?
Sent from my Nexus 5 using XDA Free mobile app
I tried to wipe cache and delete all user data, but nothing works.
I read on net that I have to be pressing the volume(-) button on google animation to make a factory reset, this never worked for me....
I was thinking in install a custom firmware to try to fix this...
Do I have to hcange the bootloader, or a stock bootloader will be enough...
for example I wanna try this:
[ROM] NEXUS 5 PORT 4.4.2 KOT49H odexed 10/12/2013
http://forum.xda-developers.com/nexus-4/development/rom-nexus-5-port-4-4-2-kot49h-odexed-10-t2507021
But the problem that as my nexus are not working I have no access to adb commands, so how I can fix that?
Just by now i was able to sideload to flash my phone
So I tried a old 4.2.2 google version.
But I have a failure:
" Signature verification failed"
Why this failure happens if I am using a oficial stock from google?
Dark_Hyoga said:
Just by now i was able to sideload to flash my phone
So I tried a old 4.2.2 google version.
But I have a failure:
" Signature verification failed"
Why this failure happens if I am using a oficial stock from google?
Click to expand...
Click to collapse
Are you trying to flash a rom in the stock recovery? It won't work, you need a custom recovery. You can try to install a custom recovery by flashing an image file in fastboot. Or you can flash the factory image in fastboot and start all over. I'm not sure what stage your device is on right now
Sent from my Nexus 5 using XDA Free mobile app
I installed the most old version 4.2.2 of stock version by flash mode, I dont know why, but on versions 4.3 and 4.4 the precess always stops on some part of the flastool.. thats why I try the sideload.
4.2.2 was ok,
now I finally get over the stuck logo and can access the phone, but the phone its nothing find the network, But I am still working on it.
Now I understand Why......
I lost my IMEi on the process
*#06# shows no IMEI...
Now I have to find a tool to burn the IMEI again...
Anyone knows some, I just find the OCtoplus, but I have to buy....
There is one free?
I have a defective device and in preparing to return it, I locked the bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
I was afraid that the N9 was like the N5 & 7 with the "tamper" flag, but after some digging (and advice from others out here), I decided to restore the factory image to see if that would overwrite the image. Yes! No more big fat red "I unlocked my bootloader and may have voided my warranty" message.
I can't take credit for this, but I thought I would consolidate everything I was finding in the Q&A threads into one spot, so I put this little tutorial together. Thank you @Pilz, @jd1639 & @PhilDX for your various posts.
Step 1 - Prepare your system
[Windows]
Since your bootloader is unlocked, you probably already have ADB and fastboot, but if not, grab the SDK from here, unzip and add the "platform-tools" directory to your PATH statement
If your drivers are set up properly and your device has Android debugging enabled, connect USB and execute `adb devices` from a command prompt you should see your device listed
Download the factory image for "volantis" here
The image is double zipped, so unzip, untar, then unzip the image-volantis-lrx21q.zip file into the same directory that contains the bootloader*.img file
Step 2 - Unlock bootloader
If you locked your bootloader, unlock again:
Code:
adb reboot bootloader
fastboot oem unlock
Step 3 - Flash stock image
The flash-all.bat script is broken, so you have to do it by hand:
Open a command prompt
cd into the directory where you unzipped the factory image files
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase vendor
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Before rebooting, relock the bootloader:
Code:
fastboot oem lock
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Typo: fastboot oem unlock
hirndurst said:
Typo: fastboot oem unlock
Click to expand...
Click to collapse
Hahaha! Thanks.
always good to know! thanks!
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
DarthSudo said:
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
Click to expand...
Click to collapse
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Thanks for this thread. Great guide.
jd1639 said:
You could also use fastboot -w instead of the erases
Click to expand...
Click to collapse
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Thanks for this. I RMA'd my Nexus 9 and sending it back tomorrow
DarthSudo said:
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Click to expand...
Click to collapse
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
jd1639 said:
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You guys are all right. I looked back at some of my notes and I've flashed plenty of devices w/o formatting the other partitions first. Just userdata and cache. Thanks!
Hey guys, just wanted to thank you for the fixed "script". This is now my flash-stock.sh script I use whenever I need to flash a nexus device as the one delivered by google just doesn't work (reboot loop due to crashing apps on startup or "missing system.img").
Works perfect and I always like to not dirty but rather make a clean flash as it just reduces the number of possible faults .
Cheers
Creamy
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
bruce7373 said:
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
DarthSudo said:
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
Click to expand...
Click to collapse
Thx, that seems simple enough. But I made the initial system (stock) backup before I rooted. That's why I was thinking restoring that would work. I just wasn't sure about the recovery, whether the restore would put the stock recovery back or not.
Sent from my Nexus 6 using Tapatalk
DarthSudo said:
I have a defective device and in preparing to return it, I locked to bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Click to expand...
Click to collapse
Hi,
is there a way to get rid of that red message if your bootloader is locked and you cannot boot into OS?
Thanks!
EDIT* Nevermind
Hey. Sorry for reviving this thread.
I installed Remix OS on my N9 and (after discovering that performance is horrible, with ~80% RAM usage on idle) after a reboot, Remix OS won't get past it's boot splash. I am attempting to flash my device back to stock.
I never touched the bootloader (never did any 'fastboot flash bootloader ...' or anything), so it it still necessary to flash the bootloader image, or can I just flash the system.img, boot.img, vendor.img etc.?
The bootloader had never changed so there is no reason to flash it.
Sent from my Nexus 9 using XDA Free mobile app