Recommended method of unrooting - Nexus 4 Q&A, Help & Troubleshooting

What is the most common/recommended method of unrooting back to android jelly bean 4.2.2? There are so many ways/apps out there mskip, supersu ect..
thank you.

J. Clarkson said:
What is the most common/recommended method of unrooting back to android jelly bean 4.2.2? There are so many ways/apps out there mskip, supersu ect..
thank you.
Click to expand...
Click to collapse
Flashing the stock image with fastboot. http://forum.xda-developers.com/showthread.php?t=2010312

El Daddy said:
Flashing the stock image with fastboot. http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Any other alternatives this one looks far too complicated for me?

El Daddy said:
Flashing the stock image with fastboot. http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
As that's what you've recommended, I'll just try and do it that way. Hopefully this works, the person who is selling it to me says that his friend rooted the phone for him but he can't put it back for me but his offering a good price about £200. So I'll buy it and use this fastboot with the Factory Image "occam" for Nexus 4 4.2.2 (JDQ39) and hopfully, it should be back to normal again. I want the phones software to be just as it came out of the box. Will I need to do anything else?
Also, could you explain to me what the 'radio' is please? Never heard of this, I suppose the 'flash' is the image that I download from here https://developers.google.com/android/nexus/images, then what is 'radio?
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).

J. Clarkson said:
As that's what you've recommended, I'll just try and do it that way. Hopefully this works, the person who is selling it to me says that his friend rooted the phone for him but he can't put it back for me but his offering a good price about £200. So I'll buy it and use this fastboot with the Factory Image "occam" for Nexus 4 4.2.2 (JDQ39) and hopfully, it should be back to normal again. I want the phones software to be just as it came out of the box. Will I need to do anything else?
Also, could you explain to me what the 'radio' is please? Never heard of this, I suppose the 'flash' is the image that I download from here https://developers.google.com/android/nexus/images, then what is 'radio?
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
Click to expand...
Click to collapse
Once you unzip all the .zips in the factory image that you download you will see all the .IMG files. You will have system.img, radio.img, userdata.img and your boot.img and bootloader.img. Just do exactly what the instructions say and you will see that it is very easy. And its better to learn how to do this on your own and not use a tool kit.
Sent from my Nexus 4 using xda premium

lyall29 said:
Once you unzip all the .zips in the factory image that you download you will see all the .IMG files. You will have system.img, radio.img, userdata.img and your boot.img and bootloader.img. Just do exactly what the instructions say and you will see that it is very easy. And its better to learn how to do this on your own and not use a tool kit.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks mate, I'll try and take extra care and read n follow carefully, don't want to mess up here. After I have unrooted my Nexus 4, what else will I need to do to make as if it came out of the new box in terms of software ect..?

You will probably have to re install the google applications you would like; but besides those you will not need to install any additional software/apps.

beefynick said:
You will probably have to re install the google applications you would like; but besides those you will not need to install any additional software/apps.
Click to expand...
Click to collapse
Any idea which Google applications these maybe?
Chrome hopefully comes preinstalled after this unrooting process, I'm assuming the same with Google Now. It's just a case of unrooting and using the image from https://developers.google.com/android/nexus/images#occam then locking the bootloader?
Does anyone know why there is only 1 image for this phone? Usually you have many others for all networks, like T-Mobile UK ect..

After you flash the factory image, the phone will be just as it would be if you bought it from Google play. All of the Google apps will be on the phone at start up.
Once you are finished flashing the phone back to stock, reboot back into the bootloader and type, "fastboot oem lock" to re-lock the bootloader. There really is no reason to relock the bootloader. As long as you have the stock recovery, you will receive ota updates from Google.
Sent from my Nexus 4 using xda premium

lyall29 said:
After you flash the factory image, the phone will be just as it would be if you bought it from Google play. All of the Google apps will be on the phone at start up.
Once you are finished flashing the phone back to stock, reboot back into the bootloader and type, "fastboot oem lock" to re-lock the bootloader. There really is no reason to relock the bootloader. As long as you have the stock recovery, you will receive ota updates from Google.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
The last part confused me, as long as I have the 'stock recovery'? That means as long as I have flashed to the factory image downloaded from Google I will receive updates from Google?
Are there any advantages/disadvantages in performance and other things from locking/not locking the bootloader? I will be keeping the original software and won't be installing custom roms ect.. just installing updates for android from Google and that's it.

