Samsung Galaxy Note 5 N920V (nobleltevzw)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.08-B01
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.2.1 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY NOTE 5 N920V (NOBLELTEVZW)
LATEST FILE: Safestrap-4.08-B01-NOBLELTEVZW-SS-FF-flashable.zip
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
CHANGELOG:
4.08-B01 [2019-03-27]
- TWRP updated to 3.2.3.
- Fix reboot function.
- Theme clean up.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up
- Initial release.
BUGS:
- ROM-slots not working for now.
Does this allow magisk to be installed?
WhiteDragonn said:
Does this allow magisk to be installed?
Click to expand...
Click to collapse
No, not as far I know.
afaneh92 said:
No, not as far I know.
Click to expand...
Click to collapse
Interesting. I also noticed in the instructions that it says your device must be rooted in order to use safestrap. Is there a root for this phone that I am unaware of?
Also, I appreciate you and Hashcode's work on this project, but what is the purpose of this if there is no root and no roms?
WhiteDragonn said:
Interesting. I also noticed in the instructions that it says your device must be rooted in order to use safestrap. Is there a root for this phone that I am unaware of?
Also, I appreciate you and Hashcode's work on this project, but what is the purpose of this if there is no root and no roms?
Click to expand...
Click to collapse
You can get full root on combination via wondershare app.
Old 5.1.1 also can have full root.
Hmmm. I have never heard of using Wondershare. The site looks sketchy, can you go more into detail for me? I'm also running nougat.
Also will their be ROMs soon?
Could I use existing ROMs that are on the general Note 5 forum?
WhiteDragonn said:
Hmmm. I have never heard of using Wondershare. The site looks sketchy, can you go more into detail for me? I'm also running nougat.
Also will their be ROMs soon?
Could I use existing ROMs that are on the general Note 5 forum?
Click to expand...
Click to collapse
http://download.wondershare.net/mobilego-b_full1871.exe
No ROMs for now, You are on U3 bootloader if you got root it will be temporary. U2 can permenant root 5.1.1 without combo.
afaneh92 said:
http://download.wondershare.net/mobilego-b_full1871.exe
No ROMs for now, You are on U3 bootloader if you got root it will be temporary. U2 can permenant root 5.1.1 without combo.
Click to expand...
Click to collapse
That didnt work, it was stuck and kept rebooting my phone.
afaneh92 said:
You can get full root on combination via wondershare app.
Old 5.1.1 also can have full root.
Click to expand...
Click to collapse
I presume this only works on 6.0 and lower? It also just bootloops my phone on Android 7.0.
I can confirm that this is working as described. I flashed the combination firmware, rooted with wondershare, flashed safestrap via flashfire then flashed the ROM that this developer posted. What I have is a functional, rooted 5.1.1. I would love to have newer firmware, but I don't know what is possible.
Hello Reverse-anastomosis,
Where do you find the combination firmware?
gigahurts said:
Hello Reverse-anastomosis,
Where do you find the combination firmware?
Click to expand...
Click to collapse
That's a great question. I'm pretty sure I got it from some sketchy site that turned up in a google search. My theory on it was even if it was infected with something malicious, which I know has been a concern in the past, that it didn't matter because I really wasn't spending much time with the ROM booted, and I doubt there is anything tampered pre ROM, as we would have known about an exploit like that. So it might not fit your uses, my use was purely experimental and I didn't care if the device was compromised. All that being said I'll be glad to shoot you a link what I have if you're interested.
Reverse-anastomosis said:
That's a great question. I'm pretty sure I got it from some sketchy site that turned up in a google search. My theory on it was even if it was infected with something malicious, which I know has been a concern in the past, that it didn't matter because I really wasn't spending much time with the ROM booted, and I doubt there is anything tampered pre ROM, as we would have known about an exploit like that. So it might not fit your uses, my use was purely experimental and I didn't care if the device was compromised. All that being said I'll be glad to shoot you a link what I have if you're interested.
Click to expand...
Click to collapse
That would be great, I would really appreciate it. My purpose is exactly the same, for experimentation.
Reverse-anastomosis said:
I can confirm that this is working as described. I flashed the combination firmware, rooted with wondershare, flashed safestrap via flashfire then flashed the ROM that this developer posted. What I have is a functional, rooted 5.1.1. I would love to have newer firmware, but I don't know what is possible.
Click to expand...
Click to collapse
Hello @reverse_anastomosis do you find that there's issues with the WIFI password being forgotten after a reboot and the fingerprint sensor does not work? I'm gonna do a full clean wipe to see if it's still an issue.
afaneh92 said:
Samsung Galaxy Note 5 N920V (nobleltevzw)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.08-B01
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.2.1 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY NOTE 5 N920V (NOBLELTEVZW)
LATEST FILE: Safestrap-4.08-B01-NOBLELTEVZW-SS-FF-flashable.zip
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
Click to expand...
Click to collapse
Which android version does it need to be in to root?
Rootmaster906 said:
Which android version does it need to be in to root?
Click to expand...
Click to collapse
5.0
Related
VERIZON SAMSUNG GALAXY S3 (D2VZW)
ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
CURRENTLY THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
THANK YOU @BeansTown106 FOR HELPING ME DEBUG THIS
CURRENT PROJECT STATUS:
v3.71: Testing
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.1.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (3-4 on the S3 due to partition size and internal space) for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press under the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting.
By "under", I mean on the touch key portion of the front display on either side of the center button.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A VERIZON WIRELESS SAMSUNG GALAXY S3 (d2vzw)
BETA Safestrap-JFLTEVZW-3.71.apk (updated 2014-01-10)
XDA: XDA Download
Mirror 1: Crackflashers
Mirror 2: Goo.im Download
ALSO DOWNLOAD THE KERNEL MODULES .ZIP THAT MATCHES YOUR BUILD # (FLASH THIS AFTER ROMS):
d2vzw ML1: Download
As of version 3.6x, Safestrap Recovery is now based on TWRP 2.6.3.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
For the purposes of direct user testing I've established a channel on freenode.net IRC: #safestrap
I'm in the channel mostly all the time, but may not be active for discussion.
XDA:DevDB Information
Safestrap Recovery v3.71, Tool/Utility for the Verizon Samsung Galaxy S III
Contributors
Hashcode, DeesTroy & TeamWin
Version Information
Status: Alpha
Created 2014-01-10
Last Updated 2014-08-12
Reserved
Reserved
This is a great feat nice work
Sent from my SCH-I535 using XDA Premium 4 mobile app
This may sound weird, but I prefer having the option of a sort of dual boot, having one safe system that always works, and one for aosp nighties and tinkering. I have an unlocked bootloader, and don't want that to change, can I use safestrap?
rhcp1253 said:
This may sound weird, but I prefer having the option of a sort of dual boot, having one safe system that always works, and one for aosp nighties and tinkering. I have an unlocked bootloader, and don't want that to change, can I use safestrap?
Click to expand...
Click to collapse
Yes, but it's pretty unsupported. And I may need to take a look at the AOSP ramdisk to make sure I re-route internal storage correctly.
NOTE: all ROMs must use the same kernel.
Hashcode said:
Yes, but it's pretty unsupported. And I may need to take a look at the AOSP ramdisk to make sure I re-route internal storage correctly.
NOTE: all ROMs must use the same kernel.
Click to expand...
Click to collapse
So if im using verizons 4.3 update, any other rom i install needs to be on that same 4.3 kernel?
Good job man...
Sent from my SCH-I535 using Tapatalk
Nice work hash glad I could help debug/test for ya
Sent from my SM-N900V using Tapatalk
Good Job Hash !
Dadud said:
So if im using verizons 4.3 update, any other rom i install needs to be on that same 4.3 kernel?
Click to expand...
Click to collapse
Yes this will only work for tw 4.3 roms at the moment
Sent from my SM-N900V using Tapatalk
BeansTown106 said:
Nice work hash glad I could help debug/test for ya
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
OH damn, I forgot to give you a credit in the OP fixing!
Hashcode said:
OH damn, I forgot to give you a credit in the OP fixing!
Click to expand...
Click to collapse
Lol no worries buddy thanks always up for helping with safestrap-izzle lol
Sent from my SM-N900V using Tapatalk
Hashcode said:
Yes, but it's pretty unsupported. And I may need to take a look at the AOSP ramdisk to make sure I re-route internal storage correctly.
NOTE: all ROMs must use the same kernel.
Click to expand...
Click to collapse
That would be awesome if we could.
Sent from my SCH-I535 using xda app-developers app
I dont need to use this but you made roms on my old bionic possible so Thank you for bringing this to the sgs3 community. You sir are a legend.
Sent from my SCH-I535 using Tapatalk
BeansTown106 said:
Yes this will only work for tw 4.3 roms at the moment
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
If 4.3 is on my stock partition do I need to get kernel modules installed, or is that only when moving between versions?
tsachi said:
If 4.3 is on my stock partition do I need to get kernel modules installed, or is that only when moving between versions?
Click to expand...
Click to collapse
Beans sent me the ML1 modules and they are now available in the "Downloads" section as a 2nd flash.zip for when you install ROMs to rom-slots.
http://forum.xda-developers.com/devdb/project/?id=2405#downloads
tsachi said:
If 4.3 is on my stock partition do I need to get kernel modules installed, or is that only when moving between versions?
Click to expand...
Click to collapse
u will need to install the kernel module package as any tw 4.3 roms out now use a custom kernel and have the wrong modules for the stock kernel. i just sent them to hash so he should have in OP soon
@Hashcode - This isn't a request, only a "just curious" question.
if you use TWRP and goo manager, you can 'flash a rom' from goo manager, select the order to be flashed and decide if you want to wipe cache or not. press go and it will reboot the phone, start TWRP and carry out your request (I'm sure your familiar with this, i just wanted to be clear in my question) Is this something that would work with safestrap based on TWRP or is it a no-go since Safestrap is invovled?
Thanks
If i decide to go through with this can I still access the untouched system? Or will I be stuck on one of the 3-4 slots until I Odin Back to full stock?
Edit: I have fixed the issue of getting stuck in custom recovery bootloop. An updated custom recovery is required and should be available.
The info below is now outdated.
This information is what I have determined from my experiences and the reports of many others. It is accurate to the best of my knowledge.
CUSTOM RECOVERIES
There appears to be two types of bootloaders that are currently in use. One that plays nicely with custom recoveries (such as CWM, Philz, and TWRP) and a newer one that doesn't. Even if you haven't flashed a new bootloader, your device may have been manufactured with it. If you flash the KitKat firmware package, you will definitely have the new bootloader. Flashing a rom (such as NoleKat) does not give you a different bootloader.
The newer bootloader will cause you to be stuck in a recovery bootloop if you use any recovery boot method other than the 3-button method. This appears to be caused by the bootloader expecting the recovery to perform a checksum that the custom recoveries do not perform. The checksum action looks to be coded into the stock recovery init binary (which we can not use).
For some reason, this only happens if you use a "software" method to boot into recovery such as the following methods:
Any app that reboots in to recovery
ADB Reboot Recovery
The "Reboot Recovery" option in your custom recovery
Embedded Reboot to Recovery options in the rom
If you get stuck in a recovery bootloop, you need to flash the stock recovery to be able to boot the OS. You can do that by using Odin or by finding a flashable zip containing your stock recovery.
Once you get your OS to boot, you can re-install your custom recovery. Remember, only use the 3-button method to boot into recovery.
There is currently no way of returning to the old bootloader that I am comfortable with trying. It may be possible by someone creating a backup of the old PBL, SBL, and SBL2 partitions, but I do not recommend messing with your bootloader.
CHARGING WITH THE TABLET OFF
Since the KitKat roms and kernels have been release, there has been an issue with charging while the tablet is powered off. If you still have the old bootloader, the tablet will power on and boot into the OS when plugged in to charge.
If you have the new bootloader, the tablet will charge as it previously did on 4.1.2. You will see the charging icon on the screen, but the tablet does not boot into the OS.
gr8nole,
thank you for the useful post. i'm not certain if the following is relevant to the tab 3.
on the note 10.1 [old] with the new kitkat 4.4.2 firmware the same charger issue is present with respect
to reboot to os. this occurs with the jb bootloader AND the kk bootloader. ketut may have identified the
issue as resting in the kernel source itself,
ketut.kumajaya said:
For Tab 3 8.0 exynos4 platform, I managed to fix low power mode charging issue: https://github.com/kumajaya/android...mmit/97e454051b3364deafcc47a0e76a3a4fae29c356 Samsung change "lpcharge" bootloader command line to "androidboot.mode".
Click to expand...
Click to collapse
m
moonbutt74 said:
gr8nole,
thank you for the useful post. i'm not certain if the following is relevant to the tab 3.
on the note 10.1 [old] with the new kitkat 4.4.2 firmware the same charger issue is present with respect
to reboot to os. this occurs with the jb bootloader AND the kk bootloader. ketut may have identified the
issue as resting in the kernel source itself,
m
Click to expand...
Click to collapse
We've already fixed what we could with that, but it only works like it did before if you have new bootloader.
Please I'm having a problem charging 210R while powered off. It gets stuck at starting up to charge when the circle is inside the battery icon. This started happening after I downgraded from KitKat to Jelly bean. I also flashed TWRP recovery immediately.
I don't know what the problem could be. Help me please.
I'd have to long press the power button before the tab would respond and restart. If not, it would stay like that Even if the power cable is unplugged
Stuck in recovery mode
gr8nole said:
Edit: I have fixed the issue of getting stuck in custom recovery bootloop. An updated custom recovery is required and should be available soon.
The info below is now outdated.
Click to expand...
Click to collapse
Hello! The T210 has been stuck in recovery mode for some 5 months now. Is there any way to make it usable again? The only thing we can see on screen is:
ODIN MODE
Product name: SW-T210
Current binary: Custom
System Status: official
HW REV: 0x5
I have used a brand new laptop and even when I installed KIES, Odin does not see the tablet.
Pls help
Thanks,
Hector
EDIT: the tablet is back now, did the following:
1) Manually downloaded the drivers from Windows7 Device Manager.
2) Odin was able to see the Tablet
3) I ued the new file T210_CWM_6.0.4.9.KK.tar.md5
4) Then I unselect auto reboot
It took 2.5 minutes but the tablet is now a live again.
All this was a prerequisite to install the KidsROM... I had to buy another tablet 2 months ago Galaxy Tab4, which includes a Kids mode, so the KidsROM is not installed yet.
Do you know if once I flash KidsROM will I be able to use GPS functionality?
Thanks
ekthor said:
Do you know if once I flash KidsROM will I be able to use GPS functionality?
Thanks
Click to expand...
Click to collapse
It has been a while since I looked at that rom, but I don't think the World version had GPS. I do believe the US version did though. If you like the Tab 4 kids mode, keep in mind that the 4.1.2 Kids Rom is not the same. My 4.4.2 NoleKat does have a Kids Mode add-on that is like the Tab 4 Kids Mode (and GPS works).
Great! Please let me know where can I download the 4.4.2 NoleKat, and their installation instructions.
All the best, Hector
ekthor said:
Great! Please let me know where can I download the 4.4.2 NoleKat, and their installation instructions.
All the best, Hector
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2837338
@gr8nole : Can you shortly explain how you fixed it (the soft reboot to recovery problem)? Did you use the loki way, or did you something other?
thanks
SP
SolarPlexus said:
@gr8nole : Can you shortly explain how you fixed it (the soft reboot to recovery problem)? Did you use the loki way, or did you something other?
thanks
SP
Click to expand...
Click to collapse
The new bootloaders are looking for variable that our custom recoveries were not generating so we had to create and force that variable in the build.prop.
We also had to switch to the init binary from the KitKat stock recovery in order to use this newly forced variable to trigger the exec that clears recovery mode.
Basically, recovery_mode was getting set, but never cleared.
gr8nole said:
The new bootloaders are looking for variable that our custom recoveries were not generating so we had to create and force that variable in the build.prop.
We also had to switch to the init binary from the KitKat stock recovery in order to use this newly forced variable to trigger the exec that clears recovery mode.
Basically, recovery_mode was getting set, but never cleared.
Click to expand...
Click to collapse
Hi Gr8nole,
thanks for your explanation. Sorry for the late respones. The kernel source for our i8200 was really a mess, and so we have needed up to the last week to get it to work ;(
But now we can made further steps, so I come back to you tom this point. So the only thing you did is to switch the init binary? Or must there also other changes be done?
Thanks in advance for your help!
BR
SolarPlexus
SolarPlexus said:
Hi Gr8nole,
thanks for your explanation. Sorry for the late respones. The kernel source for our i8200 was really a mess, and so we have needed up to the last week to get it to work ;(
But now we can made further steps, so I come back to you tom this point. So the only thing you did is to switch the init binary? Or must there also other changes be done?
Thanks in advance for your help!
BR
SolarPlexus
Click to expand...
Click to collapse
In order to clear the "recovery_mode" flag that was being set, we did the following:
Add this line to the bottom of the default.prop
Code:
sys.recovery_done=1
Add this to the bottom of init.rc
Code:
on property:sys.recovery_done=1
exec clear_recovery_mode
gr8nole said:
In order to clear the "recovery_mode" flag that was being set, we did the following:
Add this line to the bottom of the default.prop
Code:
sys.recovery_done=1
Add this to the bottom of init.rc
Code:
on property:sys.recovery_done=1
exec clear_recovery_mode
Click to expand...
Click to collapse
Thank you very much!
BR
SP
TWRP has been successfully ported to the Galaxy J7 Refine (SM-J737p) (Oreo 8.0)
DISCLAIMER: THIS IS NOT AN ODIN FLASHABLE TWRP. THIS IS NOT AN OFFICIAL TWRP. THIS IS A TWRP PORT THAT HAS BEEN MADE POSSIBLE BY BOTH @Dark98 & MYSELF. IT WAS BUILT USING FILES FROM R16NW.J737PVPU1ARG3. IT MAY OR MAY NOT WORK ON DEVICES WITH A DIFFERENT BOOTLOADER VERSION
You must have root access. I am currently working on making an Odin-flashable .tar for TWRP devs. Hopefully it will be available soon. Until then, root your device with Magisk. SuperSU is dead..
There is a downside & an upside to porting TWRP. The downside is that after you flash TWRP, you will lose root. The upside is that TWRP will remain so all you need to do to regain root is flash the Magisk-v18.1.zip. It's a very delicate process & you will need to pay attention or else you will bootloop & start over.
In order to flash, you need an app that will do so without booting into recovery. Flashify is the ideal choice for this procedure. View attachment flashify.apk Flash TWRP in Flashify but do not reboot from the app. Power off your device & boot into TWRP manually.
PAY ATTENTION TO THESE NEXT FEW STEPS!!!
- Boot into TWRP for the first time
- Swipe to allow modifications
- Wipe > Format Data > type yes when prompted (this will not delete any files you have in your Internal Storage)
- Once wipe is completed, go to TWRP home screen & Reboot > Power Off
- Once device powers off, reboot back into TWRP (yes you will boot into recovery twice)
If you fail to immediately boot back into TWRP, you will brick & have to restart.First boot is to clear out the /Data partition to make room for your new recovery. Second boot is to secure it.
Now that you have secured TWRP, go ahead & make a backup of your Boot + System + Data partitions. Keep in mind that you've lost root access so the backup will be "stock" firmware with TWRP.
------------------------------------------------------------------------------------------------------------------------------
Now to get root back
(In TWRP)
You will now flash Magisk-v18.1. With the new security measures Samsung put in late 2017, you will need to flash 2 .zip files after to ensure that root sticks. YOU NEED TO FLASH THESE FILES IN ORDER. DO NOT WIPE CACHE AFTER EACH FLASH. DO NOT REBOOT AFTER EACH FLASH. FLASH EACH PACKAGE ONE AT A TIME. WAIT UNTIL THE 3RD FLASH IS COMPLETE & THEN REBOOT DEVICE. IT WILL TAKE SEVERAL MINUTES SO BE PATIENT.
In this order, flash:
- View attachment Magisk-v18.1(18100).zip
- View attachment no-verity-opt-encrypt-6.0.zip
- View attachment RMM-State_Bypass_Mesa_v2.zip
DO NOT WIPE THE CACHE
Now reboot device normally. If you do not flash the verity & RMM zip files in order, you will fυck your sh¡t up & have to start over.
PROOF OF TWRP:
View attachment 4730415
View attachment 4730414
View attachment 4730413
View attachment 4730412
When you get to your home screen, you will receive a notification to update Magisk. Update by either selecting the notification or manually through Magisk Manager. Allow Magisk to install the update, not TWRP.
Extract the .tar from the .zip > extract the twrp.img from the .tar View attachment J737P.zip
This is for the Galaxy J7 Refine (SM-J737P) (RUNNING OREO 8.0) (J737PVPU1ARG3)
Special thanks to @topjohnwu for Magisk
Special thanks to @Dark98 for working with me on this project. Probably could've done it without you bro but it would've taken longer
work for j737t and j737t1?
juniorgerman said:
work for j737t and j737t1?
Click to expand...
Click to collapse
The root method should, provided you substitute in your own patched_boot.img from your stock firmware.
TWRP however, will not. Those variants are GSM Carriers (T-Mobile network). This is for Boost, a CDMA Carrier (exynos7885)
Thank you
Thank you for this as I will give it a go.
Kireej said:
Thank you for this as I will give it a go.
Click to expand...
Click to collapse
This thread should've been deleted already as it's not the main one. I've moved it to here. Please direct any further comments or inquires here as well.
Is there a rootable method for the J737P 9.0 Android update?
LeThAiL JoKeR said:
Is there a rootable method for the J737P 9.0 Android update?
Click to expand...
Click to collapse
Hello, I have a Galaxy J7 Refine from Boost. Recently I decided to root it. There are only a few places that have ANY info on rooting SM-J737P.
Not realizing that this was an OLD thread, I basically just went along with this and a little info from somewhere else and some knowledge of rooting from back when I basically HAD to have my phone rooted.
Good news is, first try it worked for me. But I had this issue that I figured would be easy to remedy.
There is a notification when I boot the phone saying Unauthorized actions have been detected. Restart your device to undo any unauthorized changes.
Without doing any research on the notification I immediatly lept into action and caused the phone not only to boot loop, but also not be able to boot into recovery, where I had made my backup.
I tried flashing several roms/files and trying to figure out the issue, I realized that this was an old thread and the Binary Update number on my phone was 7, and here i was trying to flash 1's, 2's, 4's, 6's. Like no wonder they didnt do anything to help.
Immediately trying to search for U7, I was hitting road blocks, because it seems as though everyone's list stopped at U6.
Fortunatly for you, I would not take no for an answer and spents HOURS trying to figure out what file I needed and then locating it. Not being able to boot into OS or Recovery, figuring out what version my phone was on was a bit tricky. Cross referanced this info with that info, yada yada yada.
I found the most up to date file in case you brick your phone, but also if your still interested, I can help supply the info and files I used to accomplish this.
But as I type this, I cant stop thinking about that notification. I need to find out if its going to cause me problems or if I can just shut it up and everything will be fine.
I'll get back to you on those results. For now, im done typing. I haven't typed this much in a LONG time.
I cant stop thinking about that notification. I need to find out if its going to cause me problems or if I can just shut it up and everything will be fine.
(Disable the app called securitylogagent do no th delete will cause bootloop) I am looking to see is there new firmware u7. i have binary 6 rooted and would like to find u7 to try root?
Disable image
......fix that notification
I found out using lucky patcher to get rid of notification. Which that was the first app I was going to install anyways. So it worked out great.
As far as the u7 binary, I found it. I'll upload it to drive and share a link here shortly.
Currently uploading file to folder, but when its done you should be able to access it here.
https://drive.google.com/drive/folders/1MD3owVbiAjgSyz0-f4Q_eSATV1zcXZeZ?usp=sharing
hello i'm on the u7 binary i'm having trouble rooting can someone share a link for the patched boot for the u7 or a flashable twrp if there is one? any help is appreciated and thank u
never mind i got it thanks anyway
How do you root a Samsung Galaxy SM-J737P Version 9
PlsHelpMeRootingImBegging said:
How do you root a Samsung Galaxy SM-J737P Version 9
Click to expand...
Click to collapse
I'm on 7 but I believe all u would do is flash twrp and patch ur boot img from ur binary with magisk and follow the rest the steps listed above
weric43 said:
I'm on 7 but I believe all u would do is flash twrp and patch ur boot img from ur binary with magisk and follow the rest the steps listed above
Click to expand...
Click to collapse
But i can find my TWRP and no one click roots work i tried kingo root kingroot and SO many others none work and framaroot wont work either nothing works and my twrp idk if its compatible
PlsHelpMeRootingImBegging said:
But i can find my TWRP and no one click roots work i tried kingo root kingroot and SO many others none work and framaroot wont work either nothing works and my twrp idk if its compatible
Click to expand...
Click to collapse
I have the twrp flash file give me a few mins I'll get it to u
weric43 said:
I have the twrp flash file give me a few mins I'll get it to u
Click to expand...
Click to collapse
download files unzip files inside u will find flashable twrp
okey
PlsHelpMeRootingImBegging said:
okey
Click to expand...
Click to collapse
Did u get it?
weric43 said:
Did u get it?
Click to expand...
Click to collapse
so i installed magiska and tapped install to the tar file idk it never flashed so i tried again and it said their was no recovery.img found
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device
vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group
vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.
kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted
vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.
FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant
I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.
kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.
I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work
This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.
Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
UrAverageNerd said:
If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.
Hi there. I ran into similar problems when I was a Root noobie (which I still am). Try the All In One Tool that can be found in this forum. That will help you flash TWRP. It got me there when I was struggling to Flash TWRP.
redpoint73 said:
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.
Click to expand...
Click to collapse
Thanks for your help. Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching. I like using TWRP because it's convenient if I wan't to flash something else without a PC or Mac.:laugh:
UrAverageNerd said:
Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching.
Click to expand...
Click to collapse
Something wrong with the "main" download link (androidfilehost)?
UrAverageNerd said:
Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Use adb & fastboot via powershell
Get the adb files in a folder
Copy the twrp.img to the adb folder and on phone /storage/emulated/0/
Get a copy of the twrp installer on your phone anywhere works
Open adb folder
Hold shift and right click a empty space
Open powershell & type
Adb boot bootloader
Fastboot boot twrp.img (you can drag and drop the file into powershell if your lazy like me)
Flash the twrp installer on your phone
Done?
Reboot and go back into recovery to see if it works
Tip for updates:
After you get the update
Flash via twrp
Then flash twrp (so you don't need your computer)
Flash magisk if you want superuser
Reboot
Reboot recovery
Flash magisk again (seems it takes two flashes)
None of the tools work for my devices anymore just powershell
All in one doesn't read my fastboot
Cmd has a remote error after attempting to boot it.
UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Just noticed that the TWRP "guacomoleb" is the "unified" version that works with both the OnePlus 7 and the 7 Pro. Shouldn't make a difference whether you use the "unified" version or the 7 Pro specific TWRP.