Hi. I have a A5 2017. I recently changed from the Russian 7.0 to the German Rom and the baseband and also the imei disappeared. I've got ROMs from all the sites and I'm still the same. Any solution?
I can´t have root. I can not install twrp. I have the error only official released binaries ...
PS: I can not change the bootloader. I have the error sw rev ...
I can only flash Ap.The 4 files together I can not
I can install the 4 files + pit but at the moment of starting the mobile it takes me to the recovery and later says things like ...:
- / efs invalid argument
-dm-verity fail ...
Any solution? I'm desperate
deleted
DaniPS2002 said:
Hi. I have a A5 2017. I recently changed from the Russian 7.0 to the German Rom and the baseband and also the imei disappeared. I've got ROMs from all the sites and I'm still the same. Any solution?
I can´t have root. I can not install twrp. I have the error only official released binaries ...
PS: I can not change the bootloader. I have the error sw rev ...
I can only flash Ap.The 4 files together I can not
I can install the 4 files + pit but at the moment of starting the mobile it takes me to the recovery and later says things like ...:
- / efs invalid argument
-dm-verity fail ...
Any solution? I'm desperate
Click to expand...
Click to collapse
The issue seems to be a combination of incorrect firmware and bad /Efs partition..
The dm-verity issue is because you haven't flashed the correct firmware.
The EFS error may also be erroneous, but if you've been messing with the wrong firmware and PIT files it's possible you've caused this error by messing up your partition structure and corrupting the EFS partition.
You really need to obtain the correct firmware for your region and possibly flash it with the PIT file if you've messed up your partition structure.
flozge said:
Hi try to root your phone with Kingroot and install TWRP via TWRP app
EDIT: Have you enabled OEM Unlock in Developer Options?
Click to expand...
Click to collapse
Hello! Thanks for your answer. I'm on Android 7.0 and I remember that kingroot no longer worked. I have the oem unlock option enabled. Now my phone has turned on but the wifi and fingerprints work partially. The system is unusable after 15 minutes of being used. It is progressively slowing down
ashyx said:
The issue seems to be a combination of incorrect firmware and bad /Efs partition..
The dm-verity issue is because you haven't flashed the correct firmware.
The EFS error may also be erroneous, but if you've been messing with the wrong firmware and PIT files it's possible you've caused this error by messing up your partition structure and corrupting the EFS partition.
You really need to obtain the correct firmware for your region and possibly flash it with the PIT file if you've messed up your partition structure.
Click to expand...
Click to collapse
Hi. Thank you very much for your help. My phone is an Italian version and I decided to change the firmware to the Russian version and since then the phone has generated all those errors. I would appreciate very much if you could give me a solution to this problem. Thank you
DaniPS2002 said:
Hi. Thank you very much for your help. My phone is an Italian version and I decided to change the firmware to the Russian version and since then the phone has generated all those errors. I would appreciate very much if you could give me a solution to this problem. Thank you
Click to expand...
Click to collapse
Which Italian firmware are you trying to flash?
ashyx said:
Which Italian firmware are you trying to flash?
Click to expand...
Click to collapse
This. A520FXXU2BQH4/A520FVFG2BQH2 on 7.0 3 aug
DaniPS2002 said:
This. A520FXXU2BQH4/A520FVFG2BQH2 on 7.0 3 aug
Click to expand...
Click to collapse
Can you post a screen shot of the device screen after flashing the whole firmware?
ashyx said:
Can you post a screen shot of the device screen after flashing the whole firmware?
Click to expand...
Click to collapse
Let me see you. The phone now I have it working. That is, I had to install an generic a520f efs.tar for odin so that the system could start(this efs folder is empty obviously) Now what I'm looking for is how to restore the imei and in the process remove system crashes * wifi forget passwords, fingerprints do not work ... and the system does not work or does not respond within 15 minutes. The efs.tar that I have gotten makes verifying the DM verity successful only the first time. Already the second time you access the recovey I have the error dm verity error. I feel the misunderstanding
DaniPS2002 said:
Let me see you. The phone now I have it working. That is, I had to install an generic a520f efs.tar for odin so that the system could start(this efs folder is empty obviously) Now what I'm looking for is how to restore the imei and in the process remove system crashes * wifi forget passwords, fingerprints do not work ... and the system does not work or does not respond within 15 minutes. The efs.tar that I have gotten makes verifying the DM verity successful only the first time. Already the second time you access the recovey I have the error dm verity error. I feel the misunderstanding
Click to expand...
Click to collapse
Please send me the efs.tar
flozge said:
Please send me the efs.tar
Click to expand...
Click to collapse
This is the efs. Try it
EDIT:Flash in CP
DaniPS2002 said:
This is the efs. Try it
EDIT:Flash in CP
Click to expand...
Click to collapse
Thanks
DaniPS2002 said:
Let me see you. The phone now I have it working. That is, I had to install an generic a520f efs.tar for odin so that the system could start(this efs folder is empty obviously) Now what I'm looking for is how to restore the imei and in the process remove system crashes * wifi forget passwords, fingerprints do not work ... and the system does not work or does not respond within 15 minutes. The efs.tar that I have gotten makes verifying the DM verity successful only the first time. Already the second time you access the recovey I have the error dm verity error. I feel the misunderstanding
Click to expand...
Click to collapse
Guessing you made it work with only flashing the ap, and you still have the sw rev error, what you can do is download a XXUx being the last x the number of the device on the error, for instance, if the error is "Device 4 Binary 3" You want to flash an XXU4.
Good luck.
@DaniPS2002 I am waiting for a z3x box 29 crack when I have found one I tell you
flozge said:
@DaniPS2002 I am waiting for a z3x box 29 crack when I have found one I tell you
Click to expand...
Click to collapse
Perfect! Many thanks! Is there news about version 29? It is precisely the version that adds support to our model
DaniPS2002 said:
Perfect! Many thanks! Is there news about version 29? It is precisely the version that adds support to our model
Click to expand...
Click to collapse
It gives already 30 but our device is since 29 supported
flozge said:
It gives already 30 but our device is since 29 supported
Click to expand...
Click to collapse
News mate?
DaniPS2002 said:
News mate?
Click to expand...
Click to collapse
No but I think 3weeks or less is a crack available
Can someone give me an backup of the efs partiton with twrp of a520f please?
no need efs backup, since it is stored anywhere on stock rom.
if u get it, so you are good to go with odin.
Related
hi all
after installing custom ROM my phone imei has been changed so i am not able to make calls
and i am getting error message that says "not registered on network" I searched about that issues and found that changing imei may cause that problem so anyone can help me to restore original imei for my phone
the below youtube show steps to do it but my problem that am not able to access engineering mode
https://www.youtube.com/watch?v=VNGalucyFJc
please HELP ME !
do you have a backup of your EFS? if you have, follow what i did here.
http://forum.xda-developers.com/showthread.php?t=2055736&page=352
but i suggest you only do it IF you have a backup of your EFS. otherwise, it's up to you.
edong23 said:
do you have a backup of your EFS? if you have, follow what i did here.
http://forum.xda-developers.com/showthread.php?t=2055736&page=352
but i suggest you only do it IF you have a backup of your EFS. otherwise, it's up to you.
Click to expand...
Click to collapse
ah, no i don't have backup for EFS, :crying: what must i do?
ghost_j1 said:
ah, no i don't have backup for EFS, :crying: what must i do?
Click to expand...
Click to collapse
try flashing your official firmware through Odin. other users solve their imei problem by doing that. see also if you can access engineering mode with that official firmware.
edong23 said:
try flashing your official firmware through Odin. other users solve their imei problem by doing that. see also if you can access engineering mode with that official firmware.
Click to expand...
Click to collapse
i tried to flash it with an official firmware but thats does not help the imei still wrong and i am not able to access engineering mode too
any other suggestion or anyone can help
ghost_j1 said:
i tried to flash it with an official firmware but thats does not help the imei still wrong and i am not able to access engineering mode too
any other suggestion or anyone can help
Click to expand...
Click to collapse
lets wait for others specially those who are expert in android for some advice. I'm just an ordinary security guard so i can't help you much with your problem. what i have suggested you from my previous post was the last thing I did when my phone finally worked. for 4 days i been searching for solution because i also have an IMEI problem. i flash back to official rom, flash patched modem, flash other roms to no avail until such time when my phone doesn't boot because of broken partition :laugh:. if you still have warranty restore it back. if you're already out of warranty and you have money, you can it send it to service center.
P.S.
you can also try this if you have courage. i was able to make some secret codes work but i have'nt tried if it works with engineering mode by modifying hiddenmenu in /efs/carrier/hiddenmenu. use efs explorer to open hiddenmenu and change it to ON.save it and restart your phone and see if engineering mode work. remember that you have to be in official firmware and also rooted to do this. if its not working then you'll just have to wait for a much better solutions from devs.
Same question
I have the same problem, as owner of the thread. Any help?
"CF Auto root" after imei has been deleted. you have installed the fix: http://forum.xda-developers.com/showthread.php?t=2333216
Hello,
I have ran into a huge problem with my tab S and I have been trying to fix this problem for weeks on end. The problem is I can't seem to flash my tablets stock rom without it giving me some error message saying "invaild ext4 image". I have done some research and from what I've found I need the PIT file but I can't find it at all. I know you can extract the PIT file from your device but I don't have access to the OS right now, just ODIN and my custom recovery. The OS is 4.4.2 and the Version is T807PVPU1ANK1 before It messed up. I have also tried to flash a higher OS version like 6.0 to the device but every time I try I get a message that says "Image file too large 5000 > 54466" or something like that. The device was not rooted before it broke either. This tablet is very expensive so If someone could please provide me with the PIT file for this device I would greatly appreciate it. (Image below is what the error is)
irontaco1 said:
Hello,
I have ran into a huge problem with my tab S and I have been trying to fix this problem for weeks on end. The problem is I can't seem to flash my tablets stock rom without it giving me some error message saying "invaild ext4 image". I have done some research and from what I've found I need the PIT file but I can't find it at all. I know you can extract the PIT file from your device but I don't have access to the OS right now, just ODIN and my custom recovery. The OS is 4.4.2 and the Version is T807PVPU1ANK1 before It messed up. I have also tried to flash a higher OS version like 6.0 to the device but every time I try I get a message that says "Image file too large 5000 > 54466" or something like that. The device was not rooted before it broke either. This tablet is very expensive so If someone could please provide me with the PIT file for this device I would greatly appreciate it. (Image below is what the error is)
Click to expand...
Click to collapse
Post the link to the firmware and a screenshot of odin.
ashyx said:
Post the link to the firmware and a screenshot of odin.
Click to expand...
Click to collapse
Link to firmware: https://samsung-firmware.org/download/Galaxy Tab S 10.5/2q34/SPR/T807PVPU1ANK1/T807PSPT1ANK1/
Odin Screenshot:
View attachment 3889452
Thank you for assisting me!
irontaco1 said:
Link to firmware: https://samsung-firmware.org/download/Galaxy Tab S 10.5/2q34/SPR/T807PVPU1ANK1/T807PSPT1ANK1/
Odin Screenshot:
View attachment 3889452
Thank you for assisting me!
Click to expand...
Click to collapse
When Odin fails like that it usually means the firmware is not correct for your device.
It seems here you are trying to flash a very old kitkat firmware.
This may not be allowed by the bootloader if you are attempting to downgrade.
Try the firmware below. I also advise you upgrade your version of ODIN to at least 3.10.6
http://www.sammobile.com/firmwares/download/63988/T807PVPU1BOL3_T807PSPT1BOL3_SPR/
ashyx said:
When Odin fails like that it usually means the firmware is not correct for your device.
It seems here you are trying to flash a very old kitkat firmware.
This may not be allowed by the bootloader if you are attempting to downgrade.
Try the firmware below. I also advise you upgrade your version of ODIN to at least 3.10.6
http://www.sammobile.com/firmwares/download/63988/T807PVPU1BOL3_T807PSPT1BOL3_SPR/
Click to expand...
Click to collapse
Unfortunately I got the same results
Odin:
View attachment 3890264
I assure you that (SM-T807P) is the correct model number because I wrote it down and made sure it was correct. Unless you have the PIT file for the device I doubt I'll get it working again. It needs to be re-partitioned while the OS is installed because no matter what I flash I get the same error.
irontaco1 said:
Unfortunately I got the same results
Odin:
View attachment 3890264
I assure you that (SM-T807P) is the correct model number because I wrote it down and made sure it was correct. Unless you have the PIT file for the device I doubt I'll get it working again. It needs to be re-partitioned while the OS is installed because no matter what I flash I get the same error.
Click to expand...
Click to collapse
Pit file.
http://chomikuj.pl/WymianaLCD/GSM/FLASH/SAMSUNG/SM-T807P
ashyx said:
Pit file.
http://chomikuj.pl/WymianaLCD/GSM/FLASH/SAMSUNG/SM-T807P
Click to expand...
Click to collapse
First, thank you for finding the pit file for me. I flashed the firmware in Odin along with the pit file but this time I got a new error message I'm beginning to think this tablet is not going to recover now. I've tried three different firmwares one gave me the "invalid ext4 image" while other firmwares gave me the error message "Volume Size is too big 5120000 < 5929600"
irontaco1 said:
First, thank you for finding the pit file for me. I flashed the firmware in Odin along with the pit file but this time I got a new error message I'm beginning to think this tablet is not going to recover now. I've tried three different firmwares one gave me the "invalid ext4 image" while other firmwares gave me the error message "Volume Size is too big 5120000 < 5929600"
Click to expand...
Click to collapse
I would use Smartswitch or kies to download your firmware to ensure its correct.
Select firmware upgrade and type in your model and serial.
ashyx said:
I would use Smartswitch or kies to download your firmware to ensure its correct.
Select firmware upgrade and type in your model and serial.
Click to expand...
Click to collapse
I've already tried that method. Kies won't detect the device when I plug it in.
irontaco1 said:
I've already tried that method. Kies won't detect the device when I plug it in.
Click to expand...
Click to collapse
It doesn't need to detect it, just type in the model and serial and it will download the firmware.
ashyx said:
It doesn't need to detect it, just type in the model and serial and it will download the firmware.
Click to expand...
Click to collapse
Okay I know what the model is but I'm not sure what the serial is.
irontaco1 said:
Okay I know what the model is but I'm not sure what the serial is.
Click to expand...
Click to collapse
Its usually on a sticker on the back or on the box.
ashyx said:
Its usually on a sticker on the back or on the box.
Click to expand...
Click to collapse
I looked at the back and I didn't see anything but I took the back off and found this on the battery, is this it?
irontaco1 said:
I looked at the back and I didn't see anything but I took the back off and found this on the battery, is this it?
Click to expand...
Click to collapse
I don't think it is. I entered it in kies and it said it was wrong.
ashyx said:
Its usually on a sticker on the back or on the box.
Click to expand...
Click to collapse
I think I know why I get an error when I flash firmware now. The pit file I flashed to my tablet wasn't for the 10.5in version it was for the 7in model. I don't know if the 10.5in and 7in share the same pit file but if they don't then that's my problem.
irontaco1 said:
I don't think it is. I entered it in kies and it said it was wrong.
Click to expand...
Click to collapse
Thats the serial for the battery. Try downloading Samsung phone info. Im not sure if it gives the serial or not, cant remember.
Also not sure what you mean about the pit file, its definitely for the t807p?
ashyx said:
Thats the serial for the battery. Try downloading Samsung phone info. Im not sure if it gives the serial or not, cant remember.
Also not sure what you mean about the pit file, its definitely for the t807p?
Click to expand...
Click to collapse
I guess it is the right pit file I don't know. Where can I get this samsung phone info thing?
irontaco1 said:
I guess it is the right pit file I don't know. Where can I get this samsung phone info thing?
Click to expand...
Click to collapse
Play store.
ashyx said:
Play store.
Click to expand...
Click to collapse
I guess I forgot to mention I don't have access to the OS just download and recovery mode.
irontaco1 said:
I guess I forgot to mention I don't have access to the OS just download and recovery mode.
Click to expand...
Click to collapse
OIC. [emoji54]
You could always try flashing the custom rom made by DUHasianskillz with twrp.
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.
Tried everything. Searched through the webs for past couple of days. Everything failed.
Majority of articles are from times of Ancient Rome. None work and are outdated.
Reflashed stock with nand erase and pit file. Checked and failed.
Tried root related solutions? Checked and failed.
Searched modem file. Failed.
Downgrade to prev version? No longer plausible. Due to BIT.
I flashed and reflashed with odin numerious of times. Nothing. Useless. Absolutely useless.
did u solve it?
Did you guys find anything? I think I'm gonna go check at a repair shop for someone with the z3x box and hope for the best.
Mighty_Rearranger said:
Did you guys find anything? I think I'm gonna go check at a repair shop for someone with the z3x box and hope for the best.
Click to expand...
Click to collapse
any luck?
dronkit said:
any luck?
Click to expand...
Click to collapse
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.
Mighty_Rearranger said:
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.
Click to expand...
Click to collapse
no, its not possible because of the bit.... can you try using an old modem to see if it solves the problem?
applesucksLmao said:
no, its not possible because of the bit.... can you try using an old modem to see if it solves the problem?
Click to expand...
Click to collapse
You mean like flashing an older modem? How can I do that?
Mighty_Rearranger said:
You mean like flashing an older modem? How can I do that?
Click to expand...
Click to collapse
its the CP file in odin
try flashing one from may or august.. don't try november or newer
You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file
applesucksLmao said:
You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file
Click to expand...
Click to collapse
I'll get an older firmware from sammobile and get back to you if anything different happens. Just as a note, someone here on XDA said they were able to downgrade when using a Magisk altered ROM.
Edit: I found something similar on another samsung phone here on XDA: thread here.
Mighty_Rearranger said:
I'll get an older firmware from sammobile and get back to you if anything different happens. Just as a note, someone here on XDA said they were able to downgrade when using a Magisk altered ROM.
Edit: I found something similar on another samsung phone here on XDA: thread here.
Click to expand...
Click to collapse
Could you flash it with a magisk modified rom?
@Mighty_Rearranger maybe you could try flashing an android 12 gsi? https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/ I don't have the phone with me right now so I can't test it
applesucksLmao said:
You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file
Click to expand...
Click to collapse
OK I tried doing that and now phone is bootlooping with secure check fail md1img error, that's the anti-downgrade thing complaining. No luck down the downgrade hallway.
I think the only option is to wait for a possible solution from the Magisk people or check if a future update somehow fixes the problem.
Mighty_Rearranger said:
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.
Click to expand...
Click to collapse
how do you check them from recovery? I was able to see them once after a botched flashing, entering download mode, there was a "show barcode" option or something like that.
I have read in an older thread in this forum, some guy solved it by downgrading, but to a version which is impossible to downgrade to for us, because our phones already came with the AUJ4 firm, and acannot go back.
applesucksLmao said:
@Mighty_Rearranger maybe you could try flashing an android 12 gsi? https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/ I don't have the phone with me right now so I can't test it
Click to expand...
Click to collapse
what's the idea? there aren't any custom roms, are there?
or you mean this way it could be possible to downgrade?
dronkit said:
what's the idea? there aren't any custom roms, are there?
or you mean this way it could be possible to downgrade?
Click to expand...
Click to collapse
if someone manages to create twrp for a32 4g maybe there's a way back
applesucksLmao said:
if someone manages to create twrp for a32 4g maybe there's a way back
Click to expand...
Click to collapse
TWRP lets you bypass the binary version check?
Mighty_Rearranger said:
TWRP lets you bypass the binary version check?
Click to expand...
Click to collapse
i don't know probably, and we could get a backup from someone with a not fricked phone and edit it to our imeis
I have OnePlus 9 pro t mobile, I was using eu rom normally, when eu network problem gave, I returned to tmo via msm in hopes that the network problem would be solved. but i keep getting this error t mobile team They said that there is no problem, the network can be unlocked, please try again. , please help someone , i checked the imei on the back of the device and the same inside . If anyone has encountered this problem before, can you tell me the solution? Whatever the solution is, I'm ready to do it, I couldn't solve the problem no matter what I did, eu network didn't work, I tried custom rom, but the result is that I can't get the same network and I don't have a t mobile sim card. Please someone help with this. Is there any file that I can remove this lock on the computer? My English is a bit bad, sorry about that. I'm ready to give 50 euros to the person who can solve this problem, please help.
Under settings/about phone/status what do you see?
TheGhost1951 said:
Under settings/about phone/status what do you see?
Click to expand...
Click to collapse
selimo21 said:
View attachment 5814737
Click to expand...
Click to collapse
Have you tried going into settings/system and resetting network settings?
TheGhost1951 said:
Have you tried going into settings/system and resetting network settings?
Click to expand...
Click to collapse
yes i tried and no result
Something happened to the phone, now I'm getting this error, what happened? can someone help?
Search in threads for TMO non-halos.img and flash it in fastboot mode. It flashes the modem and radio for TMO
TheGhost1951 said:
Search in threads for TMO non-halos.img and flash it in fastboot mode. It flashes the modem and radio for TMO
Click to expand...
Click to collapse
I couldn't find the file you mentioned, can you help me? can you link the file
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com
Quick Google search
TheGhost1951 said:
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com
Quick Google search
Click to expand...
Click to collapse
I flashed it and the result is wrong, I still get the error you see above.
selimo21 said:
I flashed it and the result is wrong, I still get the error you see above.
Click to expand...
Click to collapse
Time to MSM to your original model number....
TheGhost1951 said:
Time to MSM to your original model number....
Click to expand...
Click to collapse
i did the result did not change , if i flash custom rom can i fix network eg pixel experience rom ?
How long was it working on Eu rom before it gave you a problem? Maybe you temporarily sim unlocked the phone for 30 days and that ran out?
OnePlus says you must go through tmobile to get it unlocked. Tmobile does need it on their network for a day or so to be able to unlock it. (They tried to do mine manually but there was no data for my phone and there is an exchange that takes place on their server so it has to be online).
Looks like the efs may be somewhat corrupt. Hope you backed up modemst1/modemst2 partitions like the conversion thread suggested you do. You'll want to flash these both back on and then problems should be resolved. You cannot use someone else's partitions, has to be yours.
MSM'ing will not help this situation. Need to unlock permanently using t-mobile's unlock in original ROM after you've restored those partitions. It blows an efuse when it does this, no custom rom can be used as a workaround.
I also had the same problem on OP9. It happened after playing with modemst partition.
joecool1029 said:
Looks like the efs may be somewhat corrupt. Hope you backed up modemst1/modemst2 partitions like the conversion thread suggested you do. You'll want to flash these both back on and then problems should be resolved. You cannot use someone else's partitions, has to be yours.
MSM'ing will not help this situation. Need to unlock permanently using t-mobile's unlock in original ROM after you've restored those partitions. It blows an efuse when it does this, no custom rom can be used as a workaround.
Click to expand...
Click to collapse
Unfortunately I don't have my own modem backups. but someone else has a backup, what can i do? please help me
ElitePotato said:
I also had the same problem on OP9. It happened after playing with modemst partition.
Click to expand...
Click to collapse
did you solve the problem? I have someone else's backup, do I have a chance to use it, please help
I have all the modem related imgs for A12 TMO if needed OP9P
TheGhost1951 said:
I have all the modem related imgs for A12 TMO if needed OP9P
Click to expand...
Click to collapse
Thank you very much for this. Finally, I'm thinking of taking a twrp backup and installing it. I've tried everything with modem backups and the result is unsuccessful I hope someone can fix this problem.
selimo21 said:
Something happened to the phone, now I'm getting this error, what happened? can someone help?
View attachment 5814789
Click to expand...
Click to collapse
Take ur SIM out then restart and connect to a US VPN and try again
L0ND0NB0Y said:
Take ur SIM out then restart and connect to a US VPN and try again
Click to expand...
Click to collapse
unfortunately i tried that too. this problem happened because i deleted modemst1 and modemst2 file in eu rom. I guess the tmo unlock application cannot read the phone's information so the unlock is refusing to bind.