[SOLVED] Phone changed the model in TWRP - OnePlus 3T Questions & Answers

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.

Related

[Q] ota update always failing

i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Spiffy Jay said:
i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Click to expand...
Click to collapse
You really dont need to re-lock bootloader. You could have just downloaded and flashed through twrp and then flash supersu. But i am not sure why it is failing on your end.
Same thing here, always installation failed
Try a different type c cable.. Apparently, I was having this issue
Op3t original cable : Android auto and adb side load works perfectly on my op3
But when used on op3t, android auto cannot detect and side load of ota fails.
Used the original cable from Google Nexus 6p, Android auto works perfectly but I didn't try side load adb because I already flash via TWRP instead.
Try changing cables
Found a FIX!
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Spiffy Jay said:
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Click to expand...
Click to collapse
I too had the same problem. Can you explain me how to get that?
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Spiffy Jay said:
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Click to expand...
Click to collapse
I am in 3.5.3 now. Locked bootloader. Still OTA gets failed. When I tried Oxygen OS 3.5.3 through sideload also gets failed. Can you give me the link for beta rom???
@kabeeradam im a complete dumbass i realized that i posted this on the wrong phone it was meant to be one the oneplus 3 not 3t but it should be the same i guess
http://downloads.oneplus.net/devices/oneplus-3/ flash open beta 10 through sideload and then flash oxygenos 3.2.8 and do normal ota update im sorry i just saw

How to root 3T on OOS4.0 ?

Hey,
I bought my phone 2 days ago, after charging it I updated to OOS4.0 through the system updates using VPN, when I got home I unlocked the bootloader but did nothing else afterwards. I'm seeing a lot of threads with people having issues with TWRP and encryption, considering my last device was the OPO and I was running Lollipop (was too lazy to update it ) I'm kinda out of the loop.
How can I root it now that it's running Nougat ? simply flashing the twrp img using fastboot and then flashing the SuperSU zip or is there a different method ?
Any kind of help is greatly appreciated.
Also, one more question, is Xposed working on Nougat ? I had quite a few useful modules on my OPO, wanted to know if that's possible on the 3T as well.
The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.
WeirdSoup said:
The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.
Click to expand...
Click to collapse
And where should I download SuperSU from ? Heard the project is being taken over or smth like that
B00steed said:
And where should I download SuperSU from ? Heard the project is being taken over or smth like that
Click to expand...
Click to collapse
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
WeirdSoup said:
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Is it better to install this instead of SuperSU ?
If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.
B00steed said:
Is it better to install this instead of SuperSU ?
Click to expand...
Click to collapse
It's case by case, and I don't know which one is good for you. Do some research and figure out yourself.
---------- Post added at 11:30 AM ---------- Previous post was at 11:24 AM ----------
23Six said:
If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.
Click to expand...
Click to collapse
Magisk is open source, and it is also easy to install. You can also install the Magisk modules. It's not a simple root-hide app as many people still misunderstand.
So, with oxygen 4.0.1 the procedure will be the same?
TWRP Stuck Mount password
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers
junostik said:
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers
Click to expand...
Click to collapse
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Thanks for quick reply, I'll check it.
bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------
junostik said:
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------
Click to expand...
Click to collapse
I read that it takes some minutes if you are f2s and encrypted but I don't know how to proceed since I haven't flashed twrp and root yet.
Sorry but you may have to wait someone who has already done it

Cannot install TWRP on Mi Mix

Hi!
I recently bought a Mi Mix and want to flash it with Lineage OS.
I followed all relevant instructions - did unlock the bootloader and so on - but I am not able to install TWRP using ADB and fastboot.
The phone is connecting well in ADB - even the "fastboot flash recovery twrp.img" gets a positive response - all seems to work fine. But after rebooting, I am always confronted with the stock recovery - the flashing so seems not to work out of some reason - TWRP gets removed during the reboot process.
I also tried to first flash and then use the "fastboot boot twrp.img" command. This command starts TWRP, but only in a frozen state - TWRP then starts in a way that you are not able to interact with the interface. Also here - after rebooting the stock recovery is there again. Can someone give me a hint, how to solve this problem?
I am running ADB on a Linux Computer (Debian 9) - dont think, that this might cause issues, but maybe....
The phone runs the MIUI-Version "MIUI Global 9.1 Stable"
It would be great, if someone here could help me out. I am somehow stuck and dont know how to proceed..
Thanks for taking the time!
Best
You can find two compatible versions of TWRP here.
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
H0707 said:
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
Click to expand...
Click to collapse
Touch has never worked on the official versions to my knowledge. Even the latest 3.2.1.0 build still has broken touch. It is still usable if you use a USB adapter/mouse, but not via touch.
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
H0707 said:
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
Click to expand...
Click to collapse
Use 8.1.4 and wipe caches
https://redirect.viglink.com/?forma...://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
H0707 said:
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
Click to expand...
Click to collapse
After
I use thishttps://androidfilehost.com/?fid=673368273298927160 TWRP Modified by MrRaines (Highly recommended) and this how to show install twrp on mi mix
gavin19 said:
You can find two compatible versions of TWRP here.
Click to expand...
Click to collapse
I was looking for that as well! Thanks for sharing. I can confirm that this TWRP version works well with the Mi Mix.
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
Are you encrypted, or maybe you missed a stage when installing,
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
james1089 said:
Are you encrypted, or maybe you missed a stage when installing,
Click to expand...
Click to collapse
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
malimt said:
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
Click to expand...
Click to collapse
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
james1089 said:
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
Click to expand...
Click to collapse
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
malimt said:
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
Click to expand...
Click to collapse
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
james1089 said:
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
Click to expand...
Click to collapse
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
malimt said:
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
Click to expand...
Click to collapse
So does it show up when phone is booted?
james1089 said:
So does it show up when phone is booted?
Click to expand...
Click to collapse
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
malimt said:
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
Click to expand...
Click to collapse
I'm going to try when I get home, it's been do long since I tried something like that, have you ticked and then unticked mount in read only. Then reboot to recovery again.