J. Clarkson said:
The last part confused me, as long as I have the 'stock recovery'? That means as long as I have flashed to the factory image downloaded from Google I will receive updates from Google?
Are there any advantages/disadvantages in performance and other things from locking/not locking the bootloader? I will be keeping the original software and won't be installing custom roms ect.. just installing updates for android from Google and that's it.
Click to expand...
Click to collapse
The only thing is that if one day you decide that you want to root, you will have to re-unlock the bootloader and this will wipe all data on your phone. But if you never plan to root then you can lock it
Sent from my Nexus 4 using xda premium

lyall29 said:
The only thing is that if one day you decide that you want to root, you will have to re-unlock the bootloader and this will wipe all data on your phone. But if you never plan to root then you can lock it
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
And when the phone comes brand new from Google, the bootloader comes locked, right? I think I might just lock it, I will need to wipe this phone anyway.

Yes, when you get the phone new the bootloader is locked. There will be no performance loss or gain from having the bootloader locked or unlocked.
Do you have fast boot and adb set up on your computer?
Sent from my Nexus 4 using xda premium

Related

help! about factory image ota

fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?
xIC-MACIx said:
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?
Click to expand...
Click to collapse
the development section. only dev question ? ok
sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
If you have the factory image, from Google (and nowhere else), just run the flash-all.bat file. You "may" have to unlock your bootloader prior to running it if you haven't already, and you'll need to have the device in fastboot mode prior to running the batch file too, but once those 2 simple tasks are done, the batch file takes care of the rest.
If your using a toolkit or some other method for flashing a factory image, I suggest stopping, and just doing the above.
This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...
craigacgomez said:
This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...
Click to expand...
Click to collapse
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english
lKBZl said:
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english
Click to expand...
Click to collapse
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium
dboftlp said:
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
There is... i've seen a post in google + from a guy that links you to a google page with n10 4.2.1 img.
sikagoon7 said:
Nexus 10 hasn't gotten the (JOP40D) images yet which means the only way to get the 4.2.1 update is to get an OTA. I think the OTA link is floating around AndroidPolice and AndroidCentral somewhere but you'll have to look. Whatever images for 4.2.1 on the Nexus 10 are fake because Google hasn't even released them yet.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium
dboftlp said:
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..
lKBZl said:
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..
Click to expand...
Click to collapse
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...
Watcher64 said:
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...
Click to expand...
Click to collapse
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?
lKBZl said:
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?
Click to expand...
Click to collapse
I don't see how that would matter, I used the aosp browser as well, and all I did was put stock recovery back on ..
hmmmm
Maybe you should just flash one of the updated stock/rooted roms in the dev section.

[Q] Software update using sideload and fastboot

