Please help with my mobile.
I know XDA where the experts gathered android, even technicians.
My mobile case is hardbrick.
I've done a lot of ways, using almost all flashing software and methods from various sources. But the result is not there.
The position of the phone is only in QDLOADER9008 mode.
But it always fails when flashing.
I'm not sure if my phone has to replace EMMC. And if indeed from your judgment who is adept at saying my emmc is broken, I might believe it.
I need flashing guides that are right and true of you all. Flashing process always runs like normal, but instantly failed not yet finished.
Please help.
Thanks.
Post some screenshots of the error while flashing!
Daluw said:
Please help with my mobile.
I know XDA where the experts gathered android, even technicians.
My mobile case is hardbrick.
I've done a lot of ways, using almost all flashing software and methods from various sources. But the result is not there.
The position of the phone is only in QDLOADER9008 mode.
But it always fails when flashing.
I'm not sure if my phone has to replace EMMC. And if indeed from your judgment who is adept at saying my emmc is broken, I might believe it.
I need flashing guides that are right and true of you all. Flashing process always runs like normal, but instantly failed not yet finished.
Please help.
Thanks.
Click to expand...
Click to collapse
Post some screenshots of the error!
if you use QFIL make sure to put the ROM dir anywhere close to the root of your volume, otherwise you'll get a "sahara protocol error".
meltbanana said:
if you use QFIL make sure to put the ROM dir anywhere close to the root of your volume, otherwise you'll get a "sahara protocol error".
Click to expand...
Click to collapse
What ur mean ? Im not understand, details please..
Sent from my Huawei Y541 using XDA Labs
in QDLOADER9008 (EDL) mode you should use QFIL (qualcomm flash image loader) to restore your ROM but extract it in a folder like D:\santoni or D:\ROM cause QFIL has issues with deeper pathways.
https://www.youtube.com/watch?v=7V-Jf4YzdLs
meltbanana said:
in QDLOADER9008 (EDL) mode you should use QFIL (qualcomm flash image loader) to restore your ROM but extract it in a folder like D:\santoni or D:\ROM cause QFIL has issues with deeper pathways.
https://www.youtube.com/watch?v=7V-Jf4YzdLs
Click to expand...
Click to collapse
Im already try this, but still same..
This may can help
@Rishi said:
Post some screenshots of the error!
Click to expand...
Click to collapse
Done
Sent from my Huawei Y541 using XDA Labs
Daluw said:
View attachment 4498198
Click to expand...
Click to collapse
That's exactly what I told you - the path C:\Program Files (x86)\Qualcomm\QPST\bin is too long,
extract your rom into C:\Temp or something closer to the root of your volume or else you'll get the sahara firehose fail error.
For example I have D:\santoni\santoni_global_images_V8.2.10.0.MAMMIEA
... and don't pick the images folder, QFIL needs the batch files, just use flash_all.bat.
meltbanana said:
That's exactly what I told you - the path C:\Program Files (x86)\Qualcomm\QPST\bin is too long,
extract your rom into C:\Temp or something closer to the root of your volume or else you'll get the sahara firehose fail error.
For example I have D:\santoni\santoni_global_images_V8.2.10.0.MAMMIEA
... and don't pick the images folder, QFIL needs the batch files, just use flash_all.bat.
Click to expand...
Click to collapse
This photo just example, im already doing, like ur talk to me..but still same, thanks Bro :laugh:
What u mean QFIL need FLASH ALL BAT ? thats for Miflash, right ? QFIL just need Patch, Raw, Firehose. Right ? Tell me more details Bro..
Sent from my Huawei Y541 using XDA Labs
that worked for me
hope it helps
Daluw said:
Done
Sent from my Huawei Y541 using XDA Labs
Click to expand...
Click to collapse
After seeing your screenshots, I would say you are doing wrong bro!
Just download the latest stock rom & extract it on the Desktop or in other drive. Then open Mi Flash Tool and browse for the folder of the extracted rom. After that connect your phone in edl mode (I mean download mode) & click refresh on the Mi Flash Tool. Wait for a sec and click flash!
Or just head on to Youtube bro!
:fingers-crossed:
Thanks!
@Rishi said:
After seeing your screenshots, I would say you are doing wrong bro!
Just download the latest stock rom & extract it on the Desktop or in other drive. Then open Mi Flash Tool and browse for the folder of the extracted rom. After that connect your phone in edl mode (I mean download mode) & click refresh on the Mi Flash Tool. Wait for a sec and click flash!
Or just head on to Youtube bro!
:fingers-crossed:
Thanks!
Click to expand...
Click to collapse
Thanks...but not help..
My case not simple like ur think...
Do u know about TOOL STUDIO ? I need 2 file for SANTONI to flash my phone with this Software.
In TOOL STUDIO, need 2 important file, MPRG_8937.mbn and 8937_msimage.mbn
Can u give me this file ??
Sent from my Huawei Y541 using XDA Labs
Daluw said:
Thanks...but not help..
My case not simple like ur think...
Do u know about TOOL STUDIO ? I need 2 file for SANTONI to flash my phone with this Software.
In TOOL STUDIO, need 2 important file, MPRG_8937.mbn and 8937_msimage.mbn
Can u give me this file ??
Sent from my Huawei Y541 using XDA Labs
Click to expand...
Click to collapse
Ok, I will try bro!
Edit: You can try this https://www.aryk.tech/2016/12/how-to-create-msimagembn-file-flashable.html
@Rishi said:
Ok, I will try bro!
Edit: You can try this https://www.aryk.tech/2016/12/how-to-create-msimagembn-file-flashable.html
Click to expand...
Click to collapse
Give me some file if u done try this tutorial..
No help Bro, no file msm created, like others comment on ur link. Look Comment by user on that link...u have ?
Sent from my Huawei Y541 using XDA Labs
I guess you opened back case and test point method to get qdloader mode.
If it was in warranty mi center would have repaired it without any charge(i got mine in 2nd sale and i still have warranty so i guess you may have too)
Remember you can have many excuses of claiming warranty of bricked device.
But as u opened it warranty is no more.
Sometimes its simple but we make it complex.
You could try fastboot rom and mi flash tool..
gursewak.10 said:
I guess you opened back case and test point method to get qdloader mode.
If it was in warranty mi center would have repaired it without any charge(i got mine in 2nd sale and i still have warranty so i guess you may have too)
Remember you can have many excuses of claiming warranty of bricked device.
But as u opened it warranty is no more.
Sometimes its simple but we make it complex.
You could try fastboot rom and mi flash tool..
Click to expand...
Click to collapse
Why im post to XDA if u recommended me to simple solution, give to service center ???
I think in this FORUM, all people got many solution..from many user Bro...
Thanks ur respon..
Sorry my bad english...
Sent from my Huawei Y541 using XDA Labs
Daluw said:
Why im post to XDA if u recommended me to simple solution, give to service center ???
I think in this FORUM, all people got many solution..from many user Bro...
Thanks ur respon..
Sorry my bad english...
Sent from my Huawei Y541 using XDA Labs
Click to expand...
Click to collapse
Ok
Did you tried fastboot rom with mi flash.
Rather than opening case you should have used deep flash cable which worked for redmi 3s. I used fastboot rom with mi flash tool.
gursewak.10 said:
Ok
Did you tried fastboot rom with mi flash.
Rather than opening case you should have used deep flash cable which worked for redmi 3s. I used fastboot rom with mi flash tool.
Click to expand...
Click to collapse
Give me right tutorial making deep flash cable..
Sent from my Huawei Y541 using XDA Labs
Daluw said:
Give me some file if u done try this tutorial..
No help Bro, no file msm created, like others comment on ur link. Look Comment by user on that link...u have ?
Sent from my Huawei Y541 using XDA Labs
Click to expand...
Click to collapse
Sorry bro, I don't have those files!
Even I got the same error like you after I tried.
Anyway, I will surely look into this further & will be back if I find any solution.
Btw, have you tried the test point method?
Related
I have a Samsung device Galaxy SIII Mini (GT-I 8190)
Accidentally installed a version that was not his, and knocked on the recovery, and now my device does not get any updates, not through the OTA and automatic updates, simply the recovery screwed.
I tried to change version, and restore the original version and it did not help ..
By the way, every time a version I do, he gets stuck, and I must do him param then he recovers back. No param is stuck in the front window.
You know how you fix it please?
I dont think that any update was published.
Sent from my GT-I8190 using xda app-developers app
.
ppero196 said:
I dont think that any update was published.
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Well, what shall I do?
Can fix this?
Maybe flash an official firmware from the start and do a hard reset (after the flashing).
That should definitely install the official recovery again!
quendil said:
Maybe flash an official firmware from the start and do a hard reset (after the flashing).
That should definitely install the official recovery again!
Click to expand...
Click to collapse
How do I do this?
salah_nahi said:
How do I do this?
Click to expand...
Click to collapse
You can download a new firmware from sammobile.com and then use the following guide for instructions:
http://www.tsar3000.com/Joomla/inde...and-stock-firmware&catid=57:how-to&Itemid=104
I tried what you said .. It did not help .. Still in the same situation
Sent from my GT-I8190 using xda app-developers app
salah_nahi said:
I tried what you said .. It did not help .. Still in the same situation
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Was your flash succesful and did you do a hard reset after the flash?
Can you describe us EXACTLY (by letter) what your device does?
.
quendil said:
Was your flash succesful and did you do a hard reset after the flash?
Can you describe us EXACTLY (by letter) what your device does?
Click to expand...
Click to collapse
I did install the original version, the installation is completed to the end ..
After doing the installation device stuck, I could not do anything to him, not a hard reset, or anything that is stuck and went to recovery.
The device remains stuck until I did a setup to PARAM
Well, the way I understand I need to Install a new ClockworkMod Recovery..
Where can I get this file please?
salah_nahi said:
Well, the way I understand I need to Install a new ClockworkMod Recovery..
Where can I get this file please?
Click to expand...
Click to collapse
There is no cwm recovery for our phone yet.
quendil said:
You can download a new firmware from sammobile.com and then use the following guide for instructions:
http://www.tsar3000.com/Joomla/inde...and-stock-firmware&catid=57:how-to&Itemid=104
Click to expand...
Click to collapse
quendil said:
There is no cwm recovery for our phone yet.
Click to expand...
Click to collapse
How I saw that s iii mini and the sii is the same system and the same processor and the same data to both devices,
what do you say? I can try the cwm recovery of the S II on my device?
salah_nahi said:
How I saw that s iii mini and the sii is the same system and the same processor and the same data to both devices,
what do you say? I can try the cwm recovery of the S II on my device?
Click to expand...
Click to collapse
please dont do it. you risk bricking your phpne.
quendil said:
please dont do it. you risk bricking your phpne.
Click to expand...
Click to collapse
Well then I will not do anything,
I understand that I have to wait until a CWM to my device ..
Right?
salah_nahi said:
Well then I will not do anything,
I understand that I have to wait until a CWM to my device ..
Right?
Click to expand...
Click to collapse
yes mate as we all do.
there is a guide for building cwm in xda university
if i get time i might study a bit for it.
quendil said:
yes mate as we all do.
there is a guide for building cwm in xda university
if i get time i might study a bit for it.
Click to expand...
Click to collapse
So come on, when you have something suitable for my device do not forget me ..
And really I thank you for helping me.
Thanks man :good:
salah_nahi said:
I did install the original version, the installation is completed to the end ..
After doing the installation device stuck, I could not do anything to him, not a hard reset, or anything that is stuck and went to recovery.
The device remains stuck until I did a setup to PARAM
Click to expand...
Click to collapse
sorry my english is not so good
I have exactly the same problem I do not come purely from recopvery menu
already tried everything from nor even with ADB hardreset not one time with the code * # 87976633 #. if I pull on it ne other firmware I've also the problem that the programs I had before the bottles are then on it is still there or twice since
there may be the possibility to erase the phone completely, format as in the PC hard drive???
or what can I do otherwise??
[FONT="<font><font>Arial Black</font></font>"]I needed help penetrate[/FONT]
jony1512 said:
sorry my english is not so good
I have exactly the same problem I do not come purely from recopvery menu
already tried everything from nor even with ADB hardreset not one time with the code * # 87976633 #. if I pull on it ne other firmware I've also the problem that the programs I had before the bottles are then on it is still there or twice since
there may be the possibility to erase the phone completely, format as in the PC hard drive???
or what can I do otherwise??
[FONT="<font><font>Arial Black</font></font>"]I needed help penetrate[/FONT]
Click to expand...
Click to collapse
Probably your problem is like mine, you have the recovery fails, and you can not do anything, that recovery is available now, so have to wait
I used the Recovery-Toolkit and than came this screen.
Look here : https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Dont work(
persa2011 said:
Dont work(
Click to expand...
Click to collapse
What your device ? 3 or 3t ?
Try mega unbrick ,
Always work for me ,
persa2011 said:
I used the Recovery-Toolkit and than came this screen.
Click to expand...
Click to collapse
Don't you think that a little more information would be helpful? For example what's your device, what did you exactly do, why does the solution in "Mega unbrick guide"-Thread not work (like you said). We are no magicians here, we need information to be able to help you
persa2011 said:
I used the Recovery-Toolkit and than came this screen.
Click to expand...
Click to collapse
did you open Recovery Toolkit as administration?
Its never bricked, i have flashed the wrong things before and screwed everything up just like you have and seen that exact same screen. You need to keep researching and reading. There never fully bricked.
persa2011 said:
I used the Recovery-Toolkit and than came this screen.
Click to expand...
Click to collapse
This picture shows you have to use in brick method 2 by using unbrick tool full.zip if you have one plus 3.
i know, but what can i do?
rob rich said:
Don't you think that a little more information would be helpful? For example what's your device, what did you exactly do, why does the solution in "Mega unbrick guide"-Thread not work (like you said). We are no magicians here, we need information to be able to help you
Click to expand...
Click to collapse
I write nevertheless here in the oneplus 3 forum or, so which telephone I then?
persa2011 said:
I write nevertheless here in the oneplus 3 forum or, so which telephone I then?
Click to expand...
Click to collapse
1. There were others already posting here, which had a 3T, that's why I'm asking.
2. Still no answers from you to the questions we have asked. No infos = no help
RKBD said:
did you open Recovery Toolkit as administration?
Click to expand...
Click to collapse
yes
I have TWRP installed is this helpful?
persa2011 said:
I have TWRP installed is this helpful?
Click to expand...
Click to collapse
Well, can you boot to it? If you can, mount USB, copy a ROM on the phone and try reflashing it.
If all else fails, boot to fastboot and sideload a whole new OxygenOS ROM.
robogo1982 said:
Well, can you boot to it? If you can, mount USB, copy a ROM on the phone and try reflashing it.
If all else fails, boot to fastboot and sideload a whole new OxygenOS ROM.
Click to expand...
Click to collapse
Can you tell me how can i flash a Oxygen-Rom with fastboot?
persa2011 said:
I used the Recovery-Toolkit and than came this screen.
Click to expand...
Click to collapse
Follow this
ashokmor007 said:
Follow this
Click to expand...
Click to collapse
didnt work, the same screen as in the picture.
Can you share some screen shot of the device or msg me on fb page check video description
thank you. I'll be back on Facebook.
Something is wrong with the drivers in your PC. This is exactly what I got when u did not follow the driver part of the guide.
Good day! Realme X2 Pro brick. Need files to restore the system. Only works in mode EDL. :crying: Firmware needed for the program QFIL. How to make the necessary files for this program?(QFIL) Or can someone share a backup from the program QFIL, so that they can restore their system?
chronos1831 said:
Good day! Realme X2 Pro brick. Need files to restore the system. Only works in mode EDL. :crying: Firmware needed for the program QFIL. How to make the necessary files for this program?(QFIL) Or can someone share a backup from the program QFIL, so that they can restore their system?
Click to expand...
Click to collapse
I'm in the same boat man. I don't know how to get it reflashed either.
Im bricked too. Becare if you want to lock bootloader the system must be all the same in default, one app you delete or change will cause soft-bricked...
necsynx said:
Im bricked too. Becare if you want to lock bootloader the system must be all the same in default, one app you delete or change will cause soft-bricked...
Click to expand...
Click to collapse
No. Sew on a clean Rom. There, all programs will be installed from the firmware and everything will be fine. Maybe someone will backup through programs Qfil. And then we can restore and reflash the device. Find file for MsmDownloadTool in the format .ofp(
chronos1831 said:
No. Sew on a clean Rom. There, all programs will be installed from the firmware and everything will be fine. Maybe someone will backup through programs Qfil. And then we can restore and reflash the device. Find file for MsmDownloadTool in the format .ofp(
Click to expand...
Click to collapse
Would be a godsend if someone could do this. Seriously man.
Lanes100 said:
Would be a godsend if someone could do this. Seriously man.
Click to expand...
Click to collapse
I will look for someone who can share their backup to restore the device. I'll take it to the official service this weekend. Let's see if they can restore the device there
chronos1831 said:
I will look for someone who can share their backup to restore the device. I'll take it to the official service this weekend. Let's see if they can restore the device there
Click to expand...
Click to collapse
see if they will share the tool and stuff they use to do that. I am located in the US and have no official service place to take it to so if you could manage to get that by sweet talking the service people that would be awesome for the community.
:good:
We were unable to recover. Failed to upload last file to device
I probably found an opportunity to restore the device.
https://drive.google.com/file/d/1dmJXCHReL0z38eZIkqK_MG4g2MfvD36y/view
for MsmDownloadTool. Who can try it out? My device is in service and there is no way to check
chronos1831 said:
I probably found an opportunity to restore the device.
https://drive.google.com/file/d/1dmJXCHReL0z38eZIkqK_MG4g2MfvD36y/view
for MsmDownloadTool. Who can try it out? My device is in service and there is no way to check
Click to expand...
Click to collapse
Please help me with this firmware. What data do you need to enter to run?
chronos1831 said:
Please help me with this firmware. What data do you need to enter to run?
Click to expand...
Click to collapse
This is not an ofp file.
necsynx said:
This is not an ofp file.
Click to expand...
Click to collapse
ofp and msm are in the archive by reference. But there you need an authorized account to run the application
Has anyone had any luck with unbricking their phone when in EDL mode? im in the same boat as well and i cant seem to find the correct firmware to use with qfil tool etc.
joey2177 said:
Has anyone had any luck with unbricking their phone when in EDL mode? im in the same boat as well and i cant seem to find the correct firmware to use with qfil tool etc.
Click to expand...
Click to collapse
not yet(may soon appear
How do you access edl mode on this phone?
joey2177 said:
Has anyone had any luck with unbricking their phone when in EDL mode? im in the same boat as well and i cant seem to find the correct firmware to use with qfil tool etc.
Click to expand...
Click to collapse
you found it?
hey guys!
I think I almost have it, but I need the scatter file, any of you have it generated?
Guys have cn version?
Wont installing a11 ota ozip via twrpcnen work?
striderdon37 said:
Guys have cn version?
Wont installing a11 ota ozip via twrpcnen work?
Click to expand...
Click to collapse
it won't work, because it doesn't let fastboot or recovery go into EDL alone
---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------
chronos1831 said:
I probably found an opportunity to restore the device.
https://drive.google.com/file/d/1dmJXCHReL0z38eZIkqK_MG4g2MfvD36y/view
for MsmDownloadTool. Who can try it out? My device is in service and there is no way to check
Click to expand...
Click to collapse
HI, please can you autoriced me? for a test my gmail is [email protected]
Isavar said:
it won't work, because it doesn't let fastboot or recovery go into EDL alone
---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------
HI, please can you autoriced me? for a test my gmail is [email protected]
Click to expand...
Click to collapse
I already said that it only loads EDL. And looking for recovery methods only for this mode
Greetings everyone,
I'm pretty new here to XDA and really hope you can help me out with this.
I've had my Redmi Note 10S for about a year now and well I think Xiaomi hates me now.
Recently when I went to Pisa for a holiday, my phone bricked after updating to MIUI 13.
It's stuck at the Redmi logo and will only lower brightness a little bit after it then reboot, recovery mode works but if I try reboot it's the same stuff and it won't even boot into safe mode.
I haven't modded the phone in any way but yea it literally bricked after the first reboot.
I have no backups (both Mi Cloud and GDrive and no local) but really need to try to copy files from rom to pc.
There's some important stuff that I've stored as screenshots and really need to get em.
There's a few things I want to make clear though:
-Again, phone was not modded in any way and no root/custom rom was on it
-Only updated through the actual GUI and downloaded the update like normal
-USB Debugging is enabled
-Bootloader is not enabled
-Only device with Debug permissions with my phone is a goddamn Oculus Quest 1 (don't ask me why but yea it's the only one that I had connected with it)
If someone knows in any way if I can recover my stuff through ADB on an android like device (my Quest 1) lemme know, if there's other ways please lemme know as well.
If there's no way that I can do it...well I'll just hope that wiping it fixes the issue.
Already tried contacting a Mi Authorized Center and the Xiaomi Italian Phone Number, they both said they won't be able to legally recover my data due to privacy reasons and gave me the middle finger by saying I should have paid for storage on Mi Cloud (outside of one guy on Live Chat that was actually very helpful even tho he said basically the same thing).
Sorry for the long post but please I need help.
Thanks in advance
you can just flash the fastboot firmware with miflashtool and select the option to save user data and the device wil get the new firmware without lose your valuable data in the process
tutibreaker said:
you can just flash the fastboot firmware with miflashtool and select the option to save user data and the device wil get the new firmware without lose your valuable data in the process
Click to expand...
Click to collapse
wait really?
salvo91able said:
wait really?
Click to expand...
Click to collapse
yup
salvo91able said:
wait really?
Click to expand...
Click to collapse
oh boi I'll definately try it out
can you link me to the actual program website?
all I'm seeing is fake mirror websites
also one last thing is it safe even if I have the bootloader disabled?
yup, is safe
Mi forum guide to flash
tutibreaker said:
yup, is safe
Mi forum guide to flash
Click to expand...
Click to collapse
ok thanks a lot, can you link me a download of the tool?
salvo91able said:
ok thanks a lot, can you link me a download of the tool?
Click to expand...
Click to collapse
click the blue link ._.
tutibreaker said:
click the blue link ._.
Click to expand...
Click to collapse
Ok thanks I downloaded everything and will do it after I come back from work.
One last thing, I know I'm being paranoide but just wanted to ask this as well.
Will this delete the android/media folder?
Since there's like my WhatsApp related stuff there.
tutibreaker said:
click the blue link ._.
Click to expand...
Click to collapse
Help I tried to click the "unlock" button on the website but It just downloads a file that's 0 bytes and doesn't do anything
Did it work
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