Hi,
My phone is stuck at boot
error boot.img
keeps rebooting, unable to boot to recovery (can only access erecovery)
bootloader unlocked, frp locked
I tried using dload method to flash stock firmware but each time installation fails at 5% and I am not getting anywhere with it.
MODEL - BND-AL10
How can i recover my phone from this state? Please help!
lalitkhokhar said:
Hi,
My phone is stuck at boot
error boot.img
keeps rebooting, unable to boot to recovery (can only access erecovery)
bootloader unlocked, frp locked
I tried using dload method to flash stock firmware but each time installation fails at 5% and I am not getting anywhere with it.
MODEL - BND-AL10
How can i recover my phone from this state? Please help!
Click to expand...
Click to collapse
They did something different for dload on this phone.
It needs special firmware to dload
We found that service firmware for l21c432 will get the phone working again, then use hwota to restore correct region firmware
mrmazak said:
They did something different for dload on this phone.
It needs special firmware to dload
We found that service firmware for l21c432 will get the phone working again, then use hwota to restore correct region firmware
Click to expand...
Click to collapse
what is hwota?
will i need to keep all files in dload folder or just the update.app?
is service firmware same as the full ota which is found on Firmware finder?
and there are two type of full ota FullOTA-MF and FullOTA-MF-PV which one should i download
lalitkhokhar said:
what is hwota?
will i need to keep all files in dload folder or just the update.app?
is service firmware same as the full ota which is found on Firmware finder?
and there are two type of full ota FullOTA-MF and FullOTA-MF-PV which one should i download
Click to expand...
Click to collapse
Service rom is different then fullOTA.
From the screenshot you have . The fullota-mf-pv examples are Oreo and the ones without the pv are nougat.
This separation is not allways Oreo/ nougat, but only in your example.
HWOTA is a method to force install fullOTA files that uses a modified stock recovery that bypasses version verifications.
Here is link.--( there is other hwota too. One that has more batch file script and incorporate bootloader unlock and device rebranding. )
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
And service rom was found on rusian site 4pda.
The file download there has reached a download limit and forces you to sign up for a Yandex account. I copied the service rom to Android file host.
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
mrmazak said:
Service rom is different then fullOTA.
From the screenshot you have . The fullota-mf-pv examples are Oreo and the ones without the pv are nougat.
This separation is not allways Oreo/ nougat, but only in your example.
HWOTA is a method to force install fullOTA files that uses a modified stock recovery that bypasses version verifications.
Here is link.--( there is other hwota too. One that has more batch file script and incorporate bootloader unlock and device rebranding. )
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
And service rom was found on rusian site 4pda.
The file download there has reached a download limit and forces you to sign up for a Yandex account. I copied the service rom to Android file host.
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Click to expand...
Click to collapse
thank you! I will try this.
@mrmazak Thank you very much! L21 firmware worked and I am running it without any issue.
What difference does it make as now I am using BND-L21 firmware instead of BND-AL10?
Acc. to me this Rom is better as there are very few bloatware installed as compared to AL10 and everything seems to work fine.
In About Phone only things changed are-
Build number
Baseband Version
Model and imei are same as before.
Does i really need to install AL-10 firmware again?
lalitkhokhar said:
@mrmazak Thank you very much! L21 firmware worked and I am running it without any issue.
What difference does it make as now I am using BND-L21 firmware instead of BND-AL10?
Acc. to me this Rom is better as there are very few bloatware installed as compared to AL10 and everything seems to work fine.
In About Phone only things changed are-
Build number
Baseband Version
Model and imei are same as before.
Does i really need to install AL-10 firmware again?
Click to expand...
Click to collapse
As long as the phone is working normally, I think you should be fine . But further updates will , of course, need to be manually done . Like this install was.
mrmazak said:
Service rom is different then fullOTA.
From the screenshot you have . The fullota-mf-pv examples are Oreo and the ones without the pv are nougat.
This separation is not allways Oreo/ nougat, but only in your example.
HWOTA is a method to force install fullOTA files that uses a modified stock recovery that bypasses version verifications.
Here is link.--( there is other hwota too. One that has more batch file script and incorporate bootloader unlock and device rebranding. )
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
And service rom was found on rusian site 4pda.
The file download there has reached a download limit and forces you to sign up for a Yandex account. I copied the service rom to Android file host.
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Click to expand...
Click to collapse
Restored my phone using the service firmware but the "OEM Unlock" option in the Developer Options is completely missing. Is there a fix for this?
XandeR180 said:
Restored my phone using the service firmware but the "OEM Unlock" option in the Developer Options is completely missing. Is there a fix for this?
Click to expand...
Click to collapse
Never saw that before, unless your phone in C00 or C01 (China region)
Try factory reset?
Then skip wifi and Google account, but set a lock screen pin or pattern. See if that helps.
Then share screenshot of "about phone". Block out imei number though.
Also which service ROM did you use. How did you use it. Did you change method from as described, did it flash both parts? The update and hw_update?
mrmazak said:
Never saw that before, unless your phone in C00 or C01 (China region)
Try factory reset?
Then skip wifi and Google account, but set a lock screen pin or pattern. See if that helps.
Then share screenshot of "about phone". Block out imei number though.
Also which service ROM did you use. How did you use it. Did you change method from as described, did it flash both parts? The update and hw_update?
Click to expand...
Click to collapse
Actually, my phone is a BND-L34 (Mate SE)
Performed a factory reset 3 times. Third time I set up a pattern but the option still hasn't appeared.
I used the ROM in the link you provided in your previous post (had no idea there were any others, as I haven't been able to find anything else).
Didn't change anything. Extracted the dload folder to my external SD card, powered on while holding all three buttons and the update itself went just fine. Also I'm not sure how to tell whether or not it flashed both parts.
Everything else SEEMS to be working. Haven't poked around or anything, nor have I tried my SIM card. However the only issue I'm coming across (that I actually care about at the moment) is the inability to enable OEM unlocking (not grayed out or anything. It's just completely missing).
Pictures below.
XandeR180 said:
Actually, my phone is a BND-L34 (Mate SE)
Performed a factory reset 3 times. Third time I set up a pattern but the option still hasn't appeared.
I used the ROM in the link you provided in your previous post (had no idea there were any others, as I haven't been able to find anything else).
Didn't change anything. Extracted the dload folder to my external SD card, powered on while holding all three buttons and the update itself went just fine. Also I'm not sure how to tell whether or not it flashed both parts.
Everything else SEEMS to be working. Haven't poked around or anything, nor have I tried my SIM card. However the only issue I'm coming across (that I actually care about at the moment) is the inability to enable OEM unlocking (not grayed out or anything. It's just completely missing).
Pictures below.
Click to expand...
Click to collapse
The system number ending in .046 is clue that the second part of service ROM did not load.
Before worrying about the oem toggle too much. Does the boooader screen show frp locked?
mrmazak said:
The system number ending in .046 is clue that the second part of service ROM did not load.
Before worrying about the oem toggle too much. Does the boooader screen show frp locked?
Click to expand...
Click to collapse
Nope. It just says "PHONE locked". Weird, I could've sworn it said frp locked the first time I went into fastboot
XandeR180 said:
Nope. It just says "PHONE locked". Weird, I could've sworn it said frp locked the first time I went into fastboot
Click to expand...
Click to collapse
Alright, oem unlock should work.
Then after the reset and boot up , back to fastboot to flash TWRP.
Then use hwota, and best to go with probably b330,
mrmazak said:
Alright, oem unlock should work.
Then after the reset and boot up , back to fastboot to flash TWRP.
Then use hwota, and best to go with probably b330,
Click to expand...
Click to collapse
WOW it actually worked!! I'm amazed that it was that simple. Thank you so much. I'll follow your HWOTA guide and keep you posted if anything goes wrong :good:
XandeR180 said:
WOW it actually worked!! I'm amazed that it was that simple. Thank you so much. I'll follow your HWOTA guide and keep you posted if anything goes wrong :good:
Click to expand...
Click to collapse
I did see one time the issue with unknown model and strange build number. And hwota did not help going from emui 8 to emui 8. But downgradeing from emui 8 to emui 5 fixed it. Then update back to 8 went normal
mrmazak said:
I did see one time the issue with unknown model and strange build number. And hwota did not help going from emui 8 to emui 8. But downgradeing from emui 8 to emui 5 fixed it. Then update back to 8 went normal
Click to expand...
Click to collapse
Actually, installing the update files for emui 8 while on emui 8 worked perfectly! At least I think. Everything looks normal so far, even the model number and build number
XandeR180 said:
Actually, installing the update files for emui 8 while on emui 8 worked perfectly! At least I think. Everything looks normal so far, even the model number and build number
Click to expand...
Click to collapse
Sounds good.
So now let me ask what was the issue you had to recover from. And I assume you had the unlock code already?
I ask because yesterday I was helping someone , also with mate se. They are trying to get uock code from DC unlock, but need to downgrade first. I had guided a downgrade this way before to get unlock codes , and it went just fine. But when you had the unknown model number, it makes me wonder what caused it, and of it could be avoided for the guy I'm helping now.
mrmazak said:
Sounds good.
So now let me ask what was the issue you had to recover from. And I assume you had the unlock code already?
I ask because yesterday I was helping someone , also with mate se. They are trying to get uock code from DC unlock, but need to downgrade first. I had guided a downgrade this way before to get unlock codes , and it went just fine. But when you had the unknown model number, it makes me wonder what caused it, and of it could be avoided for the guy I'm helping now.
Click to expand...
Click to collapse
As much as I would love to help, I really don't know what caused the unknown model number.
The reason I needed to restore my phone was because I had originally gotten the Oreo update through firmware finder because I never officially got the OTA (even though my IMEI was approved according to FF). The update seemed to have worked alright but one day my camera suddenly stopped functioning completely. Reboot didn't fix it. So I decided to factory reset it but that only ended in a bootloop.
I could have used TWRP to fix it but for some reason it would not boot into TWRP, so I opted for triggering an OTA installation through stock recovery but that didn't work (this was before I knew of the service ROM). So then I tried reflashing TWRP but I couldn't because I forgot to enable USB debugging. I knew I was done for at that point. And stupid me added to the problem by relocking the bootloader (I don't remember why I decided to do that).
So I hadn't touched the thing in months up until today to see if there was any new methods for restoring a bricked device. That's when I found some threads pointing towards a service ROM. And here I am.
Sorry that I couldn't provide any specific details. Some things I just forgot and some things I don't even know the cause of (like the camera malfunctioning and the bootloop after factory resetting).
Related
Hello =)
I was wondering if someone will be able to help me with my honor 8 pro.
I rooted my device with TWRP for a couple of month and decided to get back because I was not able to update my device.
So I restart my phone and was in the TWRP recovery mode I did a wipe and uncheck twrp install app.
I decided to relock my bootloader to install stock firmware.
So it restart in the erecovzry mode (i think he is called like this) it let me download the latest firmware through the wifi but show me an error message couple of second after that.
I'm able to boot in fastboot and rescue mode (with android logo)
I try to download in "dload" folder in the SD Card but when i'm starting with three fingers method it's the same it load 5% and say redownload package (error)
I juste bought the honor 8 pro during the pre realease i'm living in france and i've order it on the official website.
I'm trying to know which model I have (Europe - Asia - Russia) because i put everything in the dload folder but it always show me an error.
Do you know a way to check which region my phone is coming from ? With S/N or IMEI for example ?
What I did it's I have unlock the bootloader (once again) and i have seen the TWRP recovery mode only one time and can't access it again.
Thanks for your help..
I can't use my device for one week now and that's quite embarassing.
Michael
Zirconiumirish said:
Hello =)
I was wondering if someone will be able to help me with my honor 8 pro.
I rooted my device with TWRP for a couple of month and decided to get back because I was not able to update my device.
So I restart my phone and was in the TWRP recovery mode I did a wipe and uncheck twrp install app.
I decided to relock my bootloader to install stock firmware.
So it restart in the erecovzry mode (i think he is called like this) it let me download the latest firmware through the wifi but show me an error message couple of second after that.
I'm able to boot in fastboot and rescue mode (with android logo)
I try to download in "dload" folder in the SD Card but when i'm starting with three fingers method it's the same it load 5% and say redownload package (error)
I juste bought the honor 8 pro during the pre realease i'm living in france and i've order it on the official website.
I'm trying to know which model I have (Europe - Asia - Russia) because i put everything in the dload folder but it always show me an error.
Do you know a way to check which region my phone is coming from ? With S/N or IMEI for example ?
What I did it's I have unlock the bootloader (once again) and i have seen the TWRP recovery mode only one time and can't access it again.
Thanks for your help..
I can't use my device for one week now and that's quite embarassing.
Michael
Click to expand...
Click to collapse
Simple method is download stock firmware and flash via dload...
Did you download correct number firmware..??
Which number of firmware you were on before hoing to custom?
hassanjavaid8181 said:
Simple method is download stock firmware and flash via dload...
Did you download correct number firmware..??
Which number of firmware you were on before hoing to custom?
Click to expand...
Click to collapse
I already try through the dload procedure but didn't succeed lol.
Maybe I didn't find the correct firmware .
I try several maybe 3.
I can't remember which version I was on before trying to reinstall.
I didn't do the B150 and the previous one so I have to version late.
Should I recover only the version I had when trying to reinstall it ?
Thanks a lot for your help
Zirconiumirish said:
I already try through the dload procedure but didn't succeed lol.
Maybe I didn't find the correct firmware .
I try several maybe 3.
I can't remember which version I was on before trying to reinstall.
I didn't do the B150 and the previous one so I have to version late.
Should I recover only the version I had when trying to reinstall it ?
Thanks a lot for your help
Click to expand...
Click to collapse
yes you have to be on same one or higher to flash it succesfully..
otherwise you need a rollback pkg and flash any firmware you want..
if you can find rollback pkg i suggest to you to flash lower android version of full available firmwre after your device boots up update it via ota
hassanjavaid8181 said:
yes you have to be on same one or higher to flash it succesfully..
otherwise you need a rollback pkg and flash any firmware you want..
if you can find rollback pkg i suggest to you to flash lower android version of full available firmwre after your device boots up update it via ota
Click to expand...
Click to collapse
When you say "flash" you mean use TWRP ? or only put the firmware on the sdcard and do the 3 button method ?
Should I have the bootloader unlock or lock or doesn't matter the state of the bootloader ?
Zirconiumirish said:
When you say "flash" you mean use TWRP ? or only put the firmware on the sdcard and do the 3 button method ?
Should I have the bootloader unlock or lock or doesn't matter the state of the bootloader ?
Click to expand...
Click to collapse
Yes i mean dload method with three button..not need bootloader status unlock or lock..
All you have to make sure is to be on stock recover and right firmware
hassanjavaid8181 said:
Yes i mean dload method with three button..not need bootloader status unlock or lock..
All you have to make sure is to be on stock recover and right firmware
Click to expand...
Click to collapse
Okay thanks lol
The last attempt was "Error" and stop at 5% and another one saying incompatible firmware.
So i'm downloading couple of firmware and trying to reinstall through the 3 button method.
Zirconiumirish said:
Okay thanks lol
The last attempt was "Error" and stop at 5% and another one saying incompatible firmware.
So i'm downloading couple of firmware and trying to reinstall through the 3 button method.
Click to expand...
Click to collapse
Give some details about your model number etc..if i will find i will drop a link here
Good luck..
hassanjavaid8181 said:
Give some details about your model number etc..if i will find i will drop a link here
Good luck..
Click to expand...
Click to collapse
Oh thanks a lot
That's the :
Honor 8 Pro 64 GB (Europe)
DUK-L09
Thanks
Zirconiumirish said:
Oh thanks a lot
That's the :
Honor 8 Pro 64 GB (Europe)
DUK-L09
Thanks
Click to expand...
Click to collapse
I try once again with an older firmware and the latest but always told me " Install failed at about 5%) or Not recognize.
Do you know why it always told ma that message ?
I though I was able to access to the TWRP recovery but only when I lock and unlock the bootloader.
I have a message who told me
ERROR MODE
Func NO : 11 (recovery image)
Error NO : 2 (load failed)
Thanks for your help.
Michael
Zirconiumirish said:
I try once again with an older firmware and the latest but always told me " Install failed at about 5%) or Not recognize.
Do you know why it always told ma that message ?
I though I was able to access to the TWRP recovery but only when I lock and unlock the bootloader.
I have a message who told me
ERROR MODE
Func NO : 11 (recovery image)
Error NO : 2 (load failed)
Thanks for your help.
Michael
Click to expand...
Click to collapse
If you unlock the bootloader you will be in twrp.
Ok i got the device details as DUK-L09 but any idea on the region that was present in build number as DUK-L09CXYZBXYZ.
IF you know the build number it will of great help to proceed.
Have you taken twrp backup?
shashank1320 said:
If you unlock the bootloader you will be in twrp.
Ok i got the device details as DUK-L09 but any idea on the region that was present in build number as DUK-L09CXYZBXYZ.
IF you know the build number it will of great help to proceed.
Have you taken twrp backup?
Click to expand...
Click to collapse
Okay thanks for your help
My region is EUROPEAN this one should be the asian one:
Russian is L09C10B120a
European L09C432B120a
I didn't have any backup unfortunately of the TWRP.
I was able to access to the fastboot mode
I unlock and relock the bootloader but instead of falling on the TWRP Recovery I have the message I told you before with Error.
And sometime the same error number but instead of recovery it show boot or something like that..
I don't know what's going wrong with the three button method because I correctly format the SD Card and create the folder in it and try couple of firmware and always error ..
And I try old firmware and new firmware..
Thanks a lot for your time
Michael
Zirconiumirish said:
Okay thanks for your help
My region is EUROPEAN this one should be the asian one:
Russian is L09C10B120a
European L09C432B120a
I didn't have any backup unfortunately of the TWRP.
I was able to access to the fastboot mode
I unlock and relock the bootloader but instead of falling on the TWRP Recovery I have the message I told you before with Error.
And sometime the same error number but instead of recovery it show boot or something like that..
I don't know what's going wrong with the three button method because I correctly format the SD Card and create the folder in it and try couple of firmware and always error ..
And I try old firmware and new firmware..
Thanks a lot for your time
Michael
Click to expand...
Click to collapse
What was your exact build before having all these issues. That would help me to provide you the correct link for right firmware
shashank1320 said:
What was your exact build before having all these issues. That would help me to provide you the correct link for right firmware
Click to expand...
Click to collapse
Hi sorry for the late answer.
I have my bootloader locked and the original recovery.
I would like to install the tock firmware and try couple without any success.
I don't remember what was the build number because I didn't have any backup but I did a preorder so it could be the first firmware that they put in it after production.
I try couple and always say "firware not found or incompatibility" I don't really understand because they are all for Honor 8 pro and european version..
Thanks for your help..
We should create a general recovery method because many people have similar recovery issues.
In my case "dload recovery" does not work and always fails at 5% (I've tried over 10 ROMs).
As I know this means that UPDATE.APP does not match the current Honor 8 pro version (you cannot downgrade), region, modelname etc...
Please try this method..
You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img ,
{{{ bootloader "NO NEED" This Work Before Just Because v48 and v56 have the same bootloader version }}} , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
EDIT HELLO
Things Have Changed Dont Try To Downgrade Bootloader or The Phone Will Get Hard Bricked , Why well bootloader versions on new firmwares have been upgraded please check all the information on the Bootloader/Fastboot
MODE Of The Phone Which Version You Have , Now For Example If You Are On Version NCQS26.69-64-5 you will need SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml full package then extract and now you will need SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml extract it too , Now Just Move The 2 Oems Images And 4 System Images And Boot Image To SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml Folder Next Look for RSD_Lite_Motorola_XML_To_Batch_Script on Google Download it And Watch The Video Of Rootjunky on how to use it. Very Simple Wish All Of You Luck And im Not Responsible Of Any Damage Of Your Phone Use This Guide On Your Own Terms.
ozmage said:
You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img , bootloader , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
Click to expand...
Click to collapse
I flashed the Sprint firmware and had data working on my XT1766 after it got it's carrier update, the Sprint firmware does not soft brick the phone as I flashed it and can confirm it doesn't soft brick it, so you are incorrect in saying that.
I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?
dlinderaz said:
I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?
Click to expand...
Click to collapse
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?
madbat99 said:
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?
Click to expand...
Click to collapse
I restored the entire thing after flashed the indicated files causing the error message.
dlinderaz said:
I restored the entire thing after flashed the indicated files causing the error message.
Click to expand...
Click to collapse
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.
madbat99 said:
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.
Click to expand...
Click to collapse
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.
dlinderaz said:
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.
Click to expand...
Click to collapse
Keep in mind I have the virgin mobile version (sprint xt1766). Don't know which one you have. Some have had trouble with rsdlite on Windows 10, it worked fine for me though.
I used rsdlite from here
The newest one, 6.2.4 I think
Apn Xt1766
I just want to add apn and want to use hot spot again
As the phone is updated on latest build ..
I don't want the root access..
What's should I try then from previous build , can anyone
Guide me easy steps plz.
Xt1766 how to get working apn
Will anyone confirm
danishamini.saifi said:
Will anyone confirm
Click to expand...
Click to collapse
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.
madbat99 said:
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.
Click to expand...
Click to collapse
Thanks, ill try and share the result.
I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.
danishamini.saifi said:
I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.
Click to expand...
Click to collapse
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.
madbat99 said:
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.
Click to expand...
Click to collapse
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?
danishamini.saifi said:
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?
Click to expand...
Click to collapse
N/A will be there. But you can flash a new boot logo to kinda hide it. Instead of a black screen, any logo you want, maybe with a white strip at the top to hide it. I'll get you a link.
Here are some good ones. https://forum.xda-developers.com/mo...om-boot-logos-converted-t3759320/post75787882
And here is the guide to make your own
https://forum.xda-developers.com/moto-e4/how-to/replace-n-boot-image-t3687212/post74118155
@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks
danishamini.saifi said:
@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks
Click to expand...
Click to collapse
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.
madbat99 said:
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.
Click to expand...
Click to collapse
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.
dlinderaz said:
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.
Click to expand...
Click to collapse
Ota updates will likely always fail if you have twrp, or have modified the system in any way. The ota performs many checks (assert props) to see if the system is clean. If any asserts fail, the ota will fail. Even restoring the stock recovery doesn't guarantee the ota will work.
I got a Huawei mate se and didn't realize that allowing it to update to Android o would block the bootloader unlock tool. Is there anyway to downgrade my firmware so I can unlock my bootloader?
voldomart13 said:
I got a Huawei mate se and didn't realize that allowing it to update to Android o would block the bootloader unlock tool. Is there anyway to downgrade my firmware so I can unlock my bootloader?
Click to expand...
Click to collapse
There is a roll-back ROM on firmware finder. As long as it shows your IMEI as approoved, it should install.
That's the nice clean way.
There is a dirty ( possibly dangerous way ) by using the nougat service ROM. That ROM is for bnd-L21, so not sure how an unlocked bootloader will handle it. It has worked on unlocked before.
mrmazak said:
There is a roll-back ROM on firmware finder. As long as it shows your IMEI as approoved, it should install.
That's the nice clean way.
There is a dirty ( possibly dangerous way ) by using the nougat service ROM. That ROM is for bnd-L21, so not sure how an unlocked bootloader will handle it. It has worked on unlocked before.
Click to expand...
Click to collapse
I have been attempting to use firmware finder but I can't wrap my head around actually pushing the update. I heard you need an outdated version of hisuite but no one specifies what version. Any help is appreciated =)
voldomart13 said:
I have been attempting to use firmware finder but I can't wrap my head around actually pushing the update. I heard you need an outdated version of hisuite but no one specifies what version. Any help is appreciated =)
Click to expand...
Click to collapse
Insttall firmware finder from playstore.
In the app select the "hamburger" menu, from top left corner. Select instructions. Either watch videos, or read the text guides
mrmazak said:
Insttall firmware finder from playstore.
In the app select the "hamburger" menu, from top left corner. Select instructions. Either watch videos, or read the text guides
Click to expand...
Click to collapse
The mobile app as far as I can tell doesn't work on newer versions of android. They even have a disclaimer mentioning that the app only works for older devices now.
voldomart13 said:
The mobile app as far as I can tell doesn't work on newer versions of android. They even have a disclaimer mentioning that the app only works for older devices now.
Click to expand...
Click to collapse
You are not on 8.1, the app can work.
But I was only referencing the app for the guides linked inside.
You should be able to use it to flash b330. Which should work in DC
mrmazak said:
You are not on 8.1, the app can work.
But I was only referencing the app for the guides linked inside.
You should be able to use it to flash b330. Which should work in DC
Click to expand...
Click to collapse
My bad I am on 8.0 to be specific bnd-l34 8.0.0.341(c567) and as much as I've tried I can not get it to work on the phone following along on the videos. They are using the app on emui 5.0 not 8.0. It doesn't work anymore on 8.0
All there videos revolve around emui 5.0 or lower. It stopped working with 8.0
voldomart13 said:
My bad I am on 8.0 to be specific bnd-l34 8.0.0.341(c567) and as much as I've tried I can not get it to work on the phone following along on the videos. They are using the app on emui 5.0 not 8.0. It doesn't work anymore on 8.0
Click to expand...
Click to collapse
Because the locked bootloader, you can only use the firmwares that are approoved.
Chances are , the only one that's approoved is the b330
And if not , then only option is the service-rom. Followed by dc-unlock, then the hwota and correct ROM
It has been done.
There should be confirmation back in the mate thread somewhere.
mrmazak said:
Because the locked bootloader, you can only use the firmwares that are approoved.
Chances are , the only one that's approoved is the b330
And if not , then only option is the service-rom. Followed by dc-unlock, then the hwota and correct ROM
It has been done.
There should be confirmation back in the mate thread somewhere.
Click to expand...
Click to collapse
Which mate thread?
voldomart13 said:
Which mate thread?
Click to expand...
Click to collapse
I'm searching. I know i have recommended this process many times, and got many success responses. But I am striking out in finding threads with confirmed responses.
This search only shows 4 found matches for the search info. One does fit real good, but the author has made it sound , not real credible.
https://forum.xda-developers.com/search/forum/7100?query=unlock mate service-rom#posts
mrmazak said:
Because the locked bootloader, you can only use the firmwares that are approoved.
Chances are , the only one that's approoved is the b330
And if not , then only option is the service-rom. Followed by dc-unlock, then the hwota and correct ROM
It has been done.
There should be confirmation back in the mate thread somewhere.
Click to expand...
Click to collapse
What about this method? https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/
mrmazak said:
I'm searching. I know i have recommended this process many times, and got many success responses. But I am striking out in finding threads with confirmed responses.
This search only shows 4 found matches for the search info. One does fit real good, but the author has made it sound , not real credible.
https://forum.xda-developers.com/search/forum/7100?query=unlock mate service-rom#posts
Click to expand...
Click to collapse
This post you made here sounds doable.
This service rom so far has been only thing we found that will load with three button method (dload)
But it is not a full rom to keep on device. It needs you to follow up with flashing fullOTA of your correct version after.
https://www.androidfilehost.com/?fid...83647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Enlighten me what is huru or hwota? If I were to flash this does it boot up into android or is it non functional?
voldomart13 said:
This post you made here sounds doable.
This service rom so far has been only thing we found that will load with three button method (dload)
But it is not a full rom to keep on device. It needs you to follow up with flashing fullOTA of your correct version after.
https://www.androidfilehost.com/?fid...83647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Enlighten me what is huru or hwota? If I were to flash this does it boot up into android or is it non functional?
Click to expand...
Click to collapse
Yes, this should leave you able to boot. And with build level that should allow DC unlocked to give you the code.
Remember like I said before this is kind of a dirty way around and 'could' have issues unknown. Like what if DC does not give you a code, you would then be stuck . (Though you are stuck now)
Huru and hwota are very similar. They both use TWRP to give custom flashing control.
Hwota uses modified stock recovery to flash full ota files.
Huru repacks full ota files so that TWRP can flash them.
Since doth start with TWRP , bootloader unlock is needed.
mrmazak said:
Yes, this should leave you able to boot. And with build level that should allow DC unlocked to give you the code.
Remember like I said before this is kind of a dirty way around and 'could' have issues unknown. Like what if DC does not give you a code, you would then be stuck . (Though you are stuck now)
Huru and hwota are very similar. They both use TWRP to give custom flashing control.
Hwota uses modified stock recovery to flash full ota files.
Huru repacks full ota files so that TWRP can flash them.
Since doth start with TWRP , bootloader unlock is needed.
Click to expand...
Click to collapse
I see. And say dc cant get a code I would be stuck no way of recovery? Man I miss the days of samsung phones and using odin for upgrade/downgrade =/ been doing this stuff since samsung captivate days.
voldomart13 said:
I see. And say dc cant get a code I would be stuck no way of recovery? Man I miss the days of samsung phones and using odin for upgrade/downgrade =/ been doing this stuff since samsung captivate days.
Click to expand...
Click to collapse
Just spent most of the morning going back and forth with someone else with mate see, and they just did restored his device with the service ROM.
I do not now what he was restoring from, but he ended up with "unknown model" and default build number of 8.0.0.46
This is because of (probably) some data corrupt issue making the flash go bad. But he was able to run the ROM and unlock boooader.
Difference is he already had his unlock code.
https://forum.xda-developers.com/honor-7x/help/dload-method-stuck-5-t3821898
voldomart13 said:
I see. And say dc cant get a code I would be stuck no way of recovery? Man I miss the days of samsung phones and using odin for upgrade/downgrade =/ been doing this stuff since samsung captivate days.
Click to expand...
Click to collapse
Have you seen this guide?
It is for "official" hisuite roll-back
I have not rolled back so do not know it it works though.(I checked with my device, it shows no downgrade available)
I know the roll-back firmwarm listed on firmware finder was listed as "bond" and not "bnd". So this means not available "officially"
https://usermanual.wiki/Huawei/EMUI...roid70OperationInstructionpdf.1621060771/help
I have lost IMEI number after flashing Pie. On my Sprint Moto Z2 Force. Signal bar has turned grey and IMEI is showing as zero.
Wifi is working
Bluetooth is working
Barcodes in bootloader mode is showing some different IMEI no.
Downgrade to Stock Oreo or Naugat
If I downgrade to stock Oreo then I lost all wifi, sim and Bluetooth. Also no baseband found in bootloader.
Will appreciate if someone can help.
Thanks in advance.
If you have already flashed Pie Rom (including bl、 baseband), you will not be able to return to Oreo
Hello.
I am trying to research the imei bricks on Sprint models after Verizon pie update. In short, everything we understand says this should not be happening, and yet it is.
Can you, for research purposes, describe the state of your device when you applied the update? Was it running full verizon firmware down to the bl, modem, and gpt? I may have an experimental fix but I need to gather more info about the bricks.
Also, it is impetative that you don't flash any further modems for my fix to have a good chance to work. Thanks.
Thanks for the message,
The device working fine, very super smooth and I can feel the difference.
The only think which is not working is cell phone and it's because of 0 IMEI number, currently I am on pie retail version (NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml) downloaded from mirrors lolinet com / firmware / Moto / Nash / retail
Pls let me know if you want more info.
Thanks in advance.
hqureshi said:
Thanks for the message,
The device working fine, very super smooth and I can feel the difference.
The only think which is not working is cell phone and it's because of 0 IMEI number, currently I am on pie retail version (NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml) downloaded from mirrors lolinet com / firmware / Moto / Nash / retail
Pls let me know if you want more info.
Thanks in advance.
Click to expand...
Click to collapse
What firmware did you flash from? Stock? Do you have an unlocked bootloader?
If yes to all the above, I can give you some experimental things to try.
Yes to all and bootloader is unlocked.
btw i have flashed firmware in this order
1. i flashed NASH_PPX29.159_19_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
then
2. XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and now on
3. NASH_RETAIL_9.0_PPX29.159-19_subsidy-default_regulatary-DEFAULT_CFC.xml
That's not ideal (the additional flashes) but what I have is still worth a try and you have nothing to lose.
The first thing we need is to boot twrp on the device using fastboot (get the latest .img here and fastboot boot twrp.img it). Once in twrp, immediately reboot to "EDL."
https://dl.twrp.me/nash/
Get drivers for qualcomm 9008 mode device if needed (should show in Windows device manager under "ports"):
https://androidfilehost.com/?fid=11410963190603862036
Then get the nougat blankflash here:
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/blankflash_from_NDX26.183-15_17.zip
Extract and run the cmd inside. You may need to try a few times, on different usb ports. I heard usb 2.0 works best.
If it succeeeds, try flashing your stock firmware and see if imei is back.
Good luck. This is a real stretch but it just might work...
PS: This does have potential to completely brick your device. Please keep that in mind and weigh your options.
I have tried as per instruction but still getting the "baseband not found" status on all stock oreo & nougat firmwares. So when I flash Pie retail I get wifi and Bluetooth back with 0 IMEI status. so the situation is the same.
BTW I have read somewhere the 0 IMEI issue is related persist file/folder/. I may be able to share reference link of that discussion in a while. (Link of discussion)
Let me know if you want me to test anything else. Thanks again for your time. best
hqureshi said:
I have tried as per instruction but still getting the "baseband not found" status on all stock oreo & nougat firmwares. So when I flash Pie retail I get wifi and Bluetooth back with 0 IMEI status. so the situation is the same.
BTW I have read somewhere the 0 IMEI issue is related persist file/folder/. I may be able to share reference link of that discussion in a while. (Link of discussion)
Let me know if you want me to test anything else. Thanks again for your time. best
Click to expand...
Click to collapse
That's really odd. Sorry, I have nothing right now for you but will look into this as best I can.
Thanks, btw whenever i flash stock nougat i am getting verification failed error during flashing of bootloader.img
EDL
R-T-B said:
That's not ideal (the additional flashes) but what I have is still worth a try and you have nothing to lose.
The first thing we need is to boot twrp on the device using fastboot (get the latest .img here and fastboot boot twrp.img it). Once in twrp, immediately reboot to "EDL."
https://dl.twrp.me/nash/
Get drivers for qualcomm 9008 mode device if needed (should show in Windows device manager under "ports"):
https://androidfilehost.com/?fid=11410963190603862036
Then get the nougat blankflash here:
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/blankflash_from_NDX26.183-15_17.zip
Extract and run the cmd inside. You may need to try a few times, on different usb ports. I heard usb 2.0 works best.
If it succeeeds, try flashing your stock firmware and see if imei is back.
Good luck. This is a real stretch but it just might work...
PS: This does have potential to completely brick your device. Please keep that in mind and weigh your options.
Click to expand...
Click to collapse
I can see the qualcomm device in twrp on my device manager. how to i get to edl mode. there is no reboot edl option in twrp. do i command fastboot reboot edl when device in twrp screen? when i run the qboot blank-flash it says wating for device
Please use latest TWRP from here https://dl.twrp.me/nash/ load it using fastboot and the in TWRP click reboot and select EDL.
Let me know if you face any issue.
i'm on the same boat
no celluler, no IMEI
wifi and bluetooth working
Everyone keeps trying to flash pie firmware that isn't for their variant and this is the result, no baseband. Plus once you upgrade to a pie modem, you can't go back to an oreo modem. Maybe something will come along and remedy that, that's a big maybe too. The devs are trying to find a solution, but there just might not be one. You can't blankflash your way out of it, and if you're not careful you can brick your phone for real. Not 9008 brick, paperweight. Not trying to be an ass, just trying to warn others. If it isn't pie for your phone, don't flash it.
Blankflash doesn't work anyways.
Stand by we are working on another fix.
R-T-B said:
Blankflash doesn't work anyways.
Stand by we are working on another fix.
Click to expand...
Click to collapse
Let me know if you need this fastboot_nash_verizon_oem_vzw_user_9_PCX29.159-21_10d9a_release-keys-cid2_vzw.tar.gz. I have got it from @oslov a member of discord.
I have tried this in this sequence but still zero IMEI.
1. Nougat Blank flash
2. Flashed Stock Verizon Oreo and then staying in bootloader mode I flashed above Pie Update using Flash-All batch file.
Phone successfully booted with Verizon sim activation warning but IMEI was 0.
I thought I should update you guys.
Thanks
Oslov is my discord nick.
Confusing I know, lol.
Be careful with that file, we don't fully understand it yet. I gave it to you because, how much worse off can you be really?
R-T-B said:
Oslov is my discord nick.
Confusing I know, lol.
Be careful with that file, we don't fully understand it yet. I gave it to you because, how much worse off can you be really?
Click to expand...
Click to collapse
Lol. Wow!
Thanks again for doing this. Best
un1ocked said:
i'm on the same boat
no celluler, no IMEI
wifi and bluetooth working
Click to expand...
Click to collapse
Have restored IMEI # with the help of @oslov, We will share the solution in a while.
hqureshi said:
I have lost IMEI number after flashing Pie. On my Sprint Moto Z2 Force. Signal bar has turned grey and IMEI is showing as zero.
Wifi is working
Bluetooth is working
Barcodes in bootloader mode is showing some different IMEI no.
Downgrade to Stock Oreo or Naugat
If I downgrade to stock Oreo then I lost all wifi, sim and Bluetooth. Also no baseband found in bootloader.
Will appreciate if someone can help.
Thanks in advance.
Click to expand...
Click to collapse
I have resolved the 0 IMEI issue with the help of R-T-B, by doing undo Sim/network Unlock. changing CHMOD of id_00 to 0770
so now I am facing sim/network locked,
So whenever i unlock the sim/network lock i get 0 IMEI issue.
I will appreciate if someone now can help me to unlock SIM/network lock while keeping IMEI
I am currently on Retail pie with Sim/Network Locked. Phone Model is Sprint XT1789-03, dual sim enabled
I bought a used realme 7 pro that restarts every 10-15 minutes
It doesn't go into fastbot but only into recovery mode
It has build RMX2170_11_F.23.
How can I reflash the phone?
lucasat said:
I bought a used realme 7 pro that restarts every 10-15 minutes
It doesn't go into fastbot but only into recovery mode
It has build RMX2170_11_F.23.
How can I reflash the phone?
Click to expand...
Click to collapse
Sometimes formatting data/factory resetting can fix the issue.
Or if you want to flash a new firmware, then, download a firmware, that comes in .ozip format, transfer it to your SD card, and flash it through it.
If you have some luck, also you can try, updating via Wi-Fi.
Thank you for the answer ... I have already tried to format several times by restoring the factory settings but the problem remained
Having installed the latest version and my recovery doesn't recognize my upload via local .ozip (see picture)
I think the ota didn't go perfectly...
Do you recommend installing the PU version? But then I can put the 11_F23?
lucasat said:
Thank you for the answer ... I have already tried to format several times by restoring the factory settings but the problem remained
Having installed the latest version, it doesn't recognize my upload via .ozip
I think the ota didn't go perfectly...
Do you recommend installing the PU version? But then I can put the 11_F23?
Click to expand...
Click to collapse
Is It your bootloader unlocked?
If your device has Qualcomm there is a tool here in XDA, to flash the . ofp file (fastboot is available through other method, If your device has a MediaTek, SoC, also there are other tools to flash it.
About that specific firmware you're asking, if it is an update, you may flash it.
What is the issue with the file update not recognized?
SubwayChamp said:
Is It your bootloader unlocked?
If your device has Qualcomm there is a tool here in XDA, to flash the . ofp file (fastboot is available through other method, If your device has a MediaTek, SoC, also there are other tools to flash it.
About that specific firmware you're asking, if it is an update, you may flash it.
What is the issue with the file update not recognized?
Click to expand...
Click to collapse
My bootloader is locked and the device has qualcomm snapdragon.
The firmware is the latest UI3.0 installed via ota 3 days ago.
I installed deep testing to unlock the bootloader but it doesn't work .... now I'm trying this procedure (https://c.realme.com/in/post-details/1526491339024314368) and I will keep you informed if it works with UI 3.0 too
Nothing... It's still under warranty and will go to the service center
If restarting occurs exactly certain time period its firmware problem. otherwise battery or emmc fault.
lucasat said:
My bootloader is locked and the device has qualcomm snapdragon.
The firmware is the latest UI3.0 installed via ota 3 days ago.
I installed deep testing to unlock the bootloader but it doesn't work .... now I'm trying this procedure (https://c.realme.com/in/post-details/1526491339024314368) and I will keep you informed if it works with UI 3.0 too
Click to expand...
Click to collapse
Strange, your recovery doesn't have the option to update through the local directory.
lucasat said:
Nothing... It's still under warranty and will go to the service center
Click to expand...
Click to collapse
It could be the best, probably it's a hardware issue that comes from the battery flex cable.
engage4 said:
If restarting occurs exactly certain time period its firmware problem. otherwise battery or emmc fault.
Click to expand...
Click to collapse
I also think it's a firmware issue
SubwayChamp said:
Strange, your recovery doesn't have the option to update through the local directory.
Click to expand...
Click to collapse
Unfortunately not
SubwayChamp said:
It could be the best, probably it's a hardware issue that comes from the battery flex cable.
Click to expand...
Click to collapse
for this reason I sent it to the service center
Thank at all