Hi Guys,
a german Forum advised me to ask here because, here are the experts. So sorry for my Basic englisch, but have a big problem.
My problem:
I got a Huawei Nova Youth as a gift. This is explicitly offered in the Chinese market. After some fumbling I have been able to change the language to German. However, the keyboard still partially takes false inputs. In addition, the Play and App store does not work. Of course, many other apps will be blocked, not to mention the Bloodware.
It is the model WAS-AL00. I now know that it is sold here as P10 lite. I did not find out how to install a European OS or a custom OS (Lineage). The support say only blah blah does not work, blah blah license problems ... Can someone please give useful information about my problem?
If more information is needed, I'll give it to you. I have always been Windows Phone users so far. So please apologizes if I do not understand all Android technical Terms.
thx
Hi, you need
backup alldata
unlock bootloader
install twrp
service rom: b182(ds) or b183(ss),
oeminfo: c432ds or ss
adb drivers
sdcard 8gb or more
links:
adb: https://forum.xda-developers.com/showthread.php?t=2588979
oeminfo: https://www.youtube.com/watch?v=I2DeM1pCcwo
service rom: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
twrp: https://forum.xda-developers.com/p10-lite/development/beta-t3619496
info:
imei: open settings, go to about phone and look if there one or two imei
oem unlock: press several times till enable in build number(developer settings), back to settings and open developer options scroll to see oem unlock and enable
twrp1: fastboot flash recovery recovery.img(open cmd c: )
sdcard1: create dload folder
insert sdcard:
servicerom: extract the download file, open folders untill you see update.app and folders, then copy all to dload folder in your sdcard
oeminfo: extract
twrp2: open twrp with vol+ + power, backup only oeminfo in sdcard(copy to safe place), then copy the downloaded oeminfo to the backup folder and replace oeminfo then press restore(dont reboot, poweroff only)
install: press vol+/- and power buttons untill update starts.
foliaje said:
Hi, you need
backup alldata
unlock bootloader
install twrp
service rom: b182(ds) or b183(ss),
oeminfo: c432ds or ss
adb drivers
sdcard 8gb or more
links:
adb: https://forum.xda-developers.com/showthread.php?t=2588979
oeminfo: https://www.youtube.com/watch?v=I2DeM1pCcwo
service rom: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
twrp: https://forum.xda-developers.com/p10-lite/development/beta-t3619496
info:
imei: open settings, go to about phone and look if there one or two imei
oem unlock: press several times till enable in build number(developer settings), back to settings and open developer options scroll to see oem unlock and enable
twrp1: fastboot flash recovery recovery.img(open cmd c: )
sdcard1: create dload folder
insert sdcard:
servicerom: extract the download file, open folders untill you see update.app and folders, then copy all to dload folder in your sdcard
oeminfo: extract
twrp2: open twrp with vol+ + power, backup only oeminfo in sdcard(copy to safe place), then copy the downloaded oeminfo to the backup folder and replace oeminfo then press restore(dont reboot, poweroff only)
install: press vol+/- and power buttons untill update starts.
Click to expand...
Click to collapse
I tryed to do this.
I entered the developer steeings. 2 points are not present oem unlock and root access are both not seen. I tryed to install app store for twrp but it is blocked. If I try to enter the fastboot option with restart from smartphone, it is blocked. So I think the main problem is to get twrp to load new image. I tryed to install the with apk file directly and via huawei store. Both was not possible. Any Idea? Backup is not necessary. I never worked with the smartphone.
Update:
It was possible to download me.twrp.twrpapp-26.apk and copy on phone. Now he ask for device. Is the P9 plus the best choise?
ok you need first unlock bootloader:
register here with your phone(faster with it) or with email: https://emui.huawei.com/en/plugin/unlock/detail
then:
1º Download serviceRom(b182 or b183) on your pc and extract it, Same thing for oeminfo c432(ds or ss) and twrp.
2º Once you get unlock code open cmd(type cd c: /users/yourname/adb(more or less)), type fastboot oem unlock code , press on the screen and reboot wait to finish.
3º Move twrp image(extract) to c:/adb, type fastboot flash recovery recovery.img, type fastboot reboot and press vol+ till erecovery screen, poweroff and unplug then vol+ and power button(briefly stop pressing power button)
4º insert your sdcard on laptop and create dload folder in it, then copy update.app and folders from dload folder of downloaded service rom.
5º in twrp press backup button select sdcard storage and backup only oeminfo(copy to safe place), with downloaded oeminfo copy and replace oeminfo then restore.
6ºpoweroff and unplug, then press vol+- and power button untill update starts, if all goes ok should reboot.
at first big thanks foliaje. I am very happy for your fast answers. I tryed today the unblock page from hauwei. There was foolowing Problem.
1. I registered an account via Smartphone. Most of informations was chinese.
2. Change lange was not possible - same in PC browser. Seems like fix Region.
3. delete account and create new on PC. Change language to german was possible.
4. Try to login to unblock Website was not possible - Change Password Shows failure Email or account not present ....
Is it necessary to great account on Smartphone with fixed Region again and use this account for unblock?
Further *adb devices* shows an ID and unautorised device. Is that right?
Kerberos79 said:
at first big thanks foliaje. I am very happy for your fast answers. I tryed today the unblock page from hauwei. There was foolowing Problem.
1. I registered an account via Smartphone. Most of informations was chinese.
2. Change lange was not possible - same in PC browser. Seems like fix Region.
3. delete account and create new on PC. Change language to german was possible.
4. Try to login to unblock Website was not possible - Change Password Shows failure Email or account not present ....
Is it necessary to great account on Smartphone with fixed Region again and use this account for unblock?
Further *adb devices* shows an ID and unautorised device. Is that right?
Click to expand...
Click to collapse
try now on your pc, i change hwid5 to hwid7(link below), logged without problems :good:
for adb/fastboot devices Works correctly enable usb debugging and press authorize
https://hwid7.vmall.com/CAS/portal/userRegister/regbyemail.html?reqClientType=2023&loginChannel=22000000&countryCode=es&loginUrl=https%3A%2F%2Fhwid7.vmall.com%2FCAS%2Fportal%2Flogin.html&service=https%3A%2F%2Femui.huawei.com%2Fen%2Fplugin%2Fhwlogin%2Fvalidate%3Fru%3D%252F%252Femui.huawei.com%252Fen%252Fplugin%252Funlock%252Findex&lang=en-us&themeName=red
I think I have to wait 2 weeks
*The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.*
Kerberos79 said:
I think I have to wait 2 weeks
*The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.*
Click to expand...
Click to collapse
have you tried deleting account since huawei id and creating one on your pc with the link from above?
yes I greated a new account with your link with other email adress.
Any progress with your p10lite?
I tryed it now and still same issue. this time I tryed with meid other time with emei.
https://www.pic-upload.de/view-34293605/unlockfehler.jpg.html
same message with both emei
Hi, I have this problem months ago, (I have a Nova Youth as gift too) and I solve it installing this app: gmsinstaller.apk or can use Googleinstaller.apk (just google it) and you dont need the root, it install the play services from Google and then you can install any app from the play store, sorry cause I dont have the apps to share but there is easy to find.
greetings from México!
Hi!
i create a software to fix Balong issue after flashing a ROM.
Download the zip, extract the folder then only need to follow the steps in software!
Check the pictures bellow!
If fails check if cust image is properly installed before execute the software again.
Tell me if worked for you!
.
Thanks.
I've installed TWRP 3.1.1-0, but when I use your software it says "error: no devices/emulators found", even if I put the correct cust path
persona78 said:
Hi!
i create a software to fix Balong issue after flashing a ROM.
Download the zip, extract the folder then only need to follow the steps in software!
Check the pictures bellow!
If fails check if cust image is properly installed before execute the software again.
Tell me if worked for you!
.
Click to expand...
Click to collapse
Hi
After an update (official!) I re-encountered BALONG. After using your marvelous tool, it worked again, but there's no need to reset device (as written on CMD).
In addition, for the ones that get the error "no device attached" or something similar, you've only to reboot to TWRP, connect the phone to Windows and press Win+X, click on "device manager", look for "android device" or something similar. Right click on it and select "update driver", click the second option and than select that you already have the CD driver. You'll see a list: select "ADB composite device" and than finish: you've done!
Ah, I was about to forget: thank you!
Regards,
F
fixed
Hi.
Thanks for fast answer. I could fix the problem.
I downloaded the EMUI 3.1 as Magyar Telekom firmware from an arabic server cause ru huawei servers doesnt work lol. So I downloaded it I extracted boot, recovery, system, cust img files from UPDATE.APP with Huawei AppImage Extractor application. I flashed these with fastboot (Not TWRP, not huawei recovery). Fastboot from computer. Ok. But at the moment SIM does not work. I upgraded the system from Huawei update from settings (not recovery, system settings). After update the ROM and SIM is work perfectly.
Btw thanks your answer, topices too. This is a big help from you.
Have a nice day, Balázs.
How Can i use it for Meanaf Localization ????
How Can i use it for Meanaf Localization ????
@persona78
can you provide me Tool To fix Balong
Countryakistan
Mobile:ALE-L21
ROM:C185
Hello thanks for creating such tool
I've tried to use it but i get this error after TWRP boot :
mount: No such file or directory
mkdir: '/cust/hw': No such file or directory
ln: cannot create symbolic link from '/cust/hw/eu' to '/cust/hw/meafnaf': No such file or directory
Is there any solution for this?
-Mouhammad said:
Hello thanks for creating such tool
I've tried to use it but i get this error after TWRP boot :
mount: No such file or directory
mkdir: '/cust/hw': No such file or directory
ln: cannot create symbolic link from '/cust/hw/eu' to '/cust/hw/meafnaf': No such file or directory
Is there any solution for this?
Click to expand...
Click to collapse
Which Cust Path Do you Want?
hw/meafnaf?
MohmmadUzairKhan said:
Which Cust Path Do you Want?
hw/meafnaf?
Click to expand...
Click to collapse
The program detected this path : cust/hw/meanfaf
Is this what you mean?
-Mouhammad said:
The program detected this path : cust/hw/meanfaf
Is this what you mean?
Click to expand...
Click to collapse
What Do You Want?
hw/eu?
MohmmadUzairKhan said:
What Do You Want?
hw/eu?
Click to expand...
Click to collapse
Do you know what cuases this error?
Thank you its working excellent . And wipe is not needed. Tnx again ?
pls say me
how can i fix it with opened bootloader? must i flash cast?
Doesn't work. Did everything by the instructions. Twice.
Disclaimer :
I'm not responsible for bricked devices, dead SD cards. This guide have not tested by anyone yet and because of that have a high chance to damage your device .Please think twice before deciding to do this guide !!!
Hello all, I was successful to extract the ofp firmware for the CN and GLOBAL version. The firmware is kind of QFIL based firmware and include patch0.xml , rawprogram0.xml , prog_firehose_ddr.elf that can be loaded on the Qualcomm QFIL tool for flashing a stock rom on EDL mode .
I do not have this phone yet so this is not tested by me but it should work .
This should work on bricked devices with locked bootloader .
This is not a full guide as I haven't tested it yet, but I will share you of my idea. I suggest to not try this if your not in hard brick and the bootloder is not locked .
Warning- This process will wipe your internal storage .
1. Extract the firmware and the 1-Qualcomm USB Driver + QFIL.7z.
2. You should install the Qualcomm USB Driver
3. Install QPST.2.7.480 , move the firmware to C:\Program Files (x86)\Qualcomm\QPST\bin .
4. Run as administration the QFIL software ,it found on C:\Program Files (x86)\Qualcomm\QPST\bin .
5. Click on the Configuration tab and then on the FireHose configuration .
6. Click on the Device Type and choose ufs .
7. Tick the "Reset after Download" and press OK.
8. Tick the flat boot circle option .
9. Click Browse on the Programmer Path and choose prog_firehose_ddr.elf in the firmware file .
10. Click Load XML and choose "rawprogram0.xml" and then choose "patch0.xml" .
Open windows device manger, boot you phone to EDL by connecting a cable to you PC and then press and hold power bottom and volume + bottom .You should see Qualcomm HS-USB QDLoader 9008, It is really important to be on QDLoader 9008 .Do not try to proceed to 11 if it does not show as QDLoader 9008 .
11. you will see the Port on the QFIL software and then choose Download .
Download -
Qualcomm USB Driver + QFIL - https://mega.nz/file/pU8FRILJ#y54f4lnq6p3T7TCITGyWRw0Kuf4ymgOt4srQ654NqUo
Extracted RMX1931EX_11_A.09 OFP (Global firmware) - https://mega.nz/file/YQ80wSwB#wflYZ-hI5O96QjTq4oc4pnovn6UoAtry2lHn7ThmbLo
CHECK MD5 !!! - 58A5C6D75787029B664FD5583F265872
Extracted RMX1931_11_A.11 OFP (CN firmware) - https://mega.nz/file/lMMlQK4K#bOCrQrg7tkKj2n6VNhS__4bBQw1RdsxTSI5XrzRpMG0
CHECK MD5 !!! - A0CCED006DF8FC0B06B0669A8325883F
Please download the firmware according to your realme x2 pro model, This probably wont work and may damage your device if you have a CN model and try flash a EU firmware and the opposite EU model and try flash a CN firmware .
UPDATE-
After long testing it seem that we can not write to or read from this phone without the realme tool, It must have a special code . I will stop searching for a way because it seems impossible without the Realme tool.
Thanks to @shilpakar7, @Designguru and @iamkgehlot for testing tools and files for many hours .
English is not my native language, please excuse any errors on my part.
Reserved
Fingers crossed ? if it works, it's going to help alot of folks!
luisarriaga said:
Fingers crossed ? if it works, it's going to help alot of folks!
Click to expand...
Click to collapse
Yes I know, It also will remove the fear of hard brick when locking the bootloder .
Furthermore if it will work for the realme x2 pro, it will work on many Realme devices that have a snapdragon CPU including the realme x2 .I just need to extract the ofp firmware of each device .
Yes absolutely! It's the only android smartphone I never unlocked the bootloader, first of all because of loosing FP if you install twrp, and there's the risk of relocking it. Let's wait for some feedback ?
Here is what I have currently
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Designguru said:
Here is what I have currently
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Click to expand...
Click to collapse
Try to immediately start flashing(choose Download ) after you have put your phone into EDL mode .Also does you see Qualcomm HS-USB QDLoader 9008 on windows device manager ?
or965 said:
Try to immediately start flashing(choose Download ) after you have put your phone into EDL mode .Also does you see Qualcomm HS-USB QDLoader 9008 on windows device manager ?
Click to expand...
Click to collapse
Here is another problem I'm seeing. I put all the files in C:\ as per your instructions. When I download from QFIL, it shows Working Folder is C:\Users\<username>\AppData\Roaming\Qualcomm\QFIL\COMPORT_3. I copied over all the files into this folder as well and am seeing the errors posted earlier.
Yes I'm showing HS-USB QDLoader 9008 (COM#)
Designguru said:
Here is another problem I'm seeing. I put all the files in C:\ as per your instructions. When I download from QFIL, it shows Working Folder is C:\Users\<username>\AppData\Roaming\Qualcomm\QFIL\COMPORT_3. I copied over all the files into this folder as well and am seeing the errors posted earlier.
Yes I'm showing HS-USB QDLoader 9008 (COM#)
Click to expand...
Click to collapse
Try uninstall the qfil and install this version https://mega.nz/file/hFdDDKBK#szUu2TqPdd6VO_XLKfYIu9pJ6yYT0LbaeZqTaIEQ8Fo
put the firmware on C:\Program Files (x86)\Qualcomm\QPST\bin
or965 said:
Try uninstall the qfil and install this version https://mega.nz/file/hFdDDKBK#szUu2TqPdd6VO_XLKfYIu9pJ6yYT0LbaeZqTaIEQ8Fo
put the firmware on C:\Program Files (x86)\Qualcomm\QPST\bin
Click to expand...
Click to collapse
Done. Here is where it fails now
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Verifying signature failed with 3" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
19:17:51: DEBUG: XML FILE (115 bytes): CharsInBuffer=315-115=200
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Authentication of signed hash failed 0" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
19:17:51: DEBUG: XML FILE (94 bytes): CharsInBuffer=200-94=106
-------------------------------------------------------------------------------------------
Designguru said:
Done. Here is where it fails now
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Verifying signature failed with 3" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
19:17:51: DEBUG: XML FILE (115 bytes): CharsInBuffer=315-115=200
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Authentication of signed hash failed 0" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
19:17:51: DEBUG: XML FILE (94 bytes): CharsInBuffer=200-94=106
-------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Maybe we should try to use other software to flash ,try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash ,if you have an error, try to go to the firmware and change setting.xml name to flash_local.xml and try to flash again .
or965 said:
Maybe we should try to use other software to flash ,try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash ,if you have an error, try to go to the firmware and change setting.xml name to flash_local.xml and try to flash again .
Click to expand...
Click to collapse
When I hit flash, here is what I get under status
"The filename,directory name, or volume label syntax is incorrect (0x8007007b: Open programmer "MPRG*hex")
what about using qpst tool as mentioned in https://www.getdroidtips.com/stock-rom-realme-x2-pro/ Method 3. The above mentioned url contains guide for chinese ROM but since you have ofp firmware for global version. Will this method work?
it fails during dowload process. I have attached the log.
Total to be tansferd with <program> or <read> is 8.98 GB
09:09:35: INFO: Sending <configure>
09:09:35: INFO: TARGET SAID: 'INFO: Binary build date: May 17 2019 @ 23:12:26'
09:09:35: INFO: TARGET SAID: 'INFO: Binary build date: May 17 2019 @ 23:12:26
'
09:09:35: INFO: TARGET SAID: 'INFO: Chip serial num: 1387265276 (0x52affcfc)'
09:09:35: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
09:09:35: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
09:09:35: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
09:09:35: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
09:09:35: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
Writing log to 'C:\Users\Pawan-PC\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt', might take a minute
Log is 'C:\Users\Pawan-PC\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
or965 said:
Maybe we should try to use other software to flash ,try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash ,if you have an error, try to go to the firmware and change setting.xml name to flash_local.xml and try to flash again .
Click to expand...
Click to collapse
Let me provide a couple of tips here: When pointing to the path of your extracted files in C : copy paste the path directory using the mouse.
If you have a firehose connection error , disconnect the usb cable and reconnect only to a usb2 port ( use a hub if needed) QPST can be setup to not start until you connect the phone.
Next, if facing a signature issue. temporarily disable antivirus and firewall and Windows signature enforcement if absolutely necessary.
This can all be easily re enabled afterwards.
If you face any other issues, refer to my old guide for troubleshooting ideas. here for additional things to try. I have personally helped possibly over a hundred people unbrick their phone
These steps are identical for most qualcomm phones. obviously use only qfil repair files made for your device and not from my link.
PS : Firehose fail error does not necessarily mean that the process will fail, just wait longer, up to 15 to 20 minutes, sometimes you will get that error and it will sort itself out. restart the process all over again, but wait for 15 minutes on each attempt. Also disconnect peripheral devices from other usb ports. it is very important that you use a USB 2 port or a usb hub.
Once the rom is restored the phone should reboot to the set screen up on it's own.
tsongming said:
Let me provide a couple of tips here: When pointing to the path of your extracted files in C : copy paste the path directory using the mouse.
If you have a firehose connection error , disconnect the usb cable and reconnect only to a usb2 port ( use a hub if needed) QPST can be setup to not start until you connect the phone.
Next, if facing a signature issue. temporarily disable antivirus and firewall and Windows signature enforcement if absolutely necessary.
This can all be easily re enabled afterwards.
If you face any other issues, refer to my old guide for troubleshooting ideas. here for additional things to try. I have personally helped possibly over a hundred people unbrick their phone
These steps are identical for most qualcomm phones. obviously use only qfil repair files made for your device and not from my link.
PS : Firehose fail error does not necessarily mean that the process will fail, just wait longer, up to 15 to 20 minutes, sometimes you will get that error and it will sort itself out. restart the process all over again, but wait for 15 minutes on each attempt. Also disconnect peripheral devices from other usb ports. it is very important that you use a USB 2 port or a usb hub.
Once the rom is restored the phone should reboot to the set screen up on it's own.
Click to expand...
Click to collapse
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
https://pastebin.com/vYjC5rxq
And here is my log from C:\Users\Pawan-PC\AppData\Roaming\Qualcomm\QFIL\COMPORT_5 port_tra
ce.txt
https://pastebin.com/2VynsCD7
shilpakar7 said:
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
First just a friendly tip, when people spend time helping at the very least, click the thank you button otherwise what is their motivation? When posting logs, post it as an attachment ( XDA Rules) its clutters threads.
The bootloader destroyed is no big deal, it's resolved by flashing the boot image. The real issue is the key mismatch error. You need to use the fastboot rom only from your device model. Example : Global versus Chinese.
Finally, I do not own that phone so there isn't ,much more I can contribute. However, I am, certain that you will eventually solve it, try another fastboot rom, be patient ( this could take days the first time) and take notes, so when you are finished you can help other people.
I would suggest that you contact others within the realme community that have had bricks. for example I have seen that people have had success with other real me 3s. You may better off joining Telegram and connecting with user's on the Global scale. You can find telegram groups by searching keywords.
Finally, @or965 stated that he successfully restored his phone that is identical to yours...I think. I would definitely speak with him and if he helps you unbrick your phone, I would absolutely buy him a beer.
Good Luck.
Click to expand...
Click to collapse
ok thank you for your advice, I will definitely take it as a reminder. I have uploaded the log file to pastebin.com and postel the url link. Since you don't personally have the device, I shouldn't have asked for more help. Anyways thank you for your valuable time. Since this is so frustating, I guess i will just send it to service center for repair.
tsongming said:
shilpakar7 said:
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
First just a friendly tip, when people spend time helping at the very least, click the thank you button otherwise what is their motivation? When posting logs, post it as an attachment ( XDA Rules) its clutters threads.
The bootloader destroyed is no big deal, it's resolved by flashing the boot image. The real issue is the key mismatch error. You need to use the fastboot rom only from your device model. Example : Global versus Chinese.
Finally, I do not own that phone so there isn't ,much more I can contribute. However, I am, certain that you will eventually solve it, try another fastboot rom, be patient ( this could take days the first time) and take notes, so when you are finished you can help other people.
I would suggest that you contact others within the realme community that have had bricks. for example I have seen that people have had success with other real me 3s. You may better off joining Telegram and connecting with user's on the Global scale. You can find telegram groups by searching keywords.
Finally, @or965 stated that he successfully restored his phone that is identical to yours...I think. I would definitely speak with him and if he helps you unbrick your phone, I would absolutely buy him a beer.
Good Luck.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Designguru said:
When I hit flash, here is what I get under status
"The filename,directory name, or volume label syntax is incorrect (0x8007007b: Open programmer "MPRG*hex")
Click to expand...
Click to collapse
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 and try to flash with miflash like I write in the last message .
shilpakar7 said:
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
https://pastebin.com/vYjC5rxq
Click to expand...
Click to collapse
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 .
try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash.
Finally said:
@or965[/user] stated that he successfully restored his phone that is identical to yours...I think. I would definitely speak with him and if he helps you unbrick your phone, I would absolutely buy him a beer.
Click to expand...
Click to collapse
I did not have this device yet so I do not successfully restored my phone .
or965 said:
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 and try to flash with miflash like I write in the last message .
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 .
try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash.
I did not have this device yet so I do not successfully restored my phone .
Click to expand...
Click to collapse
this method also not working. The status tab on MiFlash displays same message as mentioned by designguru
Hi,
I've been using some custom Lineage with my S8 SM-G950F which worked for for a while and now I'm trying to get back to stock, usually its quite simple download the firmware from Sammobile and flash it with Odin.
I did it and it seem to work perfectly, download the latest version G950FXXSADTI1_G950FOXMADTI1_ITV, my phone is from Italy and bough directly from samsung.
I flashed with Odin 3.14 pointing the 4 files, used the CSC not the HOME one, clean everything, no errors.
I started to install things and after installed most of the stuff I try to add my Credit Cards to Google Pay and it does not let me do it and tell me it is a rooted phone and I could not do add credit cards.
Netflix doesn't even appear on PlayStore to donwload.
Everything works fine, I tried to reflash a couple of times with no success
Only thing strange is when I enter into recovery, it gives me some errors as bellow:
#fail to open recovery cause (no such file or directory)# --> the cause would be me holding keys while starting the phone I believe
Supported API: 3
e: unknow voulme for path [/odm]
e: unknow voulme for path [/vendor]
e: unknow voulme for path [/odm]
e: unknow voulme for path [/vendor]
#MANUAL MODE v1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT (no such file or directory)
can't open directory /system/omc/SUP/
....some others similar lines
E:[libfs_mgr]is_dt_compatible() firmware info not valid : '/proc/device-tre/firmware/android/compatible: no such file or directory
IF someone can help me here, I appreciate
Solved, just closed the bootloader.. Silly of me to forget it
Thanks anyway.