So just putting this thread together just for research in hope of a Widevine Level 1 on all devices
Some people say its not possible, but im literally steps away from gaining this on an un authorized S905x device
So what do we know so far?
DRM is implemented almost everywhere in the firmware, partitions include
-booloader
-system
-uboot
-kernel
... plus more?
So its not a matter of copying files and adding a few properties to the rom.
From my underatanding and confirmed by a source, the bootloaded must be able to withhold/wipe core DRM data if the bootloader is unlocked or the device is rooted.
There may be an acception to root over UART.
The good think about AMLogiv devices is the simple fact that they distribute updates bundled as firmware, some devices have Widevine L1, some dont.
As most boards/chips are almost exactly the same with slight differences that do no effect functionallity, theoretically we could flash a Widevine L1 firmware on a non widevine L1 device.
Thats the firmware problem solved.
But thats still not enough, from the very very small research and tests ive been able to conduct, we need to flash keys with USB burning tool, and so far im unable to gain these keys..
The keys i think we may require are DHCP and WidevineKeybox, these keys are distributed by manufacturers/sellers of our boxes, they are license files required for flashing certain firmware, if anyone has keys like this please let me know.
As for anyone else who has any info on how we may be able to achieve this goal, if your information is very relavent, PM me, we do not want Google, netflix, amlogic, etc to know we have found a way around this.
For any other useful info post in this thread.
Hi
I'm using VideoStrong K III pro device , and few months ago they update Widevine key . In attachment you can see the app with keys to few videostrong devices . But few weeks ago this key was blocked by Google I think. Maybe it help somehow
bratmat said:
Hi
I'm using VideoStrong K III pro device , and few months ago they update Widevine key . In attachment you can see the app with keys to few videostrong devices . But few weeks ago this key was blocked by Google I think. Maybe it help somehow
Click to expand...
Click to collapse
Hey, my DRM research is complete, seems those new keys were released due to my research as i did gain Widevine L1 on an uncertified device, thats why i removed my other thread
How do I get l1 on my device with wiped drm keys
I'm stuck with l3 on my device (asus zenfone max pro m1) .my drm keys are wiped by the firmware.how do I get l1 on device?
Related
hi, i am totally new to rooting. my phone is sony Xperia Mk16i with rooting status - Bootloader unlock status: Yes. the ROM is factory installed 2.3.4.
i was checking this forum and noticed the test point method of rooting which allows to maintain the DRM keys. i do not purchase any songs or videos online neither do i use the trackID app of my phone. is there any other reason to save the DRM keys other than the ones mentioned?
i noticed a thread in another forum where someone was complaining about not being able to use camera after rooting without saving the DRM keys.
i would also like to know if there is any method of rooting the phone without unlocking the bootloader. the main reason i want to root my phone is to increase its internal memory and be able to use the USB OTG option in my phone which is locked.
i am trying this after expiry of the warranty period and seriously can't afford to brick my phone.
any help or answers will be much appreciated.
thank you
austicorn said:
hi, i am totally new to rooting. my phone is sony Xperia Mk16i with rooting status - Bootloader unlock status: Yes. the ROM is factory installed 2.3.4.
i was checking this forum and noticed the test point method of rooting which allows to maintain the DRM keys. i do not purchase any songs or videos online neither do i use the trackID app of my phone. is there any other reason to save the DRM keys other than the ones mentioned?
i noticed a thread in another forum where someone was complaining about not being able to use camera after rooting without saving the DRM keys.
i would also like to know if there is any method of rooting the phone without unlocking the bootloader. the main reason i want to root my phone is to increase its internal memory and be able to use the USB OTG option in my phone which is locked.
i am trying this after expiry of the warranty period and seriously can't afford to brick my phone.
any help or answers will be much appreciated.
thank you
Click to expand...
Click to collapse
Yes... Rooting can be done without unlocking bootloader...try the eroot thread...
Sent from my Xperia Neo V using Tapatalk 2
Hi!
I recently purchased a Verizon-build Samsung Galaxy A10e (the "economy Flagship" / little-brother of the A10) but XDA has very little information on this phone. Would this be the best place to try to find/request information?
Thanks for your help!
where can i get more developer information on this phone
Give it some time before developers start posting, since the phone was released only a couple of monthes ago. It will be a good minute before you start seeing significant posts for the galaxy a10 e. Keep updating by searching on a regular basis. Check howardforums or android central as well.
On another note:
Some of us need to know the a10e galaxy update to android 10, anyone got then lastest news on that yet? I got one with metro pcs.
Thx
Sent from my SM-A102U using Tapatalk
yea like alot of sites keep saying galaxy a10e will not be getting android 10 and one ui 2.0 but the fail to see samsung own site says they will probavly in may or june of 2020
Also using an SM-A102U device, I believe the official Android 10 date is sometime in the first half of 2020. I believe March.
What would really help us is pHH-Treble support for these devices and Android 10, which I can't find any info for, aside from a GSI post on the Galaxy a20, which has (essentially) the same Exynos chip.
timba123 said:
On the metro variant I was trying to figure out bootloader unlock and the phone vibrated and a yellow exclamation ! Appeared at bottom of black screen. What is that?
Click to expand...
Click to collapse
depends on wat u mean by trying to figure it out lol.. if its like any the other usa variants its not unlockable which is why u dont see oem unlock
timba123 said:
This.
Click to expand...
Click to collapse
i dont kno wat that is but seems to be a indicator for your charger.. maybe not fast charging or something.. i assume the device is off when you get this screen.. if its off and plugged in via pc it could simply be indicating its not fast charging as its being charged from the usb port.
Sent from my SM-N976V using Tapatalk
timba123 said:
It's not off exactly. Kinda reminds me of system crash on eng fac roms. I've seen articles about older devices and it meaning no battery or no charging like you say. Guess I got over excited for nothing lol. Though it might be a hackable situation etc or different mode of some kind.
Click to expand...
Click to collapse
Yea.. and fyi, a common misconception is "eng fac" roms are two completely different things lol.. it's a pet peeve of mine which I owe to all the firmware sites and generic "guides" on the web lol.
They always refer to factory/combo roms as "eng" when they are not eng at all.. fac roms are debuggable (ro.debuggable=1) and permissive and adb enabled by default and dmv disabled with a bare bone os mainly used for testing or fixing issues with the device.
Eng on the other hand is typically a stockish build with su binary by default (allows actual adb root shell) is permissive, verity disabled, contains other high level engineering software etc etc that is supposed to be used by engineers to test their software and things of that nature. My sampwnd root for s8/s8+ for example used eng system.img to gain root. Older devices did have eng boot.img many used to root devices but since s8 and newer they are no longer used because samsung implemented security measures to where u cant flash or run them without an eng token and device being in actual eng mode. Eng tokens are hard to find as they are device specific and need to be generated on samsung servers at which if u can find someone willing to make one they are usually expensive since they need to have a legit business, purchase a signing cert from samsung to be able to generate eng tokens as well as they typically need to also pay for each individual token which just the signing cert alone I've heard various prices from thousands to 100k lol. Then after all that if you have an eng token and device is in eng mode then it's not the same as a bl unlock as you would need to flash eng firmware which is another adventure to locate and probably another pretty penny.
Rant on eng/fac differences is over lmao.
On a side note, I'm working on something that "might" work... according to my dev buddies it will work.. it's a process tho as I need to generate some custom files and I never did this before (I mainly use usa locked snaps) .. but if all goes as planned with some trickery could probably unlock the bl and at the very least root the device.. stay tuned lol
timba123 said:
On the metro variant I was trying to figure out bootloader unlock and the phone vibrated and a yellow exclamation ! Appeared at bottom of black screen. What is that?
Click to expand...
Click to collapse
I also tried (with my limited knowledge here) to enable OEM bootloader unlock by changing the settings flag in the phone but have not had luck. I talk about what I tried to do/have a screenshot showing where the system has it looked in this post:
https://forum.xda-developers.com/ga...rint-oem-lock-developer-t3963898/post80909957
I have also looked at using Tasker/other tools to try to change something here or to see if there's an intent or action or something that will trigger the unlock but haven't had luck.
timba123 said:
So since this is the only A10e root thread. I'll post here. After browsing the internet I found out that Samsung changed some security. Now fac combo cant be flashed with 3.14 odin which newer devices like our A10e will not work with odin 3.13 and before patched or not. A new odin needs to be made. Patched. And the new Security for samsung.
Click to expand...
Click to collapse
This isnt new information. I do not think a new/patched odin will work since it uses a token system. Trying to flash will say you need approval to use factory binary.
With that being said you can use a factory bin token which will then allow you to flash combo rom.
There are ways to bypass need for a token but they are not public.
Also tokens are device specific and if you can find someone to get them they are not free.
Side question that's not totally related but I'm finding conflicting answers online:
Does the A10e NOT have USB-OTG capabilities? :-/
I don't have a USB-C OTG cable to test myself. I realize this phone purposely does not have some features/capabilities that I guess are supposedly deemed more "premium," in order to keep this phone in a class I've heard described as "Economy-Flagship," (lol ). Hence: no wireless charging, no fingerprint reader, no gyroscope, no proximity sensor (this exclusion is kind of annoying - surely I can't be the only person experiencing the annoying phenomenon of chronic cheekbone-call-muting? ). But overall, I'm super happy with this phone!
I also wish I could disable Knox but I don't think that's possible without the OEM bootloader unlock setting enabled.
timba123 said:
No not new info but figured alot of people especially new people could use the info. Lol they sure are locking down phones. I wonder what influence the NSA etc have.
Click to expand...
Click to collapse
govt contracts are definitely a big part of it.. every device manufacturer wants that govt money lol
elliwigy said:
govt contracts are definitely a big part of it.. every device manufacturer wants that govt money lol
Click to expand...
Click to collapse
^This makes a lot of sense.
Sorry for my english. I'm looking for help ... i was 3 weeks in US and i lost my phone. So i buyed this A10e with boost mobile but i didn't activate it because they were trying to force me to buy a monthly subscription, wich i didn't... I bring the phone just for wifi use because is a phone with good specs for the price of 90$... and then the horror shows in a form of Harassing message ... trying to make me "accept terms and conditions" and then Boom the phone was restricted from data usage and other things, i tried to unlock the OEM and nothing, also i wipe the phone and it works fine but it keeps harassing with sudden appears of that screen asking if you accept, the icon of that screen is a peace of chess. So my question is ... Can i force an instalation of other rom? in sammobile is a international rom, so, even if i can't unlock the oem , can i install it? is there a way to root the device without the oem unlock? Thanks in advance
reyesergio23 said:
Sorry for my english. I'm looking for help ... i was 3 weeks in US and i lost my phone. So i buyed this A10e with boost mobile but i didn't activate it because they were trying to force me to buy a monthly subscription, wich i didn't... I bring the phone just for wifi use because is a phone with good specs for the price of 90$... and then the horror shows in a form of Harassing message ... trying to make me "accept terms and conditions" and then Boom the phone was restricted from data usage and other things, i tried to unlock the OEM and nothing, also i wipe the phone and it works fine but it keeps harassing with sudden appears of that screen asking if you accept, the icon of that screen is a peace of chess. So my question is ... Can i force an instalation of other rom? in sammobile is a international rom, so, even if i can't unlock the oem , can i install it? is there a way to root the device without the oem unlock? Thanks in advance
Click to expand...
Click to collapse
no.. bl is locked.. only stock official firmware can be flashed
timba123 said:
Found a rooted AP tar but gives SHA error using Odin 3.14
Click to expand...
Click to collapse
doesnt work.. ur getting error bcuz its modified which cant use bcuz bl is locked
timba123 said:
Seems to be verizon firmware by the bootloader number etc. The firmware I posted pics of. I'd upload it but my browser keeps crashing trying to upload it
---------- Post added at 04:42 AM ---------- Previous post was at 04:25 AM ----------
https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=200612
Looks like root kernel for metro or tmobile
Click to expand...
Click to collapse
correct.. all it is is stock firmware with a rooted/patched kernel for unlockable variants
Combination File, for FRP & bootloop Repair
http://www.mediafire.com/file/ekejzhig7b9zx7r/ROMProvider.COM_SM-A102USQU1ASF1.rar/file
mark332 said:
Combination File, for FRP & bootloop Repair
http://www.mediafire.com/file/ekejzhig7b9zx7r/ROMProvider.COM_SM-A102USQU1ASF1.rar/file
Click to expand...
Click to collapse
how do you expect people to flash it without a factory binary token?
timba123 said:
Is OTP similar or related to the factory token? Like a password?
Click to expand...
Click to collapse
nope.. otp more of a one time password.. the token is something that uses device specific identifiers that then gets sent to a server where it gets signed and sent back.. then it needs to b physically flashed to the device
Sent from my SM-G977P using Tapatalk
Hi, @ante0 , @Pretoriano80 and everyone else!
Been lurking on these forums ever since mate 10 Pro was released, but due to being one of the folks to downgrade from emui 9 to brick I had to take my phone to service for board swapping as I wasn't in a situation to do the testpoint fix myself.
Now, I'm looking to get the bootloader unlock code again and to my surprise even the 3rd party sites are down.
There's a guy at minstryofsolutions that offers bootloader unlock code using testpoint but he asks for 40$ + access to pc for 2 hours + refuses to describe in any way what he's doing to the device and why will the device end up rebranded + new imei and with it new bootloader code ( Obviously device in that condition can't be taken into a Huawei service center) .
So, upon searching and trying to find if anyone had found a way to unlock using testpoint I stumbled upon this : https://forum.xda-developers.com/mediapad-m5/how-to/downgrade-unbrick-huawei-device-methods-t3915693
Op and several others seem successful with downgrading their devices and using dc unlocker to get the code once the security patch is no more.
Op even mentions that for kirin 970 it's probably the same process but I haven't seen anyone sharing their experience doing the same on 979 devices.
Couple users are having issues as well and while op was quite helpful he and several others that were helping out seem to have been gone missing. There's a guy helping out with issues regarding this process but it seems rather finicky when even after doing all this and flashing with dload certain parts like lte modem remain present on a WiFi only tablet.
Does anyone have passes for easy firmware or dc unlocker firmware database? Is anyone willing to give these a try and see if the process will work on our devices or if it will ask for verification of some kind for images being flashed?
It looks quite promising, so if anyone has a bricked device ( Maybe someone that was refused at the Huawei repair center during the wave of downgrades ) would you be willing to give it a try?
I've got no tools, no passes and no other device to use while playing with this.
Obviously, I'm not asking for you guys to go out of your way and brick the device so I can know whether this is a viable option or not lol.
Just thought about sharing and seeing if anyone more knowledgeable has anythiny they'd like to add to this as a tip or personal experience trying this method.
This might be what we are looking for when it comes to unlocking device / downgrading to lower versions.
Hopefully the post I linked helps someone, in case anyone has experience with this please share as well!
Anyways thanks in advance!
Rstment ^m^ said:
Hi, @ante0 , @Pretoriano80 and everyone else!
Been lurking on these forums ever since mate 10 Pro was released, but due to being one of the folks to downgrade from emui 9 to brick I had to take my phone to service for board swapping as I wasn't in a situation to do the testpoint fix myself.
Now, I'm looking to get the bootloader unlock code again and to my surprise even the 3rd party sites are down.
There's a guy at minstryofsolutions that offers bootloader unlock code using testpoint but he asks for 40$ + access to pc for 2 hours + refuses to describe in any way what he's doing to the device and why will the device end up rebranded + new imei and with it new bootloader code ( Obviously device in that condition can't be taken into a Huawei service center) .
So, upon searching and trying to find if anyone had found a way to unlock using testpoint I stumbled upon this : https://forum.xda-developers.com/mediapad-m5/how-to/downgrade-unbrick-huawei-device-methods-t3915693
Op and several others seem successful with downgrading their devices and using dc unlocker to get the code once the security patch is no more.
Op even mentions that for kirin 970 it's probably the same process but I haven't seen anyone sharing their experience doing the same on 979 devices.
Couple users are having issues as well and while op was quite helpful he and several others that were helping out seem to have been gone missing. There's a guy helping out with issues regarding this process but it seems rather finicky when even after doing all this and flashing with dload certain parts like lte modem remain present on a WiFi only tablet.
Does anyone have passes for easy firmware or dc unlocker firmware database? Is anyone willing to give these a try and see if the process will work on our devices or if it will ask for verification of some kind for images being flashed?
It looks quite promising, so if anyone has a bricked device ( Maybe someone that was refused at the Huawei repair center during the wave of downgrades ) would you be willing to give it a try?
I've got no tools, no passes and no other device to use while playing with this.
Obviously, I'm not asking for you guys to go out of your way and brick the device so I can know whether this is a viable option or not lol.
Just thought about sharing and seeing if anyone more knowledgeable has anythiny they'd like to add to this as a tip or personal experience trying this method.
This might be what we are looking for when it comes to unlocking device / downgrading to lower versions.
Hopefully the post I linked helps someone, in case anyone has experience with this please share as well!
Anyways thanks in advance!
Click to expand...
Click to collapse
You can as I've done it.
Use testpoint (this will void warranty as you have to remove back of the phone) and flash bootloader files from DC Phoenix, there are several Kirin970 to choose from but only one should work. DC will tell you when phone is in fastboot mode after flashing.
Then I used IDT (Image Download Tool) to flash board firmware. Boot to board firmware and used HCU to repair imeis and all that. Then used HCU to get an unlock code. After this flash dload firmware back to Oreo (needs to be a new dload because of updated bootloader).
HCU fix guide for BLA:
1)Flash oeminfo (own backup) from fastboot OR dump existing oeminfo using adb pull (adb pull /dev/block/bootdevice/by-name/oeminfo) then flash it from fastboot.
2)Backup modemnvm_system, modemnvm_factory and modemnvm_backup using adb pull from a command prompt (/dev/block/bootdevice/by-name/modemnvm_system and so on)
3)Flash backed up modemnvm_system, modemnvm_factory and modemnvm_backup from fastboot
3)Modify and brand with HCU in the CDMA tab (check everything but those that erase/flash empty board) (remember to fill vendor and cust)
4)Unlock sim 'Direct SIM Unlock'
5)Read Bootloader code if you ever used HCU to get code before or if you need unlock code
6)Download and flash Oreo service firmware from androidhost.ru using a OTG cable and a memory stick. Pick the latest Oreo one you find for your cust
If you fail to do any of the steps above you will end up with no IMEIs or 'No Network' and/or Sim lock
So you'd need: DC/HCU pass and unencrypted board firmware (gem-flash and easy-firmware has them but they're paid.).
I have not tested using DCs own board firmware.
ante0 said:
You can as I've done it.
Use testpoint (this will void warranty as you have to remove back of the phone) and flash bootloader files from DC Phoenix, there are several Kirin970 to choose from but only one should work. DC will tell you when phone is in fastboot mode after flashing.
Then I used IDT (Image Download Tool) to flash board firmware. Boot to board firmware and used HCU to repair imeis and all that. Then used HCU to get an unlock code. After this flash dload firmware back to Oreo (needs to be a new dload because of updated bootloader).
HCU fix guide for BLA:
1)Flash oeminfo (own backup) from fastboot OR dump existing oeminfo using adb pull (adb pull /dev/block/bootdevice/by-name/oeminfo) then flash it from fastboot.
2)Backup modemnvm_system, modemnvm_factory and modemnvm_backup using adb pull from a command prompt (/dev/block/bootdevice/by-name/modemnvm_system and so on)
3)Flash backed up modemnvm_system, modemnvm_factory and modemnvm_backup from fastboot
3)Modify and brand with HCU in the CDMA tab (check everything but those that erase/flash empty board) (remember to fill vendor and cust)
4)Unlock sim 'Direct SIM Unlock'
5)Read Bootloader code if you ever used HCU to get code before or if you need unlock code
6)Download and flash Oreo service firmware from androidhost.ru using a OTG cable and a memory stick. Pick the latest Oreo one you find for your cust
If you fail to do any of the steps above you will end up with no IMEIs or 'No Network' and/or Sim lock
So you'd need: DC/HCU pass and unencrypted board firmware (gem-flash and easy-firmware has them but they're paid.).
I have not tested using DCs own board firmware.
Click to expand...
Click to collapse
Thanks a lot!
Will any of this process leave bootloader unlocked / relocked along the way?
I'm experiencing screen burn in due to outdated firmware and was gonna get the code, apply new adhesive I buy online and have them replace the device's screen + seal it properly in the process so the water resistance remains - kinda essential to hide any signs of tampering like bootloader unlock '-' ( 2nd burn in on Oreo firmware now, both happened within few months of the device running old firmw )
Thanks for the guide as well!
I'm not completely sure how to do the whole process yet but I'll try getting all the software I can right now and try figuring it out.
One question tho, do you have any screenshots you can share of which firmware will work out of those several that you mentioned and is there any possibility of brick by flashing wrong xload, etc.?
I'm on 8.0.0.156 c432 and was gonna drop to 142 or 143 - will have to check which one is the latest without security patch.
Glad to know this is a possibility! Will order the tools required for this and when / if I'm successful I'll create seperate thread under guides as there prolly are peps still trying to unlock.
Rstment ^m^ said:
Thanks a lot!
Will any of this process leave bootloader unlocked / relocked along the way?
I'm experiencing screen burn in due to outdated firmware and was gonna get the code, apply new adhesive I buy online and have them replace the device's screen + seal it properly in the process so the water resistance remains - kinda essential to hide any signs of tampering like bootloader unlock '-' ( 2nd burn in on Oreo firmware now, both happened within few months of the device running old firmw )
Thanks for the guide as well!
I'm not completely sure how to do the whole process yet but I'll try getting all the software I can right now and try figuring it out.
One question tho, do you have any screenshots you can share of which firmware will work out of those several that you mentioned and is there any possibility of brick by flashing wrong xload, etc.?
I'm on 8.0.0.156 c432 and was gonna drop to 142 or 143 - will have to check which one is the latest without security patch.
Glad to know this is a possibility! Will order the tools required for this and when / if I'm successful I'll create seperate thread under guides as there prolly are peps still trying to unlock.
Click to expand...
Click to collapse
I doubt that the burn-in is because of the old firmware, probably the oled panel it's getting old.
You should do the other way around, first send it to Huawei for a display replacement and then get the unlock code.
The procedure it's not really easy and the water resistant part it's the last of your problem, first you must make sure that you don't break the glass back cover when you open it up. xD
Probably Huawei's repair center won't even bother to replace the display only, but they will replace almost everything, so you would endup with a locked bootloader again.
Pretoriano80 said:
I doubt that the burn-in is because of the old firmware, probably the oled panel it's getting old.
You should do the other way around, first send it to Huawei for a display replacement and then get the unlock code.
The procedure it's not really easy and the water resistant part it's the last of your problem, first you must make sure that you don't break the glass back cover when you open it up. xD
Probably Huawei's repair center won't even bother to replace the display only, but they will replace almost everything, so you would endup with a locked bootloader again.
Click to expand...
Click to collapse
The display literally burned in couple months after I boguht the device and and we still had the emui 8 only. Replaced it and switched to the 9 the same month. All was good for a year or so untill they replaced motherboard. Now the same thing all over again, few months have passed - literally 2/3 months and the screen burned in again at the same spot - navigation bar.
The opening part doesn't look that complicated, was thinking of buying a heating plate, heat phone to 120°C and go back and forward cutting adhesive then heating the phone again. Should be fast and efficient this way.
The finicky part that I'm worried about has to do with bricking the device or shorting the motherboard in some way '-' Maybe service also uses some repair stickers that aren't present on any of the guides and will get dmged when I open the device - after all, I took the device for repairs under warranty at least 5+ times by now
Last time for the replacement they indeed replace almost everything - display, battery, back cover, new frame - essentially a new device w same motherboard.
Pretoriano80 said:
I doubt that the burn-in is because of the old firmware, probably the oled panel it's getting old.
You should do the other way around, first send it to Huawei for a display replacement and then get the unlock code.
The procedure it's not really easy and the water resistant part it's the last of your problem, first you must make sure that you don't break the glass back cover when you open it up. xD
Probably Huawei's repair center won't even bother to replace the display only, but they will replace almost everything, so you would endup with a locked bootloader again.
Click to expand...
Click to collapse
Rstment ^m^ said:
The display literally burned in couple months after I boguht the device and and we still had the emui 8 only. Replaced it and switched to the 9 the same month. All was good for a year or so untill they replaced motherboard. Now the same thing all over again, few months have passed - literally 2/3 months and the screen burned in again at the same spot - navigation bar.
The opening part doesn't look that complicated, was thinking of buying a heating plate, heat phone to 120°C and go back and forward cutting adhesive then heating the phone again. Should be fast and efficient this way.
The finicky part that I'm worried about has to do with bricking the device or shorting the motherboard in some way '-' Maybe service also uses some repair stickers that aren't present on any of the guides and will get dmged when I open the device - after all, I took the device for repairs under warranty at least 5+ times by now
Last time for the replacement they indeed replace almost everything - display, battery, back cover, new frame - essentially a new device w same motherboard.
Click to expand...
Click to collapse
Also, if they do replace stuff the code you get through DC will not work.
It works by modifying some strings in the oeminfo partition, so if they were to wipe and reflash everything your code would be lost.
If they replace motherboard you will need a new unlock code.
There is a sticker on one of the screws you need to remove, so they will know you did open it anyway.
Bricking is no problem as you can unbrick using testpoint. Shorting shouldn't be a problem. I tried all the visible points and only 1 or 2 actually send current back so USB devices in computer restarted xD But none of them shorted my phone.
ante0 said:
Also, if they do replace stuff the code you get through DC will not work.
It works by modifying some strings in the oeminfo partition, so if they were to wipe and reflash everything your code would be lost.
If they replace motherboard you will need a new unlock code.
There is a sticker on one of the screws you need to remove, so they will know you did open it anyway.
Bricking is no problem as you can unbrick using testpoint. Shorting shouldn't be a problem. I tried all the visible points and only 1 or 2 actually send current back so USB devices in computer restarted xD But none of them shorted my phone.
Click to expand...
Click to collapse
I see on pictures online that there are some points exposed with the shield on. Will take a look at picture you posted earlier for testpoint location to determine if indeed you can access it without removing the shield - hence not touching the stickers you mentioned - ty!
Wdym by losing dc unlocker code tho?
Does it not read the bootloader code of the device - meaning after they wipe / flash their stuff I can use the same code again to unlock via fastboot?
Or can it not read the code and just modifies the nvme files or whatev inside the partition to allow for a custom bootloader code?
Thanks for all the info! Will go look now for the picture then decide whether I'll open before or afterwards depending on the position of test point.
Rstment ^m^ said:
I see on pictures online that there are some points exposed with the shield on. Will take a look at picture you posted earlier for testpoint location to determine if indeed you can access it without removing the shield - hence not touching the stickers you mentioned - ty!
Wdym by losing dc unlocker code tho?
Does it not read the bootloader code of the device - meaning after they wipe / flash their stuff I can use the same code again to unlock via fastboot?
Or can it not read the code and just modifies the nvme files or whatev inside the partition to allow for a custom bootloader code?
Thanks for all the info! Will go look now for the picture then decide whether I'll open before or afterwards depending on the position of test point.
Click to expand...
Click to collapse
When you use HCU to get code it writes stuff to oeminfo, replacing 2 strings with "DC-UNLOC". So that's used in calculation of code. If you flash back stock, unmodified, oeminfo after using HCU you won't be able to use the code it generated.
Testpoint is located under the shield, so it's not possible to get to it without removing the shield. I have my phone with shield on infront of me. And I can't remember which screw had the sticker on it. If it's on one of the corners I guess you could try to bend it up to get to testpoint.
I just can't understand why the won't release the bootloader unlock at this point? The phone is now 'outdated' and old.... where is the harm?
ante0 said:
When you use HCU to get code it writes stuff to oeminfo, replacing 2 strings with "DC-UNLOC". So that's used in calculation of code. If you flash back stock, unmodified, oeminfo after using HCU you won't be able to use the code it generated.
Testpoint is located under the shield, so it's not possible to get to it without removing the shield. I have my phone with shield on infront of me. And I can't remember which screw had the sticker on it. If it's on one of the corners I guess you could try to bend it up to get to testpoint.
Click to expand...
Click to collapse
Thanks but I'm still having hard of a time following ?
After you use hcu it modifies the oeminfo to get strings it needs for calculations - You get the code aftwerards and your oeminfo is modified, right?
What I don't get is how flashing stock makes code unusable tho?
Is it not original bootloader code we'd get if Huawei site was still up? That code should be usable even after all modifications were reflashed with stock, no?
Or is it a custom code that depends on modified oeminfo to work?
Rstment ^m^ said:
Thanks but I'm still having hard of a time following ?
After you use hcu it modifies the oeminfo to get strings it needs for calculations - You get the code aftwerards and your oeminfo is modified, right?
What I don't get is how flashing stock makes code unusable tho?
Is it not original bootloader code we'd get if Huawei site was still up? That code should be usable even after all modifications were reflashed with stock, no?
Or is it a custom code that depends on modified oeminfo to work?
Click to expand...
Click to collapse
It's a custom code. If you use HCU to generate a code it invalidates your stock code. If you flash back stock oeminfo you can use the code Huawei gave you but not the HCU code (until you use HCU again to generate code).
Iirc on Kirin960 (and probably below it) you can use both HCU and stock code, so it uses another way of generating it I guess
Has anyone tried this approach for a MATE 10? or would you recommend it?
FUHuawei said:
Has anyone tried this approach for a MATE 10? or would you recommend it?
Click to expand...
Click to collapse
What method are you talking about?
If through testpoint, then yes!
Everything works perfectly
geogsm_1 said:
What method are you talking about?
If through testpoint, then yes!
Everything works perfectly
Click to expand...
Click to collapse
Yes, of course, I meant through test point. Do you know of any good step by step guide on how to do it? I want to try it and post here my results, if everything goes well I hope everyone ditches huawei software.
Also, I have searched around for options regarding ROMs, does anyone recommend anything in particular?
FUHuawei said:
Yes, of course, I meant through test point. Do you know of any good step by step guide on how to do it? I want to try it and post here my results, if everything goes well I hope everyone ditches huawei software.
Also, I have searched around for options regarding ROMs, does anyone recommend anything in particular?
Click to expand...
Click to collapse
Yes, I know the method) and have long written instructions on another forum with the permission of my teacher.
Decision made
On Huawei Mate 10 / Mate 10 Pro /, you can get the bootloader unlock code using a testpoint. But you need to have a programmer such as MRT / SIGMA / HDE / HCu-Client
So I've been searching the whole internet yet I couldn't find any working way to root honor 7 lite NEM-L21
EMUI 5.0
Android 7
I want to do it using a Magisk
Additionally I couldn't find any way to unlock the bootloader code for my honor 7 lite
Could someone please provide the detailed step by step instruction on how to do this without breaking the phone down?
Please I beg you I badly need to root my phone without any trouble with Magisk.
Does anybody have the working TWRP file that will not break the phone and the correct version of Magicdisk and could provide the detailed way on how to do it?
It's very important for me yet for years I can't find the very detailed description and root the phone without breaking it.
I beg for you help the crucial thing is to get my bootloader code but it doesn't seem to be possible anymore? :|
I've heard many different version on which TWRP works for that device and I've heard that it's the same device that is called Huawei Honor 5C for whatever reason?
For years I manage to figure out that one of those TWRPs works but I couldn't exactly figure out which one of these won't brick the device:
1. twrp-3.0.2-0-nemo-modaco-rc1.img (This one wasn't tested by me which presumably worked)
2. twrp-3.1.1-0-venus.img (This one was said not to work for other person?)
Now Im so totaly confused because I can't find the file that is presumably working nowhere on the internet anymore the second I can't even get the bootloader code for free anywhere other than some fake oferts that will hack your bank card info and clear it out of the cash and the third I only presume that "UPDATE-SuperSU-v2.65-20151226141550" version would work with that.
Can anybody help me and is 100% sure of the links and files in 2020 that won't ruin my phone?
Does anybody have any idea how to get the bootloader code WITHOUT using your credit card info for FREE?
So far I've been through hundreds of threads hundreds of posts and endless hours reading and studying it. Yet I couldn't find the working method that people would not have the problems with and I dont want to destroy my phone because it's the only one I have and I dont have the money to afford another one and I think that's the only and last place where I can ask for help.
My phone got bricked so I unbricked it by following this guide https://forum.xda-developers.com/t/unbrick-realme-7-pro-ui-1-0-android10.4347457/ (Thanks to xxx8086)
But i forgot to back up persist.img and now my fingerprint is not working.
I tried to search about persist.img so i can download it from anywhere but i didn't find any thing
So can anyone provide me with a persist.img download link for realme 7 pro? please
Thanks in advance.
Sorry to say, but I don't think there's any way as of now to recover the fingerprint, once the bootloader is unlocked and/or the device is rooted, you can't recovery your fp, it's like in the case of Samsungs where KNOX gets altered after unlocking the BL and lose the access to Samsung Pay.
I'm also facing the same problem, and if anyone found a fix, I'd happy to hear it.
I have the same problem of the fingerprint, it is not recovered with the persist.img of another realme? I also have problems with face unlock and fast charging. Will they always be related to persist.img damage?
Hello. I have the same problem, have you been able to solve it?
TheAngryGuitarist said:
Sorry to say, but I don't think there's any way as of now to recover the fingerprint, once the bootloader is unlocked and/or the device is rooted, you can't recovery your fp, it's like in the case of Samsungs where KNOX gets altered after unlocking the BL and lose the access to Samsung Pay.
I'm also facing the same problem, and if anyone found a fix, I'd happy to hear it.
Click to expand...
Click to collapse
Sry I was busy this year so I couldn't open,
I solved the problem by going to realme customer service, It was so easy that it didn't cost me ANYTHING!
He just flashed the software of the specific phone using msm download tool and what I mean by specific is the software that was designed just for ur phone like exclusively for ur IMEI.
He said the only problem I did that I didn't flash the correct software for the phone. Hope I helped