[Q] Nexus 4.. questions - Nexus 4 Q&A, Help & Troubleshooting

Hey I rooted and unlocked my nexus to try cyanogenmod... I don't want to keep it because my phone doesn't have a stable release and the experimental crashes very frequently.. I have a few questions -
How to flash return to stock android but rooted and unlocked?
Can a rooted and unlocked nexus do OTA updates? If not, how should I go about them?
Thanks,

U çan download and flash the stock rim available for ur device...
Whenever an update is available u can't update directly due to unlocking bootloader...
so u can get the update here in ur development thread easily...
Sent from my Xperia S using xda premium

Google nexus 4 factory images, then download them from Google. Unzip and flash each .img to its respective partition using fastboot.

http://forum.xda-developers.com/showthread.php?t=2010312
That will explain how to flash factory images. Do this and you'll return to stock.
Once you get back to stock you can boot into twrp 2.5.0.0. Personally I like to simply stick with stock recovery and only boot into custom recovery with fastboot when I need to flash something. I find that doing it while in front of my PC helps me to take my time and do things right versus keeping custom recovery on the device and trying to do things on the fly. But that's just me. Anyhow...boot into twrp and when you go to the reboot tab and try to reboot it will say that it sees your device is not rooted and will ask if you want the recovery to root for you. Done.
Also, once you flash all factory images you'll likely have to use the factory reset option through recovery before it will actually boot. If you don't you'll probably bootloop and you'll also likely lose half your memory. So flash the images and before you "fastboot reboot" you should fastboot boot recovery and factory reset using twrp and that will allow it to reboot properly and not get stuck in loop.
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 11:10 PM ---------- Previous post was at 11:01 PM ----------
happy3777 said:
U çan download and flash the stock rim available for ur device...
Whenever an update is available u can't update directly due to unlocking bootloader...
so u can get the update here in ur development thread easily...
Sent from my Xperia S using xda premium
Click to expand...
Click to collapse
Unlocked boot loader does not block ota in any way (at least not on nexus). If he is stock ROM with unlocked boot loader and stock recovery he will update just fine. Root could potentially be lost I suppose but that's hit or miss.
I typically keep stock recovery only and simply fastboot into a custom recovery if I need to so I'm not sure if you can OTA with a custom recovery but I don't think you can.
But point is that stock ROM stock recovery unlocked boot loader will update just fine.
Sent from my Nexus 4 using xda app-developers app

thos25 said:
http://forum.xda-developers.com/showthread.php?t=2010312
That will explain how to flash factory images. Do this and you'll return to stock.
Once you get back to stock you can boot into twrp 2.5.0.0. Personally I like to simply stick with stock recovery and only boot into custom recovery with fastboot when I need to flash something. I find that doing it while in front of my PC helps me to take my time and do things right versus keeping custom recovery on the device and trying to do things on the fly. But that's just me. Anyhow...boot into twrp and when you go to the reboot tab and try to reboot it will say that it sees your device is not rooted and will ask if you want the recovery to root for you. Done.
Also, once you flash all factory images you'll likely have to use the factory reset option through recovery before it will actually boot. If you don't you'll probably bootloop and you'll also likely lose half your memory. So flash the images and before you "fastboot reboot" you should fastboot boot recovery and factory reset using twrp and that will allow it to reboot properly and not get stuck in loop.
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 11:10 PM ---------- Previous post was at 11:01 PM ----------
Unlocked boot loader does not block ota in any way (at least not on nexus). If he is stock ROM with unlocked boot loader and stock recovery he will update just fine. Root could potentially be lost I suppose but that's hit or miss.
I typically keep stock recovery only and simply fastboot into a custom recovery if I need to so I'm not sure if you can OTA with a custom recovery but I don't think you can.
But point is that stock ROM stock recovery unlocked boot loader will update just fine.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This poster is correct. Unlocked bootloader blocks nothing. To get back to stock, download the stock image directly from Google: https://developers.google.com/android/nexus/images. YES you will lose root, however, will lose root when you update 4.2.1 to 4.2.2 or when we go 4.2.2 to 4.3. However, in the Play store is a neat little called OTA RootKeeper that allows you to "backup" your root access and after the OTA is done, it easily "restores" root. It works great!
OTA RootKeeper: https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en

thos25 said:
http://forum.xda-developers.com/showthread.php?t=2010312
That will explain how to flash factory images. Do this and you'll return to stock.
Once you get back to stock you can boot into twrp 2.5.0.0. Personally I like to simply stick with stock recovery and only boot into custom recovery with fastboot when I need to flash something. I find that doing it while in front of my PC helps me to take my time and do things right versus keeping custom recovery on the device and trying to do things on the fly. But that's just me. Anyhow...boot into twrp and when you go to the reboot tab and try to reboot it will say that it sees your device is not rooted and will ask if you want the recovery to root for you. Done.
Also, once you flash all factory images you'll likely have to use the factory reset option through recovery before it will actually boot. If you don't you'll probably bootloop and you'll also likely lose half your memory. So flash the images and before you "fastboot reboot" you should fastboot boot recovery and factory reset using twrp and that will allow it to reboot properly and not get stuck in loop.
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 11:10 PM ---------- Previous post was at 11:01 PM ----------
Unlocked boot loader does not block ota in any way (at least not on nexus). If he is stock ROM with unlocked boot loader and stock recovery he will update just fine. Root could potentially be lost I suppose but that's hit or miss.
I typically keep stock recovery only and simply fastboot into a custom recovery if I need to so I'm not sure if you can OTA with a custom recovery but I don't think you can.
But point is that stock ROM stock recovery unlocked boot loader will update just fine.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
But in my case Xperia S i had prob with OTA...
if i update on air it will go for infinity...
:laugh:

