Hello, every Developer...
So I own a OnePlus 3t (A3000). I rooted it using TWRP 3.2.3-1 & Magisk 16.7.
Everything was going fine until I upgraded Magisk with the Direct Install. My phone got into what forums say Bootloop.
I found many solutions but mostly had that Flash Magisk Un-installer and further. But whenever I was trying to Flash it said Error occurred installing.
So I thought that Installing Original ROM from OnePlus site would help but now its stuck on Circle Spinning.
I'm totally dead. Don't know what to do.
Please help me.
I would really appreciate a step by step guide as I am not good in understanding things like others here on this firm.
Root-1001 said:
Hello, every Developer...
So I own a OnePlus 3t (A3000). I rooted it using TWRP 3.2.3-1 & Magisk 16.7.
Everything was going fine until I upgraded Magisk with the Direct Install. My phone got into what forums say Bootloop.
I found many solutions but mostly had that Flash Magisk Un-installer and further. But whenever I was trying to Flash it said Error occurred installing.
So I thought that Installing Original ROM from OnePlus site would help but now its stuck on Circle Spinning.
I'm totally dead. Don't know what to do.
Please help me.
I would really appreciate a step by step guide as I am not good in understanding things like others here on this firm.
Click to expand...
Click to collapse
See this post https://forum.xda-developers.com/on...genos-5-0-1-android-8-0-t3728119/post78381819
And use TWRP 3.2.3-0 not -1
Sent from my OnePlus3T using XDA Labs
Related
Hi all,
I just got my Mi MIX today (6gb version). I have been trying to get TWRP and SuperSU working on it, then flash the EU rom. During this process, my TWRP has become unresponsive. At the same time, my Wifi cannot be enabled. (I am installing EU rom because my Google Play Store download speed was throttled, and I could not find the option in Mi App Store to disable)
I am hoping that someone has a stock recovery I can flash, or knows how I can revert to stock. I have ADB and Fastboot installed.
I have tried re-flashing TWRP, and it does not work. I have also tried Fastboot -w to see if it helps. It instead shows me the screen asking to write to system again, instead of the main menu like before.
Any help is very appreciated! :crying:
go read the entire detailing how to install xposed, twrp, etc others have had similar things happen and there are instructions on what to type in fastboot to fix. just read the thread.
http://forum.xda-developers.com/mi-mix/how-to/guide-flash-global-china-rom-root-gapps-t3510592/page1
The OP in this thread has a comprehensive run through of how to install TWRP, EU ROM and root with Su. I suggest using the EU TWRP from the beginning as we found that it works best with the CN Stable ROM (8.0.11.0) .
Don't forget to root
Cheers
J
Sent from my MIX using XDA Labs
Hello,
I encountered the same problem (TWRP not responsible)
Solved with flashing this version of TWRP that work with latest EU ROM .
https://mega.nz/#!A91zFZqQ!AB1AB6HMaAtVS-2GQlUNgVXDtn-ZJej22rjEwJgVQlU
Try and tell me if it's OK ?
Thanks all! This is solved now Happy to be using my new Mi MIX!
4DM said:
Thanks all! This is solved now Happy to be using my new Mi MIX!
Click to expand...
Click to collapse
Glad to hear you have it working
Enjoy your Mix
Best
J
Sent from my MIX using XDA Labs
Hi Guys,
I really need help here. I am using Huawei P9 EVA-L19.
I once unlocked bootloader, installed TWRP and rooted my phone. After 1 day I using it, I tried to flash to unofficial emui 5 which is follow the instruction from here; https://forum.xda-developers.com/p9/how-to/huawei-p9-eva-l19-android-7-0-nougat-t3532649
However, after I done flash it. I found out that there's a lot of application I can't access including my camera ( which totally gone from my phone ). I decided to flash back to emui 4.1.
The issue that I'm facing right now is, I can't even access to TWRP. I tried a lot of ways to install TWRP and try to boot. Nothing happen. I've tried to use Dload, I tried using CMD it seems never success.
Now, I really need someone to help me on this issue. I know there's a lot of people who facing the same issue that I'm facing right now. Or someone who already solve this issue please assist me. I'm already give up on this.
Thanks in advance.
Hey,
I have question about a problem I have.
So I tried to install the latest open beta version (beta 17) on my OnePlus 3T through TWRP.
This didn't worked because of ERROR: 7.
I found some solutions to fix ERROR 7 but it doesn't worked with this OS.
I tried some things like updating TWRP and installing the Oxygen recovery. I messed some things up. I deleted my OS from my device accidentally.
I solved the problem and was able to install the latest stable OS without problems.
Then I tried to install ResurrectionRemix-N for OP3T and I got the ERROR 7 again. but it said:
E3004: This package is for device: OnePlus3T, oneplus3t; this device is Oneplus3.
The thing is, it is an OnePlus 3T.
I don't know why and how it changed. The TWRP is for OP3T.
In the settings it says that the Build-Number is: ONEPLUS A3003_28_171012.
So I don't know. The default device name was OnePlus 3T.
Later I got an automatic email from Google because I logged in on an "new" device. But here they say that it is an OP3.
I would like to change it, but I don't know how.
I thought I can just change someting in the build.prop, but I didn't tried it yet.
Hopefully someone can help me.
-Fun4Jan
Okay so, I went in the build.prop and this is what I found:
ro.build.product=OnePlus3
ro.build.user=OnePlus
ro.build.flavor=OnePlus3-user
ro.build.description=OnePlus3-user 7.1.1 NMF26F 136 dev-keys
ro.common.soft=OnePlus3
ro.display.series=OnePlus 3T
ro.build.oemfingerprint=7.1.1/NMF26F/10122113:user/release-keys
[...]
ro.build.ota.versionname=OnePlus3TOxygen_28_1710122300
ro.build.version.ota=OnePlus3TOxygen_28.A.57_GLO_057_1710122300
So do you think I can just change it in the build.prop?
Yes, you can change it in the build.prop.
please try changing it and report us back.
akash.galaxy07 said:
Yes, you can change it in the build.prop.
please try changing it and report us back.
Click to expand...
Click to collapse
So I changed it and tried to install it but failed. It tells me that it is an OP3
Try the Qualcomm MSM Tool and try resetting your device completely as instructed on the Unbrick guide. Looks like you installed a corrupted Open Beta package, and something from Bootloader configuration went completely haywire. You can backup your Internal Storage since you have TWRP access.
Good Luck!
Have you tried using TWRP version 3.1.1-0?
Fun4Jan said:
So I changed it and tried to install it but failed. It tells me that it is an OP3
Click to expand...
Click to collapse
With oreo use this TWRP https://forum.xda-developers.com/devdb/project/dl/?id=27068
after flash again beta 17
przemcio510 said:
Have you tried using TWRP version 3.1.1-0?
Click to expand...
Click to collapse
I tried it with TWRP 3.1.1-2 for the OnePlus 3t
thes3usa said:
Try the Qualcomm MSM Tool and try resetting your device completely as instructed on the Unbrick guide. Looks like you installed a corrupted Open Beta package, and something from Bootloader configuration went completely haywire. You can backup your Internal Storage since you have TWRP access.
Good Luck!
Click to expand...
Click to collapse
Okay, I will try it. I hope it works
kob72 said:
With oreo use this TWRP https://forum.xda-developers.com/devdb/project/dl/?id=27068
after flash again beta 17
Click to expand...
Click to collapse
Can you Explain it to me a bit detailed please.
Fun4Jan said:
Okay, I will try it. I hope it works
Click to expand...
Click to collapse
So I tried it with this instruction: http://www.androidbrick.com/oneplus-one-two-3-3t-5-mega-unbrick-guide-twrp-flashing/
I did it like it says but some things were different and I think it was because my phone worked and wasn't bricked.
Now I have my phone and got the oldest OOS 3.5.1. My changeable Phonename is OnePlus 3T but I got a mail again where it says that I logged in with a OnePlus 3.
I will try to install TWRP and the latest OOS version.
So I finally solved it.
I was a bit confused with the TWRP version, so I thought that I can install the latest OOS with the Oxygen Recovery and I saw, that I used the wrong Recovery for my phone.
I used the right TWRP version for my phone but not the right Oxygen Recovery when I tried it with it.
I thank all you guys for the help.
Fun4Jan said:
So I finally solved it.
I was a bit confused with the TWRP version, so I thought that I can install the latest OOS with the Oxygen Recovery and I saw, that I used the wrong Recovery for my phone.
I used the right TWRP version for my phone but not the right Oxygen Recovery when I tried it with it.
I thank all you guys for the help.
Click to expand...
Click to collapse
No problem, would you mind adding [SOLVED] to the title, so other users with the same or similar problem will read this post to fix their devices too?
Thanks, and happy flashing!
Fun4Jan said:
I tried it with TWRP 3.1.1-2 for the OnePlus 3t
Click to expand...
Click to collapse
Then try with the older version, the newest one is known to cause problems with proper device detection.
Edit: nevermind, just saw it's fixed.
Hey all, so yesterday i got my phone stuck in a "boot loop". I was trying to install TWRP and magisk to root my phone, after 2 hours of constantly reinstalling TWRP i finally got it to work. Every time my phone would end up just being on a black screen not being able to get to the TWRP menu but i could still access fastboot, i fixed it by "installing" orangefox TWRP, it never actually installed it but i got back into my phone at least, however now thats not working, and im stuck here only being able to get into fast boot. I followed this tutorial - https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127. When i eventually did get it to install TWRP its because i used the All in one tool. Im currently stuck in the loop again, all i did was follow a youtube video on overclocking my display to 81hz, so i was in TWRP, made a backup of a file, flashed the 81hz.img and now i cant get into twrp or my phone.....How do i fix this?
Im currently flashing a stock rom with MiFlash, taking a few minutes but this is the last thing i can think of to fix this, no im not using the flash and lock method.
Edit: So i decided to use the All in one tool to flash the rom instead, i can now get into TWRP but the phone still by default boots to Fastboot, it wont actually go into the phone? What do i do?
Edit 2: Okay so that fixed it, now to reinstall TWRP with the all in one tool and reroot my phone.........
Edit 3: Okay so new issue, everything is all good TWRP is installed phone is rooted, but im trying to update to the latest MIUI 10 version (on MIUI 9 atm) and i can't install it? It downloads fine but it wont install? Do i have to flash the update file since it wont update through the updater?
JasonBjorn said:
Hey all, so yesterday i got my phone stuck in a "boot loop". I was trying to install TWRP and magisk to root my phone, after 2 hours of constantly reinstalling TWRP i finally got it to work. Every time my phone would end up just being on a black screen not being able to get to the TWRP menu but i could still access fastboot, i fixed it by "installing" orangefox TWRP, it never actually installed it but i got back into my phone at least, however now thats not working, and im stuck here only being able to get into fast boot. I followed this tutorial - https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127. When i eventually did get it to install TWRP its because i used the All in one tool. Im currently stuck in the loop again, all i did was follow a youtube video on overclocking my display to 81hz, so i was in TWRP, made a backup of a file, flashed the 81hz.img and now i cant get into twrp or my phone.....How do i fix this?
Im currently flashing a stock rom with MiFlash, taking a few minutes but this is the last thing i can think of to fix this, no im not using the flash and lock method.
Edit: So i decided to use the All in one tool to flash the rom instead, i can now get into TWRP but the phone still by default boots to Fastboot, it wont actually go into the phone? What do i do?
Edit 2: Okay so that fixed it, now to reinstall TWRP with the all in one tool and reroot my phone.........
Click to expand...
Click to collapse
A bit of advice.
If you don't know what your doing, don't follow random YouTube videos.
There are some very good videos and some very bad videos. If you don't know what you're doing, you won't know the difference between a good video and a bad one
Until you're comfortable with flashing mods, etc. stick to advice given here. It might not be instant, but you'll get good advice (if it's not good advice then someone else will point that out).
When asking for help give us more info.
What phone do you have?
What ROM was on the phone before first trying to install TWRP?
What version of TWRP have you been trying to install?
Why did you change from using Mi Flash Tool to the all in one tool?
Did you wait for the Mi Flash Tool to finish but it didn't work, or did you get bored of waiting for it to complete and cancelled it?
I appreciate this is a bit late now and not necessary as you've eventually sorted it yourself, but giving the info I've pointed out, at the time, may have actually got you some useful replies before you actually got there yourself.
Robbo.5000 said:
A bit of advice.
If you don't know what your doing, don't follow random YouTube videos.
There are some very good videos and some very bad videos. If you don't know what you're doing, you won't know the difference between a good video and a bad one
Until you're comfortable with flashing mods, etc. stick to advice given here. It might not be instant, but you'll get good advice (if it's not good advice then someone else will point that out).
When asking for help give us more info.
What phone do you have?
What ROM was on the phone before first trying to install TWRP?
What version of TWRP have you been trying to install?
Why did you change from using Mi Flash Tool to the all in one tool?
Did you wait for the Mi Flash Tool to finish but it didn't work, or did you get bored of waiting for it to complete and cancelled it?
I appreciate this is a bit late now and not necessary as you've eventually sorted it yourself, but giving the info I've pointed out, at the time, may have actually got you some useful replies before you actually got there yourself.
Click to expand...
Click to collapse
I have a rough idea on what im doing i've done all this stuff before loads, but xiaomi just seems to be different idk. Considering this is the k20/k20pro section i assumed its obvious thats what i was using.......Everything is sorted like i said but i cant get MIUI to update, it downloads, i hit reboot and it boots me to TWRP instead of installing the update.......i've come to really like the MIUI without the app drawer but now i have an app drawer as im on Android 9, I flashed the lastest rom but before flashing i didnt have an app drawer and was on the latest build so no idea whats going on there......guess i just have to live with this now?
JasonBjorn said:
I have a rough idea on what im doing i've done all this stuff before loads, but xiaomi just seems to be different idk. Considering this is the k20/k20pro section i assumed its obvious thats what i was using.......Everything is sorted like i said but i cant get MIUI to update, it downloads, i hit reboot and it boots me to TWRP instead of installing the update.......i've come to really like the MIUI without the app drawer but now i have an app drawer as im on Android 9, I flashed the lastest rom but before flashing i didnt have an app drawer and was on the latest build so no idea whats going on there......guess i just have to live with this now?
Click to expand...
Click to collapse
What's not obvious is whether you have a Chinese or Indian K20 Pro, or a global or European 9T Pro. Also whether you're trying to install the version of MIUI that is correct for the phone, or if you're flashing from a different region. As you say Xiaomi does things a bit different, so we're seeing things in these forums that what works on one version of the phone doesn't quite work on another.
Robbo.5000 said:
What's not obvious is whether you have a Chinese or Indian K20 Pro, or a global or European 9T Pro. Also whether you're trying to install the version of MIUI that is correct for the phone, or if you're flashing from a different region. As you say Xiaomi does things a bit different, so we're seeing things in these forums that what works on one version of the phone doesn't quite work on another.
Click to expand...
Click to collapse
well heres the weird thing, i bought the EU version of the phone, which i know is supposed to be the 9t pro, but not only did the site call it the K20 pro, but in the settings its model number is also the K20 pro. I got everything working fine.
I am getting the endless bootloop at the Motorola logo screen after installing magisk. I've tried 4 different versions of magisk and all end the same way. I am following This Guide
I have a couple of questions:
1. Should my first step after flashing twrp be this command to flash noverity which I am getting from this instructional thread? because the guide I am following doesn't mention it. I've also tried this file with no success either: no-verity-opt-encrypt-6.0.zip
2. Also, In the guide just before pushing fstab, it says to input the following command but my command prompt doesn't return any kind of confirmation when I put this in. Should there be a response that something was mounted?
Code:
adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
There is a similar but different command from the thread that says to flash noverity that also doesn't return any response:
Code:
adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor
What am I doing wrong? I feel like I'm so close to being rooted but I must be missing something or using a wrong file or something. I've unlocked my bootloader, I've successfully installed twrp, I can successfully reflash the stock rom after the bootloop. I just can't get magisk installed.
IDrinkTooMuchCoffee said:
Use Magisk v19.3. It's the last one that works with stock 8.0. You can upgrade from Magisk manager to 20.3 afterwards if you want to and it won't boot loop.
Click to expand...
Click to collapse
What about the questions I had regarding the process? I've already tried 4 different versions of Magisk including 17.2 and 18.1 so I don't think it's as simple as installing an older version.
IDrinkTooMuchCoffee said:
Sorry. I'm not sure what the point in that would be but I'm not on xda much and didn't see your post. All you should need to do is flash the no verity-opt encrypt zip, then magisk v19.3. No need to push a modded fstab or anything else.
Click to expand...
Click to collapse
After 10 posts I think, it opens up some sort of permissions so some people write useless posts to get to that.
I tried 19.3 the day of your post and it still boot looped but I did finally get it working without noverity and with 19.2.
MilkyTech said:
After 10 posts I think, it opens up some sort of permissions so some people write useless posts to get to that.
I tried 19.3 the day of your post and it still boot looped but I did finally get it working without noverity and with 19.2.
Click to expand...
Click to collapse
In case you didn't know you can upgrade magisk once you are back on. It won't put you in a bootloop.
Play Nicely Please
Thread cleaned.
We expect all members to abide by the forum rules In this case, specifically;
2. Member conduct.
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
Click to expand...
Click to collapse
This sums up as: If you can't say something nice, don't say anything at all.
Yeah I apologise on my half. Don't know why he was coming after me but I let my dark side do the typing in the response ????
moto e5 play after installing twrp then got supersu
but as soon as i installed it both n i got on twrp recovery then i tried installing super from twrp then after i find out that my phone gets stuck in a bootloader loop and i didnt install stock rom or any rom or firmware im really stuck would appreciate if i can get some help oh n also when i use fastboot to get into recovery mode my touch screen wouldn't work
IDK about su. Everyone that I have seen is using magisk. And when you say the touchscreen isn't working is that in twrp?