Hi this is my first post and i hope its in the correct place and all
My nexus 7 (2013) is stuck in an android update circle where it constantly fails.
I tried to so the update to jss15q 4.3 using sideload where got so close but it said "signature verification failed" why could that be and can i stop it needing a verification?
I then tried to do it using fastboot and got so close again but got
:checking version-bootloader failed"
:device version-bootloader is "flo-03.05"
:Update requires "flo-03.14"
is there a way to correct either of them?
I am not rooted and i have downloaded the jss15q from developers google themselves (and i have debugging enabled)
Thanks for any help
Joe
Do you have the LTE version of the nexus or the WiFi version?
Guhrasoh said:
Do you have the LTE version of the nexus or the WiFi version?
Click to expand...
Click to collapse
I have the wifi only version.
joeyt90 said:
I have the wifi only version.
Click to expand...
Click to collapse
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2382051 to unlock the bootloader (your data on the device will be lost). Make sure you reboot the device at least once after unlocking and before you do anything else with it!
After that you can flash or boot TWRP and try to install the update with TWRP, if that fails you can flash a full factory image (the above thread contains all the information needed).
Guhrasoh said:
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2382051 to unlock the bootloader (your data on the device will be lost). Make sure you reboot the device at least once after unlocking and before you do anything else with it!
After that you can flash or boot TWRP and try to install the update with TWRP, if that fails you can flash a full factory image (the above thread contains all the information needed).
Click to expand...
Click to collapse
What exactaly do i have to do on that page to be able to continue the methods i am trying to use? If i just unlock the bootloader willi be able to update the boot loader from version-bootloader "flo-03.05" to "flo-03.14" then download jss14q using fast boot or is it not that easy?
Thanks again
P.S I dont want to root yet and Is it possible to just update the bootloader without unlock bootloader or do you have to unlock before you can update?
Thanks
If you want to use fastboot and the factory images you need to be unlocked.
Which file did you feed it when you "sideloaded" it? It needs to be the OTA file.
sfhub said:
If you want to use fastboot and the factory images you need to be unlocked.
Which file did you feed it when you "sideloaded" it? It needs to be the OTA file.
Click to expand...
Click to collapse
Hi I used the image from Google developers for nexus which was a zip file. Where could get the ota file from.
By unlocking do you mean just unlocking boot loader?
Thanks Joe
joeyt90 said:
Hi I used the image from Google developers for nexus which was a zip file. Where could get the ota file from.
By unlocking do you mean just unlocking boot loader?
Click to expand...
Click to collapse
Yes, bootloader must be unlocked to use the factory image restore.
As to the zip file, the zip file from the google developer site is a factory image. It is not meant to be sideloaded, only used in fastboot-style restores.
If you want to go the sideload route, what you want is the appropriate OTA zip (JWR66N->JSS15Q, JSS15J->JSS15Q), which you can get in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2415497
If you'd rather do the factory image to JSS15Q, then I suggest you unlock the bootloader and use this post:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Personally, I'd go the factory image restore route, it is less hassle.
sfhub said:
Yes, bootloader must be unlocked to use the factory image restore.
As to the zip file, the zip file from the google developer site is a factory image. It is not meant to be sideloaded, only used in fastboot-style restores.
If you want to go the sideload route, what you want is the appropriate OTA zip (JWR66N->JSS15Q, JSS15J->JSS15Q), which you can get in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2415497
If you'd rather do the factory image to JSS15Q, then I suggest you unlock the bootloader and use this post:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Personally, I'd go the factory image restore route, it is less hassle.
Click to expand...
Click to collapse
PERFECT!!!
Thank you so much to everyone who helped me on here my device is now running 4.3 version jss15q and what a difference from jwr66n.
I used the Unlock bootloader and then use factory images and it worked a treat!!
Again i cannot thank you enough i called google and the people who suplied my nexus and they both said they didnt know!!
WAHOO!!!:good::good::good::laugh::laugh:

Get softbrick with bootloop

Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.
nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.
tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.

Nexus 6P Factory Restore Help

Hey guys need some help on restoring my nexus 6p im on a custom rom with twrp and everything.
I was on Stock 7.1 January Security patch before i flashed.
Can i get some help on the codes and which stock zip to flash.
Thanks!
You need to give more info. Is your boatloader unlocked? Why do you need to go back to stock anyway is something wrong? Do you need to save any data on the phone?
Sent from my Nexus 6P using XDA-Developers Legacy app
Xavier102296 said:
Hey guys need some help on restoring my nexus 6p im on a custom rom with twrp and everything.
I was on Stock 7.1 January Security patch before i flashed.
Can i get some help on the codes and which stock zip to flash.
Thanks!
Click to expand...
Click to collapse
Hey... Just flash March factory image from Google:
https://developers.google.com/android/images
Flashing instructions are explained at the top of this page. Now scroll down till N6P images. There are two builds, one is Verizon specific. It's written anyway.
Good luck...
One of my questions was do you need to back up anything. If so make sure you understand flashing a factory image wipes the phone completely.
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
One of my questions was do you need to back up anything. If so make sure you understand flashing a factory image wipes the phone completely.
Click to expand...
Click to collapse
I plan on wiping Everything just need to get back to stock
Xavier102296 said:
Hey guys need some help on restoring my nexus 6p im on a custom rom with twrp and everything.
I was on Stock 7.1 January Security patch before i flashed.
Can i get some help on the codes and which stock zip to flash.
Thanks!
Click to expand...
Click to collapse
Easiest way You need to just download Nexus root toolkit to your computer plug in phone and let the toolkit do the work it will flash the proper files and reboot the phone
Do not Re- lock bootloader until you have flashed back to stock or you will brick it for good. Or don't lock the bootloader at all for that matter and yes save all files photos anything to PC..Or flags drive before you restore cause it will all vanish
Sent from my Nexus 6P using XDA-Developers Legacy app
androidddaaron said:
Easiest way You need to just download Nexus root toolkit to your computer plug in phone and let the toolkit do the work it will flash the proper files and reboot the phone
Do not Re- lock bootloader until you have flashed back to stock or you will brick it for good. Or don't lock the bootloader at all for that matter and yes save all files photos anything to PC..Or flags drive before you restore cause it will all vanish
Click to expand...
Click to collapse
Link?
Xavier102296 said:
I plan on wiping Everything just need to get back to stock
Click to expand...
Click to collapse
Just go to Google site, download the factory image, extract it and run the flash-all.
Done...
androidddaaron said:
Easiest way You need to just download Nexus root toolkit to your computer plug in phone and let the toolkit do the work it will flash the proper files and reboot the phone
Do not Re- lock bootloader until you have flashed back to stock or you will brick it for good. Or don't lock the bootloader at all for that matter and yes save all files photos anything to PC..Or flags drive before you restore cause it will all vanish
Click to expand...
Click to collapse
Hi... Why would someone install another program just to do what is done in one click?
I mean... Extract Google image, run flash-all.
Easiest way.

