I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
TheEarman said:
I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
Click to expand...
Click to collapse
Rooting in MM includes flashing modified boot.img (modified kernel). I guess that's what you are missing. There is the modified boot.img for root in MM dev edition thread or I can recommend you the flar2 elementalX 6.0.2 kernel that I am using right now and is far better on battery life/performance vs the stock one. Cheers!
Thanks. I had read something about a modified boot.img but thought it was only for the GPE version. I'll give it a try. Thanks for the help!
TheEarman said:
Thanks. I had read something about a modified boot.img but thought it was only for the GPE version. I'll give it a try. Thanks for the help!
Click to expand...
Click to collapse
let us know what the outcome is. Been looking for a thread on rooting unlocked/dev edition and was unable to find any
TheEarman said:
I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
Click to expand...
Click to collapse
I was able to root properly, with proper binaries, by using the method described here (I was missing the boot.img flashing step, as indicated by High_voltage): http://forum.xda-developers.com/htc-one-m8/development/kernel-unlocked-developer-edition-t3262823. Problem solved. Thanks!
This isn't a bad question, as the newer 2.6x SU betas can alter the boot image of some devices during the ZIP install. I was actually about to ask whether or not that included the M8's boot image, but it would appear the answer is no.
jshamlet said:
This isn't a bad question, as the newer 2.6x SU betas can alter the boot image of some devices during the ZIP install. I was actually about to ask whether or not that included the M8's boot image, but it would appear the answer is no.
Click to expand...
Click to collapse
I was running 2.64 and now I'm running SuperSU 2.65 and about to test 2.66 later on stock boot.img for MM (I'm on stock MM 6.12.709.4 ROM)
There is no need for a patched boot.img
SuperSU will detect boot.img
If it is stock boot.img, it will install root in systemless mode
If it is a patched boot.img, it will install root in system mode
The point is I have no problem to root a stock MM ROM with 2.64 and later versions
ckpv5 said:
I was running 2.64 and now I'm running SuperSU 2.65 and about to test 2.66 later on stock boot.img for MM (I'm on stock MM 6.12.709.4 ROM)
There is no need for a patched boot.img
SuperSU will detect boot.img
If it is stock boot.img, it will install root in systemless mode
If it is a patched boot.img, it will install root in system mode
The point is I have no problem to root a stock MM ROM with 2.64 and later versions
Click to expand...
Click to collapse
The posts i've read point to the possibility of getting stuck in a bootloop or worst case bricking the device if its attempted without a modified boot. While those were for the gpe version i shouldn't think it matters.
Your suggesting its possible without modifying the boot.img? If so are there any repercussions vs using a patched boot.img?
ShinAkira00 said:
The posts i've read point to the possibility of getting stuck in a bootloop or worst case bricking the device if its attempted without a modified boot.
Click to expand...
Click to collapse
You should always do a TWRP backup before making major system changes, including root. Doing a TWRP backup mean you can simply revert to your backup if you run into such issues.
A bootloop or no boot (into OS) are always possibilities when modding the phone. I doubt a real brick is possible just by attenting root. If you read this somewhere, my guess is the person just meant a bootloop or no boot, not a true brick (which by definition is not recovery except by opening the phone).
redpoint73 said:
You should always do a TWRP backup before making major system changes, including root. Doing a TWRP backup mean you can simply revert to your backup if you run into such issues.
A bootloop or no boot (into OS) are always possibilities when modding the phone. I doubt a real brick is possible just by attenting root. If you read this somewhere, my guess is the person just meant a bootloop or no boot, not a true brick (which by definition is not recovery except by opening the phone).
Click to expand...
Click to collapse
cool, thanks for clarifying.
Related
I can't get TWRP to install on my phone. I've tried manually fastbooting all three TWRP images that are available from the TWRP website. I tried installing TWRP using the Skipsoft Toolkit. Whatever I do I never get past the TWRP splash screen--no menus ever come up. Since no menus ever come up I can't install the TWRP zip or a custom ROM. I've been trying this for hours and it's driving me crazy. Is there a different procedure to boot into temporary TWRP if you are on the June bootloader? Is there another version of the TWRP image file that I'm missing? Am I supposed to let the TWRP sit there for a really long time? This is driving me completely batty.
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
I did. Will give that a try. Thanks.
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
That did the trick! Thanks.
jhs39 said:
That did the trick! Thanks.
Click to expand...
Click to collapse
Np
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
jhs39 said:
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
Click to expand...
Click to collapse
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
noidea24 said:
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
Click to expand...
Click to collapse
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
jhs39 said:
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
Click to expand...
Click to collapse
Booting into the rom, going back into temp TWRP and flashing the TWRP zip seems to have worked --TWRP actually stuck this time and I can boot directly into it now. It's a shame Google made the Pixel XL such a headache to flash on.
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
If you don't want to wipe just update through factory image, just open the factory zip, open flash-all file and remove "-w" from last line, then execute it (update without wipe)
But I suggest to flash the stock factory image with the "-w" to make a clean install, flashing major release like 7.x -> 8.x is always better wipe to avoid potential issues.
But yes, you can first give a try without wipe and only if you find bugs try wiping. Your choice.
simply flash the OTA, then re-root
xraystyle said:
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
Click to expand...
Click to collapse
Use full unroot in supersu. Then take ota. Then root again after upgrading to O
Thanks for the help everyone, you pointed be in the right direction.
In the event that it might help someone else, here's what I ended up doing:
1. I downloaded the OTA, booted into the TWRP I had currently installed, and then sideloaded the OTA.
2. I used ADB to push the newest TWRP flashable zip, the latest SuperSU, and the latest SU-Hide to /sdcard on the device.
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
4. Finally, I rebooted to recovery on the phone (latest TWRP now instead of stock), and flashed SuperSU and SU-Hide.
I'm now stock, rooted, on O. No wipe necessary, kept all my apps and data. So far the OS itself has been entirely stable. I had an issue or two with a few apps after the upgrade, but those were fixed with a quick re-install. Except for Better Terminal Emulator Pro, seems it doesn't want to work on Oreo and it's no longer under active development. It's fine though, there's other terminal emulators out there.
Thanks again for the help!
xraystyle said:
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
Click to expand...
Click to collapse
Which version of TWRP do you have TWRP working with Oreo 8.0?
I can boot into the modded TWRP 3.1 (fastboot boot twrp-3-1-pixel-bootable-mod.img) but AFAIK there is no working flashable recovery for 8.0 yet.
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
gordonlw said:
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
Click to expand...
Click to collapse
That's how I did it. I don't use suhide.
Does the -w in the .bat file format or wipe the data? I want a clean clean , o-fresh in the morning feeling kind of wipe
toknitup420 said:
That's how I did it. I don't use suhide.
Click to expand...
Click to collapse
Thanks! What I ended up doing:
Decided to try and unroot and take the ota. super-su full unroot would not work. so I fastbooted to the mod twrp and flashed UPDATE-unSU. I then took the ota. then fastbooted to mod twrp and flashed super-su. worked perfect!
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
azertguigui said:
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
Click to expand...
Click to collapse
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Huge thanks for this!!! I was having the exact same problem (boot hangs at Google logo) and this resolved it!
I noticed that afterwards in the apps drawer I could not find any SuperSU, but doing adb shell and then invoking su worked, so I then just installed the supersu app from the play store to handle prompts (it seems without the app, root is enabled silently and doesn't seem like that great of an idea).
-----------EDIT------------
After installing the app from play store, DO NOT allow it to update the supersu binaries! I ran into bootloop again after that, and had to re-flash SR5 again. Seems like that's the magical version to use!
You're right about having super su update. I had the same problem.
Edit, I just checked and I'm actually using SR3. SuperSu then updated those binaries without a problem.
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
azertguigui said:
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
Click to expand...
Click to collapse
fastboot boot (drag and drop twrp.img file here)
Sent from my Nexus 5X using Tapatalk
Well for the record, I did the following
Code:
fastboot boot twrp-3.2.1-0-bullhead
Then, I installed SuperSU downloaded here. I went back to fastboot and used
Code:
fastboot flash twrp-3.2.1-0-bullhead
but I still got stuck on the Google logo, meaning that my boot was corrupted or something... I then flashed the original Google boot.img
Code:
fastboot flash boot.img
and re-did the process of flashing SuperSU but I wisely chose to find a SR5 version of the file. I didn't flash TWRP after that and my phone booted normally with supersu.apk installed in it and the root privileges granted ... I don't know if I should try flashing TWRP again since my phone is working fine right now, but thanks anyway for the tip of booting to TWRP and not flashing it directly!
I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.
As far as i know, trying to root stock rom isn't easy. I could be wrong but idk. You can try by:
1. Flashing stock
2. Flashing TWRP
3. Format data
4. Flash DM-Verity and Disable Force-Encrypt then flash magisk.
And i think you can't flash kernels on stock. I could be wrong but idk.
Hey, how did you even install TWRP?
Before I tried installing it my model number was "SM-J600 FN/DS" and now after the install, when I plug it into my pc it says that it's "FN-600G." Whenever I try to boot it in system mode it's stuck in a loop.
I haven't tried flashing the newest firmware yet because I can't even download it for my country.
Sorry, I am a total newbie and can't seem to fix it.
Al-Ameen Adewunmi said:
I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.
Click to expand...
Click to collapse
Hi Guys,
Did you manage to do this? I was experiencing the same bootloop issue and I think it is the version of Twrp (I was using 3.3.1-0).
I used Odin to flash a lower version 3.2.3 found here after which I flashed this DM Verity + Magisk.
Root Success!
Hi everyone, I have an HTC One M8. I wanted to root it but something went wrong and now it is stuck on the white screen with the ONE logo. I correctly unlocked the bootloader and installed twrp. I had downloaded SuperSU on my pc (flashing it with TWRP should have been the following and last step), but after I installed TWRP, before rebooting, it asked me to install SuperSU and I said yes, thinking it would save time. Now I can enter bootloader, I can enter TWRP, but that's it. I tried to install a couple of 0P6BIMG packages, but it always says that the image size is too big. Any help? Thanks.
Download stock ROM, install it from TWRP. If you get errors, try flashing through fastboot (if you can access it)
0purple said:
Download stock ROM, install it from TWRP. If you get errors, try flashing through fastboot (if you can access it)
Click to expand...
Click to collapse
I tried a few, different sizes, I don't know which one to chose, they're all 0P6BIMG, from 1,2Gb to 1,6Gb. Which one should I choose?
This is what TWRP gave me when I tried to install Lineage OS. Also, can you provide a link for the custom rom since all those I tried didn't work?
I`m sorry, I won`t be able to help here. Try researching
Solved. If it can be of any help, apparently the twrp was corrupted and couldn't flash any rom. I changed twrp (3.5) and flashed lineage 17.1. All fine, just keep in mind lineage 17.1 is not friend with Magisk 20.4, but gets along well with 20.3.