lg g4 bootloop after twrp and supersu - G4 Q&A, Help & Troubleshooting

so i tried rooting my g4 h815. i followed multiple guides and got bootloader unlocked and twrp installed it however bootlooped after flashing supersu. i restarted the phone and went into recovery mode and hit yes to enter twrp it however did not go into twrp and now no longer boots... anybody got an idea how to fix this?
Anna

just_anna said:
so i tried rooting my g4 h815. i followed multiple guides and got bootloader unlocked and twrp installed it however bootlooped after flashing supersu. i restarted the phone and went into recovery mode and hit yes to enter twrp it however did not go into twrp and now no longer boots... anybody got an idea how to fix this?
Anna
Click to expand...
Click to collapse
Without knowing exactly what you have done, it is pretty well impossible to give any helpful suggestions. You will have to be more specific.
- what model of LG G4 do you have? H815, H811, H810, H812 ..... ?
- what guides did you follow?
- exactly how did you unlock your bootloader?
- what TWRP version did you install? Did you follow the installation process in the LG G4 TWRP thread?
- did you flash a custom rom, if so what one? What SUperSU version did you install?
- etc., etc.

sdembiske said:
Without knowing exactly what you have done, it is pretty well impossible to give any helpful suggestions. You will have to be more specific.
- what model of LG G4 do you have? H815, H811, H810, H812 ..... ?
- what guides did you follow?
- exactly how did you unlock your bootloader?
- what TWRP version did you install? Did you follow the installation process in the LG G4 TWRP thread?
- did you flash a custom rom, if so what one? What SUperSU version did you install?
- etc., etc.
Click to expand...
Click to collapse
i used the following quides and used the official lg method of unlocking the bootloader
https://www.youtube.com/watch?v=skmGRgfx2V8
https://www.**************/install-twrp-recovery-on-lg-g4-international-variant/
https://www.**************/how-to-root-lg-g4-h815-using-supersu/
https://forum.xda-developers.com/g4/general/discussion-unlock-root-situations-please-t3122752
and downloaded twrp and supersu from the following sites
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
https://dl.twrp.me/g4/twrp-2.8.6.0-h815.img.html

