Related
Hi guys, I tried searching the forum for this same question as well as googling, but I seem to have failed at that, so I stopped lurking, registered and am asking directly:
I am planning on selling my Omnia 7, but am curious as to how the whole "reset my phone" option works. I have mango update, not interop unlocked tho (I didn't update the latest 2 bugfixes fearing that my unlock would go away, although after some lurking that fear is proven irrational) and I want to "advertise" my phone as jailbroken, but I can't seem to be able to "detach" my hotmail account from the phone, and people have suggested that "reset my phone" option takes the phone all the way back to initial configuration. Now, what I'm curious about is - does this option also undo my jailbreak?
If so, how hard is it to re-unlock the phone for the new owner (I'd like to help him out as much as I can, in case he is not a tech-savvy guy and would rather get a fully unlocked product hassle free)?
I got my Omnia 7 and unlocked it via chevron, so it was fairly easy.
Thank you in advance for any help provided .
If it really is Mango, and not 8107, than you need to hard reset the phone and windowbreak it again. You don't need to enter your liveID to do this. After that, your phone will be clean of ALL your info, files and settings and jailbroken. You can than update it to the latest OS version (8107) via Zune so you can advertise that too.
http://windowsphonehacker.com/articles/the_windowbreak_project-12-23-11
PS: The buyer will not be able to windowbreak again if he needs to if you don't provide him with the backup files from your computer, because samsung has "fixed" the hole windowbreak was using in the new updates. You could backup your phone after the hard reset (but before you update it to 8107) and provide that. It should not be a huge file when the phone is hard reseted.
d.a.v.o.r said:
If it really is Mango, and not 8107, than you need to hard reset the phone and windowbreak it again. You don't need to enter your liveID to do this. After that, your phone will be clean of ALL your info, files and settings and jailbroken. You can than update it to the latest OS version (8107) via Zune so you can advertise that too.
http://windowsphonehacker.com/articles/the_windowbreak_project-12-23-11
PS: The buyer will not be able to windowbreak again if he needs to if you don't provide him with the backup files from your computer, because samsung has "fixed" the hole windowbreak was using in the new updates. You could backup your phone after the hard reset (but before you update it to 8107) and provide that. It should not be a huge file when the phone is hard reseted.
Click to expand...
Click to collapse
Amazing response Davor, 100% documentated and acurate.
d.a.v.o.r - your answer is much appreciated, however, I found a video on youtube demonstrating windowbreak method being done on the same version of software (how I forgot to mention that in my first post is beyond me and I apologize for being vague) I had and it was being done after the uploader restarted his phone using the "reset my phone" option, so I took that as a sure sign it could be done with no problem.
Sold my phone, buyer seems to be a regular on XDA tho, so I'm guessing he'll have no problems whatsoever .
Hi. Been waiting a while to post this, and playing around based on what I see, but I the last change I made to my phone hasn't worked out too well and I don't think I have enough of a grip on the process. I am an ex-computer 3rd level tech support so I have reasonable skills around computers etc.
I bought an Axon 7 (A2017G) in Germany but it got flooded one day when it went down the toilet pan, literally. So I replaced it with a 128 Gb model from China, not really thinking about the software versions. Of course it came with A2017, and more importantly, no ability got OTA upgrades from Android 6.
So recently I've been having some battery life issues so I've changed the battery.
Following guides here, I've managed to get it onto a newer A2017 version and it has taken an OTA upgrade to Android 7. The build number is B13. The boot loader is still unlocked. But it's not very stable and Google Play service has now stopped, and I can't be doing with the unreliability. And tbh although it worked, I can't remember exactly which guide or what steps I followed to do it.
So I want to put it onto a stock G version, which I think seems to be possible, based on stuff I've read here. I don't think I need root going forwards (once this is done) and I'm looking for the simplest method. Unfortunately, due to the length of time it's been live, this forum really is information-overload and I've been reading for two days now and made loads of notes but I'm not really very clear about what I need to do.
I'm quite happy to find and read the right guides but would be really grateful if someone could take a few minutes to just tell me exactly which bits are essential to be upgraded and what steps I do need to follow. If I am confused I can come back with any queries.
I'd be happy to root the phone if it's felt that is a really useful thing but I'm not really a "power user" and I'm OK with standard.
Also I'm assuming any upgrade would receive any future Android releases OTA (if there are any for this phone), but if not that's not too vital.
Thanks in advance...
Geoff
But regarding your situation: You have an A2017 with A2017G firmware, right? Can you tell us your firmware version?
Would you be fine with Chinese firmware (MiFavor 5.2, B17) or prefer stock+ (G B01/B02, U B12)?
Thanks for the quick response, really appreciated.
The firmware is still A2017 version AFAIK, but I don't know where to check. If I go to the boot loader screen it says ZTE/P996A03_N/ailsa_ii and on the next line 7.1.1/NMF26V/20170912.013327
I'm thinking I'd do the change from A2017 to A2017G to get round the annoying junk which came with the Chinese version, and also avoid the Google Play Services problem I came across. It may not be do-able but I thought I'd read it was.
I guess in addition to telling me the steps, telling me exactly which file versions to use would help a lot. I promise to keep notes!
I don't mind which firmware, so long as it works reliably and so long as I can preferably put a G version on it.
of course it's doable, the thing is that you'll need to unlock the bootloader in order to.
If you had trouble with Play Services then it's most probably on chinese firmware, finding out would be as easy as going to Settings, then About phone
The boot loader is still unlocked from when I managed to do the previous upgrade. That took me quite some hours, and it was more by luck than judgement that I got a result. This time I want to better understand what I'm doing.
Not sure what I'm looking at for the firmware, isn't it the versions I quoted above? But the menus (mostly) are in Chinese at start up, and I had to load Google Play and Play Services from the ZTEYR store so I'm pretty sure it is on Chinese firmware.
So if it is, do I just need to upgrade the firmware then the ROM (is that the terminology?). If so which versions would I use?
Ta
Geoff
EDIT I missed the kernel version - which is 3.18.31
OK so I've spent more time reading. I'm coming to the conclusion that I don't need TWRP and I don't need to update my Chinese bootloader, does that sound about right?
Is it right that all I need to do is
- find a G firmware zip file <<< may have incorrect terminology here, would appreciate a pointer to a valid download as I have many but not sure they are the right type of file
- put it on an SD card named as update.zip
- boot into recovery mode
- choose "apply update from SD card"
And, assuming I have used a stock version, will it then update to the latest version (hopefully Oreo) once it's started?
Do I need to do any formats or wipes anywhere in the process? I already have a backup of my stuff, done with AXON7Toolkit.
And can you recommend a version of firmware to go to, or does it not really matter as it'll update itself anyway?
UPDATE: MiFavor UI is v5.0
OK, so there is no real short easy answer to this.
I've used the updates from ZTE since I've had the phone until I soft bricked it.
Zte offer updates similar to this.
Eg: B06 to B08 or B08 to B09 and B09 to B12
The update has to be done in stages.
Some updates you can copy to the internal SD card then go settings > system > update, your phone should detect the updates and tap install.
Some Zip files can be done the same way after changing the file name to update.zip or Ota.zip depending on the instructions.
Some zip files have the update within the Zip so it needs to be extracted.
Make sure you have the correct version software and correct version for your phone.
After the update is done all the data etc will be still in place unless you reset your phone.
All I can say is research, research, research.
Btw if your bootloader is unlocked some updates will fail.
I hope this helps
PS: you can use the method you described as well, just follow the instructions carefully.
In most cases there is no need to wipe or format unless you are using a custom ROM etc.
Excellent, thanks.
Going back a post or two - I re-installed Google Play services but still have problems. Before a reboot it appears in the list of apps, and Play opens, but the sidebar comes straight in and behind there is a message "Error while retrieving information from server [RH-01]" . After a reboot it is no longer in the list of Apps (even when expanded to include System apps), and Play just opens and closes real quick.
So I found a thread which led me look in Settings in Play Store at the Play Protect Certification, which says the device is not certified. So I downloaded the related app and ran it, which gave me a code which I put in web page then entered the stuff into my phone but still no joy. I suspect this is causing the Play problem and I think it'd be due to trying to use Google product on a Chinese firmware (again I'm not sure my terminology is right - I mean whatever the software is which throws up the initial boot screen).
So I think I need to get off the Chinese firmware at the same time as going to a G version, and I'm even less clear on how to replace the firmware than the rest of the process - what files and how it's done.
Going back to the more recent post (Syberclone), as I have already wiped my phone I'm not concerned about keeping data. I understand about doing this is steps - I hadn't thought of doing it that way but it seems very sensible.
I found a post by Raystef66 with loads of links to software - including A2017X_B15_Universal_Bootloader.zip. Does this replace the Chinese firmware and would it work with all zipfiles? How would I apply it? (I was using Axon7ToolKit the other day and that looks quite impressive).
I am still confused over the different types of files and the naming conventions but it's slowly making more sense. Appreciate all advice.
Thanks
Geoff
Personally I use Edl packages much easier imo.
I use Miflash or Edl tool by @djkuz
I have a bad flash help page that explains the process.
The bootstacks etc are mainly for custom ROMs, if you are just looking a factory firmware, Edl's are much easier to install without worrying about bootstacks, twrp etc.
My last Edl update was from Nougat (Chinese Rom)
To Oreo A2017G I had to factory reset after the install though.
Thatnks. Today I've done a fwe more hours reading, literally. This is taking all my time!!
Anyway I decided to follow your advice and found a full EDL of Oreo, which I applied. (ZTE_A2017V3.0.0B17) and the phone is still working, and I've not lost my apps.
However I still have the problem that Play Services won't run. I've upgraded it, followed a few troubleshooting guides, used different versions ( - should I be using the 64 bit one??) but still no joy. If I could only get that going I'd stick with the Chinese firmware. It is looking to me like it can't sync, though whether that's a cause or an outcome I'm not sure. Not unexpectedly, a number of apps will not run as a result.
I haven't done a factory reset yet, I thought I'd ask here first to see if that is likely to fix it or whether anyone has any better ideas.
Despite the time this is taking I'm enjoying learning and am grateful to you all for the responses.
The play store link "device not certified" will happen when you change a ROM from its original.
So I have an A2017G, when I run any other ROM it will show "device not certified" because the link between the phone and the software isnt in sync.
When I was running the beta Oreo from the Chinese my device always had this issue and NFC does not either usually.
There is a play store app version which will work as it should however the certified is still a problem without a work around.
When I installed the G version Oreo to my device the certification is back.
I'm miss some of the Chinese ROM animations tho.
Anyway I hope this helps
I am using an A2017 ROM on an A2017. I've not changed anything else. Maybe I need to update the boot stuff (firmware?).
What I'm seeing is that Play Services always needs to be manually enabled, and seems to drop out and require re-installation sometimes. So I have an apk on my internal memory for quick access.
I'm not sure that the "device not certified" is a cause or effect really.
So I have an apk on my internal memory for quick access. It's the latest non-beta 64bit version for Android 8 - should I try a specific one, e.g. is there likely to be a specific one which matches the ROM? (An older non 64 bit one seemed to give much the same problem)
I'd put up with the problem except I can't run some Google stuff at all (Play Store for instance), and some other stuff is compromised (e.g. I can't get into Waze on my usual ID, I'm guessing Play Services plays a part in authorizing). And I can't install some stuff I'd like.
And I'd still be interested to know which bits require upgrade to go to a G version, if it is do-able and would run trouble free.
There was a play store app that worked on most ROMs.
You are on Oreo now yes?
There was a link on one of the Android pie ROMs that I used, it worked fine.
If you are still having issues you can use an app called Yalp that works like the play store.
I've used it on custom ROMs when the play store app refuses to work.
Yes, Oreo now.
I've put YALP on and that looks pretty good. I now seem to have most things working, and those that aren't I can probably live without.
I use a network tool called FING which reports my phone details, and I think it's incorrect but it's saying in one place it's a A2017U which I don't think is right. But now I am more comfortable with EDL and stuff I'm going to continue to fix this properly but the urgency is now not there. I was thinking if I couldn't fix this I might have to buy a new phone on black Friday!! So thanks for your help.
I'm still not really quite sure why I get Chinese characters at start up and what files I need to change to out a G firmware on, if that is what is wrong, and if it's do-able. I think if I knew how to do that then I could put on a G firmware and matching ROM and I'd be in business!!
The same page offered me F-DROID which seems to offer a whole load of different free apps. Maybe they don't have ads? Anyway I'll have a look.
Anyway, again - thanks!!
Geoff
Geoff I'm glad I could help
I was running the Chinese Oreo on my phone and after selecting English in setting some parts of the ROM were still in Chinese, even some notifications.
I converted to the A2017G Oreo update when it was released.
I miss some of the features in the Chinese ROM tho.
So... without wishing to prolong this... your phone was Chinese (as mine was) and you are now running a Global version and all you upgraded was the ROM? And are you able to use the Play Store and you don't have any issues running apps I - and can you run, say, Google Maps?). Is your bootloader still unlocked and if so is the menu at boot time still in Chinese?
Or have you upgraded something other than the ROM?
I actually have an Axon 7 A2017G here in Australia.
I soft bricked it when I accidentally made a mistake flashing a ROM.
I searched for a suitable stock firmware but I could only flash the Chinese Oreo Beta. It had to be modified to run on my device until the Oreo package for my A2017G had been uploaded.
I've now running the proper software for this phone.
Thanks.
Another couple of hours and I have made a Major breakthrough! I went back over all my notes and checked what i'd done and one thing I hadn't remembered doing was setting the Pay Store to Autorun. So using the Mi-Assistant I have done this, and most of the stuff which wasn't working now is. I am still working on why OK Google won't work, but the list of things I might have to live without is now quite short!! The one major benefit is that my battery life seems to be greatly increased. Boot time is also much quicker which is a bonus but not critical.
Nice, yes battery life is improved, actually the Chinese Oreo Beta has a better battery life than my current Oreo.
I could get up to 4 days out of the Chinese ROM, my current ROM can manage just over 3 days at best.
I have battery saver mode on but not ultra battery saver.
I hope this has been a good learning experience for you?
"I hope this has been a good learning experience for you?"
For sure it has. Back in the days when I was 3rd level computer techie, the best learning came from other experts and from being thrown in the deep end, rather than what they taught you in the classroom!
Like a month ago, I was rooting my phone with Magisk. First, I installed TWRP, everything went OK. Then I flashed Magisk, everything was still OK. But when I tried to install Xposed with root privileges, it just installed and I rebooted, the phone got bricked, like the last level of soft brick! Factory reset wasn't working, I didn't had a Xposed Uninstaller, I didn't also have an SD Card, so I couldn't flash a ROM from SD Card using TWRP, also my PC didn't have a SD Card slot. It was rebootlooping over and over again. eRecovery gave me an error, saying "A serious boot problem has occured, it is hardly recommended to wipe data/factory reset." or something like that. I did what it said, still rebootlooping. Nothing was working, Xposed has completely screwed my phone. The last solution was to give the phone to Huawei Service Center. It came back 3 days later, and the results Xposed made was terrible. Huawei locked my bootloader and Xposed FRIED MY MOTHERBOARD. But they changed the motherboard, nothing else. So my warranty is still in place , but still, my phone is no longer open for rooting, flashing etc. I don't know what to do. I want know two things;
1- How did Xposed do that and is it not supporting my phone?
2- How can I unlock my bootloader back?
Thanks.
HuaweiPUser said:
Like a month ago, I was rooting my phone with Magisk. First, I installed TWRP, everything went OK. Then I flashed Magisk, everything was still OK. But when I tried to install Xposed with root privileges, it just installed and I rebooted, the phone got bricked, like the last level of soft brick! Factory reset wasn't working, I didn't had a Xposed Uninstaller, I didn't also have an SD Card, so I couldn't flash a ROM from SD Card using TWRP, also my PC didn't have a SD Card slot. It was rebootlooping over and over again. eRecovery gave me an error, saying "A serious boot problem has occured, it is hardly recommended to wipe data/factory reset." or something like that. I did what it said, still rebootlooping. Nothing was working, Xposed has completely screwed my phone. The last solution was to give the phone to Huawei Service Center. It came back 3 days later, and the results Xposed made was terrible. Huawei locked my bootloader and Xposed FRIED MY MOTHERBOARD. But they changed the motherboard, nothing else. So my warranty is still in place , but still, my phone is no longer open for rooting, flashing etc. I don't know what to do. I want know two things;
1- How did Xposed do that and is it not supporting my phone?
2- How can I unlock my bootloader back?
Thanks.
Click to expand...
Click to collapse
Xposed doesn't work on P smart at the moment ..everybody knows this and you were warned not to install it ...xposed did NOT do anything to your motherboard ...pay dc unlocker 4€ and download their application anf follow the instructions on how to unlock your bootloafer ...huawei service center will have installed the LATEST firmware which is IMPOSSIBLE to umlock bootloader ..so FIRST you will need to downgeade ...there are many posts explaining how to downfrade using firmware finder tool & dns
KevMetal said:
Xposed doesn't work on P smart at the moment ..everybody knows this and you were warned not to install it ...xposed did NOT do anything to your motherboard ...pay dc unlocker 4€ and download their application anf follow the instructions on how to unlock your bootloafer ...huawei service center will have installed the LATEST firmware which is IMPOSSIBLE to umlock bootloader ..so FIRST you will need to downgeade ...there are many posts explaining how to downfrade using firmware finder tool & dns
Click to expand...
Click to collapse
Thanks for the explanation, I get it now. But I wasn't warned to not to download Xposed, and where does it say P smart is not supported?
HuaweiPUser said:
Thanks for the explanation, I get it now. But I wasn't warned to not to download Xposed, and where does it say P smart is not supported?
Click to expand...
Click to collapse
I don't remember .... obviously it's not mentioned in every post but i definitely saw it in more than few spots ...anyway bad luck .. ultimately it's huawei who screwed us their clients by not releasing source code and locking bootloader ..making it a pain in the behind to build custom roms for the device and costing money to unlock it ...so the good devs just move on ...the sad situation is we are on the fringe ..lucky enough to have got root through a last ditch paid bootloadee unlock and treble support making custon roms possible albeit with broken camera , nfc and others ...uuugh stupid huawei .... definitely my first and last one ....
Sorry for a noob question.
I rooted my previous device, Xperia Z3 compact, without unlocking bootloader, so I am completely new to this stuff.
I am looking into buying a used X Compact and worried that the device no longer has its TA intact.
I've searched the forum but didn't quite find an answer to my question.
So, for X compact and many other xperia models, there is DRM fix that restore DRM keys on a bootloader-unlocked device, even if you didn't backup your TA and your TA is completely wiped by unlocking, correct?
Then, how can you tell the difference between a device that has its original TA (either still intact or TA properly restored from backup) and a device without TA but DRM keys restored?
And, if you can't tell the difference, what is the point of having TA backup and restoring it later?
Sorry it seems pretty basic stuff but I can't find any direct answer to it.
Hope someone can help. Thanks in advance!
tapa_t said:
So, for X compact and many other xperia models, there is DRM fix that restore DRM keys on a bootloader-unlocked device, even if you didn't backup your TA and your TA is completely wiped by unlocking, correct?
Click to expand...
Click to collapse
Not exactly - the drm fix is a mod that attempts to replicate the features and functions that are lost when wiping ta. I've never used it, so can't say myself, but it seems like people who have are happy with it. The main issue with wiping ta is the loss of Sony camera features and quality. I believe there are also other things attached to the ta, but most people probably wouldn't ever miss them.
If you wipe the ta without backing it up, then it is gone, and your only option is drm fix. Most people would probably rather have the ta intact...
levone1 said:
Not exactly - the drm fix is a mod that attempts to replicate the features and functions that are lost when wiping ta. I've never used it, so can't say myself, but it seems like people who have are happy with it. The main issue with wiping ta is the loss of Sony camera features and quality. I believe there are also other things attached to the ta, but most people probably wouldn't ever miss them.
If you wipe the ta without backing it up, then it is gone, and your only option is drm fix. Most people would probably rather have the ta intact...
Click to expand...
Click to collapse
Thanks -- but that doesn't really answer my question. Question is *HOW* do you tell apart a phone with drm fix and no TA from a phone with an intact TA. If you can't tell the difference, people can't be sure they've got the TA intact whether they prefer it or not.
tapa_t said:
Thanks -- but that doesn't really answer my question. Question is *HOW* do you tell apart a phone with drm fix and no TA from a phone with an intact TA. If you can't tell the difference, people can't be sure they've got the TA intact whether they prefer it or not.
Click to expand...
Click to collapse
Service menu > service tests > security
See in screen shot :
- Widevine... "OK"
- ckb... "OK"
- Fido keys provisioned
with drm fix
zokkii said:
with drm fix
Click to expand...
Click to collapse
Interesting - and thats with drm keys missing (TA wiped)?
yes,without drm keys
That's only half of the story. The DRM Fix library has two working modes, and what defines which mode it'll pick depends if you have your unique device key (that get wiped when you unlock the bootloader) flashed in an alternate TA Unit. You can extract your device key and then flash it on an alternate unit as long as you have a TA backup taken before unlocking the bootloader (the RootKernel utility from @tobias.waldvogel ships with the required tools to extract and flash your device key).
On the "normal" mode (DRM Fix + device key flashed on alternate TA unit) you have exactly the same functionality you would get on a bootloader locked device with its TA intact, everything works. But, in case you don't have your device key flashed into an alternate TA unit (e.g. unlocked the bootloader without backing up the TA first, lost backup, etc), then DRM Fix will work in emulation mode. On emulation mode, most features that check for DRM will still work (e.g. camera algorithms, X-Reality Engine, etc) but some specific DRM features that requires the device key (e.g. Widevine L1 decryption, HDCP on Screen Mirroring, etc.) won't work. As it was increasingly more difficult to find exploits for newer devices and firmwares, that's the mode most DRM Fix users utilize, I guess.
Now, how to tell a DRM Fix restored device apart a device with intact TA is a little tricky, but you basically have 3 situations:
• Bootloader locked device, security test in Service Menu shows both Widevine and CKB as [OK] [Active] => stock device with TA partition intact
• Security test in Service Menu shows [unknown] or [generic error] on Widevine or CKB (or both) => TA partition wiped, DRM Fix not applied
• Bootloader unlocked device, security test in Service Menu shows both Widevine and CKB as [OK] [Active] => TA partition wiped, DRM Fix applied
When a device has the DRM Fix applied, it's not possible to tell if it's working in normal or emulation mode until you try something that requires the device keys (e.g. Widevine L1 or HDCP on Screen Mirroring). If it works, DRM Fix is in normal mode, otherwise it's in emulation mode. Also, you can't trust the "Bootloader Status" info on the Security Test of the Service menu to tell whether the bootloader was unlocked or not, as it'll always report "locked" if you have the DRM Fix applied. A safe way to tell the bootloader status is (re)booting the device and observing if the "Your device has been unlocked and can't be trusted" message appears before the Sony logo. If that message appears, the bootloader was unlocked.
You'll also find many people debating whether FIDO Keys being provisioned or not actually indicates the status of the DRM Fix, but from my experience, they aren't related. Fact is that I had FIDO Keys not provisioned on my Xperia X right after I turned it on for the first time (brand new device, had just taken it from the box), but upon registering a fingerprint, FIDO Keys became Provisioned again. Same thing occurred after I backed up my TA with the dirtycow exploit then unlocked the bootloader, FIDO Keys became not provisioned but after enrolling a fingerprint they became Provisioned again, even through I hadn't installed DRM Fix yet at that point.
And to finish, keep in mind all I said on this post is only valid for Xperia devices that launched before Xperia XZ Premium. With XZ Premium launch, Sony reworked many parts of the DRM protection and the original DRM Fix from previous devices didn't work at all. Another user eventually developed a new DRM Fix solution for those newer devices, but it works completely different and I have absolutely zero experience with it.
Does this work on the Android 9.0 custom roms? DRM Camera fix for 9.0?
sheeplings said:
Does this work on the Android 9.0 custom roms? DRM Camera fix for 9.0?
Click to expand...
Click to collapse
No
mbc07 said:
That's only half of the story. ...
Click to expand...
Click to collapse
Thanks A LOT for this information!
I have searched for a long time for something similar but everyone seems to just know this and expecting everyone else too, so it's never thoroughly described, until now!
mbc07 said:
On the "normal" mode (DRM Fix + device key flashed on alternate TA unit)
Click to expand...
Click to collapse
Do you have any information that would help a noob accomplish this? Link to a good, noob adopted, step-by-step guide? So far I'm out of luck finding anything that will give me confidence enough to try it.
Thanks again!
Holton181 said:
Do you have any information that would help a noob accomplish this? Link to a good, noob adopted, step-by-step guide? So far I'm out of luck finding anything that will give me confidence enough to try it.
Click to expand...
Click to collapse
Sorry, nope. The process is "half" streamlined if your phone happens to be supported by the original Root Kernel tool or the modded version posted on the last pages of that thread, but you would still need knowledge on how to get a TA backup on your particular device and on unlocking the bootloader / flashing a modded kernel. If your phone isn't supported then the process also involves manually modding the kernel to include the DRM Fix library too, and none of that is noob-friendly, at all...
If you can't/don't want to deal with it, your best bet is searching at your device's subforum, perhaps somebody already did the work for your particular phone model and published a ready to flash, DRM Fixed kernel there...
mbc07 said:
Sorry, nope.
Click to expand...
Click to collapse
Okay, thanks anyways. My understanding of this is much better already after your description.
Backing up TA, unlocking bootloader and rooting is the easy part, pretty good understanding how its done. It's how to make good use of the DRM:s that's all new to me.
My device is the full size X (not Compact as in this sub-forum), my wife's old working phone. I'll try to search the forum for it.
my first g6 had a broken screen last week. me being abusive to it. from frustration.
bought a used g6 as a backup very quickly but im not liking v9.0
id like to install the first 7.0 version it ever had available H870. I have 3 apps total installed more of a pro privacy advocate so no browser and would like to shut those annoying update popups which are extremely intrusive and come at the worst times. would like to block as much as possible to also have battery life
I dont understand what the roo does, what the bootloader does and I understand I need to flash a kdz rom. if I understand, I need to install 7.0 (not 7.1 or later) then use the root and bootloader to block updates notifications and to remove default apps in the phone.. basically tweak system things...is this correct?
I used to tinker with windows mobile back in the days but after years of fear of bricking and only have one phone, I had to suffer through annoyances in the OS they give. it is time to have a phone that doesnt annoy me and isnt intrusive. I really do need calmness after 18 months of hell with covid.
inevitably I will move to pinephone once it gets mature. for now using this g6. I dont run after the newest models.
any insight or experiences or tips you could throw at me would be appreciated as I think i may be mixing things up
stay afe
i have a used H870 here. Did the root+twrp, up to PIE and tryed/flashed many things, but wasn´t that happy at all. That was a few month ago. A week ago I replaced my battery and tada, sweet runner. So again I wanted more and bricked it to "no sim" after restoring from a kernel here. Since there isnt much for Pie, roms, deadlinks, broken twrp etc. the only tool which worked and helped me was LG bridge to restore to latest stock pie.
I would recommend u to root without recovery via magisk/fastboot method and go for some adaway, acc battery charger, lsposed + gravity, debloat and maybe a kernel manager + etc.
dont forget, when u have sporadic lags, go for the battery.
gl on ur way mate
----
ps just for info
the only working usb drivers where delivered via the LG bridge tool driver update for me, i tryed many..