Related
I've been having issues with my phone, and I'm not sure if this is a HW issue or not, but no matter what I do, either I lose recovery or get a security error. I poked around and found some instructions in the CloudyG3 thread. They're for 3.0 but I would guess 3.3 wouldn't be different enough to brick this thing. Can't remember who the quote is from, I just copy/pasted it, but here it is:
Some of you sent me a PM asking for the install instructions on D800 and this is how you install CloudyG2 3.0:
Downloads:
1. Download CloudyG2 3.0 - https://www.androidfilehost.com/?fid=95897840722646001
2. Download Patch - https://mega.co.nz/#!sVY0mRTb!qn7S9B...3m_QpMQkgzunn0
3. Download Signal Patch - https://dl.dropboxusercontent.com/u/...l_Variants.zip
4. Download LP Baseband - http://blastagator.ddns.net/modem.php - d800-30f-modem-blastagator-signed.zip
5. Download KK Bootstack - http://blastagator.ddns.net/bootloader.php - bootstack-d800-KK_20c-blastagator-signed.zip
6. Optional: Download JB Bootstack in case if you want to revert the installation process and go back to your current ROM - http://blastagator.ddns.net/bootloader.php - bootstack-d800-JB_10d-blastagator-signed.zip
Flashing Process:
1. Backup the existing ROM (including EFS, Modem, etc.) in TWRP - very important and copy it over to the computer, just in case!
2. Wipe System + Data + Cache + Dalvik Cache - Do NOT select internal storage as it contains all your downloaded files + backups!
3. Flash KK Bootstack (downloaded from Step 5)
4. Flash LP Baseband (downloaded from Step 4)
5. Flash CloudyG2 3.0 (downloaded from Step 1) - Leave the default in Aroma when you have to pick the variant. Do NOT reboot the device as the patch installation (next Step) is very important.
6. Flash Patch (dowloaded from Step 2) - Select your variant.
7. Flash Signal Patch (downloaded from Step 3)
8. Reboot
Enjoy!
Click to expand...
Click to collapse
I'm guessing I have the incorrect files, most of the links I found in the thread with these instructions didn't seem to work so I Googled for them, maybe I don't even have the correct files. I took a screenshot in cmd of the exact filesizes.
Any help would be greatly appriciated!
level5music said:
I've been having issues with my phone, and I'm not sure if this is a HW issue or not, but no matter what I do, either I lose recovery or get a security error. I poked around and found some instructions in the CloudyG3 thread. They're for 3.0 but I would guess 3.3 wouldn't be different enough to brick this thing. Can't remember who the quote is from, I just copy/pasted it, but here it is:
I'm guessing I have the incorrect files, most of the links I found in the thread with these instructions were dead mega.co.nz links so maybe I don't even have the correct files. I took a screenshot in cmd of the exact filesizes.
Any help would be greatly appriciated!
Click to expand...
Click to collapse
you want to install cloudy g2 3.3?
this is whati did
used to root http://www.droidviews.com/easily-root-lg-devices-using-the-one-click-root-script/ if you are on lollipop it gets stuck at 90% twice after 3 attemps same stuck at 90% rebooted and it was rooted
then on playstore i used autorec canat remeber if it says v2.. but for lollipop installed and it checked my device and its said it was ready. so i just clicked twrp and it installed twrp then i downloaded blastogator twrp and installed cloudy g2 3.3 on d800 unlocked... sorry if you were refferimg to another version of cloudy..
raptorddd said:
you want to install cloudy g2 3.3?
this is whati did
used to root http://www.droidviews.com/easily-root-lg-devices-using-the-one-click-root-script/ if you are on lollipop it gets stuck at 90% twice after 3 attemps same stuck at 90% rebooted and it was rooted
then on playstore i used autorec canat remeber if it says v2.. but for lollipop installed and it checked my device and its said it was ready. so i just clicked twrp and it installed twrp then i downloaded blastogator twrp and installed cloudy g2 3.3 on d800 unlocked... sorry if you were refferimg to another version of cloudy..
Click to expand...
Click to collapse
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?
level5music said:
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?
Click to expand...
Click to collapse
no not really, but i do know that we had to use 2871 cause newer version were wiping f2fs, so now latest build its working but i dont think it has something to do .... am sorry i just got mine like a week ago and mine was in lollipop.. so i know nothing about coming from other version of android. dont even know whatsa tot flash.. i still need to learn alot..
check here and see if you can find a way to fix this good luck
http://forum.xda-developers.com/lg-g2/general/05-10-index-guides-fixes-roots-t3218178
level5music said:
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?
Click to expand...
Click to collapse
I had the exact problem happen to me ....... I got the black screen of death .... phone wouldnt boot ....... and when i used the kk bootloader i would lose recovery ..... I was coming from kk to CloudyG2 ....
This is how i solved.
1. Flashed back to stock, stumproot to root Autorec v1 for bootloader
2. used Flashify to upgrade to 2.8.7.1 ( its now 2.8.7.3)
3. Downloaded n used bumpted LP bootstack and flashed blastagator stripped rom (its in flashable zip and installs everythin including modem .... patches etc EVERYTHING) http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195
4. Downloaded kk bootstack , CloudyG2 3.3 and clean flashed in recovery
I have been enjoying Cloudy ever since ...... D800
Thanks all, got it running! Cloudyfa has done some absolutely brilliant work here with this ROM, as well as xdabbeb with the advanced camera driver and xCam. I'm usually a vanilla-or-nothing guy with my Android ROMs but this one is quick and power efficient. The KitKat ROM that shipped with the phone was super bloated and gross, but I'll admit LG UX 4.0 isn't really that offensive, plus I like the goodies like Multi-Window and QuickRemote. Once I disabled/hid some of the remaining LG bloat, it's surprisingly pleasant and not really that far from AOSP aesthetically. Again, cheers to those who provided the assist on this one for me!
... now my only question is, should I try CloudyG3?
UPDATE: This is now unneeded because threr is a faster way ro unlock bootloader on official MM here, he updated for official MM
Hi, I discovered an unlock method for official MM!! This maybe long but's it totally safe
You need:
Adb and fastboot environment ready PC
LP RAW File
Android 6.0 Beta Unlock tool
Android 5.0 One-Click Unlock tool
First version of beta MM (Z00A) (Z008)
Official MM zip (find it on Asus site)
Thanks to all people upload these links
Just do the following:
Flash the lastest LP via AFT (using raw file given above), wipe all data. If you already on MM, you have to downgrade
Unlock your bootloader using 1 click tool given above
Boot to stock recovery and sideload the first version of beta MM
Unlock the bootloader using MM beta unlock tool above
Boot to stock recovery
Two case here:
Case 1: You can't boot stock recovery
Normally boot your phone (to Android)
Setup it as a new phone
If it shows there is a new firmware, don't update!!!
Enable Developer options, then enable usb debugging
Copy the official MM zip to external sd card
Open command prompt, run adb reboot recovery, accept the adb permission if prompted
After it boots to recovery, select Apply update from SD, then choose the zip file you've copied before
Wait for it to update, it may stuck at flashing splashcreen, don't worry, it's trolling you, may be Asus forgot to update the script
Goto step 7
Case 2: You can boot stock recovery
Sideload the official MM zip (adb sideload <filename>.zip)
Goto step 7
7. Flash this TWRP (fastboot flash recovery <twrp>.img)
8. Root your phone using this method
9. Reboot, if it shows "Your phone has failed verification bla bla..", then you've success. It may reset loop like note 7 in the first time start, don't worry.
9. Enjoy :highfive:
Note: If you're facing with battery problems on MM, factory reset it in Settings > Backup and Reset > Factory Reset > Erase everything
Successfully on my ZE550ML
The warning screen is normal so don't worry and there is no way to fix it for now
Reverse
Reverse #2
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
NiTesh said:
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, BL will be relocked once you upgrade to MM.
If you want to unlock MM BL(6.0), refer to this thread.
Or you can downgrade to Lollipop referring to this thread. Then your BL(5.0) is unlocked.
Upgrade to MM
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
R3D SoX F4N said:
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
Click to expand...
Click to collapse
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
can anyone please upload official recovery for Zenfone 2 ZE551ML, currenty i have twrp installed on Android version 5.0 LP Stock
HungNgocPhat said:
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
Click to expand...
Click to collapse
i have twrp recovery at the moment cause i followed mr_gouvad2000 tuturial..
what do you sugest?
flash WW_ZE551ML_2.20.40.196_20160815.raw?
WW_ZE551ML_2.20.40.194_20160713.raw?
and then go and do what you told?
cheers
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
tridet18 said:
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
Click to expand...
Click to collapse
someone correct me if i am worng but....
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Look for this version WW-4.21.40.134
Hello, thank you but this version is official, i need de first beta 6.0
R3D SoX F4N said:
someone correct me if i am worng but....
Look for this version WW-4.21.40.134
Click to expand...
Click to collapse
that version...i can´t find it anywere..maybe someone here knows were to find it?
Updated the first MM beta link in OP
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
tridet18 said:
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
Click to expand...
Click to collapse
Have you downloaded the correct build? There are build for MM bootloader, if you flash the normal builds, it will fail and reboot to recovery again. Gapps is the same for all builds
After you install that special build, do not update to newer nightlies, it will fail. For updates, check the link i give you and see if there is a new MMBL build.
About that, here is the post: http://forum.xda-developers.com/showpost.php?p=68542370&postcount=8551
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
tridet18 said:
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
Click to expand...
Click to collapse
Run the script again (i gave you in above post). Download the CM13 in that link, not in the OP of CM13 thread. Flash that CM13 and Gapps (Gapps is universal for MMBL and LPBL).
May be you have corrupt download, I'm currently running CM13 on MMBL
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
hlp
tridet18 said:
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
Click to expand...
Click to collapse
how u unlocked bootloader
1,unlocked bootload,https://www.gizdev.com/lg-g5-h850-twrp-3-0-rooting-guide/
2,install rec for h850 ,http://thunderztech.com/root-lg-g5-on-android-7-0-nougat-with-twrp-recovery/
3,into rec and flash LG-H85010E-Flashable.Bootloader.zip from autoprime,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
4,lg up flash 6.0.1 kdz,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
5,wipe you device by keep volume- always and power,when look lg logo,press power again and keep it ,then press yes,yes
you have downgrade to 6.0.1
xjqlfq said:
1,unlocked bootload,https://www.gizdev.com/lg-g5-h850-twrp-3-0-rooting-guide/
2,install rec for h850 ,http://thunderztech.com/root-lg-g5-on-android-7-0-nougat-with-twrp-recovery/
3,into rec and flash LG-H85010E-Flashable.COMPLETE.zip from autoprime,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
4,lg up flash 6.0.1 kdz,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
5,wipe you device by keep volume- always and power,when look lg logo,press power again and keep it ,then press yes,yes
you have downgrade to 6.0.1
Click to expand...
Click to collapse
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
thanks,get it
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
I had several problems with this procedure (coming from V20a):
1. After flashing 10C BOOTLOADER ZIP via TWRP, LGUP was not able to detect my device type anymore, but this worked with previous bootloader. Why?
2. Flashing the 10C COMPLETE ZIP did result in a loss of TWRP (although recovery.img is not part if complete ZIP). Why?
3. Flashing the 10E COMPLETE ZIP caused FCs and a bootloop Reset in system recovery did help to get the device up again.
After that LGUP did find again my H850 and upgrade option works now with M KDZs (which did not work under Nougat). But the refurbish option is still not working and says "not supported".
fuxi222 said:
I had several problems with this procedure (coming from V20a):
1. After flashing 10C BOOTLOADER ZIP via TWRP, LGUP was not able to detect my device type anymore, but this worked with previous bootloader. Why?
2. Flashing the 10C COMPLETE ZIP did result in a loss of TWRP (although recovery.img is not part if complete ZIP). Why?
3. Flashing the 10E COMPLETE ZIP caused FCs and a bootloop Reset in system recovery did help to get the device up again.
After that LGUP did find again my H850 and upgrade option works now with M KDZs (which did not work under Nougat). But the refurbish option is still not working and says "not supported".
Click to expand...
Click to collapse
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
autoprime said:
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
Click to expand...
Click to collapse
At first: Big thanks for your quick response!!!
to 1.: The reason for 10C instead of 10E is simple: you do not have a KDZ file for 10E on your codefire drive (only a ZIP), but for 10C the KDZ was available. And the links to LG server were not working yesterday for me.
I read Uppercut the first time now and will give it a try today in the evening (German time). :fingers-crossed:
to 2.: Understood. Thank you! :good:
to 3.: Then how can I get rid of the 3 error messages on start-up related to NT-code ("Can't find matched cust for NT-code" + "OP name for Buyer-code...")? I understood, that refurbish will flash new cust partition and this will solve the problem. I see cust.img also on your drive, but it is not inluded in the COMPLETE ZIPs. Would it help to flash this?
Or can LG Bridge help in this case? It does refuse to flash my phone, maybe because of the bootloader unlock?!
I read so many threads yesterday, but nothing solved this issue... :crying::crying:
fuxi222 said:
to 3.: Then how can I get rid of the 3 error messages on start-up related to NT-code ("Can't find matched cust for NT-code" + "OP name for Buyer-code...")? I understood, that refurbish will flash new cust partition and this will solve the problem. I see cust.img also on your drive, but it is not inluded in the COMPLETE ZIPs. Would it help to flash this?
Or can LG Bridge help in this case? It does refuse to flash my phone, maybe because of the bootloader unlock?!
I read so many threads yesterday, but nothing solved this issue... :crying::crying:
Click to expand...
Click to collapse
cust should be getting flashed regardless of selecting refurbish or not as far as I know.. but perhaps I'm wrong.
if you have root/twrp just zero out the cust partition or simply delete the files inside the cust folder using a file explorer app... and the error msg should go away on next reboot.
this is in the FAQ/Q&A section in the OP of all my stock threads for H850.
if you're on M and must flash a KDZ with refurb option... just use the old LGUP methods. but if you're sticking with TWRP there's not really any need to flash any KDZ.. you can flash whatever in TWRP instead.
autoprime said:
cust should be getting flashed regardless of selecting refurbish or not as far as I know.. but perhaps I'm wrong.
if you have root/twrp just zero out the cust partition or simply delete the files inside the cust folder using a file explorer app... and the error msg should go away on next reboot.
this is in the FAQ/Q&A section in the OP of all my stock threads for H850.
if you're on M and must flash a KDZ with refurb option... just use the old LGUP methods. but if you're sticking with TWRP there's not really any need to flash any KDZ.. you can flash whatever in TWRP instead.
Click to expand...
Click to collapse
"and the error msg should go away on next reboot." I get 3 error messages related to this. Will I get rid of all of them?
"old LGUP methods" means tool version 1.11 instead of 1.14? So use version 1.11 for MM and 1.14 for N?!
Unfortunately, refurbish does not work even under MM for me regardless if I use version 1.11 or 1.14.
BTW: The old version 1.11 asks my each time I trigger the refurbish process to "Input new NT code" (the new version does not behave like this). Is my problem maybe caused by this or can this be used to input a working string there?
fuxi222 said:
"and the error msg should go away on next reboot." I get 3 error messages related to this. Will I get rid of all of them?
"old LGUP methods" means tool version 1.11 instead of 1.14? So use version 1.11 for MM and 1.14 for N?!
Unfortunately, refurbish does not work even under MM for me regardless if I use version 1.11 or 1.14.
BTW: The old version 1.11 asks my each time I trigger the refurbish process to "Input new NT code" (the new version does not behave like this). Is my problem maybe caused by this or can this be used to input a working string there?
Click to expand...
Click to collapse
i dont have an H850 so idk.. but any time ive had someone zero cust theyve said errors have gone away. so if they dont for you.. you must be special. try it and find out... then report back. if it doesnt work... ¯\_(ツ)_/¯
old lgup methods = 1.11 + dll msi installer, yes. but i see no reason to use 1.11 simply for refurbish option. most people should be able to use LGUP 1.14 + UPPERCUT for most situations on G4/G5/V20.
i dont know abotu the NT code stuff with LGUP.. again.. I dont have a H850. but if you have TWRP then there's really no need to be messing with LGUP at all unless you want to be 100% stock/unrooted with no TWRP. just zero cust or try flashing the cust.img that's in the folder.
I cant help any more on this NTCode subject without a device that uses it. good luck.
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
Only if someone is on the same point: For me, it is only working to flash the COMPLETE ZIP! When I flash bootloader only, LGUP does not detect the model type of my device anymore (detected type is "Unknown"). I have tried it now for 2 times with similar results...
BTW: I used this method to get rid of the annoying NT code issue: http://forum.xda-developers.com/showpost.php?p=66957161&postcount=4
@autoprime Can't we just flash 10E with the refubrish option? Somehow I'm unable to get into recovery with the button combination after downgrading and updating again, even though I'm doing it properly and I was able to do it before.
EDIT: So refubrish stopped working now too. Dang. I installed the recovery through Dirty Cow, flashed the bootstack and went back to 10E, but I still don't have a recovery. ;_;
Ok, I've tried everything and button combination for recovery still doesn't work, so think if you really wanna risk being unable to easily factory reset your phone.
autoprime said:
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
Click to expand...
Click to collapse
Well I am trying to flash stock EE rom, which I have the KDZ for.
I am flashing via upgrade, and all that happens is when the phone boots it is unstable, phone app crashing etc.
All settings still intact, no myee app, app from open EU rom still exists, very very strange.
Is it possible to convert a KDZ to a twrp flashable zip as twrp seems far easier.
I suspect if I used refurbish it would fix this issue as upgrade seems to not be clearing everything.
chrcol said:
Well I am trying to flash stock EE rom, which I have the KDZ for.
I am flashing via upgrade, and all that happens is when the phone boots it is unstable, phone app crashing etc.
All settings still intact, no myee app, app from open EU rom still exists, very very strange.
Is it possible to convert a KDZ to a twrp flashable zip as twrp seems far easier.
I suspect if I used refurbish it would fix this issue as upgrade seems to not be clearing everything.
Click to expand...
Click to collapse
Did u try what I suggested in other thread? Wipe internal storage before first boot, reboot recovery afterwards before booting system; are u clean flashing? Are you trying to restore any data at all besides things like messages and call logs?
Going from an openEU.kdz to a branded .Kdz would definitely require a Twrp data format and a recovery reboot, perhaps do all this b4 using LGUP with kdz.
Yes it is possible to make a .zip from a kdz, but it's not a simple process and there is no EE branded 20a.zip
Autoprime already stated that refurbish option can be used if you use LGUP v1.11 instead of latest 1.14 but don't forget the .DLL file. Also all refurbish does is wipe data and internal storage; which can be done via TWRP using the method I mentioned above. Try what I mentioned and then reflash kdz;forget about any data besides text messages just take the extra 30min to resetup device from scratch.
What version of LGUP are you using? Can u give more info be more descriptive about what's happening?
it is resolved now but I was just trying to get it in a good state to return the phone to EE.
Doing a factory reset in twrp didnt work, but what did work is I did a reset from in the rom, and after the reboot it was properly reset.
What was odd is when I wiped system and data manually in twrp that also didnt work.
I think I forgot to check if I completely wiped the internal storage, photos etc. As I was rushing to get the phone to be sent back. But the description for the reset option in android says it does wipe all personal data so hopefully that did it.
How can I downgrade LS992?
İs this possible for lg g5 H860?
For H850 just download H85010i_00_OPEN_EU_OP_0923.kdz flash it with LGUP 1.4(uppercut) after it's finished reset the phone then just flash android 6 firmware that you like.
i have h850 ,
current firmware is v20a updated via fota
no root , no bootloader unlock ,,, compleatlly stock phone
i want to downgreade to any 6.0.1 firmware without losing data (if possible)
if not, what to check and what steps to do without tripping on cust ot drk or modem or .... issues ?
pleas advice me ....
LGUP corrupts whenever i hit Start, but it works just fine with N kdz (mine is 20a). I have tried to flash bootloader but still ended up with the same outcome.
Lucky patcher does not work on nougat. Application not installed. playstore error 504
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
I rooted H850 following autoprime's LG G5 H850 Bootloader Unlock instruction with autoprime's modded "Minimal ADB and Fastboot" {[ 1.) selecting port 41 in device manager (maybe was not necessary) and 2.) pushing TWRP twrp-3.1.1-0-h850.img 3.)booted into recovery (Using 2 hands.. use one hand/finger to press/hold volume down.. and use the other hand for the power button. Press n hold both buttons.) 4. flashing SuperSU (UPDATE-SuperSU-v2.82-20170528234214.zip) ]}.
Installed 20a with lgup because for a strange (windows 10 folder administrator permission) reason nether UPPERCUT_1.0.0.0.exe nether LGFlashTool.exe worked properly).
Unfortunatly I installed [ROM] [Nougat 7.0] Fulmics ROM 3.3 ◦ v20D ◦ H850 but, because the very big LACK of xposed framework on nougat, I had too much difficulties to patch correctly the core jar with lucky patcher getting a lot of error "app not installed the package appears to be corrupt" and other play store error 504 app not installed.
So I decided to downgrade and leave from any Nougat 7.0 based rom in order to move on Marshmallow 6.0. In particular I used TWRP to wipe everything and flash [STOCK][M] H850 10E OPEN EU ROM autoprime's 10E COMPLETE ZIP then Supersu then framework.
On android this time I skipped google registration and LG software updates with data and wifi OFF.
Then I activated USB debug in developer section
Then I followed these step in that really precise order:
a) installed super su again with twrp (want to be sure to have got ROOT);
b) configure Super Su setting in android to activate pseudo PRO option then uncheck the "separation mount space" in order to share .init;
c) configure Super Su setting giving permission always without asking and also during in boot (to everybody);
d) installed xposed-v87-sdk23-arm64.zip in TWRP
e) installed lucky patcher and using it to unistall every LG apps;
f) activate for the very first time wify in order to update immidiately lucky patcher (update available in lucky patcher settings) than download patch update;
g) installed xposed apk (in android obviosly because I refer to apk pattern) and run it following app procedure for a correct detection of framework then activate Lucky patcher module in xposed apk then reboot to permit lucky patcher using framework;
h) installed busybox (after the check I choose the "smart install").
i) and now I enjoy the freedom that I haven't got in Nougat to test some application before buying them, just to be sure to not waste money for fake apk like voice pro or other expensive one that fools me before so many times. :good:
Update: G5 H850 Genisys Theme 1.3 v10e MM is a great choice for stability and battery life.
Hey...Help me with this..
I tried to root my moto g4 plus using temporary twrp so that i get system updates,It is not working out.
I have used moto g3.. and used this same method for rooting and is successful..
In g4 plus till the last step i.e untill u need to flash supersu it works but there comes error.
Every data is lost and i have to boot into my custom rom backup...
Please suggest something to help me...please
Adarsh balu said:
Hey...Help me with this..
I tried to root my moto g4 plus using temporary twrp so that i get system updates,It is not working out.
I have used moto g3.. and used this same method for rooting and is successful..
In g4 plus till the last step i.e untill u need to flash supersu it works but there comes error.
Every data is lost and i have to boot into my custom rom backup...
Please suggest something to help me...please
Click to expand...
Click to collapse
Can I request some more details please?
OS version?
TWRP version?
Did you unlock your bootloader and enabled OEM unlocking in Developer Settings?
Which rooting method did you use (e.g. did you flash ElementalX kernel https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 or the superboot method https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556) ?
What error do you get?
EDIT - I understand you're desperate for help resolving this, please don't post the same thing in 3 places if you can.
echo92 said:
Can I request some more details please?
OS version?
TWRP version?
Did you unlock your bootloader and enabled OEM unlocking in Developer Settings?
Which rooting method did you use (e.g. did you flash ElementalX kernel https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 or the superboot method https://forum.xda-developers.com/mo...-how-to-root-n-firmware-npj25-93-11-t3532556) ?
What error do you get?
Click to expand...
Click to collapse
Here it is
I did not use kernel
Oem done
twrp-3.0.2-0-athene
SuperSU-v2.66
My error was that I could not get booted back on...
It would not turn on..
Then i downloaded another stock rom from xda and got back...im xt1643
All steps are followed until flashing of supersu..The error comes there..is there any xt 1643 users who could suggest a correct reliable and error free method for this
Adarsh balu said:
twrp-3.0.2-0-athene
SuperSU-v2.66
My error was that I could not get booted back on...
It would not turn on..
Then i downloaded another stock rom from xda and got back...im xt1643
Click to expand...
Click to collapse
Couple of things:
Try installing the newer TWRP from here: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
I don't think TWRP 3.0.2 is supported that well.
SuperSU - use the SuperSU 2.78 or the beta https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I think if you desire root, you'll need a modified kernel (so far, it appears that the stock kernel security prevents rooting, someone correct me if I'm wrong), which may explain the bootloops. Try with the ElementalX kernel method as linked above, seems that people have had luck with it. https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 You may need phh's Superuser instead.
echo92 said:
Couple of things:
Try installing the newer TWRP from here: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
I don't think TWRP 3.0.2 is supported that well.
SuperSU - use the SuperSU 2.78 or the beta https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I think if you desire root, you'll need a modified kernel (so far, it appears that the stock kernel security prevents rooting, someone correct me if I'm wrong), which may explain the bootloops. Try with the ElementalX kernel method as linked above, seems that people have had luck with it. https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 You may need phh's Superuser instead.
Click to expand...
Click to collapse
Thanks..let me test it....
Any way thnq for the suggestions...:good:
Tell me will i be able to update if android O comes for g4 plus..please reply fast
Adarsh balu said:
Tell me will i be able to update if android O comes for g4 plus..please reply fast
Click to expand...
Click to collapse
If android o does arrive, I imagine you'll have to revert back to the stock ROM to update, so removing root and flashing your stock boot image over your existing installation. Alternatively you could fast boot a stock ROM to restore a stock install.
What's the rush anyway, no announcements have even been made for android o...?
echo92 said:
If android o does arrive, I imagine you'll have to revert back to the stock ROM to update, so removing root and flashing your stock boot image over your existing installation. Alternatively you could fast boot a stock ROM to restore a stock install.
What's the rush anyway, no announcements have even been made for android o...?
Click to expand...
Click to collapse
Im using stock rom..with nougat update....
So if o arrives i will need to do what exactly...please share
Adarsh balu said:
Im using stock rom..with nougat update....
So if o arrives i will need to do what exactly...please share
Click to expand...
Click to collapse
Again, Android O hasn't been formally announced yet...
I see you've already gotten an answer from tywinlannister regarding this question https://forum.xda-developers.com/showpost.php?p=71265934&postcount=249
I don't see much to add to his well thought out reply except if you're staying with stock (assuming you're using temporary TWRP):
1) Unroot completely using the SuperSU settings panel or follow the unrooting instructions for your superuser app.
2) Reboot into temporary TWRP, restore your boot.img (if you flashed ElementalX kernel) from within TWRP (if I recall, it's Restore >Select image and then assign it as a boot image). If you did not make a backup of your boot.img, there are images around (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/1643-indian-version-stock-boot-modem-t3460615 - i don't know if this is for nougat or marshmallow - download and extract the rar file, copy the extracted boot.img to your device and boot into temporary TWRP, then flash the boot.img).
3) Reboot and you should be fully stock - with stock kernel/boot.img, recovery and no root.
1a) As tywinlannister linked, you could just reflash the latest fastboot image which would remove root and give you a stock boot, which would be the best for reliability (which as of this post is this: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
Thus, when/if Android O does arrive, you should be able to update via OTA. It's gonna be at least 6-12 months away for the update, if previous Android updates have been anything to go by.
I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance
2CanSan said:
I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance
Click to expand...
Click to collapse
It's really simple actually: if you install B15 your data will be wiped, after that just skip everything and update to B29 (is B29 the latest? I have a G, dunno) and then use it. What you describe is not the actual performance that it should have, it's your specific case obviously.
I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery
tabletalker7 said:
I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery
Click to expand...
Click to collapse
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.
2CanSan said:
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.
Click to expand...
Click to collapse
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.
tabletalker7 said:
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.
Click to expand...
Click to collapse
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.
2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Choose an username... said:
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.
Click to expand...
Click to collapse
OK on the A2017U units you need the official marshmallow B29 package to roll back, and that only works with stock recovery on a clean B15 N install. The Rollback package I told you to use earlier will roll you back to B29 marshmallow NO MATTER WHAT YOU ARE USING (I have used this a lot, and OBVIOUSLY there are differences between the the A2017U version in North America and the A2017G version in Europe). If you want stock and rooted, I personally recommend B29 marshmallow over B15 Nougat, but either way go for it (I think the marshmallow had a much better radio than any of the Nougat packages). If you are interested in TWRP and root, I found B29 marshmallow much easier for both, and the marshmallow version of android also gives you Xposed, but back to your first post, you mentioned wanting marshmallow, and this is the best way to get it.
Step by Step method
1. Roll back to B15. Use the update.zip method. It will factory reset your device so backup everything you can't lose
2. Use MiFlash to unlock and install TWRP - check that thread on XDA for instructions.
3. (If desired) In TWRP, install the B29 marshmallow rollback. Do not reboot into system afterwards.
4. (If step 3 is done) In TWRP, flash TWRP. The marshmallow rollback will overwrite recovery with stock recovery
If you do this you will have exactly what you wanted in your original post. I can personally tell you this works, as I have tried every custom rom on here and always wind up back at B29 marshmallow when all is said and done. It has never failed me, and it will never fail you either.