Database Info

Recovery Testing SM-T330NU CLOSED

OKay, so
the thread for our working Philz/Advanced CWM recovery for the sm-t330nu is located here;
http://forum.xda-developers.com/tab-4/development/recovery-philz-smnu-t2980094
more work to do but will need to wait till i have the device.
-------------------------------------
NOTE- @gr8nole has opened TWRP recovery thread in development
http://forum.xda-developers.com/tab-4/development/twrp-2-8-2-0-unofficial-t330-t2980716
--------------------------------------
This thread will be closed as it has served it's purpose. Thanks everyone ! =)

I'm a wus and don't want to test but thank you for helping move this device forward. Looking forward to some good news here.

xnatex21 said:
I'm a wus and don't want to test but thank you for helping move this device forward. Looking forward to some good news here.
Click to expand...
Click to collapse
x,
hi,
no worries, i completely understand. as it happens i may be recieving an sm-t330nu by way of donation sometime soon
specifically for the purpose of developing. This call is meant for those with experience. I will say i am working towards
putting together device trees for sm-t33x in general just in case.
be good
m

I considered looking into a recovery build for this device. But, based on the lack of responses to this thread, I don't see enough interest to make it a worthwhile endeavor. I see several threads asking for a recovery, but no responses when someone builds a test???

gr8nole said:
I considered looking into a recovery build for this device. But, based on the lack of responses to this thread, I don't see enough interest to make it a worthwhile endeavor. I see several threads asking for a recovery, but no responses when someone builds a test???
Click to expand...
Click to collapse
I got this device just yesterday, Big improvement from the T210R for sure. Of course we all want a recovery but don't want to risk our tabs

gr8nole said:
I considered looking into a recovery build for this device. But, based on the lack of responses to this thread, I don't see enough interest to make it a worthwhile endeavor. I see several threads asking for a recovery, but no responses when someone builds a test???
Click to expand...
Click to collapse
Yeah, it's a little meh. But mainly i'm working on getting my tree for this tab sorted
while i wait for it to arrive. Maybe the OP is a little harsh. ... meh.
:silly:
m

Rusell said:
I got this device just yesterday, Big improvement from the T210R for sure. Of course we all want a recovery but don't want to risk our tabs
Click to expand...
Click to collapse
No risk, no reward.

moonbutt74 said:
No risk, no reward.
Click to expand...
Click to collapse
Especially since it is a new device...
What could go wrong?? What is the worst thing that could happen??

Flashing a bad recovery is not really even a risk. I probably flashed 50 bad recoveries when trying to get the T210 recoveries working. As long as you have stock recovery image to re-flash (Odin) there really isn't any risk.

gr8nole said:
Flashing a bad recovery is not really even a risk. I probably flashed 50 bad recoveries when trying to get the T210 recoveries working. As long as you have stock recovery image to re-flash (Odin) there really isn't any risk.
Click to expand...
Click to collapse
Does the Firmware from sammobile .com for SM-T330NU contain stock recovery?

Rusell said:
Does the Firmware from sammobile .com for SM-T330NU contain stock recovery?
Click to expand...
Click to collapse
It should, but MB has it posted in the OP also. :good:

Rusell said:
Does the Firmware from sammobile .com for SM-T330NU contain stock recovery?
Click to expand...
Click to collapse
The stock recovery is linked to in OP
Rusell,
I mean this in the best way,
You may not meet the requirements I set out in OP
for a tester. Which is nothing bad. If you're willing to wait, I should be receiving my tab
this coming week, at which time I won't need a tester . My effort is geared toward getting
things moving.
m

Well i flashed and it just keeps rebooting over and over trying to get into recovery, Here is what is read at the top left corner every time:
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
It wont let me go further then just seeing the "Samsung galaxy Tab 4" splash screen.

Rusell said:
Well i flashed and it just keeps rebooting over and over trying to get into recovery, Here is what is read at the top left corner every time:
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
It wont let me go further then just seeing the "Samsung galaxy Tab 4" splash screen.
Click to expand...
Click to collapse
Okay, connect via adb and see if you can get logcat,
the hang means the kernel is good, but the fstab may be wrong, or i need to patch init and adb.
thanks,
m

moonbutt74 said:
Okay, connect via adb and see if you can get logcat,
the hang means the kernel is good, but the fstab may be wrong, or i need to patch init and adb.
thanks,
m
Click to expand...
Click to collapse
give me ambitmto get to my comp, if you're willing to run another test pm me please.

