Related
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Whoa! the unlock tool is out!
Is there any chance someone can make a root guide? I really want to buy Zenfone 3 Ultra but I wouldn't do it without root method out there. Any help is appreciated.
Were waiting on a dev to compile TWRP for us then we can get root
Trying to root ZU680KL
Hi!
I have unlocked my ZU680KL with the Asus unlock tool. Bootloader shows 'unlocked'.
Then I unpacked the stock boot.img (from WW_13.6.15.21_20161215, this what I have installed) and using Vim I set:*ro.secure=0, ro.adb.secure=0, and*ro.debuggable=1 in default.prop.
Repacked the new boot.img and flashed it with 'fastboot flash boot new-boot.img'.
'adb shell getprop' indicates that the new setting was applied.
Yet in the stock recovery mode I cannot install SuperSU-v2.79.zip and no adb devices are seen in recovery mode.
What else is needed? Do I have to edit something in the stock recovery or must wait for custom TWRP?
I was following the basic instructions found here:
https://machiry.wordpress.com/2012/10/26/getting-root-access-on-android-the-actual-way/
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
hillg001 said:
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
Click to expand...
Click to collapse
Any news?
https://forum.xda-developers.com/ze...t-zenfone-3-ultra-7-0-ww14-1010-1703-t3612108
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
when the ultra 3 first came out, many suggested waiting for a boot loader unlocker, & not updating any Android versions, because an unlock program might not work on subsequent Android versions. Is that the case? ... or does the unlocker work on the newest Android version too.
Thanks
.
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
I have just downloaded the zip, made the APK and installed it on my Zenfone 3 Ultra.
When I run the app, after clicking all the "are you sure..." acknowledgements, the app does not succeed in unlocking the bootloader. The error message indicates an unknown or perhaps network error, and suggests I "try again later..."
Running WW_14.1010.1804.75_20180612
Anybody else seeing this?
Ideas??
Reading on the ASUS blogs, they indicate it isn't supported anymore (no surprise), but shouldn't it still work??
heroxbd said:
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
Click to expand...
Click to collapse
Note the links above no longer work. Yes, you can get to the page, but the unlocker isn't there any more.
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
Does anybody know which version(s) of the stock ROM this works with? I've tried a couple, and all of them just yield the "unknown error" when running the unlocker.
If you know of a stock ROM version this works with, please post a URL for where I can find it (as it's proven really hard to find specific versions...)
Thanks in advance.
agree it no longer works. getting the unknown error...wait message that everyone else is getting. there are other XDA threads that indicate the same.
Keeping bootloader locked. Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even the SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
-
jrchester said:
Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even and SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
Click to expand...
Click to collapse
How did you do that? Can I get more details?
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hi Madlzz:
Checkout my XDA post here for more details on how I did this:
unlocking bootloader zenfone ultra
Hi all ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago, my friend wanted to see if my phone could be charged with a dash charger, where others wouldnt my battery was already low and overnight it ran out and when i...
forum.xda-developers.com
- John
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
lucy1983 said:
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
Click to expand...
Click to collapse
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
jrchester said:
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
Click to expand...
Click to collapse
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
lucy1983 said:
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
Click to expand...
Click to collapse
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
jrchester said:
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
Click to expand...
Click to collapse
You can install Magisk 24 without any problems. For me it doesn't break safetynet and play store says "certified". Even without enabling zigisk.
Issue status: Fixed
Issue details: Bricked device with Bootloader locked.
Issue solution : This thread
Thanks to: devcon69
Special Thanks for information: takagen, lindvall, cebu, darkhelmetnl
File sources: https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
Info sources: https://forum.xda-developers.com/showpost.php?p=79083641&postcount=38
Been flashing roms, wanted to try them out, and before you ask, yes I wipe cache, system, and data before I do a wipe...
But somewhere down the line, rotation stops working, I don't know why, but it just did and wouldnt work in any rom I tried
Eventually Twrp stopped letting me flash new roms giving me excuses like zip verification failure.
Then it stopped letting me flash other zips like verity disable and gapps.
Being basically locked to Havoc wasn't really an option for me so I decided to go the nuclear route and reflash stock rom+recovery which bricked my device but not before wiping my recovery and locking that pesky bootloader. "SYSTEM DESTROYED"
So here I am with a locked bootloader, only access to Fastboot, and what I believe is EDL as it shows up as Qualcomm driver in device manager if I do it right.
I tried using the same flash tool that bricked my device both in Fastboot and EDL, in Fastboot it tells me my device is locked
In EDL it tells me the device is locked and error getting "hello packet"
And when I try to use the unlock tool, it tells me my current account is not bound to the device, even though it used to be. And I don't have a system to go in to make it so again.
So does anyone know how to flash anything around the locked bootloader?
Hi
I do not have much knowledge of xiaomi, just my mi pad 4 ... But from what I read, you must never relock a bootlader already unlock with fastboot ... It almost systematically causes a hard brick
Try the steps did here ?
https://forum.xda-developers.com/mi-pad-4/help/destroyed-lock-bootloader-t3840762/page5
Zayatoshi said:
Hi
I do not have much knowledge of xiaomi, just my mi pad 4 ... But from what I read, you must never relock a bootlader already unlock with fastboot ... It almost systematically causes a hard brick
Click to expand...
Click to collapse
Doesn't really mention that in the instruction manual. And the flashing tool locks the bootloader anyway and the guides don't mention the bricking issue + anyone that suggests using the flash tool tend to leave that part out, it's only until after I done it and am googling how to undo are people showing up with comments saying "yeah you shouldn't have done that"
Like where were the warnings before?!
takagen said:
Try the steps did here ?
https://forum.xda-developers.com/mi-pad-4/help/destroyed-lock-bootloader-t3840762/page5
Click to expand...
Click to collapse
Hopefully ill have time to try that tomorrow but thank you so much for a suggestion.
I have put my device in EDL I think, kind of hard to tell with the screen off, but when I attempted the flash, the miflash tool told me sry can't do it cause of a lock.
I'll investigate later if it's anything different than what I tried before.
I definitely want to get it back to working order because I have yet actually got a chance to enjoy using it. The first thing I did was try to flash a rom and it's been downhill of trying to troubleshoot onething after another.
I didn't backup via twrp because I forgot, and I didn't anticipate just how locked down and a pain in the ass Xiaomi devices could be, and in the past on other devices, recovering from a bricked state is usually a more simple process.
Thank god my pocophone has a full miui backup via twrp
My device was bricked and the people credited helped me recover it.
Had to take off the back to put the device into EDL mode.
Used specifically the software /files and instructions provided by devcon69, the patches elf file was key
And the information provided by Lind all helped me more than I thought, particularly the part where he/she said "I waited too long"
So as soon as I opened up miflash tool, I clicked flash as fast as I could, maybe the tool goes through some sort of background security check and clicking flash starts before it finishes (I doubt it) , I don't know...
takagen said:
Try the steps did here ?
https://forum.xda-developers.com/mi-pad-4/help/destroyed-lock-bootloader-t3840762/page5
Click to expand...
Click to collapse
You helped me out a ton! Tysm!
Congrats
Hello! I can't seem to make TWRP Official app (from Google Playstore) and Magisk root to work.... so hacking game is still a distant possibility here. I downloaded both app, but couldn't get them to work, so now uninstalled both.
My phone is: Moto G7-Power with Android 9 (Pie), my questions are:
1. Which of these two should I install first on android without PC? Magisk or TWRP? Seem to get conflicting instruction from those tutorials on Youtube.
2. After downloaded "TWRP Official app" from Google Playstore, chose my phone from the list and downloaded the version for my phone. It said downloaded successful, but I can't flash TWRP, can't open it in recovery mode (hardreset), it wouldn't do anything!
3. As for Magisk apk... one of the two files won't install, the zip files.... it said "failed"... so what do I do then?
Can anyone please help me fix all these problems? Very frustrating right now.
Morky001 said:
Hello! I can't seem to make TWRP Official app (from Google Playstore) and Magisk root to work.... so hacking game is still a distant possibility here. I downloaded both app, but couldn't get them to work, so now uninstalled both.
My phone is: Moto G7-Power with Android 9 (Pie), my questions are:
1. Which of these two should I install first on android without PC? Magisk or TWRP? Seem to get conflicting instruction from those tutorials on Youtube.
2. After downloaded "TWRP Official app" from Google Playstore, chose my phone from the list and downloaded the version for my phone. It said downloaded successful, but I can't flash TWRP, can't open it in recovery mode (hardreset), it wouldn't do anything!
3. As for Magisk apk... one of the two files won't install, the zip files.... it said "failed"... so what do I do then?
Can anyone please help me fix all these problems? Very frustrating right now.
Click to expand...
Click to collapse
Hello, Morky.
I am afraid I don't understand what you really mean by your question above. You have not used a PC yet but tried to flash TWRP. Please give me more insight on what you are trying to do.
x.ak**** said:
Hello, Morky.
I am afraid I don't understand what you really mean by your question above. You have not used a PC yet but tried to flash TWRP. Please give me more insight on what you are trying to do.
Click to expand...
Click to collapse
Thank you, Kumar for your response. First of, I'm NOT a techie like you. I just followed these tutorials on YouTube....
With TWRP app this is what happened (or not happened):
https://www.youtube.com/watch?v=RtvI2C9VrOY
Started having problem at the 3:00 min mark here as well... even with hardreset
https://www.youtube.com/watch?v=wEHChHcpZEI
I couldn't do what this guy did at the 3:00 min mark....
With Magisk Manager app.... what happened was just like at the 3:00 min mark on this video
https://www.youtube.com/watch?v=DvlLy42UtGg
I thought explaining what'd happened by referencing what I was doing per these tutorials would better answer your questions, since I don't know how else to say it, again not a techie person.
<Morky>
You have to unlock your bootloader first. It requires that you read out a encrypted code from the phone, via the USB port using ADB/Fastboot. The code is entered into a web page at Motorola, and if your phone can be unlocked, they will send you a unlock code. Then you fastboot the unlock code. then fastboot twrp. then flash magisk.
you may consider going to the forum page for your phone, it will have all the details.
https://forum.xda-developers.com/g7-power
look under the guides section
hope that helps
Nivead said:
You have to unlock your bootloader first. It requires that you read out a encrypted code from the phone, via the USB port using ADB/Fastboot. The code is entered into a web page at Motorola, and if your phone can be unlocked, they will send you a unlock code. Then you fastboot the unlock code. then fastboot twrp. then flash magisk.
you may consider going to the forum page for your phone, it will have all the details.
https://forum.xda-developers.com/g7-power
look under the guides section
hope that helps
Click to expand...
Click to collapse
Nivead, I did unlocked the OEM before downloading that though, but still didn't work. The phone is an unlocked phone.
And, thank you for your help.
Morky001 said:
Kumar, I did unlocked the OEM before downloading that though, but still didn't work.
Click to expand...
Click to collapse
And.. thank you.
Morky001 said:
Thank you, Kumar for your response. First of, I'm NOT a techie like you. I just followed these tutorials on YouTube....
With TWRP app this is what happened (or not happened):
https://www.youtube.com/watch?v=RtvI2C9VrOY
Started having problem at the 3:00 min mark here as well... even with hardreset
https://www.youtube.com/watch?v=wEHChHcpZEI
I couldn't do what this guy did at the 3:00 min mark....
With Magisk Manager app.... what happened was just like at the 3:00 min mark on this video
https://www.youtube.com/watch?v=DvlLy42UtGg
I thought explaining what'd happened by referencing what I was doing per these tutorials would better answer your questions, since I don't know how else to say it, again not a techie person.
<Morky>
Click to expand...
Click to collapse
Hello, Morky.
I do not understand how one can flash any image directly from the device without rooting it. Now, in order to root your device you will need either TWRP or flash SUPERSU or Magisk using fastboot. If you wish to root your device and install TWRP on it, you will require access to a computer.
The phone has to be BOOTLOADER unlocked in order to install TWRP and Magisk. Turning on OEM unlock, is a step in unlocking the phone - but it does not unlock the bootloader.
When you are saying the phone is unlocked, I believe you mean the phone is unlocked so it will run on any cell phone carrier - a way the phone is sold. But its not bootloader unlocked.
Bootloader unlocked is different - Most phones are sold with the bootloader locked and because of that, you cannot modify the operating system. Unlocking the bootloader allows you to modify the the android operating system.
You will have to install Motorola USB drivers on your computer. Go to the Motorola page at: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and read about unlocking the bootloader. You will have to create a Motorola account to get an unlock code, if the bootloader can be unlocked. The pages will also have a link to obtain the Motorola USB drivers (MotorolaDeviceManager_2.5.4.exe).
You will need to install Minimal ADB Fastboot, a terminal program that allows you to push data/commands back and forth between the computer and your phone via the USB port. https://forum.xda-developers.com/showthread.php?t=2317790 You will use the FASTBOOT command to obtain the encrypted unlock code from the phone. You will also use FASTBOOT to install the unlock code that Motorola will send you,
After the bootloader is unlocked, you will use FASTBOOT to install TWRP into your phones recovery partition. TWRP info at https://www.xda-developers.com/how-to-install-twrp/ TWRP is a backup and recovery program that is used to install programs, etc,
After you install TWRP, you can install MAGISK, which will ROOT the phone. Magisk info at https://forum.xda-developers.com/apps/magisk.
Please go to the forum I told you about and under the guides section you will find documentation that explains how to root the phone and install custom ROMs.
https://forum.xda-developers.com/g7-power A guide will give you the finer details for your phone model.
Before you do any of the above, I advise you strongly to have a backup. Using FASTBOOT there is a command called "getvar all", it will return a long printout of info and it will include a readout of the original firmware installed on the phone. You will want to know this in case you brick the phone. Having this info will allow you to obtain the original firmware and be able to restore it via FASTBOOT. Firmwares at https://mirrors.lolinet.com/firmware/moto/ .l After installing TWRP, you should backup the phone to your SD card and then move the backup to your computer for future needs.
Good luck.
Nivead said:
The phone has to be BOOTLOADER unlocked in order to install TWRP and Magisk. Turning on OEM unlock, is a step in unlocking the phone - but it does not unlock the bootloader.
When you are saying the phone is unlocked, I believe you mean the phone is unlocked so it will run on any cell phone carrier - a way the phone is sold. But its not bootloader unlocked.
Bootloader unlocked is different - Most phones are sold with the bootloader locked and because of that, you cannot modify the operating system. Unlocking the bootloader allows you to modify the the android operating system.
You will have to install Motorola USB drivers on your computer. Go to the Motorola page at: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and read about unlocking the bootloader. You will have to create a Motorola account to get an unlock code, if the bootloader can be unlocked. The pages will also have a link to obtain the Motorola USB drivers (MotorolaDeviceManager_2.5.4.exe).
You will need to install Minimal ADB Fastboot, a terminal program that allows you to push data/commands back and forth between the computer and your phone via the USB port. https://forum.xda-developers.com/showthread.php?t=2317790 You will use the FASTBOOT command to obtain the encrypted unlock code from the phone. You will also use FASTBOOT to install the unlock code that Motorola will send you,
After the bootloader is unlocked, you will use FASTBOOT to install TWRP into your phones recovery partition. TWRP info at https://www.xda-developers.com/how-to-install-twrp/ TWRP is a backup and recovery program that is used to install programs, etc,
After you install TWRP, you can install MAGISK, which will ROOT the phone. Magisk info at https://forum.xda-developers.com/apps/magisk.
Please go to the forum I told you about and under the guides section you will find documentation that explains how to root the phone and install custom ROMs.
https://forum.xda-developers.com/g7-power A guide will give you the finer details for your phone model.
Before you do any of the above, I advise you strongly to have a backup. Using FASTBOOT there is a command called "getvar all", it will return a long printout of info and it will include a readout of the original firmware installed on the phone. You will want to know this in case you brick the phone. Having this info will allow you to obtain the original firmware and be able to restore it via FASTBOOT. Firmwares at https://mirrors.lolinet.com/firmware/moto/ .l After installing TWRP, you should backup the phone to your SD card and then move the backup to your computer for future needs.
Good luck.
Click to expand...
Click to collapse
Deae Nivead,
..Oy! That sounds painful!! Guess, I have no business be doing this lock/unlock/rooting thing, huh?! Not a techie at all, this is very foreign to me! And those guys on YouTube... they lied then, said I could do all these without PC... Yeah, right! Turned out, it wasn't as easy as they were showing on videos. (((sigh))) Would be easier if I just send my phone to you?!?!!!
Thank yoooouuu soooo much for taking the time to write/tell me all this, truly appreciate your help and replies.
<Morky>
x.ak**** said:
Hello, Morky.
I do not understand how one can flash any image directly from the device without rooting it. Now, in order to root your device you will need either TWRP or flash SUPERSU or Magisk using fastboot. If you wish to root your device and install TWRP on it, you will require access to a computer.
Click to expand...
Click to collapse
Kumar,
I guess those YouTube tutorials omitted left out a lot of steps and not as easy nor simple as they made it to be.... "without PC" as they claimed. How would someone with no background in computer programing, nor a "techie" like you here at xda... like me would know that?! If you "don't understand how....." I wouldn't understand either!! More so than you. One thing I've learnt now, all those tutorials about rooting and TWRP. on YouTube... are crap.
Hi,
I tried to upgrade my US998 from Oreo to Pie using LGUP patched. The upgrade process went well until the phone restarted and have this error message:
"Your device has failed a routine safety check and will not boot..."
I did try using LG Bridge to fix = not working
I did try fastboot boot laf.img (using extracted laf from H93031a_00_OPEN_EU_OP_1105) not working.
Any other solution?
Thanks
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
JanBoyGamer23 said:
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
Click to expand...
Click to collapse
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
jaacoozee said:
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
Click to expand...
Click to collapse
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
JanBoyGamer23 said:
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
Click to expand...
Click to collapse
I'm not sure. Normally I access download mode using volume up and power button. The download mode was there for a sec and then the screen back to
"Your device has failed a routine safety check and will not boot..."
again.
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
JanBoyGamer23 said:
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
Click to expand...
Click to collapse
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
JanBoyGamer23 said:
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
Click to expand...
Click to collapse
Unfortunately my LG V30 is US region. The official bootloader site not support my phone. Thanks for your info anyway
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
schwinn8 said:
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
Click to expand...
Click to collapse
Thanks for the reply.
I didnt install TWRP or any recovery tools to my phone. My phone bootloader still locked thou.
I have read the WTF thread but the problem is I cant get into my Download mode.
Ok, what steps are you using to try to get into download mode? Presumably turning off the phone, then holding the volume up button and plugging in the USB cable (other end already connected to a Windows computer), correct? If that doesn't work, can you try other USB cables? Sometimes a bad cable could prevent the phone from going into download mode.
Yesterday, decided to remove bloatware(mostly Google) on my Huawei p8 lite using ADB. And somehow removed this.
:/ $ pm uninstall -k --user 0 com.android.location.fused
Restarted.
Boot Loop.
Before I rebooted my phone usb debugging was on.
Phone boots into eRecovery with 4 options
1)Download latest version and recovery(usuless gives my an "Getting package info failed")
2)Wipe data/factory reset
3)Reboot
4)Shutdown
When I'm connected to pc I allways get a message "Unable to open MTP device".
I don't have the root privalage so I can't folow these steps in this guide below.
Bootloop after removing com.android.location.fused [SOLVED]My questions is:
1. Any method of saving data on bootloop phone without root?
2. Should I try factory reset?
I don't understand what you want, but you can't root in boot loop.
But I hear you will root, it's really easy to root Huawei!
Guide.
1. Get your firmware, with hisuite, after install downgrade or update, will firmware file be saved in document folder on PC.
2. Extract files inside the firmware file, and find the boot.img, system.img or boot.img and opened it and modified, some you will and repack it again.
3. Update hash's for partition controller.
4. Make a form of server and port forward your device to think this is the server there get updating from and see request some your phone ask for or read source of Huaweis update.apk.
4. Configure your server, with coding and upload the firmware to your server.
5. Now just install your update and you have custom os
JonasHS said:
But I hear you will root, it's really easy to root Huawei!
Click to expand...
Click to collapse
This guide is missing most important predecessor step: unlocking bootloader (and therefore useless)
JonasHS said:
I don't understand what you want, but you can't root in boot loop.
Click to expand...
Click to collapse
Thanks for reply. Sorry that I not spicified. My problem is that I unistalled com.android.location.fused witch resulted in boot loop. My phone is not rooted and I don't know what to do next. Only think I can is factory reset, becouse eRecovery gives me an error. I just looking right now for any way to save my data. I found a similar problem solved, but person rooted phone before boot loop. So I guess I only have 1 option then?
You can try to start you Huawei in back up mode,
JonasHS said:
You can try to start you Huawei in back up mode,
Click to expand...
Click to collapse
Yes my phone in recovery mode. Should I try "Wipe data/factory reset"? Because "Download latest version and recovery" option gives me an error"Getting package info failed".
You don't need to unlock bootloader for edit system, i making my own exploit and do it.
O just look at this:
We say you can't edit Any software file on your device, because you don't has permission, like Linux nonroot user.
There are only 1 way to get this permission, it's unlocking bootloader and add your code to software.
NOT TRUE.
if we put this together with a door that's locked and you don't have the key, what do you do?
I will find another way to open the door.
so to show what i mean: update.apk ask server for download the update and send it back too your phone, and your phone will install. Inside an update package, where are boot.img and system.img, what if we edit this file before update, and put a code some will give your user on system the highest privilege. But we can't edit this file, because they are saved on folder, we don't has permission too?
For do this, can we manipulate the data server send back too us.
Prot forwarding.
JonasHS said:
You don't need to unlock bootloader for edit system, i making my own exploit and do it.
Click to expand...
Click to collapse
So you're a hacker and found method to properly sign system.img with huawei's private oem key? you're a genius!
https://android.googlesource.com/platform/external/avb/+/master/README.md#The-VBMeta-struct
Unfortunately the repair has to be done in /data/system/users/0/package-restrictions.xml and requires root access. Furthermore /data is encrypted therefore that modification can't be done offline, it requires booted android to stage where we can enter screen unlock pin (or at least to stage where /data/system is decrypted)
JonasHS said:
You don't need to unlock bootloader for edit system, i making my own exploit and do it.
O just look at this:
We say you can't edit Any software file on your device, because you don't has permission, like Linux nonroot user.
There are only 1 way to get this permission, it's unlocking bootloader and add your code to software.
NOT TRUE.
if we put this together with a door that's locked and you don't have the key, what do you do?
I will find another way to open the door.
so to show what i mean: update.apk ask server for download the update and send it back too your phone, and your phone will install. Inside an update package, where are boot.img and system.img, what if we edit this file before update, and put a code some will give your user on system the highest privilege. But we can't edit this file, because they are saved on folder, we don't has permission too?
For do this, can we manipulate the data server send back too us.
Prot forwarding.
Click to expand...
Click to collapse
That sounds awesome. I guess we can try.
aIecxs said:
So you're a hacker and found method to properly sign system.img with huawei's private oem key? you're a genius!
https://android.googlesource.com/platform/external/avb/+/master/README.md#The-VBMeta-struct
Unfortunately the repair has to be done in /data/system/users/0/package-restrictions.xml and requires root access. Furthermore /data is encrypted therefore that modification can't be done offline, it requires booted android to stage where we can enter screen unlock pin (or at least to stage where /data/system is decrypted)
Click to expand...
Click to collapse
Dahm.
The easiest way to fix bootloop is factory reset. There is no way to safe userdata without fixing bootloop, sorry. it's a hen and egg dilemma.
aIecxs said:
The easiest way to fix bootloop is factory reset. There is no way to safe userdata without fixing bootloop, sorry. it's a hen and egg dilemma.
Click to expand...
Click to collapse
I agree.
Just reset its easiest.
Think about this here: your PC has SSD or HDD and you can take it off and take it into new pc, and edit everythiny on the disk without admin and make a backup.
The true is, you can do the same with a phones chip, but it's hard to do
Next time, before playing with packages, do a backup of your pictures.
Btw you can unlock bootloader with PotatoNV and root with Magisk. rooted devices you can backup with Migrate or TWRP.
New to said:
Yes
Huawei don't store theres OEM keys on devices chip, so they will never could control if i replaced it with my own, and avb will still work in offline mode, so I can just read vbmeta.img with avbtool.py and generate the same vbmeta.img with different size or hash of partitions, some is benn modified.
Click to expand...
Click to collapse
You could me a hacker, i am not a hacker, i have just a good kwoning of code and dissembling
JonasHS said:
Just reset its easiest.
Think about this here: your PC has SSD or HDD and you can take it off and take it into new pc, and edit everythiny on the disk without admin and make a backup.
The true is, you can do the same with a phones chip, but it's hard to do
Click to expand...
Click to collapse
aIecxs said:
Next time, before playing with packages, do a backup of your pictures.
Btw you can unlock bootloader with PotatoNV and root with Magisk. rooted devices you can backup with Migrate or TWRP.
Click to expand...
Click to collapse
Thanks for replys(they gived me alot of ideas what I can learn about phone and hacking).I will be more careful about deleting packages in future.
I just did Factory reset and my phone is working fine again.
JonasHS said:
Huawei don't store theres OEM keys on devices chip, so they will never could control if i replaced it with my own, and avb will still work in offline mode, so I can just read vbmeta.img with avbtool.py and generate the same vbmeta.img with different size or hash of partitions, some is benn modified.
Click to expand...
Click to collapse
Of course they don't. No, you can't flash own vbmeta.img on locked bootloader as the bootloader verifies the hash of vbmeta which is oem signed (you don't have key).
If you know about any flash tool for HiSilicon Kirin exist (IDT?) it would probably easier to flash magisk patched (properly avb signed) ramdisk.img to get root access and adb (osm0sis AIK is capable of signing AVBv2) instead of modifying system.
Nevertheless this won't fix bootloop therefore it's pointless, as the culprit lies in package-restrictions.xml. it's impossible to decrypt userdata partition offline, so there is no hope sorry.
Who has told you this here, i am developer and has readers the source code, yes you can make your own sign keys with openssl
yes, that is called user-settable root of trust and requires you to compile own complete ROM, for example LineageOS. In any case that is impossible with stock EMUI as again you can't cheat Android Verified Boot chain of trust per design. That's the whole purpose of locked bootloader.