Thanks to some questions and awnsers I was able to create the
rooted boot.img for our HTC Bolt devices.
This was tested on the HTC Bolt Software 1.17.651.11 Android N 7
How To: (downloads at bottom of page)
Connect Device to computer
Insure that usb debugging is on as well as OEM unlock is checked.
The device must be Boot-loader unlocked to do this!
place both the patched_boot.img and the magisk_cache.img in the same directory your fastboot files are setup at ( c:/android/sdk/fastboot or wherever you have it)
Boot the phone into Download mode. ( Power + VOL down)
Open up terminal on the computer and run both these commands:
fastboot devices
fastboot flash boot patched_boot.img
fastboot flash cache magisk_cache.img
followed by fastboot reboot
you'll need to head over to :
http://forum.xda-developers.com/htc-10/development/root-magisk-autoroot-magisk-phhs-t3507505
Grab the manager.apk and the super user apk to complete the setup.
Give these guys a thanks also for getting this going, gonna build a rom with debloat next and see if the twrp will flash it with this boot.img behind it.
shall see
Thanks to:
@OMJ Everything!
@topjohnwu magisk
@Captain_Throwback -twrp,root
@Chainfire - root
Downloads
Patched boot.img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528674
Cache img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528673
***********DevDigitel Custom Images************
Secure Boot Img: https://www.androidfilehost.com/?fid=457095661767122602
Unsecure Boot Img: https://www.androidfilehost.com/?fid=745425885120693359
Flashable ZIPS:
SuperSU:
https://www.androidfilehost.com/?fid=673368273298916495
Radio Fix Zip/FP Scanner Fix : https://www.androidfilehost.com/?fid=673368273298916521
Device will bootloop once, and when done will install su. Please be patient
Nice!
suprised that it went so smoothly, su being systemless is a little buggy here and there with Android N, but otherwise i was able to navigate the internals, remove the bloat, make some build prop edits and theyve stuck. so far so good.
Went ahead and tried to use flashify and flash the twrp image from other post. Flashed and was able to make a backup to sd only. I didn't flash or try to restore it yet but I did have to relock and restore 3x with the stock ruu after removing too much system and trying to flash xposed
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
S off
urbster1 said:
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
Click to expand...
Click to collapse
Not sure.. Probably gonna be some time with Android N.
I was able to change carrier types in Ui.
Got vzw 1x 3g 4G icons
Hot-spot mod
And a few other things working.
No radios to flash.. No kernels and I don't dev kernels.
So I don't need s-off really.. It's more so just having to re-lock
To go back to stock.
I just ordered a Bolt, can't wait to play
Screen shots
OMJ said:
I just ordered a Bolt, can't wait to play
Click to expand...
Click to collapse
Yey can't wait! It didn't want to be the only one working
On it!
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
Use the other supported devices section at bottom.
Just follow the steps on htc dev.
Save the unlock.bin file HTC will email you. You need it Every time you need to lock/unlock. Without s-off (removing the 2nd lock that protects the radios)
* the phone has to be re-locked to be restored with the stock htc software "ruu's"
Htc ruu is a 1 click style restore program...similar to odin that Will run on the PC and restore phone to stock.
It also comes in a update.zip format that can be flashed with the stock Signed recovery only via sd card slot.
Twrp is currently working on bolt / but has limitations because Its not 100%
More screenshots
Random stuff that can be unlocked hidden in the phone.
urbster1 said:
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
Click to expand...
Click to collapse
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
OMJ said:
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
Click to expand...
Click to collapse
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
jcase said:
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
Click to expand...
Click to collapse
@jcase let me know if you need any more partitions, or anything else dumped... Worse case I can send you mine.
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Team DevDigitel said:
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Click to expand...
Click to collapse
I actually just switched to this method after s-off, due to safetynet failing after detecting a unlocked bootloader...magisk can hide the detection
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Team DevDigitel said:
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Click to expand...
Click to collapse
yep...AP is my only goal
there's a kernel patch to bypass detection but I don't know squat about kernel modding
Related
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."
For the life of me I can't figure out why I cannot achieve root thru normal means on lollipop. Currently this is what I have to do when flashing a new ROM (even this method isn't 100 percent successful every time) :
First I flash my rom
Then, if I want to use supersu to manage root, I would flash koush's superuser (that's right you aren't hallucinating, I said koush's superuser)
Then I boot the phone, get it all setup
Then i boot into recovery again and flash supersu
Then reboot
Now I have root.
If I wanted to use superuser I would just do the opposite of what I listed.
And like I said, even this doesn't always work
What the hell fire and brimstone is going on? This should not be so hard., right
DaveKid said:
For the life of me I can't figure out why I cannot achieve root thru normal means on lollipop. Currently this is what I have to do when flashing a new ROM (even this method isn't 100 percent successful every time) :
First I flash my rom
Then, if I want to use supersu to manage root, I would flash koush's superuser (that's right you aren't hallucinating, I said koush's superuser)
Then I boot the phone, get it all setup
Then i boot into recovery again and flash supersu
Then reboot
Now I have root.
If I wanted to use superuser I would just do the opposite of what I listed.
And like I said, even this doesn't always work
What the hell fire and brimstone is going on? This should not be so hard., right
Click to expand...
Click to collapse
You might wanna check Chainfire's posts about rooting Lollipop on here or G+ - it's a bit different to other Android versions
You cant use anything other that SuperSU BETA 2.27 unless you're wanting to use a permissive kernel.
http://forum.xda-developers.com/goo...basic-overview-root-options-lollipop-t2947144
EddyOS said:
You might wanna check Chainfire's posts about rooting Lollipop on here or G+ - it's a bit different to other Android versions
Click to expand...
Click to collapse
You wouldn't happen to have the direct link to it.
And, you are completely correct. I read all about it and then completely forgot that I read it and that I need to send it through ADB to the phone as opposed to flashing it. I just can't find the link in my history.
Thanks
DaveKid said:
You wouldn't happen to have the direct link to it.
And, you are completely correct. I read all about it and then completely forgot that I read it and that I need to send it through ADB to the phone as opposed to flashing it. I just can't find the link in my history.
Thanks
Click to expand...
Click to collapse
Just read the link I posted
rootSU said:
Just read the link I posted
Click to expand...
Click to collapse
Yep, I got it, thanks.
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.
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
First of all, I am not a dev and this write up contains steps used by various devs to achieve fulll root. For some, these steps have worked out well. But, not for me. I had issues with some of the steps not fully working as they should, so I did some research until I could piece together something that worked for me. Here's what I did and managed to get fully rooted using the boot.img from the stock firmware after doing all the steps from this link Articul8Madness's Rooting Guide and couldn't get full root access even after using the steps from this link Articul8Madness's Guide for R/W Access. As I have said, these steps worked for most people. I wasn't one of them.
I followed the steps up to the step where the boot.img is modded by Magisk. This is where I omitted using the modded boot.img and used the original boot.img from the stock firmware and I then ran the flashfile script as mentioned in the steps. After everything was applied I then, rebooted the phone, started setup, disabled System Updates, and I then proceeded to install TWRP using the steps from this link https://drive.google.com/drive/folders/1KZ0xhstQ9V_7TYt3xs7P5XdroYX61CEA after opening Minimal ADB and Fastboot applying these scripts
adb reboot fastboot
then apply this
fastboot flash recovery twrp-3.5.2_10-kiev.img
I then rebooted into recovery and installed TWRP to all available partitions. I then installed Magisk, enabled Systemless Hosts in settings, and rebooted. Afterwards, I used the steps here Munjeni's RW in Super Partition Tool to get RW in super partitions after downloading and using superrepack. I had omitted the ./superrepack /dev/block/bootdevice/by-name/super system_a in order to have it applied to all available partitions. Everything worked out great. I then rebooted, updated Magisk, installed Root Checker and Root Explorer with Superuser root access. I then installed Adaway from https://github.com/AdAway/AdAway and clicking on the Get It On AdAway image. Anything that requires root access here on out, can now be installed. As for the SafetyNet issue, I have not had any problem with it at all even though the check had failed. All is now working well and I sincerely hope that this guide will help others as it have helped me. I may have done this write up but, all credits goes to the true devs.
Time for devs to start making custom Roms now that TWRP can be installed.
Your first link doesn't work for me. The Adaway link works. FYI.
RETIEF said:
Your first link doesn't work for me. The Adaway link works. FYI.
Click to expand...
Click to collapse
WOW!!! I see what I did wrong. All links are now working.
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Sorry, but you will have to ask one of the Devs in the links that I've provided in the OP. Perhaps they are more suited to help with that.
eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Linux will work fine. All the commands required are done thru a terminal session. Use a text editor to get the long unlock code from the phone.
Good luck.
Ok about terminal. I used cmd , but bootloader cannot be unlocked official way nor at&t unlockable coz i don't live in usa.I will try 3rd party helpers.
iceman19631 said:
First of all, I am not a dev...
Click to expand...
Click to collapse
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.
egalambos said:
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.
Click to expand...
Click to collapse
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.
iceman19631 said:
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.
Click to expand...
Click to collapse
Any plans for an update to 3.6.0 for Android 11??
egalambos said:
Any plans for an update to 3.6.0 for Android 11??
Click to expand...
Click to collapse
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.
iceman19631 said:
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.
Click to expand...
Click to collapse
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I don't have an answer for that at this time since I'm still on 10. That'd be too much like a blind man in a desert looking for shade and telling another which way to go.
Greetings, I have a few questions. re the Moto G 5G (One 5G Ace)
I've not found a TWRP for this phone yet which were you using?
In other phones it was important to backup the IMEI (EFS ) and 'persistent' partitions. Do we not do that with this phone as well?
Thx in advance
Sorry for the late reply. I used this version of TWRP twrp-3.5.2_10-kiev.img. As far as the IMEI (EFS) question, it wasn't required when using this root process. However, you can back those up if you like.