Hello everyone, today I made a bull****, let's start from the beginning, my K10 2017 M250n had Android Oreo and I had come to know the exploit LGLAF, I tried, and did not work because I discovered that the flaw was patched on Android Oreo but I had the idea to downgrade to Nougat, after hours of problems due to drivers I can flashare nougat with LG UP in Download Mode, after doing the Downgrade, with the Dual-Boot to Linux on PC I used LGLAF on Linux, I made a backup of the LAF partition, I have the IMG file, a backup of the recovery, always an IMG I created, I did the wipe, I restarted and I tried to boot in fastboot, it does not boot, I tried to start in Download Mode, it does not work, all this to try to unlock the BootLoader, flash the TWRP and root.
Now how do I update and report the Download Mode?
I'm stuck without Fastboot, without Download Mode and with Android Nougat.
http://www.mediafire.com/file/y0d8sj4od5j3a34/laf.img/file
http://www.mediafire.com/file/179cr1b1y2d62cy/recovery.img/file
But you can boot it normally, I guess. Then hopefully Oreo ota update fixes it...
No, I can not find the updates anymore
XRed_CubeX said:
No, I can not find the updates anymore
Click to expand...
Click to collapse
i suggest that you try to update your phone via lg up by downloading the kdz of your exact phone model and without booting into download mode just by booting normal and i hope it solved
no warranty No promises... and no responsibility i take
abdoh01 said:
i suggest that you try to update your phone via lg up by downloading the kdz of your exact phone model and without booting into download mode just by booting normal and i hope it solved
no warranty No promises... and no responsibility i take
Click to expand...
Click to collapse
I tried and does not work, simply before Flash restarts you downloading and mode flash but I'm unloaded mode.
XRed_CubeX said:
No, I can not find the updates anymore
Click to expand...
Click to collapse
And you have done the factory reset? Then maybe laf is needed for the fota too??
At the end is the latest fota update, but no idea if it can be used similar way as before. [***]
https://forum.xda-developers.com/showpost.php?p=59103556&postcount=326
Now it probably should be named as dlpkgfile and placed in /data/fota/ or /cache/fota/ if smaller ...
But how to put it there, IDK... Also LGUP has some FOTA mode but haven't tested it.
LGM250nAT-V20b-EUR-XX-AUG-13-2018+0_fota.up
https://mega.nz/#!WpkERCgK!QiqndSPXG2aaaq7jqoG27IyBvhfd16bh6G2gNs7UoeA
edit: [***] hiddenmenu opens by calling *#546368#*250# and there you'll find that package select
mentioned in the first link. File in /storage/emulated/0/SoftwareUpdate/ shows but I don't want to update yet...
:good:
CXZa said:
And you have done the factory reset? Then maybe laf is needed for the fota too??
At the end is the latest fota update, but no idea if it can be used similar way as before. [***]
https://forum.xda-developers.com/showpost.php?p=59103556&postcount=326
Now it probably should be named as dlpkgfile and placed in /data/fota/ or /cache/fota/ if smaller ...
But how to put it there, IDK... Also LGUP has some FOTA mode but haven't tested it.
LGM250nAT-V20b-EUR-XX-AUG-13-2018+0_fota.up
https://mega.nz/#!WpkERCgK!QiqndSPXG2aaaq7jqoG27IyBvhfd16bh6G2gNs7UoeA
edit: [***] hiddenmenu opens by calling *#546368#*250# and there you'll find that package select
mentioned in the first link. File in /storage/emulated/0/SoftwareUpdate/ shows but I don't want to update yet...
:good:
Click to expand...
Click to collapse
Error RESULT_NOT_EXECUTED
XRed_CubeX said:
Error RESULT_NOT_EXECUTED
Click to expand...
Click to collapse
Pity... it then maybe use laf - although there is also fota tools on
the recovery. What about LGUP, is there fota option or have I dreamed it.
CXZa said:
Pity... it then maybe use laf - although there is also fota tools on
the recovery. What about LGUP, is there fota option or have I dreamed it.
Click to expand...
Click to collapse
The problem that I have formatted laf,i cant boot on download mode, how can I reboot in recovery mode?
XRed_CubeX said:
The problem that I have formatted laf,i cant boot on download mode, how can I reboot in recovery mode?
Click to expand...
Click to collapse
Some fota tools are there in the sbin, but I don't know how can they be activated.
Fota file must be in some default folder and recovery maybe booted having a
command somewhere....
You can reboot to recovery using adb, or in terminal "reboot recovery"
or "setprop sys.powerctl reboot,recovery"
I was thinking that maybe LGUP changes the mode like it does
before flashing kdz files. If in normal mode, that is.
And if it uses recovery mode with fota then it might work.
Just hoping not knowing...
CXZa said:
Some fota tools are there in the sbin, but I don't know how can they be activated.
Fota file must be in some default folder and recovery maybe booted having a
command somewhere....
You can reboot to recovery using adb, or in terminal "reboot recovery"
or "setprop sys.powerctl reboot,recovery"
I was thinking that maybe LGUP changes the mode like it does
before flashing kdz files. If in normal mode, that is.
And if it uses recovery mode with fota then it might work.
Just hoping not knowing...
Click to expand...
Click to collapse
The recovery mode says No Command.
XRed_CubeX said:
The recovery mode says No Command.
Click to expand...
Click to collapse
Press power and then vol up shortly. Same time that is.
CXZa said:
Press power and then vol up shortly. Same time that is.
Click to expand...
Click to collapse
When I try to do FOTA upgrade on LG UP it gives me the error "Error: 0x2000, Fail! MTP is not Running" but when in fact the device to recognize the port MUST be in MTP and I in MTP mode I have it put.
XRed_CubeX said:
When I try to do FOTA upgrade on LG UP it gives me the error "Error: 0x2000, Fail! MTP is not Running" but when in fact the device to recognize the port MUST be in MTP and I in MTP mode I have it put.
Click to expand...
Click to collapse
IDK. Are you using LGUP having a patched exe and the dll?
Is the dll our own? Does it matter if it's own or not? IDK.
Patching it is instructed somewhere...
edit: patching not needed as fota mode shows already.
edit22: have you the WPDAPI.exe in the LGUP\main\Common dir?
the LGUP_Common.dll might need it...
There is still that other way, using that "Activity Launcher" app,
or "am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart"
And what about a newer tool, LGBridge? I read somewhere at LGlaf github
that its or SupportTool's protocol data looks different compared to LGlaf.
https://github.com/Lekensteyn/lglaf/issues/7
What else is different...
CXZa said:
IDK. Are you using LGUP having a patched exe and the dll?
Is the dll our own? Does it matter if it's own or not? IDK.
Patching it is instructed somewhere...
edit: patching not needed as fota mode shows already.
edit22: have you the WPDAPI.exe in the LGUP\main\Common dir?
the LGUP_Common.dll might need it...
There is still that other way, using that "Activity Launcher" app,
or "am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart"
And what about a newer tool, LGBridge? I read somewhere at LGlaf github
that its or SupportTool's protocol data looks different compared to LGlaf.
https://github.com/Lekensteyn/lglaf/issues/7
What else is different...
Click to expand...
Click to collapse
How to get WPDAPI?
XRed_CubeX said:
How to get WPDAPI?
Click to expand...
Click to collapse
It's many times included in those hacked version packages.
I guess it was included with dll needed, but don't know for sure.
Here it's needed
https://forum.xda-developers.com/showpost.php?p=75677301&postcount=6
I don't when it will be needed in this long thread.
https://forum.xda-developers.com/lg-g5/how-to/unlocking-lgup-features-fun-profit-t3634650
Maybe it's said somewhere in it. The exe is mentioned in the dll though...
From where? See the attachment. The UI_Config.lgl in it gives more options.
No hacking and cracking needed. But is a hacked version better, IDK...
CXZa said:
It's many times included in those hacked version packages.
I guess it was included with dll needed, but don't know for sure.
Here it's needed
https://forum.xda-developers.com/showpost.php?p=75677301&postcount=6
I don't when it will be needed in this long thread.
https://forum.xda-developers.com/lg-g5/how-to/unlocking-lgup-features-fun-profit-t3634650
Maybe it's said somewhere in it. The exe is mentioned in the dll though...
From where? See the attachment. The UI_Config.lgl in it gives more options.
No hacking and cracking needed. But is a hacked version better, IDK...
Click to expand...
Click to collapse
Always the same error, but also the method of DmcEzUpdateStart remains with the words "FOTA EASY UPDATE" and then crash.
No solution?
There is a scatter file so you can flash it from SP Flash Tools??
XRed_CubeX said:
There is a scatter file so you can flash it from SP Flash Tools??
Click to expand...
Click to collapse
LG has made so much changes that I think that it doesn't work as mtk device anymore.
Anyway the MTK driver package IDs probably have to be changed... at least.
With LG drivers installed, the SP Flash Tool readback started, a text about
LG connection was shown, but it just failed - miserably...
If you uninstall the lg drivers and maybe mtk too. And then connect it
(without the battery?), you might see that it shows itself as MTK preloader
for a second or two. With lg drivers it shows as something else, I think...
When doing readback from a normal mtk device I think it is the preloader
which is used. When downloading a firmware, I don't remember does it
switch to another state that is used... serial or whatever the text says
in SP Flash Tool, but was it with or without the preloader text... ??? IDR...
Related
Hy nexus friends,
I need help from someone with a 791F 32GB. I dont know if a 790 or a 16gb version is identical.
It would be great if someone with a rooted device can make a backup for me of the bootloader bin files.
aboot, sbl1, rpm, tz, sdi, sbl1b, tzb, rpmb, abootb, misc, laf, persist.
I flashed the hammerhead bootloader and stuck at 9008 mode.
It will be ver great if someone could help me.
Some partition apps could make a backup or with the dd command.
If i fet a solution, i would post it here. At the moment i had the device and the tools that i flashed for test a nexus 5 sbl. So write is possible.
Thanks for help guys
Where can I see if my phone is 791F?
i have the US Nexus 5X 32GB. Tell me what to do and I'll get you what you need.
tacofromhell said:
Where can I see if my phone is 791F?
Click to expand...
Click to collapse
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok. Just rebooted into bootloader and under "Variant" it says LGH791 but no F, sorry
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
konsolen said:
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
Click to expand...
Click to collapse
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
nate0 said:
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
Click to expand...
Click to collapse
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Apayah said:
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Click to expand...
Click to collapse
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
nate0 said:
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
Click to expand...
Click to collapse
I see boardiag for n5 , please don't give up ?.
And i see blank flash file for N6
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
konsolen said:
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
Click to expand...
Click to collapse
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Apayah said:
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Click to expand...
Click to collapse
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
nate0 said:
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
Click to expand...
Click to collapse
Yes it same , i got that to.
So what is blank flash? on N6 thread .
链接：https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg 引脚：g5cg
Hi guys,
for the last months I was using LineageOs, but since they dropped development for our device I wanted to get rid of it.
I tried to get AOSP running but failed. Next I flashed a stock kdz file in Download Mode using LGUP and it worked,
I was back to stock. I tried to install AOSP through TWRP but failed again and eventually ended up doing a hard reset.
This temporarily bricked the device because now the stock android booted and Android Device Protection (FRP) was
active and didn't let me log in. Desperate to find a solution I flashed random kdz/tot files for the device that I found on
the Internet until one finally worked (LGH815 EU Nougat 7.0 BySezerSimsek), the FRP thing was gone. Then I tried to at
least get back to stock again, but when I tried to flash the stock kdz file LGUP aborts at 25% with Error Code 0x2000.
Every time I start the phone now, it goes directly in this firmware update/download mode.
The device shows up as "LGE AndroidNet USB Serial Port" In Windows Device Manager
In Download mode it says "633A B92 Official" on the display
I already tried:
Different dll files for LGUP
Using LG Flash Tool 2014 instead
Putting dump file on SD card
Should I put it in 9008 mode and work with QFIL or what am I supposed to do now?
Thank you.
I'm still able to get into fastboot mode btw. But I'm going to wait for replies here
before I make things worse. If that's even possible at this point. :silly:
h4yabu5a said:
I'm still able to get into fastboot mode btw. But I'm going to wait for replies here
before I make things worse. If that's even possible at this point. :silly:
Click to expand...
Click to collapse
:highfive:<-
jason_l367 said:
:highfive:<-
Click to expand...
Click to collapse
My phone is alive again, thanks Jason:laugh:
Just a short recap what I've done now in case it helps someone with the same problem, the full instructions
are in Jasons link.
I used the KDZ and TOT Extractor to extract the LGUP8994.dll file out of a stock Marshmallow v20p KDZ.
I renamed the dll to LGUP_8994.dll and moved it to C:\..\LG Electronics\LGUP\model\8994, overriding the
existing file. Now LGUP was able to flash the v20p KDZ without the 0x2000 Error.
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
jetzecazemier said:
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
Click to expand...
Click to collapse
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
mrmazak said:
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
Click to expand...
Click to collapse
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error) I am frp unlocked by the way.
jetzecazemier said:
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
mrmazak said:
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
jetzecazemier said:
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
Click to expand...
Click to collapse
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
mrmazak said:
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
Click to expand...
Click to collapse
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
jetzecazemier said:
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
Click to expand...
Click to collapse
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
Alright, I'll try that before I have a look at that thread
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
jetzecazemier said:
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
Click to expand...
Click to collapse
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
mrmazak said:
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
Click to expand...
Click to collapse
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
jetzecazemier said:
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
Click to expand...
Click to collapse
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
mrmazak said:
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
Click to expand...
Click to collapse
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
jetzecazemier said:
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
Click to expand...
Click to collapse
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
mrmazak said:
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
Click to expand...
Click to collapse
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
jetzecazemier said:
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
Click to expand...
Click to collapse
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
mrmazak said:
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
Click to expand...
Click to collapse
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
jetzecazemier said:
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
Click to expand...
Click to collapse
Yes.
The lazy tool has recovery with encryption working
I got it working on EMUI8 but I decided to flash the aosp rom cuz i prefer stock android. Can't seem to get twrp to install tho. I keep getting "1 was unexpected at this time"
Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.
HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.
Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?
Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!
@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now
Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader
I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!
Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?
Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.
Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them
hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much
thanks so much i was able to put my phone back to life. i had almost given up.
smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.
damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.
Alexenferman is not responsible for any damages or bricks made to your device. Please do some research if you have any concerns about rooting, its features and downsides. You are choosing to make these modifications, you should blame yourself for any mistakes you make.
Rooting may require a factory reset, please backup your data. Rooting will void your device warrany. By rooting your device, you will not be able to install OTA updates on your phone.
US carrier specific devices such as Verizon and Sprint might not be bootloader unlockable, therefore, not rootable.[/B]
You will need:
Platform Tools (Download from here)
Motorola Drivers
Windows or Linux PC
Bootloader Unlocked Moto E 2020
Your phone must be bootloader unlocked. Rooting your phone and not unlocking the bootloader will result in a soft brick.
Download the latest Magisk Manager APK from Github: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.0/MagiskManager-v8.0.0.apk
Install the APK file. Make sure to enable "Unknown Sources" in the Settings app
Patching the boot image
To retrieve the boot image in order to patch it, you will need to download the stock ROM for your specific variant.
Download the ROM from your variant from here: https://mirrors.lolinet.com/firmware/moto/ginna/official/
To check which region is your device, go to Settings > About Phone > Software Channel.
After downloading, open the ROM zip file with an archive manager.
Extract the boot.img file only.
Transfer the boot.img file on your phone.
On your phone, open the Magisk app.
Select "Install" > "Install" > "Select and Patch a File"
Locate the boot image in the internal storage on your phone. Select the boot.img file.
Transfer the magisk_patched.img file on your computer.
Rooting the device
Boot the device into fastboot mode by holding the [Volume Down] and [Power] buttons.
Connect your phone to your PC.
On your PC, open a fastboot console window.
Type:
Code:
fastboot devices
Your phone serial number should be displayed along with the word "fastboot" or "device" in the console.
Now, type the following commands:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Replace patched_boot.img with the path to your boot image we patched previously.
To reboot the device, type:
Code:
fastboot reboot
Once the device rebooted, open the Magisk app.
If you see the "Magisk is installed" message, you have successfully rooted your device!
You are done!
To view instructions with images, follow these instructions: https://www.alexenferman.com/articles/MotoE2020/root-moto-e-2020-magisk
I can confirm this works, I was about to give up on root or TWRP until I saw this. I'm now rooted, but I still can't find a download link for the latest TWRP for the Ginna model.
Hypercore said:
I can confirm this works, I was about to give up on root or TWRP until I saw this. I'm now rooted, but I still can't find a download link for the latest TWRP for the Ginna model.
Click to expand...
Click to collapse
Me neither, can anyone provide a TWRP for ginna?
I eventually found it after a ton of digging. I've uploaded it to my drive to assure the link stays active for anyone else who may need it.
For peace of mind, here's the VirusTotal scan HERE.
And here is the link to twrp-3.4.0-10_0-ginna HERE.
Hypercore said:
I eventually found it after a ton of digging. I've uploaded it to my drive to assure the link stays active for anyone else who may need it.
For peace of mind, here's the VirusTotal scan HERE.
And here is the link to twrp-3.4.0-10_0-ginna HERE.
Click to expand...
Click to collapse
Confirmed working. Tyvm!
Before I brick my phone. Can anyone confirm if the Tracphone version XT2052DL is rootable?
I'd like to know, too. Can we root our Tracfone XT2025DLs? Anyone successful?
dragonfire0501 said:
Before I brick my phone. Can anyone confirm if the Tracphone version XT2052DL is rootable?
Click to expand...
Click to collapse
Ranthalion75 said:
I'd like to know, too. Can we root our Tracfone XT2025DLs? Anyone successful?
Click to expand...
Click to collapse
I have one too and I've tried to unlock the bootloader however Motorola's website says the bootloader for this phone is not unlockable. It seems like this is what's preventing me from being able to install a different firmware like the stock one or root the device.
I do not know if there is any sort of workaround for this
For some reason on a Moto E, after rescuing using the Moto rescue assistant and then using
you guys can also use OFox Recovery and swipe magisk to root
Thank you. I used this guide to root my Moto E
QPGS30.82-135-2_Root.img
This method works well for QPGS30.82-135-2, but I just attempted it with QPGS30.82-135-9 and unfortunately the Magisk patched boot image will not work. I tried it 3 times, re-patching boot image each time. I suppose Motorola updated something in android to block this?
i can't get this to work at all, i cannot find a matching stock firmware being qpg30.82-135, there's no extra S and nothing else after the 135, got this phone from my motorola insiders rewards and now it's bootlooping after trying the 135-2 patched image
Has anyone been able to root and hopefully install a custom recovery on the lastest update? Mine is QPGS30.82-135-14, and so far I've only been able to get orangefox to boot but couldn't get it to decrypt my storage or install magisk. I tried twrp first, but to no avail, touch screen still doesn't work on it, so now I'm asking on a few different threads for this phone lol. Any help would be great!
Do you know of an updated method to get it to flash correctly? I was able to boot into ofox, but couldn't get it to properly flash. Ended up stuck on a screen that said my phone was unlocked and couldn't be trusted and that it'll reboot in 5 seconds. I don't know much about ofox either, been using twrp for years lol, it looks too different. Anyhow, any help would be appreciate much!
ace120ms said:
you guys can also use OFox Recovery and swipe magisk to root
Click to expand...
Click to collapse
You have to fastboot boot it anyway I don't have this phone anymore so idk
bouyakasha said:
This method works well for QPGS30.82-135-2, but I just attempted it with QPGS30.82-135-9 and unfortunately the Magisk patched boot image will not work. I tried it 3 times, re-patching boot image each time. I suppose Motorola updated something in android to block this?
Click to expand...
Click to collapse
I have the same problem with QPGS30.82-135-9. I can't get it to boot after Magisk patched boot image.