Database Users

[Solved]Lava Pixel V1 Stock Recovery Marshmallow [white variant] Needed. Help Please!

Solution Can Be Found HERE.
Thanks for Viewing.
I want to take a Backup of Stock Recovery , But failed in all attempts.
So please can someone give me the required Stock Recovery Image(.img) file.
Details of my Mobile Phone:
Make:Lava
Modelixel V1
Android Version: 6.0(Marshmallow) {as per setting>about phone}
Android security patch level:1 August 2016 {as per setting>about phone}
Build number:Lava_PixelV1_S040_20160801 {as per setting>about phone}
[If more Details required, Please do ask]
Why I need Backup of Stock Recovery?
So that I can Install TWRP , and use Stock Recovery to install OTA Updates.
Which methods I tried?
I tried almost all methods except those which replaces Stock Recovery.
Since my aim is to take Backup of Stock Recovery I did not tried those.
Which methods I tried without replacing Stock Recovery?
1. Rooting the Phone without replacing Stock Recovery.
a. Using android version (.apk)
Example: iRoot , Kingo Root , King Root.
All of the above Failed , even after trying for several attempts for each APK.
b. Using PC version [Did not use the one's which replace Stock Recovery]
Example : iRoot , [can not remember other PC version right now, i'll update when i can]
The above Failed , even after trying for several attempts.
After Rooting there is a method to Extract Stock Recovery from Recovery partition , But did not bothered since my phone was not getting Rooted.
2. Soft Booting a Custom Recovery.
Example Commands:
1. fastboot boot recovery recovery.img
2. fastboot boot recovery.img
3. fastboot -c "your_default_command_line lge.kcal=0|0|0|x" boot customrecovery.img [I have misplaced that command line, cannot find, may update later]
But as always Failed. :crying:
I was getting some similar error:
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.596s
Note : I am new to This stuff and to Android OS. Please Understand.
I also know that there is a method to extract Stock Recovery from Stock ROM , But I do not Know how to do that.
Note to Moderator : I am new to this Forum, so if I made any mistakes or broke rule's please do correct me.
Please do not delete the post or ban me , I am ready to correct myself.
So please Kindly Help me.
Thanking You.
Dark❶.

So you have unrooted Pixel V1 and want to make backup of stock recovery...CORRECT? If yes..I can help

Suraj Pandey said:
So you have unrooted Pixel V1 and want to make backup of stock recovery...CORRECT? If yes..I can help
Click to expand...
Click to collapse
Yes ! Sir.
Sorry for late Reply , I had lost hope! , & did not see this post. :angel:
Thank you for the reply. :good:
waiting for further Instruction.
Thank You.

Dark❶ said:
Yes ! Sir.
Sorry for late Reply , I had lost hope! , & did not see this post. :angel:
Thank you for the reply. :good:
waiting for further Instruction.
Thank You.
Click to expand...
Click to collapse
You can get your stock recovery from stock ROM extract and you will see a recovery.IMG that it is
https://docs.google.com/uc?id=0BynLDiCMvBUCQUdFVXBMQzhaaW8
But that will be useless
OTA cannot be installed unless you have a pure stock ROM
What I suggest is install TWRP and let it replace the stock recovery. Reason:- You can install OTA using TWRP

Suraj Pandey said:
You can get your stock recovery from stock ROM extract and you will see a recovery.IMG that it is
https://docs.google.com/uc?id=0BynLDiCMvBUCQUdFVXBMQzhaaW8
But that will be useless
OTA cannot be installed unless you have a pure stock ROM
What I suggest is install TWRP and let it replace the stock recovery. Reason:- You can install OTA using TWRP
Click to expand...
Click to collapse
Sir,
Thanks for the Link, I already had that ZIP file as a backup if I messed any thing, and I have successfully extracted recovery.img.
BUT as you said "that will be useless" as "OTA cannot be installed unless you have a pure stock ROM", I am deducing that for that recovery it needs same stock ROM.(Just tell me if I m right or wrong of this assumption).
Now, "You can install OTA using TWRP" , I read on this forum that OTA cannot be installed using TWRP due to some checks in OTA unless those checks R removed.(Reff).
If this is not the case Please tell me the procedure to install OTA using TWRP.
Thanking You.
EDIT 1: I am going to root my phone after my Internal Test which will end next week.
Edit 2: If the latest TWRP(Reff1&Reff2) has the ability to install OTA, then I guess my problem is solved.

Dark❶ said:
Sir,
Thanks for the Link, I already had that ZIP file as a backup if I messed any thing, and I have successfully extracted recovery.img.
BUT as you said "that will be useless" as "OTA cannot be installed unless you have a pure stock ROM", I am deducing that for that recovery it needs same stock ROM.(Just tell me if I m right or wrong of this assumption).
Now, "You can install OTA using TWRP" , I read on this forum that OTA cannot be installed using TWRP due to some checks in OTA unless those checks R removed.(Reff).
If this is not the case Please tell me the procedure to install OTA using TWRP.
Thanking You.
EDIT 1: I am going to root my phone after my Internal Test which will end next week.
Edit 2: If the latest TWRP(Reff1&Reff2) has the ability to install OTA, then I guess my problem is solved.
Click to expand...
Click to collapse
Yeah u r right- recovery gets updated with an OTA update.(That's why your assumption is right)
For installing OTA through TWRP you will have to remove the checks..i.e get prop lines from updater script in the OTA package..(Don't worry.. there is a TWRP-ready package available - to install through TWRP)
But these packages will only work if u don't change system files--mainly build.prop and system apps(DON'T UNINSTALL THEM )
THAT'S IT
BUT SPECIFY ME THE REASON FOR TWRP INSTALLATION- ROM or ROOT

Suraj Pandey said:
Yeah u r right- recovery gets updated with an OTA update.(That's why your assumption is right)
For installing OTA through TWRP you will have to remove the checks..i.e get prop lines from updater script in the OTA package..(Don't worry.. there is a TWRP-ready package available - to install through TWRP)
But these packages will only work if u don't change system files--mainly build.prop and system apps(DON'T UNINSTALL THEM )
THAT'S IT
BUT SPECIFY ME THE REASON FOR TWRP INSTALLATION- ROM or ROOT
Click to expand...
Click to collapse
Sir, Thanks for your kind help and answering my queries.
let me put my Question in point form.
[1]Yesterday I have Successfully Flashed TWRP and then Installed SuperSU v2.78 (systemless).
but , Installing SuperSU v2.78 (systemless), does it replace any /system files? such that OTA can not be installed?
(ie. supersu is not Installed on /system, as u may know)
[2]I have not modified build.prop and UNINSTALL any system apps.
but i have renamed two files in /system/media/ui/ (so that to remove camera trigger sound).
but my guess is ,if i restored the names of the files then mount /system as read-only and then install OTA , will it not cause any Problem?
[3]How can I ,"For installing OTA through TWRP you will have to remove the checks..i.e get prop lines from updater script in the OTA package.", do this?(Teach me or point me to the right direction)
[4]Where can I get those? :"Don't worry.. there is a TWRP-ready package available - to install through TWRP"?
Since @MSF Jarvis discontinued this thread.
And @MSF Jarvis , It was very Helpful, I wish u could continue it.
[5]Can I get latest recovery OR recovery.img from OTA?
Answer to your Question "BUT SPECIFY ME THE REASON FOR TWRP INSTALLATION- ROM or ROOT" is ROOT , which is already answered in (1), but my 1st objective was to take backup of stock ROM and then ROOT,but my guess is that can not be done.
Sorry for the long post and simple silly Question (since I m new to this stuff).
Thank You.

Dark❶ said:
Sir, Thanks for your kind help and answering my queries.
let me put my Question in point form.
[1]Yesterday I have Successfully Flashed TWRP and then Installed SuperSU v2.78 (systemless).
but , Installing SuperSU v2.78 (systemless), does it replace any /system files? such that OTA can not be installed?
(ie. supersu is not Installed on /system, as u may know)
[2]I have not modified build.prop and UNINSTALL any system apps.
but i have renamed two files in /system/media/ui/ (so that to remove camera trigger sound).
but my guess is ,if i restored the names of the files then mount /system as read-only and then install OTA , will it not cause any Problem?
[3]How can I ,"For installing OTA through TWRP you will have to remove the checks..i.e get prop lines from updater script in the OTA package.", do this?(Teach me or point me to the right direction)
[4]Where can I get those? :"Don't worry.. there is a TWRP-ready package available - to install through TWRP"?
Since @MSF Jarvis discontinued this thread.
And @MSF Jarvis , It was very Helpful, I wish u could continue it.
[5]Can I get latest recovery OR recovery.img from OTA?
Answer to your Question "BUT SPECIFY ME THE REASON FOR TWRP INSTALLATION- ROM or ROOT" is ROOT , which is already answered in (1), but my 1st objective was to take backup of stock ROM and then ROOT,but my guess is that can not be done.
Sorry for the long post and simple silly Question (since I m new to this stuff).
Thank You.
Click to expand...
Click to collapse
1. SuperSU by default is systemless, so just installing SuperSU won't break OTAs.
2. Renaming and remounting as RO won't fix OTAs. You'll need to use a customized OTA zip for this.
3. You can use my packages for this.
4. I have all the packages still saved on my system, I'll reupload all of them to Google Drive and have the thread reopened.
5. If you mean latest TWRP, then there will soon be an official app for that, but for now there's no option for a recovery OTA. If there are enough users needing it I may consider coming up with a solution.
Sent from my Pixel V1 using XDA Labs

Dark❶ said:
Sir, Thanks for your kind help and answering my queries.
let me put my Question in point form.
[1]Yesterday I have Successfully Flashed TWRP and then Installed SuperSU v2.78 (systemless).
but , Installing SuperSU v2.78 (systemless), does it replace any /system files? such that OTA can not be installed?
(ie. supersu is not Installed on /system, as u may know)
[2]I have not modified build.prop and UNINSTALL any system apps.
but i have renamed two files in /system/media/ui/ (so that to remove camera trigger sound).
but my guess is ,if i restored the names of the files then mount /system as read-only and then install OTA , will it not cause any Problem?
[3]How can I ,"For installing OTA through TWRP you will have to remove the checks..i.e get prop lines from updater script in the OTA package.", do this?(Teach me or point me to the right direction)
[4]Where can I get those? :"Don't worry.. there is a TWRP-ready package available - to install through TWRP"?
Since @MSF Jarvis discontinued this thread.
And @MSF Jarvis , It was very Helpful, I wish u could continue it.
[5]Can I get latest recovery OR recovery.img from OTA?
Answer to your Question "BUT SPECIFY ME THE REASON FOR TWRP INSTALLATION- ROM or ROOT" is ROOT , which is already answered in (1), but my 1st objective was to take backup of stock ROM and then ROOT,but my guess is that can not be done.
Sorry for the long post and simple silly Question (since I m new to this stuff).
Thank You.
Click to expand...
Click to collapse
Yeah sure I will continue. It he doesn't

MSF Jarvis said:
1. SuperSU by default is systemless, so just installing SuperSU won't break OTAs.
2. Renaming and remounting as RO won't fix OTAs. You'll need to use a customized OTA zip for this.
3. You can use my packages for this.
4. I have all the packages still saved on my system, I'll reupload all of them to Google Drive and have the thread reopened.
5. If you mean latest TWRP, then there will soon be an official app for that, but for now there's no option for a recovery OTA. If there are enough users needing it I may consider coming up with a solution.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Suraj Pandey said:
Yeah sure I will continue. It he doesn't
Click to expand...
Click to collapse
Thanks @Suraj Pandey & @MSF Jarvis ,
[1]My query is resolved.
[2]my guess i was not clear , what i meant was i renamed "xyz.ogg" to "xyz.ogg.BACKUP" in "/system/media/ui/", now assume i received October OTA update , since i want to install this OTA , i rename that .ogg file to "xyz.ogg" from "xyz.ogg.BACKUP".
Then mount the /system as read-only.
Assuming i edited the OTA with checks removed or got the edited OTA from you.
Reboot to TWRP and install edited OTA.
Now the Question is : Will the OTA install or Not or will it cause any problem?
[3]I meant was "I want to learn how to edit the OTA with checks removed" or point me in right direction.
[4] Thanks @MSF Jarvis for reopening the thread.
[5]I was not clear on this one, my fault. :fingers-crossed:
I meant update for stock recovery which come in OTA update.
And hence my corrected Question is : Can I get latest stock recovery OR recovery.img from latest OTA?
Thank you @MSF Jarvis & @Suraj Pandey
Edit 1: Please Do answer my [2]&[5] Question.
Edit 2:I just realized that I used "OTP" instead of "OTA" in some places. This is really embarrassing!!
So I edited "OTP" to "OTA".

Dark❶ said:
...
[2]my guess i was not clear , what i meant was i renamed "xyz.ogg" to "xyz.ogg.BACKUP" in "/system/media/ui/", now assume i received October OTA update , since i want to install this OTP , i rename that .ogg file to "xyz.ogg" from "xyz.ogg.BACKUP".
Then mount the /system as read-only.
Assuming i edited the OTP with checks removed or got the edited OTP from you.
Reboot to TWRP and install edited OTP.
Now the Question is : Will the OTP install or Not or will it cause any problem?
...
[5]I was not clear on this one, my fault. :fingers-crossed:
I meant update for stock recovery which come in OTA update.
And hence my corrected Question is : Can I get latest stock recovery OR recovery.img from latest OTA?
Click to expand...
Click to collapse
2. Yeah it should work out, audio files don't get frequent updates anyway
5. You automatically get updated if there's an update to the stock recovery, almost always there's no update tho.
Sent from my Pixel V1 using XDA Labs

Dark❶ said:
Thanks @Suraj Pandey & @MSF Jarvis ,
[1]My query is resolved.
[2]my guess i was not clear , what i meant was i renamed "xyz.ogg" to "xyz.ogg.BACKUP" in "/system/media/ui/", now assume i received October OTA update , since i want to install this OTP , i rename that .ogg file to "xyz.ogg" from "xyz.ogg.BACKUP".
Then mount the /system as read-only.
Assuming i edited the OTP with checks removed or got the edited OTP from you.
Reboot to TWRP and install edited OTP.
Now the Question is : Will the OTP install or Not or will it cause any problem?
[3]I meant was "I want to learn how to edit the OTP with checks removed" or point me in right direction.
[4] Thanks @MSF Jarvis for reopening the thread.
[5]I was not clear on this one, my fault. :fingers-crossed:
I meant update for stock recovery which come in OTA update.
And hence my corrected Question is : Can I get latest stock recovery OR recovery.img from latest OTA?
Thank you @MSF Jarvis & @Suraj Pandey
Edit 1: Please Do answer my [2]&[5] Question.
Click to expand...
Click to collapse
Answers
2. Yes. The OTA will be installed
5. No you cannot obtain recovery from the OTA package

MSF Jarvis said:
2. Yeah it should work out, audio files don't get frequent updates anyway
5. You automatically get updated if there's an update to the stock recovery, almost always there's no update tho.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
(2.) one was a relief.
Thank you @MSF Jarvis for your Kind Help.

Suraj Pandey said:
Answers
2. Yes. The OTA will be installed
5. No you cannot obtain recovery from the OTA package
Click to expand...
Click to collapse
Thanks for your Answers
Thank you very much @Suraj Pandey for your Kind Help. :good:

Dark❶ said:
Thanks for your Answers
Thank you very much @Suraj Pandey for your Kind Help. :good:
Click to expand...
Click to collapse
Always welcome...

Suraj Pandey said:
Always welcome...
Click to expand...
Click to collapse
Thank you Sir,
but just one more thing,(Sorry to trouble you or annoy you),
I really want to learn how to edit OTA Update and remove the checks.
since i do not have a sample OTA Update , I will wait for October OTA update and request you to teach me.
Thank You Once again @Suraj Pandey.

Dark❶ said:
Thank you Sir,
but just one more thing,(Sorry to trouble you or annoy you),
I really want to learn how to edit OTA Update and remove the checks.
since i do not have a sample OTA Update , I will wait for October OTA update and request you to teach me.
Thank You Once again @Suraj Pandey.
Click to expand...
Click to collapse
No Proficiency is required for that.
It's very easy
Just erase the getprop lines from Updater script
That's it

Dark❶ said:
Thank you Sir,
but just one more thing,(Sorry to trouble you or annoy you),
I really want to learn how to edit OTA Update and remove the checks.
since i do not have a sample OTA Update , I will wait for October OTA update and request you to teach me.
Click to expand...
Click to collapse
Remove all get prop lines and apply_patch_check lines. Basically, there's a comment at the end of the checks, that says "start making changes here", you need to wipe all lines till there, excluding the line that mounts /system . You can remove OEM partition mounting since we aren't using it anymore. These modded updates will ONLY flash on TWRP, since ZIPs are signed with a signature that gets invalidated by any edits.
Sent from my Pixel V1 using XDA Labs

Suraj Pandey said:
No Proficiency is required for that.
It's very easy
Just erase the getprop lines from Updater script
That's it
Click to expand...
Click to collapse
Ok Sir , I will let you know when I get October OTA Update and test it.
Thank you. :good:

MSF Jarvis said:
Remove all get prop lines and apply_patch_check lines. Basically, there's a comment at the end of the checks, that says "start making changes here", you need to wipe all lines till there, excluding the line that mounts /system . You can remove OEM partition mounting since we aren't using it anymore. These modded updates will ONLY flash on TWRP, since ZIPs are signed with a signature that gets invalidated by any edits.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Ok Sir ,
I will test this when I get October OTA Update.
I will let you know when it is done.
Thank you. :good:

[GUIDE][ROOT][UNIVERSAL] FORCE INSTALLING STOCK OTA UPDATES WITH SToCK RECOVERY

Since lollipop there is no manual update option in huawei updater and even the huawei stock recovery has no or less interface which has no adb sideload option. This became a crunch to flash the update which your friend got and which u dont.
This Method is Universal for all huawei devices
In order to apply ota update using this method , root access is a major requirement so be sure your device is rooted.
If u had twrp recovery , at first flash SuperSu package to root your device (Try systemless root only) .
After successfull root ,flash stock recovery from twrp and reboot system.
Step 1:
In my case b370 is the last ota i found for kiw-l22 which vsriram92 posted here . Thanks to him for posting the update before 99% users got their update :good:
Download the relevant update package (ota) which you need a relevant base package to install it on . Ex: b360 as base for b370 update
step 2:
just remember the path where u downloaded the package . Install Flashify from playstore or From Here
Select Zip file which is the third option in flashify .
step 3 :
Navigate to the path where u downloaded ota package select the update.zip (ota package).
flashify starts downloading the package to its path asks you for root access .
Grand Su permissions , Select Cwm recovery if flashify asks as the next option.
Now the phone reboots to recovery and starts flashing.
After the ota update , your device will be unrooted . so take a backup of your stock recovery by following below guide.
Enable Usb debugging and connect ur phone to pc.
navigate to adb folder and place twrp.img or recovery.img in adb folder ,open command window from the same folder and type
Code:
adb reboot bootloader
Now type
Code:
fastboot boot recovery.img
or what_ever_its_name.img
now it temporarily boots twrp , take a backup of your stock recovery and then flash twrp for permanent install and then reroot ur device.
Happy flashing :laugh::good:​

it gets zip signature verification failed....the method is similar to installing the zip file directly from the recovery but that doesn't work unless zip signature is verified

rbtrai said:
it gets zip signature verification failed....the method is similar to installing the zip file directly from the recovery but that doesn't work unless zip signature is verified
Click to expand...
Click to collapse
You might have installed a zip which is not stock ota update . i haven't posted this without trying . I installed b370 with this method and made this live here .

i downloaded from the link provided above which vsriram92 posted...

rbtrai said:
i downloaded from the link provided above which vsriram92 posted...
Click to expand...
Click to collapse
Were you in b360 before doing this ?

Thanks again Gopi. Another great contribution.

vsriram92 said:
Were you in b360 before doing this ?
Click to expand...
Click to collapse
yes ofcourse

This only for rooted phone ?
I'm having honor 4x unroot and I don't know how to install the ota file. Is there any way for upgrading a phone without root option and in my phone there is no local update option

Ajith san said:
This only for rooted phone ?
I'm having honor 4x unroot and I don't know how to install the ota file. Is there any way for upgrading a phone without root option and in my phone there is no local update option
Click to expand...
Click to collapse
Nope. It was there in EMUI 3 previously. Now, we can't unless it has only update.app.

so b370 is only for the ones who gave root access to their phones?

Like your contribution. Perfectly updated to B370.

rajibie said:
Like your contribution. Perfectly updated to B370.
Click to expand...
Click to collapse
great

Hello together, I tried flashing the B360 update for my L21 with this method but unfortunately I did not succeed. I followed every step but when flashify reboots to the stock recovery nothing happens. Just nothing.
I used the file for the L21 that I linked to in this post.
Any suggestions how to get it to work?

Zacki06 said:
Hello together, I tried flashing the B360 update for my L21 with this method but unfortunately I did not succeed. I followed every step but when flashify reboots to the stock recovery nothing happens. Just nothing.
I used the file for the L21 that I linked to in this post.
Any suggestions how to get it to work?
Click to expand...
Click to collapse
Are you on B350D0003 or some earlier firmware? I'm on stock B350, just rooted with Magisk+phh's superuser, and it doesn't want to flash that big file at all; tried flashing OTA update (200MB file) and it failed at 80%, causing a damn bootloop. Gah, I thought my old phone was pain in the ass...

ShadySquirrel said:
Are you on B350D0003 or some earlier firmware? I'm on stock B350, just rooted with Magisk+phh's superuser, and it doesn't want to flash that big file at all; tried flashing OTA update (200MB file) and it failed at 80%, causing a damn bootloop. Gah, I thought my old phone was pain in the ass...
Click to expand...
Click to collapse
I'm on B350D003. After I tried the OTA instead of the full package I came across the same problem with the stock recovery, but when flashing it from TWRP it did flash it, but exited with an error.
No bootloop but as a file was missing for the full update process wifi (and probably bluetooth) are not working.
If you are interrested to solve it, have a look here. It looks like there is a way to fix the problem and we are currently investigating.

Zacki06 said:
I'm on B350D003. After I tried the OTA instead of the full package I came across the same problem with the stock recovery, but when flashing it from TWRP it did flash it, but exited with an error.
No bootloop but as a file was missing for the full update process wifi (and probably bluetooth) are not working.
If you are interrested to solve it, have a look here. It looks like there is a way to fix the problem and we are currently investigating.
Click to expand...
Click to collapse
TBH, I'm on a verge to start building LOS or PAC/Slim/whatever is properly maintained and fast for my own needs and ditch EMUI completely....
I'm searching for other firmwares now via FirmwareFinder, there is a probability that one is a leaked test or something like that, because it simply doesn't want to flash. If I find out something, I'll continue on thread you've linked, to avoid flooding this one.

Hi. Thanks for your guide.
I need to update my phone with several ota updates. I just need to repeat this guide's procedure until updated to the last ota or there is a better way to do that?

Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
rajibie said:
Like your contribution. Perfectly updated to B370.
Click to expand...
Click to collapse
How to update step by step.. Mention it plz

Tapan Patel said:
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
How to update step by step.. Mention it plz
Click to expand...
Click to collapse
Just because you can't do it, that doesn't mean it's fake.

Tapan Patel said:
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
How to update step by step.. Mention it plz
Click to expand...
Click to collapse
Just follow the procedure and you will be done

[REQUEST] LG K420N Stock PreRooted Rom.

Since LG Removed All Possibilities to Root European LG K10
The best and easiest way to root it is to flash PreRooted Rom.
I know that actually don't exist PreRooted firmware for LG K420N, but was searching guides "How to unpack and repack Stock LG KDZ Files".
I found couple guides how to unpack it, but no guide how to put it all together in KDZ.
If someone know some guide how to Pack KDZ Files please help me, I want try to make Stable Stock PreRooted Rom.
With some help is possible!

D_Vovan_238 said:
Since LG Removed All Possibilities to Root European LG K10
The best and easiest way to root it is to flash PreRooted Rom.
I know that actually don't exist PreRooted firmware for LG K420N, but was searching guides "How to unpack and repack Stock LG KDZ Files".
I found couple guides how to unpack it, but no guide how to put it all together in KDZ.
If someone know some guide how to Pack KDZ Files please help me, I want try to make Stable Stock PreRooted Rom.
With some help is possible!
Click to expand...
Click to collapse
that's impossible

Yes it's possible
flamenkito34 said:
that's impossible
Click to expand...
Click to collapse
Yes it's theoretically possible.
With KDZ File you can flash everything you want ( PreRooted Kernel, PreRooted System, Custom Recovery, Modem Files even BootLoader… ).
Also have crazy idea to port Samsung Preload System, I used many different devices, but I found Samsung Preload System very very useful for developer's, to make PreRooted Roms or simply to leave some preloaded apps which will be installed on first system boot (after flashing rom).

D_Vovan_238 said:
Yes it's theoretically possible.
With KDZ File you can flash everything you want ( PreRooted Kernel, PreRooted System, Custom Recovery, Modem Files even BootLoader… ).
Also have crazy idea to port Samsung Preload System, I used many different devices, but I found Samsung Preload System very very useful for developer's, to make PreRooted Roms or simply to leave some preloaded apps which will be installed on first system boot (after flashing rom).
Click to expand...
Click to collapse
The problem is to re-compress the file in KDZ format, anyway if you see it viable and I can help you with something.
greetings
Enviado desde mi LG-K420 mediante Tapatalk

Problem.
flamenkito34 said:
The problem is to re-compress the file in KDZ format, anyway if you see it viable and I can help you with something.
greetings
Enviado desde mi LG-K420 mediante Tapatalk
Click to expand...
Click to collapse
Yes this is my problem, at least for now, to recompress (repack) KDZ File.
My idea, for try will it work or not, simply replace stock recovery for TWRP. This way it will be much more easily to root it and with nandroid backup-restore not so risky ?

D_Vovan_238 said:
Yes this is my problem, at least for now, to recompress (repack) KDZ File.
My idea, for try will it work or not, simply replace stock recovery for TWRP. This way it will be much more easily to root it and with nandroid backup-restore not so risky
Click to expand...
Click to collapse
Actually its not so simple to replace the recovery. On the MTK devices even if rooted if we flash twrp instead of stock the phone is not booting but turns off right after the device corrupt message. I believe it requires something like dump (you can find it on other lg threads - it means there is a hex signature at the end of the recovery image). I found the signature at the end of the stock recovery image, partly the same signature is there in the end of the boot image and the laf image (and i guess all partitions). I copied the signature to the end of the twrp but still its not booting up. I guess that signature is generated somehow related to size or some other details of the image itself but i'm unable to understand it's structure.
So the thing is that even if you could repack the kdz (which is impossible) adding the twrp instead of stock recovery is not an option until you can sign it properly.
I'd rather check the download mode com port commands (https://forum.xda-developers.com/android/software-hacking/tool-lg-download-mode-laf-t3285946), maybe that way there is a chance to exchange the boot image to a rooted one and push supersu.
You also need to unlock the bootloader somehow. I remember some could unlock it on qualcomm device...

gottlasz said:
Actually its not so simple to replace the recovery. On the MTK devices even if rooted if we flash twrp instead of stock the phone is not booting but turns off right after the device corrupt message. I believe it requires something like dump (you can find it on other lg threads - it means there is a hex signature at the end of the recovery image). I found the signature at the end of the stock recovery image, partly the same signature is there in the end of the boot image and the laf image (and i guess all partitions). I copied the signature to the end of the twrp but still its not booting up. I guess that signature is generated somehow related to size or some other details of the image itself but i'm unable to understand it's structure.
So the thing is that even if you could repack the kdz (which is impossible) adding the twrp instead of stock recovery is not an option until you can sign it properly.
I'd rather check the download mode com port commands (https://forum.xda-developers.com/android/software-hacking/tool-lg-download-mode-laf-t3285946), maybe that way there is a chance to exchange the boot image to a rooted one and push supersu.
You also need to unlock the bootloader somehow. I remember some could unlock it on qualcomm device...
Click to expand...
Click to collapse
Qualcomm Snapdragon 210 models could unlock it!
I think I know the signature you are talking about. Its called LG Magic Number. It is "41a9e467744d1d1ba429f2ecea655279". I saw developers adding it to their recoveries at the end I think using Hex Editor and it worked!
Anyways, I like the innovative idea of getting a pre-rooted Stock ROM.
LG Magic number source: https://github.com/CyboLabs/Open_Bump/blob/master/open_bump.py
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
D_Vovan_238 said:
Since LG Removed All Possibilities to Root European LG K10
The best and easiest way to root it is to flash PreRooted Rom.
I know that actually don't exist PreRooted firmware for LG K420N, but was searching guides "How to unpack and repack Stock LG KDZ Files".
I found couple guides how to unpack it, but no guide how to put it all together in KDZ.
If someone know some guide how to Pack KDZ Files please help me, I want try to make Stable Stock PreRooted Rom.
With some help is possible!
Click to expand...
Click to collapse
I found a tool to repack KDZ file.
https://github.com/ehem/kdztools
If it may help in repacking KDZ!
---------- Post added at 04:43 PM ---------- Previous post was at 04:27 PM ----------
D_Vovan_238 said:
Since LG Removed All Possibilities to Root European LG K10
The best and easiest way to root it is to flash PreRooted Rom.
I know that actually don't exist PreRooted firmware for LG K420N, but was searching guides "How to unpack and repack Stock LG KDZ Files".
I found couple guides how to unpack it, but no guide how to put it all together in KDZ.
If someone know some guide how to Pack KDZ Files please help me, I want try to make Stable Stock PreRooted Rom.
With some help is possible!
Click to expand...
Click to collapse
Tools which can help you
https://forum.xda-developers.com/showthread.php?t=2020737
http://4pda.ru/forum/lofiversion/index.php?t184435-100.html

pvineeth97 said:
Qualcomm Snapdragon 210 models could unlock it!
I think I know the signature you are talking about. Its called LG Magic Number. It is "41a9e467744d1d1ba429f2ecea655279". I saw developers adding it to their recoveries at the end I think using Hex Editor and it worked!
Click to expand...
Click to collapse
This is the old signature. This is used in Bump, tried it already.
pvineeth97 said:
Anyways, I like the innovative idea of getting a pre-rooted Stock ROM.
LG Magic number source: https://github.com/CyboLabs/Open_Bump/blob/master/open_bump.py
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
I found a tool to repack KDZ file.
https://github.com/ehem/kdztools
If it may help in repacking KDZ!
Click to expand...
Click to collapse
I don't think it works, there is this statement:
"WARNING: It has been found there is some additional unknown verification
mechanism in LGE's tools. Due to this mechanism currently the generated KDZ
files haven't been shown to work. There are some guesses as to where the
mechanism is, but as of now not enough is known to work around it."
pvineeth97 said:
---------- Post added at 04:43 PM ---------- Previous post was at 04:27 PM ----------
Tools which can help you
https://forum.xda-developers.com/showthread.php?t=2020737
http://4pda.ru/forum/lofiversion/index.php?t184435-100.html
Click to expand...
Click to collapse
Those are from 2010 and 2012... many things changed.
No offence bro...

Thanks
Thank you very much guys ?
Now have many information to work…
Yes bootloader is other problem, but was reading some Russian Guides how to root LG K 10 LTE and they saying that I don't need to unlock BL to root it.
Or there is other way, like with Samsung Galaxy S6, one dev made big change in Samsung Marshmallow Rom, so this MM Rom can be rooted by System Root, not like our Systemless (Need to repack kernel).
So im going to work with new information…
For me UnRooted device is not complete device.
Why I need root?
To add init.d support to kernel, xposed installer, lucky patcher, titanium backup, Linux SWAP, change LCD Density, build.prop tweaks, I can count whole day and I will forget something…

D_Vovan_238 said:
Thank you very much guys
Now have many information to work…
Yes bootloader is other problem, but was reading some Russian Guides how to root LG K 10 LTE and they saying that I don't need to unlock BL to root it.
Or there is other way, like with Samsung Galaxy S6, one dev made big change in Samsung Marshmallow Rom, so this MM Rom can be rooted by System Root, not like our Systemless (Need to repack kernel).
So im going to work with new information…
For me UnRooted device is not complete device.
Why I need root?
To add init.d support to kernel, xposed installer, lucky patcher, titanium backup, Linux SWAP, change LCD Density, build.prop tweaks, I can count whole day and I will forget something…
Click to expand...
Click to collapse
We are excited and waiting eagerly!
Join our Whatsapp group. We would be grateful

Honor 8 FRD-L04 B385 update?

I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
EDIT: I tried to install it through firmware finder and it didn't pass the verification at the end
https://drive.google.com/open?id=0B4baHcoSeBbgY21CVjlPNk45YlE
https://drive.google.com/open?id=0B4baHcoSeBbgYTZiR1ZDeUpoWnc
https://drive.google.com/open?id=0B4baHcoSeBbgV0g3ejBlMXlzdkk
I have downloaded the 3 zips in this update and verified the md5 they are all good if someone figures out how to install this

krchi said:
I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
Click to expand...
Click to collapse
I found the same... Gonna try!

Jessooca said:
How did that work out for you Jorge??
Sent from my FRD-L04 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...

JorgeCS said:
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...
Click to expand...
Click to collapse
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.

Well the good news I see out of this even if we cannot install is that the update is finally coming after 2 months of the other versions enjoying it for that long. Hopefully it fixes the battery drain.
Sent from my FRD-L04 using Tapatalk

Received the OTA update for the B380 version on my FRD L09C185 yesterday. But no notable change in the battery life till now.

krchi said:
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.
Click to expand...
Click to collapse
Yep, you can't install this...

Can you install the full firmware from B162 though?

Gus194 said:
Can you install the full firmware from B162 though?
Click to expand...
Click to collapse
You can try and tell us

Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs

Jessooca said:
So the 622mb update file is the correct B385 update file? Can i push it to the phone via adb? Or what's the best way to install it??
Click to expand...
Click to collapse
Likely you'd push both update.zip and the region specific zip to where the stock recovery is expecting, then from a powered-off state use the key combinations to force-udpate. I'm unsure why there are 3 zips this time though since B360 was only 2 zips, I haven't had time yet to look at the contents.

Telperion said:
Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs
Click to expand...
Click to collapse
Mines was just the OTA files you have the full ota files

Jessooca said:
Did you install the update you found?
Click to expand...
Click to collapse
I tried.

I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...

usmcnyc said:
I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...
Click to expand...
Click to collapse
Tried that, compatibility error.

Telperion said:
Tried that, compatibility error.
Click to expand...
Click to collapse
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV

usmcnyc said:
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV
Click to expand...
Click to collapse
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.

Telperion said:
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.
Click to expand...
Click to collapse
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...

usmcnyc said:
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...
Click to expand...
Click to collapse
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.

Telperion said:
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.
Click to expand...
Click to collapse
There's a 1.9gb OTA on firmware finder...I'd download it here at work but the internet is too slow, it'd take hours.

Oreo stock recovery ze520kl

Does anyone have the stock recovery Oreo for Asus Zenfone 3 ze520kl?
I need it to upgrade my rooted phone since I'm getting error "can't install this package on device version less than...".
I know I can download the .raw and extract it, but I don't have PC to do it. Using phone I couldn't find any app which allows me to extract.
Thanks for your attention

mvini_ab said:
Does anyone have the stock recovery Oreo for Asus Zenfone 3 ze520kl?
I need it to upgrade my rooted phone since I'm getting error "can't install this package on device version less than...".
I know I can download the .raw and extract it, but I don't have PC to do it. Using phone I couldn't find any app which allows me to extract.
Thanks for your attention
Click to expand...
Click to collapse
This folder will help everyone with the same problem:
https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!xhVEhCjB

mvini_ab said:
This folder will help everyone with the same problem:
https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!xhVEhCjB
Click to expand...
Click to collapse
Interesting this folder, but it is outdated, the latest firmware stock is WW-15.0410.1806.68
2018/07/13.
---------- Post added at 12:58 PM ---------- Previous post was at 12:57 PM ----------
mvini_ab said:
Does anyone have the stock recovery Oreo for Asus Zenfone 3 ze520kl?
I need it to upgrade my rooted phone since I'm getting error "can't install this package on device version less than...".
I know I can download the .raw and extract it, but I don't have PC to do it. Using phone I couldn't find any app which allows me to extract.
Thanks for your attention
Click to expand...
Click to collapse
what program do I use to extract firmware recovery?

kiq1702 said:
Interesting this folder, but it is outdated, the latest firmware stock is WW-15.0410.1806.68
2018/07/13.
---------- Post added at 12:58 PM ---------- Previous post was at 12:57 PM ----------
what program do I use to extract firmware recovery?
Click to expand...
Click to collapse
Yes, it is outdated, but it might be really useful because there are stock recoverys from ze520kl oreo version.
I believe you can extract files using 7-Zip.

mvini_ab said:
Yes, it is outdated, but it might be really useful because there are stock recoverys from ze520kl oreo version.
I believe you can extract files using 7-Zip.
Click to expand...
Click to collapse
I can not find any file that corresponds to recovery. Can you tell me what it is?

kiq1702 said:
I can not find any file that corresponds to recovery. Can you tell me what it is?
Click to expand...
Click to collapse
Sorry for answering so late.l, but here we go.
You don't have the correct file. What you have is just a file to update your phone. You need to download .RAW firmware if you want to extract stock recovery.
What are you planning to do? If you phone got bricked (like infinite loop) you can easily use that virtual folder and use the latest available (there) recovery to put your phone in normal, trust me, it'll solve the problem.
But if you really need the .RAW files, here you can some Oreo examples, not the lastest, but also work.
ZE520KL: https://drive.google.com/file/d/1Y5OVqmmAjb5PWZ6sKknzP0YnQHGyDxD0/view
ZE522KL:
https://drive.google.com/file/d/1DInYnZ4hLICjI_-cZ-NvUC_Vpzc_FnPO/view
And, in case you need some stock recovery for ZE520KL from that virtual folder, try these for ZE520KL:
[1803.55] https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!xhVEhCjB
[1804.61] https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!RgFnSKwZ
Again, I don't know what are planning to do, so my answer might not be useful. xD

mvini_ab said:
Sorry for answering so late.l, but here we go.
You don't have the correct file. What you have is just a file to update your phone. You need to download .RAW firmware if you want to extract stock recovery.
What are you planning to do? If you phone got bricked (like infinite loop) you can easily use that virtual folder and use the latest available (there) recovery to put your phone in normal, trust me, it'll solve the problem.
But if you really need the .RAW files, here you can some Oreo examples, not the lastest, but also work.
ZE520KL: https://drive.google.com/file/d/1Y5OVqmmAjb5PWZ6sKknzP0YnQHGyDxD0/view
ZE522KL:
https://drive.google.com/file/d/1DInYnZ4hLICjI_-cZ-NvUC_Vpzc_FnPO/view
And, in case you need some stock recovery for ZE520KL from that virtual folder, try these for ZE520KL:
[1803.55] https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!xhVEhCjB
[1804.61] https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!RgFnSKwZ
Again, I don't know what are planning to do, so my answer might not be useful. xD
Click to expand...
Click to collapse
Many thanks, I just wanted to know how to extract the "recovery.img" file from the .raw file.
But I realized that I was looking for the wrong file, this print I sent is from the stock rom firmware file that comes from the Asus website. (http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-JP-15.0410.1806.68-user.zip).
Where can I find this ".RAW" file that you put there on the link, has it updated on the asus website?

@mvini_ab
Why don't you just skip the stock recovery and flash it thru twrp? Editing the updater-script bypasses the error you're getting. That's how I've been doing it for years, no issues, you just have to flash magisk or superSU afterwards.

kiq1702 said:
Many thanks, I just wanted to know how to extract the "recovery.img" file from the .raw file.
But I realized that I was looking for the wrong file, this print I sent is from the stock rom firmware file that comes from the Asus website. (http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-JP-15.0410.1806.68-user.zip).
Where can I find this ".RAW" file that you put there on the link, has it updated on the asus website?
Click to expand...
Click to collapse
You can't find RAW files on official Asus website.
That was the most recent RAW firmware I could find.
You can flash that and update it through the phone in settings -> system -> update
Flash Tools: https://drive.google.com/file/d/0BzBzT9RsAkigcTlCSlZpMTRBV1U/view
Put your phone in droidboot mode by holding volume+ and power and then use flashtools.

wang1chung said:
@mvini_ab
Why don't you just skip the stock recovery and flash it thru twrp? Editing the updater-script bypasses the error you're getting. That's how I've been doing it for years, no issues, you just have to flash magisk or superSU afterwards.
Click to expand...
Click to collapse
I honestly don't know how to do it. Never read any tutorial teaching that. Furthermore, I don't have computer/laptop (poor enough for that), just my cellphone. =\

@mvini_ab
I've done it through my phone before with rootexplorer, it's annoying but it works. Open the updater-script in the rom zip, it's located in META-INF/com/google/android/. Be careful, there are two files in that directory, you want updater-script not updater-binary.
Open the file with a text editor, delete the first few lines, pretty much up to "ui_print target asus ww_phone release keys", and then save it back into the rom zip and flash it. I think I had to extract the script, delete it from the archive, and then add the edited script back to the archive when I was done.
Flashing magisk and wiping cache/dalvik is all you need after flashing the modified stock Rom through twrp.

wang1chung said:
@mvini_ab
I've done it through my phone before with rootexplorer, it's annoying but it works. Open the updater-script in the rom zip, it's located in META-INF/com/google/android/. Be careful, there are two files in that directory, you want updater-script not updater-binary.
Open the file with a text editor, delete the first few lines, pretty much up to "ui_print target asus ww_phone release keys", and then save it back into the rom zip and flash it. I think I had to extract the script, delete it from the archive, and then add the edited script back to the archive when I was done.
Flashing magisk and wiping cache/dalvik is all you need after flashing the modified stock Rom through twrp.
Click to expand...
Click to collapse
Nice! In the next update I'll try that. Thank you, that was really satisfying.

Thank you so much. It's really help me!! I'm going to take my phone to fixer! Thank you again! <3