Related
Hello,
I wanted to ask if there is a way to remove the unlocked bootloader message. I find this message very annoying and ugly. On my older OnePlus X there was a way to get rid of this message, so I thought that there might be a way on the OnePlus 5T.
Yes, simply re-lock the bootloader and it's gone.
dreinulldrei said:
Yes, simply re-lock the bootloader and it's gone.
Click to expand...
Click to collapse
Thats not what i want to do, i want it to be unlocked and that message gone
No way. The price to pay for benefits of root...
I don't think you can do it unless you want to risk a hard brick.
On the phones I know of if it being eliminated its not actually eliminated, its just hidden. The message is replaced with an image of something else.
Here is an example utility (Nexus 5X)
Just looks like the boot image needs unpacked, modified, repacked, and flashed?
well, you can change it by flashing splash image... see in Moto G5s plus thread there is a solution....
yourSKD said:
well, you can change it by flashing splash image... see in Moto G5s plus thread there is a solution....
Click to expand...
Click to collapse
No, it works differently in the OP5T. I don't think it's possible on our device. There's already a thread about this somewhere that explains it in more detail.
bramgus12 said:
Thats not what i want to do, i want it to be unlocked and that message gone
Click to expand...
Click to collapse
I understand that's what you want. So be a man, live with it or re-lock the bootloader. It's not like you would have to stare at that notice for hours.
yourSKD said:
well, you can change it by flashing splash image... see in Moto G5s plus thread there is a solution....
Click to expand...
Click to collapse
Yes because on the Moto this very message is a graphic in a separate partition. On the OP it's baked into the bootloader. Since this is the thing that's also signed with private keys etc., it's (as of today and someone else finds a way) impossible to change.
dreinulldrei said:
Yes because on the Moto this very message is a graphic in a separate partition. On the OP it's baked into the bootloader. Since this is the thing that's also signed with private keys etc., it's (as of today and someone else finds a way) impossible to change.
Click to expand...
Click to collapse
The Nexus 5X link I posted, they are modifying the bootloader.
So you have such tool for the OP5? Not seen before.
OhioYJ said:
The Nexus 5X link I posted, they are modifying the bootloader.
Click to expand...
Click to collapse
No they're not, not really. They're modifying dumps of the imgdata partition, which is flashed as part of the factory bootloader.img but it's not an actively run bootloader partition (like aboot, xbl, sbl, etc are), and so not verified the same on-device and can be changed without bricking the device.
See here: https://forum.xda-developers.com/on...ader-warning-boot-t3749808/page2#post76002163
You can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (cheaper but FunkyHuawei is more certain)
As most of you already know, Huawei stopped giving away bootloader unlock codes. So it is up to us, to hack our way to root and custom ROMs.
Following, are a few things we could try,
Also, I own a Nova 3i currently. There are always the possibility that something working for me won't work for you, because of different chipsets, but I guess that this forum is also for the development of Nova 3i.
NOTE THAT SOME OF THE FOLLOWING ARE PAID SERVICES. I'M NOT RELATED WITH ANY OF THEM.
+DC-Unlocker:
I tried the latest version, got an unknown error 375. (This error also goes for the latest versions of P20 Pro, Mate 10, etc.). And the developers said that they won't support any new Huawei phones, and that they'll leave new Huawei phones for HCU-Client, because the two services are related.
+HCU-Client:
You can't try this without buying credits. If you feel generous, go on and try this. They released a couple of new versions in this week.
+Bootloader exploiting:
I really don't know anything about this, feel free to contribute.
+Secret Fastboot backdoors:
There can be a LOT of these, considering that there are a family of commands under <fastboot oem backdoor>. And I discovered quite a lot of secret commands, almost every one of them sounding like that they could seriously brick the device. For example, consider what <fastboot oem djtagtosd> sounds like. (Search Google for JTAG) If you would like to test some of the less-dangerous looking ones, please PM me, even an old Huawei device is okay as long as it has a Kirin chipsets.
Please check this link from P20 Pro Forum - we may have a chance to be supported if many of us do the request. I have done mine. - https://forum.xda-developers.com/hu...ol-tool-one-driversunlocktwrpfactory-t3779080
waltermsalomon said:
Please check this link from P20 Pro Forum - we may have a chance to be supported if many of us do the request. I have done mine. - https://forum.xda-developers.com/hu...ol-tool-one-driversunlocktwrpfactory-t3779080
Click to expand...
Click to collapse
Sorry, did not see this. So, this tool installs TWRP without unlock codes? Still we need to get TWRP compiled.
Huawei nova 3i rom
Dears I need stock firmware and flash tool officially for Huawei Nova 3i ine-lx1
cant EU do anything about this bootloader unlocking situation? I mean, isn't it our right to do whatever we want with our bought device? Im actually not from any EU country btw.
jioleight said:
cant EU do anything about this bootloader unlocking situation? I mean, isn't it our right to do whatever we want with our bought device? Im actually not from any EU country btw.
Click to expand...
Click to collapse
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Supersonic27543 said:
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Click to expand...
Click to collapse
mandated but no one is enforcing it so huawei will just delay the relase of the kernel source until the insterest has died out.
nope, not gonna take that risk :laugh:. $55 seems cheaper until it's converted to my country's currency. haha.
Supersonic27543 said:
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Click to expand...
Click to collapse
Another one source to unlock bootloader - $22
This method has already been tested on 4pda. Working TWRP can be taken from here
And HCU doesn't have NOVA 3 support yet to read the unlock code now
OEM Unlock option
Is it enought to enable "OEM Unlock" in "Developer Options" from the phone settings to unlock the bootloader and I can simply install TWRP afterthat? (the option "OEM Unlock" is not greyed out, and can be easily enabled, at least in the devices that are sold in my country).
Or do I still have to unlock it using unlock key from Huawei Website (or other sources)?
Jan oatcoal said:
Do I still have to unlock it using unlock key from Huawei Website (or other sources)?
Click to expand...
Click to collapse
Yep. It is like this when you issue the command in fastboot to unlock:
Without code and without enabling the toggle: Gives and error telling to turn on the toggle.
With code and without enabling the toggle: Same as above
Without code and toggle enabled: Error wrong password
With both: Success
I think we are lucky on that side, I think that the toggle is also disabled on Mate 20 series. So we can unlock the bootloader. with external sources for now, so it may be a good idea to block OTA updates.
Ine-lx2 8.2.0.131(c636)
*update*
so i checked using fastboot oem get-bootinfo. lo and behold it's really unlocked.
jioleight said:
does Phone Unlocked mean the bootloader or just the GSM part that is unlocked?
Click to expand...
Click to collapse
I did this then installed titanium backup and it said it wasn't rooted.
meekspace said:
I did this then installed titanium backup and it said it wasn't rooted.
Click to expand...
Click to collapse
you have to root first by installing magisk or supersu. and it needs twrp to root. in case of nova 3i there isnt any existing twrp. only on nova 3 since it has the same soc as p20pro.
was about to test it on my nova 3i. good thing i checked the specs of nova 3 first before proceeding.
Unfortunately, cant flash patched ramdisk since fastboot fail. Remote command not allowed. So close yet so far away.
jioleight said:
Unfortunately, cant flash patched ramdisk since fastboot fail. Remote command not allowed. So close yet so far away.
Click to expand...
Click to collapse
Let's try flashing the stock boot.img. If that works, I will patch the boot image to manually disable dm-verity and add Magisk.
Supersonic27543 said:
Let's try flashing the stock boot.img. If that works, I will patch the boot image to manually disable dm-verity and add Magisk.
Click to expand...
Click to collapse
"fastboot flash ramdisk patched_boot.img". That's what entered in cmd. Also after magisk patched the ramdisk the patched ramdisk is only 5mb. The original was around 25mb.
What should be patched anyway? I patched ramdisk.img via magisk ang since the partitioning is different with phones released with oreo. What is your method?
*update*
well, this sux. based on what i have read on other huawei device flashing via fastboot is not always the best way. the phone may display that the bootloader is unlock but it wont still allow any modifications. why cant this be straight forward like samsung/oneplus. this is frustrating.
jioleight said:
"fastboot flash ramdisk patched_boot.img". That's what entered in cmd. Also after magisk patched the ramdisk the patched ramdisk is only 5mb. The original was around 25mb.
What should be patched anyway? I patched ramdisk.img via magisk ang since the partitioning is different with phones released with oreo. What is your method?
*update*
well, this sux. based on what i have read on other huawei device flashing via fastboot is not always the best way. the phone may display that the bootloader is unlock but it wont still allow any modifications. why cant this be straight forward like samsung/oneplus. this is frustrating.
Click to expand...
Click to collapse
What if we try obtaining a code by one of the third party methods and try that? Maybe they just forgot or didn't care to set the variables you saw there as this is a new chipset. I think it is not really unlocked, if it was the phone will display the "Your device has been unlocked and cannot be trusted" message on boot.
Looks like what I said before is true. fastboot oem lock-state info returns USER Locked.
Has anyone tried this?
https://www.techdroidtips.com/unloc...i/#How_to_Unlock_Bootloader_on_Huawei_Nova_3i
stevefwt said:
Has anyone tried this?
https://www.techdroidtips.com/unloc...i/#How_to_Unlock_Bootloader_on_Huawei_Nova_3i
Click to expand...
Click to collapse
They are just copy pastes and no longer works as of Huawei stopping providing codes.
Google should try to remove them from coming at top of Google searches, IDK.
Moto G7 Play bootloader unlock issues - "bad key", not OTA, no way to roll back?
My plan was to unlock the bootloader before configuring the new phone - just in case I might need it later, then use the phone as out-of-box. I unlocked the bootloader for the new Moto G7 Play, following the official procedure via the Motorola Accounts page, resulting in:
- Fastboot page shows: "flashing unlocked"
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
- I could not try TWRP, as there is no TWRP for the G7 Play yet (so not sure if flashing would work)
My concerns now are that I will not be able to update the phone, and that the "bad key" issue might cause other problems.
So my plan would be to roll back and lock the phone again, to use it as out-of-box (not worrying about warranty loss that might already have happened - I did accept these terms). However, that does not work, too:
- Locking bootloader requires factory images, which are not available for the G7 Play
- Locking bootloader with fastboot OEM lock will not work without complete images
Any suggestions how bring the phone back to normal? I am disappointed by Motorola, as they officially offer the unlock procedure - which then does not produce the expected outcome, breaks updating, and provides no way to go back? Mind you, I did not apply any "hacks", nothing but the official Motorola unlocking steps.
Thanks for advice
I have the same problem and i cannot fix it.
I tried to get advice from Motorola support - but replies are very generic, referring to the bootloader unlock page (we obviously found that) or to the Motorola Forum (where the answer isn't). Will now just live with the unlocked phone and hope for the opportunity to OTA / update in a while
CoffeeMachineSwitch said:
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
Click to expand...
Click to collapse
Unlocking any Motorola bootloader will cause the bootscreen to display "Bad Key". This is normal. It is a warning that the bootloader has been unlocked and the phone may not be "safe". Once you root a Motorola phone, it will display "N/A" instead of "Bad Key". Again, this is normal behavior. There are image makers that can replace the "splash" image and "hide" the "N/A", but since this phone doesn't have TWRP yet, you'll have to live with it for now.
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
mn1968 said:
Unlocking any
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
Click to expand...
Click to collapse
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
CoffeeMachineSwitch said:
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
Click to expand...
Click to collapse
That would be an unfortunate change if true. Prior devices could be unlocked and still get OTA updates. They won't install if certain changes are made but still get notified of updates.
You still can install full ROM using fastboot commands and regain root by patching boot.img from updated ROM
I did it on both G6 and G7
Where did you get the ROM images from. I understand there are no officials?
CoffeeMachineSwitch said:
Where did you get the ROM images from. I understand there are no officials?
Click to expand...
Click to collapse
Have you tried the LMSA tool? It's a tool you download from Motorola. There is a discussion here about it. It has a rescue button with which, I understand that you can download stock images directly from Motorola, but I haven't used it myself.
umbrisle said:
Have you tried the LMSA tool? ....
Click to expand...
Click to collapse
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
CoffeeMachineSwitch said:
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
Click to expand...
Click to collapse
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Should've read the thread here before i go buy g7 play, not my phone get softbricked.
Unblocked bootloader successfully following the official doc but failed to install magisk by copying the wrong build number of boot.img of OTA from here mirrors.lolinet.com/firmware/moto
now my g7 says
Code:
failed to load kernel, no Bootable A/B slot,
Failed to book Linux
falling back to fastboot.
I downloaded `RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC` which i think this is the right build number when i see error like
Code:
river/retail corrupted
(can't remember exactly, but it's RETAIL not RETUS)
and make my own version of fastboot command stemming from servicefile.xml, still with unlucky.
there is no recovery.img and google has limited resource to make g7 play back to stock orm, i'd like to see if community has any idea or i have to give it to moto to fix it.
========================update=================================
update: i finally get the correct stock ORM which is exactly matching my build number "XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" i was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict, "second time rooting in my life".
not i has flash all of the original orm into my phone then fastboot reboot works, it give me the original error like
Android Recovery
motorola/channel_retail/channel9/PPY29.105-36/d7abeuser/release-keys
Use volum up/down and power
can't load Android system. Your data may be corrupt.
If you continue to get this message, you may need to perform a factory data
reset and erase all user data stored on this device
=====
Try again
Factory data reset
Click to expand...
Click to collapse
now i need to figure out what to do next
===============update=========
lol, turns out just press Factory data reset will bring the brick back to life!!!!!
just want to post my process for anyone having my issue.
the key point to find the correct build number
umbrisle said:
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Click to expand...
Click to collapse
.
The G6 Play is really slow, at least the Boost one. I was kind of sorry I bought one to put on Sprint's free unlimited plan. At least Sprint unlocked it for me after 60 days.
Give the G7Play some time, it just came out.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
gedster314 said:
.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
Click to expand...
Click to collapse
Yeah, but there is inconsistency in Motorolas communication, they actively offer the option to unlock the bootloader (with T&C and all) incl. a link to a rollback feature. Which then does not work. So in a scenario where a developer buys the device because it actively offers this features, they dont get what they paid for. Mind you, we are not discussing hacking a device here or jailbraking - we are discussing features that Motorola actively promotes with a dedicated webpage.
wallace_mu said:
was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict
Click to expand...
Click to collapse
You completely missed the wrong code name "river" in RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC it is for another device, while "channel" is the right one
Where did you get the correct Rom from? Thanks
I don't own Moto G7 Play and can not confirm, however this one worked for wallace_mu
wallace_mu said:
XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
realsine said:
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
Click to expand...
Click to collapse
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
CoffeeMachineSwitch said:
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
Click to expand...
Click to collapse
Hello,
I'm glad to read that I could help.
I have "my" image of 'https :// mirrors.lolinet.com/firmware/moto/channel/official/RETEU/'. There are also some others - just have a look. And please remove the spaces around '://'. I'm currently not allowed to post (external) links, so this way.
* Every 'LOCK' deletes all data and the system is "clean" again.
* The same applies (unfortunately) to EVERY 'UNLOCK'.
I don't care at the moment because I haven't set up my smartphone yet. But it's not nice.
Best regards
Does anyone know if there’s any way to eliminate the Google warning message that pops up every time you boot up a Pixel phone once you have unlocked the phone’s bootloader? I just saw instructions for doing this on a Samsung phone and I’m just wondering if it’s also possible on my Pixel 2 XL.
just disable dm-verity
Using the Universal DM-Verity, ForceEncrypt, Disk Quota Disabler, which I found in an XDA forum, I disabled DM-Verity, but the Google boot up warning message is still displayed whenever the phone boots up. Either the script didn’t work or the warning message is not DM-Verity dependent.
Any additional help would be appreciated.
neilth said:
Using the Universal DM-Verity, ForceEncrypt, Disk Quota Disabler, which I found in an XDA forum, I disabled DM-Verity, but the Google boot up warning message is still displayed whenever the phone boots up. Either the script didn’t work or the warning message is not DM-Verity dependent.
Any additional help would be appreciated.
Click to expand...
Click to collapse
hex edit it
The warning message is independent of dm-verity and is triggered upon unlocking the bootloader. While hacking the bootloader to have the message not be displayed may be possible, that course of action could cause an unrecoverable brick. The easiest way to not have the message show is to lock the bootloader.
Thanks for the bad news.
neilth said:
Thanks for the bad news.
Click to expand...
Click to collapse
When the message comes up, tap your power button twice.
The first press pauses booting up, the second is to continue to booting up. I do this whenever I turn on or reboot my phone, and the message is gone in less than a second.
Thanks, I guess that’s about the best solution available.
neilth said:
Thanks, I guess that’s about the best solution available.
Click to expand...
Click to collapse
It's a minor inconvenience. When I say less than a second, I mean like a quarter second or so. Part of the sh*t you get with an unlocked bootloader. The phone is obviously in your hands already if you're seeing the warning message. Just double tap the power button and it'll boot up.
Back story here, I used to use HTC devices. When you went S-Off on them, you'd get a red warning that the build was for in house HTC development purposes only, and that sharing it could lead to legal consequences (lol). That warning stayed up for at least 15 seconds. Maybe 20. And there was no way to dismiss it.
I have a 2013 Google Nexus 7 with an unlocked bootloader and the only "warning" is the appearance of an open padlock at the bottom of the boot screen. Following this the Google legal department must have decided that the current warning message was needed to protect Google from potential lawsuits over possible security issues possibly caused by having an unlocked bootloader on any of their devices.
neilth said:
I have a 2013 Google Nexus 7 with an unlocked bootloader and the only "warning" is the appearance of an open padlock at the bottom of the boot screen. Following this the Google legal department must have decided that the current warning message was needed to protect Google from potential lawsuits over possible security issues possibly caused by having an unlocked bootloader on any of their devices.
Click to expand...
Click to collapse
I have the same tablet lol.
Yeah, the warning is probably for people who don't realize that there are vulnerabilities with having an unlocked bootloader. Most of us older Android enthusiasts already know this.
I don't know about lawsuits, but it's more along their line of being "secure". Not so long ago, Android was less secure than iOS. They have changed that with the Pixel line and the monthly updates.The warning is probably tied to that. idk
Strephon Alkhalikoi said:
The easiest way to not have the message show is to lock the bootloader.
Click to expand...
Click to collapse
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
TheRealEdwin said:
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
Click to expand...
Click to collapse
Not a stupid question. Yes you can. I don't think you'll be able to update it however, though I haven't tried.
TheRealEdwin said:
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
Click to expand...
Click to collapse
Use a safetynet fix. Passing safetynet is usually all that's required. On LineageOS 20 rooted on a Pixel 5a and have all wallet, tap to pay, and problematic apps like Dasher working perfectly fine. Just have to re-flash my modified boot image after any OTA update
TheRealEdwin said:
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
Click to expand...
Click to collapse
https://github.com/Displax/safetynet-fix/releases/tag/v2.4.0-MOD_1.2 is the Git for the modded version (by the same people) of the safetynet fix plugin. (the original version of the plugin didn't work for me personally HERE is the original) install this, let it reboot, then in magisk you want to go to settings > enable Enforce DenyList > Configure DenyList(under it) and select and apps that don't work.
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Is it what happen to your device ? Hopefully you could recover ?
Steve0007 said:
Is it what happen to your device ? Hopefully you could recover ?
Click to expand...
Click to collapse
No, someone else's, we're trying to see if there's anything we can do via edl currently
craznazn said:
No, someone else's, we're trying to see if there's anything we can do via edl currently
Click to expand...
Click to collapse
Hope it's not a one way street...
craznazn said:
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Click to expand...
Click to collapse
I came across the corrupt message twice during my rooting mission hold down pwr+vol up+vol down until it shut off, then held down all three buttons til it turns on and it went into bootloader mode. It did take several tries but it got there. Then I could oem lock/unlock and reboot to a fresh system. Now I didn't mess with my partitions so maybe that is something deeper but it's worth a try.
hllywd said:
I came across the corrupt message twice during my rooting mission hold down pwr+vol up+vol down until it shut off, then held down all three buttons til it turns on and it went into bootloader mode. It did take several tries but it got there. Then I could oem lock/unlock and reboot to a fresh system. Now I didn't mess with my partitions so maybe that is something deeper but it's worth a try.
Click to expand...
Click to collapse
Yeah, we can get to the bootloader and EDL mode. However, we can't fastboot oem lock/unlock because OEM lock/unlock option is not togged in the System -> Dev options -> OEM Unlocking. This is a T-Mobile device, so not only that, we need to flash cust-unlock first which is not possible with OEM unlocking disabled in dev options.
avid_droid said:
Looks like I won't be doing the Tmo to EU. Looks like root will suffice until MSM for 2127 is released. I'm just wanting my camera updated to the latest and couldn't get it on unrooted. Waiting for my token, will use your magusk patch and update my camera. Thanks for the warning
Click to expand...
Click to collapse
The MSM for the 2127 is actually available now via remote support, just nobody has posted it online yet. That's where this warning comes from. Another user was able to run the 2127 MSM on his phone, and now it's bricked
I thought there was a command for the oem tick switch?
This is essentially what happened to my device! I ended up just returning it as I was in The 15day return window. Waiting on a refund now
ssjucrono said:
This is essentially what happened to my device! I ended up just returning it as I was in The 15day return window. Waiting on a refund now
Click to expand...
Click to collapse
When did this happen? What device did you have?
craznazn said:
When did this happen? What device did you have?
Click to expand...
Click to collapse
Oneplus 9 pro green 256gb. Happened last Wednesday
craznazn said:
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Click to expand...
Click to collapse
Might be a good idea to update the thread title as it's misleading. Makes it look like the normal MSM tool is going F someone's normal variant device. Most people don't have the crappy T-Mobile variant. I understand saving a quick Buck is important though.
avid_droid said:
Looks like I won't be doing the Tmo to EU. Looks like root will suffice until MSM for 2127 is released. I'm just wanting my camera updated to the latest and couldn't get it on unrooted. Waiting for my token, will use your magusk patch and update my camera. Thanks for the warning
Click to expand...
Click to collapse
Is this the Camera app from APKmirror? The one that you'd have to move to... privapp, I think? Because they failed to sign it correctly?
avid_droid said:
Don't understand when people say "save a quick buck on Tmo," when it's exactly the same $1069 right across. It's about getting it in hand instead of waiting for shipping. And the thread is not misleading as it is for the 2127 which is the Tmo variant but it doesn't say that haha
Click to expand...
Click to collapse
Clearly is misleading because he doesn't put T-Mobile in the thread title.
I'd gladly wait up to 2 weeks to get a device that has timely updates and easily has up-to-date development..
avid_droid said:
Yes. Root is needed.
Click to expand...
Click to collapse
How is it so far? Is it worth trying out?
Burt Squirtz said:
Clearly is misleading because he doesn't put T-Mobile in the thread title.
I'd gladly wait up to 2 weeks to get a device that has timely updates and easily has up-to-date development..
Click to expand...
Click to collapse
It's not misleading, because ANY device where you modify a partition that is not usually touched my the MSM tool can result in a hard brick if it's checked by avb
avid_droid said:
@craznazn , it's only if you edit partitions correct? My unlock token should be here in a few days and plan on only rooting for a couple apps. This won't affect my re-locking would it?
Click to expand...
Click to collapse
Rooting only touches the boot partition and that's fine. Even flashing AA/BA/DA is fine because all of those partitions will just get overwritten by the MSM. Things only start to get dicey when you start messing with param, persist, and the likes.
craznazn said:
Rooting only touches the boot partition and that's fine. Even flashing AA/BA/DA is fine because all of those partitions will just get overwritten by the MSM. Things only start to get dicey when you start messing with param, persist, and the likes.
Click to expand...
Click to collapse
Just theoretical question: would flashing the device to something else like LineageOS (if there was working version) help? Or is the partitions check on HW/FW level?
drozd128 said:
Just theoretical question: would flashing the device to something else like LineageOS (if there was working version) help? Or is the partitions check on HW/FW level?
Click to expand...
Click to collapse
Once the bl is locked due to msm, you can't flash anything again.
craznazn said:
Once the bl is locked due to msm, you can't flash anything again.
Click to expand...
Click to collapse
I see. Thank you.