moonbutt74 said:
give me ambitmto get to my comp, if you're willing to run another test pm me please.
Click to expand...
Click to collapse
So how do i take logcat from adb and when should i do it,While flashing or while booting?
Excuse me since im a newb

Rusell said:
So how do i take logcat from adb and when should i do it,While flashing or while booting?
Excuse me since im a newb
Click to expand...
Click to collapse
Oops , okay skip that, okay this test is a fail you can refurn to stock and delete the custom,
i will mark test 1 as fail and take it down.
m

Rusell,
okay, round 2 if you're up for it,
ROUND 2 http://d-h.st/8U5f -modified default.prop,fstab temp test with prebuilt kernel and dt.img
the kernel should be msm8226, if this fails i will revisit my config and run a new build,
m

and if you are really feeling frisky, give this TWRP a try.
http://d-h.st/Qm3

gr8nole said:
and if you are really feeling frisky, give this TWRP a try.
http://d-h.st/Qm3
Click to expand...
Click to collapse
hey, if you're jumping in cool, how do i add you as contributor ?
m

Note 5 keeps boot loopig after odin back to stock?

So Ive tried going back to stock with odin using the COJ5 software. Baseband was previously COI5 with custom rom and kernel. I received my Gear VR today and it wont play with the COI5 baseband at all. What should I do???? Phone just keeps bootlooping and freezing at the T-Mobile screen. Flash passes in Odin fine. Any help?

Well false alarm guys and gals. I had to trick the phone into going in recovery then I did a factory wipe that way and I'm good to go! Just figured I would mention this incase any others had my issue!

Yeah, you gotta do the wipe.

also mentioned in the thread that most people have used to flash to 6.0 http://forum.xda-developers.com/tmo...ndroid-6-0-marshmallow-note-5-t3250812/page39

playya said:
also mentioned in the thread that most people have used to flash to 6.0 http://forum.xda-developers.com/tmo...ndroid-6-0-marshmallow-note-5-t3250812/page39
Click to expand...
Click to collapse
I dont think he wouldve searched there since it seems he was upgrading from COI5 to COJ5 and not downgrading from the leaked MM build..

pcriz said:
I dont think he wouldve searched there since it seems he was upgrading from COI5 to COJ5 and not downgrading from the leaked MM build..
Click to expand...
Click to collapse
I guess you're correct I would have searched bootlooping and looked at everything and tried everything. But that's just me thanks for your reply

playya said:
I guess you're correct I would have searched bootlooping and looked at everything and tried everything. But that's just me thanks for your reply
Click to expand...
Click to collapse
Frankly wiping (be it cache or a full factory) should be troubleshooting step number 1 when it comes to a boot loop.

pcriz said:
Frankly wiping (be it cache or a full factory) should be troubleshooting step number 1 when it comes to a boot loop.
Click to expand...
Click to collapse
Again I can't argue that point either I'm old school I'm going to search my ass off before I post a thread. Thats how I do my searches and I start reading other stuff you actually find other things that may help you down the line. But that's just me

You also need the pit file. Otherwise it won't boot. You'd get into boot loop.

TheUndertaker21 said:
You also need the pit file. Otherwise it won't boot. You'd get into boot loop.
Click to expand...
Click to collapse
Nah he shouldn't need a pit for COJ5 unless he damages a partition which doesn't seem likely as he was only upgrading.
Just boot into recovery and wipe everything, and Odin COJ5 again.
Sent from my SM-N920T using Tapatalk

7.1.2 Upgrade Help

Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.

Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available

bush911 said:
Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available
Click to expand...
Click to collapse
I have tried to stay away from flash fire because I know a couple buddies who soft-bricked by using it.

xxbilxx said:
Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.
Click to expand...
Click to collapse
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2

TonikJDK said:
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
Click to expand...
Click to collapse
I don't have to sideload the March security patch first?

xxbilxx said:
I don't have to sideload the March security patch first?
Click to expand...
Click to collapse
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).

TonikJDK said:
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).
Click to expand...
Click to collapse
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.

xxbilxx said:
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.
Click to expand...
Click to collapse
Correct, you want N2G47E.

TonikJDK said:
Correct, you want N2G47E.
Click to expand...
Click to collapse
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!

xxbilxx said:
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!
Click to expand...
Click to collapse
No problem at all. Second to the last post in the same thread I linked you to before. It all still works fine on 7.1.2. Did all of this myself yesterday afternoon.

Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways

Download the OTA, Flash it from TWRP, reflash twrp and reboot

