Hello, since i flash Nougat Roms on my k3 i allways loose the imei.
I try to fix it with campheleon APP, but after this i loose the sim. Engineer mode is not possible. Can anyone help to fix this.
Thanks a lot
Peter
Since you know how to flash Rom, the first thing you do before flashing is to back up (Nandroid) of your Rom with atleast TWRP (especially the system, boot, pro info, Nvram, Protect etc) before flashing it's always there in the warning ⚠
If you did that just restore the Nvram, proinfo, protect partitions
Else, you'll have to try flash stuck Rom with SP flash tool (using firmware upgrade option under download)
Chamelophon could give you a temporary fix thou
Thank you sir.. but i want to get clarified about another thing..
Bolumstar said:
Since you know how to flash Rom, the first thing you do before flashing is to back up (Nandroid) of your Rom with atleast TWRP (especially the system, boot, pro info, Nvram, Protect etc) before flashing it's always there in the warning
If you did that just restore the Nvram, proinfo, protect partitions
Else, you'll have to try flash stuck Rom with SP flash tool (using firmware upgrade option under download)
Chamelophon could give you a temporary fix thou
Click to expand...
Click to collapse
I have lost imeis after flashing nogaut roms and then flashed stock rom using chamelophon app i restored imeis.. Now if i take a backup of nvram system pro info etc and flash custom roms and restore nvram proinfo etc.. Then can i not loose imeis again? Does it help now? Thank you
sandeepr3884 said:
I have lost imeis after flashing nogaut roms and then flashed stock rom using chamelophon app i restored imeis.. Now if i take a backup of nvram system pro info etc and flash custom roms and restore nvram proinfo etc.. Then can i not loose imeis again? Does it help now? Thank you
Click to expand...
Click to collapse
If you flash stock Rom with SP flash tool and after that your imei is not restored without using Chamelophon app then you have a bigger problem. Chamelophon app modifications are cleared once there's a factory reset or system wipe - its not a permanent fix.
If after flashing your stock Rom with SP flash tool and your imei is not valid then you have to use imei write tool to write your imei (works only on mtk devices)
Then use TWRP recovery to backup your Nvram and restore it anytime you flash nougat Roms.
If after flashing stock Rom and your imei is back then take a TWRP recovery back up of Nvram and restore it after flashing nougat Roms.
Hope I helped
Bolumstar said:
If you flash stock Rom with SP flash tool and after that your imei is not restored without using Chamelophon app then you have a bigger problem. Chamelophon app modifications are cleared once there's a factory reset or system wipe - its not a permanent fix.
If after flashing your stock Rom with SP flash tool and your imei is not valid then you have to use imei write tool to write your imei (works only on mtk devices)
Then use TWRP recovery to backup your Nvram and restore it anytime you flash nougat Roms.
If after flashing stock Rom and your imei is back then take a TWRP recovery back up of Nvram and restore it after flashing nougat Roms.
Hope I helped
Click to expand...
Click to collapse
But actually the thing is.. I flashed nougat rom and lost imei then flashed stock using sp flash too.. Didnt restore imei.. Then i used chamelephon.. It helped.. Now i am using "Stock rom imei working with help of chamelephon".. So now can i backup nvram etc and flash nougat rom? So that i dont loose my imei this time? I tried with sn write too but it says some meta default error.. So all i have is only chamelephon imei.. So Please help...
sandeepr3884 said:
But actually the thing is.. I flashed nougat rom and lost imei then flashed stock using sp flash too.. Didnt restore imei.. Then i used chamelephon.. It helped.. Now i am using "Stock rom imei working with help of chamelephon".. So now can i backup nvram etc and flash nougat rom? So that i dont loose my imei this time? I tried with sn write too but it says some meta default error.. So all i have is only chamelephon imei.. So Please help...
Click to expand...
Click to collapse
If you have any old TWRP backups then restoring from it could be the best option.
This is the reason we warn ⚠ make full backups before flashing anything.
The default stored information on some hidden partition has been altered or corrupted and there may not be much you can do than keep using Chamelophon (if it works well on Nougat)
You can try and download the latest RR 5.8.2 it has mtk engineering mode and very stable you can use to write imei too. But am not sure it stays permanently
Bolumstar said:
If you have any old TWRP backups then restoring from it could be the best option.
This is the reason we warn make full backups before flashing anything.
The default stored information on some hidden partition has been altered or corrupted and there may not be much you can do than keep using Chamelophon (if it works well on Nougat)
You can try and download the latest RR 5.8.2 it has mtk engineering mode and very stable you can use to write imei too. But am not sure it stays permanently
Click to expand...
Click to collapse
No sir.. Chamelophon is not working on nougat roms i think not maybe on custom roms actually i flashed the latest 5.8.2 rr beta 2 uploaded on 10/03/2017.. Mtk engineering mode is not working on rr 5.8.2 beta 2.. I dont have any previous backups now i am using stock with the help of chamelephon imei.. If i take a backup now with chamelphon restored imei.. Does it gonna help in nougat roms to restore imeis?
sandeepr3884 said:
No sir.. Chamelophon is not working on nougat roms i think not maybe on custom roms actually i flashed the latest 5.8.2 rr beta 2 uploaded on 10/03/2017.. Mtk engineering mode is not working on rr 5.8.2 beta 2.. I dont have any previous backups now i am using stock with the help of chamelephon imei.. If i take a backup now with chamelphon restored imei.. Does it gonna help in nougat roms to restore imeis?
Click to expand...
Click to collapse
There is mtk engineering mode in the RR 5.8.2 that am using but it doesn't have option to change imei.
Am sorry there may not be another way for now since there's no xposed Framework for nougat yet.
You may have to stick with Marshmallow for now.
Or buy another motherboard from Aliexpress
Bolumstar said:
There is mtk engineering mode in the RR 5.8.2 that am using but it doesn't have option to change imei.
Am sorry there may not be another way for now since there's no xposed Framework for nougat yet.
You may have to stick with Marshmallow for now.
Or buy another motherboard from Aliexpress
Click to expand...
Click to collapse
Thank you bro? for your valuable information. Finally i want to know if i flash marhsmellow custom custom rom to my device can it be possible not to loose imeis again? I mean do i loose my imeis after flashing marshmallow custom rom? Since i am using imeis with help of chamlephon app.. If i loose it again can i restore using any mobile app? On which rom mtk engineering mode is available? And is it possible to change imeis using mtk mode on my deive? Or is there any other solution for this problem? Please let me know.. Thank you
pba066 said:
Hello, since i flash Nougat Roms on my k3 i allways loose the imei.
I try to fix it with campheleon APP, but after this i loose the sim. Engineer mode is not possible. Can anyone help to fix this.
Thanks a lot
Peter
Click to expand...
Click to collapse
Download IMEI_MAKER.zip (to create a new IMEI file) then unzip the content of the folder (imei.exe) to a folder on your desktop
In command prompt, navigate to the imei.exe containing folder you just created on your desktop
NOTE
Code:
cd\ then Enter returns to root directory
cd.. then Enter goes up one directory
cd foldername then Enter navigates to a folder called foldername
A faster method is to open the imei.exe containing folder > Hold down Shift > Right-click on an empty space > Select "Open Command Window here"
When you're inside the imei folder in command prompt, type
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
eg
Code:
imei.exe 123456789111111 123456789111124
Press Enter
If both IMEIs you gave are of the correct format, a file named MP0B_001_NEW will be created. Rename it MP0B_001.
Now you can send it to the sd of your phone
Install ROM toolbox lite then go to root explorer
In root explorer, delete the existing MP0B_001 file (located @ device/data/nvram/md/NVRAM/NVD_IMEI) and replace with the one you just created
Long press the new MP0B_001, go to permissions and tick all 9 boxes at the top then select ok (don't tick special pernissions)
Restart your phone
Your SIMs should be detected, IMEI reflect and Baseband version change from unknown to what it should be.
Note that getting this done might not be this direct due to different scenarios but replacing the MP0B_001 file is the ultimate goal in order to fix the issue.
Download link:
[NOT ALLOWED FOR ME]
SEARCH ON GOOGLE !
Related
ISN'T NECESSARY MTK DROID TOOLS OR OTHER MTK TOOLS , JUST MTK ENGINEER MODE IN LP FIRMWARE
This way it’s permanent just if you don’t wipe nvram & nvdata partitions and work only on who have LP and MM Firmware + TWRP Recovery for LP Firmware
Disclaimer : I'm not responsable for any damage on your device , use my tutorial step by step and will result a success!
Click to expand...
Click to collapse
Go back to LP Firmware [trought SP FLash Tools],
Restore IMEI with MTK Engineer Mode,
Flash TWRP,
Wipe cache,
Backup nvram,
Restore backup of nvram,
Install stock recovery,
Wipe cache,
Update again to MM using OTA
After MM is booted up ,
You will see IMEI,
Reboot to Recovery [Stock]
Wipe cache,
Install TWRP 2.8.7-N (Download)
[Trought SP FLash Tools]
To install TWRP with success , after TWRP is flashed just reboot to recovery first!
If you reboot first to system , will replace twrp with stock recovery , and entrie operation need to repeat [ from installing twrp ]
READY , NOW YOU HAVE PERMANENT FIX IMEI FOR ALL DEVICES [MTK] WHICH HAVE LP & MM FIRMWARE + TWRP ON BOTH VERSIONS
IF YOU WILL DO FACTORY RESET , IMEI WILL BE STILL HERE , NO ERASE , 100% TESTED
IacobIonut-DW said:
ISN'T NECESSARY MTK DROID TOOLS OR OTHER MTK TOOLS , JUST MTK ENGINEER MODE IN LP FIRMWARE
This way it’s permanent just if you don’t wipe nvram & nvdata partitions and work only on who have LP and MM Firmware + TWRP Recovery for LP Firmware
Go back to LP Firmware [trought SP FLash Tools],
Restore IMEI with MTK Engineer Mode,
Flash TWRP,
Wipe cache,
Backup nvram,
Restore backup of nvram,
Install stock recovery,
Wipe cache,
Update again to MM using OTA
After MM is booted up ,
You will see IMEI,
Reboot to Recovery [Stock]
Wipe cache,
Install TWRP 2.8.7-N (Download)
[Trought SP FLash Tools]
To install TWRP with success , after TWRP is flashed just reboot to recovery first!
If you reboot first to system , will replace twrp with stock recovery , and entrie operation need to repeat [ from installing twrp ]
READY , NOW YOU HAVE PERMANENT FIX IMEI FOR ALL DEVICES [MTK] WHICH HAVE LP & MM FIRMWARE + TWRP ON BOTH VERSIONS
IF YOU WILL DO FACTORY RESET , IMEI WILL BE STILL HERE , NO ERASE , 100% TESTED
Click to expand...
Click to collapse
Thanks for your effort IacobIonut-DW, and it works great, but only if you decide to use Blu's Stock Marshmallow ROM.
The bad news is that the problem is still present if one goes beyond stock and try to install any other custom ROM like AEX or Resurrection Remix ROMs.
I think that most people here want to skip using the stock (while rooted) ROM and experiment with other ROMs like AEX and RR.
Any pointers would be welcomed!
In the meantime, I am on MM Stock, Rooted and debloated.
Try to use SPlus LP and MM Firmware
IacobIonut-DW said:
Try to use SPlus LP and MM Firmware
Click to expand...
Click to collapse
Thanks but I don't quite understand.
After that, will I be able to install RR or AEX?
Rayan said:
Thanks but I don't quite understand.
After that, will I be able to install RR or AEX?
Click to expand...
Click to collapse
yes
Do same operation but with S Plus Firmware
IacobIonut-DW said:
yes
Do same operation but with S Plus Firmware
Click to expand...
Click to collapse
Great, will do and post results [emoji106]
Sent from my VIVO XL using Tapatalk
IacobIonut-DW said:
READY , NOW YOU HAVE PERMANENT FIX IMEI FOR ALL DEVICES [MTK] WHICH HAVE LP & MM FIRMWARE + TWRP ON BOTH VERSIONS
IF YOU WILL DO FACTORY RESET , IMEI WILL BE STILL HERE , NO ERASE , 100% TESTED
Click to expand...
Click to collapse
Thank you very much!!! I have also checked it and it works perfectly !!!!
msellaro said:
Thank you very much!!! I have also checked it and it works perfectly !!!!
Click to expand...
Click to collapse
Quite honestly I've been swamped with other things and have not tried this yet.
So you're saying that you have AEX running (or other custom ROM) with your Blu Vivo XL without losing both IMEI?
I'll try it out later, but just checking in the meantime
Rayan said:
Quite honestly I've been swamped with other things and have not tried this yet.
So you're saying that you have AEX running (or other custom ROM) with your Blu Vivo XL without losing both IMEI?
I'll try it out later, but just checking in the meantime
Click to expand...
Click to collapse
It works very well and I was really surprised at the speed with which the operating system loads. Although surely much is because I have not installed the gapps yet.
Awesome to know!
But I'll have to ask which S Plus rom variant did you use? I found three different ones with different numbers. ?
Also what Custom ROM did you installed?
Thanks in advance!
Rayan said:
Awesome to know!
But I'll have to ask which S Plus rom variant did you use? I found three different ones with different numbers. ?
Also what Custom ROM did you installed?
Thanks in advance!
Click to expand...
Click to collapse
XOS V2
Sent from my Blu Vivo XL using XDA Labs
Hmmm, even after trying all that's been said here, I simply can't keep the IMEI functions after flashing any custom ROM. I know my way around custom roms since the XDA days but this one is really getting on my nerves... U_U
Nevermind I have it working now!!!... With your feedback I was able to come up with a different path to get the firmware directory in place without corrupting the ROM.
Rayan said:
Nevermind I have it working now!!!... With your feedback I was able to come up with a different path to get the firmware directory in place without corrupting the ROM.
Click to expand...
Click to collapse
Please tell us how you did. I tried to repeat the process and this time it didnt work for me. Thank you!!!
Sorry for late reply!
I have moved to an LG G6 since and now I don't recall the exact steps! U_U
Restore IMEI with MTK Engineer Mode, i dont undertand is there any video tutorial?
Hello guys, how can I fix my BLU VIVO XL, its showing invalid imei, the baseband got wiped off after hard resetting the phone, pls I really need y'all to help me. can Gionee S plus stock ROM work on this phone? cos I've downloaded the stock ROM & flash the phone still it didn't work.
Youngklassic said:
Hello guys, how can I fix my BLU VIVO XL, its showing invalid imei, the baseband got wiped off after hard resetting the phone, pls I really need y'all to help me. can Gionee S plus stock ROM work on this phone? cos I've downloaded the stock ROM & flash the phone still it didn't work.
Click to expand...
Click to collapse
Did you ever recover your imei and baseband...I just did that myself and it was to easy to fix...
I have faced imei = 0 on 3 phones till date and hence I'm **** scared of it.
How to backup imei ?
I mean how to backup the following-
1. EFS partition
2. Modemst1 (imei 1)
3. Modemst2 (imei 2)
Also is there any solution as of now to imei=0 if there is no backup saved? Also will a twrp backup of all available partition help?(because it didn't help on OnePlus 2)
Did you root?
Sent from my Moto G (5S) Plus using Tapatalk
tbiwalkar said:
I have faced imei = 0 on 3 phones till date and hence I'm **** scared of it.
How to backup imei ?
I mean how to backup the following-
1. EFS partition
2. Modemst1 (imei 1)
3. Modemst2 (imei 2)
Also is there any solution as of now to imei=0 if there is no backup saved? Also will a twrp backup of all available partition help?(because it didn't help on OnePlus 2)
Click to expand...
Click to collapse
I assume you flashed a custom ROM because I have experienced it too. I have IMEI = 0. If you find a solution, please do share. We need someone who will share us a working EFS partition.
Thanks and best regards,
Geb
tbiwalkar said:
I have faced imei = 0 on 3 phones till date and hence I'm **** scared of it.
How to backup imei ?
I mean how to backup the following-
1. EFS partition
2. Modemst1 (imei 1)
3. Modemst2 (imei 2)
Also is there any solution as of now to imei=0 if there is no backup saved? Also will a twrp backup of all available partition help?(because it didn't help on OnePlus 2)
Click to expand...
Click to collapse
I am new to this device but i know modemst1 and modemst2 is not IMEI thing and you cannot backup it, or it is not needed..
And also don't know if which partition is correct for backup of IMEI. But you can try restoring all partitions.
gebcruz06 said:
I assume you flashed a custom ROM because I have experienced it too. I have IMEI = 0. If you find a solution, please do share. We need someone who will share us a working EFS partition.
Thanks and best regards,
Geb
Click to expand...
Click to collapse
Have you tried flashing stock firmware ?
For your information, EFS contains backup of IMEI for individual devices, so why do you think someone will give you their IMEI ?
I have got this device before 2 days, i will see what i can do for you guys, but after 5th February.. Wait till, and try to flash stock...
____Mdd said:
I am new to this device but i know modemst1 and modemst2 is not IMEI thing and you cannot backup it, or it is not needed..
And also don't know if which partition is correct for backup of IMEI. But you can try restoring all partitions.
Have you tried flashing stock firmware ?
For your information, EFS contains backup of IMEI for individual devices, so why do you think someone will give you their IMEI ?
I have got this device before 2 days, i will see what i can do for you guys, but after 5th February.. Wait till, and try to flash stock...
Click to expand...
Click to collapse
I did. Tried so many times even with different versions of the stock firmware, to no avail. Thanks for your kind intention. Please share with us if you have found a way. thanks.
same problem here bro!!
i am able to see efs partition in twrp but wat to do to restore imei
I'm so happy I finally managed to restore my imei .I just flash validus rom 8.1 beta and imei was back
Sri Datta said:
I'm so happy I finally managed to restore my imei .I just flash validus rom 8.1 beta and imei was back
Click to expand...
Click to collapse
Which version/ build date of the validus rom? Thanks.
Sri Datta said:
I'm so happy I finally managed to restore my imei .I just flash validus rom 8.1 beta and imei was back
Click to expand...
Click to collapse
Thanks, bro
Doing this recovered my IMEI
Bro, I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. Make TWRP backup of your EFS partition
3. Re-flash stock ROM
4. Re-install TWRP and restore your EFS backup
Special thanks to @Sri Datta, @premaca and GZOSP/ Validus devs
gebcruz06 said:
Thanks, bro
Doing this recovered my IMEI
Bro, I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. Make TWRP backup of your EFS partition
3. Re-flash stock ROM
4. Re-install TWRP and restore your EFS backup
Special thanks to @Sri Datta, @premaca and GZOSP/ Validus devs
Click to expand...
Click to collapse
Bro r u an indian,if yes then despite restoration of imei jio sim won't work.also can u tell me which version of firmware is for Indian varient??
gebcruz06 said:
Thanks, bro
Doing this recovered my IMEI
Bro, I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. Make TWRP backup of your EFS partition
3. Re-flash stock ROM
4. Re-install TWRP and restore your EFS backup
Special thanks to @Sri Datta, @premaca and GZOSP/ Validus devs
Click to expand...
Click to collapse
jio users must run these commands after flashing validus(run only if jio is not working,and run after 1st boot.)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
gebcruz06 said:
Thanks, bro
Doing this recovered my IMEI
Bro, I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. Make TWRP backup of your EFS partition
3. Re-flash stock ROM
4. Re-install TWRP and restore your EFS backup
Special thanks to @Sri Datta, @premaca and GZOSP/ Validus devs
Click to expand...
Click to collapse
volte doesn't work with this method
Sri Datta said:
volte doesn't work with this method
Click to expand...
Click to collapse
You surely wait for official android 8
In G5 plus thread I searched fix imei And also volte doesn't work
Sent from my Moto G5S Plus using XDA Labs
gebcruz06 said:
Thanks, bro
Doing this recovered my IMEI
Bro, I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. Make TWRP backup of your EFS partition
3. Re-flash stock ROM
4. Re-install TWRP and restore your EFS backup
Special thanks to @Sri Datta, @premaca and GZOSP/ Validus devs
Click to expand...
Click to collapse
bro my SIM CARD its dead (i think i have the same problem you had) can you help me please ? i tried roms 7.1.2, 8.0, 8.1
also when i flash stock rom all comands works but ERASE CLOGO AND ERASE CUSTOMIZE FAILED and the phone restart but no sim card
i found a old backup and restored with twep now i have IMEI thank you so much!
Draaaven said:
bro my SIM CARD its dead (i think i have the same problem you had) can you help me please ? i tried roms 7.1.2, 8.0, 8.1
also when i flash stock rom all comands works but ERASE CLOGO AND ERASE CUSTOMIZE FAILED and the phone restart but no sim card
Click to expand...
Click to collapse
Have you tried popping your sim in another phone? Please check imei, *#06#. If it is 0 then your phone will not be recognized by any network. Clogo and customize may show failure msg but it doesn't do anything. I suggest you try first the flashing of stock rom for your variant. Remove sim before flashing and pop it after 1st boot. Check your imei at once. If the above link I mentioned didn't work, try the latest lineage 15.1 build. It has updated rild libs. You can also get signal there and your imei. Once booted in it, reflash modem, clear modemst1 and modemst2, then reboot. Take an efs backup in twrp after.
gebcruz06 said:
Have you tried popping your sim in another phone? Please check imei, *#06#. If it is 0 then your phone will not be recognized by any network. Clogo and customize may show failure msg but it doesn't do anything. I suggest you try first the flashing of stock rom for your variant. Remove sim before flashing and pop it after 1st boot. Check your imei at once. If the above link I mentioned didn't work, try the latest lineage 15.1 build. It has updated rild libs. You can also get signal there and your imei. Once booted in it, reflash modem, clear modemst1 and modemst2, then reboot. Take an efs backup in twrp after.
Click to expand...
Click to collapse
thanks my SIM worked perfect in other device and my IMEI was "0"
so i flashed stock 26.116-64 then restored efs from a old backup now all good :laugh::good:
My jio call service is not working however my internet connection is just fine.(no VoLTE). Can someone help me
Gimmmi said:
My jio call service is not working however my internet connection is just fine.(no VoLTE). Can someone help me
Click to expand...
Click to collapse
Apparently there is no solution for this go to service centre m only they can fix
Sri Datta said:
Apparently there is no solution for this go to service centre m only they can fix
Click to expand...
Click to collapse
never mind
Hello ... Any ideas on recovering IMEI after successful root of Note9 ?
IMEI currently unknown (both), TWRP shows empty EFS folder (should i see these files?), Software Baseband is UNKNOWN too.
Software factory wipe done with no effect, OEM unlock is unlocked (and not greyed out).
Thanks
Just wondering if anyone has recovered from this ?
did you read all of dr ketans thread on root?
go to general discussion section / dr ketan oem fix and root and simply do a search in that thread for imei
edit
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143
basicaly you flash back stock firmware and try again.
bober10113 said:
did you read all of dr ketans thread on root?
Click to expand...
Click to collapse
do let us know the tread link
bober10113 said:
did you read all of dr ketans thread on root?
go to general discussion section / dr ketan oem fix and root and simply do a search in that thread for imei
edit
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143
basicaly you flash back stock firmware and try again.
Click to expand...
Click to collapse
nrah said:
do let us know the tread link
Click to expand...
Click to collapse
added link
Thanks for the link
I have been plowing through - i still can't work out how to backup the EFS before TWRP is installed.
Should the backup take place after TWRP is installed, before the first reboot (and before running the Dr's script) ??
nrah said:
Thanks for the link
I have been plowing through - i still can't work out how to backup the EFS before TWRP is installed.
Should the backup take place after TWRP is installed, before the first reboot (and before running the Dr's script) ??
Click to expand...
Click to collapse
restore back to stock and be sure everything works.
then flash twrp with odin and dont let phone reboot.
manualy reboot to recovery. using an external sd card backup EFS partition.
go to wipe menu and format data.
go to reboot menu and reboot back to recovery.
go to wipe menu and do a factory wipe, the default swipe right option.
now you have 2 choices:
either flash dr ketan method 1 root oem fix zip and stay on stock firmware.
or
flash dr ketan method 1 zip and then flash a custom rom.
then reboot. if no signal restore the backup of efs you made earlier.
bober10113 said:
restore back to stock and be sure everything works.
then flash twrp with odin and dont let phone reboot.
manualy reboot to recovery. using an external sd card backup EFS partition.
go to wipe menu and format data.
go to reboot menu and reboot back to recovery.
go to wipe menu and do a factory wipe, the default swipe right option.
now you have 2 choices:
either flash dr ketan method 1 root oem fix zip and stay on stock firmware.
or
flash dr ketan method 1 zip and then flash a custom rom.
then reboot. if no signal restore the backup of efs you made earlier.
Click to expand...
Click to collapse
I have been doing this, except for the additional step on the factory wipe that you pointed out - thanks.
But after three full rounds of rooting and trying to restore the EFS, i still have "unkown" and no Baseband information when i get to the end. When i return to the stock image, both Baseband & IMEI's are present.
I have backed up EFS/Baseband/Carrier configs/carrier images successfully and restored all 4 partitions. But IMEI does not return.
nrah said:
I have been doing this, except for the additional step on the factory wipe that you pointed out - thanks.
But after three full rounds of rooting and trying to restore the EFS, i still have "unkown" and no Baseband information when i get to the end. When i return to the stock image, both Baseband & IMEI's are present.
I have backed up EFS/Baseband/Carrier configs/carrier images successfully and restored all 4 partitions. But IMEI does not return.
Click to expand...
Click to collapse
are you on pie or oreo?
bober10113 said:
are you on pie or oreo?
Click to expand...
Click to collapse
8.1, Oreo .. was thinking of grabbing a ver9 image and giving it a go
nrah said:
8.1, Oreo .. was thinking of grabbing a ver9 image and giving it a go
Click to expand...
Click to collapse
did you try method 2 in dr ketans oem fix root hread?
also maybe try flashing a custom rom instead of being on stock and see if that works out for you.
but to think of it, believe your issue is kernel related. i think i remember reading something about it.
so after twrp and data format , reboot back to twrp and oem fix, dont reboot to OS yet. try flashing endurance kernel or tgp kernel. just be sure to take the appropriate oreo or pie version depending on what android os version you go on.
bober10113 said:
did you try method 2 in dr ketans oem fix root hread?
also maybe try flashing a custom rom instead of being on stock and see if that works out for you.
but to think of it, believe your issue is kernel related. i think i remember reading something about it.
so after twrp and data format , reboot back to twrp and oem fix, dont reboot to OS yet. try flashing endurance kernel or tgp kernel. just be sure to take the appropriate oreo or pie version depending on what android os version you go on.
Click to expand...
Click to collapse
:good:
I have not tried method 2 yet .. I did flash OREO and when i tried to run to flash TWRP, the console echoed "Only official released binaries are allowed to be flashed(Recovery)". So i will need to roll back to an earlier image on 8.1
Forgive my lack of knowledge - where would i find the endurance kernel ? Thanks.
nrah said:
:good:
I have not tried method 2 yet .. I did flash OREO and when i tried to run to flash TWRP, the console echoed "Only official released binaries are allowed to be flashed(Recovery)". So i will need to roll back to an earlier image on 8.1
Forgive my lack of knowledge - where would i find the endurance kernel ? Thanks.
Click to expand...
Click to collapse
that binaries issue you had should have been fixed by ketans oem fix root.( method 1)
when you flash back stock to correct the issue. go to system settings and go down to software update and make if manualy find updates. it will then pop up "device registered". then to go to software and tap "build" a few times to make developer options appear.
then go check in dev options oem unlock should say already unlocked."
if i dont do the manual software update check thing after a binaries issue, i would get stuck.
also unrelated:
when you flash stock, you flash all 5 files right?( in odin csc slot you put csc.md5 and not the home csc.md5 and all the other slots only have 1 appropriate file so you cant go wrong there)
endurance:
https://forum.xda-developers.com/galaxy-note-9/development/kernel-endurance-kernel-v1-1-7-t3883862/
v2.xxxx is pie
v1.xxxx is oreo
after flashing kernel.zip you MUST flash magisk or you wont have anyways to manage root and give permissions.
so also flash right after kernel:
https://github.com/topjohnwu/Magisk/releases/download/v19.3/Magisk-v19.3.zip will eventualy be not the latest( check last link below dor mire up to date)
then if and when phone boots up you can install the magisk manager app:
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.1.2/MagiskManager-v7.1.2.apk
both can be found here are up to date :
https://github.com/topjohnwu/Magisk/releases
bober10113 said:
that binaries issue you had should have been fixed by ketans oem fix root.( method 1)
when you flash back stock to correct the issue. go to system settings and go down to software update and make if manualy find updates. it will then pop up "device registered". then to go to software and tap "build" a few times to make developer options appear.
then go check in dev options oem unlock should say already unlocked."
Click to expand...
Click to collapse
In developer mode, it was set for USB debug correctly. The OEM lock option was not present on this OREO version.
Currently bumping back to 8.1
And yes, I select all 4 files in Odin.
nrah said:
In developer mode, it was set for USB debug correctly. The OEM lock option was not present on this OREO version.
Currently bumping back to 8.1
And yes, I select all 4 files in Odin.
Click to expand...
Click to collapse
well thats one of your problems. if oem unlock has not appeared you either need to wait for 7 days or try the method i described by visiting system/software update/manual update and wait for a pop up message that says device registered. then go back to dev options to see of OEM unlock has appeard and says that it is unlocked
Waititng 7 days sure....
That doesn't work imho. Just download an older 8.1 stock rom and flash . u will find OEM to be unlocked there.
The fix in the end was to use the Root_for_OEM_issue_devices_v5 script. I had been using the v3 script. I had followed Max's vid from high on Android, where he's got the earlier script version on his site.
Issue also, once rooted, was that Magisk was out of sync - Magisk was ahead of the manager, so i down graded the manager (once I worked out the release pairs), and magisk was stable again. I did note that the Magisk did not always maintain root for some reason, when the version were out of sync. Possible connection, not sure.
Must admit you learn a lot about these phones when you have a root problem - a lot more compared to someone just following someone else's good work and wanting the %100 it will work path !
Thanks bober10113 for chipping in along the way.
I rooted my phone 2 weeks ago. While backing up and restoring Dem keys, I broke something I don't kno. Now every custom rom I install boots and gets stuck at Phone is starting and then reboots. Tried LOS 16, 17.1 and Pixel experience rom. But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?
GOrMHATRe said:
But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Click to expand...
Click to collapse
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
GOrMHATRe said:
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?
Click to expand...
Click to collapse
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.
SXUsr said:
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.
Click to expand...
Click to collapse
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
I have already use flashtool and newflasher. That's how I rooted my phone. Both of them are successful in flashing stock sony firmware. But the custom roms are in zip file. Don't kno of its possible to flash those using flashtool.
GOrMHATRe said:
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
Click to expand...
Click to collapse
Steps :
Remove your screen lock (set it to swipe up or none) and remove all your fingerprints registered.
Download the zip above and extract the boot, system and vendor images
Make sure you have Android 10 TWRP as mentioned above with link
Go to recovery > wipe and wipe system, cache and data nothing else.
Then go to install and flash boot.img as boot image, system.img as system image and vendor.img as vendor image.
Click to expand...
Click to collapse
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.
SXUsr said:
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.
Click to expand...
Click to collapse
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.
GOrMHATRe said:
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.
Click to expand...
Click to collapse
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.
SXUsr said:
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.
Click to expand...
Click to collapse
I tried this but the result was same. Rom boots upto the lock screen. Then when I swipe it shows: phone is starting and goes into bootloop. I even tried an older version of PE Rom whic contain s only img files but again same result.
You kno initially, after I unlocked the bootloader I just installed stock rom and installed LOS on top of it as per guide. It worked well. I coud go into menu and see apps.
But I panicked that I had forgotten to restore drm keys. Instead of first checking camera, I went back and restored the Ta partition and repeated the steps after it upto installation of rom and since then I have faced problems . Restoring ta partition and flashing stock rom after it is where I have made a mistake and broken something. Can this be fixed with twrp. I kno there are options in twrp to format & repair partitions. Coud that help to repair what ever that was broken?
GOrMHATRe said:
Coud that help to repair what ever that was broken?
Click to expand...
Click to collapse
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?
SXUsr said:
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?
Click to expand...
Click to collapse
Which kernel are you speaking about? I had backed up Ta image using renoroot exploit and restored it using:
adb pull /data/local//tmp/TA-unlocked.img
adb push TA-locked.img /data/local/tmp
Then in window with temp root prompt:
cd /data/local/tmp
de if=TA-locked.img of=/dev/block/bootdevice/by-name/TA
sync
sync
Reboot phone
But actually, when I checked my phone just now and that tmp directory seems empty. So, does that mean TA didn't get restored properly? Is that why I am facing problems? Stock roms seem to be working fine.
As for sony's own flashtool, I have it installed. But thought it doesn't offer any different functionality than newflasher or old flashtool? Woud sony flashtool help me go back to square 1 and make my phone as it was before rooting so that I can do everything again properly?
GOrMHATRe said:
Which kernel are you speaking about?
Click to expand...
Click to collapse
The kernel of the rom. Check your service menu for drm status.
SXUsr said:
The kernel of the rom. Check your service menu for drm status.
Click to expand...
Click to collapse
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.
GOrMHATRe said:
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.
Click to expand...
Click to collapse
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.
Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).
SXUsr said:
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.
Click to expand...
Click to collapse
I will try this but after some time. I have experimented on my phone a lot in recently. Need it to be stable for work for some time now. My secondary phone is not setup to work with gmail etc. Thanks for all the advice you have provided though.
On another note, now that Android 11 is out, do you think we will get a rom based on it for Xz1 compact? I even had a thought of skipping 10 and going for 11 based rom.
thefelineofaveb said:
Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).
Click to expand...
Click to collapse
I have not touched drm keys after I backed up and restored them for the 1st time.
hellow everyone, sorry for my english. but i need your help !
yesterday i was trying to repair IMEI of my pixel 4xl. unlocked bootloader working on android 12.1
after restoring QCN of another same model. nothing happens so i reset ESP using TWRP commands found somewhere in forum ..
after that im unable to restore my modem.img or modemst1, st2. fsg. i have backup of all files but unable to flash using fastboot mode. it gives me error.
Remote user not allower to flash MODEM. etc..
the situation is. my wifi is not working and imei is crupted or blank.
i have tried android flash tool online and upgraded to Android 13 Developer 2.
but same results
i restored QCN using QFIL. but. nothing happens
is there another way to flash modem files? or any easy commands. thanku
Go to halabtech they've solution but paid.
rohailadnan said:
hellow everyone, sorry for my english. but i need your help !
yesterday i was trying to repair IMEI of my pixel 4xl. unlocked bootloader working on android 12.1
after restoring QCN of another same model. nothing happens so i reset ESP using TWRP commands found somewhere in forum ..
after that im unable to restore my modem.img or modemst1, st2. fsg. i have backup of all files but unable to flash using fastboot mode. it gives me error.
Remote user not allower to flash MODEM. etc..
the situation is. my wifi is not working and imei is crupted or blank.
i have tried android flash tool online and upgraded to Android 13 Developer 2.
but same results
i restored QCN using QFIL. but. nothing happens
is there another way to flash modem files? or any easy commands. thanku
Click to expand...
Click to collapse
can you pls share your efs backup or full backup i have no sim no service issue i will be grateful i corrupted the partitions so pls Here is that you can restore efs https://forum.xda-developers.com/t/tool-backup-restore-efs-imei-for-all-sgsiii.1901098/ and restore modems from qfil