Related
After about 3 weeks of trying everything I could find here on XDA and on Google I stumbled on a possible workaround to get root on KitKat:
I started with:
HTC One dual sim 802w (Chinese Unicom); running stock Chinese Jelly Bean 4.2.2.
Chinese 4.2.2 bootloader unlock, CWM recovery, root, S-off through WWE European 4.4.2 if you're interested:
My initial task upon arrival NIB with Chinese Jelly Bean 4.2.2 was to remove chinese bloatware, install CWM recovery, and root following Marrk Daviid's instructions.
Pounded my head on the wall repeatedly trying to get my Windows 8.1 computer with USB 3.0 to work using assorted usb drivers, installing and removing HTC software and multiple HTC drivers without getting a connection for fastboot or adb to get my id token.
I found tobesedated's thread Guide - Suggestion For S-off On 1.55 HBoot Using Ubuntu , then followed pt's blog posting How to fix the adb no permissions error on Ubuntu Lucid to set the udev/rules.d/51-android.rules file to get adb to work, and I was able to get the bootloader unlocked, run rumrunner S-off, CWM recovery and rooted.
Converting to WWE European ROM 4.2.2 then 4.4.2:
I decided to go European so I could update to a Western KitKat, and used fastboot to flash the WWE ROM from shwetkprabhat's thread Guide--HTC Dual Sim 802w (China Unicom), apply WWE European RUU, OTA & CWM or TWRP ( PN07IMG_M7C_DUG_JB_50_S1_HTC_Europe_2.19.401.1_Radio_1237.21.28.0627_release_326125.zip ) using my old Linux 12.04 (Precise) machine after clearing cache. It installed the stock bootloader also, and I didn't mod or change anything, until I received the two small OTAs and a few hours later, the “big” OTA automatically and OK'd the install for dual sim 4.4.2, and waited until the update completed, and root was GONE.
I then had: WWE international 4.4.2, an unlocked bootloader. S-off, NO root, NO custom recovery,
I (re)installed the modified custom recovery for dual sim (called 802w.img) extracted from HTC_802w_CWM_recovery_6.0.4.8.7z posted with Marrk Daviid's instructions and then installed UPDATE-SuperSU-v194.zip from Chainfire (placed in internal storage) through recovery.
After selecting reboot I selected NO for both options (the defaults) and upon restart I had root. If I repeated the process selecting the fix root option (first question No; second question Yes-Fix root) I lost root. I reinstalled above SuperSU through recovery, answered No to both questions and root was back (Root Checker Pro) and functional (and no tampered flag either).
Do I know why/how it worked? Not a clue, but it did work for me.
This fool has now blindly run where angels fear to tread, I hope this information is helpful to the gurus and cautionary to the brave/foolhardy until confirmed.
gaguzman said:
After about 3 weeks of trying everything I could find here on XDA and on Google I stumbled on a possible workaround to get root on KitKat:
I started with:
HTC One dual sim 802w (Chinese Unicom); running stock Chinese Jelly Bean 4.2.2.
Chinese 4.2.2 bootloader unlock, CWM recovery, root, S-off through WWE European 4.4.2 if you're interested:
My initial task upon arrival NIB with Chinese Jelly Bean 4.2.2 was to remove chinese bloatware, install CWM recovery, and root following Marrk Daviid's instructions.
Pounded my head on the wall repeatedly trying to get my Windows 8.1 computer with USB 3.0 to work using assorted usb drivers, installing and removing HTC software and multiple HTC drivers without getting a connection for fastboot or adb to get my id token.
I found tobesedated's thread Guide - Suggestion For S-off On 1.55 HBoot Using Ubuntu , then followed pt's blog posting How to fix the adb no permissions error on Ubuntu Lucid to set the udev/rules.d/51-android.rules file to get adb to work, and I was able to get the bootloader unlocked, run rumrunner S-off, CWM recovery and rooted.
Converting to WWE European ROM 4.2.2 then 4.4.2:
I decided to go European so I could update to a Western KitKat, and used fastboot to flash the WWE ROM from shwetkprabhat's thread Guide--HTC Dual Sim 802w (China Unicom), apply WWE European RUU, OTA & CWM or TWRP ( PN07IMG_M7C_DUG_JB_50_S1_HTC_Europe_2.19.401.1_Radio_1237.21.28.0627_release_326125.zip ) using my old Linux 12.04 (Precise) machine after clearing cache. It installed the stock bootloader also, and I didn't mod or change anything, until I received the two small OTAs and a few hours later, the “big” OTA automatically and OK'd the install for dual sim 4.4.2, and waited until the update completed, and root was GONE.
I then had: WWE international 4.4.2, an unlocked bootloader. S-off, NO root, NO custom recovery,
I (re)installed the modified custom recovery for dual sim (called 802w.img) extracted from HTC_802w_CWM_recovery_6.0.4.8.7z posted with Marrk Daviid's instructions and then installed UPDATE-SuperSU-v194.zip from Chainfire (placed in internal storage) through recovery.
After selecting reboot I selected NO for both options (the defaults) and upon restart I had root. If I repeated the process selecting the fix root option (first question No; second question Yes-Fix root) I lost root. I reinstalled above SuperSU through recovery, answered No to both questions and root was back (Root Checker Pro) and functional (and no tampered flag either).
Do I know why/how it worked? Not a clue, but it did work for me.
This fool has now blindly run where angels fear to tread, I hope this information is helpful to the gurus and cautionary to the brave/foolhardy until confirmed.
Click to expand...
Click to collapse
Alternatively... just install TWRP !!
ascot17 said:
Alternatively... just install TWRP !!
Click to expand...
Click to collapse
Agree it would be much easier and cleaner, if it had worked for me. Touch didn't work after install of 2.7.0.0b, so I gave up on it, and had to reflash CWM to get recovery function and proceed with root. I guess there are still some variations in there that can't be accounted for. I posted this as an interesting observation that might be useful to the devs.
Hi all,
needing help upgrading to MM.
I'm stuck on 1.17.40.1106 since I unlock the bootloader I can't receive further updates.
I've read that to be able to upgrade to MM you need to have .1531 firmware but since I'm stuck, can I sideload MM 21.40.1220 from Lolli 1.17.40.1106?
I have TWRP installed but not rooted.
First if you want sideload u must in "STOCK recovery"
And Seccond if you want update to MM u must have final firmware of LL. Go to asus.com check ur firmware version, If you are using last LL u just download MM firmware copy to sdcard and go to recovery-->apply update from sd card-->choose firmware MM and wait it update
.....
Dont flash firmware of asus.com if u use custom recovery it will brick your phone....
Thanks Val.
I'm having status 7 error both in stock recovery and twrp, another reason why Im stuck.
What are my options?
anyone?
stockdiordna said:
Hi all,
needing help upgrading to MM.
I'm stuck on 1.17.40.1106 since I unlock the bootloader I can't receive further updates.
I've read that to be able to upgrade to MM you need to have .1531 firmware but since I'm stuck, can I sideload MM 21.40.1220 from Lolli 1.17.40.1106?
I have TWRP installed but not rooted.
Click to expand...
Click to collapse
you have twrp but no root? how does that work?
in any case, the Terms of Service of the Asus unlock tool says you will not be able to get OTA update after using. We have confirmed that the unlock tool communicates with Asus when you use it - we highly suspect it sends your phone information to Asus to prevent official OTA.
I would root phone and install ROM.
check this out for issue of installing official MM update with TWRP:
http://forum.xda-developers.com/zen...ne-2-laser-t3399441/post67336853#post67336853
Thanks Eric.
I was reading the links you gave and have this questions:
1. Is it true that if I use custom recovery (TWRP) to sideload official firmware my phone will be bricked?
2. If I do "fastboot erase system" and flash full official firmware such as 1.17.1531, will it erase the custom recovery and go back to stock?
This way I can manually upgrade to MM once in stock recovery.
stockdiordna said:
Thanks Eric.
I was reading the links you gave and have this questions:
1. Is it true that if I use custom recovery (TWRP) to sideload official firmware my phone will be bricked?
2. If I do "fastboot erase system" and flash full official firmware such as 1.17.1531, will it erase the custom recovery and go back to stock?
This way I can manually upgrade to MM once in stock recovery.
Click to expand...
Click to collapse
1)i think twrp will not flash the official firmware, like if you downloaded it from Asus or got the ota .zip.
2) i do not know that command but it scares me to look at it.
in the thread i linked to, was answer to y question about flashing the official MM stock image.
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
Hey people,
I've updated to the unofficial Nougat leak here and ever since I can't get into the recovery. The ROM is OK but no matter what I do I can't get into the recovery. After "adb reboot recovery" I just get stuck in a boot loop and I must get into the upgrade utility and restart phone into the system from there. I've tried to flash few other recovery but nothing works. So far I'm fine with the system and I'd like to also try LineageOS but I have no way to flash the ROM. I have tried "Fastboot flash zip xx.zip" from the bootloader to flash LineageOS but it told me I don't have permissions so it was no good.
So do you folks here have any idea what I did wrong and how to make the recovery work again? I'm kind of learn from the tutorial guy so I'll post the sources I've been using to do the flash.
Unlocking bootloader and flashing new recovery
I've only used the unlock bootloader and flash twrp sections with their provided recovery. I've also tried to flash THIS recovery by Meticulus after the nougat update.
Flashing the ROM + used ROM
Used the old process because upgrade with system utility kept giving me errors.
Model number - VNS-L21
Also if this issue can't be (yet) fixed do you know any way to safely flash ROMs without recovery?
Thanks for any kind of help
You cannot flash any ROM in the nougat recovery, because it does not support /data mounting. Downgrade to MM and install the ROM you want from there.
@SALVO9
Ok, thank you for the reply. I'll probably try to downgrade and flash it afterwards to know which ROM suits me better. All I need to do is find the stock ROM copy it to the phone and restart with all buttons pushed right? Also, do you have any info about when there will be a nougat recovery that can mount /data?
TheAstaros said:
@SALVO9
All I need to do is find the stock ROM copy it to the phone and restart with all buttons pushed right?
Click to expand...
Click to collapse
No.
Flash proper OEMinfo first!
@Schlengge
Thanks for the advice. I did my research because I didn't know a thing about oeminfo and I have hit a wall since my phone is not rooted(Should have mentioned that earlier I know) and I'm supposed to replace custom.bin and then flash the img. So afterwards I searched how to root this nougat ROM and found nothing no app was working and everything I found was just using the phone's recovery which I can't access. Does anything come to mind? I will continue getting through the pages of google but I don't think I'll find anything useful.
EDIT> After some searching I found the official rollback package. I have yet to test it (downloading on slow connection atm) and I hope it will work.
Ok it's finally done and I'm back at old stock ROM(EMUI 4.1.1 VNS-L21C432B160) after hours of searching I gave up on the oeminfo or rooting the phone. I searched for the stock firmware and found some rollback packages on the Huawei site. I will post the links in there you even have instructions packed with the zip.
LINK1
LINK2
Download both start with the smaller one because it's flashing first and follow the instructions in the pdf. Worked for me so hope it also helps you.
Also as I found out just now this rollback also locks back your bootloader so be sure to unlock it back again with the code.
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Sovjohn said:
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Click to expand...
Click to collapse
Hello,
my doubt is that you flashed a different firmware version from the one you had, thus corrupting the device's oem file. Could you post which was the latest complete firmware without this problem and the last one you downloaded and flashed? ( ex. L21CxxxB382 & LxxCxxxB506 ).
Let me know this info ...
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Sovjohn said:
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Click to expand...
Click to collapse
Yep, you used correct file but anyhow the firmware has been corrupted.
I think you have some ways to solve...
1 - if you have stock recovery, reboot into it and
download and flash the same latest firmware.
If you do not have it, you can extract (with huawei update extractor) it
(should be recovery1.img) from B506 firmware (update.zip) you already got,
then can be flashed via fastboot commands.
2 - Flash a previous or B380 firmware via HuRUpdater, then
update to latest via Firmware Finder with dns/vpn method.
3 - Repeat the whole job you done with B506 firmware. (via HuRupdater)
4 - Reboot recovery, reflash L21OEMinfo file, dual sim one, then the latest firmware again...
P.S.: method 1, 2, 4 will re-lock the bootloader, no problem if still you got the code...
Beware method 4, after you flash the oeminfo file do not shout down, reboot to bootloader
and unlock it again with the code. Device will reboot into twrp, then flash B506 firmware.
Good luck and let the community know..