I'm planning to buy the K20 Pro from Aliexpress with the Chinese Rom and then flash the global ROM.
I've searched the forum but couldn't find anything regarding IMEI repair incase something goes wrong.
Is it possible to repair the IMEI on the K20 Pro? has anyone tried it?
redvern said:
I'm planning to buy the K20 Pro from Aliexpress with the Chinese Rom and then flash the global ROM.
I've searched the forum but couldn't find anything regarding IMEI repair incase something goes wrong.
Is it possible to repair the IMEI on the K20 Pro? has anyone tried it?
Click to expand...
Click to collapse
In ten years of flashing a hundred phone's I've never experienced an IMEI issue. It's so extremely rare you almost never see it mentioned in any forum of any phone. It's really the last thing you need to worry about with this extremely fickle phone.
954wrecker said:
In ten years of flashing a hundred phone's I've never experienced an IMEI issue. It's so extremely rare you almost never see it mentioned in any forum of any phone. It's really the last thing you need to worry about with this extremely fickle phone.
Click to expand...
Click to collapse
Can you help me too? I am getting Nv data corrupted error on Redmi-Recovery 3.0 screen. It's all because of WriteDualIMEI. My main thread is here. Thanks...
Dentrax said:
Can you help me too? I am getting Nv data corrupted error on Redmi-Recovery 3.0 screen. It's all because of WriteDualIMEI. My main thread is here. Thanks...
Click to expand...
Click to collapse
If you can boot TWRP, then use LR team's TWRP, get the persist partition from the stock fastboot rom and flash the persist.img.
theincognito said:
If you can boot TWRP, then use LR team's TWRP, get the persist partition from the stock fastboot rom and flash the persist.img.
Click to expand...
Click to collapse
Thanks, I don't quite understand the second one. How can i get the persist partition? And where can I find the persist.img?
Dentrax said:
Thanks, I don't quite understand the second one. How can i get the persist partition? And where can I find the persist.img?
Click to expand...
Click to collapse
persist.img is inside the fastboot rom.
Dentrax said:
Thanks, I don't quite understand the second one. How can i get the persist partition? And where can I find the persist.img?
Click to expand...
Click to collapse
Fixed, see here.
i have the same problem. how do u do to recover your phone dude? help pls :c
Related
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
florian-m19 said:
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
Click to expand...
Click to collapse
I think yes, but I'm not sure
Was wondering the same thing, does anyone know if the red magic 3 is A only or an A/B device. I'm pretty sure it's A only, but I couldn't find any documentation online.
Its A only i think.
Hum... So Project Treble should work ?
That is interesting !
If I could install Resurrection Remix to this device and provided everything works it would become really almost perfect.
If anyone wants to try... If not I'll do it myself when I have time (in 2 or 3 days)...
Regards.
If the device has treble support, meaning a vendor partition it should work no problem, a/b partitioning is really not required for treble.
I tested treble using fastboot, since twrp had some issues, but it resulted in a bootloop and a corrupted recovery partition. I managed to fix it by following: https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
Twrp gave me a mounting error for
/system_root, which is fixable by setting system to be read-only and then rebooting the recovery and re enableing read/write. Have not had the time to test using twrp and treble yet.
*I posted earlier in the day but managed to fix all the issues I had, so this a better summary :silly:
trepKep said:
I tested treble using fastboot, since twrp had some issues, but it resulted in a bootloop and a corrupted recovery partition. I managed to fix it by following: https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
Twrp gave me a mounting error for
/system_root, which is fixable by setting system to be read-only and then rebooting the recovery and re enableing read/write. Have not had the time to test using twrp and treble yet.
*I posted earlier in the day but managed to fix all the issues I had, so this a better summary :silly:
Click to expand...
Click to collapse
So, this means its not working.. Sad Story.
florian-m19 said:
So, this means its not working.. Sad Story.
Click to expand...
Click to collapse
Well not necessarily, since I flashed the lineageos gsi through fastboot. (That may be the issue) I was having issues with twrp. I will try again today, although the chances are slim.
trepKep said:
Well not necessarily, since I flashed the lineageos gsi through fastboot. (That may be the issue) I was having issues with twrp. I will try again today, although the chances are slim.
Click to expand...
Click to collapse
U should clear user data and cache after installing new system if you have bootloop problem
Make sure its A only GSI
em902566 said:
U should clear user data and cache after installing new system if you have bootloop problem
Make sure its A only GSI
Click to expand...
Click to collapse
I'll keep that in mind
trepKep said:
I'll keep that in mind
Click to expand...
Click to collapse
Hey, did you try it again?
florian-m19 said:
Hey, did you try it again?
Click to expand...
Click to collapse
No, I was busy. But I'm trying right now
Treble Attempt #2
No luck, everything flashed with no errors, but all I get is more than 10 minutes of black screen. I also tried flashing magisk right after the gsi finished, same result.
trepKep said:
Treble Attempt #2
No luck, everything flashed with no errors, but all I get is more than 10 minutes of black screen. I also tried flashing magisk right after the gsi finished, same result.
Click to expand...
Click to collapse
Hmm then we must wait for a custom Rom..
florian-m19 said:
Hmm then we must wait for a custom Rom..
Click to expand...
Click to collapse
Yeah, a one plus 7 pro port would be nice
florian-m19 said:
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
Click to expand...
Click to collapse
Word of advice. Do not attempt to flash anything on this cell. You will regret it. I tried to flash TWRP over 6 weeks ago an it's been dead ever since. Even a cellphone repair center guy could not repair it.
You need to leave good enough alone.
People all around the world have been stuck in permanent recovery screens or fastboot screens like me.
It really is a very good cell the way it is ?
Bryceicle1971 said:
Word of advice. Do not attempt to flash anything on this cell. You will regret it. I tried to flash TWRP over 6 weeks ago an it's been dead ever since. Even a cellphone repair center guy could not repair it.
You need to leave good enough alone.
People all around the world have been stuck in permanent recovery screens or fastboot screens like me.
It really is a very good cell the way it is ?
Click to expand...
Click to collapse
Many people have faced the issue and they have recovered their device. Look for all solutions available.
danishajaz said:
Many people have faced the issue and they have recovered their device. Look for all solutions available.
Click to expand...
Click to collapse
I have. 7 weeks an counting an no working cell yet. I bought an Mi9 an no issues with it. Easy to reinstall firmware. The red magic 3 is the most difficult to repair cell I have ever encountered. I wish they had something like miflashpro for it
Treble is working from chinese ROM with twrp make sure image is A/B because this device is A/B
Hello everyone,
Can someone help me with fixing my Persist Partition?
My Fingerprint Scanner doesn't work, and I found out it might be due to a corrupt /Persist.
I've tried extracting a Payload.bin (from the latest OTA Firmware) but it doesn't contain any Persist Images.
Can anyone either send me their Persist.img or help me find a original Persist.img from the Stock ROM?
Thanks in advance!
Fatal_Scythe said:
Hello everyone,
Can someone help me with fixing my Persist Partition?
My Fingerprint Scanner doesn't work, and I found out it might be due to a corrupt /Persist.
I've tried extracting a Payload.bin (from the latest OTA Firmware) but it doesn't contain any Persist Images.
Can anyone either send me their Persist.img or help me find a original Persist.img from the Stock ROM?
Thanks in advance!
Click to expand...
Click to collapse
Here you go...
Andrologic said:
Here you go...
Click to expand...
Click to collapse
Thank you!
If I may ask, is this your Persist, or is this from an Official ROM?
Fatal_Scythe said:
Thank you!
If I may ask, is this your Persist, or is this from an Official ROM?
Click to expand...
Click to collapse
It's mine. Persist is not part of the ROM, that's why you can extract it from there. It's factory installed in its own partition.
Andrologic said:
It's mine. Persist is not part of the ROM, that's why you can extract it from there. It's factory installed in its own partition.
Click to expand...
Click to collapse
That makes sense.
Though I kinda think that it's dumb that it's kind-of-impossible to obtain an "official" Persist Image from Asus since others like Xiaomi just put it into their Firmwares too, but alrighty I guess.
Will flash tomorrow and hopefully it helps.
Andrologic said:
It's mine. Persist is not part of the ROM, that's why you can extract it from there. It's factory installed in its own partition.
Click to expand...
Click to collapse
Well, kind of expected that but it doesn't work.
The Contents of my Persist Partition don't seem to change no matter how often I "erase" and "flash" the Persist.img. Calibrating with the "Factory Test" Tool also gives me an "get calibrate failed" error again so yeah.... Guess I'll go with Face Unlock for now.
Thank you very much though for your quick help.
Fatal_Scythe said:
Well, kind of expected that but it doesn't work.
The Contents of my Persist Partition don't seem to change no matter how often I "erase" and "flash" the Persist.img. Calibrating with the "Factory Test" Tool also gives me an "get calibrate failed" error again so yeah.... Guess I'll go with Face Unlock for now.
Thank you very much though for your quick help.
Click to expand...
Click to collapse
How do you flash it? Try using TWRP and if that doesn't work you should be able to flash it with the device in EDL mode.
Andrologic said:
How do you flash it? Try using TWRP and if that doesn't work you should be able to flash it with the device in EDL mode.
Click to expand...
Click to collapse
I tried all of that actually. It flashed just fine, but that's pretty much it.
Can someone please send me a backup of persist file because the ROM does not that and I bricked my device without a backup now orientation sensor is In a loop from 0 to 360. Any help would be highly appreciated.
dequr said:
Can someone please send me a backup of persist file because the ROM does not that and I bricked my device without a backup now orientation sensor is In a loop from 0 to 360. Any help would be highly appreciated.
Click to expand...
Click to collapse
we are not wizards to know what version of firmware your are using to send you the respective file
tutibreaker said:
we are not wizards to know what version of firmware your are using to send you the respective file
Click to expand...
Click to collapse
Lol I've got miui 13.6 global and miui 12.5 on which the device came with both global and running pixel experience plus so will help man.
There you go Persist data form MIUI 13.0.5ID
tutibreaker said:
There you go Persist data form MIUI 13.0.5ID
Click to expand...
Click to collapse
Have been searching for a long time hopes it fixes my problem tho any way to flash it without wiping data maybe fastboot will work ?
dequr said:
Have been searching for a long time hopes it fixes my problem tho any way to flash it without wiping data maybe fastboot will work ?
Click to expand...
Click to collapse
is a twrp back up
tutibreaker said:
is a twrp back up
Click to expand...
Click to collapse
Using pixel experience can't run twrp or orange fox
tho if anyone has the persist for Model: M2101K7BG AKA Redmi note 10s 6/128 non-NFC please send it here
tutibreaker said:
There you go Persist data form MIUI 13.0.5ID
Click to expand...
Click to collapse
I'm on global and I tried installing this zip but it says that "ERROR installing zip file.
any suggestions on what I could do?
dequr said:
I'm on global and I tried installing this zip but it says that "ERROR installing zip file.
any suggestions on what I could do?
Click to expand...
Click to collapse
you are supposted to extract it to /sdcard/TWRP/BACKUPS/(serialnumber) not flash it
if someone has a persist.img please send it so I can flash it using
./fastboot flash persist location/of/persist.img
would help a lot.
J6idot said:
you are supposted to extract it to /sdcard/TWRP/BACKUPS/(serialnumber) not flash it
Click to expand...
Click to collapse
ok, let me try.
J6idot said:
you are supposted to extract it to /sdcard/TWRP/BACKUPS/(serialnumber) not flash it
Click to expand...
Click to collapse
serialnumber of? I'm glad you're helping me. got it I'm sorry devices serial numb
J6idot said:
you are supposted to extract it to /sdcard/TWRP/BACKUPS/(serialnumber) not flash it
Click to expand...
Click to collapse
Okay so I directly placed its contents in the serialnumber folder and now I restore?
J6idot said:
you are supposted to extract it to /sdcard/TWRP/BACKUPS/(serialnumber) not flash it
Click to expand...
Click to collapse
Okay, so what I did was that I created a persist backup of mine delete its content and then replaced then with the contents of the one @tutibreaker sent me here and now still the compass is constantly ramping up in a loop but slower.
any solutions. I think the device is making its own when it needs it as it asked for unlocking but then changed back to normal without me unlocking it.
dequr said:
Okay, so what I did was that I created a persist backup of mine delete its content and then replaced then with the contents of the one @tutibreaker sent me here and now still the compass is constantly ramping up in a loop but slower.
any solutions. I think the device is making its own when it needs it as it asked for unlocking but then changed back to normal without me unlocking it.
Click to expand...
Click to collapse
are you using miui 13? because i thought miui 13 had an issue with the compass
J6idot said:
are you using miui 13? because i thought miui 13 had an issue with the compass
Click to expand...
Click to collapse
I flashed the persist on miui 13 then from the past some days I've been shifting from miui 12.5 to 13 to custom ROM tho it shouldn't change the persist. And at first the raise to wake-up also glitched but now it's working fine so idk there was an issue of compass it skipped points and jumped to some instant and after I sent it to the company then it came back and was working fine before I bricked it.
Hi,
I have a question about my OnePlus 10 pro. Some guy helped me revive my OnePlus through MSM tool after I bricked it flashing konabess overclock. It got me into crashdump. After a reboot, I got a fingerprint registration problem and wasn't able to register one ever since. As soon as I try to register one, it vibrates and doesn't show up any fingerprint icon at all. What can I do about this??
Phone used to be NE2213.
nothing. you may have lost your persist.img file. i don't believe that is recoverable using MSM. only if you have a backup.
g96818 said:
nothing. you may have lost your persist.img file. i don't believe that is recoverable using MSM. only if you have a backup.
Click to expand...
Click to collapse
What happened to OnePlus seriously never experienced this in all their generation phones until this one. Are there any thing we can do reversing the problem?
NinoLatif said:
What happened to OnePlus seriously never experienced this in all their generation phones until this one. Are there any thing we can do reversing the the problem?
Click to expand...
Click to collapse
It's quite normal for people to lose it. Oneplus was bought out by OPPO. Oneplus as you knew it no longer exists.
g96818 said:
It's quite normal for people to lose it. Oneplus was bought out by OPPO. Oneplus as you knew it no longer exists.
Click to expand...
Click to collapse
NinoLatif said:
Hi,
I have a question about my OnePlus 10 pro. Some guy helped me revive my OnePlus through MSM tool after I bricked it flashing konabess overclock. It got me into crashdump. After a reboot, I got a fingerprint registration problem and wasn't able to register one ever since. As soon as I try to register one, it vibrates and doesn't show up any fingerprint icon at all. What can I do about this??
Phone used to be NE2213.
Click to expand...
Click to collapse
I've had the same thing occur.
Unfortunately there's no recovery so you can't reset file that controls these items.
The only thing you can do now is perform a Local re-flash or update.
Reply to this if you need the files to do so.
Savio Dantes said:
I've had the same thing occur.
Unfortunately there's no recovery so you can't reset file that controls these items.
The only thing you can do now is perform a Local re-flash or update.
Reply to this if you need the files to do so.
Click to expand...
Click to collapse
Thanks for the reply, I'd be glad to, pls let me know, greetings!
you will need a persist.img file from another NE2213(identical storage specifications) to restore the fingerprint.
Cyanide_zh said:
you will need a persist.img file from another NE2213(identical storage specifications) to restore the fingerprint.
Click to expand...
Click to collapse
I'd gladly even pay for one, thanks for the info!
NinoLatif said:
Thanks for the reply, I'd be glad to, pls let me know, greetings!
Click to expand...
Click to collapse
Install this file OP_LocalUpdater_For_Android12.apk
This will allow you to install the update locally.
This is the latest update: NE2215_11_C.21 Stable (full).zip
If for some reason you get stuck in a boot loop follow this guide I wrote:
https://forum.xda-developers.com/t/oneplus-10-pro-android-13-stock-update-rom-root-and-recovery.4525451/post-87806713
I have same problem on my OP9, and I can fix it with this video. Its 100% work, but need to buy calibration tool. I buy this one on the aliexpress.
Savio Dantes said:
Install this file OP_LocalUpdater_For_Android12.apk
This will allow you to install the update locally.
This is the latest update: NE2215_11_C.21 Stable (full).zip
If for some reason you get stuck in a boot loop follow this guide I wrote:
https://forum.xda-developers.com/t/oneplus-10-pro-android-13-stock-update-rom-root-and-recovery.4525451/post-87806713
Click to expand...
Click to collapse
One thing I forgot to mention is that you need to have your ROM version correct
- India ROM
- EU Rom
- World ROM
If the version I've provided ( World ROM) does not work for you, simply download the correct one, and follow the same steps.
NinoLatif said:
I'd gladly even pay for one, thanks for the info!
Click to expand...
Click to collapse
Try the following command: dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img.
Savio Dantes said:
Try the following command: dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img.
Click to expand...
Click to collapse
Thank you brother for the help, nothing works, i have flashed, rolled back and forth every region and update, even flashed manually through fastboot enhanced, still no luck. Never should've flashed konabess, this would never happened
Sounds like its time to perform a:
Google back-up
What's app back-up
Format/Wipe Device
Restore Google and WhatsApp
Savio Dantes said:
Sounds like its time to perform a:
Google back-up
What's app back-up
Format/Wipe Device
Restore Google and WhatsApp
Click to expand...
Click to collapse
Trust me brother, this issue is on a whole other level. I'm sure someone will have the same problem (hope not), and that there will be a fix one day. I also did all on the list here multiple times. I've got to know a guy on Telegram, he says he can fix it. I'll update soon if something good is up. Greetings bro
NinoLatif said:
Trust me brother, this issue is on a whole other level. I'm sure someone will have the same problem (hope not), and that there will be a fix one day. I also did all on the list here multiple times. I've got to know a guy on Telegram, he says he can fix it. I'll update soon of something good is up. Greetings bro
Click to expand...
Click to collapse
Sounds good, let us know if and when you get things sorted.
Savio Dantes said:
Sounds good, let us know if and when you get things sorted.
Click to expand...
Click to collapse
Savio Dantes said:
Sounds good, let us know if and when you get things sorted.
Click to expand...
Click to collapse
I know what the issue is now, the persist.img is corrupted due to konabess overclock installation. This can only be recovered through another OnePlus 10 pro of the same model it's persist.img file you need to extract and flash it on the corrupted OnePlus to get it working again, the guy is going to share me a file soon. As soon as I'll get it, i might be the first one with the file for the OnePlus 10 pro. I'll share it here
NinoLatif said:
Hi,
I have a question about my OnePlus 10 pro. Some guy helped me revive my OnePlus through MSM tool after I bricked it flashing konabess overclock. It got me into crashdump. After a reboot, I got a fingerprint registration problem and wasn't able to register one ever since. As soon as I try to register one, it vibrates and doesn't show up any fingerprint icon at all. What can I do about this??
Phone used to be NE2213.
Click to expand...
Click to collapse
I now read again and find out malfunction of your device is not caused by konabess overclocking but by MSM tool downloading. Konabess overclocking will only modify the boot partition so it has nothing to do with the persist partition. The latter was broken as you downloaded a full rescue package with a invalid persist image.
Cyanide_zh said:
I now read again and find out malfunction of your device is not caused by konabess overclocking but by MSM tool downloading. Konabess overclocking will only modify the boot partition so it has nothing to do with the persist partition. The latter was broken as you downloaded a full rescue package with a invalid persist image.
Click to expand...
Click to collapse
This is the file, I fixed it finally! In case someone needs it
Just like the title, i use the lower version of 10r(12.0) try to flash my ace(13.0).
Then my phone keep reopening, and i couldn't let it into fastboot or recovery.
How i can fix it :<
dipper13579 said:
Just like the title, i use the lower version of 10r(12.0) try to flash my ace(13.0).
Then my phone keep reopening, and i couldn't let it into fastboot or recovery.
How i can fix it :<
Click to expand...
Click to collapse
Were you able to fix it?
You mistake was using OOS12. When you are switching from COS to OOS or vice-versa the version you are switching to must be newer than your current version.
yashaswee1708 said:
Were you able to fix it?
You mistake was using OOS12. When you are switching from COS to OOS or vice-versa the version you are switching to must be newer than your current version.
Click to expand...
Click to collapse
No still in trouble.
I knew it after my terrible tried. how could i fix it out now:<
dipper13579 said:
No still in trouble.
I knew it after my terrible tried. how could i fix it out now:<
Click to expand...
Click to collapse
Able to boot into fastboot?
yashaswee1708 said:
Able to boot into fastboot?
Click to expand...
Click to collapse
no....reboot still.
dipper13579 said:
no....reboot still.
Click to expand...
Click to collapse
Go to a service centre or pay someone to flash the firmware remotely. I know one person through forums only if you want I can share his WhatsApp number
yashaswee1708 said:
Go to a service centre or pay someone to flash the firmware remotely. I know one person through forums only if you want I can share his WhatsApp number
Click to expand...
Click to collapse
i ask some people for help on wechat butz they say it couldn't work without into the fastboot.
dipper13579 said:
i ask some people for help on wechat butz they say it couldn't work without into the fastboot.
Click to expand...
Click to collapse
Exactly. And we also don't have unbrick tool. Go to a service centre of it's there in your city.
c
yashaswee1708 said:
Exactly. And we also don't have unbrick tool. Go to a service centre of it's there in your city.
Click to expand...
Click to collapse
thanks appreciate for help.
dipper13579 said:
i ask some people for help on wechat butz they say it couldn't work without into the fastboot.
Click to expand...
Click to collapse
you need to pay someone to flash for you. I've been there and done that it would cost 30usd ....they got the oppo tools with the factory login to flash for you they don't need it to enter fastboot