Related
Recently I got a nexus 7 2013 5.1.1 LMY48I which I tried to root with NRT. Long story short like many other people I cant get TWRP to mount the files it needs(I get to the automated step that is suppose to open TWRP and install some files from a ZIP archive and it hangs up). First off I have a USB OTG cable coming within a couple days. I have looked for the past couple hours for a solution and keep coming up empty. Basically I have two questions, 1. what files do I need to have transferred so that I can get my Root permissions installed properly and 2. should I wait for the USB OTG calbe or should I try to use abs push
I'm in the same boat, really would like to get this thing rooted. I have been all over the WugFresh Forum, as well as Android Central and this one too of course. I have not found an answer to this problem yet. If I come across one I will post here, please do the same.
Dude. this is infuriating. Apparently the alst batch that was made, they changed the mmc chip. These all went out on Groupon and stuff on sale.
https://www.reddit.com/r/AndroidQue...e_to_mount_partitions_after_flashing_twrp_on/
The only recovery that I got to work was the TWRP for Multirom because they actually addressed the issue. The bug has been brought up on the TWRP flo github they just have yet to fix it.
This is infuriating
gorilla p said:
Dude. this is infuriating. Apparently the alst batch that was made, they changed the mmc chip. These all went out on Groupon and stuff on sale.
The only recovery that I got to work was the TWRP for Multirom because they actually addressed the issue. The bug has been brought up on the TWRP flo github they just have yet to fix it.
This is infuriating
Click to expand...
Click to collapse
So what version of Android are you running now. I am on 6.0.1 and want to root it. Did you apply this to to Lollipop or Marshmallow? Thanks for the info.
UPDATE: This worked for me I am now on MM 6.0.1 and rooted. Thank you for the find.
Yea we already have a thread for this..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
sgtfoo said:
Yea we already have a thread for this..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
Click to expand...
Click to collapse
Thank you I was able to downgrade and root my device using that method. Now I just need to figure out how to flash to purenexus or just upgrade my device to 6.+ and root it.
AngryPotato said:
Thank you I was able to downgrade and root my device using that method. Now I just need to figure out how to flash to purenexus or just upgrade my device to 6.+ and root it.
Click to expand...
Click to collapse
You can root 6.0.1 using the beta SU from Chainfire. I am running the new one from Groupon using the multirom TWRP and I flashed SU 2.65 and it worked perfectly.
diggitydogg said:
You can root 6.0.1 using the beta SU from Chainfire. I am running the new one from Groupon using the multirom TWRP and I flashed SU 2.65 and it worked perfectly.
Click to expand...
Click to collapse
so update to 6.0.1 stock then root or flash a rooted rom?
AngryPotato said:
so update to 6.0.1 stock then root or flash a rooted rom?
Click to expand...
Click to collapse
I did a clean flash of stock 6.0.1. Then flashed the multirom version of TWRP since I have one of the newer chipsets of the Nexus 7. Then I flashed the beta SU. All was good. The issue I am having now is that I can't get the restore from within TWRP to work. I backup fine, but when I restore it gets partway through the system part and then just says Failed. Not really sure what the deal is there. I am guessing it has to do with this multirom version of TWRP, but I'm not really sure...
Hi! So I'm looking to root my Nexus 5x following this guide. However, I can't find the modified boot.img for my build MMB29P. I have a brand new phone out of the box (my mic stopped working so this is a replacement) so I'd like to get this done in the next little while the phone has no data and I can wipe anything I need to without worry and use the restore afterwards. I also heard something about SuperSU being able to use stock boot.img or something of that nature, could someone clue me in? Thanks!
[GUIDE] Unlock/Root/Flash for Nexus 5X - Heisenberg's How-To Guide For Beginners
take a look at section 6
as an alternative there are some toolkits that may be more convenient to you (on-screen instructions and detailed faq/guides)
The latest version of SuperSU (v. 2.66 I believe) is automated for systems root. I actually used the SuperSU beta v. 2.62 to root. I just unlocked bootloader, flashed TWRP, and then flashed that version of SuperSU.
Sent from my Nexus 5X using Tapatalk
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
https://www.androidfilehost.com/?w=files&flid=43558
k.s.deviate said:
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
Click to expand...
Click to collapse
Even with systemless root?
When it comes to upgrading, there are a couple of routes you can take. Both involve downloading the official factory image ZIP first. Extract the contents, reboot into bootloader, and then you have option:
1. Edit the flash-all script (.bat for windows and .sh for Linux/Mac) by removing the -w option. Removing this option will prevent the upgrade from wiping user data. Once the option is removed, simply run the script to upgrade.
2. Flash the images individually. Sometimes certain things don't change like bootloader.img or radio.img. You should always flash boot.img, system.img, and vendor.img when updating. This is the route I take.
After flashing the images, you will need to reboot into Recovery mode and flash SuperSU. Then wipe cache and dalvik and reboot into system. If you use a custom kernel, you will need to reflash that as well after updating.
Sent from my Nexus 5X using Tapatalk
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
jkingaround said:
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
Click to expand...
Click to collapse
Google posts the official factory images on the developer site. Here is the link: https://developers.google.com/android/nexus/images
AFAIK the boot warning can't be removed, but I may be wrong. It's nothing to worry about though.
Having a custom kernel is not necessary, but there are benefits to using one. Custom kernels typically provide better battery life with same or improved performance. They can also make your device run cooler and use less memory. Custom kernels also allow for various tweaks such as change vibration intensty, screen DPI, headphone/speaker gain, etc. I personally use ElementalX with the Interactive Governor tweaks from the thread in the general forum, but I've read that Franco Kernel is very good as well and will probably try that out in the future.
Sent from my Nexus 5X using Tapatalk
jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
Just pick a custom rom to try and follow OP instructions. Cataclysm seems to be a hit...
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
More details will be needed to help. Bootloader unlocked? Guessing yes since you say you had twrp. Check the guide section for root instructions.
Yes I have it unlocked. I looked at the guide and it looks like I will have to reflash the stock rom which I'd like to avoid.
Kreuger said:
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
Click to expand...
Click to collapse
Since, twrp is not available yet for Android 10 (Q), I suggest one of the three following options:
1. If you have to re-flash the Pixel 3 XL Android 10 (Q) Factory image, do #4 'keep data' in this Guide.
2. If your Pixel 3XL has the latest Android 10 (Q) Factory image installed, just do #9 A. in this Guide to root.
3. If you are on a Custom ROM follow the OP Instructions in the Custom ROM thread to root.
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Kreuger said:
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Click to expand...
Click to collapse
Yes!
Why not do #1 update your Pixel 3 XL to the February Factory image (QQ1A.200205.002). You will not lose your data (need to reinstall anything). Then do #2 to root.
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Kreuger said:
Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Some people are reporting that issue. You can set the custom channel to canary/canary debug manually. Check the magisk thread.
Thank you. I tried to find it on the github site and found nothing.
Kreuger said:
Thank you. I tried to find it on the github site and found nothing.
Click to expand...
Click to collapse
It is under the magisk files repo.
Kreuger said:
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Kernel/Kernel Managers are optional. #10 B ,in the guide, updated.
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Kreuger said:
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Click to expand...
Click to collapse
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
wangdaning said:
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
Click to expand...
Click to collapse
Ah I was unaware. Thanks
Can anyone write an up-to-date guide on precisely what I need to do to install TWRP on a global-edition, fully updated (MIUI 12) Note 8 Pro today?...
There are three different guides and none of them work. I'm not interested in custom firmwares or anything else besides TWRP. I just want to install TWRP and magisk.
We are in the same boat...
Edit: N/A
Are you able to unlock your bootloader?
Also, pay really close attention to the warning at the top of the TWRP downloads page for your device.
WARNING: This device hard bricks really easily for unknown reasons. Restoring device without spending real money is impossible as of now. Don't flash TWRP unless you are an advanced user who knows what he is doing.
Click to expand...
Click to collapse
Additionally, there are a lot of weird quirks all over the place, which makes your device... non-optimal for modding.
Let me know if you really want help with this.
I really just wanted root and didn't realize you aren't supposed to use TWRP for it on new phones (especially this one.)
sfaeium said:
I really just wanted root and didn't realize you aren't supposed to use TWRP for it on new phones (especially this one.)
Click to expand...
Click to collapse
It's not that you're not supposed to use TWRP. It's that you need to know what you're doing.
That device you have is very easy to brick. I'm just making sure.
If you do only want root, that is very easy. First: do you have an unlocked bootloader? Second: exactly what software version do you have?
LoganDark said:
It's not that you're not supposed to use TWRP. It's that you need to know what you're doing.
That device you have is very easy to brick. I'm just making sure.
If you do only want root, that is very easy. First: do you have an unlocked bootloader? Second: exactly what software version do you have?
Click to expand...
Click to collapse
I have read many post about "how to root RN8P" but in none of these there was a clear and decisive answer!
For example mine RN8P with A9 and bootloader unlocked go in bootloop everytime im trying to install TWRP ---->
twrp-3.4.0-0-begonia.img28.5M2020-06-21 22:25:46 EDT
so what custom recovery i need to install???
roberto_1986 said:
I have read many post about "how to root RN8P" but in none of these there was a clear and decisive answer!
For example mine RN8P with A9 and bootloader unlocked go in bootloop everytime im trying to install TWRP ---->
twrp-3.4.0-0-begonia.img28.5M2020-06-21 22:25:46 EDT
so what custom recovery i need to install???
Click to expand...
Click to collapse
I would recommend installing Magisk first since then you can use the TWRP installer.
LoganDark said:
I would recommend installing Magisk first since then you can use the TWRP installer.
Click to expand...
Click to collapse
wait...i dont understand....
usualy first u need to install the recovery then u can root your phone....
can u explain better pls?
roberto_1986 said:
wait...i dont understand....
usualy first u need to install the recovery then u can root your phone....
can u explain better pls?
Click to expand...
Click to collapse
Installing Magisk from recovery is a legacy option and no longer recommended. The recommended method of installing Magisk consists of patching the boot image using the Magisk Manager app and then using fastboot to flash the patched boot image to the phone.
Installing TWRP is then as easy as using Magisk Manager to flash the TWRP installer zip, then reinstalling Magisk using direct install.
In order to retrieve a boot image to patch, you need to download the update you are using to a computer, then use a tool like Payload Dumper to extract the boot.img.
Kind of complex but it's the only option if installing TWRP without it bootloops you.
LoganDark said:
Installing Magisk from recovery is a legacy option and no longer recommended. The recommended method of installing Magisk consists of patching the boot image using the Magisk Manager app and then using fastboot to flash the patched boot image to the phone.
Installing TWRP is then as easy as using Magisk Manager to flash the TWRP installer zip, then reinstalling Magisk using direct install.
In order to retrieve a boot image to patch, you need to download the update you are using to a computer, then use a tool like Payload Dumper to extract the boot.img.
Kind of complex but it's the only option if installing TWRP without it bootloops you.
Click to expand...
Click to collapse
Well ty for your answer but i really cant understand your explanation....
also there is another way to install a custom recovery and its LR TWRP!
i did many month ago with success but a week ago for wrong im uninstalled magisk so now i have to repeate all from zero...
I find that LR TWRP from this thread but unfortunately the link is dead ----> here so can u tell me where i can find that version of LR TWRP 1104??
also can u show me a link for your guide also??? ty very much
roberto_1986 said:
Well ty for your answer but i really cant understand your explanation....
also there is another way to install a custom recovery and its LR TWRP!
i did many month ago with success but a week ago for wrong im uninstalled magisk so now i have to repeate all from zero...
I find that LR TWRP from this thread but unfortunately the link is dead ----> here so can u tell me where i can find that version of LR TWRP 1104??
also can u show me a link for your guide also??? ty very much
Click to expand...
Click to collapse
I don't own this device so I don't know any guides. The process is the same for most devices and the scripts will automate it for you.
Like I said, find a software update for your phone (search "miui 12.4.847.37586 OTA update zip" or similar), use Payload Dumper to extract a boot.img, transfer it to your device, install Magisk Manager and use that to patch the image, download the patched image to your computer, boot the phone into fastboot and flash the new boot image, and you'll have Magisk.
From there, go to the official TWRP website and download the "twrp-installer" for your device. Use Magisk Manager to install it. Then direct install Magisk to keep root.
LoganDark said:
I don't own this device so I don't know any guides. The process is the same for most devices and the scripts will automate it for you.
Like I said, find a software update for your phone (search "miui 12.4.847.37586 OTA update zip" or similar), use Payload Dumper to extract a boot.img, transfer it to your device, install Magisk Manager and use that to patch the image, download the patched image to your computer, boot the phone into fastboot and flash the new boot image, and you'll have Magisk.
From there, go to the official TWRP website and download the "twrp-installer" for your device. Use Magisk Manager to install it. Then direct install Magisk to keep root.
Click to expand...
Click to collapse
sry i dont understand can u explain more easly?
I am from the Philippines. Rooting my old tablet MyPhone brown 1, with Nougat OS installed, is my biggest frustration. Tried Kingroot & Kingoroot but failed so anyone who can help me Pls.!!!
roberto_1986 said:
sry i dont understand can u explain more easly?
Click to expand...
Click to collapse
I know it's a lot to look at but please do just try to follow them in order. Each step is only a few words long.
What software version is your phone at?
xdagogo2017 said:
I am from the Philippines. Rooting my old tablet MyPhone brown 1, with Nougat OS installed, is my biggest frustration. Tried Kingroot & Kingoroot but failed so anyone who can help me Pls.!!!
Click to expand...
Click to collapse
this thread are for redmi note 8 pro this is not the correct place to ask....>.>
roberto_1986 said:
this thread are for redmi note 8 pro this is not the correct place to ask....>.>
Click to expand...
Click to collapse
Sorry !!!I,m new member!
LoganDark said:
I know it's a lot to look at but please do just try to follow them in order. Each step is only a few words long.
What software version is your phone at?
Click to expand...
Click to collapse
Well this is the version i have installed:
Redmi Note 8 Pro EEAStableFastbootV11.0.3.0.PGGEUXM9.03.5 GB2019-12-10Download
roberto_1986 said:
Well this is the version i have installed:
Redmi Note 8 Pro EEAStableFastbootV11.0.3.0.PGGEUXM9.03.5 GB2019-12-10Download
Click to expand...
Click to collapse
Hey!! Fun fact, you don't need to use payload dumper for that! Download the "Full ROM" with "Type: Recovery", and unzip it. Inside there will be a "boot.img". That's what you patch using Magisk Manager.
Seeing a lot of issues with Android 11 and 12 unlocking the bootloader and applying root. Is now not a good time to upgrade or should I wait for a boot image?
Not quite sure what you're referring to, but there are zero issues with unlocking the bootloader or rooting your device...
I can't speak for TWRP. I have had issues with it the last few versions so I had to make due without it. If I am mistaken about having twrp on the OP9 Pro on the newest LE2125 c61 update, I'd be interested.
Anyway, my response is mostly to address your question regarding root. Here are the steps that worked for me.
[OnePlus 9 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
I have been rooted since day one on both A11 & A12. I'm running stock and haven't had a single issue.
Avoid TWRP, it's known to not work properly on A12
If you like to flash a custom ROM. Follow the instructions and you will be fine.
I am coming off the oneplus 7pro was enjoying TWRP and Magisk, with Exposed now I am hearing TWRP isn't working on anything above 10.0 ver. Guess I have to do so more research or pay Monfrio a ransom to work on TWRP.
intense21 said:
I am coming off the oneplus 7pro was enjoying TWRP and Magisk, with Exposed now I am hearing TWRP isn't working on anything above 10.0 ver. Guess I have to do so more research or pay Monfrio a ransom to work on TWRP.
Click to expand...
Click to collapse
there is no need for TWRP...
Smedslund said:
I have been rooted since day one on both A11 & A12. I'm running stock and haven't had a single issue.
Avoid TWRP, it's known to not work properly on A12
If you like to flash a custom ROM. Follow the instructions and you will be fine.
Click to expand...
Click to collapse
How do you root without twrp? or you mean to just boot twrp and not install it?
CtrlValCanc said:
How do you root without twrp? or you mean to just boot twrp and not install it?
Click to expand...
Click to collapse
Use Magisk, patch bootimg , install and reboot.
Read this usefull guide.
Smedslund said:
Use Magisk, patch bootimg , install and reboot.
Read this usefull guide.
Click to expand...
Click to collapse
thank you, i couldn't find what boot.img to download (and how), but this guide has already all!
CtrlValCanc said:
thank you, i couldn't find what boot.img to download (and how), but this guide has already all!
Click to expand...
Click to collapse
I always just sideload. (downdload magisk apk & rename to zip before)
this way you do not need the extra boot.img I think.
vincemue said:
I always just sideload. (downdload magisk apk & rename to zip before)
this way you do not need the extra boot.img I think.
Click to expand...
Click to collapse
could you explain better? I never used sideload before. What commands do you use?
CtrlValCanc said:
could you explain better? I never used sideload before. What commands do you use?
Click to expand...
Click to collapse
If you want to install any add-ons, Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip those packages in sequence. (GAPPS or Magisk for example)
for example for magisk:
download the newest magisk apk version
after download, rename it and instead of .apk do it .zip
go into revovery and click Apply Update, then Apply from ADB
command is : "adb sideload Magisk-v2X.X.zip"
you must exchange X for your version.
Boot images gets patched
please note that I am not an expert, that is just what I found somewhere and use since then.
if you need more information you could also check the install instructions for lineageOS to get to know some basics: https://wiki.lineageos.org/devices/lemonadep/install