just_anna said:
i used the following quides and used the official lg method of unlocking the bootloader
https://www.youtube.com/watch?v=skmGRgfx2V8
https://www.**************/install-twrp-recovery-on-lg-g4-international-variant/
https://www.**************/how-to-root-lg-g4-h815-using-supersu/
https://forum.xda-developers.com/g4/general/discussion-unlock-root-situations-please-t3122752
and downloaded twrp and supersu from the following sites
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
https://dl.twrp.me/g4/twrp-2.8.6.0-h815.img.html
Click to expand...
Click to collapse
OK, so as you were able to unlock your H815 Officially(H815 Europe version?), there shouldn't be a problem there if you did everything correctly.
That leaves TWRP version and SuperSU where the problem is most likely arising from.
Wipe your Cache & Dalvik cache in TWRP if it's functioning
Then, go to the TWRP site I linked in my previous post that is specific for the LG G4 and find and download the latest preview version you require for the firmware you currently have installed (I'm presuming Marshmallow [M]?). Follow the fastboot flashing method as exactly outlined there.
Next, if you really require SuperSu* (no longer currently supported or updated and free version removed from Play Store) you want to use SuperSU v2.82.
* I would however, recommend Magisk for your root program - it is currently supported and updated frequently. Download the latest ZIP and apk versions abd install them.
** You will have to uninstall SuperSU first before installing Magisk. Download and use the program linked in this post to uninstall SuperSU before installing Magisk.
Note: Please learn to use the Thanks button (bottom right of post) when members answer your question or provide useful/helpful information - it's an XDA Courtesy and it only takes a quick click.

sdembiske said:
OK, so as you were able to unlock your H815 Officially(H815 Europe version?), there shouldn't be a problem there if you did everything correctly.
That leaves TWRP version and SuperSU where the problem is most likely arising from.
Wipe your Cache & Dalvik cache in TWRP if it's functioning
Then, go to the TWRP site I linked in my previous post that is specific for the LG G4 and find and download the latest preview version you require for the firmware you currently have installed (I'm presuming Marshmallow [M]?). Follow the fastboot flashing method as exactly outlined there.
Next, if you really require SuperSu* (no longer currently supported or updated and free version removed from Play Store) you want to use SuperSU v2.82.
* I would however, recommend Magisk for your root program - it is currently supported and updated frequently. Download the latest ZIP and apk versions abd install them.
** You will have to uninstall SuperSU first before installing Magisk. Download and use the program linked in this post to uninstall SuperSU before installing Magisk.
Note: Please learn to use the Thanks button (bottom right of post) when members answer your question or provide useful/helpful information - it's an XDA Courtesy and it only takes a quick click.
Click to expand...
Click to collapse
i indeed have the eu version of the h815 unfortunately twrp doesnt start from recovery mode and when not in recovery the phone bootloops (twrp did work before as i used it to flash supersu)

just_anna said:
i indeed have the eu version of the h815 unfortunately twrp doesnt start from recovery mode and when not in recovery the phone bootloops (twrp did work before as i used it to flash supersu)
Click to expand...
Click to collapse
Using adb, try booting into recovery mode directly using this command adb reboot recovery.
Failing that see if you can get into fastboot mode - try this command fastboot reboot recovery If that works, uninstall SuperSU with the zip in the post I referenced above and install the SuperSU version I referenced or Magisk and then try rebooting the system.
Failing that try re-installing TWRP in fastboot mode with this fastboot flash recovery (twrp.image name exactly) and then fastboot reboot recovery if successful. Then uninstall SuperSu etc.

[/IMG]
sdembiske said:
Using adb, try booting into recovery mode directly using this command adb reboot recovery.
Failing that see if you can get into fastboot mode - try this command adb reboot bootloader and then try booting into recovery mode directly using this command fastboot reboot recovery. If that works, uninstall SuperSU with the zip in the post I referenced above and install the SuperSU version I referenced or Magisk and then try rebooting the system.
Failing that try re-installing TWRP in fastboot mode with this fastboot flash recovery (twrp.image name exactly) and then fastboot reboot recovery if successful. The uninstall SuperSu etc.
Click to expand...
Click to collapse
i tried all the commands using dos/command prompt from my fastboot folder it however cant find my device[IMG="dos results"]https://flic.kr/p/2gpcL5k

just_anna said:
i tried all the commands using dos/command prompt from my fastboot folder it however cant find my device
Click to expand...
Click to collapse
Try rebooting your PC with your phone connected and then try in your adb/fastboot folder again to see if your device is recognized.

sdembiske said:
Try rebooting your PC with your phone connected and then try in your adb/fastboot folder again to see if your device is recognized.
Click to expand...
Click to collapse
unfortunately it did not recognize the device and gave me the same results

just_anna said:
unfortunately it did not recognize the device and gave me the same results
Click to expand...
Click to collapse
Try reinstalling your LG G4 USB driver (LGMobileDriver_WHQL_Ver_4.2.0) on your PC and test again.
Failing that, try using FWUL to see if you can connect to your device - refer to the LG G4 TWRP link again and see FAQ # 3 where it's suggested.
If successful, go through the above commands again in FWUL - it has adb/fastboot built-in.
If you're still having no luck, see FAQ # 2 in the LG G4 TWRP thread and see if you can connect with @steadfasterX (the TWRP thread author & recognized developer) to help you - if anybody can, he can. I'm out of suggestions as of now.

Related

[Q] LS990 Certificate verify/secure boot error(s)

Hi there! I rooted my LS990 on lollipop 5.0.1 a recently and I tried to use TWRP to get a ROM on it and when I tried to install TWRP it came back with the error right after the LG logo on reboot when I tried to boot to recovery. I looked through a few threads but they all led to other LG models and not the LS990 from what I saw. I'm not able to boot to recovery, update my phone or factory reset. My endgame would be able to factory reset my phone and not worry about rooting it because it's just caused problems for me.
If there's any help I can get it would be much appreciated!
What method did you use to install TWRP? Try either TWRP Manager or Flashify from the Play Store, or push the recovery *img via adb shell or a terminal emulator app. You can find the latest *img file for the LS990 here...
https://twrp.me/devices/lgg3sprint.html
Follow the "dd Install Method (Requires Root):" directions at the bottom of the page. And make sure to never take an OTA update or perform a factory reset w/ a custom recovery like CWM or TWRP installed.
redduc900 said:
What method did you use to install TWRP? Try either TWRP Manager or Flashify from the Play Store, or push the recovery *img via adb shell or a terminal emulator app. You can find the latest *img file for the LS990 here...
Follow the "dd Install Method (Requires Root):" directions at the bottom of the page. And make sure to never take an OTA update or perform a factory reset w/ a custom recovery like CWM or TWRP installed.
Click to expand...
Click to collapse
I had downloaded TWRP from the Play Store and used the instructions in the app to patch my SD card and then downloaded the latest img from TWRP and when I tried to install the img it came back unsuccessful and since then I have had my error(s).
Try using the Flashify app instead. Make sure the external SD has indeed been patched by running the "SDFix: KitKat Writable MicroSD" app (available from the Play Store) beforehand. The app also works w/ Lollipop, and can be uninstalled after the verification or installation of the fix.
redduc900 said:
Try using the Flashify app instead. Make sure the external SD has indeed been patched by running the "SDFix: KitKat Writable MicroSD" app (available from the Play Store) beforehand. The app also works w/ Lollipop, and can be uninstalled after the verification or installation of the fix.
Click to expand...
Click to collapse
I'll give Flashify a shot. Just to be sure on what I do, I am flashing a new recovery img correct or am I doing a boot img?
Yes, a recovery image.
redduc900 said:
Yes, a recovery image.
Click to expand...
Click to collapse
Does it matter which one I do? There is a choice of TWRP, Philz and CMM.
TWRP is the recovery of choice for the G3.
redduc900 said:
TWRP is the recovery of choice for the G3.
Click to expand...
Click to collapse
It told me the flash was successful but when I rebooted my phone when it prompted me to it rebooted back to the certificate verify and secure boot error.
I forgot about the locked bootloader for that model. You'll need to first download the LS990 BUMP *.img file to your phone from here...
http://downloads.codefi.re/thecubed/lg_g3/bump/
... then open Flashify, select Recovery Image -> Choose a file -> Downloads, and select the TWRP recovery image you downloaded.
redduc900 said:
I forgot about the locked bootloader for that model. You'll need to first download the LS990 BUMP *.img file to your phone from here...
... then open Flashify, select Recovery Image -> Choose a file -> Downloads, and select the TWRP recovery image you downloaded.
Click to expand...
Click to collapse
Do I need to restore my old recovery before I do this or can I just go ahead and flash this new recovery?
No, just flash the new recovery image.
redduc900 said:
No, just flash the new recovery image.
Click to expand...
Click to collapse
Okay, I flashed the signed img from that download and it still giving the the boot certificate verify error :/
See if this video is of any help to you...
http://www.xda-developers.com/lg-g3-locked-bootloader-bump-xdatv/
That's what I did and it still gave me an error :/
I'm out of ideas... sorry.
redduc900 said:
I'm out of ideas... sorry.
Click to expand...
Click to collapse
No worries, I appreciate all of your help!

Unable to mount partitions after flashing TWRP on Nexus 7 (2013, WiFi, flo)

I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].
I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.
I have also tried to use this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.
So at this point now I can only access bootloader and the recovery which does not show partitions.
At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.
SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img
This allowed TWRP to work.
Thanks to Batfink33 and lynnux
You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
lynnux said:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
Click to expand...
Click to collapse
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Batfink33 said:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Click to expand...
Click to collapse
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
lynnux said:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
Click to expand...
Click to collapse
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Batfink33 said:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Click to expand...
Click to collapse
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
a4abbas said:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
Click to expand...
Click to collapse
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Batfink33 said:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Click to expand...
Click to collapse
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
a4abbas said:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
Click to expand...
Click to collapse
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
theminikiller said:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
Click to expand...
Click to collapse
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
a4abbas said:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
Click to expand...
Click to collapse
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
theminikiller said:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
Click to expand...
Click to collapse
You must be right, it make sense.

Installed twrp, but can't get into it

I did the following
1. Downgraded to V30b-EUR-XXX with LGUP. Went smooth.
2. Rooted phone sucessfully with kingroot.
3. Got a shell with "adb shell"
4. "su"
5. Filled the recovery-partition with zeros from /dev/zero with dd
6. Installed twrp3.2.3-0 with dd on recovery-partition
When I boot into Marshmallow, all is fine. When I boot into recovery, I'm informed about a necessary factory reset. I say "Yes" both times, then the LG Logo and some tiny text is displayed and afterwards the screen goes dark. The LED is blinking blue and red; the only way out of this is to remove the battery.
If I do a factory reset from within marshmallow, the result is the same.
What can I do now? Should I flash a stock recovery with dd? But where to get it? Or should I flash an older version of twrp?
Hello,
Last time when I downgraded, I also rooted with KingRoot, but I installed the "Flashify" full version, ( on the ROM of course ) and I flashed the twrp with the flashify as "recovery". This is working.
NetDog75 said:
Hello,
Last time when I downgraded, I also rooted with KingRoot, but I installed the "Flashify" full version, ( on the ROM of course ) and I flashed the twrp with the flashify as "recovery". This is working.
Click to expand...
Click to collapse
Excuse me, but I'm not able to decipher that. What is flashify? What means "on the ROM of course"? Can you give more information please.
- flashify is an application.
- on the ROM = when the phone booted and the operation system is working, you can use your phone... example for phone calls. As you wrote: "boot into Marshmallow"
So, downgrade again, and boot into Marshmallow, use the kingroot, than install the flashify application. You can flash the twrp with the mentioned Flashify application, than reboot to recovery.
NetDog75 said:
- flashify is an application.
- on the ROM = when the phone booted and the operation system is working, you can use your phone... example for phone calls. As you wrote: "boot into Marshmallow"
So, downgrade again, and boot into Marshmallow, use the kingroot, than install the flashify application. You can flash the twrp with the mentioned Flashify application, than reboot to recovery.
Click to expand...
Click to collapse
Don't had to downgrade, because I was in V30b. Got root, installed flashify and flashed twrp - the first time 3.2.3, then 2.8.0. Same result as before.
From what version of android did you install what version of twrp?
Hi,
I use the twrp3.2.3 and no problem.
I'm not expert, I just can recommend some steps...
Maybe good idea to flash again the stock ROM. You can find here on the forum many step by step guide for this. ( tools and steps )
It seems your phone recovery partition is not OK....
I have no more idea...
@theuving, why did you decide to zero out the recovery partition? I don't know but that may be part of the problem. Since you were connected via adb was it not possible to use fastboot? Flashing the recovery via that should(?) have also worked.
If the recovery partition is messed up you might have to start over. Not sure though as I haven't experienced that problem.
ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy
marcdw said:
@theuving, why did you decide to zero out the recovery partition? I don't know but that may be part of the problem. S
Click to expand...
Click to collapse
It's the same partition where I flashed twrp, so the zeros are already overwritten with something else ...
Seriously: Zeroing the partition before writing to it was mentioned in a thread about the installation of a "bumped" recovery.
NetDog75 said:
Hi,
I use the twrp3.2.3 and no problem.
Click to expand...
Click to collapse
OK, that is the version I used also. What android version was installed when you flashed the recovery? Mine is stock V30b.
Hi,
I'm not sure, because I changed to 8.1 (oreo).
Maybe V30N.....
I am having the same problem. There is no "unlock bootloader" in the developer options, and adb reboot bootloader just starts into android again. I might have to reflash the stock firmware, but nowhere in the install instructions for twrp does it say that you first have to unlock the bootloader, and nowhere does it even mention that there might not be such an option. This is genuinely strange.

Unable to install twrp

So this is my millet 6, I try Adb, TWRP manager, but my computer can use U disk mode, you can also use the official phone assistant to install the development version, but can not install the TWRP Manager to TWRP Recoey. You can view the video, hope everyone can help me.
https://www.facebook.com/100015187571561/posts/614327575750156/
潇霄小云 said:
So this is my millet 6, I try Adb, TWRP manager, but my computer can use U disk mode, you can also use the official phone assistant to install the development version, but can not install the TWRP Manager to TWRP Recoey. You can view the video, hope everyone can help me.
https://www.facebook.com/100015187571561/posts/614327575750156/
Click to expand...
Click to collapse
Did you unlocked bootloader? You have to flash twrp with adb while the phone is in fastboot mode.
mArIuS% said:
Did you unlocked bootloader? You have to flash twrp with adb while the phone is in fastboot mode.
Click to expand...
Click to collapse
I am sure to unlock bl。
The twrp manager always downloads the img file repeatedly, as if the img file could not be used. My moto xforce button is blue and can be installed after clicking twrp
Hey, I'm having the same issue here :S Already tried with Linux and Windows, both same issue... Fastboot detects my device, but it got stuck in there... I'm using the latest version of stock firmware...
I never faced this issue before, for sure my phone is unlocked and I already flashed like hundreds of time in the past. Is there something new?
Thanks!

[GUIDE] How to Root OnePlus 7T without TWRP

So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi
Flashed and working flawless.
Really thanks for this.
Awesome work bro.
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder
Working, thanks a lot @mauronofrio
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it
Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.
Thanks, rooted successfully
?
To be honest need video tutorial asap?
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.

Categories

Resources