Related
WARNING: You REALLY need to UNDERSTAND and read EVERYTHING or you MAY brick your phone!
Purpose of this thread:
To get you, the Verizon Moto X 2014 owner, from any version to 5.0 ( LXE22.46-11).
Things you will need:
FXZ LXE22.46-11
Thanks @stras1234
Instructions:
Use the RSD Flasher with KEEP DATA to flash this on your phone with RSD.
OR
Use the House of Moto with KEEP DATA to flash this to your phone with fastboot.
OR
RSD Lite 6.2.4
Has anyone done this? Mighty tempting... Didnt even know this was possible!
I'm not sure what you mean by "done this", exactly, but, if you mean flashing this FXZ to upgrade, then yes. It's the same update as the OTA that's pushing out now...this is just the full version rather than the update zip. Is that what you were asking?
Do you mind reuploading both of those tools to a new file hosting service? Because I can't see either of them because I'm not a member of DroidRZR.com and I don't intend to be.
Or just providing the direct link to a upload or mirror would be great.
Just use RSD 6.2.4 in that case. I keep the tools I wrote in one place only because there's a lot of instructions that go with it and it's easier to support if it's in one place. But the link to RSD is to a mediafire download so you should be able to grab that no problem.
Don't bother, just updated ota. Rocking lollipop now
I followed your root and boot loader unlock on the xt926 I had. You being on the moto x makes me very happy. I bow down to you
SamuriHL said:
Just use RSD 6.2.4 in that case. I keep the tools I wrote in one place only because there's a lot of instructions that go with it and it's easier to support if it's in one place. But the link to RSD is to a mediafire download so you should be able to grab that no problem.
Click to expand...
Click to collapse
Can you provide the direct links to both then? I'd like to be able to clean flash this at some point.
bmwh0r3 said:
I followed your root and boot loader unlock on the xt926 I had. You being on the moto x makes me very happy. I bow down to you
Click to expand...
Click to collapse
I don't own any of these devices. LOL
The fact you are so good with them is even more amazing.
SamuriHL said:
I don't own any of these devices. LOL
Click to expand...
Click to collapse
You're probably still rocking the Bionic
texassax said:
You're probably still rocking the Bionic
Click to expand...
Click to collapse
It's around. I'm rocking an NX6 right now. Love it.
SamuriHL said:
It's around. I'm rocking an NX6 right now. Love it.
Click to expand...
Click to collapse
Trying to extract the system.img - is there a catch with Moto devices? I can't seem to get anywhere with mounting it on Windows or OS X.
I have consulted the great and powerful(tm) search engine thingie and determined your fate on this endeavor as documented with the following scroll...
http://forum.xda-developers.com/showthread.php?t=2294909
Sent from my SM-P600 using Tapatalk
SamuriHL said:
I have consulted the great and powerful(tm) search engine thingie and determined your fate on this endeavor as documented with the following scroll...
http://forum.xda-developers.com/showthread.php?t=2294909
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
LOL - If only it were that easy. Anyone else?
SamuriHL said:
I don't own any of these devices. LOL
Click to expand...
Click to collapse
me neither
joderme said:
Trying to extract the system.img - is there a catch with Moto devices? I can't seem to get anywhere with mounting it on Windows or OS X.
Click to expand...
Click to collapse
Extracting system.img on Windows is simple Just do the following:
1. You need two utilities: sparse2img.exe and ImgExtractor.exe
2. Download and extract both in one folder
3. Put system.img in the same folder
4. Run CMD from that folder
5. Run: sparse2img system.img system_new.img
File system_new.img will be created
6. Run: ImgExtractor system_new.img
Folder system_new_ will be created. You will find all extracted files and folders here
Al936 said:
Extracting system.img on Windows is simple Just do the following:
1. You need two utilities: sparse2img.exe and ImgExtractor.exe
2. Download and extract both in one folder
3. Put system.img in the same folder
4. Run CMD from that folder
5. Run: sparse2img system.img system_new.img
File system_new.img will be created
6. Run: ImgExtractor system_new.img
Folder system_new_ will be created. You will find all extracted files and folders here
Click to expand...
Click to collapse
Welp - I feel like an idiot. I saw this method elsewhere, however, it seemed like it would only work with system1.sparse files as other updates have had multiple files for system.img.
This worked - thanks!!!
Now to find the APKs for moto assist.
This is quite interesting as none of the APKs will work on a Nexus 6.
APKs from the pure edition seem to have little problem.
I would think that the Nexus 6 wouldn't have a problem running these.
Hi
These is a Windows batch file applications which can automatically downgrade your
1) Moto G XT1033 on Lollipop GPe to KitKat Asia Retail version, or
2) Moto G XT1032 on Lollipop GPe to KitKat GPe
Downgrade is possible and i have successfully done it.
There is a slight bug that every time you boot a line appears flickering the screen for some time and i don't take any responsibility if you end up bricking your phone
Information
The contents of both the firmwares are renamed according to their version and the commands are also modified to be compatible with the renamed components.
The components are renamed so that cmd can differentiate between both the firmwares.
Also 'motoboot.img" and 'gpt.bin' are removed from both the firmwares since they cause error during flashing and are not required.
So you can either download the modified firmwares from below or if you already have the original firmwares downloaded then make the following changes :-
1) Delete 'motoboot.img' and 'gpt.bin' from both the firmwares.
2) For GPe firmware rename the contents by adding gpe before each file. Eg. NON-HLOS.bin to gpeNON-HLOS.bin
For Asia Retail firmware rename by adding 33 before each file. Eg NON-HLOS.bin to 33NON-HLOS.bin
Instructions :-
1) Download and install "Minimal ADB and Fastboot" in a separate folder.
2) Download the batch file and put it in that folder.
3) Now if you want to downgrade just to GPe 4.4.4 then just download the GPe 4.4.4 zip file and extract it to the same folder. If you want to downgrade to Asia 4.4.4 then download both GPE 4.4.4 and Asia 4.4.4 zip files and extract it to that folder.
4) Connect your phone to the computer and ensure USB Debugging is enabled
5) Then just execute the batch file.
Downloads
Batch file - https://drive.google.com/file/d/0BzJVjgEmc7G_Y0NCVFJyVUE4cDA/view?usp=sharing
GPe firmware - https://drive.google.com/file/d/0BzJVjgEmc7G_OG9PNzlEUC1GT1U/view?usp=sharing
Asian firmware - https://drive.google.com/file/d/0BzJVjgEmc7G_bWxZZXJrbThYNEE/view?usp=sharing
Minimal ADB and Fastboot - https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
Cresdits - RootJunky for batch script, xda members for firmwares.
Meuuks13 said:
Hi
These is a Windows batch file applications which can automatically downgrade your
1) Moto G XT1033 on Lollipop GPe to KitKat Asia Retail version, or
2) Moto G XT1032 on Lollipop GPe to KitKat GPe
Downgrade is possible and i have successfully done it.
There is a slight bug that every time you boot a line appears flickering the screen for some time and i don't take any responsibility if you end up bricking your phone
Information
The contents of both the firmwares are renamed according to their version and the commands are also modified to be compatible with the renamed components.
The components are renamed so that cmd can differentiate between both the firmwares.
Also 'motoboot.img" and 'gpt.bin' are removed from both the firmwares since they cause error during flashing and are not required.
So you can either download the modified firmwares from below or if you already have the original firmwares downloaded then make the following changes :-
1) Delete 'motoboot.img' and 'gpt.bin' from both the firmwares.
2) For GPe firmware rename the contents by adding gpe before each file. Eg. NON-HLOS.bin to gpeNON-HLOS.bin
For Asia Retail firmware rename by adding 33 before each file. Eg NON-HLOS.bin to 33NON-HLOS.bin
Instructions :-
1) Download and install "Minimal ADB and Fastboot" in a separate folder.
2) Download the batch file and put it in that folder.
3) Now if you want to downgrade just to GPe 4.4.4 then just download the GPe 4.4.4 zip file and extract it to the same folder. If you want to downgrade to Asia 4.4.4 then download both GPE 4.4.4 and Asia 4.4.4 zip files and extract it to that folder.
4) Connect your phone to the computer and ensure USB Debugging is enabled
5) Then just execute the batch file.
Downloads
Batch file - https://drive.google.com/file/d/0BzJVjgEmc7G_Y0NCVFJyVUE4cDA/view?usp=sharing
GPe firmware - https://drive.google.com/file/d/0BzJVjgEmc7G_OG9PNzlEUC1GT1U/view?usp=sharing
Asian firmware - https://drive.google.com/file/d/0BzJVjgEmc7G_bWxZZXJrbThYNEE/view?usp=sharing
Minimal ADB and Fastboot - https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
Cresdits - RootJunky for batch script, xda members for firmwares.
Click to expand...
Click to collapse
Not sure, but why does everyone keep saying Simple tutorial and they keep going into complicated stuff, cant people just make a Folder called downgrade, have two more folders in it called Flash First and another flash second, instead of giving all this information and files that complicates the random user just make it simple, also, just stop talking about how its done because the random user doesnt care, they just want to downgrade which is why you made another thread which has the same c**p as the next one... Also, flashing 4.4.4 stock after GPe does need the GPT and Motoboot file as the partition table is different and it will refuse to flash the system dump files as the "image is too large"
NextGenGTR said:
Not sure, but why does everyone keep saying Simple tutorial and they keep going into complicated stuff, cant people just make a Folder called downgrade, have two more folders in it called Flash First and another flash second, instead of giving all this information and files that complicates the random user just make it simple, also, just stop talking about how its done because the random user doesnt care, they just want to downgrade which is why you made another thread which has the same c**p as the next one... Also, flashing 4.4.4 stock after GPe does need the GPT and Motoboot file as the partition table is different and it will refuse to flash the system dump files.
Click to expand...
Click to collapse
Oo i am sorry, i didn't realize that executing a batch file was more complex for the normal user than typing in commnads
Meuuks13 said:
Oo i am sorry, i didn't realize that executing a batch file was more complex for the normal user than typing in commnads
Click to expand...
Click to collapse
If executing batch files isn't a problem why have you made another thread when there is a thousand more of this exact tutorial? Also, its not am it is I'm... Idiot
NextGenGTR said:
If executing batch files isn't a problem why have you made another thread when there is a thousand more of this exact tutorial? Also, its not am it is I'm... Idiot
Click to expand...
Click to collapse
I didn't make any other thread about downgrading
Meuuks13 said:
I didn't make any other thread about downgrading
Click to expand...
Click to collapse
Who said you did? I said since there is 100 threads on the same thing why have you added on to this bulk by making one yourself when you haven't contributed any useful difference? I thought XDA was meant for people who know English and if they don't they can use a translator? Here is a useful link for you: https://translate.google.co.uk/
NextGenGTR said:
Who said you did? I said since there is 100 threads on the same thing why have you added on to this bulk by making one yourself when you haven't contributed any useful difference? I thought XDA was meant for people who know English and if they don't they should use translator? Here is a useful link for you: https://translate.google.co.uk/
Click to expand...
Click to collapse
yes i follow that site everyday, teaching my dog to how to interact with me.
And it is pretty much useful because it contains a batch file that gets things done.
Meuuks13 said:
Hi
These is a Windows batch file applications which can automatically downgrade your
Click to expand...
Click to collapse
There is an existing thread for this discussion.
http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
Thread closed for being a duplicate
TWRP 2.8.7.0 custom recovery
thanx to user @Unjustified Dev we have TWRP custom recovery for our phone.
download HERE
So anyone who download the TWRP should send him a dollar for beer or at least thank him!
Of course you do everything on your own!
To test before installation (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img
To install (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb flash recovery twrp-2.8.7.0-idol3.img
!BEFORE YOU START, PLEASE READ THIS!
And don´t forget to thank Famewolf for the tutorial, because this could save your phone when something go bad!
Thanks, tried it. It worked.
I also just installed SU directly, bypassing the previous root thread.
1. Download the .zip package from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
2. Put it on the root of my SD card.
3. In TWRP click install and find the .zip.
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Gynoid said:
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Click to expand...
Click to collapse
It's for 6045. For 4.7 TWRP, see this post: http://forum.xda-developers.com/showpost.php?p=61976520&postcount=18
Thanks!
is it functional for backing up our system in TWRP?
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
gecko702 said:
is it functional for backing up our system in TWRP?
Click to expand...
Click to collapse
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
famewolf said:
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
Click to expand...
Click to collapse
i am in touch with the dev and allready downloading the new build..will be soon on my google drive
Unjustified Dev said:
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
Click to expand...
Click to collapse
sorry, i corrected the link...
Convert TWRP Backup into flashable rom zip
I found these instructions that explain how to take a TWRP backup and turn it into a flashable zip file. This would allow someone to create a "factory" rom pre-rooted to be flashed.
For TWRP Backup
Transfer the TWRP backup from Phone to PC.
You’ll see a file named system.ext4.win which is the System partition backup of your device. Rename it to system.ext4.tar (Changing its extension from .win to .tar)
Extract the system.ext4.tar using an archive software like Winrar or 7zip.
If your TWRP backup is not in compression mode, you will directly get the system folder, else you will get a file named system.ext4, which should be renamed again to system.ext4.tar and extract it to get the system folder.
Take the boot.emmc.win file and rename it to boot.img.
Now collect a META-INF folder from any custom ROM which is made for your device. Make sure you get the correct Meta-Inf folder, else the Zip won’t work and might worsen the condition of your device.
Select the META-INF, System folders and the boot.img and right click your mouse and select add to Archive.
In the Archive settings, choose the extension of the compressed file as Zip (Make sure of this part)
Now you can use this Zip file to flash it on your Custom recovery.
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
DallasCZ said:
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
Click to expand...
Click to collapse
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
famewolf said:
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
Click to expand...
Click to collapse
i allready build some roms for my older device, so i know what it is about.
For the proper rom zip you have to make the updater script with all the simlinks and metadata ...in the latest update there were no simlinks in the updater script...
without them you can brick your phone.
for example simlinks from 4.4.2 Os from zte V5
Code:
symlink("/data/misc/audio/mbhc.bin", "/system/etc/firmware/wcd9306/wcd9306_mbhc.bin");
symlink("/data/misc/audio/wcd9320_anc.bin", "/system/etc/firmware/wcd9306/wcd9306_anc.bin");
symlink("/persist/WCNSS_qcom_cfg.ini", "/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini");
symlink("/persist/WCNSS_qcom_wlan_nv.bin", "/system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin");
symlink("/system/lib/modules/pronto/pronto_wlan.ko", "/system/lib/modules/wlan.ko");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("libGLESv2.so", "/system/lib/libGLESv3.so");
symlink("mksh", "/system/bin/sh");
this you cannot copy from another device....
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Acreo Aeneas said:
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Click to expand...
Click to collapse
Reboot or power on till you see the alcatel screen pop up....right away hold down up arrow and it should go into recovery.
Thank you so much...been waiting for this....
so now let ROM's start pouring in )))))))
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flashed the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Acreo Aeneas said:
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flash the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Click to expand...
Click to collapse
The default of boot, system and data should be fine for personal use however if you have not yet rooted please read here first! http://forum.xda-developers.com/idol-3/help/want-to-able-to-install-ota-updates-t3163745
So Awesome! best looking twrp Ive seen yet xD. Also, works well too. I havent tested backing up data, but I did a successful restore of the system and boot So far so good!
I have done my best to make sure most of the LG G5s out there will work with LGUP.
DISCLAMER: first and foremost, I take NO responsibilities for the possibility of a bricked phone(none whatsoever). if you brick it, it's YOUR fault, not mine.
ALWAYS BACKUP YOUR DATA BEFORE YOU DO ANYTHING
now for the fun bit:
1. Download and extract the LGUP.zip file from here as it contains everything you'll need except the firmwares.
2. To install the drivers for the device, go to the Drivers folder located in LGUP, and select InstallUSB.exe for a 32-bit system, or InstallUSB64.exe for a 64-bit system.
3. Install LGUP_Lab_Frame_Ver_1_11 that is in the LGUP folder
4. Install either the G5x86.reg or the G5x64.reg depending on whether you have a 32 or 64 bit windows installed.
5. Put the "model" folder in the LG Electronics\LGUP folder which will be either in C:\Program Files or C:\Program Files (x86) depending on whether you have a 32 or 64 bit windows installed
6. Put phone in download mode ( Phone off, vol up while plugging in usb from PC), start LGUP
7. Make sure you see a com # and phone model and at the bottom where it says BIN, select it, at which point you should see 3 dot on the right, select it and choose the .tot or .kdz file listed for your device, then hit start and wait for the magic.
Devices supported:
A992
F700K
F700L
F700S
H820
H830
H831
H850
H850TR
H858
H860
H860N
H868
LS992
RS988
US992
VS987
If I have not listed your device, list the exact model name (i.e LGLS992) in the comments below and I will add it for download.
I give creds to autoprime for his good work. If I missed anyone, I am giving you credits and apologizing now for not mentioning you.
Sorry for a questions that may be dumb, but what is this Tool supposed to do?
Sent from my LG-H850 using Tapatalk
Just a program that lets you flash firmware files to the described phone models
gwolfu said:
Just a program that lets you flash firmware files to the described phone models
Click to expand...
Click to collapse
Any possibility of achieving root with this on locked bootloaders?
Sent from my SM-N900T using Tapatalk
ForgottenSolstace said:
Any possibility of achieving root with this on locked bootloaders?
Click to expand...
Click to collapse
From what I understand, as long as the stock firmware is published by LG or the carrier we can inject root.
Veliion said:
From what I understand, as long as the stock firmware is published by LG or the carrier we can inject root.
Click to expand...
Click to collapse
This only if the model support the fastboot oem unlock command.
Without an unlocked bootloader is not possible to obtain root on Marshmallow, the only way would be find an exploit.
Sent from my LG G5 using XDA Labs
A992 in OP is typo.. should be AS992 obviously.
New model you could add:
H820PR
H850K
Thank you!
can i install gapps using this tool？ i have a H868 chinese version, google services are not preinstalled .
Broken Link =(
This is exactly what I needed, but when I attempt to access it, the google drive link is 404'd
Any way we might could convince you to update the info? Thanks so much in advance for your time.
--AmorImpermissus
AmorImpermissus said:
This is exactly what I needed, but when I attempt to access it, the google drive link is 404'd
Any way we might could convince you to update the info? Thanks so much in advance for your time.
--AmorImpermissus
Click to expand...
Click to collapse
all in there
https://1drv.ms/f/s!Au9ppCUF0J7lgZpUFNW-cf8ot0EweA
gwolfu said:
all in there
https://1drv.ms/f/s!Au9ppCUF0J7lgZpUFNW-cf8ot0EweA
Click to expand...
Click to collapse
Thanks a bunch gwolfu. However, what I really need are the LG<model>_DLL.msi files. Specifically, I need it for the RS988. It was listed in the supported devices at the beginning, but can't find it =(
LGUP not working...
Please help.
LGUP not working
I tried all versions LGUP, drivers installed and still does not work.
I have a LG unit G5 Demo and Windows 7 x64.
Can you advise?
Thank you.
milennium said:
Please help.
LGUP not working
I tried all versions LGUP, drivers installed and still does not work.
I have a LG unit G5 Demo and Windows 7 x64.
Can you advise?
Thank you.
Click to expand...
Click to collapse
When you open "Settings" -> "General" tab -> "About phone" -> "Hardware info" what does it have for "Model number?"
Model number: LG-H850
OK looking at the screenshot, I'm wondering if somehow the install got messed up. If you go to:
c:\program files (x86)\LG Electronics\LGUP\Model
What are the contents?
Also, open powershell as an administrator (usually can just type "powershell" from an elevated command prompt) and run this command:
Get-ChildItem -recurse 'HKCU:\Software\LG Electronics\LGUP' | where-object { $_.Property -like "DLL*"}
Then copy/paste the results so I can see them =)
In regedit, go to:
HKCU:\software\LG Electronics\LGUP\Model
Contents is (screen A and B).
Question. They must be unlocked bootloader?
Because my LGG5 be unblocked (Demo Unit).
milennium said:
Contents is (screen A and B).
Question. They must be unlocked bootloader?
Because my LGG5 be unblocked (Demo Unit).
Click to expand...
Click to collapse
You should be able to use the LGUP tool regardless of whether or not you have an unlocked bootloader. You may not be able to flash every kind of *.tot file, but whether or not your phone's bootloader is unlocked will have nothing to do with that error you're getting.
What about the output of the powershell command:
Get-ChildItem -recurse 'HKCU:\Software\LG Electronics\LGUP' | where-object { $_.Property -like "DLL*"}
?
Here is the result Powershell command:
milennium said:
Here is the result Powershell command:
Click to expand...
Click to collapse
OK, so, do the following, and then try to run LGUP with the phone connected, and let's see if it works:
1. Create a blank notepad file
2. Save it as something like h850.reg to your desktop where you can find it easily.
3. With the file still open in notepad, copy/paste the info below info and then save it again.
4. Close the file, then double-click it from your desktop to import it.
I've also attached it as a *.txt file which you can just change the extension to *.reg if that's easier:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model\H850]
"MODEL_NAME"="H850"
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H830.dll"
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model\LGH850]
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H850.dll"
"MODEL_NAME"="LGH850"
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model2]
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model2\H850]
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H850.dll"
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model2\LGH850]
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H850.dll"
DISCLAIMER: I will not be responsible of any issues you could face following this how-to. You do it at your own risk!
Here is a guide to root Honor 8 B521 Oreo. I did this on FRD-L09C432B521. Even if i think the "easy method" should work with other iteration of the phone (L02, L19, ...), I am not sure ramdisk is the same for all so test it if you feel lucky and please report if it works or not.
Requirements:
- Honor 8 running Oreo
- Unlocked Bootloader
- adb and fastboot installed on your computer (https://forum.xda-developers.com/android/software-hacking/alpha-adb-fastboot-installer-windows-t3637255 (Hit the thanks button)
Long method: (should work for all honor 8)
1 -- Visit http://pro-teammt.ru/firmware-database/ and search your exact build (FRD-L09C432B521 for me). If you have several phones listed for your build, click the name of the build on the left. This will open an xml file on the first line of which you will see the exact model it is for.
2 -- Once you know which firmware is yours, click on "filelist". This will list the files for this build and theirs url. Copy the link pointing to "update.zip" (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3109/g1699/v159456/f1/full/update.zip for me). Decompress it wherever you want.
3 -- Download and run Huawei Update Extractor (Hit the thanks button) . Untick "verify header checksum" in "settings" tab.
4 -- In the "extract" tab, click on "..." and select "update.app" in the previously "update.zip" decompressed folder.
5 -- Files from "update.app" should now be listed. Find "ramdisk" and right click on it. Choose "extract" and you will be able to save the file wherever you want. Copy this file on your phone.
6 -- On your phone: Go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. Grant permission to the manager to access your storage in phone settings > applications.
7 -- Run Magisk Manager, it will ask you if you want to install the zip. Select "Yes". It will now ask if you want to flash the zip or to patch a boot image, choose this last one. Point to the ramdisk img you previously copied on your phone. Magisk manager will now patch it and create a new "patched_boot.img" file. Copy this on your computer.
8 -- On your computer: Open a command prompt where you copied "patched_boot.img". Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_boot.img
fastboot reboot
9 -- Your phone will now reboot and be rooted. To unroot, repeat the process (8) with your stock ramdisk (the one extracted with Huawei Update Extractor)
Easy method
If your build is FRD-L09C432B521, FRD-L02C432B521, FRD-L04C567B520 or FRD-L09C432B562, you can use these already patched ramdisk.img.
patched_RAMDISKL09B521.img
stock_RAMDISKL09B521.img
patched_RAMDISKL02B521.img thanks to @Sharath007for the file
patched_RAMDISKL04B520.img thanks to @macbuggo for the file
stock_RAMDISKL04B520.img thanks to @macbuggo for the file
patched_RAMDISKL09B562.img thanks to @topscorer for the file
stock_RAMDISKL09B562.img thanks to @topscorer for the file
On your computer: Open a command prompt where you downloaded "patched_RAMDISKL09B521.img" (or L02/L04 ramdisk) .
Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_RAMDISKLXXBXXX.img (the exact name depends of the ramdisk you downloaded)
fastboot reboot
Your phone will now reboot
Go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it.
You now got root. To unroot, repeat the process with stock ramdisk.
Worked in the first attempt.. Safety net passes..
Sharath007 said:
Worked in the first attempt.. Safety net passes..
Click to expand...
Click to collapse
Did you do this on L09? Otherwise, could you share the patched ramdisk so I can add it in OP?
stephtban said:
Did you do this on L09? Otherwise, could you share the patched ramdisk so I can add it in OP?
Click to expand...
Click to collapse
Thanks for your guide. I did it on my FRD-L02 Variant.
FRD_L02_patched_boot
Sharath007 said:
Thanks for your guide. I did it on my FRD-L02 Variant.
FRD_L02_patched_boot
Click to expand...
Click to collapse
Thanks! I added your ramdisk to OP. Do you still have unpatched version of it for easy unrooting?
delete
PremiumBlaze said:
Can't guys flash Magisk using twrp? It worked for me in android oreo.
Click to expand...
Click to collapse
You can indeed use twrp but as it is not completely functional yet, some people don't use it. Besides, Open Kirin suggest to flash their rom with fastboot so it limits the interest of having twrp.
stephtban said:
DISCLAIMER: I will not be responsible of any issues you could face following this how-to. You do it at your own risk!
Here is a guide to root Honor 8 B521 Oreo. I did this on FRD-L09C432B521. Even if i think the "easy method" should work with other iteration of the phone (L02, L19, ...), I am not sure ramdisk is the same for all so test it if you feel lucky and please report if it works or not.
Requirements:
- Honor 8 running Oreo
- Unlocked Bootloader
- adb and fastboot installed on your computer (https://forum.xda-developers.com/android/software-hacking/alpha-adb-fastboot-installer-windows-t3637255 (Hit the thanks button)
Long method: (should work for all honor 8)
1 -- Visit http://pro-teammt.ru/firmware-database/ and search your exact build (FRD-L09C432B521 for me). If you have several phones listed for your build, click the name of the build on the left. This will open an xml file on the first line of which you will see the exact model it is for.
2 -- Once you know which firmware is yours, click on "filelist". This will list the files for this build and theirs url. Copy the link pointing to "update.zip" (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3109/g1699/v159456/f1/full/update.zip for me). Decompress it wherever you want.
3 -- Download and run Huawei Update Extractor (Hit the thanks button) . Untick "verify header checksum" in "settings" tab.
4 -- In the "extract" tab, click on "..." and select "update.app" in the previously "update.zip" decompressed folder.
5 -- Files from "update.app" should now be listed. Find "ramdisk" and right click on it. Choose "extract" and you will be able to save the file wherever you want. Copy this file on your phone.
6 -- On your phone: Go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. Grant permission to the manager to access your storage in phone settings > applications.
7 -- Run Magisk Manager, it will ask you if you want to install the zip. Select "Yes". It will now ask if you want to flash the zip or to patch a boot image, choose this last one. Point to the ramdisk img you previously copied on your phone. Magisk manager will now patch it and create a new "patched_boot.img" file. Copy this on your computer.
8 -- On your computer: Open a command prompt where you copied "patched_boot.img". Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_boot.img
fastboot reboot
9 -- Your phone will now reboot and be rooted. To unroot, repeat the process (8) with your stock ramdisk (the one extracted with Huawei Update Extractor)
Easy method
If your build is FRD-L09C432B521 or FRD-L02C432B521, you can use these already patched ramdisk.img.
patched_RAMDISKL09B521.img
stock_RAMDISKL09B521.img
patched_RAMDISKL02B521.img thanks to @Sharath007for the file
On your computer: Open a command prompt where you downloaded "patched_RAMDISKL09B521.img" (or L02 ramdisk) .
Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_RAMDISKL09B521.img OR fastboot flash ramdisk patched_RAMDISKL02B521.img
fastboot reboot
Your phone will now reboot and be rooted
To unroot, repeat the process with stock ramdisk.
Click to expand...
Click to collapse
Thanks! work perfectly
freewind29 said:
Thanks! work perfectly
Click to expand...
Click to collapse
Don't quote entire op please.
Did not work on my phone (L09C432) with the "easy way".
Flashed patched ramdisk, no root, but at least still running.
daFlox said:
Did not work on my phone (L09C432) with the "easy way".
Flashed patched ramdisk, no root, but at least still running.
Click to expand...
Click to collapse
Sorry, I forgot a step. After you flashed the patched ramdisk, go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. This should work then. Please tell me if it helped.
OP edited with this new step.
Worked great here for FRD-04, one thing to add
You may have to restart your phone to be able to see the patched file via MTP in order to copy it to your PC.
macbuggo said:
Worked great here for FRD-04, one thing to add
You may have to restart your phone to be able to see the patched file via MTP in order to copy it to your PC.
Click to expand...
Click to collapse
Happy this works. Could you share the stock ramdisk and the patched ramdisk so I can add it in OP.
stephtban said:
Sorry, I forgot a step. After you flashed the patched ramdisk, go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. This should work then. Please tell me if it helped.
OP edited with this new step.
Click to expand...
Click to collapse
Ahhh, okay!
Will try it this evening and report tomorrow.
daFlox said:
Will try it this evening and report tomorrow.
Click to expand...
Click to collapse
Works, thanks a lot!! (additional thanks in the original post )
stephtban said:
Happy this works. Could you share the stock ramdisk and the patched ramdisk so I can add it in OP.
Click to expand...
Click to collapse
I couldn't upload to XDA directly due to 8MB limit unfortunately, here it is if you want to put it up on your google drive or something
http://s000.tinyupload.com/index.php?file_id=10562650897614852938
This is a patched image of FRD-04C567 8.0.0.520 with Magisk 17.1
macbuggo said:
I couldn't upload to XDA directly due to 8MB limit unfortunately, here it is if you want to put it up on your google drive or something
http://s000.tinyupload.com/index.php?file_id=10562650897614852938
This is a patched image of FRD-04C567 8.0.0.520 with Magisk 17.1
Click to expand...
Click to collapse
Thanks. File and credit added to OP. Do you still have stock ramdisk for easy unrooting?
Tinyupload appears to be down, these links will last for 30 days
FRD-L04C567 8.0.0.520 ramdisk patched Magisk 17.1
https://ufile.io/nsa1h
Stock L04 520 ramdisk
https://ufile.io/34eq5
macbuggo said:
Tinyupload appears to be down, these links will last for 30 days
FRD-L04C567 8.0.0.520 ramdisk patched Magisk 17.1
https://ufile.io/nsa1h
Stock L04 520 ramdisk
https://ufile.io/34eq5
Click to expand...
Click to collapse
File added. Thx.
Hallo! Is it possible to root my FRD-L09 Honor 8 Oreo this way too? And after then can I flash/install a Stock Version with Emui 5 Android 7 Nougat and then un-root again? I need my device unrooted, because of SkyGo App (Germany) doesnt work with rootet Devices ...
If theres another way to downgrade without these operations, please let me know and maybe show me the steps for that?! Thank you so much!