Related
I've got one you've never heard of before. A Nexus 6 with TWRP loaded. Phone will boot to Recovery or Bootloader, but 'System' boot goes to "Google" and never loads. ROM is gone. Bootloader is locked. Do I have a 3-week-old brick? Phone was previously rooted and functioning, but change from Sprint to Google Fi required the stock ROM. Somehow the bootloader got locked and there was no option to enable developer mode in the ROM. So now we're here. What options do I have, other than buying another phone? I can't RMA, since it's been rooted and unlocked. I'm just screwed out of my $300 phone.
Wipe userdata and cache in TWRP. While in TWRP, hook up to your computer and transfer over a ROM zip (whatever custom ROM). Flash in TWRP.
Voila!
Didgeridoohan said:
Wipe userdata and cache in TWRP. While in TWRP, hook up to your computer and transfer over a ROM zip (whatever custom ROM). Flash in TWRP.
Voila!
Click to expand...
Click to collapse
Bootloader is locked...it won't install the ROMs. I have no way to unlock it at this point.
mightymichelob said:
Bootloader is locked...it won't install the ROMs. I have no way to unlock it at this point.
Click to expand...
Click to collapse
Have you tried? 'Cause the method I describe above have been known to work when people mess up their phones by locking the bootloader without a bootable system.
can you fastboot flash in the bootloader? if so, try Nexus Root Toolkit to try and unlock the bootloader/restore stock/do a thing to get your device back to a useful state.
SamsonIncorporated said:
can you fastboot flash in the bootloader? if so, try Nexus Root Toolkit to try and unlock the bootloader/restore stock/do a thing to get your device back to a useful state.
Click to expand...
Click to collapse
Do tell me which magic toolkit can unlock anything without you enabling Enable OEM Unlocking in settings.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
mightymichelob said:
Bootloader is locked...it won't install the ROMs. I have no way to unlock it at this point.
Click to expand...
Click to collapse
So you didn't try to flash, e.g. cyanogenmod 13 withy TWRP, then boot it up, enable OEM unlocking, and unlock bootloader?
istperson said:
Do tell me which magic toolkit can unlock anything without you enabling Enable OEM Unlocking in settings.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
So you didn't try to flash, e.g. cyanogenmod 13 withy TWRP, then boot it up, enable OEM unlocking, and unlock bootloader?
Click to expand...
Click to collapse
he said he can't install any ROM at this point due to the bootloader being locked. If he can't install a ROM, he can't get into Settings to enable OEM Unlocking. As for being able to flash, whether through toolkit or command line, any suggestion is better than nothing. Ultimately just trying to help a fellow user out.
SamsonIncorporated said:
he said he can't install any ROM at this point due to the bootloader being locked. If he can't install a ROM, he can't get into Settings to enable OEM Unlocking. As for being able to flash, whether through toolkit or command line, any suggestion is better than nothing. Ultimately just trying to help a fellow user out.
Click to expand...
Click to collapse
1. Any valid suggestion, yes, but a shot in the dark doesn't help much, does it now. More so, if we know that toolkits are nothing more than graphical frontends to comandline tools. So if typing fastboot oem unlock gives you error, then executing the same command from the toolkit will give you the same error.
2. There is not enough information on how @mightymichelob tried to flash a rom. Because fastboot flash will fail, while flashing a zip, e.g. cm-13.0 should not.
He has twrp installed what's the big deal, move a rom to SD card from twrp and flash it, am I missing something?
if you have twrp installed, then your bootloader IS unlocked, period. you can not flash twrp with a locked bootloader.
edit.. nevermind, assuming op locked his bootloader. format cache and userdata via fastboot then flash a rom.
Bootloader *was* unlocked. I screwed up and locked it, which then wiped my system settings. I could no longer get in to turn Developer Mode on so I could unlock it again because it said my user didn't have permission. After using NRT, and scouring Google for hours, I ended up with a wiped ROM and an MRT that will no longer mount. I have a ROM pushed to the device, but when trying to install, it fires off error after error about the data partition not existing (it won't mount, either). I have rooted a dozen phones or more in my life...I have no idea why this one decided to brick hard. I have no partitions, no bootloader unlock, and no way to recover. It was a long shot, but I thought maybe there was some magical solution. If it's going to exist, it would be on XDA forums.
Have you tried the repair option in twrp?
mightymichelob said:
Bootloader *was* unlocked. I screwed up and locked it, which then wiped my system settings. I could no longer get in to turn Developer Mode on so I could unlock it again because it said my user didn't have permission. After using NRT, and scouring Google for hours, I ended up with a wiped ROM and an MRT that will no longer mount. I have a ROM pushed to the device, but when trying to install, it fires off error after error about the data partition not existing (it won't mount, either). I have rooted a dozen phones or more in my life...I have no idea why this one decided to brick hard. I have no partitions, no bootloader unlock, and no way to recover. It was a long shot, but I thought maybe there was some magical solution. If it's going to exist, it would be on XDA forums.
Click to expand...
Click to collapse
nope, nothing "magical" exists. the only way to unlock your bootloader is to enable the option in developer settings first. formatting cache and userdata in fastboot should let you flash a rom via twrp.
Since no guide has been updated with information on official TWRP for root and backup reasons, I thought I'd create one.
DISCLAIMER:
To do this method requires you to unlock your bootloader. Your warranty is now void. This method assumes you have basic knowledge of ADB and Fastboot commands and know how to recover your device if you accidentally type a wrong command and now boot to TWRP and can't boot to system. If you cannot recover from this, Read up on guides to "return to stock" and familiarize yourself on how to recover your device should something go wrong.
There are two methods for root. You can flash TWRP to your boot image to be able to reboot to TWRP without a PC, or just a temp boot so you can just have root and not TWRP. I'll put in brackets the minor differences.
1: Get ready
Download latest build of TWRP img file from their website.(Previous link is to their instructions and device specific patches, download page is HERE.) {download the latest zip if you want to flash TWRP}
Download what you want on your phone (SU, Magisk, etc)
2:
Hook phone up to your PC, be sure you have latest adb/fastboot drivers. (I do not support windows related questions. If you have latest drivers, you'll have no issue with the below commands, Linux just works for this kind of thing)
3:
Navigate to your directory that has that img downloaded. (windows, shift right click and say "open command prompt here")
Type the below commands, and terminal output should be similar: (I.E. this is a copy/paste of terminal)
Main thing to remember is "Fastboot boot {filename}.img"
Code:
[email protected]:~$ adb reboot bootloader
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ fastboot boot twrp-3.2.1-1-nash.img
downloading 'boot.img'...
OKAY [ 0.841s]
booting...
OKAY [ 5.135s]
finished. total time: 5.976s
[email protected]:~/Downloads$
BE SURE TO DO BOOT AND NOT FLASH!!! (If you ask why you can no longer boot to system, I'll let you know you missed this line.)
5:
You're now in TWRP!
It will ask you for your password. This is your PIN or password to unlock your phone. Enter it.
TWRP has now decrypted your storage to read the zip file(s) you put on your phone!
Go to install and navigate to your directory where you put that file
Install Magisk/SU/TWRP/whatever you please.
(Note: some root zips require a factory reset)
6:
Reboot!
You're Done congratulations!
Attached are images if they help you see you're doing the right thing.
Special thanks @erfanoabdi @invisiblek @npjohnson @joemossjr @jbats
Without the above people a lot of what's above woudn't have been possible for this device specifically. Also, thanks to everyone who pitched in to get a device over to invisiblek. Leaps and bounds have been done since that donation. And thanks to the other devs who have invested in this phone and their time to help out.
(Quoted from Nathan Chance)
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.
Random issues post:
SU does some wonky edits to the ramdisk. It is highly suggested to flash Magisk for root.
Some have reported needing to wipe data after flashing Magisk. If you can't boot after flashing Magisk, just go back into recovery (can be twrp or stock) and wipe data/factory reset to boot again.
Note: we do not have a recovery partition. Never flash the img file! Download the flashable zip if you want twrp on your phone and flash per OP instructions.
Awesome thanks
I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo
droidgreg said:
I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo
Click to expand...
Click to collapse
Be sure to mount system under the "mount" button
I need the OCX27.1 oreo. I did a return to stock flashall to OCX27 and now reflashed TWRP and Magisk and boots fine but I lost baseband and IMEI
Added warning to OP that some root zips require a data wipe.
I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.
will4958 said:
I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.
Click to expand...
Click to collapse
This guide assumes you can unlock your bootloader. Since Verizon and AT&T feel they have a right to lock down their devices, this guide won't work. That is why I voted with my wallet and left Vz after my M7 due to them putting phone OEM's privates in a vice and forced them to lock out those carrier variants.
Has this method been tested with OCX27.1 Oreo on TMO?
droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
It probably hasn't been tested, but it should work in theory.
Uzephi said:
It probably hasn't been tested, but it should work in theory.
Click to expand...
Click to collapse
I was on 27.1 when I attempted to root and got into a bootloop and lost my baseband when I flashall back to stock OCX27. I have a feeling 27.1 update isn't compatible with this method and cannot be downgraded to even OCX 27 Oreo
so no go on 27.1 twrp? I have root on 27.1 TMO obtained post update. Obtained by fastbooting the nash twrp and running magisk 16.zip. No needing to format data or anything
I was just wondering about the installable twrp zip. I am coming from samsung development so all this A/B partitioning and some of the other partitions are new to me.
As soon as I can get twrp on the phone and feel comfortable recovering. The kernels and roms will start coming.
Feels strange not having odin to save my ass
droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
tested and working
mattlowry said:
tested and working
Click to expand...
Click to collapse
Have you actually flashed installer.zip to install TWRP or just booted TWRP and only flash magisk or SU for root without installing TWRP?
I fastboot booted the twrp. I didn't try the installer. What is it?
Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.
luponcooper said:
Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.
Click to expand...
Click to collapse
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).
Uzephi said:
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).
Click to expand...
Click to collapse
Thanks a lot uzephi for answering.
I have the 6gb ram and 64gb model, XT1789-05. I try whit no succes to install Magisk (Error1) so i made a factory reset but still doesn't boot, stays in M logo.
Im super noob, can you guide me? i dont know how to recover the boot.img.
excuse my english.
Hey, i've my mi A2 in August Patch (v9.6.10.0 ODIMIFE)
And
1. Bootloader Unlocked
2.Rooted
3.HAL3 Enabled
4.System Modified
What shoud i do to update to the latest(September) security patch.
I'm having serious wifi issue so that i'm desperate to update the latest OTA
Uinstall magisk, install ota use patched boot with magisk, ez.
T4Ump said:
Uinstall magisk, install ota use patched boot with magisk, ez.
Click to expand...
Click to collapse
This won't help him as he also modified the system partition
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
rafihasan710 said:
Hey, i've my mi A2 in August Patch (v9.6.10.0 ODIMIFE)
And
1. Bootloader Unlocked
2.Rooted
3.HAL3 Enabled
4.System Modified
What shoud i do to update to the latest(September) security patch.
I'm having serious wifi issue so that i'm desperate to update the latest OTA
Click to expand...
Click to collapse
Next to putting stock boot you need to flash system partition again. Backup your data first just to be sure you have it before you might need to flash the complete August image
Benjamin_L said:
This won't help him as he also modified the system partition
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
Next to putting stock boot you need to flash system partition again. Backup your data first just to be sure you have it before you might need to flash the complete August image
Click to expand...
Click to collapse
Im idiot, i was wrong Yea, put stock boot and install ota then patched boot
T4Ump said:
Im idiot, i was wrong Yea, put stock boot and install ota then patched boot
Click to expand...
Click to collapse
This won't be enough if he mounted or modified system partition as he said. Ota will still fail even with stock boot.
Benjamin_L said:
This won't be enough if he mounted or modified system partition as he said. Ota will still fail even with stock boot.
Click to expand...
Click to collapse
I disabled all magisk plugins, camera api, ios emoji, etc ****s after this i flash stock boot and install ota works.
T4Ump said:
I disabled all magisk plugins, camera api, ios emoji, etc ****s after this i flash stock boot and install ota works.
Click to expand...
Click to collapse
Depends on what you do. I used AdBlock and restoring stock boot was not enough for me that time
If you modified anything directly in system then your only option is to download the full rom and flash it with fastboot
http://bigota.d.miui.com/V9.6.13.0....0.ODIMIFE_20180913.0000.00_8.1_fbd1120565.tgz
Backup your data first and be careful, it will will wipe your data by default
I updated the toolkit to force update using fastboot. just run the unbrick option. Make sure to make a backup first, just in case
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Edit: Also, if you have any bugs please let me know, I can fix it today.
Nebrassy said:
If you modified anything directly in system then your only option is to download the full rom and flash it with fastboot
http://bigota.d.miui.com/V9.6.13.0....0.ODIMIFE_20180913.0000.00_8.1_fbd1120565.tgz
Backup your data first and be careful, it will will wipe your data by default
Click to expand...
Click to collapse
Is there any way i can do this without wiping my data?
rafihasan710 said:
Is there any way i can do this without wiping my data?
Click to expand...
Click to collapse
I guess you can, choose clean all, and flash_all_except_data.bat in the corner in miflash, careful not to choose lock
but you should take a backup anyway, you never know
Nebrassy said:
I guess you can, choose clean all, and flash_all_except_data.bat in the corner in miflash, careful not to choose lock
but you should take a backup anyway, you never know
Click to expand...
Click to collapse
Can You Please Explain the whole procedure step by step....
Sorry...i'm a noob
rafihasan710 said:
Can You Please Explain the whole procedure step by step....
Sorry...i'm a noob
Click to expand...
Click to collapse
http://en.miui.com/a-232.html
rafihasan710 said:
Is there any way i can do this without wiping my data?
Click to expand...
Click to collapse
You do not need to flash all. Yesterday I have updated my unlocked and rooted phone with changed system partition without any trouble, and all my apps and data are still with me. Just flash stock system and boot images via fastboot, then make OTA update. Then copy new stock boot.img to your phone, open Magisk Manager, click Install, patch boot.img, copy patched_boot.img back to PC and flash it via fastboot. That is all. For me the most difficult part was to wait for downloading 3 Gb of data from terribly slow miui.com.
drauger said:
You do not need to flash all. Yesterday I have updated my unlocked and rooted phone with changed system partition without any trouble, and all my apps and data are still with me. Just flash stock system and boot images via fastboot, then make OTA update. Then copy new stock boot.img to your phone, open Magisk Manager, click Install, patch boot.img, copy patched_boot.img back to PC and flash it via fastboot. That is all. For me the most difficult part was to wait for downloading 3 Gb of data from terribly slow miui.com.
Click to expand...
Click to collapse
Can You Provide me the necessary file links.
By the way, Thank You Very Much.
drauger said:
You do not need to flash all. Yesterday I have updated my unlocked and rooted phone with changed system partition without any trouble, and all my apps and data are still with me. Just flash stock system and boot images via fastboot, then make OTA update. Then copy new stock boot.img to your phone, open Magisk Manager, click Install, patch boot.img, copy patched_boot.img back to PC and flash it via fastboot. That is all. For me the most difficult part was to wait for downloading 3 Gb of data from terribly slow miui.com.
Click to expand...
Click to collapse
And please provide the fastboot commands for flashing all of those.
rafihasan710 said:
And please provide the fastboot commands for flashing all of those.
Click to expand...
Click to collapse
Did you do some research by yourself or are you expecting others to do the work for you? It's really not that hard..
Benjamin_L said:
Did you do some research by yourself or are you expecting others to do the work for you? It's really not that hard..
Click to expand...
Click to collapse
I'm sorry for that.
But as you've done this before so i just want to follow your proceedure strictly.
I don't want my phone to be bricked.
If you can help please do...
rafihasan710 said:
I'm sorry for that.
But as you've done this before so i just want to follow your proceedure strictly.
I don't want my phone to be bricked.
If you can help please do...
Click to expand...
Click to collapse
I understand your fear but try looking for commands and procedures yourself in the first place and then ask if this is right. Will help you more than just copy pasting stuff, you don't understand. This way you will become knowledgeable yourself but it takes time of course. Don't fear!
Benjamin_L said:
I understand your fear but try looking for commands and procedures yourself in the first place and then ask if this is right. Will help you more than just copy pasting stuff, you don't understand. This way you will become knowledgeable yourself but it takes time of course. Don't fear!
Click to expand...
Click to collapse
Thank You
Alot of people still dont seem to understand or know how to root their devices and the help ppl find online can be misleading and sketchy. I just want to share this easy method to hopefully save some ppl from trying to do this or that and having bad results. This IS the common sense duh way to root. Use magisk to root it. Long as you got adb and fastboot on ur pc and the phone's bootloader is unlocked you can root like this...
1)download the magisk manager.
2)get the ota .zip file for the android version you are running.
3)get payload-dumperwin64.zip and unzip it.
4)unzip the ota.
5)put the payload.bin file from the ota into the input folder for payload dumper.
6)run payload dumper.
7)get the boot.img from the output folder of the payload dumper.
8)copy the boot.img to your phone.
9)open magisk manager.
10)press install, then install, then 'select and patch a file'.
11)select the boot.img
12)once the boot.img is patched it will be renamed magisk_patched.img, copy the magisk_patched.img to your computer.
13)start your phone in fastboot mode
14)on your computer open a command prompt and type 'fastboot flash boot (and the magisk_patched.img file location)'
15)once successful type 'fastboot reboot'
ROoT! Super easy right? And yes, it works with 10 stable. Just make sure to use magisk manager 20.1.
As far as twrp goes, you can try flashing it with magisk if you like, but I can't say whether or not it will work on 10 because I didnt bother. Twrp hasnt been very helpful to me on my 6T.
I know to a lot of us this is pretty common sense, but it looks like there are still a lot of ppl needing help getting rooted on 10 stable for some reason... Thats why I posted this. Don't hate. Help.
<Mod edit>
To install TWRP,
download - android Q twrp img and the installer zip. Place the TWRP installer zip in your phone storage.
download magisk installer zip into your phone storage.
1. boot in fastboot, open command line in your PC.
2. flash twrp img - fastboot flash boot <your twrp>.img. You lose root and custom kernel here.
(fastboot boot <your twrp>.img for android 9.)
3. Reboot to recovery from phone's fastboot menu
4. install the <TWRP installer>.zip file in TWRP.
5. Reboot TWRP to flash magisk.
6. Flash <magisk installer>.zip in TWRP
7. Reboot system. Exit your command line on PC.
The end.
Can't we just flash Magisk on TWRP?
yot2703 said:
Can't we just flash Magisk on TWRP?
Click to expand...
Click to collapse
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
e5p10nage said:
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
Click to expand...
Click to collapse
Seeing as how I haven't made a reliable backup in TWRP/custom recoveries in like two years, I appreciate this route. Swift Backup and frequent OTG backups are enough for me, I just want root.
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Striatum_bdr said:
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Click to expand...
Click to collapse
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
e5p10nage said:
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
Click to expand...
Click to collapse
No it doesn't work at all forever. Fastboot is modified in 10 you must write 'fastboot flash boot file.img'
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
UberFiend said:
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Click to expand...
Click to collapse
I have heard of that being a bug with Q. Just look it up on google. Lots of pixel owners havin that same issue. I didnt have this problem, so I am not sure what caused it or how to fix it. You FOR SURE used the boot.img from the ota you currently have installed? Anyway, I think I saw someone say something about the throttling in the developer settings.. IDK if that really has anything to do with it though.. Im sorry that happened though.
greentag said:
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
Click to expand...
Click to collapse
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
e5p10nage said:
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
Click to expand...
Click to collapse
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
greentag said:
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
Click to expand...
Click to collapse
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Tl;dr: this is not THE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
Tl;dr: this is notTHE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
e5p10nage said:
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
Click to expand...
Click to collapse
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
e5p10nage said:
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
Click to expand...
Click to collapse
The payload dumper thing I was talking about is a method of obtaining the boot.img from the ota on your own instead of looking for one on the web. Doesnt matter what payload dumper you use, that was just the one I found. Hopefully this makes it a lil more clear.
e5p10nage said:
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Click to expand...
Click to collapse
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
greentag said:
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
Click to expand...
Click to collapse
I see. Well I am glad you pointed this out cuz I wasnt aware of the need to factory reset. The only reason I did is because after the local upgrade my phone wouldnt boot to anything but recovery UNLESS I reset it. So I didnt have an option not to really. I was rooted with twrp on 9.0.17, got the ota from oxy updater, local updated, just like ya said you did. Not sure why it wouldnt boot after that without the reset. Im not entirely sure that it is 100% needed to factory reset to root this way though. Ive talked to other people who tried this and said they had no problem. Then Ive also talked to other people who have. I feel like there are some variables we arent considering at work here. But thank you for pointing this out. The only goal I have here is to be helpful, so all problems with this method also need to be part of the conversation. So I appreciate it.
I was wondering is there any RP2 ROMS like Lineage os or other ROMS? Or not yet or it's not possible to make for this kind of phone or maybe i didn't search more to know what's going on??
No specific ROM for RP2 but you can install GSI ROM after unlocking your bootloader.
Peace
chris5s said:
No specific ROM for RP2 but you can install GSI ROM after unlocking your bootloader.
Peace
Click to expand...
Click to collapse
Okay Thanks for the info, But i'm trying to root my phone on mr2 i can't find any thread that shows how to root mr2 with steps ??
I'm on MR 2 as well. Follow these steps :-
Unlock bootloader.
Flash Arter's kernel from bootloader mode. Then boot into TWRP recovery (comes with Arters kernel) and from there flash latest Magisk zip to get root.
Peace
chris5s said:
I'm on MR 2 as well. Follow these steps :-
Unlock bootloader.
Flash Arter's kernel from bootloader mode. Then boot into TWRP recovery (comes with Arters kernel) and from there flash latest Magisk zip to get root.
Peace
Click to expand...
Click to collapse
Doesn't work on MR2 December realeas i tried and it bricked my phone any other way?
AssyrianHero said:
Doesn't work on MR2 December realeas i tried and it bricked my phone any other way?
Click to expand...
Click to collapse
Yes it does you have to flash the global version NOT the AT&T version.
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3123-user-full.zip
JDBarlow said:
Yes it does you have to flash the global version NOT the AT&T version.
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3123-user-full.zip
Click to expand...
Click to collapse
Yes this is what i'm flashing "aura-p-release-3123-user-full" its global version and i think i'm doing something wrong can you explain step by step instructions? cause i'm new to RP2 and i'm used to old simple root method
Have you tried flashing Arter's kernel then reboot into system before trying to root?
If that works then maybe it's the rooting that's bricking the phone?
Which version of Magisk are you trying to flash?
chris5s said:
Have you tried flashing Arter's kernel then reboot into system before trying to root?
If that works then maybe it's the rooting that's bricking the phone?
Which version of Magisk are you trying to flash?
Click to expand...
Click to collapse
The problem there is no steps that shows what to do I'm just using my own steps, and I'm not using any Magisk I'm just trying to flash Arter's kernel.
Maybe explain what steps you are doing and what errors you are getting then?
Can you put the phone into bootloader mode? Is it unlocked? Do you have adb and do you know how to use it?
Peace.
AssyrianHero said:
Yes this is what i'm flashing "aura-p-release-3123-user-full" its global version and i think i'm doing something wrong can you explain step by step instructions? cause i'm new to RP2 and i'm used to old simple root method
Click to expand...
Click to collapse
Honestly it's easier to root phones today than it ever has especially the RP2.
If you are truly unlocked this should only take you minutes to do.
First things first. Open a terminal where you have ADB / FASTBOOT installed or if you setup the attributes properly just open a terminal.
Type adb devices and it should give you your serial number of your phone. If not adb isn't installed properly.
If so, type adb reboot bootloader and phone will boot to bootloader.
Type fastboot devices and again it should give you the phones ID. If not fastboot isn't installed properly.
If so, type fastboot flash boot and the name of your arter97 file.img this will also install TWRP.
After installation from bootloader menu scroll down to reboot recovery and it should boot to TWRP.
Click cancel then swipe to allow modifications. In TWRP menu select INSTALL then choose where you've saved the magisk 20.3 file on your SD or internal drive.
After installation reboot system then install magisk manager if not already installed. At this point you're rooted. Have a great weekend!!
Good luck! :good:
Make sure you have unlocked your phone, suggest following razer official instruction.(new xda user cant post outside link, search it)
1.Unlock the Bootloader 2.Unlock the Bootloader Critical Partitions 3.Flash official System Image
And please note unlock will erases all user data on the Phone!
After unlocked your phone you can flash arter97 kernel or f(x)THaxxorX TrinityKernel. Both of them contain TWRP, install Magisk Manager and flash Magisk in TWRP. Get rooted.
chris5s said:
Maybe explain what steps you are doing and what errors you are getting then?
Can you put the phone into bootloader mode? Is it unlocked? Do you have adb and do you know how to use it?
Peace.
Click to expand...
Click to collapse
The bootloader is unlocked i do have adb and i i know how to use it I've been rooting all my phones HTC M9 Samsung S7-8-9 and OnePlus 7 I've rooted too many phones but this one is little bit different than others i tried my own steps like i used to do:
I reboot my phone into bootloader and type fastboot devices and it gives me the Serial number and i then i type fastboot boot boot.img i don't know if this command works with this phone it actually worked with other phones this one not..
finixs said:
Make sure you have unlocked your phone, suggest following razer official instruction.(new xda user cant post outside link, search it)
1.Unlock the Bootloader 2.Unlock the Bootloader Critical Partitions 3.Flash official System Image
And please note unlock will erases all user data on the Phone!
After unlocked your phone you can flash arter97 kernel or f(x)THaxxorX TrinityKernel. Both of them contain TWRP, install Magisk Manager and flash Magisk in TWRP. Get rooted.
Click to expand...
Click to collapse
How to unlock the Bootloader Critical Partitions? I think i missed this step i have the bootloader unlocked..
Look on the Razer website for the specific instructions to unlock bootloader/critical.
The fastboot command to flash a boot img is
fastboot flash boot boot.img
Peace
AssyrianHero said:
How to unlock the Bootloader Critical Partitions? I think i missed this step i have the bootloader unlocked..
Click to expand...
Click to collapse
"fastboot flashing unlock" unlock bootloader
"fastboot flashing unlock_critical" unlock the bootloader critical partitions
Also, make sure you're using the Razer recommended USB cord and ADB/Fastboot.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Cables
When connecting your Razer Phone to a computer for any development, it is advised by Razer to not use the in-box USB Type-C to Type-C charging cable for flashing. The supplied cable is specifically engineered for fast power delivery, not for data transfer. Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Upgrade your ADB/Fastboot here.