Welcome To Negalite HW TWRP Recovery!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
lz4 Compression Algorithm - boot speed
f2fs Support
logging enabled(logcat)
fb2png - take screenshots within recovery
compiled using Uber Toolchains
compiled using Negalite HW kernel
many features enabled
Custom Theme
Downloads
Recovery Flashable! Flash From Within Your Current Custom Recovery
negalite-HW-TWRP-3.0.3-v1.5.zip - 1/09/17
Fastboot Flashable! Flash From Within Bootloader Using Fastboot
negalite-HW-TWRP-3.0.3-v1.5.img - 1/09/17
Device Source
https://github.com/Negamann303/omni_twrp_device
Reserved...
Nice. Thanks for your work man! I'll try this out and report back if I notice any issues. If you don't hear from me then it's all good!
Is f2fs only for cache, data, and internal storage? Or can it be used on system as well?
[update] I used the flash method and it's running good. Switched cache, data, and internal storage to f2fs and all is running well.
imucarmen said:
Nice. Thanks for your work man! I'll try this out and report back if I notice any issues. If you don't hear from me then it's all good!
Is f2fs only for cache, data, and internal storage? Or can it be used on system as well?
[update] I used the flash method and it's running good. Switched cache, data, and internal storage to f2fs and all is running well.
Click to expand...
Click to collapse
Good I set it up for system to do it as well, even though technically it would be pointless since system doesn't write files(unless you manually add to it or flash something to it) . I haven't tested it though
Sent from my SM-G935P using Tapatalk
Updated Recovery To The Latest 3.0.2-1!
I guess the restore bug may not be present in this watch's system due to no efs partition. I'm wondering if it does affect it at all since it does affect quite a few devices.
shag_on_e said:
I guess the restore bug may not be present in this watch's system due to no efs partition. I'm wondering if it does affect it at all since it does affect quite a few devices.
Click to expand...
Click to collapse
We are one commit past that issue, it was already fixed
Sent from my SM-G935P using Tapatalk
i get a red exclamation when i flash this recovery and then try to reboot into recovery. i am not sure what i am doing wrong. I flashed 2-3 times now with the same result. here is the command i am using
adb reboot bootloader
fastboot flash recovery negalite-HW-TWRP-3.0.2-v1.4.img
fastboot reboot
samjoandco said:
i get a red exclamation when i flash this recovery and then try to reboot into recovery. i am not sure what i am doing wrong. I flashed 2-3 times now with the same result. here is the command i am using
adb reboot bootloader
fastboot flash recovery negalite-HW-TWRP-3.0.2-v1.4.img
fastboot reboot
Click to expand...
Click to collapse
After you flash the recovery, boot to the normal watch running before you boot back to recovery, i *think* that is how I solved it, but it has been some time ago.
Pkt_Lnt said:
After you flash the recovery, boot to the normal watch running before you boot back to recovery, i *think* that is how I solved it, but it has been some time ago.
Click to expand...
Click to collapse
i tried this multiple times without success
samjoandco said:
i tried this multiple times without success
Click to expand...
Click to collapse
I had to do it about 8 times with the same problem.
Try flashing recovery then back to bootloader with
Code:
fastboot reboot-bootloader
Then manually reboot from the bootloader to recovery.
Sorry, I just don't remember how I solved it
while in bootloader mode, is fastboot boot negalite-HW-TWRP-3.0.2-v1.4.img working?
samjoandco said:
i get a red exclamation when i flash this recovery and then try to reboot into recovery. i am not sure what i am doing wrong. I flashed 2-3 times now with the same result. here is the command i am using
adb reboot bootloader
fastboot flash recovery negalite-HW-TWRP-3.0.2-v1.4.img
fastboot reboot
Click to expand...
Click to collapse
Your bootloader is unlocked?
gwolfu said:
while in bootloader mode, is fastboot boot negalite-HW-TWRP-3.0.2-v1.4.img working?
Click to expand...
Click to collapse
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
---------- Post added at 06:45 PM ---------- Previous post was at 06:31 PM ----------
samjoandco said:
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
Click to expand...
Click to collapse
back to the same red exclaimation mark after rebooting! and boot to recovery.
my bootloader is unlocked
samjoandco said:
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
---------- Post added at 06:45 PM ---------- Previous post was at 06:31 PM ----------
back to the same red exclaimation mark after rebooting! and boot to recovery.
my bootloader is unlocked
Click to expand...
Click to collapse
Fastboot boot temporarily loads the recovery.img. Try doing that then flashing the recovery zip within recovery. Quick workaround for you
Sent from my SM-G935P using Tapatalk
samjoandco said:
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
---------- Post added at 06:45 PM ---------- Previous post was at 06:31 PM ----------
back to the same red exclaimation mark after rebooting! and boot to recovery.
my bootloader is unlocked
Click to expand...
Click to collapse
download the recovery img boot in to bootloader fastboot flash recovery img.whit the hardver button navigate to reboot recovery tourn long and you will booted in twrp recovery
negamann303 said:
Fastboot boot temporarily loads the recovery.img. Try doing that then flashing the recovery zip within recovery. Quick workaround for you
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
thanks this worked!
after trying for almost 24 hours, this worked fine. now i can go into recovery from ADB as well as from the reboot prompts within the watch. this is solved for good
negamann303 said:
Fastboot boot temporarily loads the recovery.img. Try doing that then flashing the recovery zip within recovery. Quick workaround for you
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
yeas was about to suggest just that
well my idea was to boot in TWRP temporary to validate that the recovery image works and then flash it again from recovery
but heck negamann303 was faster then me on this
glad you made it work
Hey guys
Just got mine YEEEES
Is it possible to dualboot 1.5 & 2.0 via multiROM, dual-boot-scripts or magisk?
Thank you soo much
Cheers
Blade
Also, can I take backups of the current state, to revert to it later?
BIade said:
Hey guys
Just got mine YEEEES
Is it possible to dualboot 1.5 & 2.0 via multiROM, dual-boot-scripts or magisk?
Thank you soo much
Cheers
Blade
Also, can I take backups of the current state, to revert to it later?
Click to expand...
Click to collapse
No multirom for us yet. But you can do backup and restore!
BTW, luv Koln my last visit
Related
ROOTED USERS ONLY
I am not responsible for bricked devices.
TWRP: Download the img for your device HERE
via @ WACOMalt
Download Flashify from Google Play HERE
Under the FLASH tab using the Flashify app click Recovery Image.
Find the img file you just downloaded for your specific device.
Click on the img file then you will be prompted with a Flash Recovery? screen.
Click YUP if you would like to continue with the flash or MAYBE NOT... if you chose the wrong file or have changed your mind.
If you chose to continue flashing you will see a working box which says Flashing...
A box which says Flash Completed will show after flash is complete.
Click Reboot Now.
Done!
Formatting Cache delay fix
Tick Use rm -rf instead of formatting in the settings menu of TWRP.
Tested on T-Mobile D801 using img 2.6.3.2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
did that after i installed using freegee and what do you know a bootloop. restored stock image then reflashed and worked fine.
another problem ive encountered is that once you use flashify to install recovery it does not boot into recovery at all. it boots into a black screen.
freegee boots into recovery also but you cant change versions of twrp. its at 2.6.3.0 and you cant install the 2.6.3.3 zip. tried numerous times and it fails.
I've not had that issue on T-Mobile D801.
podagee said:
another problem ive encountered is that once you use flashify to install recovery it does not boot into recovery at all. it boots into a black screen.
freegee boots into recovery also but you cant change versions of twrp. its at 2.6.3.0 and you cant install the 2.6.3.3 zip. tried numerous times and it fails.
Click to expand...
Click to collapse
THIS METHOD DOES NOT WORK!!
you will have a black screen and no recovery DO NOT ATTEMPT>
AT&T users dont do it.
podagee said:
THIS METHOD DOES NOT WORK!!
you will have a black screen and no recovery DO NOT ATTEMPT>
AT&T users dont do it.
Click to expand...
Click to collapse
I tried this method before seeing this tread. I tried to flash clean ROM when going to boot up, black screen good thing backup worked threw twrp everthing I try threw twrp backup or wipes cashes and that works just fine is there a fix for att users. Thanks
Sent from my LG-D800 using xda app-developers app
podagee said:
THIS METHOD DOES NOT WORK!!
you will have a black screen and no recovery DO NOT ATTEMPT>
AT&T users dont do it.
Click to expand...
Click to collapse
Really not needed, to post in this manner. Just because it did not work for you does not mean it will not for others...
And actually I am a AT&T User LG-D800 and it work just fine for my device, did you have the correct img file.
podagee said:
another problem ive encountered is that once you use flashify to install recovery it does not boot into recovery at all. it boots into a black screen.
freegee boots into recovery also but you cant change versions of twrp. its at 2.6.3.0 and you cant install the 2.6.3.3 zip. tried numerous times and it fails.
Click to expand...
Click to collapse
As stated it work for me, I utilized the app and installed recovery TWRP and I booted into it and updated the TWRP with the zip.
Keep in mind there has been issues with using the app, BUT there is warnings as with all tweaking/rooting/flashing......
I flashed TWRP using Flashify as well. Done on the D802 as per the instruction. Recovery works fine.
Judge Joseph Dredd said:
Really not needed, to post in this manner. Just because it did not work for you does not mean it will not for others...
And actually I am a AT&T User LG-D800 and it work just fine for my device, did you have the correct img file.
As stated it work for me, I utilized the app and installed recovery TWRP and I booted into it and updated the TWRP with the zip.
Keep in mind there has been issues with using the app, BUT there is warnings as with all tweaking/rooting/flashing......
Click to expand...
Click to collapse
the images i used were provided from here/ the link. ive tried numerous times and nothing. please share the image you used, were you on D80010o?
---------- Post added at 08:06 AM ---------- Previous post was at 07:28 AM ----------
it seems the loki aboot from the link posted for recovery images is not compatible with th D80010o. if a fix were provided there would be no problems flashing.
yup i can confirm that using flashify after the ota and root does not work on the att d800. if you have successfully done it JudgeJosephDredd please give any directions that would help. cause no matter what image i flash it does not work......at all. thanks in advance if you decide to help.
This app ****ing rocks. Thank you for introducing me to flashify. I used it to upgrade cwm and cm11 in under 5 steps. That's pretty impressive to me.
Guys is there a difference between using this and using Freegee from the Playstore which ive already done. If this way is better how do i undo the Freegee, do i just uninstall it as TWRP already exists on my phone.
mcteague said:
Guys is there a difference between using this and using Freegee from the Playstore which ive already done. If this way is better how do i undo the Freegee, do i just uninstall it as TWRP already exists on my phone.
Click to expand...
Click to collapse
You don't need to worry. They are different ways of arriving at the same destination.
Just uninstall Freegee.
Worked for me. T-Mobile G2.
Sent from my LG-D801 using Tapatalk
Works fine on D802
Sent from my LG-D802 using Tapatalk
k3xx said:
Works fine on D802
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
What did you use? the 2.6.3.3 D802 img at the link provided?
Yep I'm used that link (to be clear: http://techerrata.com/browse/twrp2/g2d802) but first I installed the 2.6.3.2 .img file cause flashify supports better img files for recovery than zip and then used that TWRP to flash the 2.6.3.3 .zip file.
Sent from my LG-D802 using Tapatalk
Every time I try Flashify on either of the two img files for Verizon, it just reboots to a black screen. After first black screen I do the hard reset with the power button but still no luck.
Guys I'm thinking of flashing recovery via flashify, I did have recovery gained via freegee but got stuck in a boot loop while flashing Omni ROM and couldn't enter recovery so had to restore full software via LG Launcher software. My question is are there any safe roms out there for us yet, or was it a problem with freegee recovery
Sent from my LG-D802 using Tapatalk
mcteague said:
Guys I'm thinking of flashing recovery via flashify, I did have recovery gained via freegee but got stuck in a boot loop while flashing Omni ROM and couldn't enter recovery so had to restore full software via LG Launcher software. My question is are there any safe roms out there for us yet, or was it a problem with freegee recovery
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I don't its freegee did you check md5 before you flashed the ROM
Sent from my Nexus 4 using XDA Premium 4 mobile app
I have combined the OnePlus 3 and OnePlus 3T TWRP threads into a single thread for the unified build.
Please visit:
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
I apologize for the inconvenience.
XDA:DevDB Information
Team Win Recovery Project for the OnePlus 3T, Tool/Utility for the OnePlus 3T
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3t
Version Information
Status: Stable
Current Stable Version: 3.0.3-1
Stable Release Date: 2017-01-16
Created 2016-11-26
Last Updated 2017-01-22
Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
Now if I have already rooted and installed a kernel will flashing TWRP wipe that stuff? I had to boot TWRP to flash SU and Kernel but did not flash it.
ghettopops said:
Now if I have already rooted and installed a kernel will flashing TWRP wipe that stuff? I had to boot TWRP to flash SU and Kernel but did not flash it.
Click to expand...
Click to collapse
TWRP will only wipe if you ask it to wipe something. OnePlus is using the usual separated recovery partition style which is great so you don't have to worry about TWRP breaking anything by flashing it.
jcadduono said:
TWRP will only wipe if you ask it to wipe something. OnePlus is using the usual separated recovery partition style which is great so you don't have to worry about TWRP breaking anything by flashing it.
Click to expand...
Click to collapse
So that means it doesn't use that new layout which includes dual A/B partitions right? If the only benefit of dual partitions is seamless updates, I guess the traditional layout is fine or even better.
Edit: Both this TWRP thread and the Tyranus kernel thread came out pretty quick, and seem very well documented and professional compared to some of the other Non Nexus device threads. I'm impressed. I just hope the threads stay uncluttered. Thank you.
So that I understand, separate recovery partition means that I can have both TWRP and Oxygen Recovery installed. Allowing me to get updates and install them through Oxygen Recovery while maintaining a TWRP recovery? Also is it just a matter of booting into them via fastboot?
Perhaps, the step between 2 and 3 should be go into the 'system>about' menu, keep tapping 'build number' to enable 'developers option', then go back out and into 'setting>developers option' and turn on 'OEM unlocking'. w/o this option turn on, you can do 'fastboot oem unlock'
And maybe perhaps, before doing anything, why not update the system via OTA first? If the OTA zip is OnePlus official, you should be able to flash it using stock recovery, doesn't it?
side note tip: if you wipe the data partition in TWRP, the default would be ext4, but the OP stock use F2FS. I think it may be wise to change that before wiping the data partition.
someone0 said:
Perhaps, the step between 2 and 3 should be go into the 'system>about' menu, keep tapping 'build number' to enable 'developers option', then go back out and into 'setting>developers option' and turn on 'OEM unlocking'. w/o this option turn on, you can do 'fastboot oem unlock'
And maybe perhaps, before doing anything, why not update the system via OTA first? If the OTA zip is OnePlus official, you should be able to flash it using stock recovery, doesn't it?
side note tip: if you wipe the data partition in TWRP, the default would be ext4, but the OP stock use F2FS. I think it may be wise to change that before wiping the data partition.
Click to expand...
Click to collapse
Done. Should now default to f2fs on data wipes as well. (redownload, I didn't change the version number)
Yes that is an option.
ghettopops said:
So that I understand, separate recovery partition means that I can have both TWRP and Oxygen Recovery installed. Allowing me to get updates and install them through Oxygen Recovery while maintaining a TWRP recovery? Also is it just a matter of booting into them via fastboot?
Click to expand...
Click to collapse
No, separate recovery partition means you can flash kernels and recoveries separately. It means recovery isn't part of the system boot image, which is an idiotic design of the Pixel phones that is hurting custom development for them. See example:
OnePlus 3T (and every other sane device):
boot partition = system boot image
recovery partition = recovery boot image
result = you can use twrp to flash custom roms! any issues = just try in twrp again!
Pixel:
boot partition = boot image with recovery ramdisk that loads system (???)
boot_a partition = the same thing as boot partition (??? again)
recovery partition = nowhere to be found
result = flash a bad custom rom? say goodbye to twrp!
Can't decrypt data so can't flash any files. Just updated to twrp in the op.
charlieb620 said:
Can't decrypt data so can't flash any files. Just updated to twrp in the op.
Click to expand...
Click to collapse
need recovery.log ... i'm guessing this is happening due to changing default partition type for data from ext4 to f2fs, might need to change it back
in the meantime, setting default back to ext4....redownload (again)
in the meantime, anyone crazy enough to test https://build.nethunter.com/test-builds/oneplus/kernel-nethunter-oneplus3t-marshmallow-test1.zip for me?
yes, this device is getting official Kali NetHunter support
Log
http://www87.zippyshare.com/v/7OhpiOv2/file.html
jcadduono said:
in the meantime, anyone crazy enough to test https://build.nethunter.com/test-builds/oneplus/kernel-nethunter-oneplus3t-marshmallow-test1.zip for me?
yes, this device is getting official Kali NetHunter support
Click to expand...
Click to collapse
Woah! Now official nethunter? I can test this Monday when I get the device. I would be surprised if we got copperhead OS too.
Another known issue: I can't get USB-OTG to work. Even in the StockOS, it seem disable by default and have to enable first, otherwise it won't provide power back out to the USB port. Not sure if this is related.
charlieb620 said:
Log
http://www87.zippyshare.com/v/7OhpiOv2/file.html
Click to expand...
Click to collapse
that's stock recovery....enable xda signatures and you will see how to get logs in my signature
someone0 said:
Another known issue: I can't get USB-OTG to work. Even in the StockOS, it seem disable by default and have to enable first, otherwise it won't provide power back out to the USB port. Not sure if this is related.
Click to expand...
Click to collapse
i'll look into it i guess, might be a /sys file we can trigger on init to enable it if you want to do the investigation for me
probably related to dash charge stupidity
jcadduono said:
that's stock recovery....enable xda signatures and you will see how to get logs in my signature
i'll look into it i guess, might be a /sys file we can trigger on init to enable it if you want to do the investigation for me
probably related to dash charge stupidity
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A3000
---------- Post added at 05:58 AM ---------- Previous post was at 05:25 AM ----------
Ok started from scratch
Have latest twrp, root and net hunter kernel running.
charlieb620 said:
Sent from my ONEPLUS A3000
---------- Post added at 05:58 AM ---------- Previous post was at 05:25 AM ----------
Ok started from scratch
Have latest twrp, root and net hunter kernel running.
Click to expand...
Click to collapse
That screenshot seem like somebody is trying to run adb from within the android shell. I would just
'adb shell'
'su'
'cd /sdcard' or /tmp or whichever directory that's writable.
then run whatever command you need from there. Having another DOS windows open up is also a good idea. That way, one window is always running shell, and another is just DOS. so no confusion and no need to keep exiting shelf and get back in.
Fails to decrypt data. Here is logs from 3t 128gb model.
Black screen
Followed instructions to a "T" (haha)
Everything gets installed, i have root, but when i try to reboot into recovery/twrp - i just get a black screen. I can still turn the phone off, and start up the phone no problems, so its usable - but just not into twrp.
Any thoughts of suggestions?
hawki said:
Followed instructions to a "T" (haha)
Everything gets installed, i have root, but when i try to reboot into recovery/twrp - i just get a black screen. I can still turn the phone off, and start up the phone no problems, so its usable - but just not into twrp.
Any thoughts of suggestions?
Click to expand...
Click to collapse
How did you get root (superSU) installed w/o twrp?
BTW, you may have the same problem I had earlier, which is the stock OS is on version 3.5.1. You need to follow the instruction again, and flash recovery and boot into twrp.img After that, patch your OS to the latest via OTA, I think you need to re-root again after that.
just to be clear. Since I am already rooted am I just flashing twrp and swiping for Mods?
Note: Do not use if you have multiple users (including a guest user)
Lots more information here: https://plus.google.com/u/1/+DeesTroy/posts/i33ygUi7tiu
I strongly recommend that kernel developers start building the touch drivers into the kernel instead of depending on modules to ensure a fully functional TWRP since recovery is now part of the boot partition.
Be careful about what you install on your device as far as kernels and ROMs go. I think there is a high potential for losing the ability to decrypt because of the OS and patch level tags that are included in the boot image and the anti-rollback features that Google has implemented.
MTP does not work in TWRP on the Pixel 2 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
Pixel 2:
https://twrp.me/google/googlepixel2.html
https://dl.twrp.me/walleye/
Pixel 2 XL:
https://twrp.me/google/googlepixel2xl.html
https://dl.twrp.me/taimen/
Reserved!
Hey Dees Troy
sounds good, does it work with DP 8.1 bootloader?
So happy to see it.
Nice
What a joy it is to see this post today. Thank you!!
Thank you! You're a hero.
I'm dying to root my Pixel 2. Does anyone know whether this alpha release of TWRP can be used to install SuperSU (and suhide)? I'm afraid to try.
Spire42 said:
Thank you! You're a hero.
I'm dying to root my Pixel 2. Does anyone know whether this alpha release of TWRP can be used to install SuperSU (and suhide)? I'm afraid to try.
Click to expand...
Click to collapse
i tried flashing SuperSU v2.82 SR5 and phone would not boot into system. It just kept booting into bootloader.
To get my phone working again, I needed to flash the boot.img from the Pixel 2 Factory image via
Code:
fastboot flsah boot boot.img
i've gathers recovery / kernel logs - however since TWRP boots i will post them in the SuperSU forum.
Code:
fastboot boot twrp-3.1.1-alpha1-walleye.img
I've tried to boot to this alpha on my Pixel 2, and it just sits there and does nothing. I've tried two different cables. If I unplug, it fails, obviously.
Code:
fastboot devices
shows my device and I'm definitely on the bootloader screen.
Any ideas? I re-downloaded the sdk platform tools as well as the latest usb driver to see if that was the problem, but it wasn't the problem.
deepdvd said:
Code:
fastboot boot twrp-3.1.1-alpha1-walleye.img
I've tried to boot to this alpha on my Pixel 2, and it just sits there and does nothing. I've tried two different cables. If I unplug, it fails, obviously.
Code:
fastboot devices
shows my device and I'm definitely on the bootloader screen.
Any ideas? I re-downloaded the sdk platform tools as well as the latest usb driver to see if that was the problem, but it wasn't the problem.
Click to expand...
Click to collapse
Connected to PC vie USB 3 port?
Try with USB 2 if you have it. I've read people having success with it.
Natakranta said:
Connected to PC vie USB 3 port?
Try with USB 2 if you have it. I've read people having success with it.
Click to expand...
Click to collapse
I tried using a third USB port, and it worked. Thanks! I thought that testing two different ports would have been enough, but apparently the third time's the charm.
deepdvd said:
I tried using a third USB port, and it worked. Thanks! I thought that testing two different ports would have been enough, but apparently the third time's the charm.
Click to expand...
Click to collapse
Sent from my Sony Xperia Z1 using XDA Labs
marc.ientilucci said:
i tried flashing SuperSU v2.82 SR5 and phone would not boot into system. It just kept booting into bootloader.
To get my phone working again, I needed to flash the boot.img from the Pixel 2 Factory image via
Code:
fastboot flsah boot boot.img
i've gathers recovery / kernel logs - however since TWRP boots i will post them in the SuperSU forum.
Click to expand...
Click to collapse
Same issue here, tried with Snoke kernal and get the same problem
Does this mean root is getting close?
stackz07 said:
Does this mean root is getting close?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-2/how-to/how-root-magisk-pixel-2-t3698713
Anyone out here that can basically decrypt in twrp? Who can see all the folders and backup like me? I can flash a zip from install? Anyone else?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------
Dees_Troy said:
Note, this is BROKEN. Decrypt does not work yet and because it does not work, a lot of other things like backup and restore don't work. You can't transfer files with MTP. I have no idea what will happen if you try to factory reset. Basically, a lot of stuff won't work so if you're scared or can't afford to lose data or be unable to use your device, DON'T use this. I strongly recommend that you have the factory images already downloaded and know how to reflash them if needed.
I am not providing a way to permanently flash TWRP at this time. You should use:
fastboot boot /path/to/twrp.img
This will one-time temp boot TWRP so you can do whatever like maybe adb sideload a zip or something.
I am working on decrypt. The Pixel 2 uses a new embedded secure element chip from NXP. Most of the crypto implementation is done in Java and not in native C/C++ so it's going to take a while to convert all of this code and its many layers into something that TWRP can run. Be patient. I'll get it eventually (probably).
Pixel 2:
https://twrp.me/google/googlepixel2.html
https://dl.twrp.me/walleye/
Pixel 2 XL:
https://twrp.me/google/googlepixel2xl.html
https://dl.twrp.me/taimen/
Click to expand...
Click to collapse
@despairfactor can see all the files in twrp and flash from install tab as well as me from my 2 XL?
Sent from my Nexus 6 using Tapatalk
bryantjopplin said:
Anyone out here that can basically decrypt in twrp? Who can see all the folders and backup like me? I can flash a zip from install? Anyone else?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------
@despairfactor can see all the files in twrp and flash from install tab as well as me from my 2 XL?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
FYI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk
bryantjopplin said:
FYIView attachment 4321138View attachment 4321139View attachment 4321140
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Forgot this. Only did vendor. Will do all later.
Sent from my Nexus 6 using Tapatalk
Anyone willing to reflash magisk via twrp and pull recovery.log immediately after from twrp and upload?????
Sent from my Nexus 6 using Tapatalk
bryantjopplin said:
Anyone willing to reflash magisk via twrp and pull recovery.log immediately after from twrp and upload?????
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Can do after work.
In about 8 hours [emoji6]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi Guys, i need help, i was playing with my leeco x720 flashing several Rooms, Mooka, Google Experience, after i flash EUI 20 s, flashable zip and the system works well.
After i download anf flash > LEX720-ML_BB72-5902303282S-5.9.023S_Root_V1 , always performing the right wipes etc.
after this ill never be abled to have new system again, i have always the twrp ...
Now when i try to flash again the EUI 20s zip, it seems flash fast , like 4 sec, and on reboot system, first start, stuck on leeco logo.\when i try to flash lineageos 15.1, show error 7.
Plz help.
Update >
i take a recovery backup from another leecco findet online.
o put it on twrp backups, restore it from twrp 3.2.1 ..
first bot crashes many apps on the start messages etcc soo i bot to recovery again, factory reset ...now stuc on EUI logo.
UPDATE :
all the problem can be solved with MAURO Tool or TOOL_ALL_IN_ONE .
for more info go to thread > https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
dont forget to thanks @mauronofrio DDDDD
Ferdinantstr said:
Hi Guys, i need help, i was playing with my leeco x720 flashing several Rooms, Mooka, Google Experience, after i flash EUI 20 s, flashable zip and the system works well.
After i download anf flash > LEX720-ML_BB72-5902303282S-5.9.023S_Root_V1 , always performing the right wipes etc.
after this ill never be abled to have new system again, i have always the twrp ...
Now when i try to flash again the EUI 20s zip, it seems flash fast , like 4 sec, and on reboot system, first start, stuck on leeco logo.\when i try to flash lineageos 15.1, show error 7.
Plz help.
Click to expand...
Click to collapse
If ur on latest twrp and 20s+ firmware I would go into fastboot and make sure ur bootloader didn't get locked for some mysterious reason.I doubt it but worth checking.never know.lol...hope u get it fixed.good luck.
marcukial said:
If ur on latest twrp and 20s+ firmware I would go into fastboot and make sure ur bootloader didn't get locked for some mysterious reason.I doubt it but worth checking.never know.lol...hope u get it fixed.good luck.
Click to expand...
Click to collapse
thanks for reply, i have twrp 3.2.1 but no system so i cant verify if my latest is 20s and if boatloader is locked...? you think maybe the boatloaderr its relocked after i flash the EUI 21s stock zip ? .. now i m trying to restore from an twro recovery make from another person..
Lex727 bootloader unlock
1.download bootloader unlock zip.
https://www.mediafire.com/file/nvsw2fhnt1e2q7d/x727-5.8.019s_bootloader-unlock.zip
Have ADB/Fasboot tools on your computer*(I am not helping you here, it you're lucky, maybe your friends will help)Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device*(again, I'm not helping with that)Make sure adb can see your device when you run "adb devices"Run "adb reboot bootloader"Run "fastboot devices" to make sure you see your deviceRun "fastboot oem unlock-go" to unlock your device temporarilyRun "fastboot oem device-info" to verify unlock statusRun "fastboot boot recovery_twrp.img"*(or whatever the twrp image filename is on your computer)to boot up to TWRP
If this fails you need to flash bootloader.
Fastboot flash emmc_appsboot.mbn.
I person personally did this command and drag and drop file minimal adb program work perfect.
If you need this program here it is.
https://www.mediafire.com/file/9gxfrob1d3idric/minimal_adb_fastboot_v1.4_setup.exe
Sent from my LEX727 using xda premium[/QUOTE]
Sent from my LEX720 using xda premium
If you need stock OS, you have to install stock recovery;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
If you need custom ROM, you have to flash correct recovery (3.2 is good for Oreo, earlier for Nougat). In twrp you should to transfer correct file, or try to adb push commands (googling for it).
Ferdinantstr said:
thanks for reply, i have twrp 3.2.1 but no system so i cant verify if my latest is 20s and if boatloader is locked...? you think maybe the boatloaderr its relocked after i flash the EUI 21s stock zip ? .. now i m trying to restore from an twro recovery make from another person..
Click to expand...
Click to collapse
Possibly. Go to fastboot and type fastboot oem device-info to check.
marcukial said:
Possibly. Go to fastboot and type fastboot oem device-info to check.
Click to expand...
Click to collapse
Thank U, ill try after the FQL mode...if dont work..ill do this..thnx.:good::good::good::good:
ps, the first method didnt work, now i verify on adb, is <
(bootloader) Device unlocked: true
so ok now i have to flash twrp again and after flash supersu, after flash an normal room ?
Ferdinantstr said:
Thank U, ill try after the FQL mode...if dont work..ill do this..thnx.:good::good::good::good:
Click to expand...
Click to collapse
ps, the first method didnt work, now i verify on adb, is <
(bootloader) Device unlocked: true
so ok now i have to flash twrp again and after flash supersu, after flash an normal room ?
Ferdinantstr said:
ps, the first method didnt work, now i verify on adb, is <
(bootloader) Device unlocked: true
so ok now i have to flash twrp again and after flash supersu, after flash an normal room ?
Click to expand...
Click to collapse
AFTER I flash the twrp and supersu, i copy the room files to internal storage
, the problem persist .. .
Ferdinantstr said:
AFTER I flash the twrp and supersu, i copy the room files to internal storage
, the problem persist .. .
Click to expand...
Click to collapse
Try format data in twrp maybe if u haven't tried.and don't flash SuperSU until after u flash a rom like lineage or aicp etc.I would stay clear of flashing stock factory ROMs in twrp unless it has been modded to flash in twrp.
marcukial said:
Try format data in twrp maybe if u haven't tried.and don't flash SuperSU until after u flash a rom like lineage or aicp etc.I would stay clear of flashing stock factory ROMs in twrp unless it has been modded to flash in twrp.
Click to expand...
Click to collapse
always 7 error., on twrp, dont letme flash lineageos or stock rooms.
Ferdinantstr said:
always 7 error., on twrp, dont letme flash lineageos or stock rooms.
Click to expand...
Click to collapse
Try to flash a different rom.
Sent from my LEX727 using xda premium
mchlbenner said:
Try to flash a different rom.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
ill try 4 different rooms so i dont think is room problems . .
the last i try pixel experience.. and the same.
start flashing and endo after 2 seconds with the indication >
flashing system files...
flashing boot image..
script succeded > resulta was (1.000000)
updating partiton details....
done... ]
THE SAME LIKE THE OTHER ROOMS.... i think i do something wrong,,but i dont know what../:crying:
Followed my guide? You should go to stock, then do all the process again.
Ferdinantstr said:
ill try 4 different rooms so i dont think is room problems . .
the last i try pixel experience.. and the same.
start flashing and endo after 2 seconds with the indication >
flashing system files...
flashing boot image..
script succeded > resulta was (1.000000)
updating partiton details....
done... ]
THE SAME LIKE THE OTHER ROOMS.... i think i do something wrong,,but i dont know what../:crying:
Click to expand...
Click to collapse
I have the exact same problems, my device is completly useless right now :crying:
StormPlayzz said:
I have the exact same problems, my device is completly useless right now :crying:
Click to expand...
Click to collapse
Go back to twrp 3.2.0.0
Sent from my LEX727 using xda premium
mchlbenner said:
Go back to twrp 3.2.0.0
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Where to find that?
StormPlayzz said:
Where to find that?
Click to expand...
Click to collapse
This should be it.
I don't use the news one
https://www.mediafire.com/file/0hhywv26neg86q1/recovery.zip
Sent from my LEX727 using xda premium
mchlbenner said:
This should be it.
I don't use the news one
https://www.mediafire.com/file/0hhywv26neg86q1/recovery.zip
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Still getting Error 7
[Patched_Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholGl4AULW_tHKaCrg
https://mega.nz/#!NUBmnawT!Pgrorx3HWBjPjv_DjeQZVN76VnwzqT1cn0u1U0MzgSA
[TWRP Backup Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholRaoTR_Nvxq7v6kw
https://mega.nz/#!0EZkXSDB!WYcB8wt1Eu92GZvVTExeaWRN9y1zQBLOjULCuKRHvR8
[Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholJT3zo4rEY9oO0lQ
https://mega.nz/#!URYmHIxZ!i77uZQZ2V0aWBRNewxLY1UJPPhuhg2wicowDQMVETo4
Be careful as Always, only use this img for booting so you can install magisk direct.
To restore your boot image with trwp:
Unzip twrp and add to root of the sdcard,
fastboot boot twrp daisy zero(sdcard fixed version) and restore trwp backup, don't touch anything else, and reboot by holding power button.
Fastboot boot patched_boot.img to boot phone for direct install of magisk. ALWAYS RECOMENDED.
thanks a lot, can you provide also an unmodified 10.30.0 boot image?
Yep, a non patched would be also useful. Which Magisk version did you use to patch the image?
Still bootlooping after flashing it.
fastboot boot patched_boot.img
fastboot reboot
pippozio said:
thanks a lot, can you provide also an unmodified 10.30.0 boot image?
Click to expand...
Click to collapse
I can provide an unmodified trwp made boot.img from my phone, thats why i said not to flash the patched boot image, and to only boot from it, twrp backups are .wim, i just changed the .wim extension to .img and patched it. As far as im aware its a normal packed boot.img but renamed .wim for trwp to flash it, ill provide it but use at own risk. https://1drv.ms/u/s!AqlJY73bUA7rholIeKoHAB8o6s94gA .Rename boot.img if your going to flash it.
anzhaki said:
Yep, a non patched would be also useful. Which Magisk version did you use to patch the image?
Still bootlooping after flashing it.
fastboot boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
I used magisk v18 latest. Unmodified boot.img is in one of the posts. Ive used it so it should be fine, but still its done at your own risk. Im not sure how you will stop it bootlooping, sounds like magisk messed up the install when re applying after OTA.
anzhaki said:
Yep, a non patched would be also useful. Which Magisk version did you use to patch the image?
Still bootlooping after flashing it.
fastboot boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
Dont fastboot reboot, just boot from it, if your rebooting then your wiping the temp boot.
boe323 said:
I used magisk v18 latest. Unmodified boot.img is in one of the posts. Ive used it so it should be fine, but still its done at your own risk. Im not sure how you will stop it bootlooping, sounds like magisk messed up the install when re applying after OTA.
Click to expand...
Click to collapse
The same thing happened when I updated from oreo to pie using the method to maintain root. If I remember well I solved the problem by flashing stock boot.img with
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
then it should normally boot and after that it should be ok to manually patch the boot image.
Maybe it's better to wait an image extracted from OTA
Thanks anyway
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
boe323 said:
Dont fastboot reboot, just boot from it, if your rebooting then your wiping the temp boot.
Click to expand...
Click to collapse
Unfortunately still bootloops D:
anzhaki said:
The same thing happened when I updated from oreo to pie using the method to maintain root. If I remember well I solved the problem by flashing stock boot.img with
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
then it should normally boot and after that it should be ok to manually patch the boot image.
Maybe it's better to wait an image extracted from OTA
Thanks anyway
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
Unfortunately still bootloops D:
Click to expand...
Click to collapse
Try anzhaki's method, he said it works but i cant confirm it as ive never run into problems (touch wood). Dont go making things worse by flashing custom stuff, try using his method and factory reset.
anzhaki said:
The same thing happened when I updated from oreo to pie using the method to maintain root. If I remember well I solved the problem by flashing stock boot.img with
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
then it should normally boot and after that it should be ok to manually patch the boot image.
Maybe it's better to wait an image extracted from OTA
Thanks anyway
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
Unfortunately still bootloops D:
Click to expand...
Click to collapse
boe323 said:
Try anzhaki's method, he said it works but i cant confirm it as ive never run into problems (touch wood). Dont go making things worse by flashing custom stuff, try using his method and factory reset.
Click to expand...
Click to collapse
I m in bootloop. Anyone help me the pie fastboot image link? Thanks.
There isn't one for v10.0.30.0 at present .
boe323 said:
There isn't one for v10.0.30.0 at present .
Click to expand...
Click to collapse
your unmodified boot.img shows 64 mb, it should be 26-27 mb. no?
and can you upload it another server plz?
---------- Post added at 09:22 AM ---------- Previous post was at 09:09 AM ----------
Flashed your unmodified boot.img. no luck, still in bootloop.
Is there any inprovements with this ypdate
boe323 said:
[Patched_Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholGl4AULW_tHKaCrg
[TWRP Backup Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholRaoTR_Nvxq7v6kw
[Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholJT3zo4rEY9oO0lQ
Be careful as Always, only use this img for booting so you can install magisk direct.
To restore your boot image with trwp:
Unzip twrp and add to root of the sdcard,
fastboot boot twrp daisy zero(sdcard fixed version) and restore trwp backup, don't touch anything else, and reboot by holding power button.
Fastboot boot patched_boot.img to boot phone for direct install of magisk. ALWAYS RECOMENDED.
Click to expand...
Click to collapse
thanks, this boot image solved my bootloop problem
pippozio said:
thanks, this boot image solved my bootloop problem
Click to expand...
Click to collapse
Hi, which one did you flash and with what command?
Nvm, I used the last one.
What is the procedure to update ota with magisk? Restore image with magisk, reboot, update ota and then flash modified boot.img?
Thx in advance.
Me tio want to update and when i see that people are having troubles. What is the correct procedure for this?
Please help me, im rooted at v10.0.2.0 but when i unsintall/revert my boot.img in magisk it say's "store backup does not exist" . i factory reset my phone when i got a problem in substratum . didn't know that it will be remove by doing that, what should i do next? i want to OTA update my Phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mms047 said:
your unmodified boot.img shows 64 mb, it should be 26-27 mb. no?
and can you upload it another server plz?
---------- Post added at 09:22 AM ---------- Previous post was at 09:09 AM ----------
Flashed your unmodified boot.img. no luck, still in bootloop.
Click to expand...
Click to collapse
No , original is bigger, only when you patch it ,it goes smaller, from other ppl who know about this stuff it's just padding
iniro said:
What is the procedure to update ota with magisk? Restore image with magisk, reboot, update ota and then flash modified boot.img?
Thx in advance.
Click to expand...
Click to collapse
I wouldnt try magisk ota method, theres reports of bootloops after OTA, best is to return everything to stock, disabale modules and reboot, uninstall modules and reboot, then uninstall magisk and reboot, any modded hosts need to be stock, audio/soundfx need to be stock, basically anything to do with system should be stock. If you get into any install issues with ota, then download the 10.0.20.0 rom from Mi's website and use flash all except storage, this will keep data and give you a fresh system image.
barumbads said:
Please help me, im rooted at v10.0.2.0 but when i unsintall/revert my boot.img in magisk it say's "store backup does not exist" . i factory reset my phone when i got a problem in substratum . didn't know that it will be remove by doing that, what should i do next? i want to OTA update my Phone.
Click to expand...
Click to collapse
Redo your system image with the rom on Mi's website, use flash all except storage.