Database Develop

[SOLVED] Phone changed the model in TWRP

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.

General Android 12 Beta Available for the Mi 11 Ultra (star)!

Download link for Xiaomi Mi 11 Ultra here.
How to flash Android 12 beta
Click to expand...
Click to collapse
The Android 12 beta ROM comes in the form of a .tgz extension, commonly referred to as a Fastboot ROM. To flash this ROM, you also need to have a Windows PC and phone with an unlocked bootloader. Instructions to unlock the bootloader of your phone can be found on your device’s subforums on XDA.
To flash the downloaded file, follow the instructions below:
Download the MiFlash Tool on your PC that can be found here. After downloading, extract the tool and install it. It is also advised to have ADB and Fastboot installed.
Reboot your phone into Download mode by powering it off and then pressing both the Power and Volume Down buttons together.
Connect your phone to the computer using the USB cable.
Download the Fastboot ROM .tgz file and extract it and make sure you remember the extract location, as you will need to paste the address into MiFlash Tool. Make sure there are no spaces in the extract location path.
Run MiFlash Tool on your PC and in the address bar within the tool, paste the extract location from Step 4.
Click “Refresh” within MiFlash and the app should automatically recognize your device.
Click “Run” within MiFlash to flash the ROM file to the device.
The progress bar within MiFlash will turn green, which indicates that the ROM was successfully installed. Your device should boot automatically to the new version.
Click to expand...
Click to collapse

Hello
Is it the stock Android 12 or with MIUI ?

I am tempted to install it, but I am wondering what's going to happen when beta program is finished!

jericho246 said:
Download link for Xiaomi Mi 11 Ultra here.
​
Click to expand...
Click to collapse
Does this involve a full data wipe ?

It works!

speedtripler said:
It works!
Click to expand...
Click to collapse
Full data wipe or not?

algerinferno said:
Full data wipe or not?
Click to expand...
Click to collapse
You can do it either way....
They have provided options:

Is the camera working? It has all the stock option?

speedtripler said:
You can do it either way....
They have provided options:
Click to expand...
Click to collapse
I think it'd be better to do a clean flash.

speedtripler said:
It works!
Click to expand...
Click to collapse
Wow how did you get past the first verify pin, for me it kept looping at that area kept asking me for pin, when I clicked use Google account it went back to the pin again a loop couldn't get out of it

Camera, wifi, calls etc are working?

mat.mark89 said:
Is the camera working? It has all the stock option?
Click to expand...
Click to collapse
Yes, the camera works and the Google services are working fine but this build is for testing , not to use daily, for most people I would advise to wait longer
You might have issues with third party apps that haven't been optimised yet for Android 12 etc

gokhujee said:
Wow how did you get past the first verify pin, for me it kept looping at that area kept asking me for pin, when I clicked use Google account it went back to the pin again a loop couldn't get out of it
Click to expand...
Click to collapse
Mine didn't even ask me for a pin
I flashed it coming from the Eu 12.6 weekly

Let us know how battery life is.

Is the file same for both global and Chinese variant ?

Wow, this is interesting and tempted to install.

Raj kiran said:
Is the file same for both global and Chinese variant ?
Click to expand...
Click to collapse
No idea... Mine was
a china 12/512 once upon a time!
I think you can flash anything these days, if it doesn't work for any reason you can go back, there's unbrick and rollback fix on YouTube
You just have to delete about 8 lines of code and then you can flash backwards as well as forwards

Jbdub17712 said:
Let us know how battery life is.
Click to expand...
Click to collapse
I would imagine the battery life is great because it's basically a skeleton barebone ROM
There is no miui apps if those are important to you, its not ready for grandma yet!
If you want to use this as a daily driver you will need to put some effort into installing and config
Not worth it yet for most people imo

speedtripler said:
It works!
Click to expand...
Click to collapse
Which variant of MI 11 ultra do you have global or Chinese

I opened XDA just to post this lol. So, did you do a dirty flash and kept your data?

Question Device does not update (SOLVED!!!)

