Related
I want to root my N7 directly from Linux, but I don't want to replace recovery with CWM. I like CWM on my phone, but I understand it won't allow OTA stock upgrades which I expect will be important for a while on the N7.
I've already unlocked the bootloader, but I haven't seen any instructions for rooting from Linux without replacing the standard recovery with CWM.
Can't you just flash CWM, root, and then reflash stock recovery?
sray1 said:
... but I understand it won't allow OTA stock upgrades which I expect will be important for a while on the N7.
Click to expand...
Click to collapse
There won't be any OTA that is not quickly (if not before it is released) will be available is a flashable download on XDA and other forums.
You are not going to miss anything.
You can as already posted, reflash the stock recovery, but again, whats the point.
rohan32 said:
Can't you just flash CWM, root, and then reflash stock recovery?
Click to expand...
Click to collapse
Where would I find the stock recovery?
I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.
I am rooted.
TWRP recovery.
Hotspot mod.
I'm guessing updating would put my phone in a boot loop, right? What do I need to do first? Turn off the root and flash a stock recovery? Is that good enough?
ChrisFSU said:
I am rooted.
TWRP recovery.
Hotspot mod.
I'm guessing updating would put my phone in a boot loop, right? What do I need to do first? Turn off the root and flash a stock recovery? Is that good enough?
Click to expand...
Click to collapse
Yes, updating will boot loop. If you want the update then you may need to flash the stock ROM to get rid of the hotspot mod.
I have heard this update checks just about everything in the book.
But yes stock recovery, and no root for sure.
Sent from my LG-LS980 using Tapatalk
ChrisFSU said:
I am rooted.
TWRP recovery.
Hotspot mod.
I'm guessing updating would put my phone in a boot loop, right? What do I need to do first? Turn off the root and flash a stock recovery? Is that good enough?
Click to expand...
Click to collapse
Wrong section don't ask questions in dev forms.
Sent from my LG-LS980 using xda premium
ChrisFSU said:
I am rooted.
TWRP recovery.
Hotspot mod.
I'm guessing updating would put my phone in a boot loop, right? What do I need to do first? Turn off the root and flash a stock recovery? Is that good enough?
Click to expand...
Click to collapse
Im on the same boat but am gonna wait. Unless theres Spark in your area there not much point to do it. Theres lots of issues with the new ZVA update (on rooted and custom recovery phones) and im gonna wait for an easier fix than what is available. The current process is a bit too complicated and not worth it. Ill wait for a simple zip to flash or a totally custom ROM with ZVA already on it. But thats just me.
If you do it... update us on here.
Rename files in fota folder. Freeze the update app.
my phone is bootloader unlock, does it mean I can flash the third part recovery like TWRP, and use it?
MY guess yes..
Sent from my LT30p using Tapatalk
allen_ho said:
my phone is bootloader unlock, does it mean I can flash the third part recovery like TWRP, and use it?
Click to expand...
Click to collapse
TWRP will not work on the OTA, yet. However, there is a working CWM in the HD forum. I flashed it to my M and have zero issues with it.
RikRong said:
TWRP will not work on the OTA, yet. However, there is a working CWM in the HD forum. I flashed it to my M and have zero issues with it.
Click to expand...
Click to collapse
I flashed the CWM recovery too...it does boot to recovery
but it seems to be some problem with CM11 package, the assert check shows my device ID is empty so the recovery just abort the installation.
I want to flash CM11-m6 snapshot....any ideas?
falleny said:
I flashed the CWM recovery too...it does boot to recovery
but it seems to be some problem with CM11 package, the assert check shows my device ID is empty so the recovery just abort the installation.
I want to flash CM11-m6 snapshot....any ideas?
Click to expand...
Click to collapse
CM11 won't work if you've updated. Apparently, the boot loader is updated and the ROMs haven't been updated for it.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
CM11 won't work if you've updated. Apparently, the boot loader is updated and the ROMs haven't been updated for it.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Bad news...Looks like i will be stucked in full bloated stock rom for sometime...thank u
falleny said:
Bad news...Looks like i will be stucked in full bloated stock rom for sometime...thank u
Click to expand...
Click to collapse
You have an unlocked BL, just flash SU to get root, and delete/freeze apps. That's pretty much what I did and used Xposed on top of that.
I haven't tried it yet, buy couldn't you just rsd back to an earlier build then flash your custom ROM?
Sent from my XT907 using Tapatalk
I fastboot flash the lastest CWM recovery, but it didn't work for the CM 4.4.2 ROM, and twrp, it didn't work again. why? does the VFW rom change something?
allen_ho said:
I fastboot flash the lastest CWM recovery, but it didn't work for the CM 4.4.2 ROM, and twrp, it didn't work again. why? does the VFW rom change something?
Click to expand...
Click to collapse
None of the ROMs have been updated to work with the new recovery. Just give it time.
RikRong said:
None of the ROMs have been updated to work with the new recovery. Just give it time.
Click to expand...
Click to collapse
what's that mean?
do you mean the third part recovery didn't work cause the VFW rom?
allen_ho said:
what's that mean?
do you mean the third part recovery didn't work cause the VFW rom?
Click to expand...
Click to collapse
It means that none of the ROMs out right now will work with the new CWM. Also, quit trying flash TWRP. TWRP is not compatible with the new KK, yet.
Got it, many thanks
Root
My xt907 Has the OTA 4.4 update and an unlocked BL. I don't have a custom recovery installed anymore. Is it possible to flash SU or superuser and get root with fastboot. If so. Please help! Thanks. I'm ok with flashing CWN if need be. I just want root to install a Xposed and remove bloatware.
Ahoalton said:
My xt907 Has the OTA 4.4 update and an unlocked BL. I don't have a custom recovery installed anymore. Is it possible to flash SU or superuser and get root with fastboot. If so. Please help! Thanks. I'm ok with flashing CWN if need be. I just want root to install a Xposed and remove bloatware.
Click to expand...
Click to collapse
I'm pretty sure you can use fastboot/ADB to sideload zips, though I'm not super familiar with the commands so I wouldn't know how to explain it to you.
I am familiar enough with the commands, but I am unable to find the zips to flash. any help would be great.
Thanks,
Egg all over the face
I was one of the people who thought it would be cool to update to the OTA immediately without waiting and reading... I got the CWM recovery going and rooted stock 4.2.2 , but I really cant wait for TWRP to get updated so I can get back to my Rom, or really any supported Rom would be better then stock. I have only myself to blame.
Eclipse00 said:
I was one of the people who thought it would be cool to update to the OTA immediately without waiting and reading... I got the CWM recovery going and rooted stock 4.2.2 , but I really cant wait for TWRP to get updated so I can get back to my Rom, or really any supported Rom would be better then stock. I have only myself to blame.
Click to expand...
Click to collapse
Looks like the new TWRP is here, but still needs one tweak. Please follow this thread for updates.
http://forum.xda-developers.com/showthread.php?p=53189684
TWRP for KitKat Bootloader
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
Hey XDA,
My Nexus ha been a dream. Though I've hit a few bumps, I don't expect to waste money on other flagships again.
I don't need to be able to right this instant, but wiping cache is one of my regular troubleshooting tools. Upon troubleshooting an MMS issue I was having, I discovered my recovery wasn't working properly. Though I fixed the MMS issue by resetting APN settings, the recovery thing has been bothering me.
I am running stock and locked. I have done nothing to this phone to warrant it being my fault. The problem is simple (and a Google search indicated, common). When you get to Recovery, you get a droid on its back, a red exclamation mark and "NO COMMAND". Doesn't matter if you hold up and power, tap up, or get there from the bootloader. The recovery software is seemingly missing completely.
I have an extended warranty through the retailer I bought from, but the phone is otherwise fine, so this is a last resort.
My dilemma is that I want to use Android pay. My understanding is that even unlocking the bootloader breaks Android pay. Is this correct? If so, can one reliably reset the phones security trips to allow Android pay after flashing the recovery back on?
Thanks for the help.
No, unlocking the boot loader does not block Android Pay.
There is a systemless root method for the Nexus that allows you to use Android Pay while rooted, there are also a couple of ROMS that have it working currently as well.
celsian said:
No, unlocking the boot loader does not block Android Pay.
There is a systemless root method for the Nexus that allows you to use Android Pay while rooted, there are also a couple of ROMS that have it working currently as well.
Click to expand...
Click to collapse
Quite so? Can you provide links to the root method and mayhaps the roms? Does this mean I could slap TWRP on here with no consequence?
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Does this mean that I can't flash at least a stock recovery?
Download your system image, unzip it, unlock your bootloader and flash only the recovery.IMG in fastboot, then relock your bootloader again. Android Pay will work fine and your warranty won't be affected so long as you relock your bootloader
Arcaed said:
Does this mean that I can't flash at least a stock recovery?
Click to expand...
Click to collapse
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Sorry, but are you saying if I wanted to install twrp I would need a modified stock boot img?
The Stig 04 said:
Sorry, but are you saying if I wanted to install twrp I would need a modified stock boot img?
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
In that case, where do I get a full system flash?
Arcaed said:
In that case, where do I get a full system flash?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Sent from my Nexus 6P using Tapatalk
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
You beat me to it with #3. Unfortunately I'm at work and couldn't come back to this thread quickly enough.
toknitup420 said:
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Actually AP now works with systemless root again. I have AP working (yes actually making purchases), currently running the latest Chroma Rom with Supersu 2.61
Found the workaround in this thread.
I'm sure Google will patch it again though.
Arcaed said:
Quite so? Can you provide links to the root method and mayhaps the roms? Does this mean I could slap TWRP on here with no consequence?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=65188325
Heisenberg said:
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I've always been under the impression that the device will not boot with twrp installed unless you have DM verity checks removed. Has something changed with that.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
I've always been under the impression that the device will not boot with twrp installed unless you have DM verity checks removed. Has something changed with that.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It isn't necessary. I'm on my eighth Nexus 6P and I haven't flashed any modified boot.img prior to flashing TWRP.
83097markcynt said:
Actually AP now works with systemless root again. I have AP working (yes actually making purchases), currently running the latest Chroma Rom with Supersu 2.61
Found the workaround in this thread.
I'm sure Google will patch it again though.
Click to expand...
Click to collapse
I can second this. I have systemless root, and AP working, confirmed with purchases. Just a note, if you can successfully add a card, that means it has to contact your bank for approval, therefore it should confirm AP is working.