Related
Hi Guys.
This is a Mediatek Helio X25 Redmi Pro and it came to me bricked from its owner who tried to root it the wrong way. I managed to flash an official rom and bring it back to life but as apparently is the case with these phones, the nvram has been corrupted/rewritten and there's no Imei numbers on the phone, which means no calls and stuff. WiFi works fine. I've already had permission to unlock the bootloader but obviously I can't do anything about it since the software won't ID the device. I believe I might be able to flash a backup of nvram.bin, but I don't have one from this phone, which is why I am posting this here, hoping that maybe one of you can help me by sending me a copy of his own Redmi Pro nvram.bin file. Of course I only need it to get the thing back in the system, after which I can unlock it and use the original Imei numbers. Or if someone has another suggestion, I would greatly appreciate it.
Thanks in advance.
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Binnylaw said:
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Click to expand...
Click to collapse
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
nsterjo said:
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
Click to expand...
Click to collapse
Tried this method?
http://en.miui.com/thread-411112-1-1.html
Sent from my Redmi Note 4 using Tapatalk
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Binnylaw said:
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Click to expand...
Click to collapse
I have tried maybe 3 different versions of Sp Flashtool, including this one. I usually get a timeout message. But I will try again. Is there any specifics I should observe regarding the mdb files I need to use? I have tried all the ones that come with the roms I've tried, but without luck.
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
No, you understood fine; it was me who typed SP Flashtool instead of SN Writer, which was what I meant. Everything else is as I wrote. I have tried 3 different versions of SN Writer, I connect fine and it starts the procedure following the same instructions you mentioned, but it stops half way, giving me an error message. I have tried different combinations of MDB and APDB files from several different ROMs I've downloaded, but they all fail. I'm not very familiar with these things but I can follow instructions and am quick to learn. Still, I have no idea why SN Writer or Maui Meta are not working. I tried to download an nvram.bin file I got from the internet with SP Flashtool, but it would not accept it as it was for Helio X20 I believe, which is why I was hoping someone would make available a copy of nvram.bin for this particular phone. I will also try to make a deepflash cable, hoping that might get me into EDL after which I can use MiFlash to reflash a new official Rom, but I don't know if it will work.
help please
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
Hi there, please can you tell me where I find the files (mdb and adb)? Are they somewhere on the phone's firmware? Or somewhere in the rom i flashed?
I'm a beginner having a very similar issue having flashed a rom in rescuing a bricked phone and now have invalid IMEI numbers.
Thanks so much
I changed my cell phone from A2017 to A2017U with no problem but ... now IMEI everything ok, unless the signal without no service appears whats wrong? Does anyone know something to solve this problem? Thank so much guys
What's ur phone model? If its the U model flash U modem if G or CN flash modem for their respective models
J0nhy said:
What's ur phone model? If its the U model flash U modem if G or CN flash modem for their respective models
Click to expand...
Click to collapse
I have an Axon 7 Chinese version I changed to the A2017U version android 7.1.1
Senik said:
I have an Axon 7 Chinese version I changed to the A2017U version android 7.1.1
Click to expand...
Click to collapse
You'll have to install ch modem im pretty sure you can find it around the forums
J0nhy said:
You'll have to install ch modem im pretty sure you can find it around the forums
Click to expand...
Click to collapse
where I find a modem that works, I searched the forum all the way down trying to see one that works. I did not install it because I do not know the right one to install, because mine was a Chinese version to get an area in the version with a U variant. Do you have a correct link?
Senik said:
where I find a modem that works, I searched the forum all the way down trying to see one that works. I did not install it because I do not know the right one to install, because mine was a Chinese version to get an area in the version with a U variant. Do you have a correct link?
Click to expand...
Click to collapse
https://androidfilehost.com/?w=files&flid=148464
Last one in the list...
joaste said:
https://androidfilehost.com/?w=files&flid=148464
Last one in the list...
Click to expand...
Click to collapse
Forgive me for asking so many questions, but this topic is good so that other people with this problem try to solve it too, I under which of the files?
Senik said:
Forgive me for asking so many questions, but this topic is good so that other people with this problem try to solve it too, I under which of the files?
Click to expand...
Click to collapse
Most people have searched and found the modem files. They are mentioned in many of the ROM threads.
As said, the last one in the list: A2017_N_Modem.zip.
Good luck.
joaste said:
https://androidfilehost.com/?w=files&flid=148464
Last one in the list...
Click to expand...
Click to collapse
joaste said:
Most people have searched and found the modem files. They are mentioned in many of the ROM threads.
As said, the last one in the list: A2017_N_Modem.zip.
Good luck.
Click to expand...
Click to collapse
I'm on android 7.1.1 I tried the last version b19 of mivafor, it did not work for twrp because when I start the system it hangs on the black screen of unlocking the bootloader
Senik said:
I'm on android 7.1.1 I tried the last version b19 of mivafor, it did not work for twrp because when I start the system it hangs on the black screen of unlocking the bootloader
Click to expand...
Click to collapse
Sorry, but you are not very clear on your issue. A modem file will not prevent you from booting.
If you flashed B19, which I believe is for the A2017U, did you also flash a universal bootloader? I believe this will be necessary. Also, how did you flash it?
You'll need to say what exactly your phone is (A2017, A2017U, A2017G), confirm your booltoader was unlocked already (I suppose it was), what state you phone is in now, and what you flashed already.
Then perhaps someone who understands your situation can help you.
joaste said:
Sorry, but you are not very clear on your issue. A modem file will not prevent you from booting.
If you flashed B19, which I believe is for the A2017U, did you also flash a universal bootloader? I believe this will be necessary. Also, how did you flash it?
You'll need to say what exactly your phone is (A2017, A2017U, A2017G), confirm your booltoader was unlocked already (I suppose it was), what state you phone is in now, and what you flashed already.
Then perhaps someone who understands your situation can help you.
Click to expand...
Click to collapse
I bought it in banggood it's a 2017 4gb 128gb Chinese version, so I unlocked the bootloader, until then everything ok, I used the B19 \ A2017U_B19-NOUGAT_FULL_EDL miflash, this was the version I used to change the system from A2017 to A2017U. because when I start the system everything works well unless the area goes up, even with the chip says in the service, however I saw that it can solve this being and the Chinese and American networks are different. I installed the one that you sent me the link by twrp modem A2017 but when I start the system it is in the black screen of the message of the unlocked bootloader. hence I come back in TWRP and it works less the system starts
Senik said:
I bought it in banggood it's a 2017 4gb 128gb Chinese version, so I unlocked the bootloader, until then everything ok, I used the B19 \ A2017U_B19-NOUGAT_FULL_EDL miflash, this was the version I used to change the system from A2017 to A2017U. because when I start the system everything works well unless the area goes up, even with the chip says in the service, however I saw that it can solve this being and the Chinese and American networks are different. I installed the one that you sent me the link by twrp modem A2017 but when I start the system it is in the black screen of the message of the unlocked bootloader. hence I come back in TWRP and it works less the system starts
Click to expand...
Click to collapse
Sorry, but it is still not clear to me. It is best to wait for someone like @Choose an username... to help, if he has the time.
Flash this ch modem through twrp https://androidfilehost.com/?fid=457095661767137840
I think this should solve ur problem
Senik said:
I bought it in banggood it's a 2017 4gb 128gb Chinese version, so I unlocked the bootloader, until then everything ok, I used the B19 \ A2017U_B19-NOUGAT_FULL_EDL miflash, this was the version I used to change the system from A2017 to A2017U. because when I start the system everything works well unless the area goes up, even with the chip says in the service, however I saw that it can solve this being and the Chinese and American networks are different. I installed the one that you sent me the link by twrp modem A2017 but when I start the system it is in the black screen of the message of the unlocked bootloader. hence I come back in TWRP and it works less the system starts
Click to expand...
Click to collapse
This is a mess. Do this:
Download an A2017 miflash package, just like the one you used to wreck your phone. Install it. If the signal works, you have two options:
-Update to official Oreo (it's out for Chinese phones). It should appear as an OTA. After updating DON'T change to other systems. Just stay with Oreo.
-If you still want to install the U system, don't update. take the A2017U package that you had downloaded, and delete the file called NHLOS.bin inside (might be called NON-HLOS.bin, I don't remember). Then flash it via MiFlash just as you did before
Choose an username... said:
This is a mess. Do this:
Download an A2017 miflash package, just like the one you used to wreck your phone. Install it. If the signal works, you have two options:
-Update to official Oreo if you don't want to install the u software (it's out for Chinese phones). It should appear as an OTA.
-If you still want to install the U system, take the A2017U package that you had downloaded, and delete the file called NHLOS.bin inside (might be called NON-HLOS.bin, I don't remember). Then flash it via MiFlash just as you did before
Click to expand...
Click to collapse
I decided the following way I made a backup of everything of the A2017U since the A2017 did not get wifi imei nothing .. so I did use the miflash and put the Chinese version B13, hence I installed the twrp since my bootloader was unlocked. I used the backup and started the system now everything works
Senik said:
I decided the following way I made a backup of everything of the A2017U since the A2017 did not get wifi imei nothing .. so I did use the miflash and put the Chinese version B13, hence I installed the twrp since my bootloader was unlocked. I used the backup and started the system now everything works
Click to expand...
Click to collapse
Good. If I were you I'd restore to B13 and update to Oreo, but if you're okay with the old U firmware then ok
Choose an username... said:
Good. If I were you I'd restore to B13 and update to Oreo, but if you're okay with the old U firmware then ok
Click to expand...
Click to collapse
when I go by twrp still appears the A2017U this can be a problem later? Even though you were the only one who understood me I speak Portuguese English for me is a bit complicated, but every day I struggle to improve. ah already there forgetting I appeared an update here of the b15 but being I updated more goes to the twrp screen I start the system and usually updates more when I go there in the mifavor to see if there is another update appears the old b15 to update again some solution?
Senik said:
when I go by twrp still appears the A2017U this can be a problem later? Even though you were the only one who understood me I speak Portuguese English for me is a bit complicated, but every day I struggle to improve. ah already there forgetting I appeared an update here of the b15 but being I updated more goes to the twrp screen I start the system and usually updates more when I go there in the mifavor to see if there is another update appears the old b15 to update again some solution?
Click to expand...
Click to collapse
I understood you, but I think it would be easier if you also wrote it in Portuguese. I talk Spanish, so I can also understand Portuguese.
So, you want to get Oreo? If you do, you have to use MiFlash to install the chinese B13 update. After that the update to Oreo should appear.
Choose an username... said:
I understood you, but I think it would be easier if you also wrote it in Portuguese. I talk Spanish, so I can also understand Portuguese.
So, you want to get Oreo? If you do, you have to use MiFlash to install the chinese B13 update. After that the update to Oreo should appear.
Click to expand...
Click to collapse
it does not update because of the twrp since the original recovery has no error in the update, how to remove twrp and return with original recovery mode?
Senik said:
it does not update because of the twrp since the original recovery has no error in the update, how to remove twrp and return with original recovery mode?
Click to expand...
Click to collapse
Didn't TWRP get replaced after you flashed the MiFlash images? If so, you can get the recovery.img from the B13 package and install it from TWRP (Install - install image
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
bothambhai said:
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Click to expand...
Click to collapse
just checking... are you using the edited princecomsy odin? http://d-h.st/gsDA or use the link here https://forum.xda-developers.com/att-s7-edge/help/princes-odin-t3545104
find the correct rom here https://forum.xda-developers.com/sprint-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3569834
just use files from one rom at a time. get good at that first. maybe you are careful but it really looks like you were guessing what goes where at the end of your post.
i just have tips on what helped me. passing along the info and the link.
epikroms said:
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
Click to expand...
Click to collapse
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
bothambhai said:
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
Click to expand...
Click to collapse
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
epikroms said:
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
Click to expand...
Click to collapse
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
bothambhai said:
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
Click to expand...
Click to collapse
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
epikroms said:
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
Click to expand...
Click to collapse
Thanks for your reply. If it is not too much can you please break down the steps a bit more because I don't want to guess and mess it up again and also if you could please kindly point me to the other thread as well so I can download the appropriate stuff from there and read a bit more about it. I am right now unable to use the phone with the sprint firmware on it on TMo, it's super annoying.
Thanks in advance.
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Did you get it sorted out? Hopefully you are on the rom and haven't bricked your device. I attached a picture so you could see that I am on what I say I am on.
epikroms said:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Click to expand...
Click to collapse
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
bothambhai said:
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
Click to expand...
Click to collapse
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
thats pretty interesting being on the binary 5 baseband and binary 4 rom. to clarify, you were on the binary 5 rom and reverted? or were you on the baseband 4 and upgraded just the baseband? thanks for the info.
epikroms said:
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
Click to expand...
Click to collapse
I odined the AP_Nougat_S7_Edge_EngBoot.tar.md5 then ran the root.bat file from Nougat_S7_Root_2_82_All_Carriers_V2 , I chose the options to install the fingerprint fix and install the root without any gpu tweaks. I watched the whole process complete and the cmd prompt close, my phone never asked my permission to ALLOW anything, everything was on the computer. I ran the root.bat from cmd as an administrator and the program ran evidently because it asked me about the fingerprint fix and root with or without tweaks etc. I noticed the phone reboot and there was a notification, the phone was rooted but no SU and flashwire says no root access. I tried it back from square one a couple of tries more right back from flashing stock sprint firmware and trying the whole rooting process again, same results except the next two times the phone doesn't reboot after running the root.bat file. I notice now when the phone boots up there is a sign saying "CUSTOM" beneath the samsung logo on the screen. I don't know where I am going wrong in the process though. I don't know if it is because I am on the binary 5 however I also read somewhere that people have been successful in rooting their binary 5 sprint S7 edges. I have rooted many devices before and installed roms etc, this has been, by far, the most perplexing phone in every which way.
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
epikroms said:
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
Click to expand...
Click to collapse
Bummer about your phone. On a glad note I managed to root and flash my phone and everything works great now. I was taking the hard nerdy way to do it by running cmd as an administrator and having that run the root.bat file. I read somewhere else you could just double click the file and it worked for me . From there on the aroma part was pretty straightforward. I am grateful to you for pointing me in this direction and breaking it down for me, I seriously doubted me being able to achieve this on my binary 5 phone but it turned out to be smooth.
I do wish you the best and thanks once again.
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Wifi works, but sim = 0
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
Thank you soo very much. you are the best, I followed your instructions step by step and my phone wifi is working as charm. my phone is alive now. Thanks a ton again.
-Bimlesh
colegui said:
Wifi works, but sim = 0
Click to expand...
Click to collapse
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
dmbardal said:
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
Click to expand...
Click to collapse
I'm trying some methods but I have not luck yet.
colegui said:
I'm trying some methods but I have not luck yet.
Click to expand...
Click to collapse
I managed to fix the WiFi and SIM (no imei).
Just flash persist.img if you only have the WiFi-issue.
There's a somewhat complicated guide here in the forums as well. Just google "mi a1 imei fix xda".
I'll help you tomorrow if you cant fix it.
dmbardal said:
I managed to fix the WiFi and SIM (no imei).
Just flash persist.img if you only have the WiFi-issue.
There's a somewhat complicated guide here in the forums as well. Just google "mi a1 imei fix xda".
I'll help you tomorrow if you cant fix it.
Click to expand...
Click to collapse
I'm fixing imei downgrade to 7.8.23 and repair imei with rbsoft tool, but when I upgrade to oreo with OTA, imeo=0 again....
I'm trying again other method....https://forum.xda-developers.com/mi-a1/help/efs-partition-eraised-boot-t3753619
dmbardal said:
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
Click to expand...
Click to collapse
Here is solution: : How to restore IMEI permanently after using factory flash
I have the same problem with IMEI, the fix is permanent.
After the repair can be uploaded any rom, including Oreo .
I also twisted up my IMEI. When I tried to downgrade to 7.8.23 it was boot looping. I was trying to solve it for 6 straight hours. Eventually, somehow the phone became unable to boot into fastboot (or anything else) for no reason. (a random shutdown occured during fastboot mode while no command was given). I had to turn to the Xiaomi service, since nothing could be done with the phone. Guess I'll have to use my old nokia flip mobile for 2-3 weeks.
coda00 said:
I also twisted up my IMEI. When I tried to downgrade to 7.8.23 it was boot looping. I was trying to solve it for 6 straight hours. Eventually, somehow the phone became unable to boot into fastboot (or anything else) for no reason. (a random shutdown occured during fastboot mode while no command was given). I had to turn to the Xiaomi service, since nothing could be done with the phone. Guess I'll have to use my old nokia flip mobile for 2-3 weeks.
Click to expand...
Click to collapse
Sorry I cant posting outside links,
You can try EDL mode:
solution how boot EDL mode via ADB or fastboot: link>> 99mediasector.com/edl-mode-boot-edl-mode-xiaomi-devicesI think this will not work for youBut you can try EDL:via Deep Flash Cable (how quickly make Deep Flash Cable): link>> en.miui.com/thread-310325-1-1.htmlorvia disassembly Mi A1 (Guide to Flash Bricked Mi A1): link>> en.miui.com/thread-1680467-1-1.html
Excellent
Ecoda00
Click to expand...
Click to collapse
amazing bro Thanks, i work fine for me...
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
Now that my wifi issue is solved, can I delete the persist.img from my device? Please advice.
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
pooniaprashant said:
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
Click to expand...
Click to collapse
Great, so now im tired of resurrection rom, want to go back stock, and since i didn't backup previously my persist img, i'm done with wifi?
seriously, why did i flashed the damn rom. What options do i have now? (thanks for the warning)
---------- Post added at 21:14 ---------- Previous post was at 20:15 ----------
pooniaprashant said:
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
Click to expand...
Click to collapse
Oh man, thank you so so much!! I used Persist Resurrector. and i'm back on wifi. really, thanks so much!!!!
amithiel said:
Great, so now im tired of resurrection rom, want to go back stock, and since i didn't backup previously my persist img, i'm done with wifi?
seriously, why did i flashed the damn rom. What options do i have now? (thanks for the warning)
---------- Post added at 21:14 ---------- Previous post was at 20:15 ----------
Oh man, thank you so so much!! I used Persist Resurrector. and i'm back on wifi. really, thanks so much!!!!
Click to expand...
Click to collapse
Can you please let me know the steps you did with Persist Resurrector or the link which has the steps? Thanks!
Bimlesh1681 said:
Can you please let me know the steps you did with Persist Resurrector or the link which has the steps? Thanks!
Click to expand...
Click to collapse
Sure, here you go: https://forum.xda-developers.com/mi-a1/how-to/tool-persist-resurrector-v1-0-0-0-t3781095
Edit: But you need to have you original persist file
Thank you so much, Bro. You saved my day. I am getting the similar problem. And ended up flashing multiple ROMs. but nothing worked out until I found your post.
i used this tool to solve wifi issue.
while using this tool make sure you enable USB debugging or it won't work.
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
I am on TWRP and using custom ROM( DOT OS). DO I have to go to fastboot and flash the firmware?
infuerano said:
I am on TWRP and using custom ROM( DOT OS). DO I have to go to fastboot and flash the firmware?
Click to expand...
Click to collapse
try flashing the latest void kernel.
Flashed A2017U b35 Nougat 7.1.1 on a2017 Chinese , USB to PC Hangs (should Restart to work)
Most Important is 2 Sim Showing No Service and when trying to Make A call Saying (Turn Off Airplane Mode to Make A Call)
Despite it Closed , SIM CARD Working on Other Device !!!
Not 100% sure, but it could have something to do with having the wrong radios on the US firmware.
Sidenote, where did you get the B35 update, would you mind sharing it?
KH_Lionheart said:
Not 100% sure, but it could have something to do with having the wrong radios on the US firmware.
Sidenote, where did you get the B35 update, would you mind sharing it?
Click to expand...
Click to collapse
It's official Nougat, literally nothing special
I think someone will upload the U files in some time anyways
Right, but what is special is that OTA is the only way it was put out. ZTE never made it available for download from the support page from what I understand so no one seems to actually have the usable firmware available to download in the way others have copies of the official firmware from ZTE support page. Plus since he has the Chinese model it means he probably didn't get it OTA and has a flash able file that he could share.
KH_Lionheart said:
Not 100% sure, but it could have something to do with having the wrong radios on the US firmware.
Sidenote, where did you get the B35 update, would you mind sharing it?
Click to expand...
Click to collapse
I Missed it but this file name (A2017U_B32_NOUGAT_FULL_EDL) .zip , i extracted it and flashed by mi-flash
Mohamed.Rady2017 said:
I Missed it but this file name (A2017U_B32_NOUGAT_FULL_EDL) .zip , i extracted it and flashed by mi-flash
Click to expand...
Click to collapse
at all , thanks for rebly ,kindly ,need to install by mi-flash A2017U_OREO_FULL_EDL as i have problem to unlock with boot-loader (twrp) and unlike to root my device