Edit:
SOLVED!!!!
finally figured out the issue, will share just for information as unlikely to happen with anyone else.
When i installed xiaomi.eu, i cannot remember which partition it was installed at, was it slot A or B. and when i flashed back to official rom, i left it by default.
This has messed up my partitions when i was back to official rom. so whenever i update my system, it would just fail all the time because it is over writing the booted partition.
dont know how, and dont ask me how i fixed it, all i can explain is the following:
checked on fastboot the slot and it was A. so i tried to change it to B and it didnt work with all available commands. So, i used TWRP to boot into fastboot slot B and installed fresh ROM 12.5.4. bootloader unlocked just to be safe. then updated and it went through without any issues.
i cannot explain what exactly happened and if what i did was correct and if my theory is correct, but it worked!!!!.
Thanks to everyone contact me and gave me any idea.
Hi All,
"Couldn't update Miui"
"download rom and try updating again"
i have an issue with my device, it all started after i install eu rom and then flashed back original rom and locked bootloader.
i was on 12.5.2 when i unlocked bootloader the first time, and install eu. version. tried it for a week, and it was really bad. so i switched back to original rom 12.5.4 when it was released and locked bootloader, after that, since then, i was not able to update my device to the following roms. i tried the first time 12.5.6 and it didnt go through when device rebooted. as deviced auto restarted for a few times, (it boot to miui logo for 3 sec's then blink green then restart, happens for a few times like 6-10 times) then device reboots back to version before update but really really really slow.
in the begining, i thought it was faulty update, but i found that several people did it successfully,
Then i thought they have their bootloader unlock and 12.5.6 was a beta version, so that was the reason, until stable 12.5.7 showed up. so i've unlocked bootloader and updated, same issue.
Then i thought, maybe 12.5.4 version downloaded is corrupt somehow, so i've installed 12.5.2 and updated, failed again. same result.
all all cases above, i tried locked and unlocked bootloader and i still get green blinking a few times then a very slow version before update.
Anyone familiar with this case? i really need your help.

Your device original rom is?

hungragezone said:
Your device original rom is?
Click to expand...
Click to collapse
yes, just going with original global rom, my device is global MI version (global global)

5th try now just failed again. i really need help please.

hassanaliyeh said:
5th try now just failed again. i really need help please.
Click to expand...
Click to collapse
I think u should reflash and lock your BL using fastboot method from beginning

hungragezone said:
I think u should reflash and lock your BL using fastboot method from beginning
Click to expand...
Click to collapse
the problem is, i did that a few times now. doesnt work.
seems like there is something blocking in the update after reboot.

the error i am getting after every failure is the following:
"Couldn't update Miui"
"download rom and try updating again"

could it be a reason of installing xiaomi.eu using twrp that the partition has changed and caused this problem? just a thought.

Are you trying to install it via the OTA? Because the problem can be the unlocked bootloader

xNAPx said:
Are you trying to install it via the OTA? Because the problem can be the unlocked bootloader
Click to expand...
Click to collapse
OTA and local upgrade through the 3 dots. any other way?
btw, just tried again with locked bootloader

Well that's weird. I can push the installation with the 3 dots and everything goes well

xNAPx said:
Well that's weird. I can push the installation with the 3 dots and everything goes well
Click to expand...
Click to collapse
How large was your file?

3.2 I think

xNAPx said:
3.2 I think
Click to expand...
Click to collapse
Do you have an idea what would be the issue?
Any help would be great

xNAPx said:
3.2 I think
Click to expand...
Click to collapse
Where can you download 12.5.6 from ?

hassanaliyeh said:
OTA and local upgrade through the 3 dots. any other way?
btw, just tried again with locked bootloader
Click to expand...
Click to collapse
My gf have a unit on global 12.5.4 and it doesn't get ota updates either , very weird
Where did you get the 12.5.6 from?

speedtripler said:
My gf have a unit on global 12.5.4 and it doesn't get ota updates either , very weird
Where did you get the 12.5.6 from?
Click to expand...
Click to collapse
here is your 12.5.6
https://bigota.d.miui.com/V12.5.6.0.RKAMIXM/miui_STARGlobal_V12.5.6.0.RKAMIXM_e0b20eed12_11.0.zip
could you please report if it goes through? also, is the bootloader locked and device not rooted?
Thanks

hassanaliyeh said:
here is your 12.5.6
https://bigota.d.miui.com/V12.5.6.0.RKAMIXM/miui_STARGlobal_V12.5.6.0.RKAMIXM_e0b20eed12_11.0.zip
could you please report if it goes through? also, is the bootloader locked and device not rooted?
Thanks
Click to expand...
Click to collapse
Will try flash in 15 minutes and update

Update file seems ok.....

speedtripler said:
Update file seems ok.....
Click to expand...
Click to collapse
how will it go? after you finish update

Question cannot update locally the A14 (india) update on EU device (2213)

it always says says that verification failed.
any ideas?
*downloaded from oneplus updater app

Download by oxygen updater.
Open setting/about device/up to date/local update and select package

dude. cant you READ? this is exactly what i did.

xsoft7 said:
dude. cant you READ? this is exactly what i did.
Click to expand...
Click to collapse
Try to delete .OTA hidden folder then give a try , or may be incompatibility issue I don't know

The problem is you are trying to install Indian software onto European one. Don't know exactly why, but is is not possible. On the other hand you can do fastboot enhance your burnt will wipe your device and probably brick it if you don't read guide properly.

kouzelnik3 said:
The problem is you are trying to install Indian software onto European one. Don't know exactly why, but is is not possible. On the other hand you can do fastboot enhance your burnt will wipe your device and probably brick it if you don't read guide properly.
Click to expand...
Click to collapse
Exactly. How he managed to download Indian file by oxygen updater in EU rom?

doc.K said:
Exactly. How he managed to download Indian file by oxygen updater in EU rom?
Click to expand...
Click to collapse
Via oxygen updater you can download it, but installation won't be possible or not that easy.

kouzelnik3 said:
Via oxygen updater you can download it, but installation won't be possible or not that easy.
Click to expand...
Click to collapse
Ok

Is easy to change region on Oxygen Updater.
You can download, you can install, but people did this on 9 Pro and got problems with SIM card and other functions of the phone. That may not happen to you, but you take the chance?..
On top of this you must wipe your phone with downgrade rom or MSM tool...

you need to use the full rom, not the ota

Question Oneplus 10 Pro NE2215 can't install updates

Hey guys! When trying to update to A16, I get this error, same issue I had before with A14, any tips on what I should do to get my phone updated to the latest fw? Happens every time I try to update to the latest.

I would recommend you to download Oxygen Updater and install the full image from them.
This should solve your issue and if not after update from the full image, just reset your device and set it up as new. That's what did the trick for me.

There's no full image unfortunately NE2215 is weird.
Local upgrade fails at 99% too, even after disabling or straight up uninstalling modules.
@dladz any tips?

same here . tried updater app also. fails at 99%

dasche said:
same here . tried updater app also. fails at 99%
Click to expand...
Click to collapse
Switching to NE2213 or reseting the device is not an option ?

zopostyle said:
Switching to NE2213 or reseting the device is not an option ?
Click to expand...
Click to collapse
I switched to NE2211, did not check the system update. now i am back on NE2215 and saw this.

resetting wont make any difference.. are you boot loader unlocked? mine is unlocked.

dasche said:
I switched to NE2211, did not check the system update. now i am back on NE2215 and saw this.
Click to expand...
Click to collapse
For me when I switched to NE2213 I had to reset the device and then the updates started to install.

when switching from one to another, it does not boot without factory reset first.

GarnetSunset said:
There's no full image unfortunately NE2215 is weird.
Local upgrade fails at 99% too, even after disabling or straight up uninstalling modules.
@dladz any tips?
Click to expand...
Click to collapse
You'd need the full update, plus you'd need the newest local installer from the OnePlus community guide.
I'm on NE2213 and the updates I install are all full zips never incremental.
The only time I've ever seen a failure at 99% is when I was using the wrong local update APK whilst I was rooted.
My advice is use the rollback zip to switch to ne2213..., you'll probably find your internet improves from doing so too.

I was using the link from oxygen updater, which is a pretty generic url that appears to be "latest" etc.
Are you sure I wont lose some 5G bands for switching to global? I'm in NA and using the NA firmware so I'm just trying to think if I'll lose any signal strength
dladz said:
You'd need the full update, plus you'd need the newest local installer from the OnePlus community guide.
I'm on NE2213 and the updates I install are all full zips never incremental.
The only time I've ever seen a failure at 99% is when I was using the wrong local update APK whilst I was rooted.
My advice is use the rollback zip to switch to ne2213..., you'll probably find your internet improves from doing so too.
Click to expand...
Click to collapse

GarnetSunset said:
I was using the link from oxygen updater, which is a pretty generic url that appears to be "latest" etc.
Are you sure I wont lose some 5G bands for switching to global? I'm in NA and using the NA firmware so I'm just trying to think if I'll lose any signal strength
Click to expand...
Click to collapse
Use the full zip here https://forum.xda-developers.com/t/oneplus-a-15-full-zips-na-in-eu.4482915/#post-87371753 for a.15 then you should be able to update without any problems. Also when rooting the phone it's always best to fastboot boot the patched magisk boot.img then use direct install. Magisk will then back up original boot.img and you will be able to restore it later when update comes then all you have to do everytime you get an update is choose restore images in magisk update but don't reboot then go back in magisk and choose install to inactive slot after ota and reboot and your good to go

GarnetSunset said:
I was using the link from oxygen updater, which is a pretty generic url that appears to be "latest" etc.
Are you sure I wont lose some 5G bands for switching to global? I'm in NA and using the NA firmware so I'm just trying to think if I'll lose any signal strength
Click to expand...
Click to collapse
They're not rollback zips in oxygen updater however you do need to turn on full from there on in..and no you won't lose bands, you'll probably gain a better signal based on previous reports.
Use the rollback zip from the OnePlus community android 13 beta 2 thread.
Once rolled back you should only use the full zips from oxygen updater with the the newest local install APK.
Pic below from oxygen updater, make sure to use the advanced settings.

Thank you!! I moved over to NE2213!

GarnetSunset said:
Thank you!! I moved over to NE2213!
Click to expand...
Click to collapse
Use the button bud
How's your signal doing now that you've shifted over?

dladz said:
Use the button bud
How's your signal doing now that you've shifted over?
Click to expand...
Click to collapse
AFAICT Identical? Not sure. Only been a couple hours and I didn't use my phone much

I was able to flash only full package zips from local upgrade. but
then i install oxygenos 13 via local upgrade. after that did same with rollback to oxygenos 12 and that fixed the issue. now i can upgrade to any OTA which is coming...