Related

hmmm, need help

Okay guys, this is another one of those unbrick threads. I have been installing roms and kernels quite a lot recently, but I recently came into a problem. I hit wipe sd card, and it wiped all of the roms, and apps from the device. I basically have nothing installed. I do have twrp, nexus root toolkit, and adb though, so what should I do? Thanks
Try returning to stock. That also happened to my friend who has TWRP. It seems like TWRP screws up a lot of peoples devices. He had an S2. He just returned to stock and reflashed CM10 and it was fine. Now he is a CWM user.
Sent from my SGH-T989 using xda premium
How would I re install those roms though, it even deleted the backups . I have adb but no fast boot
Adb push a rom.zip to /sdcard then install it from recovery
Sent from my Nexus 7
Don't I need fastboot for that?
Also left recovery and now the hardware keys don't work but adb still does, so I don't know if I can get back in to recovery
Download your stock ROM, and reflash it.
You will get a ton of thanks if you can walk me through it .
The keys probably don't work while in the bootloader because of the stupid bug, connect it via USB and it probably will. You can use adb while the device is booting up (or stuck halfway booting up) or you can use fast boot from the bootloader to bring it back to stock. Check the unbrick threads for instructions on how to do it.
Just get Wug's toolkit and click on the "Flash Stock And Unroot" Button.
---------- Post added at 04:46 PM ---------- Previous post was at 04:31 PM ----------
Just get Wug's toolkit and click on the "Flash Stock And Unroot" Button.
I'll try it thanks
Sent from my Galaxy Nexus using Tapatalk 2
Tried it, but at the end it said fastboot device not found. What should I do?
How should I go about using Odin ? Would it work? Thanks

4.3 Factory image with custom recovery?

I apologize for the noob question but I've never found myself in this particular situation...
I've decided to stick with the 4.3 JWR66V factory image while I wait for a working rooted version to be released or even an updated SuperSU or Superuser zip (that doesn't drain the battery or lose root with certain apps).
I used the factory image found HERE and followed the detailed instructions found HERE. I followed the instructions under section "D" vigorously which meant that I installed the stock recovery image as well. Everything is running as it should. However, I was curious if it was safe to flash TWRP 2.6.0.0 recovery through fastboot with my current setup. I'd like to use that recovery to wipe cache/dalvik and possibly fix permissions. However, I'm not sure if this will break something so I am hesitant to try it.
I have made sure the bootloader is unlocked. But I am curious if it's safe to flash and use TWRP while I am not rooted.
You can install recovery with no problem, root has nothing to do with it. however i think upon a reboot your recovery will be replaced with factory.
Interesting. I wonder why/how the system would flash back to stock recovery if I've pushed the TWRP recovery image over the factory image?
I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app
otariq said:
I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Without root would there be any functionality within TWRP that I shouldn't touch? Or does recovery functionality have no dependency on root?
What is there you wanna do? I just replaced stock with twrp so I can just flash the su zip when its out because I don't always have access to a PC. Also, Franco released his initial 4.3 kernel which I'm thinking about flashing.
When rebooting from twrp it'll ask if you wanna flash the su.apk because you don't have root I chose no because it wouldn't do anything for us right now without the binaries
Sent from my Nexus 4 using xda app-developers app
Good point. As of right now I guess I don't have a huge need for it. I'll just leave everything as is until a proper SuperSU is released. At which point I'll install the latest TWRP and root.
Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.
skinniezinho said:
Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.
Click to expand...
Click to collapse
No idea. I use a Mac and flash back to stock via Fastboot. You should just learn to do that anyway so you have a better sense of exactly what is going on and if something fails you'll know exactly which step is failing in order to correct it. Relying on a toolkit is like never taking the training wheels off your bike.

Recovery won't flash

I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.
OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.

Will custom recovery prevent ota updates?