Question [NE2215] OxygenOs 13 C.19 (After OTA Issues)

Before updating android i read that there could be some bugs despite being a stable rom. however, what is happening with my device is that it is apparently not charging.
Yesterday it was at 30% battery... When I tried some things with fastboot enhance, it showed up with 79%. That is, maybe it is loading, but the system is not recognizing it.
Is there any solution for this? Or would I have to go back to android 12?
Original charger!
Fastboot working normally.
Give it a factory wipe mate.. Then retest
dladz said:
Give it a factory wipe mate.. Then retest
Click to expand...
Click to collapse
I did It from recovery mode. Didnt work
Diguinho76 said:
I did It from recovery mode. Didnt work
Click to expand...
Click to collapse
Via the OS mate.
Also what things in fastboot?? We've no idea what you've done so helping isn't easy..
I would definitely do wipe as you've changed bases, brought over all your data from 12 to 13...
dladz said:
Via the OS mate.
Also what things in fastboot?? We've no idea what you've done so helping isn't easy..
I would definitely do wipe as you've changed bases, brought over all your data from 12 to 13...
Click to expand...
Click to collapse
You mean from settings, right? Didnt work too :/
Okay, I'll explain from the beginning. I was on rom 11 c.16 and had root access.
I unrooted completely and flashed the new C.19 version. I don't remember if I reset the device before putting the new version... After I updated, I rooted it again correctly...
(i downloaded full version c.19 by oxygen update app and flashed it by fastboot enhance)
I didn't realize it at the time, but I believe that since I updated the cell it didn't appear that it was charging anymore.
Finally, I was trying to go back to the previous rom (Hopefully that would solve it)... Following the steps in fastboot enhance... as soon as I clicked on reboot to fastboot, the device entered the mode and appeared with the battery at 79% whereas it was at 30%.
Since then I tried to reset through recovery mode and via OS as well but none of them worked.
Diguinho76 said:
You mean from settings, right? Didnt work too :/
Okay, I'll explain from the beginning. I was on rom 11 c.16 and had root access.
I unrooted completely and flashed the new C.19 version. I don't remember if I reset the device before putting the new version... After I updated, I rooted it again correctly...
I didn't realize it at the time, but I believe that since I updated the cell it didn't appear that it was charging anymore.
Finally, I was trying to go back to the previous rom (Hopefully that would solve it)... Following the steps in fastboot enhance... as soon as I clicked on reboot to fastboot, the device entered the mode and appeared with the battery at 79% whereas it was at 30%.
Since then I tried to reset through recovery mode and via OS as well but none of them worked.
Click to expand...
Click to collapse
Ok so avoid fastboot enhance. You really don't need that..
Rollback to 12 with the local APK and relevant rollback package..then update, then wipe, then root.
No idea why it's happened but it seems quite fixable and almost certainly something to do with the base change from 12 to 13.
dladz said:
Give it a factory wipe mate.. Then retest
Click to expand...
Click to collapse
dladz said:
Ok so avoid fastboot enhance. You really don't need that..
Rollback to 12 with the local APK and relevant rollback package..then update, then wipe, then root.
No idea why it's happened but it seems quite fixable and almost certainly something to do with the base change from 12 to 13.
Click to expand...
Click to collapse
NE2215_11_A_OTA_0150_all_3a87c8_10100001-A12-C16.zip
drive.google.com
Thats the previous rom i was using. Do you think it's gonna work?
Diguinho76 said:
NE2215_11_A_OTA_0150_all_3a87c8_10100001-A12-C16.zip
drive.google.com
Thats the previous rom i was using. Do you think it's gonna work?
Click to expand...
Click to collapse
If you find the beta update it'll link to the OnePlus community that has the rollback packages.
Here
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
dladz said:
If you find the beta update it'll link to the OnePlus community that has the rollback packages.
Click to expand...
Click to collapse
dladz said:
Here
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
Click to expand...
Click to collapse
So I have to put this beta version?
Diguinho76 said:
So I have to put this beta version?
Click to expand...
Click to collapse
No dude the rollback package..
No idea what that screenshot says ether buddy.. I'm English
.
dladz said:
No dude the rollback package..
No idea what that screenshot says ether buddy.. I'm English
Click to expand...
Click to collapse
Ah, ok.
IN and NA version there. Is there a problem, since mine is a global version?
Diguinho76 said:
Sorry, its in portuguese. But it isnt the package you sent. ill try it now
Click to expand...
Click to collapse
Diguinho76 said:
Ah, ok.
IN and NA version there. Is there a problem, since mine is a global version?
Click to expand...
Click to collapse
Ahh there's no global version?
Righto... Sorry man not sure then, there may be a global version somewhere else.
I've read that you can change region but that sounds like overkill for your situation buddy.
Seek out the global rollback package.
As per the message, are you using the local install APK instead of the system local installer.
The latter won't work, instructions are on the OnePlus site
dladz said:
As per the message, are you using the local install APK instead of the system local installer.
The latter won't work, instructions are on the OnePlus site
Click to expand...
Click to collapse
From what I've seen the NA and Global versions work equally. Wait for it to finish now and see what happens
This is now the NA version of Rollback
The title of the thread is 2215 which is the NA version, the Global misnomer comes from one of their own posts though iirc.
@Diguinho76 The NA rollback full zip is your best bet right now.
Prant said:
The title of the thread is 2215 which is the NA version, the Global misnomer comes from one of their own posts though iirc.
@Diguinho76 The NA rollback full zip is your best bet right now.
Click to expand...
Click to collapse
Hmmm, okay. Thank you. Its almost finishing... install progress at 76%

