This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
adambombz said:
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
Click to expand...
Click to collapse
It's not rooted out-of-the-box. Google doesn't allow this. But apparently, root will be very easy; just plug it into your computer and enter in a few command lines and you're set (so I've heard). Undoubtedly someone will make a one-click script that makes it even easier.
EDIT: Sorry for that one, was posting too fast without thinking first... Actually rooting includes unlocking bootloader and flashing the required binaries via recovery like said below my post.
Sent from my Desire X using XDA Premium 4 mobile app
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Click to expand...
Click to collapse
Really? Sweet!
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Naturally if you want to root the phone, it's only a quick USB cable plug into your computer and a few command line entries away.
Click to expand...
Click to collapse
Good read, BTW.
OnePlus One Review | Android Central
CafeKampuchia said:
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Good read, BTW.
OnePlus One Review | Android Central
Click to expand...
Click to collapse
That's where I heard it. In any case, it'll be simple; that much was promised from the beginning.
What about SuperSU though? I'm honestly not sure how that gets installed to the right place; the only times I've rooted were with programs that did it for me.
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Sent from my Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh really? Absolutely ridiculous.
tiny4579 said:
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Correct - no retail device shipping with Google CTS/GMS can have root enabled, much less the ability to right OUT OF THE BOX. It has to be done manually by the user, at their discretion.
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Chromium said:
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Click to expand...
Click to collapse
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
dmo580 said:
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
Click to expand...
Click to collapse
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
cyanogenmod has been planning to separate root for years. i think they are coming up with a simple method of root. maybe just an app install?
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Cm I think opted to make root removal so they could get cts approval and install Google Apps.
Sent from my HTC One using Tapatalk
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
The Jack of Clubs said:
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
Click to expand...
Click to collapse
I wonder if they're using this recovery.
https://github.com/CyanogenMod/android_bootable_recovery-cm
Simple recovery is the working title.
You are correct that custom recoveries aren't always needed for root; however, in Android 4.3 and later, the two primary root applications need to install a superuser daemon which makes rooting outside of recovery more difficult.
tiny4579 said:
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Click to expand...
Click to collapse
You all guys keep saying that rooting is trivial, but nobody told how to root. I believe you that it's trivial but - anyway -please tell me how to do this step by step.
I'm actually having trouble getting my 64GB production unit to boot into TWRP or have it flash and stick. fastboot says everything is fine, then rebooting into recovery produces the stock simple recovery.
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
I'm sort of at a loss - I've done this to many Nexus devices before, and the idea is the same. My bootloader is unlocked, that went without any issues.
Booting a debug boot.img from https://cyngn.com/products/oneplusone via fastboot just ends up shutting down and showing the battery charging icon.
Volume Up + Power while booting ends up with a black screen - in fact, the only way I can get into recovery is from a booted OS.
Edit: After many tries, trying different cables and unchecking the Settings -> Development -> update recovery with system updates, the TWRP flash succeeded, and the subsequent SuperSU sideload went just fine. Now I'm rooted.
Another tip regarding using Power+VolDn or Power+VolUp - things happen so slowly that if you keep holding Power, it'll actually trip a reboot before it has a chance to load. Just hold the Power button for a few seconds when booting, then let go and keep the VolUp or VolDn pressed.
Chromium said:
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
Click to expand...
Click to collapse
I just did this and it seems to have worked. TiBu just completed..
Used "Fastboot boot TWRP-2.7.1.0.zip" at ADB/Fastboot interface. It booted to TWRP. As I closed, it stated that it looks like "Your device isn't rooted, Do you want to install SuperSU?" To which I said Yes. It rebooted and I was able to open SuperSU, already on the phone, and get root. Then, opened TiBU and performed a full backup.
Archon810 said:
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
Click to expand...
Click to collapse
The first time I did this it hung for a while. it eventually boots into the recovery. I think it took about 2 minutes for it to finally boot into it.
Maybe that helps?
Root One+ fastboot devices hnags "waiting for device"
I amd trying to unlock bootlaoder, and install TWRP on my ONE+. I have tried both android SDK, and TOOLKIT FOR ONEPLUS FROM XDA, and I cannot get fastboot devices to recognize my One+.
What I have do so far:
My PC: windows 7 - 64bit
Installed SDK kit form developer.android.com, and installed the latest composite usb driver from Google.
Installed OnePLus toolkit and tried using that, no dice.
when I execute "fastboot devices" from my fastboot folder, my prompt hangs "waiting for device" FOREVER!!!
"ADB DEVICES" WORKS PERFECTLY, AND ECHOES MY SERIAL NUMBER BACK TO ME."
Related
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
carmike692000 said:
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
Click to expand...
Click to collapse
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Caseyk621 said:
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Click to expand...
Click to collapse
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
carmike692000 said:
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
Click to expand...
Click to collapse
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Caseyk621 said:
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Click to expand...
Click to collapse
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
EDIT - I'm sure one problem with the computer not listing the phone as a device is it cannot find the device driver to install for it, and I've not been successful googling for it. So in the Windows Device Manager list, my XT1080 has a yellow exclamation mark by it. Also, just installed TiB and froze "Motorola OTA" since I had to wait five minutes to post this edit anyways.
carmike692000 said:
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
Click to expand...
Click to collapse
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Caseyk621 said:
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Click to expand...
Click to collapse
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
carmike692000 said:
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
Click to expand...
Click to collapse
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Caseyk621 said:
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Click to expand...
Click to collapse
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
carmike692000 said:
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
Click to expand...
Click to collapse
Glad I could help! Don't forget to make a backup in TWRP! You may find yourself wanting to go back to stock sooner than you think! I keep trying ROMs but always end up missing active notifications and touch less as well as some others!
Sent From Droid Ultra
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
nubia11 said:
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
Click to expand...
Click to collapse
Flash the stock recovery with fastboot. I forget if you need to also unroot or not. Also make sure you have any apps that were disabled or frozen enabled/defrosted
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Andyw2100 said:
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Click to expand...
Click to collapse
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Andyw2100 said:
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Click to expand...
Click to collapse
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
berndblb said:
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
Click to expand...
Click to collapse
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Andyw2100 said:
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it. Though you should already have this on your computer or SD Card.
Edit: I believe there is an even easier way, just have never done it/tried it so I don't wanna lie and act like I know what to do.
The Stig 04 said:
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it.
Click to expand...
Click to collapse
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Thanks to both of you.
I don't believe I removed any bloatware, so I think the OTA update should work.
How do I flash the stock recovery in fastboot?
Again, many thanks!
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
berndblb said:
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Click to expand...
Click to collapse
Sorry I thought fastboot and ADB was kinda that same thing seeing as it was refereed to as "fastboot/adb directory"? If not my bad! Also this is the method I always use to take OTA's and have never ever had a problem.
Andyw2100 said:
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
Click to expand...
Click to collapse
Put the recovery image into the same folder with your fastboot.exe
Open a command prompt from that folder (shift + right click > open cmd window here)
check connection with
Code:
fastboot devices
if successful
Code:
fastboot flash recovery <name of recovery>.img
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
mumbles202 said:
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
No. You will lose root after the ota so it doesn't matter but you can always get it back as long as you are S-OFF by flashing a custom recovery like TWRP and then flashing SuperSu.
Well, I have run into a snag right off the bat.
While the command "ADB Devices" sees the phone, "Fastboot Devices" does not.
Any ideas as to how to rectify this?
Thanks!
I did some googling, and this problem I solved on my own.
I had to use adb to get into fastboot USB mode or something with adb reboot bootloader, and then fastboot devices worked.
I'm now continuing on.
Well, so much for this being easy.
I believe I successfully flashed my stock recovery.
But apparently I no longer have the OTA update ready to install, as at some point I tried to run it again just to get TWRP up, and now it's not showing as available. And when I try to check for updates in Settings/Software update/Check new I get an error message that says Download Unsuccessful. We were not able to download this update.
For now I guess I'll wait and see if Verizon tries to send me the update again, or if it works if I check for it myself some other time. (Or if anyone here has any suggestions.)
Also, I still seem to have root access. I thought that I wouldn't, since I believe I have replaced TWRP with the stock recovery.
I'm also now getting a constant error message about Google Play Services having stopped. And my wi-fi doesn't seem to be connecting properly.
I'm really wondering just what the heck I've done.
Well, for anyone still following my saga...
Things are somewhat better, but not totally resolved.
I kept checking, and eventually I was able to download the OTA update to 4.4.4. I did, I updated, and all went smoothly. I then was able to flash TWRP and then install Super SU and I have root access again. So on that front, all is well.
The problems that remain, though, are that I still am having issues with Google Play Services quitting and my Wi Fi not connecting. Could these things be related somehow? I've tried clearing the cache and then actually all data from Google Play services, but that has not helped. I have deleted my networks, and then tried reconnecting to them, but that also has not helped. It shows my networks in range as "saved" or "disabled" but won't connect to any of them.
Any ideas for me?
Thanks.
And thanks for the help in getting the 4.4.4 OTA update. At least that worked!
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Andyw2100 said:
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Click to expand...
Click to collapse
Not sure why I stopped receiving notifications from your thread. But at least you got your phone in working order! lol
Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.
yes, of course..
root doesn't delete any of your data
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.
timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?
pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon
The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!
But how is anything going to be written to the system partition if it is locked ?
timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?
bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?
pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?
Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!
I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!
zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.
I have my old Nvidia shield tablet and i have WiFi off and powered off.
I've been reading you can stop the kill switch from i guess changing the boot loader or operating system?
I new to this stuff.
Could someone just give me some directions on how to go threw this process please.
I don't know if it's to late cause i have the most recent update? but like i said it's turned off and WiFi is off and i heard that the kill switch is sent over the internet to your device and you don't have to confirm it.
So i hope my system is safe until i can do what ever you guys advise me to do.
Thank you...
treat your old tablet before connecting the new one to internet
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
I used my new tablet and the both were working for the day, both have no problems so far.
I've been reading that they are sending out kill switches in 4 segments, by using the last 2 digits of the serial numbers system.
So mine hasn't gone threw yet i don't think.
So i need to root it?
Then delete the OTA file?
Then flash a custom firmware?
Thanks guys...
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Jarocks said:
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
Click to expand...
Click to collapse
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Snah001 said:
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Click to expand...
Click to collapse
I see lots of root programs, is there a best one?
Can you flash with TWRP?
And someone said all i have to do is...
"Full Process
1) Unlock Bootloader.
2) Flash TWRP Recovery.
3) Get the no more OTA.zip from XDA and flash it via TWRP
4) Check if the update option is removed from Settings, if not flash it again.
Done! "
Is that ok also?
Thank you...
You need to root to flash twrp?
EowynCarter said:
You need to root to flash twrp?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader to fastboot flash anything.
amartolos said:
No, but you do need an unlocked bootloader to fastboot flash anything.
Click to expand...
Click to collapse
Yeah, that the conclusion i reached.
Flash done, now runing bliss pop. First start got me loads of errors. I went until i realized i had forgotten to wipe. It's been a while since i last played with custom roms.
oliwek said:
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Click to expand...
Click to collapse
Well, that's disappointing
oleg77 said:
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
Click to expand...
Click to collapse
Ok i followed the http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
I got to "On the tablet, select "recovery reboot"
But i didn't see it so i selected reboot, i rebooted and was on stock i think?
1) I can see that a few more steps and i'm rooted.
But i'm nervous to try this again from that point.
Should i just start at unlocking the boot loader?
2) Is rooting the device permanently unlocking the boot loader?
3) can i just no OTA from unlocking the boot loader part?
Ok i got to side loader and in the command it says error can't find device and there's an android guy on his back with a red statement mark.
So I'm in developer USB.
I have unlocked the boot loader
I'm flashing the recovery
And i get to restart in recovery.
Then i get the menus to side load the supersu.zip
I renamed it with out caps, i even made a folder in C:\Program Files\Minimal ADB and Fastboot.
Cause it installed at C:\Program Files (x86)\Minimal ADB and Fastboot.
just to avoid the (x86)
when i try and leave the menu to reset it asked me to root, but i had the error so don't want to brick it if rooting with an error on side loading supersu.zip
What do i do?
Thank you...
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
l337g0g0 said:
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
Click to expand...
Click to collapse
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
l337g0g0 said:
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
Click to expand...
Click to collapse
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
frenziedfemale said:
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
Click to expand...
Click to collapse
Ok that installed it.
WOW thank for that.
I guess I'm rooted, how do i test it and what does being rooted do for me?
Thank you....
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i just flashed nomoreOTA.zip.
It said the file was deleted and was a success.
I guess i can use the internet now?
I'm so nervous to turn the internet on and have the thing reset...
Did i need to run supersu to keep it rooted or always rooted until i use supersu to full unroot.
Thank you...
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
l7777 said:
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
Click to expand...
Click to collapse
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
bluh5d said:
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
Click to expand...
Click to collapse
The similarities are only on the surface my friend. When dealing with computers, similar and close is rarely good enough. You need exact.
bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
evilwombat said:
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
Click to expand...
Click to collapse
Can I root with latest supersu without recovery ?
Someone's bound to hose up their phone. Wondering where factory images are?
Born<ICs said:
Someone's bound to hose up their phone. Wondering where factory images are?
Click to expand...
Click to collapse
Yes. I agree. Might be me right. I wasn't planning on flashing recovery though just booting it.
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
If your bootloader is unlocked and you want root.
Try installing Chain fire's Supersu from the play store or install the apk.
I do not have my P2 yet to try.
Sent from my Nexus 5X using Tapatalk
me_droid said:
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
Click to expand...
Click to collapse
I think this may be a waste of time because it was modded to work on Oreo. They have already released a version that works on Oreo 3-1-1 that I already tried it wouldnt boot it. I will probably just wait even though i want to play. So i guess I can just say yep I have a pixel 2 with the bootloader unlocked and thats about it.
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
The_Fuzz22 said:
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
Click to expand...
Click to collapse
Yeah, I take having root completely for granted. I guess I've never bought a phone right at the moment of release before. If I didn't really need a new phone, I suppose I would have waited. Anyway, I figured out that you can block ads, without root, with apps that run all your traffic through a vpn (that's really only running locally on the phone). The best options after much research seem to me to be Netguard and AdGuard (though I haven't tried them yet). They both also include a firewall (Netguard is primarly a firewall), which I want.
https://github.com/M66B/NetGuard/blob/master/ADBLOCKING.md
https://adguard.com/en/adguard-android/overview.html
DNS66 also seems to be higly regarded, but it doesn't include a firewall. There are other firewall only apps, which work with the VPN method, but you can only run one VPN on Android at a time, so if you want both functions, without root, you need an app that does both.
https://forum.xda-developers.com/android/apps-games/app-dns66-source-host-ad-blocker-root-t3487497
Anyway, that's my plan until root comes along. Then I will go back to AdAway and AFWall+.
There is no kernel source released for the Pixel 2/XL yet. It is based on the 4.4 kernel, this should make development very smooth.
https://forum.xda-developers.com/pixel-2/development/psa-fastboot-booting-bad-image-confuse-t3692932