First let me apologise if this is in the wrong section. I could not decide if this was the best place for it or q a&a. As the title sais. If i flash twrp will it prevent me from receiving ota updates from Google. I have an HTC sensation XE and if i flash a custom recovery i know from past experience that it prevents ota updates. This nexus 7 however is my first "Google" device you could call it and as such i do not know that.
Can any one inform me on this issue. Also if it will an ota cause loss of root on this nexus like it did on my smartphone or will it stay? If it is gone i suppose it will simply be a matter of using chainfires root tool again when it gets updated for it.
Thanks in advance.
Sent from my Nexus 7 using Tapatalk 4
Q&A would be the best place for the post, but I can offer some insight. Any time you flash a custom rom you will forfeit the option of an ota update from your carrier or Google. This doesn't affect your play store apps as they will update when needed. The information that gets sent to your carrier identifies it as being non-official software so only a few custom ROMs that are well maintained will point the ota updates to its own servers. If you wish to receive official ota updates you should perform a nandroid backup of your stock rom to have a restore point for when a new release comes out. Aside from that, you would have to flash everything back to stock (probably stock recovery too) in order to be seen by the carrier as an eligible device.
Sent from my SGH-I727 using Tapatalk 2
Who said anything about flashing a custom rom. I know i didn't. Sorry but that reply is no insight at all. I asked if flashing twrp a custom recovery would prevent ota updates like on my phone. Nothing else. I did not say one word about custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Ch3vr0n said:
Who said anything about flashing a custom rom. I know i didn't. Sorry but that reply is no insight at all. I asked if flashing twrp a custom recovery would prevent ota updates like on my phone. Nothing else. I did not say one word about custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
If you install a custom recovery like twrp, you wouldn't be able to install an OTA from Google. You need stock recovery for OTAs.
now that's more of an answer i was hoping to get, can some other users confirm this? I suppose i'll lose root aswell but i imagine that would simply be a case of waiting for an updated root tool then. Say i do flash a recovery, does google have a page where you can manually download the update files to flash? But that would probably cause a lose of root as well but the custom recovery would remain intact, correct?
Ch3vr0n said:
now that's more of an answer i was hoping to get, can some other users confirm this? I suppose i'll lose root aswell but i imagine that would simply be a case of waiting for an updated root tool then. Say i do flash a recovery, does google have a page where you can manually download the update files to flash? But that would probably cause a lose of root as well but the custom recovery would remain intact, correct?
Click to expand...
Click to collapse
This has already been brought up many times e.g.
http://forum.xda-developers.com/showthread.php?t=2404833
I thought as much. I'll stick with stock recovery then until i need a custom recovery for some specific reason. For now root access is enough. And if an ota comes out and i lose recovery well I'll just wait for chainfire to update his root tool
i received the jss15j -> jsl36c update on my razorg with twrp recovery installed.
after the update stock recovery was back.
you can boot every recovery or kernel image without flashing it using fastboot:
fastboot boot nameofrecovery.img
I think you can have your cake and eat it too.
Instead of "fastboot flash recovery recovery.img" to flash the custom recovery, you can "fastboot boot recovery.img".
Every time you want the custom recovery, use fastboot boot command on the pc. This way you can make nandroid backups and flash superSU to root. But, you will not be replacing the stock recovery.
I did this on my HTC phone, when I wanted to remain stock, rooted, yet able to receive OTA updates.
HowardZ said:
I think you can have your cake and eat it too.
Instead of "fastboot flash recovery recovery.img" to flash the custom recovery, you can "fastboot boot recovery.img".
Every time you want the custom recovery, use fastboot boot command on the pc. This way you can make nandroid backups and flash superSU to root. But, you will not be replacing the stock recovery.
I did this on my HTC phone, when I wanted to remain stock, rooted, yet able to receive OTA updates.
Click to expand...
Click to collapse
Good to know.
Sent from my Nexus 7 using Tapatalk 4
I've taken OTAs using custom recoveries before on any number of devices. If you're not careful you can lose your recovery and have to reflash again, but sometimes you don't even lose that.
Well, there might be complications installing an OTA with custom recovery if it comes with a newer bootloader version/radio. Sometimes it works, but there were also reported problems.
Well i just had an ota update to jss15r and lost root as kinda expected. Now ill just have to find out if rerunning the root tool will be enough. Since it is already OEM unlocked i suppose i can simply modify that bat file and remove that line and run it again?

First person to brick 6P? Please Help!

Flashed TWRP. Went to reboot, and it asked me to flash Super SU to root.
So I did, now it's stuck in a boot loop.
Also when starting the phone I get a message saying 'your device is corrupt'.
Any ideas?
Can you still get into bootloader?
As always , not bricked , not even close .
Your bootloader is fine , flash the factory image
Sent from my Nexus 6P using Tapatalk
i did this same thing, i cant copy the stock rom over in twrp so i am stuck. guess i got a bunch more reading to do, i am trying to figure out how to flash the rom through adb.
edit: i used the skipsoft toolkit and reverted back to stock everything went smoothly.
Go to twrp format user data by wipe data and user data. Reboot recovery and install a kernel with out force encrypted or install the new twrp and should be OK
Sent from my Nexus 6P using XDA Free mobile app
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
Also might want need to flash a new ROM or fastboot the OEM tgz. There are couple fixed your not screwed!
Sent from my Nexus 6P using XDA Free mobile app
If you can't adb in recovery is a driver issue. Download the koush version and uninstall the Google drivers. It will work.

Categories

Resources