Hi guys, I have a OnePlus 3T which I have been using since 2017 and it worked perfectly. But a few months ago it updated to Android 9 Pie and ever since then my phone has gotten far slower, keeps hanging on certain things and sometimes I can't even make a call directly from contacts. I have to click call then it seems like the call is starting up but then just freezes and cuts off. Afterward, I have to go to call history and make the call again and it works.
I waited a while to see if a newer update will fix this slowdown and issues but after 2 or 3 more Pie updates it's still unresponsive and crashes the dialer. So I just want to know if anyone can tell me where I can find a ROM for final Oreo version that is compatible with OnePlus 3T and the best way I can downgrade.
I tried following a guide already but I ran into issues simply flashing TWRP. I Installed the ABD drivers, unlocked bootloader and rebooted.
Then in fastboot mode, I tried to flash it and it seemed to work because in the ABD PowerShell windows it said "Okay" after I used the cmd to flash.
But when I reboot and go into recovery, I still have the default recovery options.
This is the first time I am trying to flash my phone and I'm only doing it because it went from a phone that ran super smooth to one that is barely usable...I mean Contacts and the actual Phone apps are hanging and crashing. It even crashes when I try to answer incoming calls sometimes. The phone keeps ringing and I get a message saying the program is unresponsive, giving me options to "wait" or "close"
TT-Twister said:
...
I tried following a guide already but I ran into issues simply flashing TWRP. I Installed the ABD drivers, unlocked bootloader and rebooted.
Then in fastboot mode, I tried to flash it and it seemed to work because in the ABD PowerShell windows it said "Okay" after I used the cmd to flash.
But when I reboot and go into recovery, I still have the default recovery options.
...
Click to expand...
Click to collapse
Something you need to know: stock OOS will always reinstall the stock recovery when the phone boots into system.
So if you
1. Booted into fastboot
2. Flashed TWRP
3. Booted your phone
4. Booted into recovery
then TWRP got overwritten in step 3.
What you should have done after flashing TWRP was boot into recovery directly (use the volume keys while in fastboot mode to select that option then press the power button).
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Something you need to know: stock OOS will always reinstall the stock recovery when the phone boots into system.
So if you
1. Booted into fastboot
2. Flashed TWRP
3. Booted your phone
4. Booted into recovery
then TWRP got overwritten in step 3.
What you should have done after flashing TWRP was boot into recovery directly (use the volume keys while in fastboot mode to select that option then press the power button).
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply...and it got me a step further. But when it got to TWRP it starts at "Mount Decrypt Data" I assumed this was my phone pin...and when I tried that it opens up a cmd window which said "unable to mount storage" then says "updating partition details" but it sort of freezes then the phone turns off and powers on with the notification LED being "white" but the screen is black and the phone just stays like this for ages. Only thing I could do is hold down the power button to power down the phone and restart it. At least TWRP seems to have flashed because even when I go into recovery from the boot menu it goes to TWRP.
TT-Twister said:
Thanks for the reply...and it got me a step further. But when it got to TWRP it starts at "Mount Decrypt Data" I assumed this was my phone pin...and when I tried that it opens up a cmd window which said "unable to mount storage" then says "updating partition details" but it sort of freezes then the phone turns off and powers on with the notification LED being "white" but the screen is black and the phone just stays like this for ages. Only thing I could do is hold down the power button to power down the phone and restart it. At least TWRP seems to have flashed because even when I go into recovery from the boot menu it goes to TWRP.
Click to expand...
Click to collapse
Personally I would not downgrade to Oreo. Pie works fine. The problems your were having could have probably been solved by simply doing a factory reset.
Since you've unlocked your bootloader, you've effectively done a factory reset. So try just booting the system and set up your phone again. It'll probably be fine now that you're doing a clean install.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Personally I would not downgrade to Oreo. Pie works fine. The problems your were having could have probably been solved by simply doing a factory reset.
Since you've unlocked your bootloader, you've effectively done a factory reset. So try just booting the system and set up your phone again. It'll probably be fine now that you're doing a clean install.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Yea...I have done several factory resets in the process of unlocking the bootloader and flashing twrp. So it didn't fix the issue. The main issue is linked to "contacts" which basically freezes most times I try to make a call. It makes the call but crashes contacts and the "Phone" app. Which is stupid because that's the main purpose of a phone.
Also, another key reason for wanting to downgrade to Oreo is the ability to record phone calls. This is very useful to me and those apps stopped working with Pie I think.
TT-Twister said:
Yea...I have done several factory resets in the process of unlocking the bootloader and flashing twrp. So it didn't fix the issue. The main issue is linked to "contacts" which basically freezes most times I try to make a call. It makes the call but crashes contacts and the "Phone" app. Which is stupid because that's the main purpose of a phone.
Also, another key reason for wanting to downgrade to Oreo is the ability to record phone calls. This is very useful to me and those apps stopped working with Pie I think.
Click to expand...
Click to collapse
If I was to go back to Oreo I would:
Download the full Oreo OOS ROM and backup everything you need onto your PC. Then in TWRP:
1. Do a factory reset
2. Flash OOS 5.0.4
3. Wipe>format data (to get rid of encryption)
4. Reboot system, which will also encrypt the data again and replace TWRP with the stock recovery
5. Use ADB to restore the data on your phone
6. Flash TWRP and restore your Oero backup.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
If I was to go back to Oreo I would:
Download the full Oreo OOS ROM and backup everything you need onto your PC. Then in TWRP:
1. Do a factory reset
2. Flash OOS 5.0.4
3. Wipe>format data (to get rid of encryption)
4. Reboot system, which will also encrypt the data again and replace TWRP with the stock recovery
5. Use ADB to restore the data on your phone
6. Flash TWRP and restore your Oero backup.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Did you read what I said? I did what you said and manage to boot into TWRP but I told you the issue about encryption and my phone freezing.
So I don't know how I'm supposed to flash any OS if I can't get TWRP to work in the first place.
TT-Twister said:
Did you read what I said? I did what you said and manage to boot into TWRP but I told you the issue about encryption and my phone freezing.
So I don't know how I'm supposed to flash any OS if I can't get TWRP to work in the first place.
Click to expand...
Click to collapse
In that case, I hope you've got backups on your PC because you're going to have to format your phone. TWRP>Wipe>Format data. You'll need to cancel out of the password screen to do the wipe.
Then reboot into recovery and use ADB to copy the files to your phone and flash Oreo.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
In that case, I hope you've got backups on your PC because you're going to have to format your phone. TWRP>Wipe>Format data. You'll need to cancel out of the password screen to do the wipe.
Then reboot into recovery and use ADB to copy the files to your phone and flash Oreo.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I got my data backed up using some software called "dr.fone" but how do I use ADB to copy files to the phone?
As I said at the start, this is literally the first time I'm trying to do this. I never flashed my phone before and never used ADB or TWRP before.
I'm literally just following instructions in guides and forums. So please don't assume I know how all of this works.
Hmm. I've been thinking about your problem and I have some questions/suggestions.
1. What version of TWRP are you using? (I would use the latest one from https://dl.twrp.me/oneplus3/ )
2. Can you boot your phone normally? If so, try setting a new password and say Yes for secure start up. Then verify that when you reboot you are prompted for a password (Starting Android screen, not just the lock screen). If that works, boot into TWRP. Does the new password work?
BillGoss said:
Hmm. I've been thinking about your problem and I have some questions/suggestions.
1. What version of TWRP are you using? (I would use the latest one from https://dl.twrp.me/oneplus3/ )
2. Can you boot your phone normally? If so, try setting a new password and say Yes for secure start up. Then verify that when you reboot you are prompted for a password (Starting Android screen, not just the lock screen). If that works, boot into TWRP. Does the new password work?
Click to expand...
Click to collapse
I'm using the latest version of TWRP (top one on that list)
I can boot the phone, and it works obviously. But I was having serious issues and slowdowns after updating to Pie.
Changing the password didn't work...but doing what you said before and formatting the device and rebooting into TWRP seems to have worked.
It's recognizing the storage and I can choose zip files to install.
Do you know the last version of Oreo that was compatible with the 3T? I think it's either 5.0.8 but they may have released 5.1.8 for it...I can't remember and can't seem to find the info anywhere.
TT-Twister said:
I'm using the latest version of TWRP (top one on that list)
I can boot the phone, and it works obviously. But I was having serious issues and slowdowns after updating to Pie.
Changing the password didn't work...but doing what you said before and formatting the device and rebooting into TWRP seems to have worked.
It's recognizing the storage and I can choose zip files to install.
Do you know the last version of Oreo that was compatible with the 3T? I think it's either 5.0.8 but they may have released 5.1.8 for it...I can't remember and can't seem to find the info anywhere.
Click to expand...
Click to collapse
Glad you can now get into TWRP.
5.0.8 was the last stable Oreo version (I never used betas).
Sent from my OnePlus 3T using XDA Labs
I would second the suggestion that you don't downgrade to Oreo. I was having the same issues you mentioned on Pie, but have since sorted them out. Pie is now running very nicely for me.
A good deep cleaning did it for me, even after a previous factory reset had failed to fix it.
ataft said:
I would second the suggestion that you don't downgrade to Oreo. I was having the same issues you mentioned on Pie, but have since sorted them out. Pie is now running very nicely for me.
A good deep cleaning did it for me, even after a previous factory reset had failed to fix it.
Click to expand...
Click to collapse
Well, it seems like downgrading to Oreo is going to be a huge task. Because my research I need to flash some stock firmware before being able to flash Oreo again.
Which I tried, but for some reason, it's not flashing it. So now I need to download the latest stable version of Pie for 3T again?
Can any of you tell me what version that is?
TT-Twister said:
Well, it seems like downgrading to Oreo is going to be a huge task. Because my research I need to flash some stock firmware before being able to flash Oreo again.
Which I tried, but for some reason, it's not flashing it. So now I need to download the latest stable version of Pie for 3T again?
Can any of you tell me what version that is?
Click to expand...
Click to collapse
What is the latest stable of Pie? 9.0.5
But Bill has already given you the steps for downgrading if you want.
TT-Twister said:
Well, it seems like downgrading to Oreo is going to be a huge task. Because my research I need to flash some stock firmware before being able to flash Oreo again.
Which I tried, but for some reason, it's not flashing it. So now I need to download the latest stable version of Pie for 3T again?
Can any of you tell me what version that is?
Click to expand...
Click to collapse
I decided to test downgrading to Oreo from Pie. And I learnt that it's basically the same process as upgrading from Oreo to Pie. Since my phone is unlocked and encrypted I had to remove the encryption using TWRP>Wipe>Format data: yes when going from Oreo to Pie and the same when going from Pie to Oreo.
So my process to downgrade is:
- Backup everything I want to keep from my phone.
- Flash OOS 5.0.8 full stock zip in TWRP. This completely overwrites the 9.0.5 firmware and system.
- Remove encryption: TWRP>Wipe>Format data: yes. (You'll lose everything on your phone)
- Reboot system (it re-encrypts the phone and replaces TWRP with stock recovery).
- Restored phone data, and so on.
Sent from my OnePlus 3T using XDA Labs
One more thing that I'd forgotten about: you can run OOS Oreo on the Pie firmware. So if you still have the Pie firmware installed, just restore an Oreo backup and you should be ok.
See point at the end of https://forum.xda-developers.com/on...ageos-16-0-oneplus-3-3t-t3866517/post79378447
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
I decided to test downgrading to Oreo from Pie. And I learnt that it's basically the same process as upgrading from Oreo to Pie. Since my phone is unlocked and encrypted I had to remove the encryption using TWRP>Wipe>Format data: yes when going from Oreo to Pie and the same when going from Pie to Oreo.
So my process to downgrade is:
- Backup everything I want to keep from my phone.
- Flash OOS 5.0.8 full stock zip in TWRP. This completely overwrites the 9.0.5 firmware and system.
- Remove encryption: TWRP>Wipe>Format data: yes. (You'll lose everything on your phone)
- Reboot system (it re-encrypts the phone and replaces TWRP with stock recovery).
- Restored phone data, and so on.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Do you have a link for the OOS 5.0.8 full stock zip with the firmware?
I downloaded files from these links:
https://www.getdroidtips.com/oxygenos-5-0-8-oneplus-3-3t/
https://www.androidjungles.com/oneplus-3t-flash-file/
But neither of them are flashing in TWRP.
TT-Twister said:
Do you have a link for the OOS 5.0.8 full stock zip with the firmware?
I downloaded it from here https://www.getdroidtips.com/oxygenos-5-0-8-oneplus-3-3t/ but it's not flashing in TWRP.
Click to expand...
Click to collapse
https://otafsg1.h2os.com/patch/amaz...n_28_OTA_070_all_1812060053_d75f3be1db2be.zip
Sent from my OnePlus 3T using XDA Labs
ataft said:
I would second the suggestion that you don't downgrade to Oreo. I was having the same issues you mentioned on Pie, but have since sorted them out. Pie is now running very nicely for me.
A good deep cleaning did it for me, even after a previous factory reset had failed to fix it.
Click to expand...
Click to collapse
What do you mean by deep cleaning?. I tried hard reset but after using apps phone again became dead slow.
Related
Hi,
Android 7.0 is coming (rumors said this Christmas) :
link
link2
Update is alive: http://community.umidigi.com/thread-5751-1-1.html
But got many problems saving files son internal SD and the bartery is draining fast. LTE is working good.
nougat on umi plus
mafury said:
Update is alive: http://community.umidigi.com/thread-5751-1-1.html
But got many problems saving files son internal SD and the bartery is draining fast. LTE is working good.
Click to expand...
Click to collapse
my experience is very good .ive rooted the phone and flashed also adblock gps is working good internet very fast lte for the price just amazing
After Update Bootloop
After the 7.0 Update, i have an issue. If my Umi Plus is connected to my WLAN AP (with other devices no such error), it is rebooting every 10 seconds. If i turn my Access Point off, it stops rebooting itself and if i turn it on again, it is restarting after 5 seconds over and over again. My mobile carrier internet works fine, without any such errors.
I dont want to use my mobile carrier with limit, but my home wlan.
Anyone has similiar issues? If anyone knows the solution please write it
Preisschild said:
After the 7.0 Update, i have an issue. If my Umi Plus is connected to my WLAN AP (with other devices no such error), it is rebooting every 10 seconds. If i turn my Access Point off, it stops rebooting itself and if i turn it on again, it is restarting after 5 seconds over and over again. My mobile carrier internet works fine, without any such errors.
I dont want to use my mobile carrier with limit, but my home wlan.
Anyone has similiar issues? If anyone knows the solution please write it
Click to expand...
Click to collapse
Use flashtool to reflash firmware.
New UMI Super Android 7.0 beta update
New UMI Super Android 7.0 beta V7.01_20170114 update
Flashing through SP Flash Tool.
Camera, flash LED and on-screen buttons fixed!
The list of known bugs:
The camera still needs some adjustments
No standby Harlequin LED (only basic notification LED settings)
Other minor bugs
ROM link(UMi_SUPER_Android_N_beta_20170114_c239v55_kw_u1.rar):
mediafire.com/file/hpzw37aca481bvc/UMi_SUPER_Android_N_beta_20170114_c239v55_kw_u1.rar
SPFT link (SP_Flash_Tool_v5.1648.rar):
mediafire.com/file/2g6qau85a7fvnjq/SP_Flash_Tool_v5.1648.rar
Original post:
community.umidigi.com/thread-6169-1-1.html
Aditional IMPORTANT update info:
community.umidigi.com/thread-5265-1-1.html
Sorry, I can't attach links
This version should be stable with the mentioned minor bugs but please, post your feedback to check the correct performance, if there is any issue found, let us know!
Dora te quierooooooooo
So far so good. Android 7 has made a big improvement to my Super.
Does anyone know if root is possible with this beta and / or whether there's a version of TWRP that will work with it?
Thanks,
Steve
steveharman said:
So far so good. Android 7 has made a big improvement to my Super.
Does anyone know if root is possible with this beta and / or whether there's a version of TWRP that will work with it?
Thanks,
Steve
Click to expand...
Click to collapse
Root is possible using TWRP 3.0.2 for umi.
I've attached a zip file of the TWRP version below, unzip it and flash using SPT flashtool, you need to untick all the other boxes and just tick the recovery and direct it to where you unpacked the zip file.
I've also attached the Super su i used to root the beta 2 for the umi super. Flash it in TWRP.
Brilliant, thanks for that @Creedo4Life.
Can you remind my poof befuddled brain please - does flashing TWRP / recovery wipe the device? I should know this but can't remember.
Thanks again.
Steve
steveharman said:
Brilliant, thanks for that @Creedo4Life.
Can you remind my poof befuddled brain please - does flashing TWRP / recovery wipe the device? I should know this but can't remember.
Thanks again.
Steve
Click to expand...
Click to collapse
No worries. There's no need to wipe anything after you flashed Supersu in TWRP. One of the best things about Nougat 7 is that it use a different file system then Lollipop and Marshmallow, so you will never again sit and wait while the OS optimize apps (sometimes hundreds if you had a lot of apps installed!!) Just reboot after flash and you good to go. The first boot might bootloop once or twice, no need to do anything it will di everything on its own. Enjoy full root mate.
Creedo4Life said:
No worries. There's no need to wipe anything after you flashed Supersu in TWRP. One of the best things about Nougat 7 is that it use a different file system then Lollipop and Marshmallow, so you will never again sit and wait while the OS optimize apps (sometimes hundreds if you had a lot of apps installed!!) Just reboot after flash and you good to go. The first boot might bootloop once or twice, no need to do anything it will di everything on its own. Enjoy full root mate.
Click to expand...
Click to collapse
Quick question - I've only flashed recoveries using adb before, how do I point SPFlashTool at the recovery .img file?
Do I replace the recovery.img file inside the UMI ROM folder, with the TWRP .img file?
And then tick 'Recovery' inside SPFlashTool per your instructions?
Thanks,
Steve
steveharman said:
Quick question - I've only flashed recoveries using adb before, how do I point SPFlashTool at the recovery .img file?
Do I replace the recovery.img file inside the UMI ROM folder, with the TWRP .img file?
And then tick 'Recovery' inside SPFlashTool per your instructions?
Thanks,
Steve
Click to expand...
Click to collapse
That's correct, you browse the img file on the ticket recovery (the only one that should be ticked.) click on "download only" while your phone is switched off and then connect it through the usb. It will then flash TWRP and let you know when its done. Now disconnect your phone and hold in power button and volume up simultaneously. When you see the umi logo let go of the power button but keep holding volume up. When you see the TWRP logo you can let go. The first time you boot into TWRP you need to swipe the bar which will allow modifications, you will only have to do that once, the system will then remember it. Good luck and happy rooting.
Thanks.
Hmm, this is odd though. I managed to get TWRP flashed but whenever I flash that SuperSU and reboot, all my apps complain and keep quitting when I try to launch them. I've been careful to wipe cache after flashing, as usual.
In fact I've rried wiping everything cache, dalvik, - even started again from an entirely factory-wiped device, including data.
Flashed a fresh copy of the Nougat beta ROM, booted up fine. Flashed TWRP, booted up fine but then I reboot to recovery, flash SuperSU and bingo - on my next reboot all the apps starts complainin that they have stopped - even Launcher.
Weird...
Steve
steveharman said:
Thanks.
Hmm, this is odd though. I managed to get TWRP flashed but whenever I flash that SuperSU and reboot, all my apps complain and keep quitting when I try to launch them. I've been careful to wipe cache after flashing, as usual.
In fact I've rried wiping everything cache, dalvik, - even started again from an entirely factory-wiped device, including data.
Flashed a fresh copy of the Nougat beta ROM, booted up fine. Flashed TWRP, booted up fine but then I reboot to recovery, flash SuperSU and bingo - on my next reboot all the apps starts complainin that they have stopped - even Launcher.
Weird...
Steve
Click to expand...
Click to collapse
That's very odd. I used the exact same supersu myself and never encountered that problem. That version is also compatible with Nougat. Try one of the other versions on https://www.chainfire.eu/
Maybe that solves your problem.
Creedo4Life said:
Root is possible using TWRP 3.0.2 for umi.
I've attached a zip file of the TWRP version below, unzip it and flash using SPT flashtool, you need to untick all the other boxes and just tick the recovery and direct it to where you unpacked the zip file.
I've also attached the Super su i used to root the beta 2 for the umi super. Flash it in TWRP.
Click to expand...
Click to collapse
I follow this procedure but I only obtain partial root. I cannot cut and paste in the system partition even though I can run some apks that require root. Is there a way I can obtain full root?
[email protected] said:
I follow this procedure but I only obtain partial root. I cannot cut and paste in the system partition even though I can run some apks that require root. Is there a way I can obtain full root?
Click to expand...
Click to collapse
You have full root, you just don't know it.
If you want to edit anything in any system folders you need to change r, rw permissions. I use file explorer for this. Look at the attached SS to understand what I mean.
TWRP Install
Hi,
I'm on 3.02-20161121 version and my phone is rooted: may I flash Nougat via TWRP, instead of using SP Flashtool?
Thanks
pollock49 said:
Hi,
I'm on 3.02-20161121 version and my phone is rooted: may I flash Nougat via TWRP, instead of using SP Flashtool?
Thanks
Click to expand...
Click to collapse
No, you need to flash beta 2 using SPFT, there is no zip file to use with TWRP for this.
http://community.umidigi.com/thread-6169-1-1.html
steveharman said:
Thanks.
Hmm, this is odd though. I managed to get TWRP flashed but whenever I flash that SuperSU and reboot, all my apps complain and keep quitting when I try to launch them. I've been careful to wipe cache after flashing, as usual.
In fact I've rried wiping everything cache, dalvik, - even started again from an entirely factory-wiped device, including data.
Flashed a fresh copy of the Nougat beta ROM, booted up fine. Flashed TWRP, booted up fine but then I reboot to recovery, flash SuperSU and bingo - on my next reboot all the apps starts complainin that they have stopped - even Launcher.
Weird...
Steve
Click to expand...
Click to collapse
I have a similar problems. However in my case many of the apk still working include play store. Just the apks that needs internet quit working.
Creedo4Life said:
Root is possible using TWRP 3.0.2 for umi.
I've attached a zip file of the TWRP version below, unzip it and flash using SPT flashtool, you need to untick all the other boxes and just tick the recovery and direct it to where you unpacked the zip file.
I've also attached the Super su i used to root the beta 2 for the umi super. Flash it in TWRP.
Click to expand...
Click to collapse
Hello,
I have the problem that SPFT shows me 100% wehn I am flashing TWRP to the UMI Super but still hangs at 100% and does nothing more.
I'm using the Android N V7.01_20170123.
I also tried an Android scatter from Android 6 before I flashed Android 7, but it also doenst work.
Here's the whole story:
I was on an unofficial build of RR CM13, encrypted, using TWRP 3.0.2-1.
I wiped data, dalvik, cache, and flashed the newest Official RR 7.1.1 and open-gapps.
I boot into the new ROM and start setting stuff up.
I restore some apps' data using Titanium Backup, then reboot.
On reboot I'm greeted with the device setup screen
I reboot, wipe, reflash a bunch of times
A few times:
When I rebooted after using the system my PIN doesn't decrypt the system/data (booting into the system)
When I rebooted after using TWRP my PIN does decrypt (booting into the system)
At some point during this I try wiping everything from TWRP, but it freezes, goes black, and then the notification LED turns white. I hold the power button and boot back to TWRP.
Apparently wiping /data is the problem (everything else wipes just fine if I do them individually)
I boot back into the system, set it up, and do a full factory reset from there (after offloading my stuff from Internal Storage)
Back to TWRP, now no matter what I flash or restore, I don't end up booting into the system, only into TWRP
I've also tried TWRP 3.0.4-0 (which wouldn't decrypt my data), and I've reflash TWRP a few times.
How do I actually boot into my system? It's been 7 hours, and I'm losing my mind.
Deleted
Boot to your ROM through the power button...
Manually..
Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Do what he said. You've already wiped your internal storage, so just start from scratch.
Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
RustySpackleford said:
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
Click to expand...
Click to collapse
flash twrp
adb push os zip
adb push su
flash all , if needed format data.
This is what I have done yesterday,
edit: If u brick I don't take any responsibility.
Deleted
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
uttam.ace said:
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
Click to expand...
Click to collapse
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
bluuquthug said:
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
Click to expand...
Click to collapse
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
uttam.ace said:
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
bluuquthug said:
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
Click to expand...
Click to collapse
Your TWRP is working right!
go to TWRP/ Advanced/ADB Sideload
type "adb sideload /path/to/rom.zip"
Mate, recommend using ADB Sideload on TWRP itself is the only viable option you have. OR if that doesn't work and you still have the PIN issues, you should definitely use the Unbrick Tool and get everything back to Stock, and then reflash everything
Note: Using the unbrick tool will cause it to relock bootloader, so you're gonna have to start over again.
Cheers!
Hello, I've softbricked a fair amount of phones and tablets in my time but I must admit never had this show up. After flashing Twrp and a dm-verity thingy, I received this shiny new error on my new 1+3t. While I'm assuming it's a straightforward fix such as:
Booting into Twrp and flashing stock 4.x Oxygen os and the stock recovery to bring phone back to where I started.
My question is, can't I just go straight about flashing a rom? I.e freedom rom, or is it advisable to just try start again?
And is me flashing stock os then recovery got to work?
Everything is still stock there is no root. All I have done is:
Code:
fastboot > oemunlock > reboot > fastboot flash Twrp > Twrp boot > Twrp > swiped to Modify > flashed dm-verity.
I did receive a password request first time round but after I rebooted phone it wasn't there again.
Thank you for helping in advance.
Archtects said:
Hello, I've softbricked a fair amount of phones and tablets in my time but I must admit never had this show up. After flashing Twrp and a dm-verity thingy, I received this shiny new error on my new 1+3t. While I'm assuming it's a straightforward fix such as:
Booting into Twrp and flashing stock 4.x Oxygen os and the stock recovery to bring phone back to where I started.
My question is, can't I just go straight about flashing a rom? I.e freedom rom, or is it advisable to just try start again?
And is me flashing stock os then recovery got to work?
Everything is still stock there is no root. All I have done is:
Code:
fastboot > oemunlock > reboot > fastboot flash Twrp > Twrp boot > Twrp > swiped to Modify > flashed dm-verity.
I did receive a password request first time round but after I rebooted phone it wasn't there again.
Thank you for helping in advance.
Click to expand...
Click to collapse
You had to flash supersu or Magisk after the process to disable force encryption also make sure your are on the nougat supported twrp 3.0.4-1 or later
You can flash any rom if you have an unlocked bootloader and a working twrp
Sent from my Funk Tuned 3T
Funk Wizard said:
You had to flash supersu or Magisk after the process to disable force encryption also make sure your are on the nougat supported twrp 3.0.4-1 or later
You can flash any rom if you have an unlocked bootloader and a working twrp
Click to expand...
Click to collapse
thanks I think that's where I went wrong. I should have flashed Magisk. The guide says so but I only intended to flash a rom. Eh. I'll see if I can flash Magisk. All is not lost. I'll update once I get home. I'm annoyed with my self lol.
-101 xda points
Archtects said:
thanks I think that's where I went wrong. I should have flashed Magisk. The guide says so but I only intended to flash a rom. Eh. I'll see if I can flash Magisk. All is not lost. I'll update once I get home. I'm annoyed with my self lol.
-101 xda points
Click to expand...
Click to collapse
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Sent from my OnePlus 3T using XDA Labs
Funk Wizard said:
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Click to expand...
Click to collapse
I will do, hopefully it be fine. I'll try different thing if stuff doesn't work and I'll post back what I did incase anyone else has similar problem .
Twrp doesn't see any internal storage what so ever. So Ive flashed stock recovery from fastboot and going to attempt to sideload the stock OS. fingers-crossed
Funk Wizard said:
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Click to expand...
Click to collapse
Thanks for your help im back to a working phone!
For anyone who get stuck!
1) download op3t stock recovery and the oxygen OS from oneplus website
2) boot into fastboot.
3) with your pc get up Adb and:
Code:
fastboot flash recovery stock.img
Fastboot boot stock.img
[\CODE]
4) Once you boot into recovery navigate to install from adb.
5) in cmd again on pc type
[CODE] adb sideload filename.zip
[\CODE]
6) then reboot :). You can leave it here if you want.
So I'm back on stock. With Magisk installed. Only dm-verity still come up which I'm not keen on. But I guess I can live with it. But I'm stuck with a bunch of system apps I can't get rid of? I've tried titanium backup, and link2sd my go to but nothing any ideas? Anyone now how to get rid?
Archtects said:
So I'm back on stock. With Magisk installed. Only dm-verity still come up which I'm not keen on. But I guess I can live with it. But I'm stuck with a bunch of system apps I can't get rid of? I've tried titanium backup, and link2sd my go to but nothing any ideas? Anyone now how to get rid?
Click to expand...
Click to collapse
I can recommend OOS Aroma Debloater Credits: @siankatabg :good:
Funk Wizard said:
I can recommend OOS Aroma Debloater Credits: @siankatabg :good:
Click to expand...
Click to collapse
Cheers I found the zip you. Mentioned after I posted the question, worked sort of lol. Some still won't go but it's got rid of a fair chunk an dive just frozen any I don't want.
Hello,
I have Oneplus 3 A3000 running on OOS 4.0.1 (Android 7.0). I also have official OP3 twrp recovery version 3.0.3-0 installed and root was done using supersu free v2.82.. It also has dm verity prompt which comes up during boot time because it is oem unlocked.
I want to know exact procedure to go to complete stock rom + stock recovery along with links to download stock recovery and rom. I saw different versions of stock recovery for different OOS. I don't care about device data as everything is on cloud and nothing on is on device. App list also I can get from google account history. Only thing I care is not to corrupt any system partitions. I also saw few posts that go into boot loop if incorrectly unrooted. I would not want that either.
Your help is greatly appreciated. Virtual beer for you ???. I am software engineer so even though I am noob in terms of hacking my android, I can follow the instructions properly.
Thanks again.
You can flash official OOS Rom and just use TWRP, you can try using the current recovery you have. Allow it to boot after if it allows you then do not go back to TWRP, allow it to boot to its system and then normally it will just override TWRP with OOS stock recovery.
reyscott said:
You can flash official OOS Rom and just use TWRP, you can try using the current recovery you have. Allow it to boot after if it allows you then do not go back to TWRP, allow it to boot to its system and then normally it will just override TWRP with OOS stock recovery.
Click to expand...
Click to collapse
What about unroot and oem lock and dm verity? do I need to do all that before doing OOS update? I am getting OOS 4.1.6 in system update.
mit2nil said:
What about unroot and oem lock and dm verity? do I need to do all that before doing OOS update? I am getting OOS 4.1.6 in system update.
Click to expand...
Click to collapse
you sure you want to be locked again ? i doubt..
dm verity is not a big deal for me.. i allowed it.. im ok with but if you want to remove it siankatbg has a guide on how to remove it..
reyscott said:
you sure you want to be locked again ? i doubt..
dm verity is not a big deal for me.. i allowed it.. im ok with but if you want to remove it siankatbg has a guide on how to remove it..
Click to expand...
Click to collapse
I actually want to go to systemless su + magisk + xposed later on. This one didn't work well with some apps that can detect root. But before I do that I want to start fresh because things tend to go messy and i do not have a backup device right now
mit2nil said:
I actually want to go to systemless su + magisk + xposed later on. This one didn't work well with some apps that can detect root. But before I do that I want to start fresh because things tend to go messy and i do not have a backup device right now
Click to expand...
Click to collapse
flash stock oos thats it.. you may leave the bootloader unlocked. better that way..
Sorry but I am still not sure about exact process. Here are my noob queries:
1. Should I update twrp to latest version before proceding? If so which one? currently it is 3.0.3-0. I remember running into encryption issue due to unsupported twrp when I did this last time.
2. Should I use wipe option to wipe anything before I update OOS? I want to do clean install. If so, what should I be wiping out of dalvik/system/data/internal storage/cache/usb otg?
3. To update, I should copy full ota zip on internal memory -> go to recovery -> install -> select zip file -> swipe to flash. Is that correct?
4. After that if I boot into recovery -> I will keep twrp and if I let it boot, it will replace twrp with stock recovery right?
5. Let say, I let it boot n install stock recovery, will I have dm-verity during next boot?
6. Will my superSU root be gone or still be there? If it is still there should I do complete unroot before starting this process?
7. If it is not gone, is it ok to do complete unroot after stock oos + recovery is installed?
8. I saw a dm-verity patch zip which can be used to patch dm-verity in bootloader mode if I do "fastboot oem disable_dm_verity and fastboot oem enable_dm_verity". Does it suppress the issue or it resolves it gracefully?
Thanks for the patience and help in answering the queries advance.
mit2nil said:
Sorry but I am still not sure about exact process. Here are my noob queries:
1. Should I update twrp to latest version before proceding? If so which one? currently it is 3.0.3-0. I remember running into encryption issue due to unsupported twrp when I did this last time.
2. Should I use wipe option to wipe anything before I update OOS? I want to do clean install. If so, what should I be wiping out of dalvik/system/data/internal storage/cache/usb otg?
3. To update, I should copy full ota zip on internal memory -> go to recovery -> install -> select zip file -> swipe to flash. Is that correct?
4. After that if I boot into recovery -> I will keep twrp and if I let it boot, it will replace twrp with stock recovery right?
5. Let say, I let it boot n install stock recovery, will I have dm-verity during next boot?
6. Will my superSU root be gone or still be there? If it is still there should I do complete unroot before starting this process?
7. If it is not gone, is it ok to do complete unroot after stock oos + recovery is installed?
8. I saw a dm-verity patch zip which can be used to patch dm-verity in bootloader mode if I do "fastboot oem disable_dm_verity and fastboot oem enable_dm_verity". Does it suppress the issue or it resolves it gracefully?
Thanks for the patience and help in answering the queries advance.
Click to expand...
Click to collapse
1. Try the first the current TWRP that you have. If it work, then just reboot it on to the system and TWRP will be overwritten by Stock OOS recovery.
2. Wipe dalvik/system/data/cache ..
3. YES , if im not mistaken.
4. answered on question 1.
5. most probably. Try flashing a certain firmware (not sure which one would work) . This is what I did before. But cant be sure.
6. It will be gone.
7. gone.
8. You can try.
reyscott said:
1. Try the first the current TWRP that you have. If it work, then just reboot it on to the system and TWRP will be overwritten by Stock OOS recovery.
2. Wipe dalvik/system/data/cache ..
3. YES , if im not mistaken.
4. answered on question 1.
5. most probably. Try flashing a certain firmware (not sure which one would work) . This is what I did before. But cant be sure.
6. It will be gone.
7. gone.
8. You can try.
Click to expand...
Click to collapse
Thank you so much.
mit2nil said:
Thank you so much.
Click to expand...
Click to collapse
I will tell you what I do.
Flash the latest official TWRP which is 3.1.1-2
If you want a totally clean install, boot into recovery and wipe system data including internal storage, dalvik and cache.
Then without rebooting, push the ROM downloaded from the OnePlus site to the phone. Select the ROM in recovery and swipe to flash.
Otherwise you can copy the ROM to the phone, boot into recovery, wipe system, data, dalvik and cache and then in recovery, flash the ROM.
Wipe dalvik and cache and reboot into system.
Your root will be gone and along with it TWRP. You will be on stock ROM with stock recovery.
Leave the bootloader unlocked. If necessary, it can be locked at any time.
Most likely you will not get the dm verity error. If you do, simply flash the zip given in post #215 in siankatabg's thread on dm verity. It will merely remove the message as all such methods do.
Enjoy
tnsmani said:
I will tell you what I do.
Flash the latest official TWRP which is 3.1.1-2
If you want a totally clean install, boot into recovery and wipe system data including internal storage, dalvik and cache.
Then without rebooting, push the ROM downloaded from the OnePlus site to the phone. Select the ROM in recovery and swipe to flash.
Otherwise you can copy the ROM to the phone, boot into recovery, wipe system, data, dalvik and cache and then in recovery, flash the ROM.
Wipe dalvik and cache and reboot into system.
Your root will be gone and along with it TWRP. You will be on stock ROM with stock recovery.
Leave the bootloader unlocked. If necessary, it can be locked at any time.
Most likely you will not get the dm verity error. If you do, simply flash the zip given in post #215 in siankatabg's thread on dm verity. It will merely remove the message as all such methods do.
Enjoy
Click to expand...
Click to collapse
Hi sorry I was afk for couple of weeks. So I started following this procedure. Very strangely, after I did a reboot post stock OOS (1.4gb zip) flash, twrp said no os installed, you are sure you want to reboot? I wasn't sure so I just said yes. Then I also so dm-verity coming back which was not the case when I started as I had disabled it using "fastboot enable_dm_verity" command.
Now, its been more than five minutes and my phone is stuck on the boot animation forever. (red dot in middle and two while dots rotating).
I am not sure what happened. Can someone please help me ?
mit2nil said:
Hi sorry I was afk for couple of weeks. So I started following this procedure. Very strangely, after I did a reboot post stock OOS (1.4gb zip) flash, twrp said no os installed, you are sure you want to reboot? I wasn't sure so I just said yes. Then I also so dm-verity coming back which was not the case when I started as I had disabled it using "fastboot enable_dm_verity" command.
Now, its been more than five minutes and my phone is stuck on the boot animation forever. (red dot in middle and two while dots rotating).
I am not sure what happened. Can someone please help me ?
Click to expand...
Click to collapse
Never mind. It booted to setup screen after few minutes. I guess I was in too much hurry.
i just went to stock yesterday, i flash stock recovery followed by sideloading the Oxygen OS and after that relock the bootloader.. i kinda feel the battery is much better now compare to when it was rooted with OOS
danxtian said:
i just went to stock yesterday, i flash stock recovery followed by sideloading the Oxygen OS and after that relock the bootloader.. i kinda feel the battery is much better now compare to when it was rooted with OOS
Click to expand...
Click to collapse
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
mit2nil said:
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
Click to expand...
Click to collapse
There is a zip floating around XDA which I am not able to locate immediately. It may be on siankatabg's thread on dm verity. Simply flash it.
There is also another method I read about where you flash the 4.0.2 firmware, use the enable verity command on adb, boot the phone and then flash the current firmware.
Both methods are mentioned here in XDA. Search for it.
EDIT: One of them here: https://forum.xda-developers.com/showpost.php?p=72273041&postcount=215
See also the OP of the same thread for the other method.
mit2nil said:
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
Click to expand...
Click to collapse
i remember having the dm verity but i forgot what i did to make it disappear.. after that time ive been running OOS rooted with twrp until i decided to go back to stock locked
So, I stopped doing anything as I got busy with my life. Here comes the 4.1.7 OTA and my DM verity was gone. So, it seems like if you go to stock and if still dm verity exists, try to do ota update or go to one ota back for flashing.
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
jmalmberg said:
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
Click to expand...
Click to collapse
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
kc6wke said:
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
Click to expand...
Click to collapse
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
jmalmberg said:
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
Click to expand...
Click to collapse
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
kc6wke said:
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
Click to expand...
Click to collapse
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
jmalmberg said:
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
Click to expand...
Click to collapse
You need to format data (type yes) In twrp
kc6wke said:
You need to format data (type yes) In twrp
Click to expand...
Click to collapse
That worked! Thank you very much!!! I really appreciate it!!!!
jmalmberg said:
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
.
Click to expand...
Click to collapse
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Tigger31337 said:
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Click to expand...
Click to collapse
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
jmalmberg said:
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
Click to expand...
Click to collapse
Yup, I solved it. Thanks. I ended up using 3.2.3.official.
Rooting; ending in bootloop help
Sorry if I am hijacking this thread; thought to discuss here as the title "Trouble rooting my g6" still applies.
I have:
XT1925-13 (Moto G6 ALI) running stock Android Pie with build ppss29.55-34.
I have issues when I tried to root. I followed these steps:
I downloaded the factory image “ALI_RETAIL_9.0_PPS29.55-34_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip” and flashed it first. The mobile restarted and went to the first screen to select a language.
I rebooted it into bootloader, ran the TWRP as a temp by command “fastboot boot twrp-3.3.0-0-Ali.img,” which asked for the password.
I pressed cancel, and then I wiped cache and data.
Via ADB I transferred “adb push Magisk-v20.0.zip /sdcard” and “adb push no-verity-opt-encrypt-6.1.zip /sdcard”.
Then from TWRP, I installed Magisk. Then when installing no-verity, it gave an error “updater process ended with an error: 1 error installing zip file ‘no-verity-opt-encrypt-6.1.zip’.
Rebooted the device with hope and ended in a boot loop.
I also tried to use Magisk-v19.4.zip in the above steps and also tried to skip no-verity-opt-encrypt-6.1.zip. All ended in boot loop.
Any idea why? Are there any guides for the combination XT1925-13 (Moto G6 ALI) running ppss29.55-34?
Many thanks for your time.
Here is a solution
Flash original boot in fastboot followed by TWRP and reboot in recovery.
Install Magisk 19.4 in TWRP (3.3.x Android 9 OK) and reboot
You can update to 20 in Magisk Manager later