[GUIDE] Rooting from firmware version 226 - Asus ZenFone 4 Max Guides, News, & Discussion

I tried to use the official unlock apk but was since then stuck in a situation that I've been unable to either root or update the system.
Below is my solution:
1. Update the firmware manually following the instruction here:
https://www.asus.com/support/faq/1009748
I couldn't upgrade to version 412 directly, so I tried 232 and succeeded.
I was stuck during the initial configuration but passed through it in safe mode.
2. Do another manual update to version 412.
3. Do this: https://forum.xda-developers.com/zenfone-4-max/how-to/guide-unlock-bootloader-8-1-t3859565
4. Whenever the OS asks for a password, do a full wipe; when the recovery does, simply press the cancel button to bypass it.

I wrotE about it. By thethe wayway, they're is some patchpatch to cancelcancel encryptionencryption on system, with thisthis You getget fullfull accessaccess fromfrom twrp, but lessless security. On 4pda.
Sorry for doublesdoubled words, it's TouchPalTouchPal of Firefox

Related

[Q] root lg d415?

i have tr .apk installed on my phone then i tried to install the root and it says phone is not currently supported is there anyway i can try and root the device?
If you are on the D415-10e firmware you will how to downgrade it to 10c first using LG_Flash_Tool (it's in the forums if you search by that). After downgrading you can use towelroot to root the device and then disable OTA updates by dialing the following code: 3845#*415#
Having entered the system menu, scroll to WLAN Test.
Select OTA Setting option and turn it off by tapping the Disable button. You can search for the 10c firmware also. I am going to try to attach them, but do not know if XDA will let me yet. Anyhow...the instructions for the Flash Tool are at
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
And the fastboot via adb instructions are:
http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457

SafetyNet failed, so i'm trying to go back to stock and restart the process

[Huawei P9 EVA-L09C432B395][Magiskv15.3][TWRP Recovery]
[EMUI 5.0.1][Android version 7.0] [ITA, EU]
Hello everybody,
first of all, i want to say i read several guides in this forums and other ones but i'm still stuck in my newbiness.
I sblocked the bootloader and then i installed twrp
I tried to root my phone using first supersupermissive but i failed and then i met Magisk.
I thought to have rooted successfully my phone with Magisk v15.3, but then i saw that i could not hide from SafetyNet. My google store play says my phone is Not Certified and in the Magisk Manager i can't pass the SN check, instead i got ctsProfile:false and basicIntegrity:false.
Assuming the SuperSu root was in conflict with Magisk, i unistalled and deleted everything concerned SuperSu, reboot the device and then deleted the Google store play datas, but it still says i'm Not Certified and can't pass SafetyNet.
That's why i'm trying to go back to stock rom.
I download Firmware Finder for Huawei but it won't let me download the b395 firmware, and i can't find it on web for EU
Here we are.
I beg for any help
[UPDATE]
I unistalled the root and relock the bootloader, but now my phone is stuck at the Huawei logo and i can't go to recovery mode. I think this happened because i forgot to delete the twrp recovery and forgot to flash the stock recovery.
I can't do anything by computer prompt.
My only hope is wait for the battery to run out...
any ideas?
[UPDATE 2]
I managed to go back in fastboot&rescue mode after a lot of tryes.
In particular i disconnect the cable then recconnect and restart pressing VOLUME DOWN+START keys
I see "PHONE RELOCKED FRP UNLOCK"
[UPDATE 3]
Successfull rollback
waiting to update again the S.O.
should i root the phone now or after it will back to nougat?
Um you need stock recovery my friend. So basically a small rollback otherwise firmware finder wont let you update. After that reupdate b39x. Then you can start the procedure again. There is a topic of how to rollback as well by using twrp and a specific firmware on that post. I'll try to find it for you and post it
vampirian said:
Um you need stock recovery my friend. So basically a small rollback otherwise firmware finder wont let you update. After that reupdate b39x. Then you can start the procedure again. There is a topic of how to rollback as well by using twrp and a specific firmware on that post. I'll try to find it for you and post it
Click to expand...
Click to collapse
Thank you buddy, but I'm not sure i've understood: what do you mean with "rollback"?
You will have to flash a roll back package and use your PC to do the updates.
vampirian said:
You will have to flash a roll back package and use your PC to do the updates.
Click to expand...
Click to collapse
Applying that rollback (i found the package to go back to Emui 4.1, Android 6) the phone will return in stock condition or i have first to unistall Magisk? And what about TWRP recovery?
Read more the forum please its been posted lots of times. But rollback is your only way for now.

I am stuck on firmware LLD-L31C432B128 (8.0.0.128)

I have tried two methods (the two methods that don't fail right from the start) to update with firmware LLD-L31C432B131 (8.0.0.131)
Fastboot Method
start phone in fastboot
flash ramdisk
flash recovery_ramdisk
flash system
All is sucessful, until I reboot and goto About Phone, where Build Number is still 8.0.0.128
HuRUpdate Method
copy [HuRUpdater_0.3.zip, and update.zip] to sdcard
startup phone in TWRP recovery
install HuRUpdater_0.3.zip
All is sucessful, until I reboot and goto About Phone, where Build Number is still 8.0.0.128
I found B131 on huawei-firmware.com/phone-list/huawei-honor-9-lite, but there appears to be no B128 anywhere.
My question, is this phone (Honor 9 Lite - LLD-L31 C432) able to updated?
If so, what is the correct way?
Yes you can update to B131, I have updated from B128 to B131 via using the FF tool and using the VPN option, then followed by going into the System area to update the from there.
Thanks hacktrix2006.
Okay, my problem was, I was afraid of ending up with an expensive brick, so, in all my efforts, I excluded this, update_all_hw.zip (update_full_LLD-L31A_hw_eu.zip), file.
I finally decided to include it, and HuRUpdater worked. It reported, unknown command, but it continued to work.
My version now is 8.0.0.131, and my S/N and IMEI are all intact.
PS: I prefer the TWRP + HuRUpdater method, because I could use my existing downloaded update. I didn't want to keep downloading 2.5GB over and over again.

Bricked Honor 5c NEM-L51 ?

Hi, I think i've kinda bricked my honor 5C (nem-l51), and I really need help :
A few years ago I rooted my phone to make otg work.
It worked a little while, but then a system update came up, could not update because of the twrp, so I tried to unroot it (from supersu) to do the update, and the twrp stayed after the unroot.
I stayed with the phone like this, twrp installed and update pending (still trying to install the update from time to time) and then I had to use OTG again and tried to re-root my phone.
I tried to flash the supersu files I used the first time, but, even when the flashing worked, I couldn't see the supersu app on the phone, still unrooted.
Then I tried to change the twrp (via fastboot) and I realised that I couldn't : I get the "command not allowed" failure when the recovery should get written. I tried with numerous twrp versions, and stock recovery.
So my twrp right now is the twrp-3.1.1-0-venus "OpenKirin edition" one.
The phone says it's unlocked and the frp is locked, but I can't remember if it was already the case or not when I first rooted.
I unfortunately don't have anymore the bootloader unlock code that huawai gave me originally. I have no idea how to get it again, to try to re-lock/unlock the bootloader.
Back then when I first rooted my phone, I made a back up, so I tried to restore that back up. It failed, first with "cannot wipe the cust partition". Then I tried to restore without restoring the cust partition, and I got "extracttarfork() process ended with error 255" while the system was restoring.
After that, the phone wouldn't boot into android anymore. It would be stuck at the unlocked bootloader warning message and then reboot after a few minutes.
So, lastly, I tried to install the unofficial lineageOS port from here : https://forum.xda-developers.com/honor-5c/development/rom-lineageos-14-1-honor-5c-t3713911 with my twrp.
The installation went well, but the phone is stuck while first booting in lineageOS (I let it overnight, restarted it, re-installed it, tried with the first release, nothing).
TL;DR: My phone isn't booting and I can't flash any new recovery.
Please, help me to get my phone working again
Give me the
old build number on emui
Update build you received..
Twrp working?
Fastboot?
Erecovery?
I got access to erecovery, even if the "download latest version and recovery" doesn't work. (erecovery connects to wifi, and the first thing it tries to check/download fails)
I can boot into fastboot but can't flash recovery from there because of the command not allowed problem.
I can boot into twrp, but the back up I tried to restore and the lineageos rom I tried to install both failed, so maybe the twrp has a problem?
I'm sorry I'm not sure about the build number, I'm pretty sure I was on EMUI 5.0 and android 7.x, and I think I remember comparing current build number vs the update, and it was something like B350 or B351 for the current, and B355 or B375 for the update.
I've found this in my backup file 'recovery.log' ro.omni.version=6.0.1-20160703-nemo-HOMEMADE and ro.build.id=MOB30M . So, that mean that I had android 6.x when I did the backup, way back at the beginning.
I thought the update never got installed because each time the phone would reboot to complete installation, it would reboot into twrp. But I've still updated from android 6 to android 7 somehow ?
NEM-L51C432 or NEM-L51C10 ?
NEM-L51C432 and I'm sure of that ^^
Zhyrclew said:
NEM-L51C432 and I'm sure of that ^^
Click to expand...
Click to collapse
Flash this via twrp
http://update.hicloud.com:8180/TDS/...-L51_hw_eu/update_data_full_NEM-L51_hw_eu.zip
Once done, boot to twrp and flash this
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v82938/f1/full/update.zip
Reboot.
If you are unable to flash the 2nd link then just use the dload method to flash this. If you are not aware of dload method, link is given in my signature.
Note, this 2nd firmware will replace your twrp with stock recovery. You should boot to b350 version and it will be full stock. Reason for flashing data file first is it doesn't replace the recovery to stock but just flashes your data, settings, apps. And 2nd link is main full firmware which will replace your boot, recovery, vendor everything and should boot.
Good luck
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Zhyrclew said:
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Click to expand...
Click to collapse
You may try other higher versions like 360, 370 etc and see your luck. Twrp will be replaced only if the installation os successful for the main firmware. Its just a trial and error for you now but I am 99% sure you should be able to revive the phone via dload method
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Zhyrclew said:
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Click to expand...
Click to collapse
Firmware finder website
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Zhyrclew said:
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Click to expand...
Click to collapse
Check dload guide in my signature. You can follow that now. Good luck
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Zhyrclew said:
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Click to expand...
Click to collapse
Copy them on PC and then try dload of files you downloaded from Firmware finder website.
These are files your phone downloaded for OTA update but as you were on twrp, they never installed it amd stays there
I copied the updates my phone downloaded on PC and then deleted them both on internal storage and sd card.
Then I tried dload method with b355,b375&b377 from firmware finder, and also with the update.zip I found in the updates my phone downloaded.
Nothing worked, all of them got the error "Incompatibility with current version. Please download the correct update package."
Should I try even more firmware versions, or should I try something else ?
Btw, I noticed my phone, when connected to my PC, is labeled as huawei-P9-lite, and I don't think it was always like that, but it's probably just because the twrp-3.1.1-0-venus.img is originally for the P9 lite.
I came accross this thread, where somebody recommends to flash stuff from fastboot.
I have not tried it yet, I only tried to flash recovery from fastboot, and it is failing with the "command not allowed". But maybe I could try to flash some other things ? Any advice ?
For now, despite all my attempts to install stock OTA via dload method, the phone is still trying to boot into lineageOS, and failing.
I came across the "current" firmware version with a check with DC-unlocker : "NEM-L51C432B120"
So I downloaded full OTA firmware b120 on firmware finder software, and the dload method worked !
The installation went well, and after a few minutes of the first boot, I got into phone configuration.
I have one last problem, though : the phone configuration is looping.
There is only 4 languages to choose, so I have to choose english(US), then there is a weird list of countries, none in the EU, where I feel i have to choose united states, then after some steps I have to register to huawei ID thing.
If I try to skip it, it loops to the language selection.
If I try to log in to my original account, it says "device not supported for your location" and then loops to languages. (my original account is in french/France)
If I try to create a new account with new address mail, it works but then at the end says again that "device not supported for your location" and then loops to languages.
I tried with other countries it still loops.
The other languages seems to be Chinese and Japanese, but the configuration is looping too if I choose them.
I tried with/without sim, with/without wifi connected...
Dload the next firmware now and see if it works. Then set the phone
I downloaded and installed with dload method (by removing sd card and copying directly on it the files, because I don't know how to have access to the phone internal & external memory now) the next firmware (b130 version)
The phone booted, it launched a "system optimization" that was a few minutes long, and then the EMUI configuration poped up and looped through language selection, region(country), wifi connection (successful), terms and conditions, and WLAN+(switch between wlan and mobile data automatically).
I feel like the phone is working, the notification led is even blinking when I receive sms, but I have access to nothing because of this damned configuration.
Note: the connection to huawei ID isn't prompted again in the loop once I log in, from the original or the new account. In order to be prompted again to log in to the huawei ID, I have to go to erecovery and reset to factory the phone.

Is there a step by step tutorial on how to root US version of ROG2?

Any thread that shows how to update to latest firmware and have root on WW rom or US version?
I know I have to patch the boot img through magisk. But how can I get the boot img? I have the US version and my build number is different from everything listed on ASUS website.
I don't see that firmware on the Asus site, maybe it never auto updated on initial setup. I rooted on 1907.33 firmware so maybe try updating to that then root.
1. Download firmware WW-16.0622.1907.33 from Asus to the root of your phone (take it out of download folder and put directly in internal memory no folder)
2. Reboot the phone, upon reboot you will be asked to install the updated firmware. Install and reboot.
To root;
3. Sign out of google account
4. Download and install Asus bootloader unlocker apk HERE
(this will wipe your device so backup anything you need on the phone first. Also the phone may boot twice DO NOT press power button to pause the boot process)
5. Now your bootloader is unlocked and 1907.33 firmware installed you can follow this guide to root the device. (since you are on 1907.33 start at step 4. Only do steps 4-7 in this guide)
To udate to latest firmware;
6. Delete the previous firmware 1907.33 you just downloaded on internal memory. Download the new WW-16.0631.1908.12 and put it in internal memory no folder.
7. Follow this guide HERE
no go0d said:
I know I have to patch the boot img through magisk. But how can I get the boot img? I have the US version and my build number is different from everything listed on ASUS website.
Click to expand...
Click to collapse
Follow this guide: https://forum.xda-developers.com/rog-phone/how-to/guide-root-t3865490
Rooted mines yesterday.

Categories

Resources