Huawei is very covered by releasing any sources for kernel or whatever. But now they made a mistake in latest Firmware EVA-L09C432B386 and forgot some scripts to flash firmwares via fastboot.
I just share some codes of them, but not the whole file cause all can damage the device, until someone find out how this works.
get_root.bat
Code:
adb reboot bootloaderfastboot flash boot sec_boot.img
fastboot flash recovery sec_recovery.img reboot
pause
updateinadb_hi3650.bat
Code:
cls
setlocal enabledelayedexpansion
:start
@echo -----------------------------
@echo %date%-%time% > fastboot_log.txt
@echo %date%-%time%
@echo "Austin Fastboot Updating......" >> fastboot_log.txt
@echo "Austin Fastboot Updating......"
adb reboot bootloader
fastboot flash xloader sec_xloader.img
fastboot flash ptable ptable.img
@if not 0==!ERRORLEVEL! goto error
fastboot flash fastboot sec_fastboot.img
@if not 0==!ERRORLEVEL! goto error
fastboot reboot-bootloader
Code:
@fastboot getvar vendorcountry 2>vendorcountry.txt >> fastboot_log.txt
@fastboot getvar devicemodel 2>devicemodel.txt >> fastboot_log.txt
@for /f "tokens=2 delims= " %%i in ('findstr vendorcountry vendorcountry.txt') do set cur_country=%%i
@for /f "tokens=2 delims= " %%i in ('findstr devicemodel devicemodel.txt') do set cur_model=%%i
@del vendorcountry.txt
@del devicemodel.txt
@if exist vendor_transfer.xml (
@for /f "tokens=1,2 delims= " %%i in (vendor_transfer.xml) do (
@if %cur_country%==%%i (
@set country=%%j
@goto next
)
)
)
@set country=%cur_country%
@set vendorcountry_new=%country:/=_%
@set model=%cur_model%
Code:
C:\Windows\System32\PING.EXE -n 1 127.0.0.1>nul
) else (
if exist %userdata_path%\userdata.img (
echo %userdata_path%\userdata.img 存在 >> fastboot_log.txt
echo fastboot flash userdata %userdata_path%\userdata.img
echo 烧录运营商定制的userdata镜像
fastboot flash userdata %userdata_path%\userdata.img
if not 0==!ERRORLEVEL! goto error
Please not use, or the device gets bricked.
Code not complete, for security reason
It would be great if there was a method to unlock the bootloader without contacting the OEM.
I'm stuck on EMUI4 and Huawei could care less about rolling out updates in my region...
MHBGT said:
It would be great if there was a method to unlock the bootloader without contacting the OEM.
I'm stuck on EMUI4 and Huawei could care less about rolling out updates in my region...
Click to expand...
Click to collapse
DC unlocker.
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
askor said:
DC unlocker.
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
Paying for some random app to unlock device that you legally bought, and by any laws you own is not a solution.
Its like having a car, and you would need to go to some shady service center just to open hood. because that what it is, access to engine of car.
And no matter what price it is, it can be even 1cent, paying or even suggesting that its a solution is not good for anyone beside some dude who managed to make business on people problems, and now get a cash everytime when someone want to unlock his own phone.
askor said:
DC unlocker.
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
Akinaro said:
Paying for some random app to unlock device that you legally bought, and by any laws you own is not a solution.
Its like having a car, and you would need to go to some shady service center just to open hood. because that what it is, access to engine of car.
And no matter what price it is, it can be even 1cent, paying or even suggesting that its a solution is not good for anyone beside some dude who managed to make business on people problems, and now get a cash everytime when someone want to unlock his own phone.
Click to expand...
Click to collapse
Thank you for answering better than I would have been able to.
There is NOTHING special about these batch files.
I took a look at the whole file and really there is nothing special about this.
Is just flashes every partition via fastboot and if the flash was sucessfull the script will throw back a 1 and continue with the next partition. If the flash is not sucessfull it will throw back a 0 and it will show you the update failed screen.
Nothing special
xtcislove said:
There is NOTHING special about these batch files.
I took a look at the whole file and really there is nothing special about this.
Is just flashes every partition via fastboot and if the flash was sucessfull the script will throw back a 1 and continue with the next partition. If the flash is not sucessfull it will throw back a 0 and it will show you the update failed screen.
Nothing special
Click to expand...
Click to collapse
That's a pity, was hoping someone with more knowledge would be able to verify the OP.
But Alas, I guess it is not to be...
yep thats a pity. U should change the thread name or let it get deleted.
For these commands to work u need an unlocked bootloader either so people here could brick theire phone with the commands you posted.
Maybe not special, but what would you do, if dload gets fully blocked?
xtcislove said:
yep thats a pity. U should change the thread name or let it get deleted.
For these commands to work u need an unlocked bootloader either so people here could brick theire phone with the commands you posted.
Click to expand...
Click to collapse
Why delete this thread he clearly said do not try this it will brick your device so whats the problem here?
safariking said:
Why delete this thread he clearly said do not try this it will brick your device so whats the problem here?
Click to expand...
Click to collapse
this thread is nothing helpful. just confusing. i think thats enough.
is was excited because of "Huawei leaked fastboot flash codes". and many people will waste theire time on this too.
xtcislove said:
this thread is nothing helpful. just confusing. i think thats enough.
is was excited because of "Huawei leaked fastboot flash codes". and many people will waste theire time on this too.
Click to expand...
Click to collapse
So? ? if you dont like it dont read it and waste your time on something else
So you are fine with misleading information?
MHBGT said:
So you are fine with misleading information?
Click to expand...
Click to collapse
Oh god please...
xtcislove said:
There is NOTHING special about these batch files.
I took a look at the whole file and really there is nothing special about this.
Is just flashes every partition via fastboot and if the flash was sucessfull the script will throw back a 1 and continue with the next partition. If the flash is not sucessfull it will throw back a 0 and it will show you the update failed screen.
Nothing special
Click to expand...
Click to collapse
I think you don't get the point.
The files mentioned in the OP are special in that they're signed by Huawei, and therefore can be flashed, other than any flash files created by someone else which would fail signature check and therefore rejected.
Considering the naming, it is very likely that they would indeed unlock the (secondary) boot loader.
They have some background, because they stored it in every firmware now on Hisi95x.
Related
My carrier (C Spire) has found a problem with the device on their network that makes the device lose it's signal all the time. They claim it is a device problem anyway. I have unlocked the bootloader on the phone, but have not flashed any roms or made any other changes to the phone. Just the unlocked bootloader. They have said that since they know it is a problem with the device, they will let owners come in and exchange the phone for a Galaxy SIII free and clear. The only stipulation is it has to be in like new condition. My phone is perfect except for the unlocked bootloader. They'd probably never notice if it wasn't for that notification screen when the phone reboots that would tell them. I need to relock the bootloader to make that screen go away.
So, my question is, how do I do that? I've tried doing 'fastboot oem lock' but that doesn't work.
This is what I get when I try:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.014s]
finished. total time: 0.016s
If I run the command as it suggests I get:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.246s]
finished. total time: 0.248s
I'm not sure what to do to get it to lock again.
Can anyone please help?
The problem is, you've unlocked it 'officially' from Moto... so it's registered in the database as unlocked.
You can try to change the boot logo, I haven't tried yet... Supposedly you can to get rid of that annoying screen.
Maybe you will just have to take it in and hope they don't reboot it. Kinda sucks that we have official unlocks now, because they can now easily track who has unlocked their phones and who hasn't :/
According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.
adear11 said:
According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.
Click to expand...
Click to collapse
Did you try using the same key to unlock to relock?
I've never bothered relocking...
arrrghhh said:
Did you try using the same key to unlock to relock?
I've never bothered relocking...
Click to expand...
Click to collapse
Is the key required to relock? I had not tried using it.
adear11 said:
Is the key required to relock? I had not tried using it.
Click to expand...
Click to collapse
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.
arrrghhh said:
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.
Click to expand...
Click to collapse
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"
adear11 said:
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"
Click to expand...
Click to collapse
You entered fastboot oem lock begin <key>?
arrrghhh said:
You entered fastboot oem lock begin <key>?
Click to expand...
Click to collapse
When I do 'fastboot oem lock begin [key]' I get "(bootloader) Ready to flash signed images".
From here, if I do 'fastboot oem lock' again, I get "Re-Lock Failure. See display." On the phone's display, I get:
Code:
No valid PIV block in SP for system
piv validation failed (system)
Re-lock failure
Hrm. I was poking around Moto's FAQ's and community site, and they talk about relocking - but not in detail unfortunately. They cryptically state that they will not release any stock recoveries at this time - so perhaps if you don't have the stock recovery, you can't relock...?
I would post up on Moto's forums or call their support... Not sure how much help they will be, but their website leaves much to be desired about the relocking process...
oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.
shabbypenguin said:
oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.
Click to expand...
Click to collapse
so, if one were interested in using this anonymous persons script, how would one proceed?
adear11 said:
so, if one were interested in using this anonymous persons script, how would one proceed?
Click to expand...
Click to collapse
i would imagine gathering all the files and putting them in the proper spots/folders would assemble a replica of this script. i was just mentioning you should look thru to see if there is anything taht helps you tho
In short, in order to relock the bootloader, you have to flash signed software in the process.
Ugh why did I try this lol.. Still having problems. I restarted my computer and that fixed the problem "waiting for device" now in cmd it will at least recognize the phone BUT, I get this trying to figure out some information
getvar:cid FAILED (command write failed (unknown error))
Hi
I have problem motorola not allow to unlock my bootloader with this massege:
Your device does not qualify for bootloader unlocking.
This Photon Q is from Sprint .
Any one help?
m.
Copy and paste the code. It has to match EXACTLY.
Hi arrrghhh
This is a code :
9900020008000000#5441363935303254593400000000000000000000#5C2D5B1C871C66F72E5BF72404DE926E44948A76#C75BD600020011000000000000000000
micron said:
Hi arrrghhh
This is a code :
Click to expand...
Click to collapse
Ehm... I meant copy and paste it into the fastboot command to avoid typo's.
Again, if you even get 1 character wrong, the unlock will fail.
Do not post the code publicly, first part of it is your IMEI.
Oki fix remove any symbol.
Any idea what is the problem ?
I copy and paste the code many time but not success.
m.
micron said:
Oki fix remove any symbol.
Any idea what is the problem ?
I copy and paste the code many time but not success.
m.
Click to expand...
Click to collapse
I didn't quote the code for a reason. Skrilax_CZ recommended you remove it, and I would concur.
Edit your post and remove the code. I never wanted you to paste it in here, sorry I did not make that clear.
At any rate, all I can say is make VERY sure that the code you are provided is the SAME code you are using for the fastboot command.
I didn't even think about asking - but I assume you're not using it as a CDMA device. Did you buy one with a bad ESN? If so, I wonder if they prevent bad ESN devices from being officially unlocked...
Good luck.
Oki
I find a solution after update to last new version
Download this : http://forum.xda-developers.com/showthread.php?t=2143437
After download and share fail with samba windows or mac sharing, you need to mount from file manage > remote storage
After fix permission go to adb folder and type : "adb shell", "cd /mnt/rfs0", "./su" , "cd /", "ln -s /mnt /storage"
Next step go to console and type :
adb kill-server
adb shell /storage/rfs0/pwn
Next : Install apk package from phone , Reboot Phone and now your phone is rooted!
Update from Play Market SuperSu and go.
Best regards,
m.
Rooting and unlocking bootloader is not the same thing.
Skrilax_CZ
Yes not the same but in this moment motorola support dumb to give unlock.
and this is solution for my.
would pester them until they do.
m.
micron said:
Oki fix remove any symbol.
Any idea what is the problem ?
I copy and paste the code many time but not success.
m.
Click to expand...
Click to collapse
Try to enter the code manually.
In may case when I copy and paste the code I also got the message "Your device does not qualify for bootloader unlocking."
However when I entered the code manually I got unlock code.
micron said:
Hi
I have problem motorola not allow to unlock my bootloader with this massege:
Your device does not qualify for bootloader unlocking.
This Photon Q is from Sprint .
Any one help?
m.
Click to expand...
Click to collapse
had the same problem over the weekend. fixed now tho
Hinyo said:
had the same problem over the weekend. fixed now tho
Click to expand...
Click to collapse
First of all the site won't even load most of the time on Chromium, IE opens it fine. Typing code manually doesn't help, any ideas?
saint_tm said:
First of all the site won't even load most of the time on Chromium, IE opens it fine. Typing code manually doesn't help, any ideas?
Click to expand...
Click to collapse
You're sure it hasn't already been unlocked?
Did you try copy and paste?
What error do you get?
arrrghhh said:
You're sure it hasn't already been unlocked?
Did you try copy and paste?
What error do you get?
Click to expand...
Click to collapse
The SDK reboot to fastboot says it is locked (on phone screen).
Yes copy and paset was my first try (few times, 4 lines, not 5)
Error in IE is "Your device does not qualify for bootloader unlocking."
saint_tm said:
The SDK reboot to fastboot says it is locked (on phone screen).
Yes copy and paset was my first try (few times, 4 lines, not 5)
Error in IE is "Your device does not qualify for bootloader unlocking."
Click to expand...
Click to collapse
Where was your Q purchased? Second hand I presume?
I wonder if bad ESN devices do not qualify. Or if it has been unlocked, and relocked... perhaps it cannot be unlocked again.
Good luck.
Tried it once more a minute ago and it worked, looks like motorola servers weren't in the mood earlier
Thanks for your help
So,
Its not my problem but one of my friend is facing it and I am unable to resolve it no matter what.
He have moto g 2015 Indian variant briefly XT1550
I tried unlocking its bootloader but every time I give command, " fastboot OEM get_unlock_data "
It gives a weird error. Saying
Code:
...
(bootloader) Failed to get unlock data, Please try again!
Failed (Remote Failure)
Finished. Total time: 0.243s
I tried searching for a fix all over internet some moto x play users were facing it but no solution.
I tried almost everything. I tried minimal adb and fastboot even mfastboot.
Drivers are installed and command, "fastboot devices" reports positively.
I will be attatching a screenshot of fastboot output. So please try to help him.
These community had never let me down.
Have you granted permission for OEM Unlocking in your phone in developer options..?
Jithin91 said:
Have you granted permission for OEM Unlocking in your phone in developer options..?
Click to expand...
Click to collapse
Yup. Followed everything correctly. And if OEM unlocking was deal then it clearly states that in cmd. And yes its enabled.
Sir, I am not sure but would contacting Motorola directly be of any help?
Can you post a photo of your bootloader screen and/or the output of 'fastboot getvar all'?
acejavelin said:
Can you post a photo of your bootloader screen and/or the output of 'fastboot getvar all'?
Click to expand...
Click to collapse
Here is it.
I haven't seen this kinda issue in any osprey till now.
BTW I have attached the getvar all output.
Arcade said:
Here is it.
I haven't seen this kinda issue in any osprey till now.
BTW I have attached the getvar all output.
Click to expand...
Click to collapse
Hmm... That all looks fine. You're bootloader doesn't show Status as ENGINEERING does it? Otherwise I got nothing, it's giving you a remote failure, which is a device issue. Lenovo official forums has a specific area to ask for assistance with unlocking.
There is no harm in turning usb debugging off, turning OEM unlocking off and turning developer options off.
Then do a factory reset
Then turn developer options on agin, usb debugging on again , OEM unlocking on again and try again via fast boot
It won't cost a penny but may help to resolve the issue
just check u select correct command of ur moto id then sent it again to motorola offical page
Geekyogi said:
just check u select correct command of ur moto id then sent it again to motorola offical page
Click to expand...
Click to collapse
Maybe you should read the thread again, OP can't get the code from the phone with get_unlock_data at all, not issues with the Moto site... The phone is getting the correct command, it even acknowledges its an unlock command, it just fails to get data with a "Remote failure" meaning a failure inside the device.
acejavelin said:
Maybe you should read the thread again, OP can't get the code from the phone with get_unlock_data at all, not issues with the Moto site... The phone is getting the correct command, it even acknowledges its an unlock command, it just fails to get data with a "Remote failure" meaning a failure inside the device.
Click to expand...
Click to collapse
Yup. If that was the case then it was a very little problem and myself could have resolved it. No need to post it here.
BTW can't get unlock code till now. Isn't there any other way?
I have checked the cid value and its unlockable.
You must have known that too.
Arcade said:
Yup. If that was the case then it was a very little problem and myself could have resolved it. No need to post it here.
BTW can't get unlock code till now. Isn't there any other way?
I have checked the cid value and its unlockable.
You must have known that too.
Click to expand...
Click to collapse
We have done all we can do... You should go to the official Lenovo Motorola Support forums, they have an area specifically for bootloader unlock issues.
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/bd-p/230
acejavelin said:
We have done all we can do... You should go to the official Lenovo Motorola Support forums, they have an area specifically for bootloader unlock issues.
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/bd-p/230
Click to expand...
Click to collapse
Okay. Thanks for your help.
Its kinda weird problem.
That only my poor friend encountered.
Make sure you have properly installed Motorola Drivers.
Maybe that must be causing the issue..!!
Did u find any solution or Lenovo care helped u in any way ? I recently got my g3 and facing same issue . Everything is installed properly drivers and all . Device is unlockable as well . Tried changeing pc as well . Flashed stock firmware and tried again bt no luck . If sm1 faced this , plz tell me the solution . Thanks .
gamerboy_010 said:
Did u find any solution or Lenovo care helped u in any way ? I recently got my g3 and facing same issue . Everything is installed properly drivers and all . Device is unlockable as well . Tried changeing pc as well . Flashed stock firmware and tried again bt no luck . If sm1 faced this , plz tell me the solution . Thanks .
Click to expand...
Click to collapse
What is your output from 'fastboot devices' and 'fastboot oem get_unlock_data'?
acejavelin said:
What is your output from 'fastboot devices' and 'fastboot oem get_unlock_data'?
Click to expand...
Click to collapse
fastboot devices shows my device id .
fast oem get_unlock_data shows same result as of OP .
gamerboy_010 said:
fastboot devices shows my device id .
fast oem get_unlock_data shows same result as of OP .
Click to expand...
Click to collapse
Please post bootloader status (verbage and number, like Locked & 0, Engineering & 1, etc) and output of 'fastboot getvar all' please...
acejavelin said:
Please post bootloader status (verbage and number, like Locked & 0, Engineering & 1, etc) and output of 'fastboot getvar all' please...
Click to expand...
Click to collapse
Attached below . PLz help me .
gamerboy_010 said:
Attached below . PLz help me .
Click to expand...
Click to collapse
Unfortunately, everything looks fine... Going to have to say look at the link to Lenovo official forums given a few posts back, nothing else we can do.
Now Motorola supported has updated to support G7. You should be able to unlock open market model.
Prerequisites:
1. ADB installed
2. Motorola drivers installed
3. Your phone has enabled OEM unlock (hit build number few times to enable developers options) and USB debugging
4. Backup your internal storage. ALL PERSONAL DATA ON INTERNAL STORAGE WILL BE WIPED DURING OEM UNLOCK PROCESS!
----------------
Process:
1. Enter bootloader. After your phone connected to host computer, use the following:
Code:
adb devices
After your phone has been shown up, use the following command to enter bootloader
Code:
adb reboot bootloader
2. Retrieve your phone unlock data and submit
Go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Retrieve your phone unlock data using the following and open notepad or any text editor
Code:
fastboot oem get_unlock_data
You should see 5 lines of data starting (bootloader). Right click and mark the data on the line 2-5, drag until all data highlighted and right click once.
Paste the 4 line data on your favorite text editor and locate the cursor to the end of the line and press delete once, and repeat until 4 lines of data become a single line, and press Ctrl+a (select all) followed by Ctrl+c (copy)
Paste the single line to the box under #6 and verify. Accept the terms and press the blue button
3. Unlock your bootloader
After the unlock code delivered, highlight and copy 20 characters code
Enter the following command and press space once and paste the code
Code:
fastboot oem unlock
It should be fastboot oem unlock XXXXX (20 characters code)
You have to enter same command again to finish the process.
Your phone bootloader now unlocked and it's ready to install root
is there a way to relock once unlocked?
shaDNfro said:
is there a way to relock once unlocked?
Click to expand...
Click to collapse
Yes. fastboot oem lock but doing so will wipe the device back to factory settings.
adb backup -all
will back up your phone to a cable connected laptop. Is there anything else one needs to back up before unlocking the bootloader wipes your data off the phone?
**Specifically, will it backup
1. Documents folder
2. Download folder
3. Other custom created folders like saved photographs, etc.
Thank you.
For anyone looking at this thread and wondering, yes, Amazon branded device's bootloaders can be unlocked.
Could someone with an unlocked bootloader test out how well the Android Q GSI works?
kaiomatico said:
Could someone with an unlocked bootloader test out how well the Android Q GSI works?
Click to expand...
Click to collapse
Until a custom recovery is created, we're stuck on stock
Omegapsy said:
Until a custom recovery is created, we're stuck on stock
Click to expand...
Click to collapse
Nope, the beauty of GSI's are that you can simply do an "fastboot flash system NameOfGSI.img" and the rom is flashed. No need for a custom recovery
Now that TWRP is finally available I'm picking up my courage to unlock and root my Moto G7. Thank you for all your instructions here and in the root thread.
Because I'm not an android expert and am scared I want to be sure I understand everything correctly.
1. ADB is installed and works. (I used adb to create an adb backup to my laptop).
2. Not sure what you mean by installing Motorola drivers. (I can see the Moto G7 when I connect it by cable to my W 10 laptop).
4. Backing up:
I used a cable connection to copy all the visible files to my laptop using Windows file explorer. I also have the adb backup mentioned above.
Final question:
What will need to be restored after unlocking the bootloader? Everything I backed up or only parts?
Thank you.
I would appreciate someone helping to answer @maybeme2 questions above in post #9. Specifically question 2 about drivers. I've downloaded the Lenovo MOTO Smart Assistant and can ADB connect to my device. However when I set the device to fastboot mode then the connection is dropped.
5 seconds delay on boot after unlocking bootloader
I unlocked my bootloader using the excellent instructions above. But now, everytime I reboot I get a screen that says
Your device has been unlocked and can't be trusted.....
ID (is blank)
your device will boot in 5 seconds.
bad key
Click to expand...
Click to collapse
How do I get rid of that?
Thanks.
maybeme2 said:
I unlocked my bootloader using the excellent instructions above. But now, everytime I reboot I get a screen that says
How do I get rid of that?
Thanks.
Click to expand...
Click to collapse
That's part of unlocking and that warning is there for a reason. That said you can either relock or find another logo.bin to flash that covers it up. Flashing another logo.bin does not make your phone secure again it's just cosmetic.
ptn107 said:
That's part of unlocking and that warning is there for a reason. That said you can either relock or find another logo.bin to flash that covers it up. Flashing another logo.bin does not make your phone secure again it's just cosmetic.
Click to expand...
Click to collapse
Thank you for replying.
My next step is to root the phone. Will that get rid of it?
If not, where do I get another compatible logo.bin?
Thank you again.
maybeme2 said:
Thank you for replying.
My next step is to root the phone. Will that get rid of it?
If not, where do I get another compatible logo.bin?
Thank you again.
Click to expand...
Click to collapse
It will not remove the warning. In fact rooting is even less secure fyi.
You'll have to search on xda for a modified logo.bin.
ptn107 said:
It will not remove the warning. In fact rooting is even less secure fyi.
You'll have to search on xda for a modified logo.bin.
Click to expand...
Click to collapse
Less secure than letting Google access all my data? ? I have firewalls and tools to protect me. I'm just new to Moto.
maybeme2 said:
Thank you for replying.
My next step is to root the phone. Will that get rid of it?
If not, where do I get another compatible logo.bin?
Thank you again.
Click to expand...
Click to collapse
I used the information from this thread.
https://forum.xda-developers.com/moto-g7/themes/mod-custom-boot-logos-t3923110
The logo.bin file has several images. I found that the image named "orange" was the one displayed when my device boots.
cou94114 said:
I used the information from this thread.
https://forum.xda-developers.com/moto-g7/themes/mod-custom-boot-logos-t3923110
The logo.bin file has several images. I found that the image named "orange" was the one displayed when my device boots.
Click to expand...
Click to collapse
Thank you.
Does removing "orange" also remove the 5 second delay?
maybeme2 said:
Thank you.
Does removing "orange" also remove the 5 second delay?
Click to expand...
Click to collapse
I never said that I removed the image named "orange". I did extract the "orange" image from logo.bin, edited the orange.png to black out the warning text, replaced the orange.png file in logo.bin and then flashed the modified logo.bin "fastboot flash logo modified-logo.bin".
I concur with ptn107's recommendation that you lock your bootloader and return your device to stock. That way you won't have to wait the five seconds which seems to be your concern.
cou94114 said:
I concur with ptn107's recommendation that you lock your bootloader and return your device to stock. That way you won't have to wait the five seconds which seems to be your concern.
Click to expand...
Click to collapse
Yes it is the imposed delay that I objects to. I've had other rooted phones and none had this warning and delay after unlocking the bootloader. So it is not part of android but something added by Moto.
It's not a big deal, but an unnecessary annoyance which is why I asked in a moto thread.
Help me, I got oem unlock but I can't enable it!
I can't find anything definitive about whether it's rootable or not
Same here i tried every root app possible and failed.
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
No need to flash TWRP: Booting into it is sufficient.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
How did you unlock the bootloader?
sCriptKittY1987 said:
How did you unlock the bootloader?
Click to expand...
Click to collapse
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
Where did you find a tarp img for the LG k51?
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
tarp image????? just follow the tutorial.
I meant TWRP recovery . After you've unlocked the bootloader where did you get a custom recovery to flash for the LG k51. From what I saw on Team Wins website, there isn't one.
Bhanu8082 said:
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Click to expand...
Click to collapse
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
sCriptKittY1987 said:
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
Click to expand...
Click to collapse
I doubt that's going to work, but let me know if it does. Carriers and manufacturers use a variety of sophisticated security schemes like requiring lengthy codes that only they can provide, etc to purposely make it very difficult to unlock bootloaders. Tmobile gave me a K51 for free. They apparently feel the have to pay for it by spying on me. I bought a moto g7 plus unlocked for $117 directly from Moto and put Lineage on it, no gapps Would love to use thie k51 though if anyone figures it out because it's more waterproof and bigger battery.
mgsgta3 said:
I can't find anything definitive about whether it's rootable or not
Click to expand...
Click to collapse
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
and let me guess my doofus luck im guessing no way to unlock it with out a P.C. like nuttin at all?
Absolutely no of the crap above works at all in any capacity especially sprint. Generic postings like hold volume down and power also doesn't work to go into fastboot so if you guys are following the advice of some of these guys don't because you'll drop more money on a new phone then you will unlocking it some variants verizon is one I think you have to call LG I know I spent 6 hrs on the phone with "tech support" aka "jokes with a screen to read from" to FINALLY get into touch with an engineer who told me the only way "NOW" to unlocked the bootloader is in his office which means it has to be depot to be unlocked which as of this moment lg is not doing that WILL change in the future that was 12/03/2020. Even running external adb with kali linux to hack it broke the bootloader and sends you into an infinite reboot loop
jwoegerbauer said:
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
This returns no value on a locked bootloader because even with Dev. Opt. Enables its still read only until bootloader is unlocked this is verified on two carriers k51's sprint and att. However it is unlockable we haven't found it and/or LG has not added this service to their site which is where you will get the info needed for the unlocked.
Oh my. You know you need to do all this from a computer, right? Can't do it in an Android terminal because fastboot commands are only valid in a phone's bootloader environment. And if you didnt know that then rooting and all of the dangers that come with it just isnt for you. But yes, it's rootable. So here you go anyway.
Reboot the phone to download mode.
Install LG's K51 usb drivers, and install adb and fastboot, on your computer.
Open a command prompt and type: fastboot oem unlock
If it does anything other than pat you on the back and tell you it's proud of you and how well you follow instructions, then go back and follow the effing instructions.
Otherwise, type: fastboot reboot.
Download magisk manager.
Do the magisk manager.
Use the LG flash tool on your computer to flash what you just did when you did the magisk manager.
And presto, you're rooted. Or I successfully left out enough info and you dont know how to use Google, leaving your device still not rooted. And thank god for that.
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Kenwoodquality69 said:
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Click to expand...
Click to collapse
Yo Ken,
So your K51 rooted?
If so, maybe you could provide a step by step?
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
TexasPride said:
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
Click to expand...
Click to collapse
O lord i hope this isnt true