Related
I got my one plus one 64gb from a friend and it has ColorOs ver 1.2.0 installed on it. He said that the device is new and has never been used before but this seems odd to me as it should have come with CM11S pre installed. It has the "Global version" logo on the back package. Is there a simple guide/way that I can use to switch to CM11S or any other rom?
dilgit said:
I got my one plus one 64gb from a friend and it has ColorOs ver 1.2.0 installed on it. He said that the device is new and has never been used before but this seems odd to me as it should have come with CM11S pre installed. It has the "Global version" logo on the back package. Is there a simple guide/way that I can use to switch to CM11S or any other rom?
Click to expand...
Click to collapse
Do some research my friend this is xda all the info you need is right in front of you but you need to read. First off check if its been rooted or has a custom recovery. Please do not use a toolkit as they may cause issues down the line. Does it say CM on the back of the phone?
Main thing is everything is simple if you just read and take your time. From the way you asked your question not sure if you ever rooted before? Google the differences my friend Google it
playya said:
Do some research my friend this is xda all the info you need is right in front of you but you need to read. First off check if its been rooted or has a custom recovery. Please do not use a toolkit as they may cause issues down the line. Does it say CM on the back of the phone?
Main thing is everything is simple if you just read and take your time. From the way you asked your question not sure if you ever rooted before? Google the differences my friend Google it
Click to expand...
Click to collapse
Thanks. I've googled this as much as I can, but can't find a way to switch from ColorOs to CM11S. I'm really stuck and need you help. The device is recognised by windows 8.1 and I transferred the CM11 r33 zip file to the device. When I go into ColorOs recovery mode on the device, and try to install CM from there, it fails. When I go to fastboot mode and I try to unlock the bootloader on the device in order to go on and flash a recovery and than root... It fails. What can I do? I can't stay with the ColorOs...
Ok. Now I'm completely stuck, on bootloader logo, and no OS!! I can still enter recovery TWRP 2.8.0.1 or fastboot mod. I have unlocked the bootloader, rooted the device, wiped all and did not backup. When I tried to flash the latest CM11 it failed and there I am. No OS and device is not recognised by computer(win 8.1) so I cannot transfer files to the device anymore... What do I do now? How do I get this working once again? Thanks for your help!!
What's the full filename of the CM11S zip you flashed?
Also, if you got your phone from a friend, where on earth did the invite I gave you go to?
Transmitted via Bacon
timmaaa said:
What's the full filename of the CM11S zip you flashed?
Also, if you got your phone from a friend, where on earth did the invite I gave you go to?
Transmitted via Bacon
Click to expand...
Click to collapse
The device coming from your invite, should arrive today and I'm sure it will be with CM11S.
The stuck device I bought second hand from a friend.
I tried to flash cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Now its not possible to transfer new files to the device and the computer does not recognise the device
when it's in fastboot mod.
dilgit said:
The device coming from your invite, should arrive today and I'm sure it will be with CM11S.
The stuck device I bought second hand from a friend.
I tried to flash cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Now its not possible to transfer new files to the device and the computer does not recognise the device
when it's in fastboot mod.
Click to expand...
Click to collapse
The invite thread is only for people that don't have the device, and that's clear in the OP, which you said you read and agreed to.
Transmitted via Bacon
timmaaa said:
The invite thread is only for people that don't have the device, and that's clear in the OP, which you said you read and agreed to.
Transmitted via Bacon
Click to expand...
Click to collapse
Dear timmaaa... When you sent me the invite I did not have the device. While it was on it's way to me, I bought a used one for my daughter. Now that's the one that is currently stuck with no OS on it. The Device I ordered from One + with the invite you sent me, arrived today, has CM11 on board and works perfectly.
dilgit said:
Dear timmaaa... When you sent me the invite I did not have the device. While it was on it's way to me, I bought a used one for my daughter. Now that's the one that is currently stuck with no OS on it. The Device I ordered from One + with the invite you sent me, arrived today, has CM11 on board and works perfectly.
Click to expand...
Click to collapse
This isn't adding up to me, you told me you wanted another invite for your son.
Transmitted via Bacon
timmaaa said:
This isn't adding up to me, you told me you wanted another invite for your son.
Transmitted via Bacon
Click to expand...
Click to collapse
Correct. And you told me it's not possible. So I purchased another device. By the way, I figured out the issue I had with the instructions I found on this link: http://forum.xda-developers.com/showthread.php?t=2765455... Worked just fine to me... Now I'm on CM11 and my daughter will get a wonderful present... timmaaa, I'm sorry if I offended you. I use the device I got today thanks to you and good people on this forum and I'm grateful to you. I needed another device and purchased one on the free market. Thank you and sorry if I did something wrong.
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
ashishv said:
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
Click to expand...
Click to collapse
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
Moatmonster said:
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
Click to expand...
Click to collapse
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
timmaaa said:
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Moatmonster said:
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Click to expand...
Click to collapse
Let me search for something that might help, leave it with me.
Transmitted via Bacon
Cheers mate.
What build of CM11S are/were you on?
Transmitted via Bacon
timmaaa said:
What build of CM11S are/were you on?
Transmitted via Bacon
Click to expand...
Click to collapse
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Moatmonster said:
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Click to expand...
Click to collapse
Ah, that's a shame, the method I was thinking of won't work since that update. This is it:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
It relies on you being able to boot a recovery as opposed to actually flashing it, and then flashing a script with that recovery. I'm 99.9% sure that you can't do that since the 38R update though. It's worth a try, connect your phone in fastboot mode and try to boot a recovery (the following command assumes that you have 'openrecovery-twrp-2.8.1.0-bacon.img' in your fastboot folder).
Code:
fastboot boot openrecovery-twrp-2.8.1.0-bacon.img
Like I said, it probably won't work, but it's worth a shot.
Transmitted via Bacon
Will have a crack when i get home, thanks for your help.
No good mate as you said.
Moatmonster said:
No good mate as you said.
Click to expand...
Click to collapse
Bummer. @zephiK, do you have any ideas?
Transmitted via Bacon
Edit: After looking through some oneplus forums, looks like they have tried to issue out a patch for this issue. Have you tried this? I would try it out first and see if it helps. Again, the below one people were really bricked, hope it helps.
I haven't had to use this, and the thread is long, but a very good read. Please go to this thread. A lot of people were able to get their devices working again by using a few tools on windows machines xp win7 and win 8.1. Basically bricked device like the one you are looking at, then installing color OS somehow brought it back to life. The drivers are in chinese, but just clicking next gets them installed correctly. Mostly everyone there is in QHUSB_Bulk mode, not sure if you are or not, but worth a shot.
Please help! I clicked to update my lg g#3 on at&t and now it is stuck in twrp recovery and I can't get it to restart normally. I had no IDea this would be a problem as this is the first time I have tried to update since I installed twrp. whe what do I do? Help
Jaison33056 said:
Please help! I clicked to update my lg g#3 on at&t and now it is stuck in twrp recovery and I can't get it to restart normally. I had no IDea this would be a problem as this is the first time I have tried to update since I installed twrp. whe what do I do? Help
Click to expand...
Click to collapse
Can't update with custom recovery.. Flash tool back to KitKat and hang out in the lounge...
2SHAYNEZ
shayneflashindaily said:
Can't update with custom recovery.. Flash tool back to KitKat and hang out in the lounge...
2SHAYNEZ
Click to expand...
Click to collapse
I don't know what "Flash tool back to KitKat and hang out in the lounge" means?
http://forum.xda-developers.com/showthread.php?t=2820827
2SHAYNEZ
Go to YouTube and search lg g3 boot loop, scroll down to the video by zedomax (how to unroot/unbrick lg g3!)
This video helped me, I did the exact same thing a few months ago! Hope this helps, I know how frightening it is.
Jaison33056 said:
Please help! I clicked to update my lg g#3 on at&t and now it is stuck in twrp recovery and I can't get it to restart normally. I had no IDea this would be a problem as this is the first time I have tried to update since I installed twrp. whe what do I do? Help
Click to expand...
Click to collapse
Hey, I got you. I had the exact same problem yesterday... It was infuriating.
So boot to TWRP, plug your phone into your computer, then in TWRP go to advanced and hit enable MTP. This should allow your computer to access the G3's files after you've connected it. If you can't, google for the LG PC drivers for your model (it's easy).
Here's the zip you need to place on your device:
http://downloads.codefi.re/autoprime/LG/LG_G3/flash2/LG_G3_Flash2FixStuckRecovery.zip
Then just flash it and you're golden!
OP: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
Have a look at this
Jaison33056 said:
Please help! I clicked to update my lg g#3 on at&t and now it is stuck in twrp recovery and I can't get it to restart normally. I had no IDea this would be a problem as this is the first time I have tried to update since I installed twrp. whe what do I do? Help
Click to expand...
Click to collapse
Hi, Have a look at this guide: http://www.mylgphones.com/lg-g2-bricked-keeps-going-right-back-to-the-recovery
It work on LG G2 model which stuck in twrp recovery.
Wish this helps!
CITIZEN INSANE, Your fix worked perfectly!
CitizenInsane said:
Hey, I got you. I had the exact same problem yesterday... It was infuriating.
So boot to TWRP, plug your phone into your computer, then in TWRP go to advanced and hit enable MTP. This should allow your computer to access the G3's files after you've connected it. If you can't, google for the LG PC drivers for your model (it's easy).
Here's the zip you need to place on your device:
http://downloads.codefi.re/autoprime/LG/LG_G3/flash2/LG_G3_Flash2FixStuckRecovery.zip
Then just flash it and you're golden!
OP: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
Click to expand...
Click to collapse
Citizen Insane, I think I love you! I was at my wits end. I literally stopped trying to fix it and decided when the at&t store opened I would go buy a new phone. Then I saw I had a new message on this post. Your fix absolutely worked like a charm and REALLY saved my bacon! I am fairly new to XDA but you saved me $700 for the cost of the new phone and I would really like to thank you! Is there anything I can do to thank you (like donate $20 to you or something)? Please let me know, man. I don't know what I would have done without your help! HUGE THANKS!!!
Really... Lol smh ...mods please close thread
2SHAYNEZ
@Jaison33056 Which OTA update caused the boot loop,the KitKat 4.4.2 D85010F or the one for Lollipop? If the one for Lollipop you may have inadvertently found a way to have a custom recovery installed with stock Lollipop firmware! Sorry if this is already general knowledge. Just got my D850 LG G3 and trying to learn all there is to have it running a custom recovery with a rooted stock Lollipop ROM ).
Jaison33056 said:
Citizen Insane, I think I love you! I was at my wits end. I literally stopped trying to fix it and decided when the at&t store opened I would go buy a new phone. Then I saw I had a new message on this post. Your fix absolutely worked like a charm and REALLY saved my bacon! I am fairly new to XDA but you saved me $700 for the cost of the new phone and I would really like to thank you! Is there anything I can do to thank you (like donate $20 to you or something)? Please let me know, man. I don't know what I would have done without your help! HUGE THANKS!!!
Click to expand...
Click to collapse
Your sincere appreciation is my reward as an XDA noobie myself. Just glad to help out <3
MaMMiTs said:
@Jaison33056 Which OTA update caused the boot loop,the KitKat 4.4.2 D85010F or the one for Lollipop? If the one for Lollipop you may have inadvertently found a way to have a custom recovery installed with stock Lollipop firmware! Sorry if this is already general knowledge. Just got my D850 LG G3 and trying to learn all there is to have it running a custom recovery with a rooted stock Lollipop ROM ).
Click to expand...
Click to collapse
The OTA bootloop was caused by the 5.0 Lollipop update. After using the fix from citizen insane it was clear that I was still on 4.4.2 KitKat. The phone quickly attempted to force me to update to lollipop again, so again I was forced to use citizen insane fix again, with the addition of shutting off OTA updates after the fix was completed through the hidden menus in the phone app. Then I quickly flashed Cyanogenmod 12 nightlies to avoid the dreaded OTA update yet again! What a pain in the ass, but on the bright side I absolutely love CM 12! My phone has never performed better. Thanks for everyone's help on XDA!
Hey Jaison does your picture messaging work after flashing CM12? Mine stopped working but texting and phone calls still work.
Hey guys,
So I flashed this rom two weeks back http://forum.xda-developers.com/oneplus-one/development/rom-paranoidandroid-5-0-alpha1-t2956478
after running cm12s nightlies for a while. The capacitive keys stopped working after I flashed this rom with the PA gapps and they still don't work after trying multiple roms + relocking unlocking bootloader and flashing 44s. Kinda frustrated cause I don't know what I can do. Any ideas?
Thanks
How did you flash 44S?
Transmitted via Bacon
I first tried flashing it through twrp. Then I used the OnePlus customer support recovery tool to get it back to stock 44s. No luck zz
Sanjitha.d said:
I first tried flashing it through twrp. Then I used the OnePlus customer support recovery tool to get it back to stock 44s. No luck zz
Click to expand...
Click to collapse
By recovery tool you mean flashing with fastboot, right?
Transmitted via Bacon
Naah it was an actual tool that OnePlus customer support gave me that restored the device t to stock. But yeah I was in bootloader when I used it. Essentially it reverted the software to factory.
So I was wondering if there were any deeper settings that might have changed. The buttons still light up but don't respond to touch.
Sanjitha.d said:
Naah it was an actual tool that OnePlus customer support gave me that restored the device t to stock. But yeah I was in bootloader when I used it. Essentially it reverted the software to factory.
So I was wondering if there were any deeper settings that might have changed. The buttons still light up but don't respond to touch.
Click to expand...
Click to collapse
That's what I meant, that's flashing with fastboot. The only thing I can think of doing is completely wiping your phone including user data (back up important files first) and flashing the stock images again, but manually this time. You can find a download and instructions in section 8 of my guide thread.
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Alright, I've also tried manually flashing the stuff myself but I'll do it according to your guide to see if it works. You don't think it could be anything software/firmware related after that yeah? I remember there was a guy who said that he had to do a full wipe to make the cap keys to work on the initial pa thread but actually no idea on how this screwed up lel
Yeah, no luck man. I flashed everything manually but no luck zz. There's nothing else I could change to see if it's the problem yeah? I'm pretty sure the problem isnt physical as I haven't dropped it or done any harm to it.
I don't know much about kernels and stuff but that wouldnt be the problem either right?
No other stock firmwares or radios or something I havent heard about?
Sanjitha.d said:
Yeah, no luck man. I flashed everything manually but no luck zz. There's nothing else I could change to see if it's the problem yeah? I'm pretty sure the problem isnt physical as I haven't dropped it or done any harm to it.
I don't know much about kernels and stuff but that wouldnt be the problem either right?
No other stock firmwares or radios or something I havent heard about?
Click to expand...
Click to collapse
So you wiped the whole phone? Even the internal storage? If so, and the problem persists, it's suggesting a hardware problem. You could try a custom kernel though just in case, it wouldn't hurt.
Transmitted via Bacon
timmaaa said:
So you wiped the whole phone? Even the internal storage? If so, and the problem persists, it's suggesting a hardware problem. You could try a custom kernel though just in case, it wouldn't hurt.
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry for the inconvenience but could you suggest a couple? (for cm12 nightlies if possible)
Thanks
And there should be no other software things I could change right?
I was reading before about oneplus not using double sided tape on their digitizers and using glue instead and as such sometimes touch responsiveness in some places might of been removed in some of the earlier models. Although oneplus said that was just a software glitch but iderrrnooooo.
Thanks for the help man c:
Sanjitha.d said:
Sorry for the inconvenience but could you suggest a couple? (for cm12 nightlies if possible)
Thanks
And there should be no other software things I could change right?
I was reading before about oneplus not using double sided tape on their digitizers and using glue instead and as such sometimes touch responsiveness in some places might of been removed in some of the earlier models. Although oneplus said that was just a software glitch but iderrrnooooo.
Thanks for the help man c:
Click to expand...
Click to collapse
Can't really suggest one because I don't use them, but you'll find them all listed in my index thread here:
http://forum.xda-developers.com/showthread.php?t=2843675
I can't think of anything else on the software/firmware side of things, everything has been wiped and reflashed.
Transmitted via Bacon
I have a similar issue. The softkeys stopped working right after i unlocked the bootloader. They light up but do not respond. can anything be done? I unlocked the bootloader via adb.
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