mikeprius said:
Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways
Click to expand...
Click to collapse
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.

robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
yeah saved it. There was only one section that had the w- and it was right before the update image. I can try it again at some point later on but that's what I did. I tried to sideload adb the OTA first which does not wipe data but kept getting an error saying device not found and emulator.

robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
Your instructions worked perfectly for me. I'm nor sure what setup the other guy had, but I did make sure I removed the -w like 20 times.

Juli112 said:
Download the OTA, Flash it from TWRP, reflash twrp and reboot
Click to expand...
Click to collapse
are you on the latest twrp rc2 or rc1?

Has anyone received the update ota on a stock google pixel XL for verizon. Mine keeps telling me I am current?

[UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry

Moto E4 XT1766
Partition Index & Bootloader Updater
Build No. NCQ26.69-64
TWRP Flashable Installer​
WARNING: DO NOT use this updater.zip if your device has been updated to any firmware version newer than NCQ26.69-64. Downgrading can hard brick your device. If your device has been upgraded to a newer build, or if you aren't sure, proceed to this thread: https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749, which is the latest firmware -- NCQS26.69-64-5.
DISCLAIMER: Although I have thoroughly tested this update installer, I am not responsible for any adverse effects incurred from using it. Because this installer does flash bootloader and other sensitive partitions on your device, charging your device to at least 50% is recommended prior to proceeding.
PURPOSE:
This installer updates your partition index and bootloader components to Build No. NCQ26.69-64. If you are not running the stock Android OS, or have never updated your device to Build No. NCQ26.69-64, this installer will update your partition index (gpt.bin) and bootloader components to the most current firmware version. For custom ROM users, this alleviates the task of reverting to an unmodified stock Android OS, installing OTAs, and then reinstalling your daily driver custom ROM -- all to simply update your bootloader and partition index. Specifically, this installer updates the following partitions:
/rpm - primary bootloader
/sbl1 - secondary bootloader
/aboot - application bootloader
/tz - trust zone (bootloader component)
/devcfg - device configuration (component)
/keymaster - bootloader component
/cmnlib - bootloader component
/cmnlib64 - bootloader component
/prov - bootloader component
INSTRUCTIONS:
Download the updater zip from the below link and save it to internal or external storage. Boot into TWRP, install the zip, and reboot. Your partition index and bootloader are now up to date. Note: this update can be installed on a stock or custom ROM.
DOWNLOAD LINK:
https://drive.google.com/file/d/18eFi6E1YnNB68OwmEJeH0FGmAVsE89Jo/view?usp=drivesdk

Very cool, thanks brother
Sent from my XT1766 using Tapatalk

@MotoJunkie01 it worked fine, but I got this error. Anything to worry about?
Thanks for this bro.

@madbat99, nothing to worry about. It's a pseudo-error due to a conflict in the update-binary. I'll iron it out just because it messes with my OCD. :good:

MotoJunkie01 said:
@madbat99, nothing to worry about. It's a pseudo-error due to a conflict in the update-binary. I'll iron it out just because it messes with my OCD. :good:
Click to expand...
Click to collapse
I figured. Just thought I'd ask. Thanks again

madbat99 said:
@MotoJunkie01 it worked fine, but I got this error. Anything to worry about?
Thanks for this bro.
Click to expand...
Click to collapse
How did you screenshot in the recovery?

frederickrl said:
How did you screenshot in the recovery?
Click to expand...
Click to collapse
Same way as in the os. Power + volume down

madbat99 said:
Same way as in the os. Power + volume down
Click to expand...
Click to collapse
I thought it may be, twrp is so advanced thx!

Hard bricked
I need help my phone is hard bricked just showing on PC as an unknown usb device..
I have flashed wrong firmware my device sperry xt1766..
Please help

My phone xt1766 is bricked by flashing wring firmware on pc showinh qhs usb dload and unable to power on...
please help

hassanshaikhhyd said:
My phone xt1766 is bricked by flashing wring firmware on pc showinh qhs usb dload and unable to power on...
please help
Click to expand...
Click to collapse
Your phone is most likely in edl not sure what solution would be at this time

skullkid383 said:
Your phone is most likely in edl not sure what solution would be at this time
Click to expand...
Click to collapse
is there change of its solution in future

hassanshaikhhyd said:
is there change of its solution in future
Click to expand...
Click to collapse
I might be getting second more e4 when I get paid as a test subject cause my friend had same problem so I want to find a solution for this if and when I do I'll me u know

Bricked
Same prob, flashed it on twrp and everything looked good until it shut off completely and never powered back on.
Tried hard reset. won't even go into recovery/

I just forresst gumped my xt1765 too, i just noticed this update was for xt1766, not xt1765. Been trying out RR, AICP and Lineage with minor bugs, then thought this update might correct minor bugs since not build as specified here. Anyways, flashed favorite after trying all custom roms for few weeks at a time and decided that LineageOS was my favorite with least bugs/issues but after flashing LineageOS it felt just right. Like finding your favorite fitting lost pair of jeans or hooking up with an ex again....just felt right...anyways, short story and heartbreak after I flashed this zip, my beloved moto gen E4, my nickname, get it Jenny no. 4? Our last kiss was the reboot system kiss and caress....and just like that, she was gone forever...no power, no recovery, no nothing at all... and just now the small print cognizant epiphany opened my dreamy happily perpetually sleeping eyes. the perfect device, fast as i wanted, tweaked like i liked and she never complained or got mad or talked back well she did when i needed googlies answered...this zip was for the sperry xt1766...now my moto genE4 is gone forever....
Ive been flashing for years all kinds of different devices and never have I had this type of problem..there was always the fallback flashing back to stock if bootlooped or soft bricked. Flash, boom, fixed, start over. Never have I encountered the no power no charge no nothing one last kiss goodbye, EVER. Well, life lesson learned. I just needed to get that off my chest. I feel a little better now guys, thanks for listening.

cuervo233 said:
I just forresst gumped my xt1765 too, i just noticed this update was for xt1766, not xt1765. Been trying out RR, AICP and Lineage with minor bugs, then thought this update might correct minor bugs since not build as specified here. Anyways, flashed favorite after trying all custom roms for few weeks at a time and decided that LineageOS was my favorite with least bugs/issues but after flashing LineageOS it felt just right. Like finding your favorite fitting lost pair of jeans or hooking up with an ex again....just felt right...anyways, short story and heartbreak after I flashed this zip, my beloved moto gen E4, my nickname, get it Jenny no. 4? Our last kiss was the reboot system kiss and caress....and just like that, she was gone forever...no power, no recovery, no nothing at all... and just now the small print cognizant epiphany opened my dreamy happily perpetually sleeping eyes. the perfect device, fast as i wanted, tweaked like i liked and she never complained or got mad or talked back well she did when i needed googlies answered...this zip was for the sperry xt1766...now my moto genE4 is gone forever....
Ive been flashing for years all kinds of different devices and never have I had this type of problem..there was always the fallback flashing back to stock if bootlooped or soft bricked. Flash, boom, fixed, start over. Never have I encountered the no power no charge no nothing one last kiss goodbye, EVER. Well, life lesson learned. I just needed to get that off my chest. I feel a little better now guys, thanks for listening.
Click to expand...
Click to collapse
The old dreaded hard brick. Lights out time. Been there done that. Have you read this method to restore your device using a microSD card? https://forum.xda-developers.com/moto-e4/how-to/untested-moto-e4-xt1765-metropcs-t3843657
This guide for the xt1766 gives overview to the method as well. https://forum.xda-developers.com/moto-e4/how-to/e4-sprint-xt1766-unbrick-easy-sdcard-t3833408/page2
Basically, download the unbrick image for your xt1765 from the 1st link I posted above. Then, see the second link on the xt1766 for instructions on attempting the unbrick.

I had 1766 that broke so I put the back of it in another Moto e4 plus....just wondering if I have any options...

Amphetmine Gene said:
I had 1766 that broke so I put the back of it in another Moto e4 plus....just wondering if I have any options...
Click to expand...
Click to collapse
Wait...seen this before. Bad form pooping the same post in multiple threads.
https://forum.xda-developers.com/mo...droid-7-1-1-rom-moto-e4-t3885821/post79275927

Davey126 said:
Wait...seen this before. Bad form pooping the same post in multiple threads.
https://forum.xda-developers.com/mo...droid-7-1-1-rom-moto-e4-t3885821/post79275927
Click to expand...
Click to collapse
Thanks man, yea only 2nd time I've ever posted anything...but good to no

No permission to downloader
HI.
I need this file.
Google not permission to downloader

ADB and 8T

Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R

Try nother USB C cable. Some not able to handle data.

rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!

Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/

BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!

Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R

Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.

BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??

Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.

BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!

Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...

Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11

BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,

Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".

BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,

Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!

Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R

Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.

BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..

Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone