Download the magisk manager and patched boot file install apk.... fastboot flash boot patched-boot.img ... And you will have root my device also passes saftey net test
I have uploaded the stock boot, patched boot, and magisk apk
Magisk files
Patched boot stock boot and magisk apk for 8.0 oreo
Good try
I tried your patched boot img but the phone went into a boot loop. re-flashed your stock boot img ok, back to normal (not rooted) pity I really needed Magisk back as the ads are killing [email protected]
Aussiewaterdragon said:
I tried your patched boot img but the phone went into a boot loop. re-flashed your stock boot img ok, back to normal (not rooted) pity I really needed Magisk back as the ads are killing [email protected]
Click to expand...
Click to collapse
Thats wierd i know for shure thats the right boot becasue it made it on my phone and i uploaded it but try to download the magisk manager apk and patch your own boot image and see if that works thats all i did and flashed it with fast boot im using a couple magisk modules to one for face unlock i do t know why they wouldn't include it
No magic in my oreos
dcraffam said:
Thats wierd i know for shure thats the right boot becasue it made it on my phone and i uploaded it but try to download the magisk manager apk and patch your own boot image and see if that works thats all i did and flashed it with fast boot im using a couple magisk modules to one for face unlock i do t know why they wouldn't include it
Click to expand...
Click to collapse
tried that still no luck is your phone a 2.15 non pro?
Aussiewaterdragon said:
tried that still no luck is your phone a 2.15 non pro?
Click to expand...
Click to collapse
Yes and it's on stock 8.0 try to flash TWRP and flash like that
there is no magic left
dcraffam said:
Yes and it's on stock 8.0 try to flash TWRP and flash like that
Click to expand...
Click to collapse
I have twrp works great, still bootloop after flashing patched_boot.img.
could you run this command sequence to see if you phone is the same as mine?
PS C:\Users\norma> adb reboot bootloader
PS C:\Users\norma> fastboot devices
GAAZCY06B681E99 fastboot (If connected shows device number and connection mode)
PS C:\Users\norma> fastboot oem device-info (check phone status)
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen disabled: false
(bootloader) Display panel:
(bootloader) Device oem_adb_enable: 0
(bootloader) Uart status: disable
OKAY [ 0.077s]
finished. total time: 0.080s
thanks in anticipation
cts verification fails even with your patched boot
how did you do??
Ryder. said:
cts verification fails even with your patched boot
how did you do??
Click to expand...
Click to collapse
IDK bro it's wierd I was on the stock boot read this quote and I checked to see if it will pass it failed maby because I had twrp installed but I flashed magisk zip and it passes now that's the only thing I'm doing when I mess my phone up which happens a lot I fix it in fastboot mode with the 8.0 update_image file found in the stock 8.0 Oreo thread if that's making a difference but I don't know
Aussiewaterdragon said:
I have twrp works great, still bootloop after flashing patched_boot.img.
could you run this command sequence to see if you phone is the same as mine?
PS C:\Users\norma> adb reboot bootloader
PS C:\Users\norma> fastboot devices
GAAZCY06B681E99 fastboot (If connected shows device number and connection mode)
PS C:\Users\norma> fastboot oem device-info (check phone status)
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen disabled: false
(bootloader) Display panel:
(bootloader) Device oem_adb_enable: 0
(bootloader) Uart status: disable
OKAY [ 0.077s]
finished. total time: 0.080s
thanks in anticipation
Click to expand...
Click to collapse
My phone reads exactly the same as yours
MAGIC in MAGISK is MAGICAL
dcraffam said:
My phone reads exactly the same as yours
Click to expand...
Click to collapse
Oh the pain, the agony. I got magisk working. Had to do a full Data-Cache-Dalvik wipe, Oreo came up clean, ran TWRP 3.2.1 via Fastboot boot then used the phone to flash itself. Then flashed Magisk installer all good.
Except that I lost data and my apps and titanium backup was on the phone so I lost that for recovery. All the legal apps came down via Google Play but still lost about 60 apps. Used titanium to access apps stored in Nandroid and got most of them back. still fixing up apps with Lucky Patcher, will get there soon I hope.
dcraffam said:
Download the magisk manager and patched boot file install apk.... fastboot flash boot patched-boot.img ... And you will have root my device also passes saftey net test
I have uploaded the stock boot, patched boot, and magisk apk
Click to expand...
Click to collapse
hi.
can you write a detailed tutorial in order to root the deivice with magisk.
i did'n understand how to do.
thanks
dj75 said:
hi.
can you write a detailed tutorial in order to root the deivice with magisk.
i did'n understand how to do.
thanks
Click to expand...
Click to collapse
Can you describe full instruction for root ZS570KL device? Please.
PaulPP said:
Can you describe full instruction for root ZS570KL device? Please.
Click to expand...
Click to collapse
Just rooted my Asus zs570kl
1. Unlock bootloader via unlockTool from Asus site. Warning: all phone data will be erased.
Download for your CPU: (asus.com/en/Phone/ZenFone-3-Deluxe-ZS570KL/HelpDesk_Download)
2. Download ADB and put it to C:\adb folder
3. Download patched_boot.img and copy to adb folder
4. Turn on USB Debugging. Go to: Settings>About phone>Software information> tap on Build number 10 times then go to: Settings>Developer options
5. Connect phone via USB cable (phone is on)
6. Open Windows command line and type:
cd C:\adb
adb reboot bootloader
Phone will reboot to fastboot mode
Type:
fastboot flash boot patched_boot.img
fastboot reboot
7. In Android install MagiskManager.apk
Done. Phone is rooted.
Updated tutorial :good: with Magisk v20
1. Unlock bootloader via unlockTool from Asus site >>>> asus.com/en/Phone/ZenFone-3-Deluxe-ZS570KL/HelpDesk_Download
2. Enable USB Debugging in phone's Developer options
3. Download Magisk-v20.0.zip file and copy to device >>>> github.com/topjohnwu/Magisk/releases
3. Download TWRP for zs570kl >>>> androidfilehost.com/?w=files&flid=219790
3.1 Copy downloaded TWRP file to your adb folder and rename as twrp.img
4. Boot into TWRP
adb reboot twrp.img
4.1 Tap Install > choose Magisk zip file from device and flash it
Reboot.
Done.
Related
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
raystef66 said:
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
Click to expand...
Click to collapse
I have try also boot , try everything, not matter if youhave FRP lock fastboot oem unlock is only to unlock bootloader, which i have, that is not a problem.
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
michalss said:
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
Click to expand...
Click to collapse
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
stiggu said:
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
Click to expand...
Click to collapse
same problem on my mate s
good to know that adb is not working for others
i thaught it was just me
I've the same problem , any idea ??
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Hey , the problem is the device won't boot , so how can we enable developer option?!!!!
Sent from my iPhone using Tapatalk
There was a time when xda where the place to get the right answer and quick!
nowadays most topics are full of people with same problem and no dev to come to help, pity.
on topic: I have the same problem, ( mine is a Y6 pro) and before bricking it I had debugging and oem unlock enabled but now can't flash boot etc using fastboot ( error , denied ..) and can't use spflashtools either : preloader vcom appears for 1 second and then disappears and phone turns on.
tried many drivers, 3 Os'es (7, 8.1 ,10) still no luck.
porcha18 said:
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Click to expand...
Click to collapse
Danke!!!!!!!!!!!!! Nach ewigem Suchen diese einfache Lösung. Vielen Dank!! Tag gerettet
the same issue
Good day, i have the same issue on my p9 EVA-L19.
FRP lock. And i can't do anything...
My warranty says that they cannot recover data from the phone, but the information is very important. I need to unlock FRP and somehow boot into TWRP or something to recover my data.
Please help someone if you had a same issue and results.
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Runner85sx said:
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Click to expand...
Click to collapse
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
anditan said:
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
Click to expand...
Click to collapse
your recovery location in adb is wrong probably. try changing it to the correct path. atleast thats what worked for me
man u can'T do anything because FRP is ACTIVATED !!!
No solution till now
Use the Huawei Swype bypass Method
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
Try to do:
fastboot boot recovery.img
This will boot up the device with the given image. With that you can put a custom rom to your sd-card and flash it.
I will upload a Nandroid (stock system, recovery, boot) from my Y6 SCL-L01 soon.
With that you can restore boot and recovery with twrp. For this way you don't need to have a frp unlock.
Procedure:
fastboot boot recovery-twrp.img
Put your stock firmware (dload folder) to the sdcard.
Put my Nandroid to your sdcard.
Restore my Nandroid, reboot your device with Vol+ and Vol- pressed.
This way only works for SCL-L01 up to SCL-L04.
I need to create an extra recovery.img that includes a dt image that fits for all SCL variants.
Work in progress...
I have just removed frp today, but its not free method, unfortunately
I upgraded my OnePlus X today with the community build OxygenOS 3.1.0 using TWRP. There was an error saying that my device was not "OnePlus" but "ONE". So I edited the updater-script and replaced the word "OnePlus" by "ONE" in getprop line and successfully installed the ROM.
Then I connected my phone to PC, enabled OEM unlock and USB debugging, booted into fastboot and typed -
Code:
fastboot oem unlock
It said Okay, done...but there was not action on the phone screen. It stayed in Fastboot mode. I rebooted the phone and it was the same as before. I thought it was okay and continued with the process by booting into fastboot again and flashing TWRP with the command -
Code:
fastboot flash recovery twrp-3.0.2-0-onyx.img
It was successful. Then something weird happened when I typed -
Code:
fastboot boot twrp-3.0.2-0-onyx.img
The output was downloading image, okay. Then booting and the error FAILED(remote: dtb not found).
I tried manually entering the recovery mode, first by volume down + power button and then by advanced reboot menu -> recovery. All that happens is that it stays stuck in Oneplus Logo screen with powered by android written at bottom. I am able to boot into the OS.
I am sure that the image file is not corrupted as I have used the same before a couple of times. Still I tried flashing Stock recovery and a few other image files of the same version of TWRP. The same error comes up every time. Flashing is successful but booting is not. What should I do?
flash this recovery https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img. If it didn't help, try this http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Is my recovery or bootloader corrupt?
I tried this code -
Code:
fastboot oem device-info
Output was -
...
(bootloader) Device tampered : false
(bootloader) Device unlocked : true
(bootloader) Charger screen enabled : false
(bootloader) Display panel :
(bootloader) console_enabled : 0
(bootloader) exec_console_unconsole : 0
OKAY [0.017s]
finished. total time : 0.018s
The problem is when I type -
Code:
fastboot oem unlock
Nothing pops up on my phone.
Maybe the reason is that I had a rooted version of OxygenOS 2.2.2 with TWRP but when I flashed the community build of OxygenOS 3.1.0 somehow TWRP was missing...
What should I do now? I am back at 2.2.2 now as the beta build didn't suit me. This error still persists. The first link above was stock recovery which did work. But I need TWRP back...
....................
Sorry to bother. Issue solved. It was already unlocked and this time flashing and booting in the image worked idk why...
arunmohan16 said:
flash this recovery https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img. If it didn't help, try this http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
Thank you dude, i have been looking for this all day
I got exactly the same problem, i tested lot of recovery without any luck.
I installed the one from the dropbox, now i got the stock recovery, but, i can do anything, from SDCard or Sideload, the installation of CM13 or Oxygen 3 failed.
Any suggestions ? 4h i tested everything i got in mind to try to fix it.
Thanks
tirlibibi said:
I got exactly the same problem, i tested lot of recovery without any luck.
I installed the one from the dropbox, now i got the stock recovery, but, i can do anything, from SDCard or Sideload, the installation of CM13 or Oxygen 3 failed.
Any suggestions ? 4h i tested everything i got in mind to try to fix it.
Thanks
Click to expand...
Click to collapse
This guide will help you. http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 Use this mini tool, http://forum.xda-developers.com/showpost.php?p=64344611&postcount=4
Hi all,
Firstly, excuse my english...
I'm in OOS in version 2.1.3 (yea, old) with custom recovery and root. I have followed this guide : http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
I have recently decided to upgrade in OOS 3.x and suprised...... Impossible to boot on TWRP.
$ adb reboot bootloader
Click to expand...
Click to collapse
→ fastboot mode OK
$ sudo fastboot devices
[sudo] Mot de passe de torlik :
4c6f1504 fastboot
Click to expand...
Click to collapse
detected, nice !
$ sudo fastboot boot twrp-2.8.7.0-onyx_f2fs_r9.img
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.606s
Click to expand...
Click to collapse
WOOT ?
$ sudo fastboot flash recovery twrp-2.8.7.0-onyx_f2fs_r9.img
target reported max download size of 1073741824 bytes
sending 'recovery' (12130 KB)...
OKAY [ 0.684s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.686s
Click to expand...
Click to collapse
WHAT ?
With VOL- (+) POWER, I boot in Oxygen Recovery, nothing else.
$ sudo fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
(bootloader) Device unlocked: false
How my unlock has been lost ? My phone is yet rooted. SuperSu works correctly.
Can you tell me how it is possible to lost twrp ? I have never upgrade since my unlock.
And now, my only solution is to do a 'fastboot oem unlock' and lost my data ?
Thank you
Not sure whats going on there but easy way is to fastboot flash old stock recovery. Then install 3.1.3 with no problems. Rename file and delete .tar .
Your device bootloader is locked.
Why do you want to flash old TWRP.
To install OOS 3.1.3, you should better flash old OOS stock recovery.
But not sure it wil work.
Now, when you try to reboot recovery, on what recovery are you?
Always TWRP? None?
You should flash Oxygen one, so you can try to flash OOS 2.2.3 full rom zip to start.
Kéno40 said:
Your device bootloader is locked.
Why do you want to flash old TWRP.
To install OOS 3.1.3, you should better flash old OOS stock recovery.
But not sure it wil work.
Now, when you try to reboot recovery, on what recovery are you?
Always TWRP? None?
You should flash Oxygen one, so you can try to flash OOS 2.2.3 full rom zip to start.
Click to expand...
Click to collapse
Thanks for answers.
The issue is exactly that:
"Now, when you try to reboot recovery, on what recovery are you?"
I boot on stock recovery... oxygen recovery instead of twrp. Why?? How??
However I had flash my recovery with twrp last months ago and root my phone.
My problem is I do not want to lost my data... Indeed I can unlock again bootloader but all data will be lost.
How could you flash TWRP if your bootloader is locked? :-S
I don't think you ever get re-locked upon any update..
And yes, you probably have to unlock boot and lose all your user data.. Unless you don't have a backup handy of course :I
You can flash oos 3.1.1 through stock recovery no matter if your bootloader locked or unlocked.
Just download the full rom zip of oos 3.1.1 and place this zip in internal storage and flash with stock recovery. After installing oos3.1.1 you can backup your data and after that you have to go to the developer settings and allow the OEM Unlocking and now you can follow same procedure to unlock bootloader.
Hi,
I just got this Redmi Note 3 because I wanted a device with good support for LineageOS (I'm tired of Samsung...)
I have the PRO version (with dual SIM) and MIUI Global 8.0 stable (so the codename is KENZO).
I'm following this guide https://wiki.lineageos.org/devices/kenzo/install to get LineageOS up and running.
For my understanding (because I have the "global" MI rom), my bootloader is not locked (but how I can be sure?).
Following the LineageOS installation guide I have installed TWRP and flashed LineageOS + Open GApps ARM64 + LineageOS su addon.
The phone is booting with LineageOS, but I can see nothing apart the boot animation (waited 1 hour, but no luck).
I have tried installing only LineageOS without GApps or su, but with no luck.
I have tried 3 different snapshot of LineageOS with no luck.
Before flashing I clean system/data/cache/dalvik.
What I'm missing?
Thanks for any help or idea :fingers-crossed:
Take a look at this article to find out whether your bootloader is locked or unlocked. If it's locked, I would suggest you unlock it officially, then try installing the ROM from the beginning. Good luck.
jimakos98 said:
Take a look at this article to find out whether your bootloader is locked or unlocked. If it's locked, I would suggest you unlock it officially, then try installing the ROM from the beginning. Good luck.
Click to expand...
Click to collapse
Thank you for the hint.
This is the result of my check (I was guessing correctly, my device appears unlocked).
Code:
# fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
I have also tried the ROM Resurrection Remix, with same result... stuck at boot animation...
Any other ideas?
Thanks! :good:
huntz said:
Thank you for the hint.
This is the result of my check (I was guessing correctly, my device appears unlocked).
Code:
# fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
I have also tried the ROM Resurrection Remix, with same result... stuck at boot animation...
Any other ideas?
Thanks! :good:
Click to expand...
Click to collapse
if your bootloader is unlocked, you're good to go.
(you are getting bootloops because of outdated twrp/firmware)
1. flash official twrp or zcx twrp ( search in the forum)
2. download latest stable firmware+ rom+ gapps
3. if you are using miui, backup your internal storage to pc or otg drive.
4. go to twrp, wipe dalvik+data+system+internal storage
5. after that click "format data"
6. then install firmware+rom+gapps
7. reboot
note: as u format internal storage, u'll need a otg drive to flash rom+gapps. u can also use adb push commands. official unlock is mandatory. if you're not sure your device is unlocked officially or unofficially, u might have to flash miui fastboot rom, then get the permission
Simoom Sadik said:
if your bootloader is unlocked, you're good to go.
(you are getting bootloops because of outdated twrp/firmware)
1. flash official twrp or zcx twrp ( search in the forum)
2. download latest stable firmware+ rom+ gapps
3. if you are using miui, backup your internal storage to pc or otg drive.
4. go to twrp, wipe dalvik+data+system+internal storage
5. after that click "format data"
6. then install firmware+rom+gapps
7. reboot
note: as u format internal storage, u'll need a otg drive to flash rom+gapps. u can also use adb push commands. official unlock is mandatory. if you're not sure your device is unlocked officially or unofficially, u might have to flash miui fastboot rom, then get the permission
Click to expand...
Click to collapse
Before I was not updating the firmware. But this time I have updated also the firmware (with no luck )
I've installed:
twrp-3.1.1-0-kenzo.img
miui_HMNote3ProGlobal_7.9.7_Firmware.zip
lineage-14.1-20170906-nightly-kenzo-signed.zip
open_gapps-arm64-7.1-nano-20170910.zip
addonsu-14.1-arm64-signed.zip
All the ZIP are stored on my SD card; I have also wiped dalvik+data+system+internal storage.
But I'm again stuck on boot animation (for more than 25 min).
meh...
Thank you, anyway
huntz said:
Before I was not updating the firmware. But this time I have updated also the firmware (with no luck )
I've installed:
twrp-3.1.1-0-kenzo.img
miui_HMNote3ProGlobal_7.9.7_Firmware.zip
lineage-14.1-20170906-nightly-kenzo-signed.zip
open_gapps-arm64-7.1-nano-20170910.zip
addonsu-14.1-arm64-signed.zip
All the ZIP are stored on my SD card; I have also wiped dalvik+data+system+internal storage.
But I'm again stuck on boot animation (for more than 25 min).
meh...
Thank you, anyway
Click to expand...
Click to collapse
flash rom+gapps
then flash unlock_bootloader.zip
Simoom Sadik said:
flash rom+gapps
then flash unlock_bootloader.zip
Click to expand...
Click to collapse
:good::good::good:
You are the man!
Thank you.
What I was missing was the unlock_bootloader.zip.
After flashing this file, LineageOS booted in around 3 or 4 minutes.
Thank you, again.
I have the same problem
Simoom Sadik said:
flash rom+gapps
then flash unlock_bootloader.zip
Click to expand...
Click to collapse
Is this zip file lock the bootloader or not because it contains emmc.bin please explain
Joyel said:
Is this zip file lock the bootloader or not because it contains emmc.bin please explain
Click to expand...
Click to collapse
it wont
Can you please provide you unlock details
Simoom Sadik said:
it wont
Click to expand...
Click to collapse
You unlockd your bootloader officially or unofficially.because I am fear to do . I'm unlocked unofficially.any command to unlock the zip
Is this zip lock my bootloader
Simoom Sadik said:
it wont
Click to expand...
Click to collapse
Simoom Sadik said:
flash rom+gapps
then flash unlock_bootloader.zip
Click to expand...
Click to collapse
I'm unofficially unlocked my bootloader.im in lollipop boot loader.flashing this file will lock my bootloader itself or not.thanks in advanc
Joyel said:
Is this zip file lock the bootloader or not because it contains emmc.bin please explain
Click to expand...
Click to collapse
Joyel said:
I'm unofficially unlocked my bootloader.im in lollipop boot loader.flashing this file will lock my bootloader itself or not.thanks in advanc
Click to expand...
Click to collapse
unlock officially then. it's not so hard. and safe
i am officially unlocked. mm bootloader
These Files and Guides are NOT for the US Sense Version, use only for the U11 life Android One Version!!!
General information
These Files can restore your Device back to Stock or root your Device. The U11 life Android One Version has a/b partitions, so before flashing something you need to know which parition is active
Reboot your Device into Bootloader
Connect it to your PC and make sure you have a working Fastboot connection with
Code:
fastboot devices
Enter the command
Code:
fastboot getvar all
Search in the result for these lines
Code:
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
That means slot a is active and you need to flash your Files to boot_a and system_a
If slot b is active you need to flash your Files to boot_b and system_b
You can change the active partition using one of these Commands in Bootloader
Code:
fastboot set_active other
fastboot set_active a
fastboot set_active b
If that doesnt work for you, you should update your adb&fastboot installation.
Unlocking Bootloader
Unlocking the Bootloader is only necessary if you want to root your Device or Install a Custom Rom/GSI
Create an Account on https://www.htcdev.com/register/
Go to https://www.htcdev.com/bootloader/
Choose "All Other Supported Models" in the "Select Your Device" list
Click on "Begin Unlock Bootloader"
Follow the instructions to Unlock Your Bootloader
Unlocking the Bootloader will delete all datas on the Device
Bootloader
Turn your Device complete Off
Press and Hold Vol+ first and additional to that Press and Hold Power Button
Your Device will turn on with a Black Screen after a few seconds
Your Device will Start the Bootloader
Here You can Reboot to Bootloader/Download Mode/Recovery and System, Turn the Device Off or Enter Fastboot Commands that are not related to Flashing
Download Mode
Turn your Device complete Off
Press and Hold Vol- first and additional to that Press and Hold Power Button
Your Device will turn on with a Black Screen after a few seconds
Your Device will Start the Download Mode
Connect your Device to the PC and make sure you have a working fastboot connection with
Code:
fastboot devices
Now you can flash Files to your Device with
Code:
fastboot flash boot_<slot> boot.img
or
fastboot flash system_<slot> system.img
where <slot> is a or b depending on your active partition
After flashing a system.img you need to wipe data/cache (Factory Reset in Recovery)
Recovery
Reboot into Bootloader
Choose Reboot to Recovery
Wait till the little Android is there
Press and hold the Power Button and just a short Press to the Vol+ Button
Now you can use the Recovery
For clearing data and cache select "Wipe data/factory reset" and Press the Power Button
Select "Yes" and Press the Power Button again to start This will delete all Files on your Device!
Root
Bootloader must be Unlocked
Flash the patched boot.img for your Systemversion in Download mode using
Code:
fastboot flash boot_<slot> boot.img
where <slot> is a or b depending on your active partition
Download and install Latest Magisk Manager
Open Magisk Manager, Press Install and use "Direct" as method
reboot the Device and enjoy
Pay Attention that there will be a new patched boot.img for every Update
Before installing Updates you have to flash Stock boot.img
Turn off "Automatic System Updates" in Android Developer Settings
OTA Updates with a rooted Device
You need to flash stock boot.img for the Systemversion you are running
Start the OTA Update and finish it with a reboot
Flash the patched_boot.img for the Updated Systemversion and follow the rest of the above instructions to root your device
If the Update still fails you probably changed something on your System, so you need to flash Stock system.img and wipe the device or restore the System with SD card method to install the OTA Update
Restore or Update with SD Card
Download the Full Firmware file of your choice
Rename the file to 2Q3FIMG.zip
Place the file in the Main Folder of your SD card
Turn your Device off
Insert the SD card into your device
Boot your Device into Download Mode
The Download Mode will recognize the File on Your SD card and will ask you to install or cancel
Press Volume Up to start the Update This will delete all Files on your Device!
Restoring/Update will take a couple of minutes
When its done just exit the Download Mode and reboot your Device
If it fails you need to wipe/factory reset the Device using recovery and start the Update/restore again
Android 10
Stock boot.img
stock boot 4.68.401.1
stock Boot 4.64.401.1
stock boot 4.60.401.4
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Android 9
Stock + patched boot.img
stock boot 3.59.401.28
stock boot 3.59.401.27
stock boot 3.59.401.26
stock boot 3.59.401.24
stock boot 3.59.401.23
stock boot 3.59.401.22
stock boot 3.59.401.21
stock boot 3.59.401.20
stock boot 3.59.401.19
stock boot 3.59.401.18
stock boot 3.59.401.16
stock boot 3.59.401.15
stock boot - 3.59.401.10 - patched boot
stock boot - 3.59.401.1 - patched boot
Stock system.img
stock system - 3.59.401.10 - REL: 17/Dec/18 Securitypatch: 01/Dec/18
stock system - 3.59.401.1 - REL: 29/Nov/18 Securitypatch: 01/Oct/18
Full Firmware/Software Files
2Q3FIMG_OCEAN_LIFE_UHL_P90_SENSE10A1_MR_HTC_Europe_3.59.401.15_Radio_sdm630-000062-1810311629A_release_532276_signed_2_4.zip
2Q3FIMG_OCEAN_LIFE_UHL_P90_SENSE10A1_MR_HTC_Europe_3.59.401.1_Radio_sdm630-000062-1810311629A_release_529622_signed_2_4.zip
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Android 8.1
Stock + patched boot.img
stock boot - 2.13.401.4 - patched boot
stock boot - 2.13.401.1 - patched boot
stock boot - 2.12.401.17 - patched boot
stock boot - 2.12.401.14 - patched boot
stock boot - 2.12.401.10 - patched boot
stock boot - 2.12.401.5 - patched boot
Stock system.img
stock system - 2.13.401.4 - REL:29/Oct/18 Securitypatch: 01/Oct/18
stock system - 2.13.401.1 - REL: 25/Sep/18 Securitypatch: 01/Sep/18
stock system - 2.12.401.17 - REL: 03/Sep/18 Securitypatch: 01/Aug/18
stock system - 2.12.401.14 - REL: 23/July/18 Securitypatch: 01/July/18
stock system - 2.12.401.10 - REL: 29/June/18 Securitypatch: 01/June/18
stock system - 2.12.401.5 - REL: 01/June/18 Securitypatch: 01/May/18
Full Firmware/Software Files
2Q3FIMG_OCEAN_LIFE_UHL_O81_SENSE90A1_MR_HTC_Europe_2.13.401.4_Radio_sdm630-000052-1807161147A_release_528293_signed_2_4.zip
2Q3FIMG_OCEAN_LIFE_UHL_O81_SENSE90A1_MR_HTC_Europe_2.12.401.17_Radio_sdm630-000052-1807161147A_release_527523_signed_2_4.zip
2Q3FIMG_OCEAN_LIFE_UHL_O81_SENSE90A1_MR_HTC_Europe_2.12.401.14_Radio_sdm630-000052-1806061526A_release_526629_signed_2_4.zip
2Q3FIMG_OCEAN_LIFE_UHL_O81_SENSE90A1_MR_HTC_Europe_2.12.401.10_Radio_sdm630-000052-1806061526A_release_525228_signed_2_4.zip
2Q3FIMG_OCEAN_LIFE_UHL_O81_SENSE90A1_MR_HTC_Europe_2.12.401.5_Radio_sdm630-000052-1805111121A_release_524726_signed_2_4.zip
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Android 8.0
Stock + patched boot.img
stock boot - 1.10.401.24 - patched boot
stock boot - 1.10.401.18 - patched boot
stock boot - 1.10.401.7 - patched boot
stock boot - 1.10.401.4 - patched boot
stock boot - 1.09.401.2 - patched boot
stock boot - 1.06.401.14 - patched boot
stock boot - 1.06.401.8 - patched boot
Stock system.img
stock system - 1.10.401.24 - REL: 08/May/18 Securitypatch: 01/April/18
stock system - 1.10.401.18 - REL: 02/April/18 Securitypatch: 01/March/18
stock system - 1.10.401.7 - REL: 14/March/18 Securitypatch: 01/Jan/18
stock system - 1.10.401.4 - REL: 26/Jan/18 Securitypatch: 01/Jan/18
Full Firmware/Software Files
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1.10.401.24_Radio_sdm630-005201-1712151436A_release_524002_signed_2_4.zip
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1.10.401.18_Radio_sdm630-005201-1712151436A_release_522793_signed_2_4.zip
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1.10.401.4_Radio_sdm630-005201-1712151436A_release_519785_signed_2_4.zip
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1.09.401.2_Radio_sdm630-005201-1711161228A_release_517786_signed_2_4.zip
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1.06.401.14_Radio_sdm630-005201-1711031628A_release_515519_signed_2_4.zip
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1.06.401.8_Radio_sdm630-005201-1710211215A_release_514620_signed_2_4.zip
Full Firmware/Software Files provided by @MC_Ohr (thx for this)
will this work on oreo roms ?
skylinegtrvspec said:
will this work on oreo roms ?
Click to expand...
Click to collapse
If you have the Android One Version of the U11 life, there is only oreo and nothing else.
Worked perfectly for me, with boot and system 1.10.401.18
Thank you very much
Finally. Thanks
Gesendet von meinem HTC U11 life mit Tapatalk
Any help?
Any helpo? Thank you...
PS C:\Android> fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_ocla1_sprout
(bootloader) version: 1.0
(bootloader) max-download-size: 1148000000
(bootloader) serialno:
(bootloader) slot-count: 2
(bootloader) current-slot: b
(bootloader) imei:
(bootloader) version-main: 1.09.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2Q3F20000
(bootloader) cid: HTC__034
all:
finished. total time: 0.027s
PS C:\Android> fastboot flash system_b system.img
target reported max download size of 1148000000 bytes
Invalid sparse file format at header magi
PS C:\Android>
SOLVED!
Just wiped data and it works ! Thanks GOD. I almost bricked it.
AyaxSK said:
Any helpo? Thank you...
SOLVED!
Just wiped data and it works ! Thanks GOD. I almost bricked it.
Click to expand...
Click to collapse
Great that it worked, thats the reason i wrote "After flashing a system.img you need to wipe data/cache". But please remove your imei and serial number from your post
And a Software Brick is no problem anymore because we have everything here to restore the whole device, as long as the bootloader is working its just a thing of a couple of minutes to restore everything.
saturday_night said:
Great that it worked, thats the reason i wrote "After flashing a system.img you need to wipe data/cache". But please remove your imei and serial number from your post
And a Software Brick is no problem anymore because we have everything here to restore the whole device, as long as the bootloader is working its just a thing of a couple of minutes to restore everything.
Click to expand...
Click to collapse
Done! And thank you again.
Updated post for downloads of Update 1.10.401.24
And reduced the size of the stock system.img file now. Same content, the whole system is in there but just 1,65GB instead of 2,75GB.
Oh I see now... OTA update is not working... If I do install patch and img, all settings will be passed away and phone wiped ?
AyaxSK said:
Oh I see now... OTA update is not working... If I do install patch and img, all settings will be passed away and phone wiped ?
Click to expand...
Click to collapse
For update you need to flash stock boot.img, this will not wipe your device. Just root, magisk, xposed and so on are not working anymore.
saturday_night said:
For update you need to flash stock boot.img, this will not wipe your device. Just root, magisk, xposed and so on are not working anymore.
Click to expand...
Click to collapse
and so on are not working anymore...
So please tell me. I just now want my device to be rooted.
First I should choose new patched boot.img ? Than system.img?
I am confused because you wrote it ROOT
Before installing Updates you have to flash Stock boot.img
So when ve have update what should we do 1st, 2nd etc??
Thanks.
AyaxSK said:
and so on are not working anymore...
So please tell me. I just now want my device to be rooted.
First I should choose new patched boot.img ? Than system.img?
I am confused because you wrote it ROOT
Before installing Updates you have to flash Stock boot.img
So when ve have update what should we do 1st, 2nd etc??
Thanks.
Click to expand...
Click to collapse
Thats all written in first post. For root you dont need system.img, you just need to flash patched_boot.img for your systemversion and follow the rest of the instructions in first post under "Root"
saturday_night said:
Thats all written in first post. For root you dont need system.img, you just need to flash patched_boot.img for your systemversion and follow the rest of the instructions in first post under "Root"
Click to expand...
Click to collapse
Okay.
Another question.
My phone just cant update through OTA with an error. It can download it but not install.
Is it because of patched boot previosly installed?
Should I now install new stock boot - 1.10.401.24
then through OTA update it and then install patched ?
That shouldn't be too hard to understand.
Flash stock boot.img
Run the update
Flash patched boot.img for the bew version
Root your device (again)
Gesendet von meinem HTC U11 life mit Tapatalk
Signor Rossi said:
That shouldn't be too hard to understand.
Flash stock boot.img
Run the update
Flash patched boot.img for the bew version
Root your device (again)
Gesendet von meinem HTC U11 life mit Tapatalk
Click to expand...
Click to collapse
That is what I wanted to read! THANKX !!!!!
,,That shouldn't be too hard to understand."
After flashing boot.img... stucked on androidone loop...
So NOW I think it is hard to understand it...
Anyhoo...
My fault tried to make a phone friendly. Think it was friendly by its way...
To help you, it is important to understand what exactly you did and which files you took.
Gesendet von meinem HTC U11 life mit Tapatalk
Signor Rossi said:
To help you, it is important to understand what exactly you did and which files you took.
Gesendet von meinem HTC U11 life mit Tapatalk
Click to expand...
Click to collapse
Magisk is not working...
Download and install Latest Magisk Manager
Open Magisk Manager, Press Install and use "Direct" as method...
The is nothing asi Direct anymore... Only Zip or Patch boot image... And I did it... patched boot... not working.