Question Miui 14 root

Is there already a way to root on android 13 for redmi note 10 pro? Twrp? I can't find anything so far, maybe someone knows something?
kawala8888 said:
Is there already a way to root on android 13 for redmi note 10 pro? Twrp? I can't find anything so far, maybe someone knows something?
Click to expand...
Click to collapse
Same as on Android 12. That was the one with the issue decrypting in custom recovery.
Can't you just fix boot.img with Magisk and then fastboot flash it?
hyperboarean said:
Can't you just fix boot.img with Magisk and then fastboot flash it?
Click to expand...
Click to collapse
Yep.
so, i bought my new redmi note 10 pro yesterday.
its on android 12, miui 13. and it asks me to upgrade.
i havent upgraded yet, thinking maybe rooting it with twrp and all, would be difficult.
Should i keep the current version and root it. or am i ok to upgrade it and then rooting it?
seeing this thread, it seems like im ok with upgrading and rooting. but want to make sure.
Clawsman said:
so, i bought my new redmi note 10 pro yesterday.
its on android 12, miui 13. and it asks me to upgrade.
i havent upgraded yet, thinking maybe rooting it with twrp and all, would be difficult.
Should i keep the current version and root it. or am i ok to upgrade it and then rooting it?
seeing this thread, it seems like im ok with upgrading and rooting. but want to make sure.
Click to expand...
Click to collapse
Wait the days until you are unlocked, in case something borks during that procedure.
thank you for replying.
well, i couldn't wait, considering the new update is lighter and better. so i just updated it and everything went smooth. What is the best way of rooting it? i mean, should i go with or without the twrp. any bugs with the twrp. or is there any better recovery to flash.
Clawsman said:
thank you for replying.
well, i couldn't wait, considering the new update is lighter and better. so i just updated it and everything went smooth. What is the best way of rooting it? i mean, should i go with or without the twrp. any bugs with the twrp. or is there any better recovery to flash.
Click to expand...
Click to collapse
I'd just fix boot.img with Magisk to root. TWRP is mostly just for flashing different roms, and our phones use 2 different touch screens, so your might not even work in TWRT.
hyperboarean said:
I'd just fix boot.img with Magisk to root. TWRP is mostly just for flashing different roms, and our phones use 2 different touch screens, so your might not even work in TWRT.
Click to expand...
Click to collapse
I have been using TWRP on every device i have rooted. i just love the TWRP recovery. because, as you said, it allows me to flash different kind of roms and it allows me to backup my current rom.
i am probably not going to flash any custom roms on this device, but i would like to have the opportunity to backup my current rom for flashing it later on if needed.
Will i be able to do this with the fixed boot.img and Magisk?
Clawsman said:
I have been using TWRP on every device i have rooted. i just love the TWRP recovery. because, as you said, it allows me to flash different kind of roms and it allows me to backup my current rom.
i am probably not going to flash any custom roms on this device, but i would like to have the opportunity to backup my current rom for flashing it later on if needed.
Will i be able to do this with the fixed boot.img and Magisk?
Click to expand...
Click to collapse
Magisk is just for root and different modules (like viper4android). You need TWRP to backup rom, but as I said touch might not work for you, check the TWRP touch not working posts.
hyperboarean said:
Magisk is just for root and different modules (like viper4android). You need TWRP to backup rom, but as I said touch might not work for you, check the TWRP touch not working posts.
Click to expand...
Click to collapse
well, it seems "not worth it". until an official TWRP is released.
And if i decide flash boot.img/Magisk or TWRP, mtk will restore my device back to its locked/stocked state?

Categories

Resources