Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R
Try nother USB C cable. Some not able to handle data.
rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.
BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,
Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone
Related
Today I was using my OnePlus 7 (OOS Beta 10, TWRP 3.3.1-70, Magisk 20.3) and I accidentally rebooted it to bootloader through the advanced reboot feature. Somehow, I know not how, this soft bricked the device. I could get to the unlocked bootloader warning screen but no further. I could also boot to TWRP and Fastboot still. I tried several different things to fix this, including disabling all Magisk Modules through TWRP, but to no avail. I also tried switching to slot A (I was previously on slot B), but I only booted to the OxygenOS logo and accompanying animation, which lasted 15 minutes or more. Impatient, I began trying several other methods (instead of making a backup :facepalm. Long story short, I ended up wiping all the partitions (including Vendor and System) and I am stuck. I followed the guide here, which allowed me to boot to the OxygenOS logo and animation again, but no full OS boot. I have also reinstalled TWRP (3.3.1-79 now) which works as well, but try as I might I cannot get anything to boot besides that. I have tried installing the images from OnePlus' website, LineageOS 17.1, AOSiP, and custom kernels, but nothing works besides their own respective boot animations which loop forever.
And so, I have come to you, the best Android modding community I know of, to help me fix my problem. I can offer you no incentive besides my eternal gratitude.
Thanks in advance,
Michael
Edit: forgot to mention I use exclusively Linux so I cannot use the MSM tools. Sorry!
DrRayThe2nd said:
Today I was using my OnePlus 7 (OOS Beta 10, TWRP 3.3.1-70, Magisk 20.3) and I accidentally rebooted it to bootloader through the advanced reboot feature. Somehow, I know not how, this soft bricked the device. I could get to the unlocked bootloader warning screen but no further. I could also boot to TWRP and Fastboot still. I tried several different things to fix this, including disabling all Magisk Modules through TWRP, but to no avail. I also tried switching to slot A (I was previously on slot B), but I only booted to the OxygenOS logo and accompanying animation, which lasted 15 minutes or more. Impatient, I began trying several other methods (instead of making a backup :facepalm. Long story short, I ended up wiping all the partitions (including Vendor and System) and I am stuck. I followed the guide here, which allowed me to boot to the OxygenOS logo and animation again, but no full OS boot. I have also reinstalled TWRP (3.3.1-79 now) which works as well, but try as I might I cannot get anything to boot besides that. I have tried installing the images from OnePlus' website, LineageOS 17.1, AOSiP, and custom kernels, but nothing works besides their own respective boot animations which loop forever.
And so, I have come to you, the best Android modding community I know of, to help me fix my problem. I can offer you no incentive besides my eternal gratitude.
Thanks in advance,
Michael
Edit: forgot to mention I use exclusively Linux so I cannot use the MSM tools. Sorry!
Click to expand...
Click to collapse
Download a Fastboot ROM and extract the images.zip. CD into that directory. Get your device into fastboot and manually flash them in Linux. The instructions for doing this are in that post. I needed to do this when I first got my OP7 as I also do not use Windoze. Worked without issue.
Edit:
I just saw that you said you tried this I guess. Give the first boot time. It takes awhile.
spookcity138 said:
Download a Fastboot ROM and extract the images.zip. CD into that directory. Get your device into fastboot and manually flash them in Linux. The instructions for doing this are in that post. I needed to do this when I first got my OP7 as I also do not use Windoze. Worked without issue.
Edit:
I just saw that you said you tried this I guess. Give the first boot time. It takes awhile.
Click to expand...
Click to collapse
It has been 20 minutes and still no response. Should I wait longer?
Edit: 30 Minutes
DrRayThe2nd said:
It has been 20 minutes and still no response. Should I wait longer?
Edit: 30 Minutes
Click to expand...
Click to collapse
Nope,it takes awhile, but not that long if I remember correctly. Sorry man, don't know what else to say. I've done this a couple of times. Once outta necessity and once just to test something. Worked for me both times, so IDK.
Sent from my OnePlus 7 using Tapatalk
spookcity138 said:
Nope,it takes awhile, but not that long if I remember correctly. Sorry man, don't know what else to say. I've done this a couple of times. Once outta necessity and once just to test something. Worked for me both times, so IDK.
Sent from my OnePlus 7 using Tapatalk
Click to expand...
Click to collapse
I'll try some more things. Thanks for your help.
DrRayThe2nd said:
I'll try some more things. Thanks for your help.
Click to expand...
Click to collapse
Np, no idea why this doesn't work for you. Worse case, install Windows via virtualbox or something and use MSM tool like that. Good luck!
Sent from my OnePlus 7 using Tapatalk
Unbrick tool for OnePlus 7 (MSMTOOL Hydrogen Version)
As long as there's no hardware damage, your device can be unbricked through this tool. URL is banned in this forum so I can't give you the link, you can find it in OnePlus 7 Guides, News, & Discussion section.
Patrickzhong said:
Unbrick tool for OnePlus 7 (MSMTOOL Hydrogen Version)
As long as there's no hardware damage, your device can be unbricked through this tool. URL is banned in this forum so I can't give you the link, you can find it in OnePlus 7 Guides, News, & Discussion section.
Click to expand...
Click to collapse
Yeah, but not everyone uses or likes Windows. Myself included. So this tool is not useful for those people.
Sent from my OnePlus 7 using Tapatalk
spookcity138 said:
Np, no idea why this doesn't work for you. Worse case, install Windows via virtualbox or something and use MSM tool like that. Good luck!
Sent from my OnePlus 7 using Tapatalk
Click to expand...
Click to collapse
Patrickzhong said:
Unbrick tool for OnePlus 7 (MSMTOOL Hydrogen Version)
As long as there's no hardware damage, your device can be unbricked through this tool. URL is banned in this forum so I can't give you the link, you can find it in OnePlus 7 Guides, News, & Discussion section.
Click to expand...
Click to collapse
spookcity138 said:
Yeah, but not everyone uses or likes Windows. Myself included. So this tool is not useful for those people.
Sent from my OnePlus 7 using Tapatalk
Click to expand...
Click to collapse
Well guys, I bit the bullet, booted up an old Windows computer, and ran the MSM tool. It successfully installed HydrogenOS, so from there I could install LineageOS. My phone is working again. Thanks for your help.
DrRayThe2nd said:
Well guys, I bit the bullet, booted up an old Windows computer, and ran the MSM tool. It successfully installed HydrogenOS, so from there I could install LineageOS. My phone is working again. Thanks for your help.
Click to expand...
Click to collapse
Thanks for the update. I was curious how this turned out. Guess windows has some use after all [emoji3]
Jk windows users.
Still wonder why manually flashing the partitions via fastboot didn't work. Oh well,unimportant now. Glad ya got it working!
Sent from my OnePlus 7 using Tapatalk
DrRayThe2nd said:
Well guys, I bit the bullet, booted up an old Windows computer, and ran the MSM tool. It successfully installed HydrogenOS, so from there I could install LineageOS. My phone is working again. Thanks for your help.
Click to expand...
Click to collapse
there's also a OOS msmtools if you want, just search for that, it has been posted by @Some_Random_Username
Removed
Reserved for Links and Firmwares
It turns out a permissive Kernel helps with the Storage Problems. I will edit the Guide later with a Link
Nice guide brother, this works also on xperia 1 i think ?
Sorry for my guide, i have no time to update it anymore so thats why its kinda outdated and i found those files on a chinese site in my guide so i shared it only
Xperia
This method has problem if 55.1.A.3.149 is flashed. The "Start" screen freeze with no touchscreen function on reboot after the procedures completed.
Pandemic said:
Nice guide brother, this works also on xperia 1 i think ?
Sorry for my guide, i have no time to update it anymore so thats why its kinda outdated and i found those files on a chinese site in my guide so i shared it only
Click to expand...
Click to collapse
Same Steps, different Files like You can imagine. I made two Folders on Google Drive to keep them seperated. :angel:
I was wondering if we can use the TWRP Installer Zips from like for example the Pixel 2 XL which is almost the same as what we flash actually. Our TWRP is actually from a One Plus 2 or so, while using an old Lazy Flasher with old Magisk Boot File. While the newer TWRP Installers are using a Magisk kind of Installer to do the Ramdisk changes. Only thing i wonder is if the included ramdisk cpio is Device specific or a general thing which shares between different devices!? I'm really about to just try a flash on risk but i would like to here if You know that...
@MartinX3 can hopefully look at this
The ramdisk also contains device specific files
I put the twrp 1/5 on my to-do list
Pandemic said:
@MartinX3 can hopefully look at this
Click to expand...
Click to collapse
MartinX3 said:
The ramdisk also contains device specific files
I put the twrp 1/5 on my to-do list
Click to expand...
Click to collapse
We found together @Pandemic just asked @MartinX3 some Hours ago if he can invite us to the Xperia TWRP Family on his XZ2 Thread, and You mentition him over to this Thread. Funny
It's really no fun actually to recover my Xperia after Bootloops with Fastboot instead of TWRP. Really throw my Hat in the air once we get a working Recovery. If i can help in any way, let Me know Martin!
Wish You a good Start in the coming Week Guys! :fingers-crossed:
Miustone said:
We found together @Pandemic just asked @MartinX3 some Hours ago if he can invite us to the Xperia TWRP Family on his XZ2 Thread, and You mentition him over to this Thread. Funny
It's really no fun actually to recover my Xperia after Bootloops with Fastboot instead of TWRP. Really throw my Hat in the air once we get a working Recovery. If i can help in any way, let Me know Martin!
Wish You a good Start in the coming Week Guys! :fingers-crossed:
Click to expand...
Click to collapse
Yeah haha and i spoke him also in private
I honestly cant wait to see what lineage looks like on the Xperia 5. The stock UI is good but it feels out of place compared to my other Xperia phones
Does this require unlocked bootloader?
BuyXRPnow! said:
Does this require unlocked bootloader?
Click to expand...
Click to collapse
Yes
TWRP freezes when i try step 18, until i hard reboot. I also can't mount the storage to put the zips on my phone. Don't know what else to do. Also my touchscreen has stopped working in android, but still works on twrp.
Joran95 said:
TWRP freezes when i try step 18, until i hard reboot. I also can't mount the storage to put the zips on my phone. Don't know what else to do. Also my touchscreen has stopped working in android, but still works on twrp.
Click to expand...
Click to collapse
Please try : "fastboot flash boot_a ..." instead of just "fastboot flash boot ..." and repeat with "fastboot flash boot_b ...". This will flash the Recovery to both booth Slots. after that do "fastboot -w" which will format Your Device. Reboot into the Recovery and repeat Step 18 if possible. Would be nice to hear from You again!
Edit: You need to pass Step 18 to use Your Storage. After flashing the Zips will Your System start to work normally again. (Touch and everything else)
VIdeo Guides coming this Weekend! Stay tuned!
Miustone said:
Please try : "fastboot flash boot_a ..." instead of just "fastboot flash boot ..." and repeat with "fastboot flash boot_b ...". This will flash the Recovery to both booth Slots. after that do "fastboot -w" which will format Your Device. Reboot into the Recovery and repeat Step 18 if possible. Would be nice to hear from You again!
Edit: You need to pass Step 18 to use Your Storage. After flashing the Zips will Your System start to work normally again. (Touch and everything else)
Click to expand...
Click to collapse
Thank you for the advice! I actually got my phone working with (just) magisk with your other tutorial, that also had the a and b slots. I'll edit it to see if this works too!
Also thank you for supporting a lesser known phone!
edit-
I've tried your new steps, but the phone still freezes when formatting it. Am I doing something stupid?
Joran95 said:
Thank you for the advice! I actually got my phone working with (just) magisk with your other tutorial, that also had the a and b slots. I'll edit it to see if this works too!
Also thank you for supporting a lesser known phone!
edit-
I've tried your new steps, but the phone still freezes when formatting it. Am I doing something stupid?
Click to expand...
Click to collapse
Just a clue, did You Set TWRP to English before doing the Format? That caused Problems for Me...
Miustone said:
Just a clue, did You Set TWRP to English before doing the Format? That caused Problems for Me...
Click to expand...
Click to collapse
Oh.. that might be it. I will try again this weekend.
Joran95 said:
Oh.. that might be it. I will try again this weekend.
Click to expand...
Click to collapse
Good luck, i will investigate some time in this to figure out whats going on... But that might be it :fingers-crossed:
I was wondering if anyone knew about the partition schemes and whether there is enough room on the boot image to install custom recovery on the P4a?
The Pixel 3A did not have enough room on the RAM disk on the boot image. So installing TWRP, even a stripped down version compressed, on the P3a was a no-go.
Custom recovery was not necessary on the P3a. Just having and unlocked bootloader and root via Magisk gives a lot of options including custom ROMs.
However, I'm still curious if custom recovery will ever come to the P4a?
12paq said:
I was wondering if anyone knew about the partition schemes and whether there is enough room on the boot image to install custom recovery on the P4a?
The Pixel 3A did not have enough room on the RAM disk on the boot image. So installing TWRP, even a stripped down version compressed, on the P3a was a no-go.
Custom recovery was not necessary on the P3a. Just having and unlocked bootloader and root via Magisk gives a lot of options including custom ROMs.
However, I'm still curious if custom recovery will ever come to the P4a?
Click to expand...
Click to collapse
LMAO. Give it up. We're going to be on 11. Good night
Golf c said:
LMAO. Give it up. We're going to be on 11. Good night
Click to expand...
Click to collapse
Not everyone will move to 11 right away if thet can get TWRP working on A10 first.
digger16309 said:
Not everyone will move to 11 right away if thet can get TWRP working on A10 first.
Click to expand...
Click to collapse
Good luck my friend. Stay on 10
We don't even have kernel source yet..
I don't think there was twrp for a pixel for a couple years was there? Pixel 2? And that didn't get past rc I don't think.
Golf c said:
LMAO. Give it up. We're going to be on 11. Good night
Click to expand...
Click to collapse
Thanks! As I said TWRP has not been needed and I was just curious.
However I did enjoy your insecure condescending attitude. It made me LMAO.
Again, thanks! ??
dmb219 said:
I don't think there was twrp for a pixel for a couple years was there? Pixel 2? And that didn't get past rc I don't think.
Click to expand...
Click to collapse
I know, it looks like TWRP has been doing a long slow death spiral.
We have TWRP on Android 10 for the Pixel C tablet. But of course among other things, there's no A/B partitions and Google abandoned support for the device a while ago.
Might be a while, pixel 3+ devices haven't had a 100% working TWRP for a long time.
They can still sideload ROMs and patch boot images with adb/fastboot
I'll miss this moving on from my 2xl. Nice to flash and update things without needing a PC
Golf c said:
Good luck my friend. Stay on 10
Click to expand...
Click to collapse
I will until there is EdXposed for 11 + module updates.
digger16309 said:
I will until there is EdXposed for 11 + module updates.
Click to expand...
Click to collapse
Yucky
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Is it at least possible to unlock the bootloader right away? Is that just standard fastboot ADB procedure or is there something Pixel specific(first one)
dpaine88 said:
Is it at least possible to unlock the bootloader right away? Is that just standard fastboot ADB procedure or is there something Pixel specific(first one)
Click to expand...
Click to collapse
Just unlocked my Pixel4a using the standard ADB commands. Will say that OEM Unlocking stayed grayed out, until I connected to my WiFi (No SIM) and let the phone connect to the mother-ship.
Archangel said:
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Click to expand...
Click to collapse
yea i believe you are correct, i think same steps for the pix4 can be applied on the 4a https://www.xda-developers.com/google-pixel-4-root-magisk/
im not sure if there are other ways to get the boot img but id rather just wait for the factory images to release & mess with it then. gonna make a cronjob script to watch / notify me once its up.
renzyyy said:
yea i believe you are correct, i think same steps for the pix4 can be applied on the 4a https://www.xda-developers.com/google-pixel-4-root-magisk/
im not sure if there are other ways to get the boot img but id rather just wait for the factory images to release & mess with it then. gonna make a cronjob script to watch / notify me once its up.
Click to expand...
Click to collapse
If I get around to it this weekend, I may just do a rom dump to extract the boot.img. Haven't done it in a while. I'm still waiting for some screen protectors to arrive before I mess with my phone.
Archangel said:
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Click to expand...
Click to collapse
I can't find them either.
Isn't Android 11 going to make it more difficult to hide root anymore? I am tempted to root, but heard (or read) somewhere that with android 11 that it may not be worth it as any app (or something like that) will be able to see and not work.
This is the first phone I've owned that I think I'll be satisfied with stock. Ad guard does everything I need as ad away did. And it doesn't need root. Everything is fast! Now I don't have to hack Google pay.
edufur said:
This is the first phone I've owned that I think I'll be satisfied with stock. Ad guard does everything I need as ad away did. And it doesn't need root. Everything is fast! Now I don't have to hack Google pay.
Click to expand...
Click to collapse
Curious about adguard. I just tried it and won't install with chrome as browser.
Sent from my OnePlus 5T using XDA Labs
Ok here we go. I bought this new. I did a deleted Magisk which I should of not done. Somehow the root is screwed up. I am trying to get in the phone to restore it to like I bought it. There was an issue when I bought it with Magisk. Something about it needed to be an app. Anyway, When I do a reboot I have a choice of Reboot, Recovery, Soft Reboot , Bootloader. I want to flash a rom again and fix the Magisk so it has no errors. I have read and tried the different way to do this. I installed TWRP but cannot get it to come up on a boot because there is no home button on my phone. Any suggestions?
You can start from scratch and install the official ROM that's supposed to be on your phone via miflash
Then you can start fresh on ROM of your choice and clean install of twrp and magisk etc
Dash Riprock said:
Ok here we go. I bought this new. I did a deleted Magisk which I should of not done. Somehow the root is screwed up. I am trying to get in the phone to restore it to like I bought it. There was an issue when I bought it with Magisk. Something about it needed to be an app. Anyway, When I do a reboot I have a choice of Reboot, Recovery, Soft Reboot , Bootloader. I want to flash a rom again and fix the Magisk so it has no errors. I have read and tried the different way to do this. I installed TWRP but cannot get it to come up on a boot because there is no home button on my phone. Any suggestions?
Click to expand...
Click to collapse
U shouldn't do what u dont really know from beginning
Way to fix your problem: download miflash and fastboot rom file to flash it to stock rom (any region u want because of unlocked bootloader)
hungragezone said:
U shouldn't do what u dont really know from beginning
Way to fix your problem: download miflash and fastboot rom file to flash it to stock rom (any region u want because of unlocked bootloader)
Click to expand...
Click to collapse
I was wanting to unroot the phone and it was supposed to unroot it when you uninstall Magisk. There already was an issue with Magisk from the start wanting it to be an app instead of a system app. Things went down from there. I have fastboot, recovery on it now. Just want to be able to download some apps that won't install because of root detection. Now I have a corrupted root thanks to Magisk.
speedtripler said:
You can start from scratch and install the official ROM that's supposed to be on your phone via miflash
Then you can start fresh on ROM of your choice and clean install of twrp and magisk etc
Click to expand...
Click to collapse
I cannot find Hermes on the site. M11 Ultra is my phone. Redmi Note 2 .
speedtripler said:
You can start from scratch and install the official ROM that's supposed to be on your phone via miflash
Then you can start fresh on ROM of your choice and clean install of twrp and magisk etc
Click to expand...
Click to collapse
If I could find my Rom that would be nice.
Dash Riprock said:
If I could find my Rom that would be nice.
Click to expand...
Click to collapse
You don't sound like you have put in much effort tbh
You should read more and watch some of those video tutorials before doing things that break your phone
The phone is not bricked. I cannot find the firmware for this phone. Weird. I have looked a a lot of firmware and cannot find one for this phone. it says M11 Ultra and Redmi Note 2 (hermes) the Android OS is 10 but the hermes I see are 5.0. Too old os. I do watch the videos. When I got this phone it already was not right with the rooting it came with. I did not want rooting because I cannot download certain apps I use. I went through the steps to delete root through deleting Magisk but from there it went to ****. The phone works. But there is corrupted root and fastboot keeps tapping out when I boot to it. Also Magisk was updated to 23.1 at the start and there was a conflict with that. Had I known this phone was rooted I would of never bought it. Also not sure if bootloader is open. My PC sees it just fine communicating with the phone through a program I have not figure out. What I have tried does not work. I don't need an ass chewing here. I just asked for some help. Thanks
speedtripler said:
You don't sound like you have put in much effort tbh
You should read more and watch some of those video tutorials before doing things that break your phone
Click to expand...
Click to collapse
Yes I have put effort for a week now. I assume I need the fastboot rom to get this. I cannot get TWRP to even come up on the phone. Fastboot always does.
speedtripler said:
You don't sound like you have put in much effort tbh
You should read more and watch some of those video tutorials before doing things that break your phone
Click to expand...
Click to collapse
I also want to add there is no where in the developer options that I can turn on the OEM. What I watch on the videos is NOT on the phone I have. I do have debug on the computer sees the phone. thats it.
Dash Riprock said:
The phone is not bricked. I cannot find the firmware for this phone. Weird. I have looked a a lot of firmware and cannot find one for this phone. it says M11 Ultra and Redmi Note 2 (hermes) the Android OS is 10 but the hermes I see are 5.0. Too old os. I do watch the videos. When I got this phone it already was not right with the rooting it came with. I did not want rooting because I cannot download certain apps I use. I went through the steps to delete root through deleting Magisk but from there it went to ****. The phone works. But there is corrupted root and fastboot keeps tapping out when I boot to it. Also Magisk was updated to 23.1 at the start and there was a conflict with that. Had I known this phone was rooted I would of never bought it. Also not sure if bootloader is open. My PC sees it just fine communicating with the phone through a program I have not figure out. What I have tried does not work. I don't need an ass chewing here. I just asked for some help. Thanks
Click to expand...
Click to collapse
Fake phone. It Isn't a real Mi11 Ultra. Just some sh1tty phone try to fake 11U
And im sure that u will not be able to fix this phone here. Just throw it away
Dash Riprock said:
Yes I have put effort for a week now. I assume I need the fastboot rom to get this. I cannot get TWRP to even come up on the phone. Fastboot always does.
Click to expand...
Click to collapse
Check and make sure "USB Debugging" is on under Developer Options. Once this done, from the command prompt, execute "adb reboot recovery". This will take you to recovery (TWRP in your case).
Dash Riprock said:
I also want to add there is no where in the developer options that I can turn on the OEM. What I watch on the videos is NOT on the phone I have. I do have debug on the computer sees the phone. thats it.
Click to expand...
Click to collapse
When you get to Setting, in the search bar type "OEM" and it will list "OEM Unlocking" in the search result. Clicking on this should help you get to OEM Unlocking option.
Dash Riprock said:
The phone is not bricked. I cannot find the firmware for this phone. Weird. I have looked a a lot of firmware and cannot find one for this phone. it says M11 Ultra and Redmi Note 2 (hermes) the Android OS is 10 but the hermes I see are 5.0. Too old os. I do watch the videos. When I got this phone it already was not right with the rooting it came with. I did not want rooting because I cannot download certain apps I use. I went through the steps to delete root through deleting Magisk but from there it went to ****. The phone works. But there is corrupted root and fastboot keeps tapping out when I boot to it. Also Magisk was updated to 23.1 at the start and there was a conflict with that. Had I known this phone was rooted I would of never bought it. Also not sure if bootloader is open. My PC sees it just fine communicating with the phone through a program I have not figure out. What I have tried does not work. I don't need an ass chewing here. I just asked for some help. Thanks
Click to expand...
Click to collapse
How much did you pay for it?
It cannot be a Redmi note 2 and a mi 11 ultra at the same time....
It sounds like the other said, a fake phone
speedtripler said:
How much did you pay for it?
It cannot be a Redmi note 2 and a mi 11 ultra at the same time....
It sounds like the other said, a fake phone
Click to expand...
Click to collapse
Paid around $100 When I go to the settings it says device model M11 Ultra, BUT when I go to Regulatory Information it says Model Redmi Note 2 IC: hermes . Here is the link of the phone I bought. Again I cannot find the for sure Firmware for this. Not sure it is the right firmware. https://www.ebay.com/itm/144199997051?hash=item2192fd567b:g:MagAAOSwakdhP9I7
archer797 said:
When you get to Setting, in the search bar type "OEM" and it will list "OEM Unlocking" in the search result. Clicking on this should help you get to OEM Unlocking option.
Click to expand...
Click to collapse
Did that. Nothing. Blank screen no results.
hungragezone said:
Fake phone. It Isn't a real Mi11 Ultra. Just some sh1tty phone try to fake 11U
And im sure that u will not be able to fix this phone here. Just throw it away
Click to expand...
Click to collapse
This is the phone. Check it out. Thanks https://www.ebay.com/itm/144199997051?hash=item2192fd567b:g:MagAAOSwakdhP9I7
Dash Riprock said:
This is the phone. Check it out. Thanks https://www.ebay.com/itm/144199997051?hash=item2192fd567b:g:MagAAOSwakdhP9I7
Click to expand...
Click to collapse
The phone works fine but its rooted and I don't want root. This all started because I followed what it said about removing root. Just do it through Magisk. That did NOT work. From there corrupt root. As for phone It works. But I cannot use my banking and investment apps on a rooted phone. That is the problem.
Dash Riprock said:
This is the phone. Check it out. Thanks https://www.ebay.com/itm/144199997051?hash=item2192fd567b:g:MagAAOSwakdhP9I7
Click to expand...
Click to collapse
fake phone
confirmed
/btw: M11 not Mi 11 rofl
MTK6595, not much hope of resolving this without getting hold of seller and finding out the ROM producer and probably flashing again on a formatted system ( there are so many but a search on a browser may help). Flashing MTK systems are not hard, just need the correct ROM and leave it unrooted using SP flash tools. There are plenty of rooting bids for mtk's, so may be you can unroot too using the guides from a browser search. Unless you can return as an item not as described for a refund.
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.