Related
I know there are ways around breaking the radio, but I'm just really curious. How would rooting break the radio? Does it have something to do with the weird encryption that comes on some Marshmallow devices now? Thanks.
kernelpanic_ said:
I know there are ways around breaking the radio, but I'm just really curious. How would rooting break the radio? Does it have something to do with the weird encryption that comes on some Marshmallow devices now? Thanks.
Click to expand...
Click to collapse
Someone correct me if I'm wrong but that was only in the early root guides. I think its been fixed because even after a week and a half after the launch, I rooted and didn't lose radios. Just follow the original root guide and you'll be fine. Or just install twrp and then leedroid or viper rom and make it much simpler for yourself
kernelpanic_ said:
I know there are ways around breaking the radio, but I'm just really curious. How would rooting break the radio? Does it have something to do with the weird encryption that comes on some Marshmallow devices now? Thanks.
Click to expand...
Click to collapse
btort1 said:
Someone correct me if I'm wrong but that was only in the early root guides. I think its been fixed because even after a week and a half after the launch, I rooted and didn't lose radios. Just follow the original root guide and you'll be fine. Or just install twrp and then leedroid or viper rom and make it much simpler for yourself
Click to expand...
Click to collapse
true the previous version of supersu rooting used to mess up encryption and break your signal post which they had set the flag to enforce encryption and thus letting you root and retain radio but then if you decrypt your data manually you used to lose radio again..
but now almost all of the custom roms like ice lee viper does let you root and decrypt data and radio works fine...
i have tried it on ice and lee both works fine and i am currently decrypted with super 2.74-2 system mode from su thread
SacredDeviL666 said:
true the previous version of supersu rooting used to mess up encryption and break your signal post which they had set the flag to enforce encryption and thus letting you root and retain radio but then if you decrypt your data manually you used to lose radio again..
but now almost all of the custom roms like ice lee viper does let you root and decrypt data and radio works fine...
i have tried it on ice and lee both works fine and i am currently decrypted with super 2.74-2 system mode from su thread
Click to expand...
Click to collapse
So it does have something to do with the encryption
Side question for you - Have you noticed performance differences between encrypted and non?
_-..zKiLLA..-_ said:
So it does have something to do with the encryption
Side question for you - Have you noticed performance differences between encrypted and non?
Click to expand...
Click to collapse
Personally, I haven't noticed much difference, if any, at all between encrypted and unencrypted. Haven't bothered running any benchmarks, though, either.
schreckles said:
Personally, I haven't noticed much difference, if any, at all between encrypted and unencrypted. Haven't bothered running any benchmarks, though, either.
Click to expand...
Click to collapse
_-..zKiLLA..-_ said:
So it does have something to do with the encryption
Side question for you - Have you noticed performance differences between encrypted and non?
Click to expand...
Click to collapse
doing benchmarks on both theres is no difference, if anything its a bit slower decrypted.
kernelpanic_ said:
I know there are ways around breaking the radio, but I'm just really curious. How would rooting break the radio? Does it have something to do with the weird encryption that comes on some Marshmallow devices now? Thanks.
Click to expand...
Click to collapse
also the losing of the radio during root, like said in pervious post is a thing of the past, fixed like the first week. Just make sure your using the latest twrp recovery, and this su
afuller42 said:
doing benchmarks on both theres is no difference, if anything its a bit slower decrypted.
also the losing of the radio during root, like said in pervious post is a thing of the past, fixed like the first week. Just make sure your using the latest twrp recovery, and this su
Click to expand...
Click to collapse
No decrypted devices are always faster in performance due to less layer of security while ur soc tries to access files . but then again those differences are very hard to notice . . . encrypted devices are always a bit slower than decrypted. . .
Sent from my HTC 10 using XDA-Developers mobile app
Hello,
can somebody upload exactly this FW for this phone?
For 2 SIM cards? Yes
Software channel: reteu
Baseband version: M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST
Kernel: original (stock): 3.18.31....
Android security level: 1 August 2017
Android version: 7.0
Build number: NPPS25.137-72-4
I can't find this ROM anywhere, but reallly need it. Thx in advance.
Mcandrew2809 said:
Hello,
can somebody upload exactly this FW for this phone?
For 2 SIM cards? Yes
Software channel: reteu
Baseband version: M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST
Kernel: original (stock): 3.18.31....
Android security level: 1 August 2017
Android version: 7.0
Build number: NPPS25.137-72-4
I can't find this ROM anywhere, but reallly need it. Thx in advance.
Click to expand...
Click to collapse
I managed to break my XT1676 also, couldn't find the NPPS25.137-15-11 image either.
I ended up flashing NPP25.137-33 using RSDLite but modifying the flashing script to not flash the partition layout or the bootloader as they are older versions and got it back up and running. If you had that image on the phone previously and you have an unlocked bootloader you can do the same.
Let me know if you need more instructions.
Cheers.
Thank you for replying, raiamino.
I'd like to ask if is there any other option especially for phones with locked bootloader? I'd like to reflash my phone because it became unbelievably slow and laggy after some time. Factory reset didn't help much.
I flashed a lot of phones in the past (for example Sony Ericsson Xperia X8, Lenovo S60...) but this phone really surprises me about flashing. I found a lot of custom ROMs here on xda and I was thinking about flashing some also, but I'm a little bit scared of it - I don't know, which one is compatible and which isn't (nowhere is written if is custom ROM built for 2/16, 3/16, SingleSIM, DualSIM... variant). I need Moto Gestures feature (really useful thing for me) also, but don't know, if any custom ROM supports it. Do you know about any which will not cause brick (or hard brick) if I will flash it? Thx in advance.
Btw, sorry for bad English, but it's not my native language. Greetings from little big country - Slovakia.
Mcandrew2809 said:
Thank you for replying, raiamino.
I'd like to ask if is there any other option especially for phones with locked bootloader? I'd like to reflash my phone because it became unbelievably slow and laggy after some time. Factory reset didn't help much.
I flashed a lot of phones in the past (for example Sony Ericsson Xperia X8, Lenovo S60...) but this phone really surprises me about flashing. I found a lot of custom ROMs here on xda and I was thinking about flashing some also, but I'm a little bit scared of it - I don't know, which one is compatible and which isn't (nowhere is written if is custom ROM built for 2/16, 3/16, SingleSIM, DualSIM... variant). I need Moto Gestures feature (really useful thing for me) also, but don't know, if any custom ROM supports it. Do you know about any which will not cause brick (or hard brick) if I will flash it? Thx in advance.
Btw, sorry for bad English, but it's not my native language. Greetings from little big country - Slovakia.
Click to expand...
Click to collapse
you can do the following - warning it will erase everything on internal storage including photos music downloads documents etc - backup to sd card or laptop first if you want to keep these things
put phone into fastboot mode and connect to laptop
In a terminal/command prompt window assuming you have fastboot installed type the following
Code:
fastboot erase userdata
When you restart your phone it will be like the first time you switched it on (albeit with upgraded firmware version)
LineageOS supports moto gestures - For me they all work except shake to open camera app but you can set it to open with a double press of the power button
Flashing a custom rom designed for your phone will not hard brick it as it will never touch the bootloader so you will always be able to enter fastboot mode
Of course you can soft brick which means it either bootloops or you cant access recovery if you don't follow the correct process but you can solve that just by repeating the process correctly
All right, I will give it a try at evening (not enough time right now). So If I will do the fastboot command...
Code:
fastboot erase userdata
...what will happen? Is it the same procedure as factory reset + wipe cache?
Mcandrew2809 said:
All right, I will give it a try at evening (not enough time right now). So If I will do the fastboot command...
Code:
fastboot erase userdata
...what will happen? Is it the same procedure as factory reset + wipe cache?
Click to expand...
Click to collapse
yes but it also wipes everything on internal storage data partition
A reset + wipe cache will format data but not user data (things that are stored on internal storage such as pictures music documents downloads)
It does not format system or anything else
Thank you, it helped a lot! :highfive:
EDIT: what's difference between erase and format in fastboot? Would something bad happen if i do format command instead of erase?
Mcandrew2809 said:
Thank you, it helped a lot! :highfive:
EDIT: what's difference between erase and format in fastboot? Would something bad happen if i do format command instead of erase?
Click to expand...
Click to collapse
Iv no idea - it will either give an error unknown command or do something
erase userdata is the correct use
Hello,
I have the same phone and like to download the stock rom first before flashing a custom one (RR e.g.). I can't find anywhere a download for this version's custom rom yet. Is there any way to save the stock rom out of the still unmodified phone?
Thanks for your help!
Bro.. check this.. npps is for xt 1676 ( Europe, Turkey ) and npp is for xt 1677 ( India) . Both are dual sim 3gb version phones.. just may be customization difference. Hopefully all modem bands may work.
Npps or xt 1676 unfortunately dont have version above 25.137-15 ( which is an older firmware from what u have ) , so never flash it.
But npp have higher version 72/76/82.
Just in case u are not confident enough avoid gpt, and bootloader flashing.
Btw.. if you have messed up ur bootloader ( cant boot into fastboot) .. i think give these files a try.. btw.. you have nothing to loose since u have messed up pretty bad with bootloader.
This is the only last try till Oreo upadate ( if moto ever release it for g5)
Btw.. if u get successful.. please share.
https://www.clangsm.com/forum/index.php?showtopic=482933
---------- Post added at 02:34 PM ---------- Previous post was at 02:16 PM ----------
And if u are worried about modem ( which may cause wifi /signal issue) avoid flashing modem or try flashing old modem from npps25.137-15 ( the file is available in same directory) you can use the modem file only for flashing )
I mean.. first flash the complete npp25.137-76 ( i choose that file because its non branded ) .. after successful boot, check wifi and sim.
If everything is ok.. use the same..
If you have problems with wifi or sim..
Use modem file from npps 25.137-15 and flash modem partion only.
Or completely avoid all trial and error methods. And just flash npp25-137-76 with out flashing modem , bootloader, gpt, - its just like flashing a new kernel and system.. everything except system and kernel will remanin the same.
The method works only if u have a working bootloader. If its not there.. there is no way to trial and error things.. till u courageously flash the bootloader and gpt from npp version..
Hope you will get something.
---------- Post added at 02:51 PM ---------- Previous post was at 02:34 PM ----------
Currently.. my xt1676 is working with August security update ( npps - 25.137-72-4 ) rooted, unlocked.. i am trying hard to mess it up.. unfortunately twrp backup helps me to unbrick few times!! But soon or later i will manage to mess it up!!!???
Only then i will give these files a try... ( Or atlest till pixel 2 comes to retailer near by) . For now this is my backup phone after selling s7 edge.
This is just 2 weeks old.. and i manage to mess its os 5-6 times till now.. so i think i will be joining your club soon
Just the same phone as yours..2 weeks old.. but its alive till now.
showlyshah said:
Just the same phone as yours..2 weeks old.. but its alive till now.
Click to expand...
Click to collapse
Hi. Sorry for bumping an old thread but I thought it was better then to make a new one.
I bought this phone a few days ago and it had NPPS25.137-72-4 when delivered. Been trying to read up a bit on this device but since I'm used to samsung, it all takes a while to figure things out
Got it unlocked/rooted fine, but I want to make sure I have something to fall back on in case of trouble.
I've been searching for this fw without any luck. Any chance some one got it and can share it?
NPPS25.137-72-4
Or if anyone can suggest a different one that could work. ( I don't really understand the fw names yet)
Thanks in advance.
tys0n said:
Hi. Sorry for bumping an old thread but I thought it was better then to make a new one.
I bought this phone a few days ago and it had NPPS25.137-72-4 when delivered. Been trying to read up a bit on this device but since I'm used to samsung, it all takes a while to figure things out
Got it unlocked/rooted fine, but I want to make sure I have something to fall back on in case of trouble.
I've been searching for this fw without any luck. Any chance some one got it and can share it?
NPPS25.137-72-4
Or if anyone can suggest a different one that could work. ( I don't really understand the fw names yet)
Thanks in advance.
Click to expand...
Click to collapse
Take a twrp backup .. a clean one..
tys0n said:
Hi. Sorry for bumping an old thread but I thought it was better then to make a new one.
I bought this phone a few days ago and it had NPPS25.137-72-4 when delivered. Been trying to read up a bit on this device but since I'm used to samsung, it all takes a while to figure things out
Got it unlocked/rooted fine, but I want to make sure I have something to fall back on in case of trouble.
I've been searching for this fw without any luck. Any chance some one got it and can share it?
NPPS25.137-72-4
Or if anyone can suggest a different one that could work. ( I don't really understand the fw names yet)
Thanks in advance.
Click to expand...
Click to collapse
There's no flash able zips of stock ROMs here unfortunately. Weird for me too since I was Samsung through and through. Take a back up of your own ROM via TWRP or you can use the debloated stock ROM by Fedray on the ROM forum.
showlyshah said:
Take a twrp backup .. a clean one..
Click to expand...
Click to collapse
Smonic said:
There's no flash able zips of stock ROMs here unfortunately. Weird for me too since I was Samsung through and through. Take a back up of your own ROM via TWRP or you can use the debloated stock ROM by Fedray on the ROM forum.
Click to expand...
Click to collapse
Thanks for your answers.Thats actualy first thing I did after flashing twrp to have a clean backup of system and boot.
I also made a few partition backups in terminal, like persist, oem, modem and a few others so hopefully I'm fine.
Do you guys know if I can take stock recovery from lower version fw in case I would ever need it again?
I highly doubt I ever will, but just in case
Edit: If anyone needs a system/boot backup of this fw, just let me know and I'll upload it.
tys0n said:
Thanks for your answers.Thats actualy first thing I did after flashing twrp to have a clean backup of system and boot.
I also made a few partition backups in terminal, like persist, oem, modem and a few others so hopefully I'm fine.
Do you guys know if I can take stock recovery from lower version fw in case I would ever need it again?
I highly doubt I ever will, but just in case
Edit: If anyone needs a system/boot backup of this fw, just let me know and I'll upload it.
Click to expand...
Click to collapse
Infact i need a full twrp backup of the exact same firmware.. if u can uplaod.. please do that.. btw.. if u need recovery image i can extract it from ota.. and send to you.
showlyshah said:
Infact i need a full twrp backup of the exact same firmware.. if u can uplaod.. please do that.. btw.. if u need recovery image i can extract it from ota.. and send to you.
Click to expand...
Click to collapse
Yes please. If you could do that, that would be great
I'll zip the backup and upload it in a few hours when I get to my computer.
tys0n said:
Yes please. If you could do that, that would be great
I'll zip the backup and upload it in a few hours when I get to my computer.
Click to expand...
Click to collapse
Me too.. i will do it tomorrow itself.
Ok, here we go. Stock TWRP backup from XT1676.
NPPS25.137-72-4
CEDRIC_XT1676-NPPS25.137-72-4_TWRP.zip
Unzip, put in your twrp backup folder and restore.
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=13304
I got this too..
Hi. I have a A5 2017. I recently changed from the Russian 7.0 to the German Rom and the baseband and also the imei disappeared. I've got ROMs from all the sites and I'm still the same. Any solution?
I can´t have root. I can not install twrp. I have the error only official released binaries ...
PS: I can not change the bootloader. I have the error sw rev ...
I can only flash Ap.The 4 files together I can not
I can install the 4 files + pit but at the moment of starting the mobile it takes me to the recovery and later says things like ...:
- / efs invalid argument
-dm-verity fail ...
Any solution? I'm desperate
deleted
DaniPS2002 said:
Hi. I have a A5 2017. I recently changed from the Russian 7.0 to the German Rom and the baseband and also the imei disappeared. I've got ROMs from all the sites and I'm still the same. Any solution?
I can´t have root. I can not install twrp. I have the error only official released binaries ...
PS: I can not change the bootloader. I have the error sw rev ...
I can only flash Ap.The 4 files together I can not
I can install the 4 files + pit but at the moment of starting the mobile it takes me to the recovery and later says things like ...:
- / efs invalid argument
-dm-verity fail ...
Any solution? I'm desperate
Click to expand...
Click to collapse
The issue seems to be a combination of incorrect firmware and bad /Efs partition..
The dm-verity issue is because you haven't flashed the correct firmware.
The EFS error may also be erroneous, but if you've been messing with the wrong firmware and PIT files it's possible you've caused this error by messing up your partition structure and corrupting the EFS partition.
You really need to obtain the correct firmware for your region and possibly flash it with the PIT file if you've messed up your partition structure.
flozge said:
Hi try to root your phone with Kingroot and install TWRP via TWRP app
EDIT: Have you enabled OEM Unlock in Developer Options?
Click to expand...
Click to collapse
Hello! Thanks for your answer. I'm on Android 7.0 and I remember that kingroot no longer worked. I have the oem unlock option enabled. Now my phone has turned on but the wifi and fingerprints work partially. The system is unusable after 15 minutes of being used. It is progressively slowing down
ashyx said:
The issue seems to be a combination of incorrect firmware and bad /Efs partition..
The dm-verity issue is because you haven't flashed the correct firmware.
The EFS error may also be erroneous, but if you've been messing with the wrong firmware and PIT files it's possible you've caused this error by messing up your partition structure and corrupting the EFS partition.
You really need to obtain the correct firmware for your region and possibly flash it with the PIT file if you've messed up your partition structure.
Click to expand...
Click to collapse
Hi. Thank you very much for your help. My phone is an Italian version and I decided to change the firmware to the Russian version and since then the phone has generated all those errors. I would appreciate very much if you could give me a solution to this problem. Thank you
DaniPS2002 said:
Hi. Thank you very much for your help. My phone is an Italian version and I decided to change the firmware to the Russian version and since then the phone has generated all those errors. I would appreciate very much if you could give me a solution to this problem. Thank you
Click to expand...
Click to collapse
Which Italian firmware are you trying to flash?
ashyx said:
Which Italian firmware are you trying to flash?
Click to expand...
Click to collapse
This. A520FXXU2BQH4/A520FVFG2BQH2 on 7.0 3 aug
DaniPS2002 said:
This. A520FXXU2BQH4/A520FVFG2BQH2 on 7.0 3 aug
Click to expand...
Click to collapse
Can you post a screen shot of the device screen after flashing the whole firmware?
ashyx said:
Can you post a screen shot of the device screen after flashing the whole firmware?
Click to expand...
Click to collapse
Let me see you. The phone now I have it working. That is, I had to install an generic a520f efs.tar for odin so that the system could start(this efs folder is empty obviously) Now what I'm looking for is how to restore the imei and in the process remove system crashes * wifi forget passwords, fingerprints do not work ... and the system does not work or does not respond within 15 minutes. The efs.tar that I have gotten makes verifying the DM verity successful only the first time. Already the second time you access the recovey I have the error dm verity error. I feel the misunderstanding
DaniPS2002 said:
Let me see you. The phone now I have it working. That is, I had to install an generic a520f efs.tar for odin so that the system could start(this efs folder is empty obviously) Now what I'm looking for is how to restore the imei and in the process remove system crashes * wifi forget passwords, fingerprints do not work ... and the system does not work or does not respond within 15 minutes. The efs.tar that I have gotten makes verifying the DM verity successful only the first time. Already the second time you access the recovey I have the error dm verity error. I feel the misunderstanding
Click to expand...
Click to collapse
Please send me the efs.tar
flozge said:
Please send me the efs.tar
Click to expand...
Click to collapse
This is the efs. Try it
EDIT:Flash in CP
DaniPS2002 said:
This is the efs. Try it
EDIT:Flash in CP
Click to expand...
Click to collapse
Thanks
DaniPS2002 said:
Let me see you. The phone now I have it working. That is, I had to install an generic a520f efs.tar for odin so that the system could start(this efs folder is empty obviously) Now what I'm looking for is how to restore the imei and in the process remove system crashes * wifi forget passwords, fingerprints do not work ... and the system does not work or does not respond within 15 minutes. The efs.tar that I have gotten makes verifying the DM verity successful only the first time. Already the second time you access the recovey I have the error dm verity error. I feel the misunderstanding
Click to expand...
Click to collapse
Guessing you made it work with only flashing the ap, and you still have the sw rev error, what you can do is download a XXUx being the last x the number of the device on the error, for instance, if the error is "Device 4 Binary 3" You want to flash an XXU4.
Good luck.
@DaniPS2002 I am waiting for a z3x box 29 crack when I have found one I tell you
flozge said:
@DaniPS2002 I am waiting for a z3x box 29 crack when I have found one I tell you
Click to expand...
Click to collapse
Perfect! Many thanks! Is there news about version 29? It is precisely the version that adds support to our model
DaniPS2002 said:
Perfect! Many thanks! Is there news about version 29? It is precisely the version that adds support to our model
Click to expand...
Click to collapse
It gives already 30 but our device is since 29 supported
flozge said:
It gives already 30 but our device is since 29 supported
Click to expand...
Click to collapse
News mate?
DaniPS2002 said:
News mate?
Click to expand...
Click to collapse
No but I think 3weeks or less is a crack available
Can someone give me an backup of the efs partiton with twrp of a520f please?
no need efs backup, since it is stored anywhere on stock rom.
if u get it, so you are good to go with odin.
IMPORTANT NOTE TO USERS UPGRADING TO AN ANDROID 10 ROM:
Please BACKUP YOUR PERSIST PARTITION IN RECOVERY BEFORE FLASHING AN ANDROID 10 ROM, otherwise your device may be messed up seriously. Please read this post before upgrading to A10.
Update on this issue:
https://forum.xda-developers.com/ma...n-fixing-persist-issues-t4024247/post81656725
Apparently, due to the changes made by Google, some hacks needed to be done to make Q work with our device. Due to this, when installing an Android 10 ROM and other things like Magisk on it, some modifications are made to the persist partition. These changes might break some important stuff like Camera, Wifi, Torch etc for users who go back to Pie ROMs. Even when switching between TEN Roms, similar problems have come to some users.
*******************************************
****** WAYS TO BACKUP PERSIST ******
*******************************************
1) Using persist backup option in recovery
-> This option is present in recent versions of TWRP and other TWRP based recoveries. Its a good practice to always backup all the important partitions like Persist, EFS and Modem. These contain the most important stuff like IMEI, Wifi Mac address etc. which are unique to your device.
2) Making an Image backup of persist via recovery terminal
-> If the persist backup option isn't available, you can use the dd command from a terminal app (needs root rights) or from the recovery terminal.
Usage:
To create a backup and place it at /sdcard/persist.img:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
To restore a backup which is placed at /sdcard/persist.img:
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
Thanks to @NZedPred, due to which I came across these commands. These appear to work universally and work on our device as well. Please be careful while typing the commands, especially while restoring the persist.img. Even a small mistake could be fatal for the device.
*************************************
********* FIXING PERSIST *********
*************************************
There is no guaranteed way to fix your broken ORIGINAL persist, but currently the only way to fix the broken stuff on your device is using someone else's persist. We need to obtain a twrp backup of the persist or persist.img from some other user who has not upgraded to Android 10.
Before fixing your persist, make a BACKUP of your ORIGINAL PERSIST even if it is broken. It contains important stuff UNIQUE to your device. It might be very helpful, in case someone discovers a fix to it in the future.
Please BEWARE, there are RISKS associated with using someone else's persist. Historically in other devices, it has been used to store IMEI and other important things.
But the following things are CONFIRMED TO BREAK if using someone else's persist.
1) WIDEVINE WILL BE PERMANENTLY STUCK AT L3, since the drm certificates unique to your device will be lost forever.
2) Persist stores your serial number as well, so your ORIGINAL SERIAL number may get lost when switching to stock.
***************************************
****** FIXING SERIAL NUMBER ******
***************************************
Fortunately there is a way to fix your serial number. In the root of your persist, there is a hidden file ".sn.bin". Opening it in a text editor, we can see the last 15 digits of the serial number of the other person's device, whose persist you have used. Copy and keep this number somewhere. Then follow below steps:
1) Backup the current persist.img using the above dd commands.
2) Open the persist.img using a hex editor. You can use any hex editor software for windows/linux or Hex Editor app from Play Store.
3) In the search option, set it to find strings. Set it to 'String' or something similar depending on your software.
4) Search for the 15 digit serial number which you found previously in .sn.bin file.
5) After you find it, replace or edit it to your original serial number. Make sure that you modify ONLY THOSE 15 DIGITS AND NOTHING ELSE.
6) Then save the modified persist.img
7) Restore the modified persist.img using dd commands as above.
8) Almost done, but the new changes in persist won't be detected by the system. So you will have to install the stock pie ROM. Relocking the bootloader is not required as per my testing. So follow the steps to install stock. Use OFRP and decrypt.zip as necessary, to deal with encryption.
9) Now boot up the device.
And voila. Go to settings and check your serial. It should be restored. You can now return to your custom ROM if you want. The serial number will be retained.
Same thing happened with my device too. Widevine security level is stuck at L3.
Although I'm back in the Official Stock ROM!
(locked bootloader)
Apolle said:
Same thing happened with my device too. Widevine security level is stuck at L3.
Although I'm back in the Official Stock ROM!
(locked bootloader)
Click to expand...
Click to collapse
Yes... Even after flashing stock firmware, widevine remains L3.
Some people have suggested me to install the last stock Oreo first and then install Stock Pie.
Maybe the Oreo firmware contains the original persist files...
The Oreo firmwares were around 1.6 to 1.8 GB, whereas the pie firmwares are around 1.5 GB.
So maybe they are right then...
Maybe if its possible for some of you to do this, you could try this...
I also messed up my persist partition. even i'm getting back to all stock (including recovery and locked bootloader) my phone can't recieve update, neither install updates manually. Also, my device is shown in playstore setting as "Device not certified". I'm still searching for a fix for this.
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
Tyakrish said:
Yes... Even after flashing stock firmware, widevine remains L3.
Some people have suggested me to install the last stock Oreo first and then install Stock Pie.
Maybe the Oreo firmware contains the original persist files...
The Oreo firmwares were around 1.6 to 1.8 GB, whereas the pie firmwares are around 1.5 GB.
So maybe they are right then...
Maybe if its possible for some of you to do this, you could try this...
Click to expand...
Click to collapse
I also tried to install Oreo but, I can't update it to android Pie. It always failed.
kayamokid said:
I also tried to install Oreo but, I can't update it to android Pie. It always failed.
Click to expand...
Click to collapse
Could you tell which Oreo firmware ? If its very first Oreo firmware released by Asus, then you might need to update to the last available Oreo firmware and then upgrade to pie...
The last Oreo firmware I believe, prepares the device for pie...
So Pie might get installed after that
Tyakrish said:
Could you tell which Oreo firmware ? If its very first Oreo firmware released by Asus, then you might need to update to the last available Oreo firmware and then upgrade to pie...
The last Oreo firmware I believe, prepares the device for pie...
So Pie might get installed after that
Click to expand...
Click to collapse
If you haven't tried yet, try the persist.img from here & let us know if fix the problem.
Tyakrish said:
Could you tell which Oreo firmware ? If its very first Oreo firmware released by Asus, then you might need to update to the last available Oreo firmware and then upgrade to pie...
The last Oreo firmware I believe, prepares the device for pie...
So Pie might get installed after that
Click to expand...
Click to collapse
Oh, not the first one. i used .192 but no success... i hope there's a fix for this.. i miss stock rom so much...
mauam said:
If you haven't tried yet, try the persist.img from here & let us know if fix the problem.
Click to expand...
Click to collapse
I looked at this persist.img. But it appears weird to me. Just have a look at the contents of my persist image and this one.
Seems like a lot of stuff is missing...
Tyakrish said:
I looked at this persist.img. But it appears weird to me. Just have a look at the contents of my persist image and this one.
Seems like a lot of stuff is missing...
Is this supposed to be in a different format ? How can this be flashed ?
Click to expand...
Click to collapse
Let's see if @Wahyu6070 can enlighten us. His nick is wahyu hidayat on telegram if you want to reach him.
@kubersharma, I have spoken to many people about this issue and no one seems to know much about why it happens and how this issue can be fixed.
Can you give an insight as to why this persist problem happens ?
To save time, I linked to first post of this thread:
https://forum.xda-developers.com/ma...n-fixing-persist-issues-t4024247/post81288631
After much research, I have come to the conclusion that widevine can't be fixed. Since the drm certificates unique to our device are forever lost when some other user's persist is used. The other user's persist may contain some widevine files, but they are unique to his device and won't work with our device.
Completely Agreed with you because what I did confirm that it cannot be fixed.
I flashed Oreo Firmware Raw (Initial Oreo Firmware 158) by Fastboot/adb method. Then Install every single incremental Update by built-in Updater. But unfortunately the Widevine security level remains L3.
Apolle said:
Completely Agreed with you because what I did confirm that it cannot be fixed.
I flashed Oreo Firmware Raw (Initial Oreo Firmware 158) by Fastboot/adb method. Then Install every single incremental Update by built-in Updater. But unfortunately the Widevine security level remains L3.
Click to expand...
Click to collapse
Thanks for all that effort. I also tried with a fastboot firmware posted on 4pda. But no use.
Tyakrish said:
@kubersharma, I have spoken to many people about this issue and no one seems to know much about why it happens and how this issue can be fixed.
Can you give an insight as to why this persist problem happens ?
To save time, I linked to first post of this thread:
https://forum.xda-developers.com/ma...n-fixing-persist-issues-t4024247/post81288631
Click to expand...
Click to collapse
Try pm @wahyu6071 telegram
UPDATES:
- Added a way to make persist image backups (Can be useful for flashing persist.img files).
Check the first post
Apolle said:
Same thing happened with my device too. Widevine security level is stuck at L3.
Although I'm back in the Official Stock ROM!
(locked bootloader)
Click to expand...
Click to collapse
have you used other user's persist? are you able to install OTA after you made this process? i also use other's persist. and my imei is lost. and also, i cant update thru FOTA and manual method. it gives me an error in stock recovery.
kayamokid said:
i also use other's persist. and my imei is lost.
Click to expand...
Click to collapse
Wait a min. Did you lose your imei also ? I thought u only lost widevine L1 ?
Tyakrish said:
Wait a min. Did you lose your imei also ? I thought u only lost widevine L1 ?
Click to expand...
Click to collapse
yes. but i manage to restore it again, by editing .sn,bin file inside of persist folder. terrible happens when this persist problem occurs. i cant install or update stock rom manually. i hope there's a way to fix this. I miss clean, locked and unrooted stock rom.
kayamokid said:
yes. but i manage to restore it again, by editing .sn,bin file inside of persist folder. terrible happens when this persist problem occurs. i cant install or update stock rom manually. i hope there's a way to fix this. I miss clean, locked and unrooted stock rom.
Click to expand...
Click to collapse
You must be talking about Serial number. The file, .sn.bin contains the serial number. I don't think imei is lost if we use someone else's persist. I didn't lose mine and I came across many other people, they also didn't lose imei.
Based on what you are saying, I think serial number gets lost as well along with widevine...
Because even I lost my serial number after installing stock pie via fastboot
Deleted
As the title states. Am just wondering what happens exactly when you take a ota on a rooted device. Am not talking about the full ota. Am talking about the smaller otas just curious to know
v.konvict said:
As the title states. Am just wondering what happens exactly when you take a ota on a rooted device. Am not talking about the full ota. Am talking about the smaller otas just curious to know
Click to expand...
Click to collapse
You can't on OOS. You have to take full.
jhlogan said:
You can't on OOS. You have to take full.
Click to expand...
Click to collapse
That much i know. I want to know what will happen
v.konvict said:
That much i know. I want to know what will happen
Click to expand...
Click to collapse
Do it then tell us
ej8989 said:
Do it then tell us
Click to expand...
Click to collapse
Am sure its already been done just wanna understand how root affects the partions when taking an ota
v.konvict said:
Am sure its already been done just wanna understand how root affects the partions when taking an ota
Click to expand...
Click to collapse
You'll end up breaking your phone's functionality, simply causing boot looping, unable to root your device and have to install a full base factory ota to fix the damage done. And you wouldn't even be able to backup anything either since the device will basically be semi-bricked
Shen Ron said:
You'll end up breaking your phone's functionality, simply causing boot looping, unable to root your device and have to install a full base factory ota to fix the damage done. And you wouldn't even be able to backup anything either since the device will basically be semi-bricked
Click to expand...
Click to collapse
Thanks for this. Am not new to flashing updates with root. Was hoping for a more detailed explanation. Like the ota updates a certain partition which when rooted will cause a bootloop because a certain partition wont readable
v.konvict said:
Thanks for this. Am not new to flashing updates with root. Was hoping for a more detailed explanation. Like the ota updates a certain partition which when rooted will cause a bootloop because a certain partition wont readable
Click to expand...
Click to collapse
Every partition except the boot partition will be ok for the most part but you'll still end up boot looping even if you installed magisk over again, so unless you do a fresh install which depending on how badly you messed something up or forgot to disable any modules, you will have to start from scratch to save your phone. But if you already made a backup whether it's before everything went south or in twrp to save your data then you should be okay