Nexus 7 2012 stuck in safe mode

When I restart Nexus 7 it always boot up to safe mode. Tablet first shows bootloader menu and when I choose to start, it boot in to safe mode. It looks like volume down button is always pressed on but it don't work - does nothing in bootloader menu, and in safe mode.
I don't use it for some days. I don't remember the tablet being flooded or hit. It just appears. First I thought that it was caused by some bug in LineageOS. I made factory reset, and when it does nothing I set u Android 5.1 again but that also didn't work.
Do you have any idea why this is happening?
You mean you are always booting into recovery when starting up the device? This may happen if there is no valid boot.img / system.img installed. How did you install the current system on your device? Do you have an unlocked bootloader? Do you have the latest bootloader (4.23) installed on your device?
AndDiSa said:
You mean you are always booting into recovery when starting up the device? This may happen if there is no valid boot.img / system.img installed. How did you install the current system on your device? Do you have an unlocked bootloader? Do you have the latest bootloader (4.23) installed on your device?
Click to expand...
Click to collapse
Last thing I did is option Flash Stock + Unroot in Nexus Root Toolkit.
Yes I have bootloader 4.23.
Sorry, but I don't know what the toolkit is doing and whether everything went as expected .. that's the disadvantage of using toolkits.
Best would be to learn how to install and to use fastboot and after that you can decide either to flash stock factory image again or to upgrade to one of the custom ROMs available for the Nexus 7.
Sent from my Nexus 7 using XDA Labs
AndDiSa said:
Sorry, but I don't know what the toolkit is doing and whether everything went as expected .. that's the disadvantage of using toolkits.
Best would be to learn how to install and to use fastboot and after that you can decide either to flash stock factory image again or to upgrade to one of the custom ROMs available for the Nexus 7.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
I think you don't understand me. Nexus Root Toolkit have nothing to do with this. It works 3 years with my Nexus 4 and 1 year with Nexus 7. This problem appeared long after installation of LineageOS.
Ok, I installed Android 5.0 manually and I still have this problem.
Did you notice any error messages while flashing the stock image? Did you do a factory reset after returning to stock?
I am still thinking that your bootloader is closed and you are not really flashing / changing the ROM, but flashing fails and you are remaining in the same state as before. Just as an idea ...
Sent from my Nexus 7 using XDA Labs
I would do one step at a time assuming fastboot and adb work. Search for adb minimal. Download stock zip to same directory. Run fastboot oem unlock. Unzip stock zip and try running flash-all.bat it flashes compatible bootloader and stock zip. If that doesn't work img files are inside stock zip and can be flashed separately.
Sent from my Nexus 6 using Tapatalk
Sorry for leaving you like that.
I took the risk and ordered flex cables with volume buttons. Now the tablet works fine. I'm sorry for the trouble.

Categories

Resources