Related
Get the method from here:
https://bbs.htc.com/cn/thread-109059-1-1.html
----------
This method seems to modify the original system version number so that the old version of the RUU file can pass the checking.
--------------------
Backup your data before downgrading.
--------------------
1. Download the RUU file which is the version you need.
2. Reboot to download mode, then flash the TWRP via fastboot.
Unofficial TWRP for U11+: https://forum.xda-developers.com/htc-u11/development/unofficial-htc-u11-twrp-recovery-t3706264
Fastboot command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
3. Reboot to recovery mode, then get sde1 file by :
adb pull /dev/block/sde1
Click to expand...
Click to collapse
4. Open the file with a text editor and change the version number, which is easy to found, to the version number of your RUU file.
5. Push back the file by
adb push sde1 /dev/block
Click to expand...
Click to collapse
If it shows "does not have enough space", delete the original file by the files manager in the recovery first.
6. Flash your RUU file by entering into the download mode after copying it to the SD card.
Tested on U11+ China version, no problems found.
Hope this can help you.
handsome_hell said:
Get the method from here:
https://bbs.htc.com/cn/thread-109059-1-1.html
----------
This method seems to modify the original system version number so that the old version of the RUU file can pass the checking.
--------------------
Backup your data before downgrading.
--------------------
1. Download the RUU file which is the version you need.
2. Reboot to download mode, then flash the TWRP via fastboot.
Unofficial TWRP for U11+: https://forum.xda-developers.com/htc-u11/development/unofficial-htc-u11-twrp-recovery-t3706264
Fastboot command:
fastboot flash recovery recovery.img
3. Reboot to recovery mode, then get sde1 file by :
adb pull /dev/block/sde1
4. Open the file with a text editor and change the version number, which is easy to found, to the version number of your RUU file.
5. Push back the file by
adb push sde1 /dev/block
If it shows "does not have enough space", delete the original file by the files manager in the recovery first.
6. Flash your RUU file by entering into the download mode after copying it to the SD card.
Tested on U11+ China version, no problems found.
Hope this can help you.
Click to expand...
Click to collapse
Wow great news mate. i'll try now and post results. Thank's !!!
Great, it works! I downgraded to India_SEA 1.10.400.23 and now updating via OTA to 1.24.400.4 (as what i was looking for). Thanks a lot!
sotong said:
Great, it works! I downgraded to India_SEA 1.10.400.23 and now updating via OTA to 1.24.400.4 (as what i was looking for). Thanks a lot!
Click to expand...
Click to collapse
Hi mate, one question...to get OTA Updates i need relock bootloader and get stock recovery ?. Thank's
neofrost37 said:
Hi mate, one question...to get OTA Updates i need relock bootloader and get stock recovery ?. Thank's
Click to expand...
Click to collapse
You don't need to relock bootloader, but you have to get stock recovery.
neofrost37 said:
Hi mate, one question...to get OTA Updates i need relock bootloader and get stock recovery ?. Thank's
Click to expand...
Click to collapse
Yup, as OP stated, you only need the stock recovery. I relocked my bootloader anyway though
can u post software download link?
lohimami said:
can u post software download link?
Click to expand...
Click to collapse
You can look for it here:
https://forum.xda-developers.com/htc-u11/how-to/stock-recovery-taiwan-version-1-10-709-t3719599
or:
https://androidfilehost.com/?w=search&s=2Q4DIMG
handsome_hell said:
You can look for it here:
https://forum.xda-developers.com/htc-u11/how-to/stock-recovery-taiwan-version-1-10-709-t3719599
or:
https://androidfilehost.com/?w=search&s=2Q4DIMG
Click to expand...
Click to collapse
Thanks 4 ur help. But i want to download these file as below:
https://drive.google.com/file/d/18Fj2gHuw4TeM39oR--uhsC2OUDXn4hlm/view?usp=sharing
lohimami said:
Thanks 4 ur help. But i want to download these file as below:
https://drive.google.com/file/d/18Fj2gHuw4TeM39oR--uhsC2OUDXn4hlm/view?usp=sharing
Click to expand...
Click to collapse
I don't have ADB tools for Windows...
Maybe you can try this:
https://www.google.co.id/amp/s/www.xda-developers.com/install-adb-windows-macos-linux/amp/
Tested. Ok on HTC__621 taiwan device.
Thanks for the guide. Does it work if you swiped to "allow system modification" in twrp?
HTC U11 Plus is base on android oreo.
I think you can flash ruu normally.
You can flash older version of RUU follow software number and it's same version android.
If you want to rollback from new version android ,this method is important.
Ex RUU 1.xx.400.x Android 8.0
Your devices is software number 1.24.400.x ,Android 8.0
You can use Ruu above for flash your device.
schranzl said:
Thanks for the guide. Does it work if you swiped to "allow system modification" in twrp?
Click to expand...
Click to collapse
Of course, why I would find this method is to restore the modified system partition.
Deleted
sotong said:
Great, it works! I downgraded to India_SEA 1.10.400.23 and now updating via OTA to 1.24.400.4 (as what i was looking for). Thanks a lot!
Click to expand...
Click to collapse
hi Sotong rom India_SEA 1.10.400.23 for what is CID?
Hey Guys, would this procedure work if i would like to return the phone to stock with custom rom??
By the way, is it possible to pull the sde1 without flashing the trwp recovery image?
I have tried to pull the file with the following steps and it is a success but not sure if the file is okay:
adb root
adb pull /dev/block/sde1
I can see the version number in the file with notepad++
Please advise. thanks.
sotong said:
Yup, as OP stated, you only need the stock recovery. I relocked my bootloader anyway though
Click to expand...
Click to collapse
How do you relock your bootloader???
I managed to flash to stock but the bootloader remain unlock.
Please help.
Hi all,
Managed to get reload the stock rom and re-lock the bootloader.
Thanks.
Do I need TWRP and SD card?
Can I just use fastoot/adb and flash from PC directly?
Also what images are needed? I only have boot system and recovery stock images. Is that good enough?
Hi Guys,
Note : By doing this, you know that you're gonna do a modification to your phone, and im not in any way, responsible for what happen after. Escape Route for if something wrong happen is provided, but YOU DO THIS ON YOUR OWN RISK
since this phone is fairly new, at this moment a clear rooting method haven't established yet. This is what this thread for.
Based on information gathered from P20 Lite Forum (the rooting guide for that device even already up - here), it seems the old trick of rooting (from Mate 10 Pro) using Patched Boot Method is working fine. And Magisk is working
Basically this method need few pre-requisites :
1. Unlocked Bootloader (by getting the code here ) - and if you not sure how to do it, go here for the guide
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
3. Magisk Manager 5.5.4 (from Magisk Thread) to patch the .img above, or
4. Patched RAMDISK image (i patched it) from here
5. and of course computer with ADB & Fastboot installed (make sure you have latest SDK to prevent something not working)
Now, to Root it, all you need to do is,
1. Boot into bootloader
2. Type
Code:
fastboot flash ramdisk patched_boot.img
(patched_boot.img is the file you download from prerequisites number 4, placed it in the same directory with your adb & fastboot - i assume you know that already)
3. Reboot
4. You now should have root access, download Magisk Manager to manage modules and superuser
(you might need to flash this module if you failed to pass safetynet)
In case something go wrong, flash back the stock RAMDISK from pre-requistes number 2 above using same method as what u did to flash the patched one.
That way worked. Thanks.
Edit:
Just as a hint. To get magisk work as it should..
After boot into the system and installed Magisk Manager, install Magisk from there again, so you dont get any /data/magisk problems.
SafteyNet passed then.
Fingers crossed twrp is possible soon
Works on CLT-L09
I have a German single Sim from Vodafone tested the root yesterday and works very well
Would this method work on CLT-L09 model? Thanks
danifilth4king said:
Would this method work on CLT-L09 model? Thanks
Click to expand...
Click to collapse
The post before you just confirmed yourbquestion, LoL
Yes it does
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
otonieru said:
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
Click to expand...
Click to collapse
fl4r3 said:
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
Click to expand...
Click to collapse
It's from www.allrom.ir (its in persian) and there's another site, rusian one if am not mistaken, but i forget the exact address
Great, thanks for that! I managed to find it on allrom.ir
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
danifilth4king said:
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
Click to expand...
Click to collapse
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
otonieru said:
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
Click to expand...
Click to collapse
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
danifilth4king said:
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
Click to expand...
Click to collapse
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
otonieru said:
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
Click to expand...
Click to collapse
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
danifilth4king said:
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
Click to expand...
Click to collapse
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
otonieru said:
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
Click to expand...
Click to collapse
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
danifilth4king said:
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
Click to expand...
Click to collapse
Its better to do it from ON state, and use adb reboot bootloader command
otonieru said:
Its better to do it from ON state, and use adb reboot bootloader command
Click to expand...
Click to collapse
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Put the device off and hold power button and volume down. You should come directly into the rescue mode.
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Ah, sorry, i got it wrong. Yes, its power n volume down.
Oneplus updated the OnePlus 6's Bootloader and you may ask yourself 'Can i still root?'
The answer is yes. It is easy.
1. At first, your bootloader has to be unlocked
2. Just download the Twrp.img and the Twrp installer from twrp.me, then the latest magisk installer
3. Put the magisk.zip and twrp installer zip into the root of your device and boot into bootloader
4. Now you have to open a new shell or cmd window in your adb folder, then type "Fastboot devices" there
5. If your phone is recognized, then do this command: " fastboot boot .\twrp-3.2.1-0-enchilada.img"
6. The op6 should boot into the TWRP, there type in your pincode, pattern, or what so ever you have. If you get a message because of system modification, click 'Keep read only'
7. Go to 'Install', then flash the TWRP installer zip, then magisk right after it
8. Just reboot and enjoy
The procedure is the same as always. I can confirm it's working because i rooted a few minutes ago
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
iElvis said:
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
Click to expand...
Click to collapse
Forgot the mention that, thanks!
Edit: Screenshots
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Sorry, I thought that would be helpful for people who are worried about root because of updated bootloader.
A Moderator can remove this thread then
joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Based on how things have been going so far, people are going to be asking. Just saying.
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
So if I already have twrp and Magisk installed is the method still the same?
Will this update lock the bootloader back?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
joemossjr said:
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
Click to expand...
Click to collapse
Yes I know. I mean, you're right. Thought something like "new bootloader, new confusions". I justed wanted to help people if they're worried of a brick
dgunn said:
So if I already have twrp and Magisk installed is the method still the same?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
Click to expand...
Click to collapse
Don't worry. You can use TWRP and your phone itself as always
Sconny said:
Don't worry. You can use TWRP and your phone itself as always
Click to expand...
Click to collapse
So do I flash the update in twrp?
Must the bootloader be unlocked again?
dgunn said:
So do I flash the update in twrp?
Must the bootloader be unlocked again?
Click to expand...
Click to collapse
No you flash in system via local upgrade
joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash with local upgrade, reboot to fastboot, run twrp.img, install twrp, flash Magisk and reboot? No unlocking bootloader again?
If not correct please tell me
Yup that's it
joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
BossNexusS said:
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
Click to expand...
Click to collapse
Yes
joemossjr said:
Yes
Click to expand...
Click to collapse
What were the steps you followed if you don't mind?
Maybe someone will upload the full rom?
anyone tried hiding system updates inside magisk hide ?
it now shows only 224 update (canadian vpn), hence don't know what it will do when you take that route, anyone ?
Does anyone happen to have this? I used the 9.5.3 img for the TWRP with working decrypt, and it booted fine once, however now it keeps booting back to TWRP despite selecting "reboot system." I think someone mentioned they had it, but I can't find it for the life of me. Thanks so much!
No, don't think there are any full zips for T-Mo yet.
Bradl79 said:
No, don't think there are any full zips for T-Mo yet.
Click to expand...
Click to collapse
Thanks for the heads-up I actually got it to boot again by flashing SkyDragon kernel and Magisk!
sabrdawg said:
Thanks for the heads-up I actually got it to boot again by flashing SkyDragon kernel and Magisk!
Click to expand...
Click to collapse
How did this fix the boot image? How did your flash TWRP? The one with decryption or no?
photolarry said:
How did this fix the boot image? How did your flash TWRP? The one with decryption or no?
Click to expand...
Click to collapse
I flashed the TWRP with working decrypt. The only problem is, is that I just tried restoring a backup with it, and now I can't get out of fastboot mode. Downloading MSM Tool now :/
MSM Tool?
sabrdawg said:
I flashed the TWRP with working decrypt. The only problem is, is that I just tried restoring a backup with it, and now I can't get out of fastboot mode. Downloading MSM Tool now :/
Click to expand...
Click to collapse
Where is it? They said it is not out yet.
Here you go
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
In case you still need it, I'm fairly certain this is the boot image for GM31CB 9.5.5. I extracted it from my own device when I was flashing the international firmware. I will be honest, it might have the Chinese TWRP patched in. I doubt it though since it I can't find any of the TWRP files in the decompiled image.
https://drive.google.com/open?id=1nla0OCUpFL01CnVM5vm0G4aQ1gZ6cupI
bmg1001 said:
In case you still need it, I'm fairly certain this is the boot image for GM31CB 9.5.5. I extracted it from my own device when I was flashing the international firmware. I will be honest, it might have the Chinese TWRP patched in. I doubt it though since it I can't find any of the TWRP files in the decompiled image.
https://drive.google.com/open?id=1nla0OCUpFL01CnVM5vm0G4aQ1gZ6cupI
Click to expand...
Click to collapse
Thank you!
bmg1001 said:
In case you still need it, I'm fairly certain this is the boot image for GM31CB 9.5.5. I extracted it from my own device when I was flashing the international firmware. I will be honest, it might have the Chinese TWRP patched in. I doubt it though since it I can't find any of the TWRP files in the decompiled image.
https://drive.google.com/open?id=1nla0OCUpFL01CnVM5vm0G4aQ1gZ6cupI
Click to expand...
Click to collapse
You had to root in order to extract boot IMG correct?
Nekromantik said:
You had to root in order to extract boot IMG correct?
Click to expand...
Click to collapse
No, I flashed TWRP to the opposite partition and extracted it there.
bmg1001 said:
No, I flashed TWRP to the opposite partition and extracted it there.
Click to expand...
Click to collapse
hmm
the instructions for installing twrp mentions having stock boot.img in order to install it
how did you flash to second slot without a stock boot.img?
Nekromantik said:
hmm
the instructions for installing twrp mentions having stock boot.img in order to install it
how did you flash to second slot without a stock boot.img?
Click to expand...
Click to collapse
I didn't use the guide. I flashed TWRP (the TWRP image that is provided in that same thread) to the opposite partition.
bmg1001 said:
I didn't use the guide. I flashed TWRP (the TWRP image that is provided in that same thread) to the opposite partition.
Click to expand...
Click to collapse
ah ok
not sure I wanna risk anything as no msmtool guaranteed for the 5g version.
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
Code:
fastboot flash recovery recovery_op7t_adb_10.0.0.7_by_Killswitch.img
reboot into recovery u can use as well:
Code:
fastboot reboot recovery
you can follow this guide on how to remove magisk modules
Download: GDrive
Enjoy and good luck!
I am assuming it will work on other versions as well like OOS 10.3.0 India.
Sent from my OnePlus7T using XDA Labs
I have a quation. If I have last rom 1.0.0.7, I do not have stock recovery on my telephone?
zioloiso said:
I have a quation. If I have last rom 1.0.0.7, I do not have stock recovery on my telephone?
Click to expand...
Click to collapse
Yes, this here is that stock recovery WITH ADB ENABLED.
iruiz2 said:
Yes, this here is that stock recovery WITH ADB ENABLED.
Click to expand...
Click to collapse
default recovery is without ADB Enabled?
zioloiso said:
default recovery is without ADB Enabled?
Click to expand...
Click to collapse
no stock recovery does not come with module enabled...you can try it yourself just boot to recovery and try adb shell
thats why i did it.
parag60288 said:
I am assuming it will work on other versions as well like OOS 10.3.0 India.
Sent from my OnePlus7T using XDA Labs
Click to expand...
Click to collapse
believe it should its just a recovery, i believe the ROM localization is where the real difference is...the stock recovery eitherway comes in some chinese and english...no indian language.. and in the end you can still reflash stock if you need to do anything there with it. Eventhou i am flashing only through bootloader...never really used it except adb shell
killswitx said:
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
Code:
fastboot flash recovery recovery_op7t_adb_10.0.0.7_by_Killswitch.img
reboot into recovery u can use as well:
Code:
fastboot reboot recovery
you can follow this guide on how to remove magisk modules
Download: GDrive
Enjoy and good luck!
Click to expand...
Click to collapse
Man, this is a great post. Thank you. May I ask what you did to enable ADB shell? Did you modify default.prop in the ramdisk?
bynarie said:
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
reboot into recovery u can use as well:
Man, this is a great post. Thank you. May I ask what you did to enable ADB shell? Did you modify default.prop in the ramdisk?
Click to expand...
Click to collapse
https://forum.xda-developers.com/7t...n-os-stock-recovery-adb-t3991865/post80866897
Sent from my OnePlus7TPro using XDA Labs
In theory, we should be able to make a backup of our own boot.img with this?
qbanlinxx said:
In theory, we should be able to make a backup of our own boot.img with this?
Click to expand...
Click to collapse
Yea im trying it right now..
Is this the right path?
/dev/block/bootdevice/by-name/boot_a
/dev/block/bootdevice/by-name/boot_b
Edit:
Yea its the right path. The img can be patched with Magisk and you can root the device by flashing the boot.img
qbanlinxx said:
In theory, we should be able to make a backup of our own boot.img with this?
Click to expand...
Click to collapse
I just DD'd boot.img. This seemed to work for backing up partitions.
Recovery images don't differ across variant models do they?
This would work on global version for instance?
shorty1993 said:
Recovery images don't differ across variant models do they?
This would work on global version for instance?
Click to expand...
Click to collapse
If it doesn't work, I have a Global insecure 1.0.0.7 recovery image I could share.
grandpajiver said:
If it doesn't work, I have a Global insecure 1.0.0.7 recovery image I could share.
Click to expand...
Click to collapse
Please do. Would rather use the global if possible.
shorty1993 said:
Please do. Would rather use the global if possible.
Click to expand...
Click to collapse
Hi,
Here's a link to Google Drive for 1.0.0.7 Global ADB-enabled stock recovery:
https://drive.google.com/open?id=1e59CRQKJ9ymBKui2mtCrnbLhZ06ukvYe
Reboot your phone to fastboot (bootloader).
fastboot reboot fastboot to get to FastbootB or whatever its called. It'll look like stock recovery.
Fastboot flash recovery insecure_recovery_GLO_1007.img
Reboot.
Profit.
grandpajiver said:
Hi,
Here's a link to Google Drive for 1.0.0.7 Global ADB-enabled stock recovery:
https://drive.google.com/open?id=1e59CRQKJ9ymBKui2mtCrnbLhZ06ukvYe
Reboot your phone to fastboot (bootloader).
fastboot reboot fastboot to get to FastbootB or whatever its called. It'll look like stock recovery.
Fastboot flash recovery insecure_recovery_GLO_1007.img
Reboot.
Profit.
Click to expand...
Click to collapse
Are there differences between the Global and EU recoveries?
iruiz2 said:
Are there differences between the Global and EU recoveries?
Click to expand...
Click to collapse
wouldn't say there ist much difference.. its just recovery
Sent from my [device_name] using XDA-Developers Legacy app
obol2 said:
Yea im trying it right now..
Is this the right path?
/dev/block/bootdevice/by-name/boot_a
/dev/block/bootdevice/by-name/boot_b
Edit:
Yea its the right path. The img can be patched with Magisk and you can root the device by flashing the boot.img
Click to expand...
Click to collapse
Can you please explain me how you did it ?
samyhaff said:
Can you please explain me how you did it ?
Click to expand...
Click to collapse
Boot into recovery, go in cmd and type adb.
type
dd if=/dev/block/bootdevice/by-name/boot_a of =/data/media/0/nameoffile.img
dd if=/dev/block/bootdevice/by-name/boot_b of =/data/media/0/nameoffile.img
patch one of them in magisk manager, fastboot boot patched img, direct install magisk in magisk manager